diff --git a/locale/uk/404.md b/locale/uk/404.md
new file mode 100755
index 0000000000000..4481f3bdb99ff
--- /dev/null
+++ b/locale/uk/404.md
@@ -0,0 +1,7 @@
+---
+layout: page.hbs
+permalink: false
+title: 404
+---
+## 404: Сторінку не знайдено
+### ENOENT: немає такого файла або каталога
diff --git a/locale/uk/about/advisory-board/index.md b/locale/uk/about/advisory-board/index.md
new file mode 100755
index 0000000000000..b41215a93deb3
--- /dev/null
+++ b/locale/uk/about/advisory-board/index.md
@@ -0,0 +1,220 @@
+---
+layout: about.hbs
+title: Консультативна рада
+---
+# Хартія консультативної ради Node.js
+
+## 1. Background
+
+The Node.js open source project is continuing its rapid growth of adoption in
+the market. Given the large numbers of contributors, users, and companies with
+a stake in the future of the project, the project leadership is looking to
+supplement the current governance and contribution mechanisms with an advisory
+board, as part of its long-term commitment to create a more open governance
+model.
+
+## 2. Purpose
+
+### 2.1
+
+The primary purpose of the Node.js Advisory Board is to advise Joyent and the
+Node.js project core committers team leadership on matters related to
+supporting the long-term governance, structure, and roadmap of the Node.js open
+source project. The following main areas are included in this charter:
+
+  * Provide a forum for individuals, users, and companies to discuss the issues
+    under the scope listed below.
+  * Provide guidance and input to leadership, and where possible, present a
+    consistent and consolidated opinion from the broader Node.js community.
+
+### 2.2
+
+The Node.js Advisory Board is not:
+
+  * Intended to serve as an authoritative governance board. The Node.js
+    Advisory Board advises, but does not manage the Node.js project core
+    committers team leadership.
+  * Intended to replace existing mechanisms for community input, governance,
+    or contribution.
+  * Intended to assume a formal, fiduciary role with respect to the project.
+    The Node.js Advisory Board members will not be asked to provide funds to
+    the project, assume liabilities with respect to the project or their
+    activities, or assume responsibility for enforcing either trademarks or
+    Node.js Advisory Board recommendations.
+
+## 3. Scope
+
+### 3.1
+
+The Node.js Advisory Board is expected to provide input and formal
+recommendations regarding the following areas:
+
+  * Node.js project long term roadmap
+  * Node.js project policies and procedures around maintenance, contributions,
+    core team membership and governance.
+  * Node.js project policies and procedures around intellectual property,
+    trademark, and licensing
+  * Node.js project release schedules
+
+## 4. Meetings and Memberships
+
+### 4.1 General
+
+  * The Node.js Advisory Board will have 13 members
+  * The Node.js core committers project lead: TJ Fontaine
+  * 2 seats for the top core technical contributors
+  * Up to 8 additional seats: 4 corporate seats, 4 “user” seats
+  * One curator seat
+  * One Open Source Software guidance seat
+  * No fee or sponsorship is required for membership
+  * The membership term will last 12 months. With the exception of the Project
+    Lead, all members can serve a maximum of two consecutive terms
+
+### 4.2
+
+The selection process is intended to be open, transparent, and guided by
+objective criteria for membership.
+
+### 4.3
+
+The Curator shall prepare an agenda for and preside over regular meetings of
+the Node.js Advisory Board. These meetings shall occur as frequently as the
+Node.js Advisory Board determines is in the project’s best interest, but no
+less than quarterly.
+
+### 4.4
+
+A member of the Node.js Advisory Board may be removed by a resolution of the
+Node.js Advisory Board supported by more than two thirds of its membership.
+
+### 4.5
+
+The Node.js Advisory Board may fill any vacancy arising by removal or
+resignation by a simple majority vote to fill the remainder of the term of the
+vacating member.
+
+### 4.6
+
+The rules of election and membership outlined in this section may be varied by
+a resolution of the Node.js Advisory Board supported by more than two thirds of
+its voting membership.
+
+### 4.7
+
+All project contributors are welcome to observe at Node.js Advisory Board
+meetings.
+
+## 5. Selection Process
+
+### 5.1 Contributors
+
+Two seats will be granted to the top technical contributors, as measured by
+non-trivial pull requests as determined by the core contributor team that have
+been merged into the master in the previous 6 months.  These seats will be
+reserved for active individual contributors who are neither employees of
+Joyent, Inc. nor employees of companies that hold a corporate seat.
+
+### 5.2 Corporate seats
+
+Nomination is restricted to companies for whom all three of the following are
+true:
+
+  * Are in the top 5 companies in terms of non-trivial pull requests merged
+    into the master in the past six months as measured by contributions by the
+    entire organization.
+  * Have one or more employees for whom a key component of their job
+    description is to contribute to Node.js and/or make significant
+    contributions to the Node.js source code base.
+  * Have committed to integrate Node.js into widely used corporate products in
+    a manner consistent with Core Criteria listed in Section 8 below.
+
+### 5.3
+
+Once nominations haves been closed, selection of corporate seats will be made
+by a vote by eligible contributors. Eligible contributors are those who remain
+active as a contributor and have had at least one non-trivial pull request
+merged to master in the previous six months.
+
+### 5.4 User seats
+
+These seats are for organizations that are using Node.js. To be nominated, an
+end-user company must currently be using Node.js in production and have
+published a use case on the Node.js website.  Once nominations have been
+closed, selection will be made by a vote by eligible contributors. Eligible
+contributors are those who are currently active and have had at least one
+non-trivial pull request merged to master in the past six months.
+
+## 6. Operation
+
+### 6.1
+
+The Node.js Advisory Board is authorized to seek advice and counsel from other
+interested parties and invited experts as appropriate.
+
+### 6.2
+
+Any outside party wishing to bring an issue before the Node.js Advisory Board
+may do so by emailing the Node.js Advisory Board at
+[advisoryboard@nodejs.org](mailto:advisoryboard@nodejs.org).
+
+### 6.3
+
+The Node.js Advisory Board shall provide transparent and timely reporting
+(through any mechanism it deems appropriate) to the Node.js community at large
+on all of its activities, subject to the right of any individual to designate
+their comments and the ensuing discussion as "in confidence," in which case the
+public report shall contain only a note of the request and an agreed summary
+(if any) of the substance.
+
+### 6.4
+
+The Node.js Advisory Board is being formed at the discretion of Joyent.  Joyent
+alone may decide to terminate the Node.js Advisory Board in its sole
+discretion; provided however, that Joyent shall first consult the Node.js
+Advisory Board and Curator.
+
+### 6.5
+
+The Node.js Advisory Board and its members shall abide by appropriate antitrust
+guidelines.
+
+## 7.  Open Governance Principles
+
+The Node.js Advisory Board will formulate recommendations in conjunction with
+the following open governance principles:
+
+  * Open Contributions: anyone should be able to participate and contribute.
+    All bugs and tasks will be tracked in a public tracker and all of the
+    source code and all of the tools needed to build it will be available under
+    an open license permitting unrestricted use.
+  * Open technical meritocracy: technical merit over pride of authorship. Code
+    is contributed for the express purpose of advancing technologies relevant
+    to the project, effectively separating technology advancement from
+    individual or commercial intent.
+  * Open design: Roadmaps are discussed in the open, and designs receive input
+    from all committers and contributors.
+  * Influence through contribution: organizations and individuals gain
+    influence over the project through contribution.
+  * Open Licensing: code is licensed under the MIT license.
+
+## 8.  Core Criteria
+
+Core Criteria will generally cover such areas as: use of standard APIs, testing
+harness, quality assurance, upstream contribution models, and alternative
+distributions.
+
+As Core Criteria will not be fully defined when the initial Node.js Advisory
+Board membership is formulated, it is understood that there is a possibility
+that certain members of the initial Node.js Advisory Board may not agree with
+the Core Criteria when they are fully defined or may have products/offerings
+that are not in compliance with the Core Criteria at the time they are
+finalized. In this case, the corporate members will either agree to become
+compliant within a specified timeframe or else resign their Node.js Advisory
+Board position.  Read more about the announcement
+[https://www.joyent.com/blog/node-js-advisory-board](https://www.joyent.com/blog/node-js-advisory-board).
+
+Please help us improve this draft by sending your comments and feedback to
+[governance@nodejs.org](mailto:governance@nodejs.org).
+
+The source for this document can be found [in this
+repository](https://github.com/nodejs/nodejs.org/blob/master/locale/en/about/advisory-board/index.md).
diff --git a/locale/uk/about/advisory-board/members.md b/locale/uk/about/advisory-board/members.md
new file mode 100755
index 0000000000000..49619eb63cef1
--- /dev/null
+++ b/locale/uk/about/advisory-board/members.md
@@ -0,0 +1,65 @@
+---
+layout: about.hbs
+title: Члени консультативної ради
+---
+# Члени консультативної ради
+
+## Bert Belder
+
+ * StrongLoop, Inc.
+
+## Danese Cooper
+
+ * Expert in Open Source Communities
+
+## Kevin Decker
+
+ * Walmart
+
+## TJ Fontaine
+
+ * Joyent
+
+## Dav Glass
+
+ * Yahoo
+
+## Scott Hammond
+
+ * Joyent
+
+## Cian Ó Maidín
+
+ * nearForm
+
+## Todd M. Moore
+
+ * IBM
+
+## Gianugo Rabellino
+
+ * Microsoft Open Technologies, Inc.
+
+## Issac Roth
+
+ * StrongLoop, Inc.
+
+## Chris Saint-Amant
+
+ * Netflix
+
+## Isaac Schlueter
+
+ * npm
+
+## Dan Shaw
+
+ * NodeSource
+
+## Erik Toth
+
+ * PayPal
+
+## Chris Williams
+
+ * Emerging Technology Advisors
diff --git a/locale/uk/about/governance.md b/locale/uk/about/governance.md
new file mode 100755
index 0000000000000..e3bc10c8a2aae
--- /dev/null
+++ b/locale/uk/about/governance.md
@@ -0,0 +1,123 @@
+---
+title: Управління проектом
+layout: about.hbs
+---
+# Управління проектом
+
+## Технічний керівний комітет
+
+Цей проект спільно керується Технічним керівним комітетом
+(Technical Steering Committee (TSC)), що є відповідальним
+за найвищий рівень координування проектом.
+
+TSC має остаточне авторство над цим проектом, включаючи:
+
+* технічне спрямування;
+* управління проектом та процесом (включаючи цю політику);
+* політику співпраці;
+* хостинг GitHub–репозиторіїв;
+* керівництва з поведінки;
+* підтримку списку додаткових співаторів.
+
+В першу чергу запрошення на участь у TSC були дані тим особам, які
+були активними учасникам та мають значний досвід в управлінні проектом.
+Членство передбачає повну зайнятість, відповідно до потреб проекту.
+
+Поточний список учасників TSC можна знайти в
+[README.md](https://github.com/nodejs/node/blob/master/README.md#tsc-technical-steering-committee) проекту.
+
+## Співавтори
+
+GitHub–репозиторій [nodejs/node](https://github.com/nodejs/node)
+підтримується TSC та додатковими співавторами, що були додані
+TSC на постійній основі.
+
+Особи, що роблять значні та важливі внески стають співавторами
+та отримують доступ на запис (commit-access) у проект. Вони
+ідентифікуються через TSC і їх залучення як співавторів
+обговорюється протягом щотижневих зустрічей TSC.
+
+_Зауважте:_ Якщо ви зробили значні внески і надання вам доступу на запис
+не було розглянуто, відкрийте issue або зв’яжіться безпосередньо з членом TSC,
+щоб вашу кандидатуру розглянули на наступній зустрічі TSC.
+
+Модифікації контенту в репозиторії nodejs/node відбуваються на
+співавторській основі. Будь–хто з GitHub–аккаунтом може запропонувати
+зміни через пул-реквест, який розглянуть співавтори пректу.
+Всі пул–реквести повинні пройти ревізію та приймаються співавторами, які мають достатній досвід і можуть взяти відповідальність за ці зміни.
+У випадку, якщо пулл–реквест пропонується існуючи співавтором, вимагається
+первірка іншого співавтора. Слід шукати консенсусу, якщо інший співавтор
+брав участь і виникли розбіжності стосовно конкретної зміни. Дивіться
+_Процес пошуку консенсусу_ нижче для додаткоих деталей стосовно
+консенсусної моделі, що використовується в управлінні.
+
+Співавтори можуть винести на обговорення на TSC значні або суперечливі зміни,
+або модифікації, що не знайшли консенсусу шляхом присвоєння пул–ревкесту,
+або issue тегу ***tsc-agenda***. TSC має підготувати остаточне рішення,
+за потреби.
+
+Щоб побачити поточний список співавторів перегляньте
+[README.md](https://github.com/nodejs/node/blob/master/README.md#current-project-team-members) проекту.
+
+Керівництво для співавторів знаходиться у
+[COLLABORATOR_GUIDE.md](https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md).
+
+## Членство в TSC
+
+Однак, очікується, що буде від 6 жо 12 учасників, збалансованих
+на здатності ефективно ухвалювати рішення для забезпечення адекватного
+покриття у важливих областях.
+
+У цих правилах немає особливих вимог чи бажаного рівня кваліфікації
+для членства у TSC.
+
+TSC може додавати додаткових членів у TSC за стандартною схемою TSC.
+
+Член TSC може бути виключеним з TSC через добровільну відставку,
+або за стандартною схемою TSC.
+
+Зміни у членстві в TSC слід публікувати у порядку денному.
+Вони можуть висуватись як і будь–який інший пукт порядку денного
+(дивіться "Зустрічі TSC" нижче).
+
+Не більш як 1/3 від всіх членів TSC можуть бути пов’язані одним роботодавцем.  
+Якщо виключення чи реєстрація нового члена TSC, або зміна місця роботи
+поточного члена TSC, створює ситуацію за якої третина всіх учаників TSC
+мають спільного роботодавця, ця ситуація має негайно вирішитись шляхом
+реєстрації, або видалення одного, або більше учасників TSC,
+які пов'язані різними роботодавцями.
+
+## Зустрічі TSC
+
+TSC щотижня зустрічається вживу через Google Hangout.
+Зустріч відбувається під керівництвом модератора, назначеного TSC.
+Кожну зустріч слід публікувати на YouTube.
+
+Елемени, які додаються до порядку денного TSC, які вважаються суперечливими:
+зміна управління, політики внесків, членство TSC або процес релізів.
+
+Порядок денний не має ставити за мету прийняти або розглянути всі питання.
+Це має продовжуватись на GitHub за участі великої кількості співавторів.
+
+Будь–який член спільноти або учасник може попросити додати щось до порядку денного наступної зустрічі через GitHub Issue. Будь–який співавтор,
+член TSC або модератор може додати це питання до порядку денного додавши до відповідної issue тег ***tsc-agenda***.
+
+Перед кожною зустріччю TSC модератор поширює порядок денний між членами TSC.
+Члени TSC можуть додавати до порядку денного будь–які питання на початку
+кожної зустрічі. Модератор TSC не може накладати вето або вилучати питання.
+
+TSC може запрошувати до участі без права голосу осіб, що презентують певні проекти. Ці запрошення на разі:
+
+* Представник [збірки](https://github.com/node-forward/build)
+  обраний цим проектом.
+
+Модератор відповідальний за підсумки дискусії стосовно кожного з пунктів порядку денного та надсилання їх у вигляді пул–реквесту піля зустрічі.
+
+## Процес пошуку консенсусу
+
+TSC дотримується моделі, що приймає рішення, які базуються на
+[пошуку консенсусу](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making).
+
+Коли пункт порядку денного досягає консенсусу, модератор запитує: "Хто–небудь має заперечення?" — це є останнім закликом до відходу від консенсусу.
+
+Якщо пункт порядку денного не досягає консенсусу, член TSC може закликати до заключного голосування або голосування щодо перенесення питання до наступної зустрічі. Заклик до голосування має бути затверджений більшістю у TSC, інакше дискусія має продовжуватись. Проста більшість виграє.
diff --git a/locale/uk/about/index.md b/locale/uk/about/index.md
new file mode 100755
index 0000000000000..d866fbc82158f
--- /dev/null
+++ b/locale/uk/about/index.md
@@ -0,0 +1,70 @@
+---
+layout: about.hbs
+title: Про проект
+trademark: Торгова марка
+---
+# Про Node.js®
+
+Як асинхронне подієве JavaScript–оточення, Node спроектований для побудови
+масштабованих мережевих додатків. У нижче наведений приклад "hello world", який
+може одночасно обробляти багато з’єднань. Для кожного з’єднання викликається
+функція зворотнього виклику, проте коли з’єднань немає Node засинає.
+
+```javascript
+const http = require('http');
+
+const hostname = '127.0.0.1';
+const port = 3000;
+
+const server = http.createServer((req, res) => {
+  res.statusCode = 200;
+  res.setHeader('Content-Type', 'text/plain');
+  res.end('Hello World\n');
+});
+
+server.listen(port, hostname, () => {
+  console.log(`Server running at http://${hostname}:${port}/`);
+});
+```
+
+Це контрастує з більш загальною моделлю в якій використовуються паралельні OS
+потоки. Такий підхід є відносно неефективним та дуже важким у використанні.
+Більше того, користувачі Node можуть не турбуватись про блокування процесів,
+оскільки немає жодних блокувань. Майже жодна з функцій у Node
+не працює напряму з I/O, тому процес не блокується ніколи. Оскільки нічого
+не блокується на Node легко розробляти масштабовані системи.
+
+Якщо щось у цьому підході є незрозумілим для вас, то можете переглянути
+повну статтю [Blocking vs Non-Blocking][].
+
+---
+
+Node створений під впливом таких систем як [Event Machine][] в Ruby або
+[Twisted][] в Python. Node використовує подієву модель значно ширше,
+він приймає [цикл подій (event loop)][] за основу оточення, замість того,
+щоб використовувати його в якості бібліотеки. В інших системах завжди стається
+блокування виклику, щоб запустити цикл подій.
+
+Зазвичай поведінка визначається через функції зворотнього виклику на початку
+скрипта і в кінці запускає сервер через блокуючий виклик,
+як от `EventMachine::run()`. В Node немає нічого подібного на виклик початку
+циклу подій. Node просто входить в подієвий цикл після запуску скрипта на
+виконання. Node виходить з подієвого циклу тоді, коли не залишається
+зареєстрованих функцій зворотнього виклику. Така поведінка схожа на поведінку
+браузерного JavaScript: подієвий цикл прихований від користувача.
+
+HTTP є об'єктом першого роду в Node, розробленим з потоковістю та малою затримкою. Це робить Node хорошою основою для веб–бібліотеки або фреймворку.
+
+Те що Node спроектований без багатопоточності, не означає, що ви не можете
+використовувати можливості кількох ядер у вашому середовищі. Ви можете
+створювати дочірні процеси, якими легко керувати з допомогою API
+[`child_process.fork()`][]. Модуль [`cluster`][] побудований на цьому
+інтерфейсі і дозволяє вам ділитись сокетами між процесами та
+розподіляти навантаження між ядрами.
+
+[Blocking vs Non-Blocking]: https://github.com/nodejs/node/blob/master/doc/topics/blocking-vs-non-blocking.md
+[`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options
+[`cluster`]: https://nodejs.org/api/cluster.html
+[event loop]: https://github.com/nodejs/node/blob/master/doc/topics/the-event-loop-timers-and-nexttick.md
+[Event Machine]: http://rubyeventmachine.com/
+[Twisted]: http://twistedmatrix.com/
diff --git a/locale/uk/about/organization.md b/locale/uk/about/organization.md
new file mode 100755
index 0000000000000..32006a0235935
--- /dev/null
+++ b/locale/uk/about/organization.md
@@ -0,0 +1,40 @@
+---
+layout: about.hbs
+title: Організація
+---
+# Організація
+
+## Співавтори і Технічний керівний комітет
+
+Проект Node.js спонсорується Node.js Foundation і підтримується окремими
+учасниками. Технічний керівний комітет (Technical Steering Committee (TSC))
+складається з ключових учасників, що продемонстрували як свої спеціальні
+технічні знання і практичну підтримку, так і сприяння потсупальному розвиткові
+проекту та спільноті.
+
+Ви можете дізнатись більше про те, як стати учасником та членом TSC у
+[розділі для учасників](/contribute/).
+
+### Поточні учасники
+
+Наразі, проект Node.js має понад 300 учасників, що активно працюють над різними
+частинами проекту. Поточний список учасників можна знайти у
+[профілі проекту на GitHub](https://github.com/orgs/nodejs/people).
+
+### Поточні члени Технічного керівного комітету
+
+* Alexis Campailla ([orangemocha](https://github.com/orangemocha))
+* Ben Noordhuis ([bnoordhuis](https://github.com/bnoordhuis))
+* Bert Belder ([piscisaureus](https://github.com/piscisaureus))
+* Brian White ([mscdex](https://github.com/mscdex))
+* Chris Dickinson ([chrisdickinson](https://github.com/chrisdickinson))
+* Colin Ihrig ([cjihrig](https://github.com/cjihrig))
+* Fedor Indutny ([indutny](https://github.com/indutny))
+* James M Snell ([jasnell](https://github.com/jasnell))
+* Jeremiah Senkpiel ([Fishrock123](https://github.com/Fishrock123))
+* Julien Gilli ([misterdjules](https://github.com/misterdjules))
+* Michael Dawson ([mhdawson](https://github.com/mhdawson))
+* Rod Vagg ([rvagg](https://github.com/rvagg))
+* Shigeki Ohtsu ([shigeki](https://github.com/shigeki))
+* Steven R Loomis ([srl295](https://github.com/srl295))
+* Trevor Norris ([trevnorris](https://github.com/trevnorris))
diff --git a/locale/uk/about/releases.md b/locale/uk/about/releases.md
new file mode 100755
index 0000000000000..84409b7bc5576
--- /dev/null
+++ b/locale/uk/about/releases.md
@@ -0,0 +1,81 @@
+---
+layout: about.hbs
+title: Релізи
+---
+# Релізи
+
+Основна команда визначила дорожню карту, з якою знайома спільнота Node.js.
+Релізи відбуваються так часто, наскільки це необхідно і практично, проте не
+раніше, ніж роботу буде закінчено.
+Багів не уникнути, проте випуск релізів переважати преред впевненістю щодо коректної роботи програмного забезпечення. Високі стандарти якості є одним з
+ключових пріоритетів проекту Node.js.
+
+## Патчі
+
+Патч–релізи:
+
+- включають виправлення багів, покращення безпеки та швидкодії;
+- не додають і не змінюють публічних інтерфейсів;
+- не змінюють очікуваної поведінки даного інтерфейсу;
+- можуть виправляти поведінку, якщо вона не вказана в документації;
+- не вносять зміни, які унеможливлюють безшовні оновлення.
+
+## Мінори
+
+Мінорні релізи:
+
+- включають доповнення, або розширення API та підсистем;
+- загалом не змінюють API і не вводять зміни, що ламають зворотну сумісність, окрім тих, які неможливо уникнути;
+- є, здебільшого, доповнюючими релізами.
+
+## Мажори
+
+Мажорні релізи:
+
+- зазвичай вводять зміни, що ламають зворотну сумісність;
+- визначають API Node.js для підтримки у найближчому майбутньому;
+- вимагають обговорень, обережності, співправці між командою та користувачами.
+
+## Оцінка функціональності
+
+Команда може додавати новий функціонал та APІ у Node.js якщо:
+
+- зрозумілі потреби;
+- API або функціонал має відомих споживачів;
+- API є чистим, корисним та зручним для використання.
+
+При реалізації функціональних можливостей ядра Node.js, команда або спільнота
+може визначити інший API нижчого рівня, які могли б бути корисні поза Node.js.
+Після визначення Node.js може виставити його для споживачів.
+
+Наприклад, розглянемо інтерфейс [`EventEmitter`]. Потреба мати модель для підписки на події у модулях ядра є зрозумілою і ця абстракція може використовуватись поза ядром Node.js. Це не той випадок, коли інтерфейс не може бути реалізований поза Node.js, навпаки Node.js потребує цієї абстракції для себе і відкриває її для користувачів Node.js.
+
+Окрім того, може бути таке, що частина спільноти прийме шаблон
+для обробки деяких загальних потреб, який не задовільнятиме Node.js.
+Зрозуміло, що Node.js має за замовчуванням постачати API
+та функціонал для всіх користувачів Node.js.
+Інший можливий випадок полягає у додаткових скомпільованих розширеннях,
+які важко поширювати на різних оточеннях. З огляду на це,
+Node.js може включати ці зміни безпосередньо.
+
+Основна команда не приймає легковажно рішення стосовно внесення
+нового API у  Node.js. Node.js надає зворотній сумісності високого пріоритету.
+Таким чином, спільнота має прийняти та обговорити зміни перед тим,
+як команда прийматиме ці зміни. Навіть якщо API добре підходить змінам,
+команда мусить визначити потенційних споживачів.
+
+## Визначення застарілості
+
+У деяких випадках команда мусить визнати деякий функціонал та API
+в Node.js застарілими. Перед прийняттям будь–якого остаточного рішення,
+команда мусить визначити користувачів API і те,
+як вони його використовують. Ось деякі запитання до них:
+
+- Якщо це API широко використовується спільнотою, чому ми маємо визначати його застарілим?
+- Чи маємо ми API для заміни, чи зрозумілим є шлях переходу?
+- Як довго API має залишатись застарілим перед видаленням?
+- Чи існує якийсь зовнішній модуль, яким можна легко його замінити?
+
+Команда має проявляти таку ж обережність при визначенні APІ застарілим, як і при додаванні нового APІ в Node.js API.
+
+[`EventEmitter`]: https://nodejs.org/api/events.html#events_class_eventemitter
diff --git a/locale/uk/about/resources.md b/locale/uk/about/resources.md
new file mode 100755
index 0000000000000..cf9ab934992b8
--- /dev/null
+++ b/locale/uk/about/resources.md
@@ -0,0 +1,37 @@
+---
+layout: about.hbs
+title: Лого та графіка
+---
+# Ресурси
+
+## Завантаження лого
+
+Будь ласка, прочитайте [політику товарного знаку](/about/trademark/) щодо дозволеного використання логотипів та позначень Node.js®.
+
+Правила візуального оформлення позначень Node.js описані у
+[Visual Guidelines](/static/documents/foundation-visual-guidelines.pdf).
+
+<table border="0" cellspacing="0" cellpadding="10" class="logos">
+  <tr>
+    <td bgcolor="#FFFFFF">[![Node.js на світлому фоні](/static/images/logos/nodejs-new-pantone-black.png)](/static/images/logos/nodejs-new-pantone-black.ai)</td>
+    <td bgcolor="#333333">[![Node.js на темному фоні](/static/images/logos/nodejs-new-pantone-white.png)](/static/images/logos/nodejs-new-pantone-white.ai)</td>
+  </tr>
+  <tr>
+    <td>[Node.js звичайний AI](/static/images/logos/nodejs-new-pantone-black.ai)</td>
+    <td>[Node.js інвертований AI](/static/images/logos/nodejs-new-pantone-white.ai)</td>
+  </tr>
+  <tr>
+    <td bgcolor="#FFFFFF">[![Node.js на світлому фоні](/static/images/logos/nodejs-new-black.png)](/static/images/logos/nodejs-new-black.ai)</td>
+    <td bgcolor="#333333">[![Node.js на темному фоні](/static/images/logos/nodejs-new-white.png)](/static/images/logos/nodejs-new-white.ai)</td>
+  </tr>
+  <tr>
+    <td>[Node.js звичайний з меншою кількістю кольорів AI](/static/images/logos/nodejs-new-black.ai)</td>
+    <td>[Node.js інвертований з меншою кількістю кольорів AI](/static/images/logos/nodejs-new-white.ai)</td>
+  </tr>
+</table>
+
+## Фони для робочого столу
+
+![Screensavers](/static/images/logos/monitor.png)
+
+Оберіть розширення вашого екрану: <span class="desktops">[1024 x 768](/static/images/logos/nodejs-1024x768.png)  | [1280 x 1024](/static/images/logos/nodejs-1280x1024.png) | [1440 x 900](/static/images/logos/nodejs-1440x900.png) | [1920 x 1200](/static/images/logos/nodejs-1920x1200.png) | [2560 x 1440](/static/images/logos/nodejs-2560x1440.png)</span>
diff --git a/locale/uk/about/trademark.md b/locale/uk/about/trademark.md
new file mode 100755
index 0000000000000..169eb0c0cb4a5
--- /dev/null
+++ b/locale/uk/about/trademark.md
@@ -0,0 +1,28 @@
+---
+layout: about.hbs
+title: Політика торгової марки
+---
+# Політика торгової марки
+
+The Node.js trademarks, service marks, and graphics marks are symbols of the
+quality, performance, and ease of use that people have come to associate with
+the Node.js software and project. To ensure that the Node.js marks continue to
+symbolize these qualities, we must ensure that the marks are only used in ways
+that do not mislead people or cause them to confuse Node.js with other software
+of lower quality. If we don’t ensure the marks are used in this way, it cannot
+only confuse users, it can make it impossible to use the mark to protect
+against people who maliciously exploit the mark in the future. The primary goal
+of this policy is to make sure that this doesn’t happen to the Node.js mark, so
+that the community and users of Node.js are always protected in the future.
+
+At the same time, we’d like community members to feel comfortable spreading the
+word about Node.js and participating in the Node.js community. Keeping that
+goal in mind, we’ve tried to make the policy as flexible and easy to understand
+as legally possible.
+
+Please read the [full policy](/static/documents/trademark-policy.pdf).
+If you have any questions don't hesistate to
+[email us](mailto:trademark@nodejs.org).
+
+Guidelines for the visual display of the Node.js mark are described in
+the [Visual Guidelines](/static/documents/foundation-visual-guidelines.pdf).
diff --git a/locale/uk/about/working-groups.md b/locale/uk/about/working-groups.md
new file mode 100755
index 0000000000000..4a8ef01523306
--- /dev/null
+++ b/locale/uk/about/working-groups.md
@@ -0,0 +1,341 @@
+---
+layout: about.hbs
+title: Робочі групи
+---
+# Working Groups
+
+There are 2 types of Working Groups:
+
+* [Top-Level Working Groups](#top-level-working-groups)
+* [Core Working Groups](#core-working-groups)
+
+## Top-Level Working Groups
+
+<!-- Information here should mostly mirror: https://github.com/nodejs/TSC/blob/master/WORKING_GROUPS.md -->
+
+Top-Level Working Groups are created by the
+[Technical Steering Committee (TSC)](https://github.com/nodejs/TSC#top-level-wgs-and-tlps).
+
+### Current Top-Level Working Groups
+
+* [Inclusivity](#inclusivity)
+
+#### [Inclusivity](https://github.com/nodejs/inclusivity)
+
+The Inclusivity Working Group seeks to increase inclusivity and diversity for
+the Node.js project:
+
+* Increasing inclusivity means making the Node.js project a safe and friendly
+place for people from diverse backgrounds.
+* Increasing diversity means actively onboarding people from diverse backgrounds
+to the Node.js project and maintaining their participation.
+
+Its responsibilites are:
+
+* Foster a welcoming environment that ensures participants are valued and can
+feel confident contributing or joining discussions, regardless of any [aspect of
+their identity](https://github.com/nodejs/inclusivity/#list-of-responsibilities).
+* Proactively seek and propose concrete steps the project can take to increase
+inclusivity.
+* Serve as a resource for the development and enforcement of workflows that
+protect community members and projects from harassment and abuse.
+* Acknowledge and celebrate existing diversity accomplishments within the project
+while seeking to build upon them.
+* Identify ways to measure diversity and inclusivity within the project and report
+them at regular intervals.
+
+# Core Working Groups
+
+<!-- Information here should mostly mirror: https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md -->
+
+Core Working Groups are created by the
+[Core Technical Committee (CTC)](https://github.com/nodejs/node/blob/master/GOVERNANCE.md#core-technical-committee).
+
+
+## Current Working Groups
+
+* [Website](#website)
+* [Streams](#streams)
+* [Build](#build)
+* [Tracing](#tracing)
+* [i18n](#i18n)
+* [Evangelism](#evangelism)
+* [Roadmap](#roadmap)
+* [Docker](#docker)
+* [Addon API](#addon-api)
+* [Benchmarking](#benchmarking)
+* [Post-mortem](#post-mortem)
+* [Intl](#intl)
+* [HTTP](#http)
+* [Documentation](#documentation)
+* [Testing](#testing)
+
+
+### [Website](https://github.com/nodejs/nodejs.org)
+
+The website working group's purpose is to build and maintain a public
+website for the `Node.js` project.
+
+Its responsibilities are:
+
+* Develop and maintain a build and automation system for `nodejs.org`.
+* Ensure the site is regularly updated with changes made to `Node.js` like
+releases and features.
+* Foster and enable a community of translators.
+
+### [Streams](https://github.com/nodejs/readable-stream)
+
+The Streams WG is dedicated to the support and improvement of the Streams API
+as used in Node.js and the npm ecosystem. We seek to create a composable API that
+solves the problem of representing multiple occurrences of an event over time
+in a humane, low-overhead fashion. Improvements to the API will be driven by
+the needs of the ecosystem; interoperability and backwards compatibility with
+other solutions and prior versions are paramount in importance. Our
+responsibilities include:
+
+* Addressing stream issues on the Node.js issue tracker.
+* Authoring and editing stream documentation within the Node.js project.
+* Reviewing changes to stream subclasses within the Node.js project.
+* Redirecting changes to streams from the Node.js project to this project.
+* Assisting in the implementation of stream providers within Node.js.
+* Recommending versions of readable-stream to be included in Node.js.
+* Messaging about the future of streams to give the community advance notice of changes.
+
+
+### [Build](https://github.com/nodejs/build)
+
+The build working group's purpose is to create and maintain a
+distributed automation infrastructure.
+
+Its responsibilities are:
+
+* Produce Packages for all target platforms.
+* Run tests.
+* Run performance testing and comparisons.
+* Creates and manages build-containers.
+
+
+### [Tracing](https://github.com/nodejs/tracing-wg)
+
+The tracing working group's purpose is to increase the
+transparency of software written in Node.js.
+
+Its responsibilities are:
+
+* Collaboration with V8 to integrate with `trace_event`.
+* Maintenance and iteration on AsyncWrap.
+* Maintenance and improvements to system tracing support (DTrace, LTTng, etc.)
+* Documentation of tracing and debugging techniques.
+* Fostering a tracing and debugging ecosystem.
+
+### i18n
+
+The i18n working groups handle more than just translations. They
+are endpoints for community members to collaborate with each
+other in their language of choice.
+
+Each team is organized around a common spoken language. Each
+language community might then produce multiple localizations for
+various project resources.
+
+Their responsibilities are:
+
+* Translations of any Node.js materials they believe are relevant to their
+community.
+* Review processes for keeping translations up
+to date and of high quality.
+* Social media channels in their language.
+* Promotion of Node.js speakers for meetups and conferences in their
+language.
+
+Note that the i18n working groups are distinct from the [Intl](#Intl) working group.
+
+Each language community maintains its own membership.
+
+* [nodejs-ar - Arabic (اللغة العربية)](https://github.com/nodejs/nodejs-ar)
+* [nodejs-bg - Bulgarian (български език)](https://github.com/nodejs/nodejs-bg)
+* [nodejs-bn - Bengali (বাংলা)](https://github.com/nodejs/nodejs-bn)
+* [nodejs-zh-CN - Chinese (中文)](https://github.com/nodejs/nodejs-zh-CN)
+* [nodejs-cs - Czech (Český Jazyk)](https://github.com/nodejs/nodejs-cs)
+* [nodejs-da - Danish (Dansk)](https://github.com/nodejs/nodejs-da)
+* [nodejs-de - German (Deutsch)](https://github.com/nodejs/nodejs-de)
+* [nodejs-el - Greek (Ελληνικά)](https://github.com/nodejs/nodejs-el)
+* [nodejs-es - Spanish (Español)](https://github.com/nodejs/nodejs-es)
+* [nodejs-fa - Persian (فارسی)](https://github.com/nodejs/nodejs-fa)
+* [nodejs-fi - Finnish (Suomi)](https://github.com/nodejs/nodejs-fi)
+* [nodejs-fr - French (Français)](https://github.com/nodejs/nodejs-fr)
+* [nodejs-he - Hebrew (עברית)](https://github.com/nodejs/nodejs-he)
+* [nodejs-hi - Hindi (फिजी बात)](https://github.com/nodejs/nodejs-hi)
+* [nodejs-hu - Hungarian (Magyar)](https://github.com/nodejs/nodejs-hu)
+* [nodejs-id - Indonesian (Bahasa Indonesia)](https://github.com/nodejs/nodejs-id)
+* [nodejs-it - Italian (Italiano)](https://github.com/nodejs/nodejs-it)
+* [nodejs-ja - Japanese (日本語)](https://github.com/nodejs/nodejs-ja)
+* [nodejs-ka - Georgian (ქართული)](https://github.com/nodejs/nodejs-ka)
+* [nodejs-ko - Korean (한국어)](https://github.com/nodejs/nodejs-ko)
+* [nodejs-mk - Macedonian (Mакедонски)](https://github.com/nodejs/nodejs-mk)
+* [nodejs-ms - Malay (بهاس ملايو)](https://github.com/nodejs/nodejs-ms)
+* [nodejs-nl - Dutch (Nederlands)](https://github.com/nodejs/nodejs-nl)
+* [nodejs-no - Norwegian (Norsk)](https://github.com/nodejs/nodejs-no)
+* [nodejs-pl - Polish (Język Polski)](https://github.com/nodejs/nodejs-pl)
+* [nodejs-pt - Portuguese (Português)](https://github.com/nodejs/nodejs-pt)
+* [nodejs-ro - Romanian (Română)](https://github.com/nodejs/nodejs-ro)
+* [nodejs-ru - Russian (Русский)](https://github.com/nodejs/nodejs-ru)
+* [nodejs-sv - Swedish (Svenska)](https://github.com/nodejs/nodejs-sv)
+* [nodejs-ta - Tamil (தமிழ்)](https://github.com/nodejs/nodejs-ta)
+* [nodejs-tr - Turkish (Türkçe)](https://github.com/nodejs/nodejs-tr)
+* [nodejs-zh-TW - Taiwanese (Hō-ló)](https://github.com/nodejs/nodejs-zh-TW)
+* [nodejs-uk - Ukrainian (Українська)](https://github.com/nodejs/nodejs-uk)
+* [nodejs-vi - Vietnamese (Tiếng Việtnam)](https://github.com/nodejs/nodejs-vi)
+
+### [Intl](https://github.com/nodejs/Intl)
+
+The Intl Working Group is dedicated to support and improvement of
+Internationalization (i18n) and Localization (l10n) in Node. Its responsibilities are:
+
+1. Functionality & compliance (standards: ECMA, Unicode…)
+2. Support for Globalization and Internationalization issues that come up in the tracker
+3. Guidance and Best Practices
+4. Refinement of existing `Intl` implementation
+
+The Intl WG is not responsible for translation of content. That is the responsibility of the specific [i18n](#i18n) group for each language.
+
+### [Evangelism](https://github.com/nodejs/evangelism)
+
+The evangelism working group promotes the accomplishments
+of Node.js and lets the community know how they can get involved.
+
+Their responsibilities are:
+
+* Project messaging.
+* Official project social media.
+* Promotion of speakers for meetups and conferences.
+* Promotion of community events.
+* Publishing regular update summaries and other promotional
+content.
+
+### [HTTP](https://github.com/nodejs/http)
+
+The HTTP working group is chartered for the support and improvement of the
+HTTP implementation in Node. It's responsibilities are:
+
+* Addressing HTTP issues on the Node.js issue tracker.
+* Authoring and editing HTTP documentation within the Node.js project.
+* Reviewing changes to HTTP functionality within the Node.js project.
+* Working with the ecosystem of HTTP related module developers to evolve the
+  HTTP implementation and APIs in core.
+* Advising the CTC on all HTTP related issues and discussions.
+* Messaging about the future of HTTP to give the community advance notice of
+  changes.
+
+### [Roadmap](https://github.com/nodejs/roadmap)
+
+The roadmap working group is responsible for user community outreach
+and the translation of their concerns into a plan of action for Node.js.
+
+The final [ROADMAP](https://github.com/nodejs/node/blob/master/ROADMAP.md) document is still
+owned by the TC and requires the same approval for changes as any other project asset.
+
+Their responsibilities are:
+
+* Attract and summarize user community needs and feedback.
+* Find or potentially create tools that allow for broader participation.
+* Create Pull Requests for relevant changes to
+[ROADMAP.md](https://github.com/nodejs/node/blob/master/ROADMAP.md)
+
+
+### [Docker](https://github.com/nodejs/docker-node)
+
+The Docker working group's purpose is to build, maintain, and improve official
+Docker images for the `Node.js` project.
+
+Their responsibilities are:
+
+* Keep the official Docker images updated in line with new `Node.js` releases.
+* Decide and implement image improvements and/or fixes.
+* Maintain and improve the images' documentation.
+
+
+### [Addon API](https://github.com/nodejs/nan)
+
+The Addon API Working Group is responsible for maintaining the NAN project and
+corresponding _nan_ package in npm. The NAN project makes available an
+abstraction layer for native add-on authors for both Node.js and Node.js,
+assisting in the writing of code that is compatible with many actively used
+versions of Node.js, Node.js, V8 and libuv.
+
+Their responsibilities are:
+
+* Maintaining the [NAN](https://github.com/nodejs/nan) GitHub repository,
+  including code, issues and documentation.
+* Maintaining the [addon-examples](https://github.com/nodejs/node-addon-examples)
+  GitHub repository, including code, issues and documentation.
+* Maintaining the C++ Addon API within the Node.js project, in subordination to
+  the Node.js CTC.
+* Maintaining the Addon documentation within the Node.js project, in
+  subordination to the Node.js CTC.
+* Maintaining the _nan_ package in npm, releasing new versions as appropriate.
+* Messaging about the future of the Node.js and NAN interface to give the
+  community advance notice of changes.
+
+The current members can be found in their
+[README](https://github.com/nodejs/nan#collaborators).
+
+### [Benchmarking](https://github.com/nodejs/benchmarking)
+
+The purpose of the Benchmark working group is to gain consensus
+for an agreed set of benchmarks that can be used to:
+
++ track and evangelize performance gains made between Node releases
++ avoid performance regressions between releases
+
+Its responsibilities are:
+
++ Identify 1 or more benchmarks that reflect customer usage.
+   Likely need more than one to cover typical Node use cases
+   including low-latency and high concurrency
++ Work to get community consensus on the list chosen
++ Add regular execution of chosen benchmarks to Node builds
++ Track/publicize performance between builds/releases
+
+### [Post-mortem](https://github.com/nodejs/post-mortem)
+
+The Post-mortem Diagnostics working group is dedicated to the support
+and improvement of postmortem debugging for Node.js. It seeks to
+elevate the role of postmortem debugging for Node, to assist in the
+development of techniques and tools, and to make techniques and tools
+known and available to Node.js users.
+
+Its responsibilities are:
+
++ Defining and adding interfaces/APIs in order to allow dumps
+  to be generated when needed
++ Defining and adding common structures to the dumps generated
+  in order to support tools that want to introspect those dumps
+
+### [Documentation](https://github.com/nodejs/docs)
+
+The Documentation working group exists to support the improvement of Node.js
+documentation, both in the core API documentation, and elsewhere, such as the
+Node.js website. Its intent is to work closely with Evangelism, Website, and
+Intl working groups to make excellent documentation available and accessible
+to all.
+
+Its responsibilities are:
+
+* Defining and maintaining documentation style and content standards.
+* Producing documentation in a format acceptable for the Website WG to consume.
+* Ensuring that Node's documentation addresses a wide variety of audiences.
+* Creating and operating a process for documentation review that produces
+  quality documentation and avoids impeding the progress of Core work.
+
+### [Testing](https://github.com/nodejs/testing)
+
+The Node.js Testing Working Group's purpose is to extend and improve testing of
+the Node.js source code.
+
+It's responsibilities are:
+
+* Coordinating an overall strategy for improving testing.
+* Documenting guidelines around tests.
+* Working with the Build Working Group to improve continuous integration.
+* Improving tooling for testing.
diff --git a/locale/uk/blog/advisory-board/advisory-board-update.md b/locale/uk/blog/advisory-board/advisory-board-update.md
new file mode 100755
index 0000000000000..16e4f9de83c8e
--- /dev/null
+++ b/locale/uk/blog/advisory-board/advisory-board-update.md
@@ -0,0 +1,108 @@
+---
+title: Advisory Board Update
+date: 2014-12-03T18:00:00.000Z
+author: Timothy J Fontaine
+slug: advisory-board-update
+layout: blog-post.hbs
+---
+
+A lot has been happening in Node.js, so I wanted bring everyone up to date on
+where we are with regards to the advisory board, its working groups, and the
+release of v0.12.
+
+The interim [advisory
+board](https://www.joyent.com/blog/node-js-advisory-board) has met three times
+since its creation. You can find the minutes from the advisory board meetings
+here: [https://nodejs.org/en/about/advisory-board/](https://nodejs.org/en/about/advisory-board/). As
+we have more meetings and minutes, we will announce the dates and times for
+those meeting and their minutes here on the blog. The next meeting is this
+Thursday December 4th, at 1:30PM PST. We're looking to collect as much feedback
+and input from as many representatives of the community as we can, so it's
+important that we keep everyone up to date as much as possible.
+
+The interim advisory board has been working through a series of topics (in
+general meetings as well as working groups) to further hone the scope of the
+board, as well as define the structure that the advisory board will use to
+conduct its meetings. Everyone on the board wants to make sure we're being as
+transparent as possible, so let me describe how things operate so far. The
+board is using a traditional two conference call structure, a public portion
+that is recorded and open for anyone to join, and a private portion that is
+only for board members.
+
+The public portion is meant to provide an update of what happened in the
+previous meeting, as well as the status of action items from the previous
+meeting. At the end of each public session is a open comment section, where
+listeners are able to ask questions and the advisory board can respond.
+
+Following the public portion the board dials into the private conference,
+further discussion happens during this time around specific agenda items,
+working groups providing updates, and facilitating conversations about those
+topics. These conversations are open and frank, and their content is recorded
+in the minutes. Those minutes are then published a few days after the meeting
+in the GitHub repository
+[https://github.com/joyent/nodejs-advisory-board](https://github.com/joyent/nodejs-advisory-board),
+as well as on the website
+[https://nodejs.org/en/about/advisory-board/](https://nodejs.org/en/about/advisory-board/).
+
+There are a few working groups so far, for instance one is focused on making
+sure the membership of the board is representative of the community Node.js
+serves. While the board was initially bootstrapped with its existing
+membership, we want to quickly move to a model that fully represents our
+community. We want the board to represent the broadest spectrum of our
+community, that also enables the board to move swiftly and make progress.
+
+Another working group is having a conversation about governance. This includes
+topics like what is the team that makes decisions for Node.js, how do you
+become a member of that team, how does that team set the roadmap for the
+project, and how does that team makes decisions.
+
+One thing that we all agree on, is that we're not going to be using the
+Benevolent Dictator model. In fact, recently the project hasn't been operating
+that way. We can be more clear about that in our
+[documentation](https://nodejs.org/en/about/organization). We all agree we want
+a healthy and vibrant team, a team focused on making progress for Node.js, not
+for progress's sake, but for the betterment of the software project and the
+community we serve. We also agree that this means that there should be
+consensus among the team. The conversation has been fruitful, and is on going,
+we're continuing to work through the finer points of how much consensus we
+need.
+
+I want to take a moment to describe what consensus means in this context. The
+consensus model is about accountability. Accountability for the changes being
+integrated into the project, accountability for documentation, and
+accountability for releases. While members of the team are responsible for
+subsystems or features of Node.js, everyone reviews each others changes. They
+make sure to understand the impact on their relevant responsibilities.
+
+The goal of the team, especially that of the project lead, is to drive
+consensus and ensure accountability. This means asking critical questions and
+being able to answer them specifically and succinctly, for example:
+
+ * What are we trying to solve with this change?
+ * Does this change effectively solve for this problem?
+ * Does this API have a consumer?
+ * Does this API reach the broadest amount of use cases?
+ * Is this API supportable?
+ * Does this change have adverse effects on other subsystems or use cases (and is that acceptable)?
+ * Does this change have tests that verify its operation, now and in the future?
+ * Does this change pass our style guidelines?
+ * Does this change pass our integration tests for the matrix of our supported configurations?
+   - For instance: ia32 and x64 for Windows, Linux, OSX, SmartOS
+
+These are just some of the questions, and while the questions are not unusual
+or unique to Node.js, they are still important.
+
+Finally, we are very close to releasing v0.12, there's only one major patch
+we're waiting to land. Once that's done we'll be releasing v0.11.15 as a
+release candidate. Assuming no severe issues are filed against v0.11.15 we will
+be going live with v0.12 about two weeks after the v0.11.15 release.
+
+If you have questions for the advisory board you can email
+[advisoryboard@nodejs.org](mailto:advisoryboard@nodejs.org) or file an issue on
+its repository
+[https://github.com/joyent/nodejs-advisory-board](https://github.com/joyent/nodejs-advisory-board).
+Thanks for all of your continued contributions to Node.js, in the form of
+[filing issues](https://github.com/joyent/node/issues), [submitting pull
+requests](https://github.com/joyent/node/pulls), and publishing your modules.
+Node.js is lucky to have such an enthusiastic and engaged community, and we're
+excited to be working with you on the future of Node.js.
diff --git a/locale/uk/blog/advisory-board/index.md b/locale/uk/blog/advisory-board/index.md
new file mode 100755
index 0000000000000..40847a7869637
--- /dev/null
+++ b/locale/uk/blog/advisory-board/index.md
@@ -0,0 +1,6 @@
+---
+title: Advisory Board
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/advisory-board/listening-to-the-community.md b/locale/uk/blog/advisory-board/listening-to-the-community.md
new file mode 100755
index 0000000000000..a56801cdcac7d
--- /dev/null
+++ b/locale/uk/blog/advisory-board/listening-to-the-community.md
@@ -0,0 +1,22 @@
+---
+title: Listening to the Community
+date: 2014-12-05T21:30:00.000Z
+author: Advisory Board
+slug: listening-to-the-community
+layout: blog-post.hbs
+---
+
+We assembled the Node.js Advisory Board (AB) to listen to the community and
+make the necessary changes to have a unified direction for Node.js, a
+passionate group of developers, a vibrant ecosystem of product and service
+providers, and a satisfied user base.  Over the last month we have made great
+progress on an open governance model, API standards, IP management, and
+transparency to ensure the project is community-driven.  These efforts
+explicitly target helping resolve conflicts and with the goal of moving the
+community forward together.  It is important that we understand voices of
+dissent and frustration and work together to build the greater ecosystem.  We
+are committed to this goal.
+
+Node.js remains the trusted platform that users rely on for creative projects
+and to drive business goals.  The v0.12 release will ship shortly and the
+project team is already engaged in discussions about the next release.
diff --git a/locale/uk/blog/announcements/apigee-rising-stack-yahoo.md b/locale/uk/blog/announcements/apigee-rising-stack-yahoo.md
new file mode 100755
index 0000000000000..6a3b421fc00f0
--- /dev/null
+++ b/locale/uk/blog/announcements/apigee-rising-stack-yahoo.md
@@ -0,0 +1,38 @@
+---
+title: Apigee, RisingStack and Yahoo Join the Node.js Foundation
+date: 2015-12-08T12:00:00.000Z
+status: publish
+category: Annoucements
+slug: apigee-rising-stack-yahoo
+layout: blog-post.hbs
+---
+
+> New Silver Members to Advance Node.js Growth and Enterprise Adoption
+
+**NODE.JS INTERACTIVE 2015, PORTLAND, OR.** — [The Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced Apigee, RisingStack and Yahoo are joining the Foundation as Silver Members to build and support the Node.js platform. With over 2 million downloads per month, Node.js is the runtime of choice for developers building everything from enterprise applications to Industrial IoT.
+
+The Node.js Foundation members work together alongside the community to help grow this diverse technology for large financial services, web-scale, cloud computing companies, and more. The newly added [Long-Term Support](https://nodejs.org/en/blog/release/v4.2.0/) release version 4.0 is just one of the many initiatives from the Foundation, which addresses the needs of enterprises that are using Node.js in more complex production environments, and signals the growing maturity of the technology.
+
+“We continue to welcome new Node.js Foundation members that are committed to providing the financial and technical resources needed to ensure the technology continues to evolve, while nurturing the community and ecosystem at the same time,” said Danese Cooper, Chairperson of the Node.js Foundation Board. “We are excited to have Apigee, RisingStack, and Yahoo on board to help grow the diversity of the platform and the community.”
+
+The new members are joining just in time for the inaugural Node.js Interactive event taking place today and tomorrow in Portland, OR. The conference focuses on frontend, backend and IoT technologies, and the next big initiatives for the Node.js Foundation. It includes more than 50 tutorials, sessions and keynotes. To stream the event, go to [http://events.linuxfoundation.org/events/node-interactive/program/live-video-stream](http://events.linuxfoundation.org/events/node-interactive/program/live-video-stream).
+
+More information about the newest Node.js Foundation members:
+
+[Apigee](https://apigee.com/about/) provides an intelligent API platform for digital businesses. Headquartered in San Jose, California, Apigee’s software supports some of the largest global enterprises. Developers can use the Node.js software platform to build highly customized application programming interfaces (APIs) and apps in the [Apigee API management platform](http://apigee.com/about/products/api-management). The integration of the Node.js technology allows developers to use code to create specialized APIs in Apigee, while utilizing the huge community of JavaScript developers.
+
+“We want to provide to the developer community the best platform for building today’s modern apps and APIs,,” said Ed Anuff, executive vice president of strategy at Apigee. “We are committed to the advancement of Node.js and look forward to continuing to utilize the strengths and further possibilities of the technology. The Node.js Foundation provides an excellent place for us to help push this technology to become even better for our developers that use it everyday.”
+
+[RisingStack](https://risingstack.com/) was founded in 2014 by Gergely Nemeth and Peter Marton as a full stack Javascript consulting company. It provides help with digital transitioning to Node.js and offers a microservice monitoring tool called [Trace](http://trace.risingstack.com/). RisingStack also contributes to several open source projects, and engages the developer community via a popular JavaScript/DevOps [engineering blog](https://blog.risingstack.com/), with a tremendous amount of long reads.
+
+“Node.js is extremely important in Javascript development, and we have experienced a rapid rise of interest in the technology from enterprises.” said Gergely Nemeth, CEO and Co-Founder of RisingStack. “Our business was established to support this growing technology, and we are very excited to join the Node.js Foundation to help broaden this already active community and continue its growth through open governance.”
+
+Yahoo is a guide focused on informing, connecting and entertaining its users. By creating highly personalized experiences for its users, Yahoo keeps people connected to what matters most to them, across devices and around the world. In turn, Yahoo creates value for advertisers by connecting them with the audiences that build their businesses.
+
+“Joining the Node.js Foundation underscores our deep appreciation for the Node.js community, and our commitment to drive its health and growth,” said Preeti Somal, vice president of engineering, Yahoo. “As a technology pioneer with a deep legacy of Javascript expertise and a strong commitment to open source, we saw the promise of Node.js from the start and have since scaled to become one of the industry’s largest deployments. We embrace Node.js’s evolution and encourage our developers to be contributing citizens of the Open Source community.”
+
+Additional Resources
+* Learn more about the [Node.js Foundation](https://nodejs.org/en/foundation/) and get involved with [the project](https://nodejs.org/en/get-involved/).
+
+About Node.js Foundation
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), YLD!, and Yahoo. Get involved here: [http://nodejs.org](https://nodejs.org/en/).
diff --git a/locale/uk/blog/announcements/appdynamics-newrelic-opbeat-sphinx.md b/locale/uk/blog/announcements/appdynamics-newrelic-opbeat-sphinx.md
new file mode 100755
index 0000000000000..e6a4321c43ae6
--- /dev/null
+++ b/locale/uk/blog/announcements/appdynamics-newrelic-opbeat-sphinx.md
@@ -0,0 +1,44 @@
+---
+title: AppDynamics, New Relic, Opbeat and Sphinx Join the Node.js Foundation as Silver Members
+date: 2016-03-09T21:00:00.000Z
+category: Annoucements
+slug: appdynamics-newrelice-opbeat-sphinx
+layout: blog-post.hbs
+---
+
+> Foundation Announces Dates for Node.js Interactive Conferences in Amsterdam and Austin, Texas 
+
+SAN FRANCISCO, Mar. 9, 2016 — The [Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced AppDynamics, New Relic, Opbeat and Sphinx are joining the Foundation as Silver Members to continue to sustain and grow the Node.js platform.
+
+Many of the new members are within the application performance management industry, both established and up-and-coming vendors. Application performance management is an essential part of any infrastructure and there is a need across public, private and hybrid clouds to ensure that current and future products offer next-generation application performance with Node.js as a core component to the stability and potential of these offerings.
+
+The new members have the opportunity to support a range of Foundation activities such as new training programs and user-focused events like the new, ongoing [Node.js Live](http://live.nodejs.org/) series and Node.js Interactive events. Expanding to Europe this year, Node.js Interactive will take place September 15-16 in Amsterdam, Netherlands; while the North America event will be held November 29-30, 2016, in Austin, Texas. More information on the conference to come.
+
+Node.js has grown tremendously in the last year with a total of [3.5 million](https://www.npmjs.com/) users and 100 percent year-over-year growth. It is becoming ubiquitous across numerous industries from financial services to media companies, and is heavily used by frontend, backend and IoT developers. 
+
+“While the popularity of Node.js has dramatically increased in recent years, the Foundation is committed to maintaining a stable, neutral and transparent ground to support continuation of the technology’s growth,” said Danese Cooper, Chairperson of the Node.js Foundation Board. “We are pleased to have AppDynamics, New Relic, Opbeat and Sphinx join the Foundation to help support both continued expansion for the technology and stability needs of the community.”
+
+More About the New Members:
+
+[AppDynamics](http://www.appdynamics.com/) is the application intelligence company that provides real-time insights into application performance, user experience, and business outcomes with cloud, on-premises, and hybrid deployment flexibility. Seeing the growing popularity of Node.js as a platform for building fast and scalable web and mobile applications, AppDynamics created a Node.js monitoring solution built on their core APM platform. The solution helps customers monitor Node.js applications in real-time and diagnose performance bottlenecks while running in live production or development environments.
+ 
+“Node.js is clearly taking off, and we’ve seen significant adoption of the platform in production for quite some time now, especially within the enterprise. We have participated in multiple Node.js events in the past, and look forward to continuing to support the longevity of this project, which is important to the developers that we serve,” said AppDynamics Chief Technology Officer and Senior Vice President of Product Management, Bhaskar Sunkara.
+
+[New Relic](https://newrelic.com/) is a software analytics company that delivers real-time insights and helps companies securely monitor their production software in virtually any environment, without having to build or maintain dedicated infrastructure. New Relic’s agent helps pinpoint Node.js application performance issues across private, public or hybrid cloud environments.
+
+“We're seeing huge growth in our Node.js application counts on a daily basis, from customers of all sizes - there's just as much interest from the Fortune 100 as there is from new startups. New Relic's engineers have been contributing to Node.js's core development for years, and we're excited to help accelerate its advancement and success even further by supporting the Node.js Foundation," said Tim Krajcar, Engineering Manager, Node.js Agent, New Relic.
+
+[Opbeat](https://opbeat.com/) provides next-generation performance insights, specifically built for JavaScript developers. Opbeat maps production issues to the developers that write the code, leading to faster debugging and more coding. The young company recently launched [full support for Node.js](https://opbeat.com/nodejs/).
+
+“We’re seeing massive interest in Opbeat within the Node community - from larger organizations to smaller start-ups - so we’re excited to join the Foundation to help support the community. At the end of the day, our customers are developers and we want to contribute to the increased popularity of Node amongst developers and CTOs,” said Rasmus Makwarth, Co-Founder and CEO of Opbeat.
+
+[Sphinx](http://sphinx.sg/) was established in 2014 by experience Vietnamese developers from Silicon Valley with the aim to become the leading company on Node.js and the MEAN stack — the group has co-founded the Vietnamese Node.js and Angular.js communities. The consulting team helps take large-scale applications from the concept phase to production for some of the largest global enterprises and government departments. 
+
+“Becoming a silver member is a breakthrough for us, and gives us the opportunity to establish long-lasting relationships with companies that also share a common interest in the rapidly growing Node.js technology. We look forward to collaborating with other Foundation members and continuing to develop and support the open source community,” said Hai Luong, CEO and Co-Founder of Sphinx.
+
+About Node.js Foundation
+Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 3.5 million active users per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, AppDynamics, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, New Relic, npm, Opbeat, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), Sphinx, YLD!, and Yahoo!. Get involved here: [http://nodejs.org](http://nodejs.org/).
+
+The Node.js Foundation is a Linux Foundation Project, which are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [www.linuxfoundation.org](http://www.linuxfoundation.org/)
diff --git a/locale/uk/blog/announcements/foundation-advances-growth.md b/locale/uk/blog/announcements/foundation-advances-growth.md
new file mode 100755
index 0000000000000..4c11558e5c7a8
--- /dev/null
+++ b/locale/uk/blog/announcements/foundation-advances-growth.md
@@ -0,0 +1,53 @@
+---
+title: Node.js Foundation Advances Platform with More Than Three Million Users
+date: 2015-12-08T12:00:00.000Z
+status: publish
+category: Annoucements
+slug: foundation-advances-growth
+layout: blog-post.hbs
+---
+
+> Node.js Platform Stronger Than Ever with New Node.js Foundation Members, 
+Community Contributions, and 100 Percent Year-Over-Year User Growth 
+
+**NODE.JS INTERACTIVE 2015, PORTLAND, OR.** — [The Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today is announcing major community, code and membership growth, adoption statistics of the technology at large, and the Foundation’s new incubation program. 
+
+The Node.js Foundation was founded in 2015 to accelerate the development of Node.js and support the large ecosystem that it encompasses through open governance. As part of this mission, the Foundation announced its first incubation project libuv. Libuv is a software library that provides asynchronous event notification and improves the Node.js programming experience. The project is both critical to Node.js and already widely used, making it a natural fit for the Foundation. Under the Foundation's umbrella, it will receive additional support and mentorship. 
+
+The first Node.js Interactive event unites more than 700 developers, engineers, system architects, DevOps professionals and users representing a wide range of projects, products and companies in Portland, Ore. Node.js Interactive brings together a broad range of speakers to help experienced and novice Node.js users alike learn tips, best practices, new skills, as well as gain insight into future developments for the technology. With Node.js being used in 98% of the Fortune 500 companies regularly, the event will also highlight the maturation of the technology within enterprises. 
+
+Attendees have the opportunity to see and learn more about how organizations like Capital One, GoDaddy, Intel, NodeSource, npm and Uber are using Node.js to meet their innovation needs. Attendees are also getting a first look at Node.js advancements announced and demoed this week including:
+
+* JOYENT: Joyent is announcing the 2016 Node.js Innovation Program, which provides Node.js expertise, marketing support and free cloud or on-premise infrastructure to start-ups and teams within larger enterprises that are driving innovation powered by Node.js. The 2015 program included [bitHound](https://www.bithound.io/), who will speak at Node.js Interactive about innovative approaches to identifying risk and priorities in dependencies and code.  More info can be found [here](https://www.joyent.com/innovation). 
+<br><br>Joyent also released a new Node.js, Docker and NoSQL reference [architecture](https://www.joyent.com/blog/how-to-dockerize-a-complete-application) that enables microservices in seconds. To learn more, the company will be demoing this at booth number 7.
+
+* IBM is featuring multiple Node.js based solutions for: a complete API lifecycle via StrongLoop Arc and Loopback.io; real-time location tracking in Node using Cloudant®  data services; how to write Node applications against Apache Spark; and end-to-end mobile applications using IBM MobileFirst -- all running on Bluemix®, IBM's Cloud Platform. 
+
+* INTEL: A leader in the Internet of Things, Intel will be demoing a SmartHouse at booth number 0013. Based on the [IoTivity](https://www.iotivity.org/) open source project, which is sponsored by the [Open Interconnect Consortium (OIC)](http://openinterconnect.org/), the SmartHouse includes a home gateway from MinnowBoard Max client, three Edison controlled LEDs, fan, motion sensor, and smoke detector. Intel developed Node.js binding for IoTivity to power the demo with everything being controlled from a WebGL 3D virtual house interface.
+
+* NEARFORM: nearForm is holding a Node Expert Clinic for attendees who are looking for advice on Node.js adoption or struggling with any existing problems. Individuals will be connected to experts including Matteo Collina, Colin Ihrig, Wyatt Preul and Peter Elger for 30 minute sessions which can be arranged at the conference.
+<br><br>In addition, the company is sharing real customer successes and adoption statistics of Node.js at large. The company gathered the data from 100 of their Node customers across the globe. The leading industries in implementation and adoption of Node.js include enterprise software companies and media companies. Financial, payment, travel, e-commerce and IoT tie for third in industries that are leading in both adoption and implementation. 
+<br><br>Startups are leading the way in adding Node.js into their strategy, but in 2013 and 2014 larger incumbents started to transition their stacks with Node.js as a core technology, notable names include PayPal, Condé Nast, and Costa. In terms of startup saturation: 
+
+ * 25% of developers at growth-stage companies in enterprise software are using Node.js; 
+ * 25% of developers at FinTech startups are using Node.js; 
+ * Healthcare startups are using Node.js in a significant way - an average of 33% of developers are using Node.js with the primary    use-case to enable rapid-innovation;
+ * 48% of developers are using Node.js at IoT companies;
+ * 80% of developers at education startups are using the technology.
+
+* NODESOURCE: The company will showcase [N|Solid](https://nodesource.com/products/nsolid) for Enterprise-grade Node.js platform. It extends the capability of Node.js to provide increased developer productivity, protection of critical applications, and peak application performance. 
+<br><br>The company will also have [free upgrade tools](https://marketing.nodesource.com/acton/fs/blocks/showLandingPage/a/15680/p/p-001f/t/page/fm/4) available to help developers implement the latest Long Term Support version, v4. This version is essential for enterprises and companies using Node.js in more complex environments as it is the most stable and highly security code from the platform. 
+
+* SYNCHRO LABS: Silver Node.js Interactive sponsor Synchro Labs announced the launch of Synchro platform, a new tool that allows enterprise developers to create high quality, high performance, cross-platform native mobile applications using the Node.js framework. The company is demoing the new platform at the conference booth 2. More information on the recent announcement [here](https://synchro.io/launch).
+
+### Community and Code Growth 
+Since the independent Node.js Foundation launched earlier this year, development progress continues to accelerate with dramatic increases in contributions to the project. In the past eight months, the community has grown from 8 to more than 400 contributors, with first-time contributors as high as 63 percent per month. There are more than 3 million active users of Node.js, which has increased 100% year over year.
+
+Currently the core Node.js repository includes 52 committers, while there’s been more than 709 contributors over time. Node.js core had 77 active contributors in October alone, with 46 of those being first-time contributors. More than 400 developers have commit rights to some part of the Node.js project currently. The community is focused on creating a new type of open source contribution philosophy called participatory governance, which liberalizes contribution policies and provides direct ownership to contributors. 
+
+In addition, the Foundation announced three new Silver members to the team, Apigee, RisingStack, and Yahoo. You can find details of the new membership here. 
+
+#### About Node.js Foundation
+
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), YLD!, and Yahoo!. Get involved here: [http://nodejs.org](http://nodejs.org).
+
diff --git a/locale/uk/blog/announcements/foundation-elects-board.md b/locale/uk/blog/announcements/foundation-elects-board.md
new file mode 100755
index 0000000000000..974b432caf16d
--- /dev/null
+++ b/locale/uk/blog/announcements/foundation-elects-board.md
@@ -0,0 +1,38 @@
+---
+title: Node.js Foundation Elects Board of Directors
+date: 2015-09-04T21:00:00.000Z
+status: publish
+category: Annoucements
+slug: foundation-elects-board
+layout: blog-post.hbs
+---
+
+> New Foundation Committed to Accelerating Growth of the Node.js Platform Also Adds Marketing Chair and Community Manager
+
+SAN FRANCISCO, Sept. 4, 2015 – The [Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced key executives have been elected to its Board of Directors. The Board of Directors represents the broad Node.js community and will guide the Foundation as it executes on its mission to enable widespread adoption and help accelerate development of Node.js and other related modules.
+
+The Node.js Foundation board, which sets the business and technical direction as well as oversees IP management, marketing, and events on behalf of the organization, includes:
+
+* [Danese Cooper](https://www.linkedin.com/in/danesecooper), chairman of the board, distinguished member of technical staff - open source at PayPal;
+* [Scott Hammond](https://www.linkedin.com/pub/scott-hammond/1/a4b/92a), vice-chairman of the board, chief executive officer at Joyent;
+* [Brian McCallister](https://www.linkedin.com/in/brianmccallister), silver-level director of the board, chief technology officer of platforms at Groupon;
+* [Todd Moore](https://www.linkedin.com/pub/todd-moore/2b/540/798), board member, vice president of open technology at IBM;
+* [Steve Newcomb](https://www.linkedin.com/in/stevenewcomb), board member, founder and chief executive officer at Famous Industries;
+* [Gianugo Rabellino](https://www.linkedin.com/in/gianugo), secretary of the board, senior director of open source programs at Microsoft;
+* [Charlie Robbins](https://www.linkedin.com/in/charlierobbins), gold-level director of the board, director of engineering at GoDaddy.com;
+* [Imad Sousou](https://www.linkedin.com/pub/imad-sousou/6/b49/2b8), board member, vice president and general manager at Intel;
+* [Rod Vagg](https://www.linkedin.com/in/rvagg), technical steering committee chairperson, chief node officer at NodeSource.
+
+In addition to formalizing the board, [Bill Fine](https://www.linkedin.com/pub/bill-fine/2/497/916), vice president of product and marketing at Joyent, was elected as the marketing chairperson. The Linux Foundation also hired [Mikeal Rogers](https://www.linkedin.com/in/mikealrogers) as its community manager to help support and guide the new organization.
+
+“The new board members represent the diversity of the Node.js community and the commitment that these companies have to supporting its overall efforts,” said Danese Cooper, chairman of the board, Node.js Foundation. “Node.js is incredibly important to the developer ecosystem and is increasingly relevant for building applications on devices that are changing the pace of commerce. The board will work to support and build the Node.js platform using the blueprint of an open governance model that is transparent and supportive of its community.”
+
+In early June, the Node.js and io.js developer community announced that they were merging their respective code base to continue their work in a neutral forum, the Node.js Foundation. The new leaders will help support the ongoing growth and evolution of the combined communities and will foster a collaborative environment to accelerate growth and the platform’s evolution.
+
+### About Node.js Foundation
+
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft and PayPal. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, Sauce Labs, SAP, StrongLoop and YLD!. Get involved here: [https://nodejs.org](https://nodejs.org).
+
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [www.linuxfoundation.org](http://www.linuxfoundation.org)
diff --git a/locale/uk/blog/announcements/foundation-express-news.md b/locale/uk/blog/announcements/foundation-express-news.md
new file mode 100755
index 0000000000000..c8a7c3d87cd09
--- /dev/null
+++ b/locale/uk/blog/announcements/foundation-express-news.md
@@ -0,0 +1,31 @@
+---
+title: Node.js Foundation to Add Express to its Incubator Program
+date: 2016-02-10T21:00:00.000Z
+category: Annoucements
+slug: Express as Incubator Project
+layout: blog-post.hbs
+---
+
+> Node.js Foundation to Add Express to its Incubator Program
+
+SAN FRANCISCO, Feb. 10, 2016 — The [Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced Express, the most popular Node.js web server framework, and some of its constituent modules are on track to become a new incubation project of the Foundation.
+
+With [53+ million downloads in the last two years](http://npm-stat.com/charts.html?package=express&author=&from=&to=), Express has become one of the key toolkits for building web applications and its stability is essential for many Node.js users, especially those that are just getting started with the platform. Express also underpins some of the most significant projects that support Node.js, including [kraken.js](http://krakenjs.com/), a secure and scalable layer that extends Express and is heavily used by enterprises. Kraken.js was open sourced [by PayPal in 2014](https://www.paypal-engineering.com/2014/03/03/open-sourcing-kraken-js/). It also underpins [Sails.js](http://sailsjs.org/), a web framework that makes it easy to build custom, enterprise-grade Node.js apps, and [Loopback](http://loopback.io/), a Node.js API framework.
+
+“This framework is critical to a significant portion of many Node.js users,” said Mikeal Rogers, Community Manager of the Node.js Foundation. “Bringing this project into the Node.js Foundation, under open governance, will allow it to continue to be a dependable choice for many enterprises and users, while ensuring that we retain a healthy ecosystem of competing approaches to solving problems that Express addresses.”
+
+"The work around developing and maintaining Express has been a tremendous asset to the community," said Rod Vagg, Chief Node Officer at NodeSource and Technical Steering Committee Director of the Node.js Foundation. "With 5 million package downloads in the last month, the stability of this project, that will get a huge boost through open governance, is very important to the efforts of the Node.js Foundation in supporting Node.js as a technology and developer ecosystem."
+
+“IBM is committed not only to growing and supporting the Node.js ecosystem, but to promoting open governance for the frameworks that enable Node.js developers to work smarter, faster and with more agility,” said Todd Moore, IBM, VP Open Technology. “We are thrilled that Express is being introduced as an incubated top level project of the Foundation. Express has a bright future and a new long term home that will ensure resources, reliability and relevancy of Express to the global Node.js developer community.”
+
+Assets related to Express are being contributed to the Node.js Foundation by IBM.
+
+The Node.js Foundation Incubator Program was launched last year. Projects under the Node.js Foundation Incubator Program receive assistance and governance mentorship from the Foundation's Technical Steering Committee and related working groups. The Incubator Program is intended to support the many needs of Node.js users to maintain a competitive and robust ecosystem.
+
+### About Node.js Foundation
+
+Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 3 million active users per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, RisingStack, Sauce Labs, SAP, StrongLoop (an IBM company), YLD!, and Yahoo!. Get involved here: http://nodejs.org.
+
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [www.linuxfoundation.org](http://www.linuxfoundation.org)
diff --git a/locale/uk/blog/announcements/foundation-v4-announce.md b/locale/uk/blog/announcements/foundation-v4-announce.md
new file mode 100755
index 0000000000000..e2db55943a034
--- /dev/null
+++ b/locale/uk/blog/announcements/foundation-v4-announce.md
@@ -0,0 +1,45 @@
+---
+title: Node.js Foundation Combines Node.js and io.js Into Single Codebase in New Release
+date: 2015-09-14T17:00:00.000Z
+status: publish
+category: Annoucements
+slug: foundation-v4-announce
+layout: blog-post.hbs
+---
+
+More Stability, Security, and Improved Test Coverage Appeals to Growing Number of Enterprises Using Node.js
+
+SAN FRANCISCO, Sept. 14, 2015 – The [Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced the release of Node.js version 4.0.0. A record number of individuals and companies helped to contribute to the release, which combines both the Node.js project and io.js project in a single codebase under the direction of the Node.js Foundation.
+
+Currently, Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. With major stability and security updates, a new test cluster, support for ARM processors and long-term support, Node.js v4 represents the latest framework innovation for enterprise users leveraging it to run JavaScript programs.
+
+Named version 4.0.0 because it includes major updates from io.js version 3.0.0, the new release also contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](https://nodejs.org/en/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays (Node's Buffer is now backed by Uint8Array), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and new to V8 v4.5, arrow functions.
+
+Node.js v4 also brings a plan for [long-term support (LTS)](https://github.com/nodejs/LTS/) and a regular release cycle. Release versioning now follows the Semantic Versioning Specification, a specification for version numbers of software libraries and similar dependencies, so expect increments of both minor and patch version over the coming weeks as bugs are fixed and features are added. The LTS will support enterprise users that need more long-term requirements and continue the innovation and work with the V8 team to ensure that Node.js continues to evolve.
+
+"Under the Node.js Foundation, our unified community has made incredibly progress in developing a converged codebase,” said Mikeal Rogers, Community Manager of The Node.js Foundation. “We believe that the new release and LTS cycles allow the project to continue its innovation and adopt cutting-edge JavaScript features, while also serving the need for predictable long-term stability and security demanded by a growing number of enterprise users who are proudly adopting Node.js as a key technology.”
+
+Additional updates include:
+
+* **Stability and Security**: Key Node.js Foundation members, such as IBM, NodeSource and StrongLoop, contributed a strong enterprise-focus to the latest release. Their contributions make this latest version more stable and secure for enterprise needs.
+* **Improved Platform Test Coverage**: With the assistance of some major partners, including RackSpace, DigitalOcean, Scaleway and ARM Holdings, the new release has built one of the most advanced testing clusters of any major open source project creating additional stability to the platform.
+* **First-Class Coverage of ARM variants**: All major ARM variants, ARMv6, ARMv7, and the brand new 64-bit ARMv8, which is making major inroads in the server market, are supported as part of the test infrastructure. Developers who need to use these architectures for developing enterprise-ready and IoT applications are assured solid runtime.
+* **Addition of Arrow Functions**: Node.js v4 now includes arrow functions, an addition that was not previously available even in io.js.
+
+The technical steering committee for the Node.js Foundation is now 15 members strong with 40 plus core committers and 350+ GitHub organization members contributing to the community. The development process and release cycles are much faster due to the large, active community united under the Node.js Foundation umbrella. The next release is planned before the end of 2015. In parallel, the project will be branching a new stable line of releases every six months, with one planned in October and another for spring of 2016.  
+
+Additional Resources
+* Technical Blog - [Node v4.0.0 (Stable)](https://nodejs.org/en/blog/release/v4.0.0/)
+* New GitHub [home](https://github.com/nodejs/node)
+
+About Node.js Foundation
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft and PayPal. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, Sauce Labs, SAP, StrongLoop and YLD!. Get involved here: [http://nodejs.org](http://nodejs.org).
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [https://nodejs.org/en/foundation/](https://nodejs.org/en/foundation/)
+
+> Node.js Foundation is a licensed mark of Node.js Foundation. Node.js is a trademark of Joyent, Inc. and is used with its permission
+
+Media Contact
+Node.js Foundation
+Sarah Conway
+978-578-5300
+pr@nodejs.org
diff --git a/locale/uk/blog/announcements/index.md b/locale/uk/blog/announcements/index.md
new file mode 100755
index 0000000000000..85cc53467b518
--- /dev/null
+++ b/locale/uk/blog/announcements/index.md
@@ -0,0 +1,6 @@
+---
+title: Announcements
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/announcements/interactive-2015-keynotes.md b/locale/uk/blog/announcements/interactive-2015-keynotes.md
new file mode 100755
index 0000000000000..1c5bf33104dfc
--- /dev/null
+++ b/locale/uk/blog/announcements/interactive-2015-keynotes.md
@@ -0,0 +1,62 @@
+---
+title: Keynotes for Node.js Interactive 2015 Announced
+date: 2015-11-20T09:00:00.000Z
+status: publish
+category: Annoucements
+slug: interactive-2015-programming
+layout: blog-post.hbs
+---
+
+> Keynotes from GoDaddy, IBM, NodeSource, Uber and More Featured At Inaugural Node.js Foundation Event December 8-9, 2015, in Portland, Ore.
+
+**SAN FRANCISCO, Nov. 20, 2015** – The [Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced the final keynotes and programming for [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive). The event will feature conversations and presentations on everything from the future of Node.js in IoT to collaborations between the community and the enterprise.
+
+Node.js is the runtime of choice for building mobile, web and cloud applications. The diversity of the technology and its capabilities are making it ubiquitous in almost every ecosystem from personal finance to robotics. To highlight changes with the platform and what’s to come, Node.js Interactive will focus on three tracks: Frontend, Backend and the Internet of Things (IoT). Highlights of these tracks available [here](https://nodejs.org/en/blog/announcements/interactive-2015-programming/); full track sessions [here](http://events.linuxfoundation.org/events/node-interactive/program/schedule).
+
+Node.js Interactive brings together a broad range of speakers to help experienced and novice Node.js users alike learn tips, best practices, new skills, as well as gain insight into future developments for the technology.  
+
+2015 Node.js Interactive keynotes include:
+
+### Day 1, December 8, 2015
+
+* Jason Gartner, Vice President, WebSphere Foundation and PureApplication Dev at IBM
+* James Snell, Open Technologies at IBM, “Convergence: Evolving Node.js with Open Governance and an Open Community”
+* Joe McCann, Co-Founder and CEO at NodeSource, “Enterprise Adoptions Rates and How They Benefit the Community”
+* Ashley Williams, Developer Community and Content Manager at npm
+* Tom Croucher, Engineer Manager at Uber, “Node.js at Uber”
+
+### Day 2, December 9, 2015
+
+* Mikeal Rogers, Node.js Foundation Community Manager at The Linux Foundation, “Node.js Foundation Growth and Goals”
+* Danese Cooper, Distinguished Member of Technical Staff - Open Source at PayPal and Node.js Foundation Chairperson
+* Panel Discussion with Node.js Foundation [Technical Steering Committee members](https://nodejs.org/en/foundation/tsc/)
+
+In addition to keynotes, Node.js Foundation will have breakout sessions and panels discussing how Node.js is used in some of the largest and fastest growing organizations.
+
+**These include:**
+
+* Robert Schultz, Applications Architect at Ancestry
+* Azat Mardan, Technology Fellow at Capital One
+* Charlie Robbins, Director of Engineering UX Platform at GoDaddy
+* Chris Saint-Amant, Director of UI Engineering at Netflix
+* Kim Trott, Director of UI Platform Engineering at Netflix
+* Bill Scott, VP of Next Generation Commerce at PayPal
+* Panel - APIs in Node.js with GoDaddy, Symantec, and StrongLoop Inc.
+* Panel - Node.js and Docker with Joyent, Ancestry and nearForm
+* Panel - Node.js in the Media with Condé Nast, Mic and Bloomberg
+
+“Our list of speakers and breakout sessions are a great way to dive head first into Node.js, no matter if you are new to the platform or an expert,” said Mikeal Rogers, Community Manager, Node.js Foundation. “It is a great way for the community to come together, learn, share and better understand where the technology is heading in the future. The case studies, keynotes and breakout sessions showcased at the event shows how rapidly Node.js is growing in the enterprise.”
+
+Standard registration closes November 27, 2015, after which the conference price will increase from $425 to $525. To register visit [https://www.regonline.com/Register/Checkin.aspx?EventID=1753707](https://www.regonline.com/Register/Checkin.aspx?EventID=1753707).
+
+Node.js Interactive is made possible by Platinum sponsor IBM; Gold sponsors: Joyent, Microsoft, Modulus Inc., Red Hat; and Silver sponsors NodeSource, nearForm and npm and Synchro.
+
+### Additional Resources
+
+* Learn more about the [Node.js Foundation](https://nodejs.org/en/foundation/), and get involved with the [project](https://nodejs.org/en/get-involved/).
+* Want to keep abreast of Node.js Foundation news? Sign up for our newsletter at the bottom of the [Node.js Foundation page](https://nodejs.org/en/foundation/).
+* Follow on [Twitter](https://twitter.com/nodejs?ref_src=twsrc^google|twcamp^serp|twgr^author) and [Google+](https://plus.google.com/u/1/100598160817214911030/posts).
+
+About Node.js Foundation
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, Sauce Labs, SAP, and YLD!. Get involved here: [http://nodejs.org](http://nodejs.org).
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [https://nodejs.org/en/foundation/](https://nodejs.org/en/foundation/)
diff --git a/locale/uk/blog/announcements/interactive-2015-programming.md b/locale/uk/blog/announcements/interactive-2015-programming.md
new file mode 100755
index 0000000000000..c06a9ae0de877
--- /dev/null
+++ b/locale/uk/blog/announcements/interactive-2015-programming.md
@@ -0,0 +1,60 @@
+---
+title: Node.js Foundation Announces Programming For Node.js Interactive
+date: 2015-10-20T17:00:00.000Z
+status: publish
+category: Annoucements
+slug: interactive-2015-programming
+layout: blog-post.hbs
+---
+
+> Inaugural Conference to Advance the Use of Node.js Within Backend, Frontend, IoT Applications
+
+SAN FRANCISCO, Oct. 20, 2015 – [The Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced initial programming for [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive). This inaugural event, which is being led by the newly formed Node.js Foundation in cooperation with the Linux Foundation, will be held December 8-9, 2015, in Portland, Ore.
+
+Node.js has become ubiquitous in almost every ecosystem in technology and is consistently being used more in mainstream enterprises. To continue to evolve the platform, Node.js Interactive brings together a wide range of community, projects, products and companies to create an educational and collaborative space. With more than 700 attendees expected, Node.js Interactive will provide a way to network with other developers and engineers within this diverse community.  
+
+Node.js Interactive will also focus on three tracks: Frontend, Backend and the Internet of Things (IoT); talks for each track were selected in collaboration with track chairs [Jessica Lord](https://github.com/jlord/) (Frontend), [C J Silvero](https://github.com/ceejbot) (Backend) and [Kassandra Perch](https://github.com/nodebotanist) (IoT). A few highlights include:
+
+Frontend Session Highlights:
+* JavaScript, For Science! *with* Max Ogden, Computer Programmer for Dat Project
+* Making Your Node.js Applications Debuggable *with* Patrick Mueller, Senior Node Engineer at NodeSource
+* Node Intl: Where We Are, What's Next *with* Steven Loomis, Senior Software Engineer at IBM
+* Rapid Development of Data Mining Applications in Node.js *with* Blaz Fortuna, Research Consultant for Bloomberg L.P., Senior Researcher at Jožef Stefan Institute and Partner at Quintelligence
+* Real-Time Collaboration Sync Strategies *with* Todd Kennedy, CTO of Scripto
+* Rebuilding the Ship as It Sails: Making Large Legacy Sites Responsive *with* Philip James, Senior Software Engineer at Eventbrite
+
+Backend Session Highlights:
+* Building and Engaging High-Performance Teams in the Node.js Ecosystem *with* Chanda Dharap, Director of Engineering at StrongLoop, an IBM company
+* Microservice Developer Experience *with* Peter Elger, Director of Engineering at nearForm
+* Modernizing Winston for Node.js v4 *with* Charlie Robbins, Director of Engineering UX Platform at GoDaddy
+* Node.js API Pitfalls, Can You Spot Them? *with* Sam Roberts, Node/Ops Developer at StrongLoop, an IBM Company
+* Node.js Performance Optimization Case Study *with* Bryce Baril, Senior Node Engineer at NodeSource
+* Resource Management in Node.js *with* Bradley Meck, Software Engineer at NodeSource
+
+IoT Session Highlights:
+* Contributing to Node Core *with* Jeremiah Senkpiel, Node Core Contributor at NodeSource
+* Hands on Hardware Workshop *with* Tessel with Kelsey Breseman, Engineering Project Manager at 3D Robotics and Steering Committee Member and Board Co-Creator of Tessel Project
+* Internet of Cats *with* Rachel White, Front-End Engineer for IBM Watson
+* IoT && Node.js && You *with* Emily Rose, Senior Software Engineer at Particle IO
+* Node.s Bots at Scale *with* Matteo Collina, Architect at nearForm
+* Node.js Development for the Next Generation of IoT *with* Melissa Evers-Hood, Software Product Line Manager at Intel Corporation
+* Node.js While Crafting: Make Textile to Compute! *with* Mariko Kosaka, Javascript Engineer at Scripto
+
+“Node.js has become pervasive within the last few years, with so many community accomplishments to highlight, including forming the new Node.js Foundation and the convergence of io.js and node.js,” said Mikeal Rogers, Community Manager, Node.js Foundation. “We created this conference to help showcase this growth, to accommodate the Node.js community’s many different needs, and to help accelerate adoption as it expands into enterprises.”
+
+Early bird registration ends October 23, 2015. Standard registration closes November 21, 2015, after which the conference price will increase from $425 to $525. Discounted hotel rates are also available until Wednesday, November 11, 2015. To register visit [https://www.regonline.com/Register/Checkin.aspx?EventID=1753707](https://www.regonline.com/Register/Checkin.aspx?EventID=1753707).
+
+Node.js Interactive is made possible by platinum sponsor IBM, gold sponsor Microsoft, and silver sponsors NodeSource and nearForm.
+
+Additional panels and keynotes will be announced in the coming weeks; to see the initial program visit: [http://nodejspdx2015.sched.org](http://nodejspdx2015.sched.org). For more information visit [http://events.linuxfoundation.org/events/node-interactive](http://events.linuxfoundation.org/events/node-interactive).
+
+Additional Resources
+
+Learn more about the [Node.js Foundation](https://nodejs.org/en/foundation/), and get involved with [the project](https://nodejs.org/en/get-involved/).
+Want to keep abreast of Node.js Foundation news? Sign up for our newsletter at the bottom of the [Node.js Foundation page](https://nodejs.org/en/foundation/).
+Follow on [Twitter](https://twitter.com/nodejs?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) and [Google+](https://plus.google.com/u/1/100598160817214911030/posts).
+
+About Node.js Foundation
Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, Rising Stack, Sauce Labs, SAP, and YLD!. Get involved here: [http://nodejs.org](http://nodejs.org).
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [https://nodejs.org/en/foundation/](https://nodejs.org/en/foundation/)
diff --git a/locale/uk/blog/announcements/interactive-2015.md b/locale/uk/blog/announcements/interactive-2015.md
new file mode 100755
index 0000000000000..f474a337e5675
--- /dev/null
+++ b/locale/uk/blog/announcements/interactive-2015.md
@@ -0,0 +1,26 @@
+---
+title: Node.js Interactive
+date: 2015-09-10T17:00:00.000Z
+status: publish
+category: Annoucements
+slug: interactive-2015
+layout: blog-post.hbs
+---
+Are You Ready for Node.js Interactive?
+
+The Node.js Foundation is pleased to announce [Node.js Interactive](http://interactive.nodejs.org) happening from December 8-9, 2015 in Portland, OR. With node.js growing in all aspects of technology, the gathering will cover everything from streamlining development of fast websites and real-time applications to tips for managing node.js applications, and much more.
+
+The event will be the first of its kind under the Node.js Foundation led in cooperation with The Linux Foundation. Vendor-neutral by design, it will focus on the continued ideals of open governance collaboration between the now joined node.js and io.js community. The conference welcomes experienced developers as well as those interested in how node.js might be of use to their business with tracks that focus on IoT, front-end and back-end technologies. To curate these tracks and create the best experience for attendees, track chairs include seasoned veterans:
+
+* [Kassandra Perch](https://github.com/nodebotanist) for IoT, a software developer / evangelist / advocate / educator / roboticist living in Austin, TX, who you can follow at: [@nodebotanist](https://twitter.com/nodebotanist).
+* [Jessica Lord](https://github.com/jlord/) for Front-End, a GitHub developer and designer who loves open source, JavaScript & node.js, and stories of Tudor England and is a Portland transplant.
+* [C J Silverio](https://github.com/ceejbot) for Back-End, who is all node, all the time and works as VP of engineering at npm, Inc. in the Bay area.
+
+As the Node.js community continues to grow, the Node.js Foundation believes this event is the perfect place to continue to develop collaboration and better understand what’s next for this extremely popular technology. Interested in joining us? Register [here](http://events.linuxfoundation.org/events/node-interactive/attend/register). Timeline for discount rates are as follows:
+
+* Super Early Bird - US$200 for the 1st 100 tickets
+* Early Bird - US$325, ends October 17
+* Standard - US$425, ends November 21
+* Late & Onsite - US$525, begins November 22
+
+If you are interested in becoming a speaker, please check out our [Call For Participation](http://events.linuxfoundation.org/events/node-interactive/program/cfp) page for more details. Call for Participation closes on September 24, 2015.
diff --git a/locale/uk/blog/announcements/nodejs-foundation-survey.md b/locale/uk/blog/announcements/nodejs-foundation-survey.md
new file mode 100755
index 0000000000000..aa7aa45475d94
--- /dev/null
+++ b/locale/uk/blog/announcements/nodejs-foundation-survey.md
@@ -0,0 +1,119 @@
+---
+title: New Node.js Foundation Survey Reports New “Full Stack” In Demand Among Enterprise Developers   
+date: 2016-04-12T13:00:00.000Z
+status: publish
+category: Annoucements
+slug: nodejs-foundation-survey
+layout: blog-post.hbs
+---
+
+> Nearly 50 percent of Node.js developers surveyed using container technology, strong growth emerges in cloud, front end, mobile and devices 
+
+**SAN FRANCISCO, April, 12, 2016** — [The Node.js Foundation](http://ctt.marketwire.com/?release=11G082331-001&id=8448115&type=0&url=https%3a%2f%2fnodejs.org%2fen%2ffoundation%2f), 
+a community-led and industry-backed consortium to advance the development of the Node.js 
+platform, today announced the availability of its first ever Node.js User Survey Report. 
+
+With over 3.5 million users and an annual growth rate of 100 percent, Node.js is emerging as 
+a universal platform used for web applications, IoT, and enterprise. The Node.js User Survey 
+report features insights on emerging trends happening in this massive community that serves 
+as a leading indicator on trends like microservices architectures, real-time web applications,
+Internet of Things (IoT). The report paints a detailed picture of the technologies that are 
+being used, in particular, with Node.js in production and language preferences (current and 
+future) for front end, back end and IoT developers.
+
+## Key findings from the Node.js Foundation survey
+
+### Node.js and Containers Take Off Together
+
+Both Node.js and containers are a good match for efficiently developing and deploying 
+microservices architectures. And, while the surge in container use is relatively new, **45 
+percent of developers that responded to the survey use Node.js with the technology**. Other 
+container-related data points: 
+
+* 58 percent of respondents that identified as IoT developers use Node.js with Docker.
+* 39 percent of respondents that identified as back end developers use Node.js with Docker.
+* 37 percent of respondents that identified as front end developers use Node.js with Docker.
+
+### Node.js — the Engine that Drives IoT 
+
+JavaScript and Node.js have risen to be the language and platform of choice for IoT as both 
+are suited for data intensive environments that require parallel programming without 
+disruption. JavaScript, including Node.js and frameworks, such as React, have become the de 
+facto choice of developers working in these connected, device-driven environments with **96 
+percent of IoT respondents indicating they use JavaScript/Node.js for development**. 
+
+“Data about developer choices is catnip for developers,” said James Governor, RedMonk 
+co-founder. “In this survey, the Node.js Foundation identifies some interesting results, 
+notably about languages programmers are using alongside Node.js and IoT demographics.”
+
+These environments are challenging, and the survey revealed that on average, IoT developers 
+using Node.js have more experience than their front end and back end counterparts with more 
+than 40 percent of IoT developers surveyed having over 10+ years of development experience. 
+
+Additionally, although Docker is a server technology, many IoT developers (58%) are using 
+Node.js with Docker compared to only 39 percent of back end developers. This metric is 
+significant as it means that the new IoT world also is quickly adopting containers and 
+microservices.
+
+### Node.js Becoming Universal Platform
+
+**The full stack is no longer “front end and back end,” but rather “front end, back end and 
+connected devices,”** which is a combination of everything from the browser to a toaster all 
+being run in JavaScript and enabled by Node.js. The survey revealed that 62 percent of 
+respondents are using Node.js for both front end and back end development, and nearly 10 
+percent are using Node.js for front end, back end, and IoT development. 
+
+### Node.js Pervasive in Enterprises 
+
+Node.js is increasingly used in the enterprise, and used within huge enterprises like PayPal, 
+Go Daddy, Capital One, and Intel. The survey found: 
+
+* **More than 45 percent already using the Node.js Long Term Support release (v4) geared 
+toward medium to large enterprise users who require stability and high performance.**
+* Of those who haven’t upgraded, 80 percent report definite plans to upgrade to v4, with half 
+of respondents planning to do so this year. 
+* Strong interest in enterprise tooling among 34 percent of tech leaders.
+
+### Full “MEAN” Stack Explodes 
+
+The popularity of real-time, social networking and interactive game applications is pushing a 
+new stack among developers. The MEAN stack is able to handle lots of concurrent connections 
+and extreme scalability, which these applications demand. Node.js, in combination with 
+MongoDB, Express, AngularJS, allows developers to tackle the needs of front end and back end 
+development. Not surprisingly, all of these technologies were commonly used alongside 
+Node.js. **Express, cited the most, is used by an average of 83 percent of developers**.
+
+### Popularity of JavaScript and Node.js
+
+JavaScript and Node.js were popular among back end, front end, and IoT developers. Other 
+languages, beyond JavaScript, that were popular for all three developer types included PHP, 
+Python and Java. However, when looking to the future, back end, front end and IoT developers 
+planned to decrease their use of Java, .Net and PHP (PHP averages a 15% decrease) and 
+increase the use of Python and C++. 
+
+## About the Survey 
+
+The survey was open for 15 days, from January 13 to January 28, 2016. During this time, 1,760 
+people from around the world completed the survey. Seventy percent were developer's, 22 
+percent technical management and 64 percent run Node.js in production. Geographic 
+representation of survey covered: 35 percent from United States, 22 percent from Continental 
+Europe, 6 percent India, and 6 percent from United Kingdom with the remaining respondents 
+hailing from Asia, Latin America, Africa, Russia and the Middle East.  
+
+**Additional Resources:**
+* [Node.js Foundation User survey infographic](/static/documents/2016-survey-infographic.png) 
+* [Report summarizing Node.js Foundation User Survey 2016](/static/documents/2016-survey-report.pdf)
+
+**About Node.js Foundation**
+
+Node.js is used by tens of thousands of organizations in more than 200 countries and amasses 
+more than 3 million active users per month. It is the runtime of choice for high-performance, 
+low latency applications, powering everything from enterprise applications, robots, API 
+engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, 
+IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource 
+and Modulus/Progress Software, and Silver members include Apigee, AppDynamics, Codefresh, 
+DigitalOcean, Fidelity, Google, Groupon, nearForm, New Relic, npm, Opbeat, RisingStack, Sauce 
+Labs, SAP, StrongLoop (an IBM company), Sphinx, YLD!, and Yahoo!. Get involved here: 
+[http://nodejs.org](http://nodejs.org).
diff --git a/locale/uk/blog/announcements/v6-release.md b/locale/uk/blog/announcements/v6-release.md
new file mode 100755
index 0000000000000..806d000451b61
--- /dev/null
+++ b/locale/uk/blog/announcements/v6-release.md
@@ -0,0 +1,80 @@
+---
+title: World’s Fastest Growing Open Source Platform Pushes Out New Release
+date: 2016-04-26T12:00:00.000Z
+status: publish
+category: Annoucements
+slug: v6-release
+layout: blog-post.hbs
+---
+
+> New “Current” version line focuses on performance improvements, increased reliability and 
+better security for its 3.5 million users
+
+SAN FRANCISCO, April, 26, 2016 — [The Node.js Foundation](http://ctt.marketwire.com/?release=11G082331-001&id=8448115&type=0&url=https%3a%2f%2fnodejs.org%2fen%2ffoundation%2f), a 
+community-led and industry-backed consortium to advance the development of the Node.js 
+platform, today announced the release of Node.js version 6 (Node.js v6). This release 
+provides major performance improvements, increased reliability and better security. 
+
+With over 3.5 million users and an annual growth rate of 100 percent, Node.js is emerging as 
+a universal platform used for web applications, IoT, mobile, enterprise application 
+development, and microservice architectures. The technology is ubiquitous across numerous 
+industries, from startups to Fortune 500 companies, and is the only unified platform that 
+full stack JavaScript developers can use for front end, back end, mobile and IoT projects. 
+
+Performance improvements are key in this latest release with one of the most significant 
+improvements coming from module loading, which is currently four times faster than Node.js 
+version 4 (Node.js v4). This will help developers dramatically decrease the startup time of 
+large applications for the best productivity in development cycles and more seamless 
+experience with end users. In addition, Node.js v6 comes equipped with v8 JavaScript engine 
+5.0, which has improved ECMAScript 2015 (ES6) support. Ninety-three percent of 
+[ES6](http://node.green/) features are also now supported in the Node.js v6 release, up from 
+56 percent for Node.js v5 and 50 percent for Node.js v4. Key features from ES6 include: 
+default and rest parameters, destructuring, class and super keywords.
+
+Security is top-of-mind for enterprises and startups alike, and Node.js v6 has added several 
+features that impact security, making it easier to write secure code. The new Buffer API will 
+reduce the risk of bugs and vulnerabilities leaking into applications through a new 
+constructor method used to create Buffer instances, as well as a zero-fill-buffers 
+command-line flag. Using the new command line flag, developers can continue to safely use 
+older modules that have not been updated to use the new constructor API. In addition, V8 has 
+improved their implementation of Math.random() to be more secure — this feature is added into 
+Node.js v6.
+
+“The Node.js Project has done an incredible job of bringing this version to life in the 
+timeline that we initially proposed in September 2015. It’s important for us to continue to 
+deliver new versions of Node.js equipped with all the cutting-edge JavaScript features to 
+serve the needs of developers and to continue to improve the performance and stability 
+enterprises rely on,” said Mikeal Rogers, Community Manager of the Node.js Foundation. “This 
+release is committed to Long Term Support, which allows predictable long-term stability, 
+reliability, performance and security to the growing number of enterprise users that are 
+adopting Node.js as a key technology in their infrastructure.” 
+
+To increase reliability of Node.js, there has been increased documentation and testing done 
+around Node.js v6 for enterprises that are using and looking to implement the platform.
+
+Node.js release versioning follows the Semantic Versioning Specification, a specification for 
+version numbers of software libraries similar to dependencies. Under the Node.js’ [Long-Term 
+Support (LTS)](https://github.com/nodejs/LTS/), version 6 is now the “Current” release line 
+while version 5 will be maintained for a few more months. In October 2016, Node.js v6 will 
+become the LTS release and the LTS release line (version 4) will go under maintenance mode in 
+April 2017, meaning only critical bugs, critical security fixes and documentation updates 
+will be permitted. Users should begin transitioning from v4 to v6 in October when v6 goes 
+into LTS.
+
+Additional Resources
+* [Download version 6](https://nodejs.org/download/release/v6.0.0/)
+* [Download version 4](https://nodejs.org/en/download/)
+* [Technical blog with additional new features and updates](https://nodejs.org/en/blog/)
+
+About Node.js Foundation
+Node.js is used by tens of thousands of organizations in more than 200 countries and amasses 
+more than 3.5 million active users per month. It is the runtime of choice for 
+high-performance, low latency applications, powering everything from enterprise applications, 
+robots, API engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, 
+IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource 
+and Modulus/Progress Software, and Silver members include Apigee, AppDynamics, Codefresh, 
+DigitalOcean, Fidelity, Google, Groupon, nearForm, New Relic, npm, Opbeat, RisingStack, Sauce 
+Labs, SAP, StrongLoop (an IBM company), Sphinx, YLD!, and Yahoo!. Get involved here: 
+[https://nodejs.org](https://nodejs.org).
diff --git a/locale/uk/blog/announcements/welcome-google.md b/locale/uk/blog/announcements/welcome-google.md
new file mode 100755
index 0000000000000..944d7b8b67d49
--- /dev/null
+++ b/locale/uk/blog/announcements/welcome-google.md
@@ -0,0 +1,18 @@
+---
+title: Welcome Google Cloud Platform!
+date: 2016-03-29T13:00:00.000Z
+status: publish
+category: Annoucements
+slug: welcome-google
+layout: blog-post.hbs
+---
+
+Google Cloud Platform joined the Node.js Foundation today. This news comes on the heels of the Node.js runtime going into beta on [Google App Engine](https://cloudplatform.googleblog.com/2016/03/Node.js-on-Google-App-Engine-goes-beta.html), a platform that makes it easy to  build scalable web applications and mobile backends across a variety of programming languages.
+
+In the industry, there’s been a lot of conversations around a third wave of cloud computing that focuses less on infrastructure and more on microservices and container architectures. Node.js, which is a cross-platform runtime environment that consists of open source modules, is a perfect platform for these types of environments. It’s incredibly resource-efficient, high performing and well-suited to scalability. This is one of the main reasons why Node.js is heavily used by IoT developers who are working with microservices environments. 
+
+“Node.js is emerging as the platform in the center of a broad full stack, consisting of front end, back end, devices and the cloud,” said Mikeal Rogers, community manager of the Node.js Foundation. “By joining the Node.js Foundation, Google is increasing its investment in Node.js and deepening its involvement in a vibrant community. Having more companies join the Node.js Foundation helps solidify Node.js as a leading universal development environment.”
+
+Along with joining the Node.js Foundation, Google develops the V8 JavaScript engine which powers Chrome and Node.js. The V8 team is working on infrastructural changes to improve the Node.js development workflow, including making it easier to build and test Node.js on V8’s continuous integration system. Google V8 contributors are also involved in the Core Technical Committee.
+
+The Node.js Foundation is very excited to have Google Cloud Platform join our community and look forward to helping developers continue to use Node.js everywhere.
diff --git a/locale/uk/blog/announcements/welcome-redhat.md b/locale/uk/blog/announcements/welcome-redhat.md
new file mode 100755
index 0000000000000..f5256dd278f83
--- /dev/null
+++ b/locale/uk/blog/announcements/welcome-redhat.md
@@ -0,0 +1,31 @@
+---
+title: Node.js Foundation Welcomes Red Hat as Newest Platinum Member
+date: 2015-10-06T12:30:00.000Z
+status: publish
+category: Annoucements
+slug: welcome-redhat
+layout: blog-post.hbs
+---
+
+# Node.js Foundation Welcomes Red Hat as Newest Platinum Member
+
+> Company Looks to Accelerate Node.js Adoption for Enterprise Software Development
+
+**SAN FRANCISCO, Oct. 6, 2015** – The [Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced Red Hat, Inc. has joined the Foundation as a Platinum member. Red Hat joins platinum members, including Famous, IBM, Intel, Joyent, Microsoft and PayPal, to provide support in the adoption, development and long-term success of the Node.js project.
+
+Node.js is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications to robots. Over the last two years, more large enterprises, including Red Hat, IBM, PayPal, Fidelity, and Microsoft, have adopted Node.js as part of their enterprise fabric. Today there are 2 million unique IP addresses installing Node.js packages and more than 2 billion package downloads in the last month.
+
+Often used for building fast, scalable network applications, Node.js supports Red Hat technologies such as [Red Hat Mobile Application Platform](https://www.redhat.com/en/technologies/mobile/application-platform), and is available in [OpenShift by Red Hat](https://www.openshift.com/) and [Red Hat Software Collections](http://developerblog.redhat.com/tag/software-collections/). As a new member, Red Hat is providing financial support, technical contributions, and high-level policy guidance for the newly formed Foundation that operates as a neutral organization to support the project governed by the Node.js community.
+
+“Node.js has become an important tool for developers who need to build and deploy a new generation of highly responsive, scalable applications for mobile and Internet of Things (IoT),” said Rich Sharples, senior director, Product Management at Red Hat. “We welcome deeper collaboration with the Node.js Foundation and broader community, and look forward to helping increase the role that the technology plays in enterprise software development.”
+
+“Node.js is exploding in popularity in almost every aspect of technology from microservices architecture to data-intensive applications that run across distributed devices,” said Danese Cooper, Chairperson of the Node.js Foundation Board. “It is a pivotal moment for the technology, and the support of Foundation members is imperative to ensure that Node.js stays relevant and addresses topical projects and problems that are happening within the wider Node.js community.”
+
+Additional Resources
+* Learn more about the [Node.js Foundation](https://nodejs.org/en/foundation/) and get involved with [the project](https://nodejs.org/en/get-involved/).
+
+### About Node.js Foundation
+
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites. The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft, PayPal and Red Hat. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, Sauce Labs, SAP, and YLD!. Get involved here: [http://nodejs.org](http://nodejs.org).
+
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [https://nodejs.org/en/foundation/](https://nodejs.org/en/foundation/)
diff --git a/locale/uk/blog/community/building-nodejs-together.md b/locale/uk/blog/community/building-nodejs-together.md
new file mode 100755
index 0000000000000..b529069745f80
--- /dev/null
+++ b/locale/uk/blog/community/building-nodejs-together.md
@@ -0,0 +1,188 @@
+---
+title: Building Node.js Together
+author: tjfontaine
+date: 2014-07-29T21:00:00.000Z
+status: publish
+category: Community
+slug: building-nodejs-together
+layout: blog-post.hbs
+---
+
+Node.js is reaching more people than ever, it's attracting new and interesting
+use cases, at the same time as seeing heavy adoption from traditional
+engineering departments. Managing the project to make sure it continues to
+satisfy the needs of its end users requires a higher level of precision and
+diligence. It requires taking the time to communicate and reach out to new and
+old parties alike. It means seeking out new and dedicated resources. It means
+properly scoping a change in concert with end users, and documenting and
+regularly check pointing your progress. These are just some of the ways we're
+working to improve our process, and work to deliver higher quality software
+that meets our goals.
+
+## Documentation
+
+One of the big things we've wanted to do is to change the way the website
+works, which is something I've [mentioned
+before](http://blog.nodejs.org/2014/01/16/nodejs-road-ahead/). It should be a
+living breathing website whose content is created by our end users and team.
+The website should be the canonical location for documentation on how to use
+Node.js, how Node.js works, and how to find out what's going on in the Node
+community. We have seeded the initial documentation with [how to
+contribute](https://nodejs.org/en/get-involved/contribute/), [who the core team
+is](https://nodejs.org/en/about/organization/#index_md_technical_steering_committee),
+and some basic documentation of the [project
+itself](https://nodejs.org/en/about/organization). From there we're looking to
+enable the community to come in and build out the rest of the framework for
+documentation.
+
+One of the key changes here is that we're extending the tools that generate API
+documentation to work for the website in general. That means the website is now
+written in markdown. Contributions work with the same
+[pull-request](https://nodejs.org/en/get-involved/contribute/#code-contributions)
+way as contributions to Node itself. The intent here is to be able to quickly
+generate new documentation and improve it with feedback from the community.
+
+The website should also be where we host information about where the project is
+going and the features we're currently working on (more about that later). But
+it's crucial we communicate to our end users what improvements will be coming,
+and the reasons we've made those decisions. That way it's clear what is coming
+in what release, and also can inspire you to collaborate on the design of that
+API. This is not a replacement for our issue tracking, but an enhancement that
+can allow us to reach more people.
+
+## Features
+
+Which brings us to the conversation about features. During the Q & A portions
+of the [Node.js on the
+Road](http://blog.nodejs.org/2014/06/11/notes-from-the-road/) events there are
+often questions about what does and doesn't go into core. How the team
+identifies what those features are and when you decide to integrate them. I've
+spent a lot of time talking about that but I've also
+[added](https://nodejs.org/en/about/organization) it to the new documentation on
+the site.
+
+It's pretty straight forward, but in short if Node.js needs an interface to
+provide an abstraction, or if everyone in the community is using the same
+interface, then those interfaces are candidates for being exposed as public
+interfaces for Node. But what's important is that the addition of an API should
+not be taken lightly. It is important for us to consider just how much of an
+interface we can commit to, because once we add the API it's incredibly hard
+for us to change or remove it. At least in a way that allows people to write
+software that will continue to work.
+
+So new features and APIs need to come with known use cases and consumers, and
+with working test suites. That information is clearly and concisely present on
+the website to reach as wide of an audience as possible. Once an implementation
+meets those requirements it can be integrated into the project. Then and only
+then, when we have an implementation that meets the design specification and
+satisfies the test suite, will we be able to integrate it. That's how we'll
+scope our releases going forward, that's how we'll know when we're ready to
+release a new version of Node. This will be a great change for Node, as it's a
+step forward on moving to an always production ready master branch.
+
+## Quality Software
+
+And it's because Node.js is focused on quality software and a commitment to
+backwards compatibility that it's important for us to seek ways to get more
+information from the community about when and where we might be breaking them.
+Having downstream users test their code bases with recent versions of Node.js
+(even from our master branch) is an important way we derive feedback for our
+changes. The sooner we can get that information, the more test coverage we can
+add, the better the software we deliver is.
+
+Recently I had the opportunity to speak with [Dav
+Glass](http://twitter.com/davglass) from [Yahoo!](http://yahoo.com), and we're
+going to be finding ways to get automated test results back from some larger
+test suites. The more automation we can get for downstream integration testing
+the better the project can be at delivering quality software.
+
+If you're interested in participating in the conversation about how Node.js can
+be proactively testing your software/modules when we've changed things, please
+[join the conversation](http://github.com/joyent/node/issues).
+
+## Current release
+
+Before we can release v0.12, we need to ensure we're providing a high quality
+release that addresses the needs of the users as well as what we've previously
+committed to as going into this release. Sometimes what can seem like an
+innocuous change that solves an immediate symptom, doesn't actually treat the
+disease, but instead results in other symptoms that need to be treated.
+Specifically in our streams API, it can be easy to subtly break people while
+trying to fix another bug with good intent.
+
+This serves as a reminder that we need to properly scope our releases. We need
+to know who the consumers are for new APIs and features. We need to make sure
+those features' test cases are met. We need to make sure we're adopting APIs
+that have broad appeal. And while we're able to work around some of these
+things through external modules and experimenting with JavaScript APIs, that's
+not a replacement for quality engineering.
+
+Those are the things that we could have done better before embarking on 0.12,
+and now to release it we need to fix some of the underlying issues. Moving
+forward I'm working with consumers of the tracing APIs to work on getting a
+maintainable interface for Node that will satisfy their needs. We'll publicly
+document those things, we'll reach out to other stakeholders, and we'll make
+sure that as we implement that we can deliver discretely on what they need.
+
+That's why it's important for us to get our releases right, and diagnose and
+fix root causes. We want to make sure that your first experience with 0.12
+results in your software still working. This is why we're working with large
+production environments to get their feedback, and we're looking for those
+environments and you to [file bugs](https://github.com/joyent/node/issues) that
+you find.
+
+## The Team
+
+The great part about Node's contribution process and our fantastic community is
+that we have a lot of very enthusiastic members who want to work as much as
+possible on Node. Maybe they want to contribute because they have free time,
+maybe they want to contribute to make their job easier, or perhaps they want to
+contribute because their company wants them to spend their time on open source.
+Whatever the reason, we welcome contributions of every stripe!
+
+We have our core team that manages the day to day of Node, and that works
+mostly by people wanting to maintain subsystems. They alone are not solely
+responsible for the entirety of that subsystem, but they guide its progress by
+communicating with end users, reviewing bugs and pull requests, and identifying
+test cases and consumers of new features. People come and go from the core
+team, and recently we've added [some
+documentation](https://nodejs.org/en/about/organization) that describes how you
+find your way onto that team. It's based largely around our contribution
+process. It's not about who you work for, or about who you know, it's about
+your ability to provide technical improvement to the project itself.
+
+For instance, Chris Dickinson was recently hired to work full time on Node.js,
+and has expressed interest in working on the current and future state of
+streams. But it's not who employs Chris that makes him an ideal candidate, but
+it will be the quality of his contributions, and his understanding of the ethos
+of Node.js. That's how we find members of the team. And Chris gets that, in
+[his blog](http://neversaw.us/2014/05/08/on-joining-walmart-labs/) about
+working full time on Node.js he says (and I couldn't have said it better
+myself):
+
+> I will not automatically get commit access to these repositories — like any
+other community member, I will have to continually submit work of consistent
+quality and put in the time to earn the commit bit. The existing core team will
+have final say on whether or not I get the commit bit — which is as it should
+be!
+
+Exactly. And not only does he understand how mechanism works, but he's [already
+started](http://neversaw.us/2014/07/13/june-recap/) getting feedback from
+consumers of streams and documenting some of his plans.
+
+In addition to Chris being hired to work full time on Node.js, Joyent has
+recently hired [Julien Gilli](https://github.com/misterdjules) to work full
+time with me on Node. I'm really excited for all of the team to be seeking out
+new contributors, and getting to know Chris and Julien. They're both fantastic
+and highly motivated, and I want to do my best to enable them to be successful
+and join the team. But that's not all, I've been talking to other companies who
+are excited to participate in this model, and in fact
+[Modulus.io](http://modulus.io) themselves are looking to find someone this
+year to work full time on Node.js.
+
+Node.js is bigger than the core team, it's bigger than our community, and we
+are excited to continue to get new contributors, and to enable everyone. So
+while we're working on the project we can't just focus on one area, but instead
+consider the connected system as a whole. How we scale Node, how we scale the
+team, how we scale your contributions, and how we integrate your feedback --
+this is what we have to consider while taking this project forward, together.
diff --git a/locale/uk/blog/community/foundation-benefits-all.md b/locale/uk/blog/community/foundation-benefits-all.md
new file mode 100755
index 0000000000000..a9d20b7da975f
--- /dev/null
+++ b/locale/uk/blog/community/foundation-benefits-all.md
@@ -0,0 +1,90 @@
+---
+title: The Node.js Foundation benefits all
+author: Scott Hammond
+date: 2015-05-15T22:50:46.000Z
+status: publish
+category: Community
+slug: the-nodejs-foundation-benefits-all
+layout: blog-post.hbs
+---
+
+When I joined Joyent last summer I quickly realized that, despite the huge
+success of Node.js in the market and the tireless work of many here at Joyent,
+there were challenges in the project that we needed to address. Through
+discussions with various project contributors, Node.js users, ecosystem
+vendors and the [Node.js Advisory Board](http://nodeadvisoryboard.com), it
+became clear that the best way to address the concerns of all key stakeholders
+(and the best thing for Node.js as a whole) was to establish the Foundation as
+a path for the future.
+
+The biggest and most obvious challenge we sought to address with the
+Foundation was the friction that existed amongst some developers in the
+Node.js community. Historically, leadership ran the project fairly tightly,
+with a small core of developers working in a BDFL model. It was difficult for
+new people to join the project, and there wasn’t enough transparency for such
+a diverse, passionate community to have a sense of ownership. Consequently, a
+group of developers who wanted to operate under a more open governance model
+created the io.js fork. That team has done a great job innovating on
+governance and engagement models, and the Node.js Foundation’s models will be
+based on those policies to ensure broader community engagement in the future
+of Node.js. We welcome community review and feedback on [the draft governance
+documents](https://github.com/joyent/nodejs-advisory-board/tree/master/governance-proposal).
+
+With the recent vote by the io.js TC to join the Node.js Foundation, we took a
+giant leap toward rebuilding a unified community.  @mikeal, @piscisaureus and
+others have done an excellent job evangelizing the value of the Foundation,
+and it’s great to see it have such positive impact this early in its
+formation.
+
+Reunification of the Node.js developer community remains an important goal of
+the Foundation. But to have a successful project, we must also maintain focus
+on addressing the concerns of Node.js users and the ecosystem of vendors. If
+we succeed, Node.js will continue its meteoric rise as the defacto server side
+javascript platform, and everyone wins. If we get it wrong, we jeapordize the
+momentum and critical mass that's driven that growth, and everyone loses.
+
+In the user community, enterprise adoption of Node.js has skyrocketed with an
+abundance of success stories. But behind every successful project is someone
+who is betting their career on the choice to build with Node.js. Their primary
+“ask” is to de-risk the project. They want stable, production-grade code that
+will handle their technical requirements and an LTS that matches what they get
+from other software. The Foundation will get that right. Donations to the
+Foundation will provide the resources we need to broaden and automate the
+necessary test suites and expand coverage across a large set of platforms. We
+are working now on codifying the LTS policy (comments welcome
+[here](https://github.com/nodejs/dev-policy/issues/67)) and will establish the
+right 6-9 month release cadence with rigor on backward compatibility and EOL
+horizon.
+
+Users also want the project to be insulated from the direction of any single
+company or individual. Putting the project into a foundation insulates it from
+the commercial aspirations of Joyent or any other single company. It also
+facilitates the creation of the vibrant vendor ecosystem around Node.js that
+users want. Users want to see relevant innovation from a strong group of
+contributors and vendors.
+
+The vendors themselves have a clear set of requirements that can best be
+addressed by the Foundation. They want a level playing field and they want to
+know they can monetize the contributions they make to the project. We need a
+vibrant ecosystem to complete the solution for the users of Node.js and drive
+additional value and innovation around the core project. The ecosystem is the
+force multiplier of value for every piece of technology and Node.js is no
+exception.
+
+Finally, in addition to risk mitigation, transparency, neutrality and an open
+governance model, the Foundation will provide needed resources. Over the past
+few years Joyent and other members of the community have invested thousands of
+hours and millions of dollars into the project, and much has been
+accomplished. Going forward, Joyent will continue to invest aggressively in
+the success and growth of Node.js. But now, with the support of new Foundation
+members, we will be able to do even more. Investments from new members can be
+used to expand coverage of testing harnesses, establish API compatibility
+tests and certifications, extend coverage for additional platforms, underwrite
+travel expenses for technical meetups for core contributors, build training
+programs for users and developers, expand community development efforts, fund
+full-time developers and more.
+
+I’m convinced the Foundation is the best vehicle for balancing the needs of
+Node.js users, vendors and contributors. The project has a brilliant future
+ahead of it and I am more optimistic than ever that we can work together as
+one strong community to secure that future.
diff --git a/locale/uk/blog/community/index.md b/locale/uk/blog/community/index.md
new file mode 100755
index 0000000000000..29d5ac3dfd5b7
--- /dev/null
+++ b/locale/uk/blog/community/index.md
@@ -0,0 +1,6 @@
+---
+title: Community
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/community/individual-membership.md b/locale/uk/blog/community/individual-membership.md
new file mode 100755
index 0000000000000..9a7443a371207
--- /dev/null
+++ b/locale/uk/blog/community/individual-membership.md
@@ -0,0 +1,49 @@
+---
+title: Node.js Foundation Individual Membership Now Open
+date: 2015-11-04T12:00:00.000Z
+status: publish
+category: Community
+slug: individual-membership-nodejs-foundation
+layout: blog-post.hbs
+author: mikeal
+---
+
+The Node.js Foundation is a member-supported organization. To date we've added over 20 corporate members who provide the financial support necessary for the Foundation to thrive.
+
+With the support of the Linux Foundation we are now able to launch an Individual Membership program. These members will be electing two representatives to the Board of Directors this January who will be
+responsible for representing the diverse needs of the Node.js community in the administration of the Node.js Foundation.
+
+## How do I become a member?
+
+Membership costs [$100 a year, or $25 for students](https://identity.linuxfoundation.org/pid/99).
+Contributors to the Node.js project, including all Working Groups and sub-projects, are eligible for free membership.
+
+You are required to have a GitHub account to register.
+
+## Who can run for the board of directors?
+
+Any registered member.
+
+Keep in mind that every meeting of the Board must reach quorum in order to pass resolutions, so only people who can make themselves available on a recurring and consistent basis should consider running.
+
+## What does the Board of Directors do?
+
+The Board meets every month to approve resolutions and discuss Node.js Foundation administrative matters. This includes legal considerations, budgeting and approving Foundation-led conferences and other initiatives. Technical governance is overseen by the TSC, not the Board of Directors.
+
+The current board members are listed [here](../../../foundation/board).
+
+## What are the term lengths?
+
+The standard term length for those elected by the individual membership is 2 years, with an election each year to select a new representative for a new term.
+
+However, in the first election two representatives will be elected; the representative with the most votes will be elected for the standard 2 year term and the runner-up will serve a special 1-year term so that in 2017 we can elect a single new director for a 2 year staggered term.
+
+## When is the election?
+
+* Nominations are being solicited until January 15th.
+* A ballot will be distributed on January 20th.
+* The election will be completed by January 30th.
+
+## How do I run in the 2016 election?
+
+After you've registered as a member follow the instructions [here](https://github.com/nodejs/membership/issues/12).
diff --git a/locale/uk/blog/community/next-chapter.md b/locale/uk/blog/community/next-chapter.md
new file mode 100755
index 0000000000000..d69957597278b
--- /dev/null
+++ b/locale/uk/blog/community/next-chapter.md
@@ -0,0 +1,103 @@
+---
+title: Next Chapter
+author: tjfontaine
+date: 2015-05-08T19:00:00.000Z
+status: publish
+category: Community
+slug: next-chapter
+layout: blog-post.hbs
+---
+
+Open source projects are about the software, the users, and the community. Since
+becoming project lead in 2014, I've been privileged to be a part of the most
+passionate, diverse, and vibrant community in the ecosystem. The community is
+responsible for Node.js' meteoric rise and continued adoption by users and
+companies all over the world. Given the strength of its community, I'm confident
+that Node.js is heading in the right direction. With that said, it's time for me
+to step back.
+
+For the past year, I've worked directly with community members to improve
+Node.js, focusing on improving the parts of the project that benefit everyone.
+We wanted to know what in Node.js was working for them and what wasn't. During
+the life of a project, it's crucial to constantly reset yourself and not lose
+sight of your identity. Node.js is a small set of stable core modules, doing one
+thing, and one thing well. Every change we make, we tried to make sure we were
+being true to ourselves and not violating our ethos. We've focused on
+eliminating bugs and critical performance issues, as well as improving our
+workflows. Ultimately, our goal was to ensure Node.js was on the right path.
+
+The formation of the Node.js Foundation couldn't have happened at a better time
+in the life of Node.js. I believe this will be the tipping point that cements
+Node's place in technology. Soon, the foundation will be announcing its first
+meeting, initial membership, and future plans for Node.js. The project is on the
+right path, has the right contributors and is not tied to one person. It has a
+vibrant and loyal community supporting it.
+
+I want to take some time to highlight a few of those who have made an impact on
+Node.js. This list only scratches the surface, but these are a few of the unsung
+contributors that deserve some attention:
+
+Node.js wanted to have a [living breathing
+site](https://github.com/joyent/node-website), one that could attract our
+community and be the canonical source of documentation and tutorials for
+Node.js. Leading the charge has been [Robert
+Kowalski](https://github.com/robertkowalski) and [Wyatt
+Preul](https://github.com/geek), who have been incredibly helpful to the Node.js
+ecosystem in many ways, but most notably by helping breathe life in the website.
+
+One key point of the maturity for Node.js has been its growing predominance
+worldwide. Therefore, we've been working to improve our support for
+internationalization and localization. Node.js is so widely accepted that our
+users need Node.js to support internationalization so they can better support
+their own customers. Luckily, we have [Steven Loomis](https://github.com/srl295)
+leading the charge on this — he has the unique privilege of being a member of
+both ICU and Node.js.
+
+Node.js is seeing adoption across many new platforms, which means we need to
+collaborate with the community to support those platforms. Much like we have
+[Alexis Campilla](https://github.com/orangemocha) working to support the Windows
+platform, we have people like [Michael Dawson](https://github.com/mhdawson)
+working on adding support for PowerPC and zSeries. Additionally, he's been able
+to leverage the technical depth of IBM to help squash bugs and do work on our VM
+backend of V8.
+
+OpenSSL has had its share of issues recently, but it's not the only dependency
+that can be sensitive to upgrade -- so many thanks go to [James
+Snell](https://github.com/jasnell) for working to help simplify and manage those
+upgrades. James has also been working together with our large, diverse, and
+complex community to make sure our development policies are easy to understand
+and approachable for other new contributors.
+
+Finally, I want to make a very special mention of [Julien
+Gilli](https://github.com/misterdjules), who has been an incredible addition to
+the team. Julien has been responsible for the last few releases of Node.js —
+both the v0.10 and v0.12 branches. He's done wonders for the project, mostly
+behind the scenes, as he has spent tons of time working on shoring up our CI
+environment and the tests we run. Thanks to him, we were able to ship v0.12.0
+with all our tests passing and on all of our supported platforms. This was the
+first Node.js release ever to have that feature. He has also been working
+tirelessly to iterate on the process by which the team manages Node.js. Case in
+point is the excellent
+[documentation](https://nodejs.org/documentation/workflow/) he's put together
+describing how to manage the workflow of developing and contributing to the
+project.
+
+In short, hiring Julien to work full time on Node.js has been one of the best
+things for the project. His care and concern for Node.js, its users, and their
+combined future is evident in all of his actions. Node.js is incredibly lucky to
+have him at its core and I am truly indebted to him.
+
+It's because of this strong team, community, and the formation of the Foundation
+that it makes it the right time for me to step back. The foundation is here, the
+software is stable, and the contributors pushing it forward are people I have a
+lot of faith in. I can't wait to see just how far Node.js' star will rise. I am
+excited to see how the contributors grow, shape and deliver on the promise of
+Node.js, for themselves and for our users.
+
+Moving forward, I will still remain involved with Node.js and will provide as
+much help and support to the rest of the core team as they need. However, I
+won't have the time to participate at the level needed to remain a core
+contributor. With the core team and the community working together, I know they
+won't miss a step.
+
+
diff --git a/locale/uk/blog/community/node-leaders-building-open-neutral-foundation.md b/locale/uk/blog/community/node-leaders-building-open-neutral-foundation.md
new file mode 100755
index 0000000000000..fb27e9f3dcc51
--- /dev/null
+++ b/locale/uk/blog/community/node-leaders-building-open-neutral-foundation.md
@@ -0,0 +1,126 @@
+---
+title: Node.js and io.js leaders are building an open, neutral Node.js Foundation to support the future of the platform
+author: Mike Dolan
+date: 2015-05-15T23:50:46.000Z
+status: publish
+category: Community
+slug: node-leaders-are-building-an-open-foundation
+layout: blog-post.hbs
+---
+
+Just a couple months ago a variety of members of the Node.js and io.js
+community announced they would discuss establishing a neutral foundation for
+the community. The Linux Foundation has since been helping guide discussions
+with contributors, developers, users and leaders in these communities,
+increasingly expanding the scope of discussion to more stakeholders. Node.js
+and io.js have a long, complex history and the facilitated discussions have
+brought together key leaders to focus on what the future might mean for these
+technologies.
+
+A lot of progress has been made in just a few short months, and we're
+entering the final stages of discussions and decisions that will guide the
+projects forward. Most recently [the io.js TC voted to join in the
+Foundation](https://github.com/nodejs/node/issues/1705) effort and planning is
+already underway to begin the process of converging the codebases. The neutral
+organization, or foundation, will be a key element of that work and has been
+discussed at length by those involved. When a technology and community reach a
+level of maturity and adoption that outgrows one company or project, a
+foundation becomes a critical enabler for ongoing growth.
+
+Foundations can be used to support industrial-scale open source projects that
+require a legal entity to hold assets or conduct business (hiring, internship
+programs, compliance, licensing trademarks, marketing and event services,
+fundraising, etc). Ultimately foundations enable communities to participate in
+large scale collaboration under agreed upon terms that no one company, person
+or entity can change or dictate.
+
+It's important to note that while critical, an open governance model does not
+guarantee success or growth. The io.js project has a strong developer
+community, for example, but to grow further needs a  model to enable funding
+and investments in the project. If you haven't already, please [take a look
+at Mikeal Rogers blog post](https://medium.com/node-js-javascript/growing-up-27d6cc8b7c53).
+The Node.js community has needed an avenue for other companies
+to participate as equals in a neutral field. rowing a community and widening
+the adoption of a technology all takes resources and a governance model that
+serves everyone involved.  A foundation becomes the  place where participants
+can meet, agree on paths forward, ensure a neutral playing field in the
+community and invest resources to grow the community even more. It can also
+allow for broad community engagement through liberal contribution policies,
+community self organization and working groups.
+
+At The Linux Foundation, we've helped set up neutral organizations that
+support a variety of open source projects and communities through open and
+neutral governance and believe the future is bright for the Node.js and io.js
+communities. The technology being created has incredible value and expanding
+use cases,which is why getting the governance model and defining the role of
+the Foundation to support the developer community is the number one priority.
+
+While I'm a relative "newbie" to both the Node.js and io.js communities, I've
+been able to identify with our team at Linux Foundation a number of
+opportunities, as well as very common challenges in both communities that
+relate to other projects we've helped before. What we've found is the
+challenges the Node.js and io.js communities have are not unique; many open
+source projects struggle with the same challenges and many have been
+successful. As I've [previously written on
+Linux.com](https://www.linux.com/news/featured-blogs/205-mike-dolan/763051-five-key-features-of-a-project-designed-for-open-collaboration),
+there are five key features that we see in successful open governance:
+
+1. open participation
+2. open, transparent technical decision making
+3. open design and architecture
+4. an open source license
+5. an open, level playing field for intellectual property.
+
+I think these same features apply to the case for a foundation in the Node.js
+and io.js communities. The io.js project has certainly been founded on many of
+these principles and has taken off in terms of growing its developer
+community. Many in the io.js community joined because they felt these
+principles were not present elsewhere. For all of these reasons, we leveraged
+the governance provisions from io.js to [draft proposals for the technical
+community governance](https://github.com/joyent/nodejs-advisory-board/tree/master/governance-proposal).
+
+Now I'd like to share specific next steps for establishing the Node.js
+Foundation (all of this is of course subject to change based on input from the
+communities). We've started with a core group that offered advice on how to
+address key governance issues. We've expanded the circle to the technical
+committees of both communities and are now taking the discussion to the
+entirety of both communities.
+
+1. Draft technical governance documents are [up for review and
+comment](https://github.com/joyent/nodejs-advisory-board/tree/master/governance-proposal).
+
+2. The Foundation Bylaws and Membership Agreements based on our LF templates are
+available for companies to sign up as members. There is no need to sign any
+agreements as a community developer. If your company is interested in
+participating, [now is the time to sign
+up](http://f.cl.ly/items/0N1m3x0I3S2L203M1h1r/nodejs-foundation-membership-agreement-2015-march-04.pdf).
+
+3. Hold elections for the foundation's Gold and Silver member Board Directors and
+the Technical Steering Committee elects a TSC Chair. The process typically
+entails 1 week of nominations, 3-5 days of voting and then announcing the
+election winners.
+
+4. Set up an initial Board meeting, likely mid-June. The first Board meeting will
+put in place all of the key legal documents, policies, operations, etc that
+are being discussed (the reason for wrapping up edits on May 8).
+
+5. Initiate TSC meetings under the new foundation by upon resolution of both
+technical committees. The TSC will meet regularly on open, recorded calls.
+Details will be posted on a foundation wiki or page. The combined io.js and
+Node.js TCs have been meeting roughly every other week to work through the
+[Convergence planning](https://github.com/jasnell/dev-policy/blob/6601ca1cd2886f336ac65ddb3f67d3e741a021c9/convergence.md).
+
+6. May 25 - June 5: Announce the new foundation, members, initial Board Directors
+(elections may be pending), TSC members and any reconciliation plans agreed to
+by the TSC (if ready).
+
+And so I ask both communities to review the ideas being proposed, including
+how best to align goals, align resources and establish a platform for growing
+adoption of an amazing technology the development community working to build.
+I would like to thank the people building this future. Some you know; others
+you do not. It takes a lot of personal strength to voice opinions and stand up
+for new ideas in large communities. I appreciate the candor of the discussions
+but also ask you to seek out those putting forth ideas to understand them and
+to question them in a constructive dialogue. This community has another decade
+or more ahead of it; now is the time to set the right foundational elements to
+move forward.
diff --git a/locale/uk/blog/community/node-v5.md b/locale/uk/blog/community/node-v5.md
new file mode 100755
index 0000000000000..25df2f57ed11c
--- /dev/null
+++ b/locale/uk/blog/community/node-v5.md
@@ -0,0 +1,54 @@
+---
+title: What You Should Know about Node.js v5 and More
+date: 2015-10-30T12:00:00.000Z
+status: publish
+category: Community
+slug: node-v5
+layout: blog-post.hbs
+---
+
+## There’s Something New with Node.js Releases
+
+We just released [Node.js v5.0.0](https://nodejs.org/en/blog/release/v5.0.0/). You might be thinking to yourself: These folks just released [Node.js v4.2.1](https://nodejs.org/en/blog/release/v4.2.1/) “Argon,” under the new Long Term Support (LTS) plan, now I need to download this? The answer is yes and no.
+
+Node.js is growing, and growing fast. As we continue to innovate quickly, we will focus on two different release lines. One release line will fall under our **LTS** plan. All release lines that have LTS support will be even numbers, and (most importantly) focus on stability and security. These release lines are for organizations with complex environments that find it cumbersome to continually upgrade. We recently released the first in this line: [Node.js v4.2.1](https://nodejs.org/en/blog/release/v4.2.1/) “Argon.”
+
+The other release line is called **Current**. All release lines will be odd numbers, and have a shorter lifespan and more frequent updates to the code. The Current release line will focus on active development of necessary features and refinement of existing APIs. Node.js version 5 is this type of release.
+
+We want to make sure that you are adopting the release that best meets your Node.js needs, so to break it down:
+
+Stay on or upgrade to Node.js v4.2.x if you need stability and have a complex production environment, e.g. you are a medium or large enterprise.
+
+Upgrade to Node.js v5.x if you have the ability to upgrade versions quickly and easily without disturbing your environment.
+
+Now that you have the very basics, let’s take a deeper look at the new features and characteristics of v5, and the benefits and details of our LTS plan.
+
+## Introduction to Node.js v5
+
+[Node.js v5](https://nodejs.org/en/blog/release/v5.0.0/) is an intermediate feature release line that is best suited for users who have an easier time upgrading their Node.js installations, such as developers using the technology for front-end toolchains. This version will be supported for a maximum of only eight months and will be continually updated with new features and better performance; it is not supported under our LTS plan.
+
+The release cadence for v5.x will be more rapid than in the past. Expect a new release once every one to two weeks for v5.x. If upgrading is a challenge for you, we suggest you do not use this release. There will be significant ongoing development. The focus is on getting the releases to users as soon as possible.
+
+npm has been upgraded to v3 in Node.js v5.0.0, which (amongst other changes) will install dependencies as flat as possible in node_modules. v5.0.0 also comes with V8 4.6, which ships the [new.target](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/new.target) and [spread operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator) JavaScript language features. If you want to learn more about other technical details around this, please check out our [release post](https://nodejs.org/en/blog/release/v5.0.0/).
+
+It’s another top-quality release from us, and we are averaging roughly 50 unique contributors per month to the codebase. We are extremely excited with all the enthusiasm and amazing work that is going into this Node.js v5 and future releases.
+
+## What Is Long Term Support and Why Does It Matter to Me?
+
+First and foremost, if you haven’t read the [Essential Steps: Long Term Support (LTS) for Node.js by Rod Vagg](https://medium.com/@nodesource/essential-steps-long-term-support-for-node-js-8ecf7514dbd#.hi7hosy92), Technical Steering Committee Chairperson at the Node.js Foundation and the Chief Node Officer at NodeSource, do so. It’s a very helpful source for understanding our release cycle process. If you only have two minutes now, here is a quick summary:
+
+* The point of establishing an LTS plan for Node.js is to build on top of an existing stable release cycle by delivering new versions on a predictable schedule that have a clearly defined extended support lifecycle. It is an essential requirement for enterprise application development and operations teams. It also affects companies that provide professional support for Node.js.
+
+* As stated above, the first LTS release line is v4 “Argon," beginning at v4.2.0 and currently standing at v4.2.1. The next LTS release line will begin in 12 months around the first week of October 2016. All LTS release lines will begin at the same time each year.
+
+* All LTS release lines are assigned a “codename” drawn from the names of the elements on the Periodic Table.
+
+* The LTS release line will be actively maintained for a period of 18 months from the date the LTS release line begins. After 18 months have passed, it will transition into Maintenance mode.
+
+* There will be no more than two active LTS release lines at any given time. Overlap is intended to help ease migration planning.
+
+* Once a Current release line becomes LTS, no new features or breaking changes will be added to that release. Changes are limited to bug fixes for stability, security updates, possible npm updates, documentation updates and certain performance improvements that can be demonstrated to not break existing applications.
+
+## Questions?
+
+If you have any questions you can always connect with us on our [help](https://github.com/nodejs/help) repository. If you encounter an issue log or bug with Node.js v5, please report to our main code repository [here](https://github.com/nodejs/node/issues).
diff --git a/locale/uk/blog/community/transitions.md b/locale/uk/blog/community/transitions.md
new file mode 100755
index 0000000000000..a6803725bc2f3
--- /dev/null
+++ b/locale/uk/blog/community/transitions.md
@@ -0,0 +1,41 @@
+---
+title: Transitions
+author: Scott Hammond
+date: 2015-05-08T18:00:00.000Z
+status: publish
+category: Community
+slug: transitions
+layout: blog-post.hbs
+---
+
+In February, we announced the [Node.js
+Foundation](https://www.joyent.com/blog/introducing-the-nodejs-foundation),
+which will steward Node.js moving forward and open its future up to the
+community in a fashion that has not been available before. Organizations like
+IBM, SAP, Apigee, F5, Fidelity, Microsoft, PayPal, Red Hat, and others are
+sponsoring the Foundation, and they’re adding more contributors to the project.
+The mission of the Foundation is to accelerate the adoption of Node and ensure
+that the project is driven by the community under a transparent, open governance
+model.
+
+Under the aegis of the Foundation, the Node.js project is entering the next
+phase of maturity and adopting a model in which there is no BD or project lead.
+Instead, the technical direction of the project will be established by a
+technical steering committee run with an open governance model. There has been a
+lot of discussion on the dev policies and [governance
+model](https://github.com/joyent/nodejs-advisory-board/tree/master/governance-proposal)
+on Github.  As we move toward the Foundation model, the core team on Node.js is
+already adopting some of these policies [as shown
+here](https://github.com/joyent/node-website/pull/111).
+
+As we open a new chapter with the Foundation, we also close a remarkable chapter
+in Node.js, as TJ Fontaine will be stepping back from his post as Node.js
+Project Lead. TJ has come to be an integral member of our team, and his
+contributions will have long-lasting effects on the future of Node.js. Although
+he will not be as active, TJ will continue to act as a resource for helping the
+Node.js project as needed.
+
+I would like to thank TJ for his time and contributions to Node.js and to
+Joyent. I have witnessed firsthand the kind of impact he can have on a team, and
+his technical chops will be missed. As we take this next major step in the
+growth of Node.js, we wish TJ luck in his future endeavors.
diff --git a/locale/uk/blog/feature/index.md b/locale/uk/blog/feature/index.md
new file mode 100755
index 0000000000000..12d3702b0946e
--- /dev/null
+++ b/locale/uk/blog/feature/index.md
@@ -0,0 +1,6 @@
+---
+title: Features
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/feature/streams2.md b/locale/uk/blog/feature/streams2.md
new file mode 100755
index 0000000000000..b5cc6daf198a0
--- /dev/null
+++ b/locale/uk/blog/feature/streams2.md
@@ -0,0 +1,854 @@
+---
+title: A New Streaming API for Node v0.10
+author: Isaac Z. Schlueter
+date: 2012-12-21T00:45:13.000Z
+slug: streams2
+category: feature
+layout: blog-post.hbs
+---
+
+**tl;dr**
+
+* Node streams are great, except for all the ways in which they're
+  terrible.
+* A new Stream implementation is coming in 0.10, that has gotten the
+  nickname "streams2".
+* Readable streams have a `read()` method that returns a buffer or
+  null.  (More documentation included below.)
+* `'data'` events, `pause()`, and `resume()` will still work as before
+  (except that they'll actully work how you'd expect).
+* Old programs will **almost always** work without modification, but
+  streams start out in a paused state, and need to be read from to be
+  consumed.
+* **WARNING**: If you never add a `'data'` event handler, or call
+  `resume()`, then it'll sit in a paused state forever and never
+  emit `'end'`.
+
+-------
+
+Throughout the life of Node, we've been gradually iterating on the
+ideal event-based API for handling data.  Over time, this developed
+into the "Stream" interface that you see throughout Node's core
+modules and many of the modules in npm.
+
+Consistent interfaces increase the portability and reliability of our
+programs and libraries.  Overall, the move from domain-specific events
+and methods towards a unified stream interface was a huge win.
+However, there are still several problems with Node's streams as of
+v0.8.  In a nutshell:
+
+1. The `pause()` method doesn't pause.  It is advisory-only.  In
+   Node's implementation, this makes things much simpler, but it's
+   confusing to users, and doesn't do what it looks like it does.
+2. `'data'` events come right away (whether you're ready or not).
+   This makes it unreasonably difficult to do common tasks like load a
+   user's session before deciding how to handle their request.
+3. There is no way to consume a specific number of bytes, and then
+   leave the rest for some other part of the program to deal with.
+4. It's unreasonably difficult to implement streams and get all the
+   intricacies of pause, resume, write-buffering, and data events
+   correct.  The lack of shared classes mean that we all have to solve
+   the same problems repeatedly, making similar mistakes and similar
+   bugs.
+
+Common simple tasks should be easy, or we aren't doing our job.
+People often say that Node is better than most other platforms at this
+stuff, but in my opinion, that is less of a compliment and more of an
+indictment of the current state of software.  Being better than the
+next guy isn't enough; we have to be the best imaginable.  While they
+were a big step in the right direction, the Streams in Node up until
+now leave a lot wanting.
+
+So, just fix it, right?
+
+Well, we are sitting on the results of several years of explosive
+growth in the Node community, so any changes have to be made very
+carefully.  If we break all the Node programs in 0.10, then no one
+will ever want to upgrade to 0.10, and it's all pointless.  We had
+this conversation around 0.4, then again around 0.6, then again around
+0.8.  Every time, the conclusion has been "Too much work, too hard to
+make backwards-compatible", and we always had more pressing problems
+to solve.
+
+In 0.10, we cannot put it off any longer.  We've bitten the bullet and
+are making a significant change to the Stream implementation.  You may
+have seen conversations on twitter or IRC or the mailing list about
+"streams2".  I also gave [a talk in
+November](https://dl.dropbox.com/u/3685/presentations/streams2/streams2-ko.pdf)
+about this subject.  A lot of node module authors have been involved
+with the development of streams2 (and of course the node core team).
+
+## streams2
+
+The feature is described pretty thoroughly in the documentation, so
+I'm including it below.  Please read it, especially the section on
+"compatibility".  There's a caveat there that is unfortunately
+unavoidable, but hopefully enough of an edge case that it's easily
+worked around.
+
+The first preview release with this change will be 0.9.4.  I highly
+recommend trying this release and providing feedback before it lands
+in a stable version.
+
+As of writing this post, there are some known performance regressions,
+especially in the http module.  We are fanatical about maintaining
+performance in Node.js, so of course this will have to be fixed before
+the v0.10 stable release.  (Watch for a future blog post on the tools
+and techniques that have been useful in tracking down these issues.)
+
+There may be minor changes as necessary to fix bugs and improve
+performance, but the API at this point should be considered feature
+complete.  It correctly does all the things we need it to do, it just
+doesn't do them quite well enough yet.  As always, be wary of running
+unstable releases in production, of course, but I encourage you to try
+it out and see what you think.  Especially, if you have tests that you
+can run on your modules and libraries, that would be extremely useful
+feedback.
+
+--------
+
+# Stream
+
+    Stability: 2 - Unstable
+
+A stream is an abstract interface implemented by various objects in
+Node.  For example a request to an HTTP server is a stream, as is
+stdout. Streams are readable, writable, or both. All streams are
+instances of [EventEmitter][]
+
+You can load the Stream base classes by doing `require('stream')`.
+There are base classes provided for Readable streams, Writable
+streams, Duplex streams, and Transform streams.
+
+## Compatibility
+
+In earlier versions of Node, the Readable stream interface was
+simpler, but also less powerful and less useful.
+
+* Rather than waiting for you to call the `read()` method, `'data'`
+  events would start emitting immediately.  If you needed to do some
+  I/O to decide how to handle data, then you had to store the chunks
+  in some kind of buffer so that they would not be lost.
+* The `pause()` method was advisory, rather than guaranteed.  This
+  meant that you still had to be prepared to receive `'data'` events
+  even when the stream was in a paused state.
+
+In Node v0.10, the Readable class described below was added.  For
+backwards compatibility with older Node programs, Readable streams
+switch into "old mode" when a `'data'` event handler is added, or when
+the `pause()` or `resume()` methods are called.  The effect is that,
+even if you are not using the new `read()` method and `'readable'`
+event, you no longer have to worry about losing `'data'` chunks.
+
+Most programs will continue to function normally.  However, this
+introduces an edge case in the following conditions:
+
+* No `'data'` event handler is added.
+* The `pause()` and `resume()` methods are never called.
+
+For example, consider the following code:
+
+```javascript
+// WARNING!  BROKEN!
+net.createServer(function(socket) {
+
+  // we add an 'end' method, but never consume the data
+  socket.on('end', function() {
+    // It will never get here.
+    socket.end('I got your message (but didnt read it)\n');
+  });
+
+}).listen(1337);
+```
+
+In versions of node prior to v0.10, the incoming message data would be
+simply discarded.  However, in Node v0.10 and beyond, the socket will
+remain paused forever.
+
+The workaround in this situation is to call the `resume()` method to
+trigger "old mode" behavior:
+
+```javascript
+// Workaround
+net.createServer(function(socket) {
+
+  socket.on('end', function() {
+    socket.end('I got your message (but didnt read it)\n');
+  });
+
+  // start the flow of data, discarding it.
+  socket.resume();
+
+}).listen(1337);
+```
+
+In addition to new Readable streams switching into old-mode, pre-v0.10
+style streams can be wrapped in a Readable class using the `wrap()`
+method.
+
+## Class: stream.Readable
+
+<!--type=class-->
+
+A `Readable Stream` has the following methods, members, and events.
+
+Note that `stream.Readable` is an abstract class designed to be
+extended with an underlying implementation of the `_read(size)`
+method. (See below.)
+
+### new stream.Readable([options])
+
+* `options` {Object}
+  * `highWaterMark` {Number} The maximum number of bytes to store in
+    the internal buffer before ceasing to read from the underlying
+    resource.  Default=16kb
+  * `encoding` {String} If specified, then buffers will be decoded to
+    strings using the specified encoding.  Default=null
+  * `objectMode` {Boolean} Whether this stream should behave
+    as a stream of objects. Meaning that stream.read(n) returns
+    a single value instead of a Buffer of size n
+
+In classes that extend the Readable class, make sure to call the
+constructor so that the buffering settings can be properly
+initialized.
+
+### readable.\_read(size)
+
+* `size` {Number} Number of bytes to read asynchronously
+
+Note: **This function should NOT be called directly.**  It should be
+implemented by child classes, and called by the internal Readable
+class methods only.
+
+All Readable stream implementations must provide a `_read` method
+to fetch data from the underlying resource.
+
+This method is prefixed with an underscore because it is internal to
+the class that defines it, and should not be called directly by user
+programs.  However, you **are** expected to override this method in
+your own extension classes.
+
+When data is available, put it into the read queue by calling
+`readable.push(chunk)`.  If `push` returns false, then you should stop
+reading.  When `_read` is called again, you should start pushing more
+data.
+
+The `size` argument is advisory.  Implementations where a "read" is a
+single call that returns data can use this to know how much data to
+fetch.  Implementations where that is not relevant, such as TCP or
+TLS, may ignore this argument, and simply provide data whenever it
+becomes available.  There is no need, for example to "wait" until
+`size` bytes are available before calling `stream.push(chunk)`.
+
+### readable.push(chunk)
+
+* `chunk` {Buffer | null | String} Chunk of data to push into the read queue
+* return {Boolean} Whether or not more pushes should be performed
+
+Note: **This function should be called by Readable implementors, NOT
+by consumers of Readable subclasses.**  The `_read()` function will not
+be called again until at least one `push(chunk)` call is made.  If no
+data is available, then you MAY call `push('')` (an empty string) to
+allow a future `_read` call, without adding any data to the queue.
+
+The `Readable` class works by putting data into a read queue to be
+pulled out later by calling the `read()` method when the `'readable'`
+event fires.
+
+The `push()` method will explicitly insert some data into the read
+queue.  If it is called with `null` then it will signal the end of the
+data.
+
+In some cases, you may be wrapping a lower-level source which has some
+sort of pause/resume mechanism, and a data callback.  In those cases,
+you could wrap the low-level source object by doing something like
+this:
+
+```javascript
+// source is an object with readStop() and readStart() methods,
+// and an `ondata` member that gets called when it has data, and
+// an `onend` member that gets called when the data is over.
+
+var stream = new Readable();
+
+source.ondata = function(chunk) {
+  // if push() returns false, then we need to stop reading from source
+  if (!stream.push(chunk))
+    source.readStop();
+};
+
+source.onend = function() {
+  stream.push(null);
+};
+
+// _read will be called when the stream wants to pull more data in
+// the advisory size argument is ignored in this case.
+stream._read = function(n) {
+  source.readStart();
+};
+```
+
+### readable.unshift(chunk)
+
+* `chunk` {Buffer | null | String} Chunk of data to unshift onto the read queue
+* return {Boolean} Whether or not more pushes should be performed
+
+This is the corollary of `readable.push(chunk)`.  Rather than putting
+the data at the *end* of the read queue, it puts it at the *front* of
+the read queue.
+
+This is useful in certain use-cases where a stream is being consumed
+by a parser, which needs to "un-consume" some data that it has
+optimistically pulled out of the source.
+
+```javascript
+// A parser for a simple data protocol.
+// The "header" is a JSON object, followed by 2 \n characters, and
+// then a message body.
+//
+// Note: This can be done more simply as a Transform stream.  See below.
+
+function SimpleProtocol(source, options) {
+  if (!(this instanceof SimpleProtocol))
+    return new SimpleProtocol(options);
+
+  Readable.call(this, options);
+  this._inBody = false;
+  this._sawFirstCr = false;
+
+  // source is a readable stream, such as a socket or file
+  this._source = source;
+
+  var self = this;
+  source.on('end', function() {
+    self.push(null);
+  });
+
+  // give it a kick whenever the source is readable
+  // read(0) will not consume any bytes
+  source.on('readable', function() {
+    self.read(0);
+  });
+
+  this._rawHeader = [];
+  this.header = null;
+}
+
+SimpleProtocol.prototype = Object.create(
+  Readable.prototype, { constructor: { value: SimpleProtocol }});
+
+SimpleProtocol.prototype._read = function(n) {
+  if (!this._inBody) {
+    var chunk = this._source.read();
+
+    // if the source doesn't have data, we don't have data yet.
+    if (chunk === null)
+      return this.push('');
+
+    // check if the chunk has a \n\n
+    var split = -1;
+    for (var i = 0; i < chunk.length; i++) {
+      if (chunk[i] === 10) { // '\n'
+        if (this._sawFirstCr) {
+          split = i;
+          break;
+        } else {
+          this._sawFirstCr = true;
+        }
+      } else {
+        this._sawFirstCr = false;
+      }
+    }
+
+    if (split === -1) {
+      // still waiting for the \n\n
+      // stash the chunk, and try again.
+      this._rawHeader.push(chunk);
+      this.push('');
+    } else {
+      this._inBody = true;
+      var h = chunk.slice(0, split);
+      this._rawHeader.push(h);
+      var header = Buffer.concat(this._rawHeader).toString();
+      try {
+        this.header = JSON.parse(header);
+      } catch (er) {
+        this.emit('error', new Error('invalid simple protocol data'));
+        return;
+      }
+      // now, because we got some extra data, unshift the rest
+      // back into the read queue so that our consumer will see it.
+      var b = chunk.slice(split);
+      this.unshift(b);
+
+      // and let them know that we are done parsing the header.
+      this.emit('header', this.header);
+    }
+  } else {
+    // from there on, just provide the data to our consumer.
+    // careful not to push(null), since that would indicate EOF.
+    var chunk = this._source.read();
+    if (chunk) this.push(chunk);
+  }
+};
+
+// Usage:
+var parser = new SimpleProtocol(source);
+// Now parser is a readable stream that will emit 'header'
+// with the parsed header data.
+```
+
+### readable.wrap(stream)
+
+* `stream` {Stream} An "old style" readable stream
+
+If you are using an older Node library that emits `'data'` events and
+has a `pause()` method that is advisory only, then you can use the
+`wrap()` method to create a Readable stream that uses the old stream
+as its data source.
+
+For example:
+
+```javascript
+var OldReader = require('./old-api-module.js').OldReader;
+var oreader = new OldReader;
+var Readable = require('stream').Readable;
+var myReader = new Readable().wrap(oreader);
+
+myReader.on('readable', function() {
+  myReader.read(); // etc.
+});
+```
+
+### Event: 'readable'
+
+When there is data ready to be consumed, this event will fire.
+
+When this event emits, call the `read()` method to consume the data.
+
+### Event: 'end'
+
+Emitted when the stream has received an EOF (FIN in TCP terminology).
+Indicates that no more `'data'` events will happen. If the stream is
+also writable, it may be possible to continue writing.
+
+### Event: 'data'
+
+The `'data'` event emits either a `Buffer` (by default) or a string if
+`setEncoding()` was used.
+
+Note that adding a `'data'` event listener will switch the Readable
+stream into "old mode", where data is emitted as soon as it is
+available, rather than waiting for you to call `read()` to consume it.
+
+### Event: 'error'
+
+Emitted if there was an error receiving data.
+
+### Event: 'close'
+
+Emitted when the underlying resource (for example, the backing file
+descriptor) has been closed. Not all streams will emit this.
+
+### readable.setEncoding(encoding)
+
+Makes the `'data'` event emit a string instead of a `Buffer`. `encoding`
+can be `'utf8'`, `'utf16le'` (`'ucs2'`), `'ascii'`, or `'hex'`.
+
+The encoding can also be set by specifying an `encoding` field to the
+constructor.
+
+### readable.read([size])
+
+* `size` {Number | null} Optional number of bytes to read.
+* Return: {Buffer | String | null}
+
+Note: **This function SHOULD be called by Readable stream users.**
+
+Call this method to consume data once the `'readable'` event is
+emitted.
+
+The `size` argument will set a minimum number of bytes that you are
+interested in.  If not set, then the entire content of the internal
+buffer is returned.
+
+If there is no data to consume, or if there are fewer bytes in the
+internal buffer than the `size` argument, then `null` is returned, and
+a future `'readable'` event will be emitted when more is available.
+
+Calling `stream.read(0)` will always return `null`, and will trigger a
+refresh of the internal buffer, but otherwise be a no-op.
+
+### readable.pipe(destination, [options])
+
+* `destination` {Writable Stream}
+* `options` {Object} Optional
+  * `end` {Boolean} Default=true
+
+Connects this readable stream to `destination` WriteStream. Incoming
+data on this stream gets written to `destination`.  Properly manages
+back-pressure so that a slow destination will not be overwhelmed by a
+fast readable stream.
+
+This function returns the `destination` stream.
+
+For example, emulating the Unix `cat` command:
+
+    process.stdin.pipe(process.stdout);
+
+By default `end()` is called on the destination when the source stream
+emits `end`, so that `destination` is no longer writable. Pass `{ end:
+false }` as `options` to keep the destination stream open.
+
+This keeps `writer` open so that "Goodbye" can be written at the
+end.
+
+    reader.pipe(writer, { end: false });
+    reader.on("end", function() {
+      writer.end("Goodbye\n");
+    });
+
+Note that `process.stderr` and `process.stdout` are never closed until
+the process exits, regardless of the specified options.
+
+### readable.unpipe([destination])
+
+* `destination` {Writable Stream} Optional
+
+Undo a previously established `pipe()`.  If no destination is
+provided, then all previously established pipes are removed.
+
+### readable.pause()
+
+Switches the readable stream into "old mode", where data is emitted
+using a `'data'` event rather than being buffered for consumption via
+the `read()` method.
+
+Ceases the flow of data.  No `'data'` events are emitted while the
+stream is in a paused state.
+
+### readable.resume()
+
+Switches the readable stream into "old mode", where data is emitted
+using a `'data'` event rather than being buffered for consumption via
+the `read()` method.
+
+Resumes the incoming `'data'` events after a `pause()`.
+
+
+## Class: stream.Writable
+
+<!--type=class-->
+
+A `Writable` Stream has the following methods, members, and events.
+
+Note that `stream.Writable` is an abstract class designed to be
+extended with an underlying implementation of the
+`_write(chunk, encoding, cb)` method. (See below.)
+
+### new stream.Writable([options])
+
+* `options` {Object}
+  * `highWaterMark` {Number} Buffer level when `write()` starts
+    returning false. Default=16kb
+  * `decodeStrings` {Boolean} Whether or not to decode strings into
+    Buffers before passing them to `_write()`.  Default=true
+
+In classes that extend the Writable class, make sure to call the
+constructor so that the buffering settings can be properly
+initialized.
+
+### writable.\_write(chunk, encoding, callback)
+
+* `chunk` {Buffer | String} The chunk to be written.  Will always
+  be a buffer unless the `decodeStrings` option was set to `false`.
+* `encoding` {String} If the chunk is a string, then this is the
+  encoding type.  Ignore chunk is a buffer.  Note that chunk will
+  **always** be a buffer unless the `decodeStrings` option is
+  explicitly set to `false`.
+* `callback` {Function} Call this function (optionally with an error
+  argument) when you are done processing the supplied chunk.
+
+All Writable stream implementations must provide a `_write` method to
+send data to the underlying resource.
+
+Note: **This function MUST NOT be called directly.**  It should be
+implemented by child classes, and called by the internal Writable
+class methods only.
+
+Call the callback using the standard `callback(error)` pattern to
+signal that the write completed successfully or with an error.
+
+If the `decodeStrings` flag is set in the constructor options, then
+`chunk` may be a string rather than a Buffer, and `encoding` will
+indicate the sort of string that it is.  This is to support
+implementations that have an optimized handling for certain string
+data encodings.  If you do not explicitly set the `decodeStrings`
+option to `false`, then you can safely ignore the `encoding` argument,
+and assume that `chunk` will always be a Buffer.
+
+This method is prefixed with an underscore because it is internal to
+the class that defines it, and should not be called directly by user
+programs.  However, you **are** expected to override this method in
+your own extension classes.
+
+
+### writable.write(chunk, [encoding], [callback])
+
+* `chunk` {Buffer | String} Data to be written
+* `encoding` {String} Optional.  If `chunk` is a string, then encoding
+  defaults to `'utf8'`
+* `callback` {Function} Optional.  Called when this chunk is
+  successfully written.
+* Returns {Boolean}
+
+Writes `chunk` to the stream.  Returns `true` if the data has been
+flushed to the underlying resource.  Returns `false` to indicate that
+the buffer is full, and the data will be sent out in the future. The
+`'drain'` event will indicate when the buffer is empty again.
+
+The specifics of when `write()` will return false, is determined by
+the `highWaterMark` option provided to the constructor.
+
+### writable.end([chunk], [encoding], [callback])
+
+* `chunk` {Buffer | String} Optional final data to be written
+* `encoding` {String} Optional.  If `chunk` is a string, then encoding
+  defaults to `'utf8'`
+* `callback` {Function} Optional.  Called when the final chunk is
+  successfully written.
+
+Call this method to signal the end of the data being written to the
+stream.
+
+### Event: 'drain'
+
+Emitted when the stream's write queue empties and it's safe to write
+without buffering again. Listen for it when `stream.write()` returns
+`false`.
+
+### Event: 'close'
+
+Emitted when the underlying resource (for example, the backing file
+descriptor) has been closed. Not all streams will emit this.
+
+### Event: 'finish'
+
+When `end()` is called and there are no more chunks to write, this
+event is emitted.
+
+### Event: 'pipe'
+
+* `source` {Readable Stream}
+
+Emitted when the stream is passed to a readable stream's pipe method.
+
+### Event 'unpipe'
+
+* `source` {Readable Stream}
+
+Emitted when a previously established `pipe()` is removed using the
+source Readable stream's `unpipe()` method.
+
+## Class: stream.Duplex
+
+<!--type=class-->
+
+A "duplex" stream is one that is both Readable and Writable, such as a
+TCP socket connection.
+
+Note that `stream.Duplex` is an abstract class designed to be
+extended with an underlying implementation of the `_read(size)`
+and `_write(chunk, encoding, callback)` methods as you would with a Readable or
+Writable stream class.
+
+Since JavaScript doesn't have multiple prototypal inheritance, this
+class prototypally inherits from Readable, and then parasitically from
+Writable.  It is thus up to the user to implement both the lowlevel
+`_read(n)` method as well as the lowlevel `_write(chunk, encoding, cb)` method
+on extension duplex classes.
+
+### new stream.Duplex(options)
+
+* `options` {Object} Passed to both Writable and Readable
+  constructors. Also has the following fields:
+  * `allowHalfOpen` {Boolean} Default=true.  If set to `false`, then
+    the stream will automatically end the readable side when the
+    writable side ends and vice versa.
+
+In classes that extend the Duplex class, make sure to call the
+constructor so that the buffering settings can be properly
+initialized.
+
+## Class: stream.Transform
+
+A "transform" stream is a duplex stream where the output is causally
+connected in some way to the input, such as a zlib stream or a crypto
+stream.
+
+There is no requirement that the output be the same size as the input,
+the same number of chunks, or arrive at the same time.  For example, a
+Hash stream will only ever have a single chunk of output which is
+provided when the input is ended.  A zlib stream will either produce
+much smaller or much larger than its input.
+
+Rather than implement the `_read()` and `_write()` methods, Transform
+classes must implement the `_transform()` method, and may optionally
+also implement the `_flush()` method.  (See below.)
+
+### new stream.Transform([options])
+
+* `options` {Object} Passed to both Writable and Readable
+  constructors.
+
+In classes that extend the Transform class, make sure to call the
+constructor so that the buffering settings can be properly
+initialized.
+
+### transform.\_transform(chunk, encoding, callback)
+
+* `chunk` {Buffer | String} The chunk to be transformed.  Will always
+  be a buffer unless the `decodeStrings` option was set to `false`.
+* `encoding` {String} If the chunk is a string, then this is the
+  encoding type.  (Ignore if `decodeStrings` chunk is a buffer.)
+* `callback` {Function} Call this function (optionally with an error
+  argument) when you are done processing the supplied chunk.
+
+Note: **This function MUST NOT be called directly.**  It should be
+implemented by child classes, and called by the internal Transform
+class methods only.
+
+All Transform stream implementations must provide a `_transform`
+method to accept input and produce output.
+
+`_transform` should do whatever has to be done in this specific
+Transform class, to handle the bytes being written, and pass them off
+to the readable portion of the interface.  Do asynchronous I/O,
+process things, and so on.
+
+Call `transform.push(outputChunk)` 0 or more times to generate output
+from this input chunk, depending on how much data you want to output
+as a result of this chunk.
+
+Call the callback function only when the current chunk is completely
+consumed.  Note that there may or may not be output as a result of any
+particular input chunk.
+
+This method is prefixed with an underscore because it is internal to
+the class that defines it, and should not be called directly by user
+programs.  However, you **are** expected to override this method in
+your own extension classes.
+
+### transform.\_flush(callback)
+
+* `callback` {Function} Call this function (optionally with an error
+  argument) when you are done flushing any remaining data.
+
+Note: **This function MUST NOT be called directly.**  It MAY be implemented
+by child classes, and if so, will be called by the internal Transform
+class methods only.
+
+In some cases, your transform operation may need to emit a bit more
+data at the end of the stream.  For example, a `Zlib` compression
+stream will store up some internal state so that it can optimally
+compress the output.  At the end, however, it needs to do the best it
+can with what is left, so that the data will be complete.
+
+In those cases, you can implement a `_flush` method, which will be
+called at the very end, after all the written data is consumed, but
+before emitting `end` to signal the end of the readable side.  Just
+like with `_transform`, call `transform.push(chunk)` zero or more
+times, as appropriate, and call `callback` when the flush operation is
+complete.
+
+This method is prefixed with an underscore because it is internal to
+the class that defines it, and should not be called directly by user
+programs.  However, you **are** expected to override this method in
+your own extension classes.
+
+### Example: `SimpleProtocol` parser
+
+The example above of a simple protocol parser can be implemented much
+more simply by using the higher level `Transform` stream class.
+
+In this example, rather than providing the input as an argument, it
+would be piped into the parser, which is a more idiomatic Node stream
+approach.
+
+```javascript
+function SimpleProtocol(options) {
+  if (!(this instanceof SimpleProtocol))
+    return new SimpleProtocol(options);
+
+  Transform.call(this, options);
+  this._inBody = false;
+  this._sawFirstCr = false;
+  this._rawHeader = [];
+  this.header = null;
+}
+
+SimpleProtocol.prototype = Object.create(
+  Transform.prototype, { constructor: { value: SimpleProtocol }});
+
+SimpleProtocol.prototype._transform = function(chunk, encoding, done) {
+  if (!this._inBody) {
+    // check if the chunk has a \n\n
+    var split = -1;
+    for (var i = 0; i < chunk.length; i++) {
+      if (chunk[i] === 10) { // '\n'
+        if (this._sawFirstCr) {
+          split = i;
+          break;
+        } else {
+          this._sawFirstCr = true;
+        }
+      } else {
+        this._sawFirstCr = false;
+      }
+    }
+
+    if (split === -1) {
+      // still waiting for the \n\n
+      // stash the chunk, and try again.
+      this._rawHeader.push(chunk);
+    } else {
+      this._inBody = true;
+      var h = chunk.slice(0, split);
+      this._rawHeader.push(h);
+      var header = Buffer.concat(this._rawHeader).toString();
+      try {
+        this.header = JSON.parse(header);
+      } catch (er) {
+        this.emit('error', new Error('invalid simple protocol data'));
+        return;
+      }
+      // and let them know that we are done parsing the header.
+      this.emit('header', this.header);
+
+      // now, because we got some extra data, emit this first.
+      this.push(b);
+    }
+  } else {
+    // from there on, just provide the data to our consumer as-is.
+    this.push(b);
+  }
+  done();
+};
+
+var parser = new SimpleProtocol();
+source.pipe(parser)
+
+// Now parser is a readable stream that will emit 'header'
+// with the parsed header data.
+```
+
+
+## Class: stream.PassThrough
+
+This is a trivial implementation of a `Transform` stream that simply
+passes the input bytes across to the output.  Its purpose is mainly
+for examples and testing, but there are occasionally use cases where
+it can come in handy.
+
+
+[EventEmitter]: https://nodejs.org/api/events.html#events_class_eventemitter
diff --git a/locale/uk/blog/index.md b/locale/uk/blog/index.md
new file mode 100755
index 0000000000000..24248de1867d0
--- /dev/null
+++ b/locale/uk/blog/index.md
@@ -0,0 +1,4 @@
+---
+layout: blog-index.hbs
+paginate: blog
+---
diff --git a/locale/uk/blog/module/index.md b/locale/uk/blog/module/index.md
new file mode 100755
index 0000000000000..613857450ea6d
--- /dev/null
+++ b/locale/uk/blog/module/index.md
@@ -0,0 +1,6 @@
+---
+title: Modules
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/module/multi-server-continuous-deployment-with-fleet.md b/locale/uk/blog/module/multi-server-continuous-deployment-with-fleet.md
new file mode 100755
index 0000000000000..5614bc10a8849
--- /dev/null
+++ b/locale/uk/blog/module/multi-server-continuous-deployment-with-fleet.md
@@ -0,0 +1,92 @@
+---
+title: multi-server continuous deployment with fleet 
+author: Isaac Schlueter
+date: 2012-05-02T18:00:00.000Z
+status: publish
+category: module
+slug: multi-server-continuous-deployment-with-fleet
+layout: blog-post.hbs
+---
+
+<p><img style="float:right;margin-left:1.2em;" alt="substack" src="http://substack.net/images/substackistan.png"><i>This is a guest post by James "SubStack" Halliday, originally posted <a href="http://substack.net/posts/16a9d8/multi-server-continuous-deployment-with-fleet">on his blog</a>, and reposted here with permission.</i></p>
+
+<p>Writing applications as a sequence of tiny services that all talk to each other over the network has many upsides, but it can be annoyingly tedious to get all the subsystems up and running. </p>
+
+<p>Running a <a href="http://substack.net/posts/7a1c42">seaport</a> can help with getting all the services to talk to each other, but running the processes is another matter, especially when you have new code to push into production. </p>
+
+<p><a href="http://github.com/substack/fleet">fleet</a> aims to make it really easy for anyone on your team to push new code from git to an armada of servers and manage all the processes in your stack. </p>
+
+<p>To start using fleet, just install the fleet command with <a href="https://npmjs.com">npm</a>: </p>
+
+<pre style="">npm install -g fleet </pre>
+
+<p>Then on one of your servers, start a fleet hub. From a fresh directory, give it a passphrase and a port to listen on: </p>
+
+<pre style="">fleet hub --port=7000 --secret=beepboop </pre>
+
+<p>Now fleet is listening on :7000 for commands and has started a git server on :7001 over http. There's no ssh keys or post commit hooks to configure, just run that command and you're ready to go! </p>
+
+<p>Next set up some worker drones to run your processes. You can have as many workers as you like on a single server but each worker should be run from a separate directory. Just do: </p>
+
+<pre style="">fleet drone --hub=x.x.x.x:7000 --secret=beepboop </pre>
+
+<p>where <span class="code">x.x.x.x</span> is the address where the fleet hub is running. Spin up a few of these drones. </p>
+
+<p>Now navigate to the directory of the app you want to deploy. First set a remote so you don't need to type <span class="code">--hub</span> and <span class="code">--secret</span> all the time. </p>
+
+<pre style="">fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop </pre>
+
+<p>Fleet just created a <span class="code">fleet.json</span> file for you to save your settings. </p>
+
+<p>From the same app directory, to deploy your code just do: </p>
+
+<pre style="">fleet deploy </pre>
+
+<p>The deploy command does a <span class="code">git push</span> to the fleet hub's git http server and then the hub instructs all the drones to pull from it. Your code gets checked out into a new directory on all the fleet drones every time you deploy. </p>
+
+<p>Because fleet is designed specifically for managing applications with lots of tiny services, the deploy command isn't tied to running any processes. Starting processes is up to the programmer but it's super simple. Just use the <span class="code">fleet spawn</span> command: </p>
+
+<pre style="">fleet spawn -- node server.js 8080 </pre>
+
+<p>By default fleet picks a drone at random to run the process on. You can specify which drone you want to run a particular process on with the <span class="code">--drone</span> switch if it matters. </p>
+
+<p>Start a few processes across all your worker drones and then show what is running with the <span class="code">fleet ps</span> command: </p>
+
+<pre style="">fleet ps
+drone#3dfe17b8
+├─┬ pid#1e99f4
+│ ├── status:   running
+│ ├── commit:   webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5
+│ └── command:  node server.js 8888
+└─┬ pid#d7048a
+  ├── status:   running
+  ├── commit:   webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5
+  └── command:  node server.js 8889</pre>
+
+<p>Now suppose that you have new code to push out into production. By default, fleet lets you spin up new services without disturbing your existing services. If you <span class="code">fleet deploy</span> again after checking in some new changes to git, the next time you <span class="code">fleet spawn</span> a new process, that process will be spun up in a completely new directory based on the git commit hash. To stop a process, just use <span class="code">fleet stop</span>. </p>
+
+<p>This approach lets you verify that the new services work before bringing down the old services. You can even start experimenting with heterogeneous and incremental deployment by hooking into a custom <a href="http://substack.net/posts/5bd18d">http proxy</a>! </p>
+
+<p>Even better, if you use a service registry like  <a href="http://substack.net/posts/7a1c42">seaport</a> for managing the host/port tables, you can spin up new ad-hoc staging clusters all the time without disrupting the normal operation of your site before rolling out new code to users. </p>
+
+<p>Fleet has many more commands that you can learn about with its git-style manpage-based help system! Just do <span class="code">fleet help</span> to get a list of all the commands you can run. </p>
+
+<pre style="">fleet help
+Usage: fleet &lt;command&gt; [&lt;args&gt;]
+
+The commands are:
+  deploy   Push code to drones.
+  drone    Connect to a hub as a worker.
+  exec     Run commands on drones.
+  hub      Create a hub for drones to connect.
+  monitor  Show service events system-wide.
+  ps       List the running processes on the drones.
+  remote   Manage the set of remote hubs.
+  spawn    Run services on drones.
+  stop     Stop processes running on drones.
+
+For help about a command, try `fleet help `.</pre>
+
+<p><span class="code">npm install -g fleet</span> and <a href="https://github.com/substack/fleet">check out the code on github</a>! </p>
+
+<img src="http://substack.net/images/fleet.png" width="849" height="568">
diff --git a/locale/uk/blog/module/service-logging-in-json-with-bunyan.md b/locale/uk/blog/module/service-logging-in-json-with-bunyan.md
new file mode 100755
index 0000000000000..2fd602a139f7f
--- /dev/null
+++ b/locale/uk/blog/module/service-logging-in-json-with-bunyan.md
@@ -0,0 +1,340 @@
+---
+title: Service logging in JSON with Bunyan
+author: trentmick
+date: 2012-03-28T19:25:26.000Z
+status: publish
+category: module
+slug: service-logging-in-json-with-bunyan
+layout: blog-post.hbs
+---
+
+<div style="float:right;margin:0 0 15px 15px;">
+<img class="alignnone size-full wp-image-469" title="Bunyan" src="https://nodeblog.files.wordpress.com/2012/03/bunyan.png" alt="Paul Bunyan and Babe the Blue Ox" width="240" height="320" /><br />
+<a href="http://www.flickr.com/photos/stublag/2876034487">Photo by Paul Carroll</a>
+</div>
+
+<p>Service logs are gold, if you can mine them. We scan them for occasional debugging. Perhaps we grep them looking for errors or warnings, or setup an occasional nagios log regex monitor. If that. This is a waste of the best channel for data about a service.</p>
+
+<p><a href="https://www.youtube.com/watch?v=01-2pNCZiNk">"Log. (Huh) What is it good for. Absolutely ..."</a></p>
+
+<ul>
+<li>debugging</li>
+<li>monitors tools that alert operators</li>
+<li>non real-time analysis (business or operational analysis)</li>
+<li>historical analysis</li>
+</ul>
+
+<p>These are what logs are good for. The current state of logging is barely adequate for the first of these. Doing reliable analysis, and even monitoring, of varied <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">"printf-style" logs</a> is a grueling or hacky task that most either don't bother with, fallback to paying someone else to do (viz. Splunk's great successes), or, for web sites, punt and use the plethora of JavaScript-based web analytics tools.</p>
+
+<p>Let's log in JSON. Let's format log records with a filter <em>outside</em> the app. Let's put more info in log records by not shoehorning into a printf-message. Debuggability can be improved. Monitoring and analysis can <em>definitely</em> be improved. Let's <em>not</em> write another regex-based parser, and use the time we've saved writing tools to collate logs from multiple nodes and services, to query structured logs (from all services, not just web servers), etc.</p>
+
+<p>At <a href="http://joyent.com">Joyent</a> we use node.js for running many core services -- loosely coupled through HTTP REST APIs and/or AMQP. In this post I'll draw on experiences from my work on Joyent's <a href="http://www.joyent.com/products/smartdatacenter/">SmartDataCenter product</a> and observations of <a href="http://www.joyentcloud.com/">Joyent Cloud</a> operations to suggest some improvements to service logging. I'll show the (open source) <strong>Bunyan logging library and tool</strong> that we're developing to improve the logging toolchain.</p>
+
+<h1 style="margin:48px 0 24px;" id="current-state-of-log-formatting">Current State of Log Formatting</h1>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code># apache access log
+10.0.1.22 - - [15/Oct/2010:11:46:46 -0700] "GET /favicon.ico HTTP/1.1" 404 209
+fe80::6233:4bff:fe29:3173 - - [15/Oct/2010:11:46:58 -0700] "GET / HTTP/1.1" 200 44
+
+# apache error log
+[Fri Oct 15 11:46:46 2010] [error] [client 10.0.1.22] File does not exist: /Library/WebServer/Documents/favicon.ico
+[Fri Oct 15 11:46:58 2010] [error] [client fe80::6233:4bff:fe29:3173] File does not exist: /Library/WebServer/Documents/favicon.ico
+
+# Mac /var/log/secure.log
+Oct 14 09:20:56 banana loginwindow[41]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
+Oct 14 12:32:20 banana com.apple.SecurityServer[25]: UID 501 authenticated as user trentm (UID 501) for right 'system.privilege.admin'
+
+# an internal joyent agent log
+[2012-02-07 00:37:11.898] [INFO] AMQPAgent - Publishing success.
+[2012-02-07 00:37:11.910] [DEBUG] AMQPAgent - { req_id: '8afb8d99-df8e-4724-8535-3d52adaebf25',
+  timestamp: '2012-02-07T00:37:11.898Z',
+
+# typical expressjs log output
+[Mon, 21 Nov 2011 20:52:11 GMT] 200 GET /foo (1ms)
+Blah, some other unstructured output to from a console.log call.
+</code></pre>
+
+<p>What're we doing here? Five logs at random. Five different date formats. As <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">Paul Querna points out</a> we haven't improved log parsability in 20 years. Parsability is enemy number one. You can't use your logs until you can parse the records, and faced with the above the inevitable solution is a one-off regular expression.</p>
+
+<p>The current state of the art is various <a href="http://search.cpan.org/~akira/Apache-ParseLog-1.02/ParseLog.pm">parsing libs</a>, <a href="http://www.webalizer.org/">analysis</a> <a href="http://awstats.sourceforge.net/">tools</a> and homebrew scripts ranging from grep to Perl, whose scope is limited to a few niches log formats.</p>
+
+<h1 style="margin:48px 0 24px;" id="json-for-logs">JSON for Logs</h1>
+
+<p><code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">JSON.parse()</code> solves all that. Let's log in JSON. But it means a change in thinking: <strong>The first-level audience for log files shouldn't be a person, but a machine.</strong></p>
+
+<p>That is not said lightly. The "Unix Way" of small focused tools lightly coupled with text output is important. JSON is less "text-y" than, e.g., Apache common log format. JSON makes <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">grep</code> and <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">awk</code> awkward. Using <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">less</code> directly on a log is handy.</p>
+
+<p>But not handy enough. That <a href="http://bit.ly/wTPlN3">80's pastel jumpsuit awkwardness</a> you're feeling isn't the JSON, it's your tools. Time to find a <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">json</code> tool -- <a href="https://github.com/trentm/json">json</a> is one, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> described below is another one. Time to learn your JSON library instead of your regex library: <a href="https://developer.mozilla.org/en/JSON">JavaScript</a>, <a href="http://docs.python.org/library/json.html">Python</a>, <a href="http://flori.github.com/json/">Ruby</a>, <a href="http://json.org/java/">Java</a>, <a href="http://search.cpan.org/~makamaka/JSON-2.53/lib/JSON.pm">Perl</a>.</p>
+
+<p>Time to burn your log4j Layout classes and move formatting to the tools side. Creating a log message with semantic information and throwing that away to make a string is silly. The win at being able to trivially parse log records is huge. The possibilities at being able to add ad hoc structured information to individual log records is interesting: think program state metrics, think feeding to Splunk, or loggly, think easy audit logs.</p>
+
+<h1 style="margin:48px 0 24px;" id="introducing-bunyan">Introducing Bunyan</h1>
+
+<p><a href="https://github.com/trentm/node-bunyan">Bunyan</a> is <strong>a node.js module for logging in JSON</strong> and <strong>a <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> CLI tool</strong> to view those logs.</p>
+
+<p>Logging with Bunyan basically looks like this:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ cat hi.js
+var Logger = require('bunyan');
+var log = new Logger({name: 'hello' /*, ... */});
+log.info("hi %s", "paul");
+</code></pre>
+
+<p>And you'll get a log record like this:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ node hi.js
+{"name":"hello","hostname":"banana.local","pid":40026,"level":30,"msg":"hi paul","time":"2012-03-28T17:25:37.050Z","v":0}
+</code></pre>
+
+<p>Pipe that through the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> tool that is part of the "node-bunyan" install to get more readable output:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ node hi.js | ./node_modules/.bin/bunyan       # formatted text output
+[2012-02-07T18:50:18.003Z]  INFO: hello/40026 on banana.local: hi paul
+
+$ node hi.js | ./node_modules/.bin/bunyan -j    # indented JSON output
+{
+  "name": "hello",
+  "hostname": "banana.local",
+  "pid": 40087,
+  "level": 30,
+  "msg": "hi paul",
+  "time": "2012-03-28T17:26:38.431Z",
+  "v": 0
+}
+</code></pre>
+
+<p>Bunyan is log4j-like: create a Logger with a name, call <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.info(...)</code>, etc. However it has no intention of reproducing much of the functionality of log4j. IMO, much of that is overkill for the types of services you'll tend to be writing with node.js.</p>
+
+<h1 style="margin:48px 0 24px;" id="longer-bunyan-example">Longer Bunyan Example</h1>
+
+<p>Let's walk through a bigger example to show some interesting things in Bunyan. We'll create a very small "Hello API" server using the excellent <a href="https://github.com/mcavage/node-restify">restify</a> library -- which we used heavily here at <a href="http://joyent.com">Joyent</a>. (Bunyan doesn't require restify at all, you can easily use Bunyan with <a href="http://expressjs.com/">Express</a> or whatever.)</p>
+
+<p><em>You can follow along in <a href="https://github.com/trentm/hello-json-logging">https://github.com/trentm/hello-json-logging</a> if you like. Note that I'm using the current HEAD of the bunyan and restify trees here, so details might change a bit. Prerequisite: a node 0.6.x installation.</em></p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>git clone https://github.com/trentm/hello-json-logging.git
+cd hello-json-logging
+make
+</code></pre>
+
+<h2 id="bunyan-logger">Bunyan Logger</h2>
+
+<p>Our <a href="https://github.com/trentm/hello-json-logging/blob/master/server.js">server</a> first creates a Bunyan logger:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>var Logger = require('bunyan');
+var log = new Logger({
+  name: 'helloapi',
+  streams: [
+    {
+      stream: process.stdout,
+      level: 'debug'
+    },
+    {
+      path: 'hello.log',
+      level: 'trace'
+    }
+  ],
+  serializers: {
+    req: Logger.stdSerializers.req,
+    res: restify.bunyan.serializers.response,
+  },
+});
+</code></pre>
+
+<p>Every Bunyan logger must have a <strong>name</strong>. Unlike log4j, this is not a hierarchical dotted namespace. It is just a name field for the log records.</p>
+
+<p>Every Bunyan logger has one or more <strong>streams</strong>, to which log records are written. Here we've defined two: logging at DEBUG level and above is written to stdout, and logging at TRACE and above is appended to 'hello.log'.</p>
+
+<p>Bunyan has the concept of <strong>serializers</strong>: a registry of functions that know how to convert a JavaScript object for a certain log record field to a nice JSON representation for logging. For example, here we register the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">Logger.stdSerializers.req</code> function to convert HTTP Request objects (using the field name "req") to JSON. More on serializers later.</p>
+
+<h2 id="restify-server">Restify Server</h2>
+
+<p>Restify 1.x and above has bunyan support baked in. You pass in your Bunyan logger like this:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>var server = restify.createServer({
+  name: 'Hello API',
+  log: log   // Pass our logger to restify.
+});
+</code></pre>
+
+<p>Our simple API will have a single <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">GET /hello?name=NAME</code> endpoint:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.get({path: '/hello', name: 'SayHello'}, function(req, res, next) {
+  var caller = req.params.name || 'caller';
+  req.log.debug('caller is "%s"', caller);
+  res.send({"hello": caller});
+  return next();
+});
+</code></pre>
+
+<p>If we run that, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">node server.js</code>, and call the endpoint, we get the expected restify response:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ curl -iSs http://0.0.0.0:8080/hello?name=paul
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: *
+Access-Control-Allow-Headers: Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version
+Access-Control-Expose-Headers: X-Api-Version, X-Request-Id, X-Response-Time
+Server: Hello API
+X-Request-Id: f6aaf942-c60d-4c72-8ddd-bada459db5e3
+Access-Control-Allow-Methods: GET
+Connection: close
+Content-Length: 16
+Content-MD5: Xmn3QcFXaIaKw9RPUARGBA==
+Content-Type: application/json
+Date: Tue, 07 Feb 2012 19:12:35 GMT
+X-Response-Time: 4
+
+{"hello":"paul"}
+</code></pre>
+
+<h2 id="setup-server-logging">Setup Server Logging</h2>
+
+<p>Let's add two things to our server. First, we'll use the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">server.pre</code> to hook into restify's request handling before routing where we'll <strong>log the request</strong>.</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.pre(function (request, response, next) {
+  request.log.info({req: request}, 'start');        // (1)
+  return next();
+});
+</code></pre>
+
+<p>This is the first time we've seen this <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.info</code> style with an object as the first argument. Bunyan logging methods (<code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.trace</code>, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">log.debug</code>, ...) all support an optional <strong>first object argument with extra log record fields</strong>:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>log.info(&lt;object&gt; fields, &lt;string&gt; msg, ...)
+</code></pre>
+
+<p>Here we pass in the restify Request object, <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req</code>. The "req" serializer we registered above will come into play here, but bear with me.</p>
+
+<p>Remember that we already had this debug log statement in our endpoint handler:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>req.log.debug('caller is "%s"', caller);            // (2)
+</code></pre>
+
+<p>Second, use the restify server <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">after</code> event to <strong>log the response</strong>:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>server.on('after', function (req, res, route) {
+  req.log.info({res: res}, "finished");             // (3)
+});
+</code></pre>
+
+<h2 id="log-output">Log Output</h2>
+
+<p>Now lets see what log output we get when somebody hits our API's endpoint:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>$ curl -iSs http://0.0.0.0:8080/hello?name=paul
+HTTP/1.1 200 OK
+...
+X-Request-Id: 9496dfdd-4ec7-4b59-aae7-3fed57aed5ba
+...
+
+{"hello":"paul"}
+</code></pre>
+
+<p>Here is the server log:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>[trentm@banana:~/tm/hello-json-logging]$ node server.js
+... intro "listening at" log message elided ...
+{"name":"helloapi","hostname":"banana.local","pid":40341,"level":30,"req":{"method":"GET","url":"/hello?name=paul","headers":{"user-agent":"curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3","host":"0.0.0.0:8080","accept":"*/*"},"remoteAddress":"127.0.0.1","remotePort":59831},"msg":"start","time":"2012-03-28T17:37:29.506Z","v":0}
+{"name":"helloapi","hostname":"banana.local","pid":40341,"route":"SayHello","req_id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","level":20,"msg":"caller is \"paul\"","time":"2012-03-28T17:37:29.507Z","v":0}
+{"name":"helloapi","hostname":"banana.local","pid":40341,"route":"SayHello","req_id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","level":30,"res":{"statusCode":200,"headers":{"access-control-allow-origin":"*","access-control-allow-headers":"Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version","access-control-expose-headers":"X-Api-Version, X-Request-Id, X-Response-Time","server":"Hello API","x-request-id":"9496dfdd-4ec7-4b59-aae7-3fed57aed5ba","access-control-allow-methods":"GET","connection":"close","content-length":16,"content-md5":"Xmn3QcFXaIaKw9RPUARGBA==","content-type":"application/json","date":"Wed, 28 Mar 2012 17:37:29 GMT","x-response-time":3}},"msg":"finished","time":"2012-03-28T17:37:29.510Z","v":0}
+</code></pre>
+
+<p>Lets look at each in turn to see what is interesting -- pretty-printed with <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">node server.js | ./node_modules/.bin/bunyan -j</code>:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{                                                   // (1)
+  "name": "helloapi",
+  "hostname": "banana.local",
+  "pid": 40442,
+  "level": 30,
+  "req": {
+    "method": "GET",
+    "url": "/hello?name=paul",
+    "headers": {
+      "user-agent": "curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3",
+      "host": "0.0.0.0:8080",
+      "accept": "*/*"
+    },
+    "remoteAddress": "127.0.0.1",
+    "remotePort": 59834
+  },
+  "msg": "start",
+  "time": "2012-03-28T17:39:44.880Z",
+  "v": 0
+}
+</code></pre>
+
+<p>Here we logged the incoming request with <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">request.log.info({req: request}, 'start')</code>. The use of the "req" field triggers the <a href="https://github.com/trentm/node-bunyan/blob/master/lib/bunyan.js#L857-870">"req" serializer</a> <a href="https://github.com/trentm/hello-json-logging/blob/master/server.js#L24">registered at Logger creation</a>.</p>
+
+<p>Next the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log.debug</code> in our handler:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{                                                   // (2)
+  "name": "helloapi",
+  "hostname": "banana.local",
+  "pid": 40442,
+  "route": "SayHello",
+  "req_id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",
+  "level": 20,
+  "msg": "caller is \"paul\"",
+  "time": "2012-03-28T17:39:44.883Z",
+  "v": 0
+}
+</code></pre>
+
+<p>and the log of response in the "after" event:</p>
+
+<pre style="overflow:auto;color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:5px;"><code>{                                                   // (3)
+  "name": "helloapi",
+  "hostname": "banana.local",
+  "pid": 40442,
+  "route": "SayHello",
+  "req_id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",
+  "level": 30,
+  "res": {
+    "statusCode": 200,
+    "headers": {
+      "access-control-allow-origin": "*",
+      "access-control-allow-headers": "Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version",
+      "access-control-expose-headers": "X-Api-Version, X-Request-Id, X-Response-Time",
+      "server": "Hello API",
+      "x-request-id": "9496dfdd-4ec7-4b59-aae7-3fed57aed5ba",
+      "access-control-allow-methods": "GET",
+      "connection": "close",
+      "content-length": 16,
+      "content-md5": "Xmn3QcFXaIaKw9RPUARGBA==",
+      "content-type": "application/json",
+      "date": "Wed, 28 Mar 2012 17:39:44 GMT",
+      "x-response-time": 5
+    }
+  },
+  "msg": "finished",
+  "time": "2012-03-28T17:39:44.886Z",
+  "v": 0
+}
+</code></pre>
+
+<p>Two useful details of note here:</p>
+
+<ol>
+<li><p>The last two log messages include <strong>a "req_id" field</strong> (added to the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log</code> logger by restify). Note that this is the same UUID as the "X-Request-Id" header in the <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">curl</code> response. This means that if you use <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">req.log</code> for logging in your API handlers you will get an easy way to collate all logging for particular requests.</p>
+
+<p>If your's is an SOA system with many services, a best practice is to carry that X-Request-Id/req_id through your system to enable collating handling of a single top-level request.</p></li>
+<li><p>The last two log messages include <strong>a "route" field</strong>. This tells you to which handler restify routed the request. While possibly useful for debugging, this can be very helpful for log-based monitoring of endpoints on a server.</p></li>
+</ol>
+
+<p>Recall that we also setup all logging to go the "hello.log" file. This was set at the TRACE level. Restify will log more detail of its operation at the trace level. See <a href="https://gist.github.com/1761772">my "hello.log"</a> for an example. The <code style="color:#999;background-color:#2f2f2f;border:1px solid #484848;padding:.2em .4em;">bunyan</code> tool does a decent job of <a href="https://gist.github.com/1761772#file_2.+cat+hello.log+pipe+bunyan">nicely formatting</a> multiline messages and "req"/"res" keys (with color, not shown in the gist).</p>
+
+<p><em>This</em> is logging you can use effectively.</p>
+
+<h1 style="margin:48px 0 24px;" id="other-tools">Other Tools</h1>
+
+<p>Bunyan is just one of many options for logging in node.js-land. Others (that I know of) supporting JSON logging are <a href="https://github.com/flatiron/winston#readme">winston</a> and <a href="https://github.com/pquerna/node-logmagic/">logmagic</a>. Paul Querna has <a href="http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/">an excellent post on using JSON for logging</a>, which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching.</p>
+
+<h1 style="margin:48px 0 24px;" id="final-thoughts">Final Thoughts</h1>
+
+<p>Parsing challenges won't ever completely go away, but it can for your logs if you use JSON. Collating log records across logs from multiple nodes is facilitated by a common "time" field. Correlating logging across multiple services is enabled by carrying a common "req_id" (or equivalent) through all such logs.</p>
+
+<p>Separate log files for a single service is an anti-pattern. The typical Apache example of separate access and error logs is legacy, not an example to follow. A JSON log provides the structure necessary for tooling to easily filter for log records of a particular type.</p>
+
+<p>JSON logs bring possibilities. Feeding to tools like Splunk becomes easy. Ad hoc fields allow for a lightly spec'd comm channel from apps to other services: records with a "metric" could feed to <a href="http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/">statsd</a>, records with a "loggly: true" could feed to loggly.com.</p>
+
+<p>Here I've described a very simple example of restify and bunyan usage for node.js-based API services with easy JSON logging. Restify provides a powerful framework for robust API services. Bunyan provides a light API for nice JSON logging and the beginnings of tooling to help consume Bunyan JSON logs.</p>
+
+<p><strong>Update (29-Mar-2012):</strong> Fix styles somewhat for RSS readers.</p>
diff --git a/locale/uk/blog/nodejs-road-ahead.md b/locale/uk/blog/nodejs-road-ahead.md
new file mode 100755
index 0000000000000..ca856d50e63f1
--- /dev/null
+++ b/locale/uk/blog/nodejs-road-ahead.md
@@ -0,0 +1,54 @@
+---
+title: Node.js and the Road Ahead
+date: 2014-01-16T23:00:00.000Z
+author: Timothy J Fontaine
+slug: nodejs-road-ahead
+layout: blog-post.hbs
+---
+As the new project lead for Node.js I am excited for our future, and want to
+give you an update on where we are.
+
+One of Node's major goals is to provide a small core, one that provides the
+right amount of surface area for consumers to achieve and innovate, without
+Node itself getting in the way. That ethos is alive and well, we're going to
+continue to provide a small, simple, and stable set of APIs that facilitate the
+amazing uses the community finds for Node. We're going to keep providing
+backward compatible APIs, so code you write today will continue to work on
+future versions of Node. And of course, performance tuning and bug fixing will
+always be an important part of every release cycle.
+
+The release of Node v0.12 is imminent, and a lot of significant work has gone
+into this release. There's streams3, a better keep alive agent for http, the vm
+module is now based on contextify, and significant performance work done in
+core features (Buffers, TLS, streams). We have a few APIs that are still being
+ironed out before we can feature freeze and branch (execSync, AsyncListeners,
+user definable instrumentation). We are definitely in the home stretch.
+
+But Node is far from done. In the short term there will be new releases of v8
+that we'll need to track, as well as integrating the new ABI stable C module
+interface. There are interesting language features that we can use to extend
+Node APIs (extend not replace). We need to write more tooling, we need to
+expose more interfaces to further enable innovation. We can explore
+functionality to embed Node in your existing project.
+
+The list can go on and on. Yet, Node is larger than the software itself. Node
+is also the community, the businesses, the ecosystems, and their related
+events. With that in mind there are things we can work to improve. 
+
+The core team will be improving its procedures such that we can quickly and
+efficiently communicate with you. We want to provide high quality and timely
+responses to issues, describe our development roadmap, as well as provide our
+progress during each release cycle. We know you're interested in our plans for
+Node, and it's important we're able to provide that information. Communication
+should be bidirectional: we want to continue to receive feedback about how
+you're using Node, and what your pain points are.
+
+After the release of v0.12 we will facilitate the community to contribute and
+curate content for nodejs.org. Allowing the community to continue to invest in
+Node will ensure nodejs.org is an excellent starting point and the primary
+resource for tutorials, documentation, and materials regarding Node. We have an
+awesome and engaged community, and they're paramount to our success. 
+
+I'm excited for Node's future, to see new and interesting use cases, and to
+continue to help businesses scale and innovate with Node. We have a lot we can
+accomplish together, and I look forward to seeing those results.
diff --git a/locale/uk/blog/npm/2013-outage-postmortem.md b/locale/uk/blog/npm/2013-outage-postmortem.md
new file mode 100755
index 0000000000000..afe9dda9ea85c
--- /dev/null
+++ b/locale/uk/blog/npm/2013-outage-postmortem.md
@@ -0,0 +1,85 @@
+---
+date: 2013-11-26T15:14:59.000Z
+author: Charlie Robbins
+title: Keeping The npm Registry Awesome
+slug: npm-post-mortem
+category: npm
+layout: blog-post.hbs
+---
+
+We know the availability and overall health of The npm Registry is paramount to everyone using Node.js as well as the larger JavaScript community and those of your using it for [some][browserify] [awesome][dotc] [projects][npm-rubygems] [and ideas][npm-python]. Between November 4th and November 15th 2013 The npm Registry had several hours of downtime over three distinct time periods:
+
+1. November 4th -- 16:30 to 15:00 UTC
+2. November 13th -- 15:00 to 19:30 UTC
+3. November 15th -- 15:30 to 18:00 UTC
+
+The root cause of these downtime was insufficient resources: both hardware and human. This is a full post-mortem where we will be look at how npmjs.org works, what went wrong, how we changed the previous architecture of The npm Registry to fix it, as well next steps we are taking to prevent this from happening again.
+
+All of the next steps require additional expenditure from Nodejitsu: both servers and labor. This is why along with this post-mortem we are announcing our [crowdfunding campaign: scalenpm.org](https://scalenpm.org)! Our goal is to raise enough funds so that Nodejitsu can continue to run The npm Registry as a free service for _you, the community._ 
+
+Please take a minute now to donate at [https://scalenpm.org](https://scalenpm.org)! 
+
+## How does npmjs.org work?
+
+There are two distinct components that make up npmjs.org operated by different people:
+
+* **http://registry.npmjs.org**: The main CouchApp (Github: [isaacs/npmjs.org](https://github.com/isaacs/npmjs.org)) that stores both package tarballs and metadata. It is operated by Nodejitsu since we [acquired IrisCouch in May](https://www.nodejitsu.com/company/press/2013/05/22/iriscouch/). The primary system administrator is [Jason Smith](https://github.com/jhs), the current CTO at Nodejitsu, cofounder of IrisCouch, and the System Administrator of registry.npmjs.org since 2011.
+* **https://npmjs.com**: The npmjs website that you interact with using a web browser. It is a Node.js program (Github: [isaacs/npm-www](https://github.com/isaacs/npm-www)) maintained and operated by Isaac and running on a Joyent Public Cloud SmartMachine.
+
+Here is a high-level summary of the _old architecture:_
+
+<img width=600 src="https://i.cloudup.com/bapm3fk8Ve-3000x3000.png" alt="old npm architecture">
+<div style="text-align:center">
+  _Diagram 1. Old npm architecture_
+</div>
+
+## What went wrong and how was it fixed?
+
+As illustrated above, before November 13th, 2013, npm operated as a single CouchDB server with regular daily backups. We briefly ran a multi-master CouchDB setup after downtime back in August, but after reports that `npm login` no longer worked correctly we rolled back to a single CouchDB server. On both November 13th and November 15th CouchDB became unresponsive on requests to the `/registry` database while requests to all other databases (e.g. `/public_users`) remained responsive. Although the root cause of the CouchDB failures have yet to be determined given that only requests to `/registry` were slow and/or timed out we suspect it is related to the massive number of attachments stored in the registry.
+
+The incident on November 4th was ultimately resolved by a reboot and resize of the host machine, but when the same symptoms reoccured less than 10 days later additional steps were taken:
+
+1. The [registry was moved to another machine][ops-new-machine] of equal resources to exclude the possibility of a hardware issue.
+2. The [registry database itself][ops-compaction] was [compacted][compaction].
+
+When neither of these yielded a solution Jason Smith and I decided to move to a multi-master architecture with continuous replication illustrated below:
+
+<img width=600 src="https://i.cloudup.com/xu1faVCq8p-3000x3000.png" alt="current npm architecture">
+<div style="text-align:center">
+  _Diagram 2. Current npm architecture -- Red-lines denote continuous replication_
+</div>
+
+This _should_ have been the end of our story but unfortunately our supervision logic did not function properly to restart the secondary master on the morning of November 15th. During this time we [moved briefly][ops-single-server] back to a single master architecture. Since then the secondary master has been closely monitored by the entire Nodejitsu operations team to ensure it's continued stability.
+
+## What is being done to prevent future incidents?
+
+The public npm registry simply cannot go down. **Ever.** We gained a lot of operational knowledge about The npm Registry and about CouchDB as a result of these outages. This new knowledge has made clear several steps that we need to take to prevent future downtime:
+
+1. **Always be in multi-master**: The multi-master CouchDB architecture we have setup will scale to more than just two CouchDB servers. _As npm grows we'll be able to add additional capacity!_
+2. **Decouple www.npmjs.org and registry.npmjs.org**: Right now www.npmjs.org still depends directly on registry.npmjs.org. We are planning to add an additional replica to the current npm architecture so that Isaac can more easily service requests to www.npmjs.org. That means it won't go down if the registry goes down.
+3. **Always have a spare replica**: We need have a hot spare replica running continuous replication from either to swap out when necessary. This is also important as we need to regularly run compaction on each master since the registry is growing ~10GB per week on disk.
+4. **Move attachments out of CouchDB**: Work has begun to move the package tarballs out of CouchDB and into [Joyent's Manta service](http://www.joyent.com/products/manta). Additionally, [MaxCDN](http://www.maxcdn.com/) has generously offered to provide CDN services for npm, once the tarballs are moved out of the registry database.  This will help improve delivery speed, while dramatically reducing the file system I/O load on the CouchDB servers.  Work is progressing slowly, because at each stage in the plan, we are making sure that current replication users are minimally impacted.
+
+When these new infrastructure components are in-place The npm Registry will look like this:
+
+<img width=600 src="https://i.cloudup.com/XwrpFNICJ2-3000x3000.png" alt="planned npm architecture">
+<div style="text-align:center">
+  _Diagram 3. Planned npm architecture -- Red-lines denote continuous replication_
+</div>
+
+## You are npm! And we need your help!
+
+The npm Registry has had a 10x year. In November 2012 there were 13.5 million downloads. In October 2013 there were **114.6 million package downloads.** We're honored to have been a part of sustaining this growth for the community and we want to see it continue to grow to a billion package downloads a month and beyond.
+
+_**But we need your help!**_ All of these necessary improvements require more servers, more time from Nodejitsu staff and an overall increase to what we spend maintaining the public npm registry as a free service for the Node.js community.
+
+Please take a minute now to donate at [https://scalenpm.org](https://scalenpm.org)! 
+
+[browserify]: http://browserify.org/
+[dotc]: https://github.com/substack/dotc
+[npm-rubygems]: http://andrew.ghost.io/emulating-node-js-modules-in-ruby/
+[npm-python]: https://twitter.com/__lucas/status/391688082573258753
+[ops-new-machine]: https://twitter.com/npmjs/status/400692071377276928
+[ops-compaction]: https://twitter.com/npmjs/status/400705715846643712
+[compaction]: http://wiki.apache.org/couchdb/Compaction
+[ops-single-server]: https://twitter.com/npmjs/status/401384681507016704
diff --git a/locale/uk/blog/npm/index.md b/locale/uk/blog/npm/index.md
new file mode 100755
index 0000000000000..a26081ad303e5
--- /dev/null
+++ b/locale/uk/blog/npm/index.md
@@ -0,0 +1,6 @@
+---
+title: NPM
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/npm/managing-node-js-dependencies-with-shrinkwrap.md b/locale/uk/blog/npm/managing-node-js-dependencies-with-shrinkwrap.md
new file mode 100755
index 0000000000000..939c48bf3ab40
--- /dev/null
+++ b/locale/uk/blog/npm/managing-node-js-dependencies-with-shrinkwrap.md
@@ -0,0 +1,170 @@
+---
+title: Managing Node.js Dependencies with Shrinkwrap
+author: Dave Pacheco
+date: 2012-02-27T18:51:59.000Z
+status: publish
+category: npm
+slug: managing-node-js-dependencies-with-shrinkwrap
+layout: blog-post.hbs
+---
+
+<p style="float:right;text-align:center;margin:5px;"><a href="http://www.flickr.com/photos/luc_viatour/4247957432/"><img class="size-medium wp-image-652" style="border:1px #000000 solid;" title="Web" src="http://dtrace.org/blogs/dap/files/2012/02/web-300x300.jpg" alt="" width="250" height="250" /></a><br>
+Photo by Luc Viatour (flickr)</p>
+
+<p>Managing dependencies is a fundamental problem in building complex software. The terrific success of github and <a href="https://npmjs.com/">npm</a> have made code reuse especially easy in the Node world, where packages don&#039;t exist in isolation but rather as nodes in a large graph. The software is constantly changing (releasing new versions), and each package has its own constraints about what other packages it requires to run (dependencies). npm keeps track of these constraints, and authors express what kind of changes are compatible using <a href="https://npmjs.com/doc/semver.html">semantic versioning</a>, allowing authors to specify that their package will work with even future versions of its dependencies as long as the semantic versions are assigned properly.
+
+</p>
+<p>This does mean that when you &quot;npm install&quot; a package with dependencies, there&#039;s no guarantee that you&#039;ll get the same set of code now that you would have gotten an hour ago, or that you would get if you were to run it again an hour later. You may get a bunch of bug fixes now that weren&#039;t available an hour ago. This is great during development, where you want to keep up with changes upstream. It&#039;s not necessarily what you want for deployment, though, where you want to validate whatever bits you&#039;re actually shipping.
+
+</p>
+<p>Put differently, <strong>it&#039;s understood that all software changes incur some risk, and it&#039;s critical to be able to manage this risk on your own terms</strong>. Taking that risk in development is good because by definition that&#039;s when you&#039;re incorporating and testing software changes. On the other hand, if you&#039;re shipping production software, you probably don&#039;t want to take this risk when cutting a release candidate (i.e. build time) or when you actually ship (i.e. deploy time) because you want to validate whatever you ship.
+
+</p>
+<p>You can address a simple case of this problem by only depending on specific versions of packages, allowing no semver flexibility at all, but this falls apart when you depend on packages that don&#039;t also adopt the same principle. Many of us at Joyent started wondering: can we generalize this approach?
+
+</p>
+<h2>Shrinkwrapping packages</h2>
+<p>That brings us to <a href="https://npmjs.com/doc/shrinkwrap.html">npm shrinkwrap</a><a href="#note1-note" name="note1-top">[1]</a>:
+
+</p>
+<pre><code>NAME
+       npm-shrinkwrap -- Lock down dependency versions
+
+SYNOPSIS
+       npm shrinkwrap
+
+DESCRIPTION
+       This  command  locks down the versions of a package&#039;s dependencies so
+       that you can control exactly which versions of each  dependency  will
+       be used when your package is installed.</code></pre>
+<p>Let&#039;s consider package A:
+
+</p>
+<pre><code>{
+    &quot;name&quot;: &quot;A&quot;,
+    &quot;version&quot;: &quot;0.1.0&quot;,
+    &quot;dependencies&quot;: {
+        &quot;B&quot;: &quot;&lt;0.1.0&quot;
+    }
+}</code></pre>
+<p>package B:
+
+</p>
+<pre><code>{
+    &quot;name&quot;: &quot;B&quot;,
+    &quot;version&quot;: &quot;0.0.1&quot;,
+    &quot;dependencies&quot;: {
+        &quot;C&quot;: &quot;&lt;0.1.0&quot;
+    }
+}</code></pre>
+<p>and package C:
+
+</p>
+<pre><code>{
+    &quot;name&quot;: &quot;C,
+    &quot;version&quot;: &quot;0.0.1&quot;
+}</code></pre>
+<p>If these are the only versions of A, B, and C available in the registry, then a normal &quot;npm install A&quot; will install:
+
+</p>
+<pre><code>A@0.1.0
+└─┬ B@0.0.1
+  └── C@0.0.1</code></pre>
+<p>Then if B@0.0.2 is published, then a fresh &quot;npm install A&quot; will install:
+
+</p>
+<pre><code>A@0.1.0
+└─┬ B@0.0.2
+  └── C@0.0.1</code></pre>
+<p>assuming the new version did not modify B&#039;s dependencies. Of course, the new version of B could include a new version of C and any number of new dependencies. As we said before, if A&#039;s author doesn&#039;t want that, she could specify a dependency on B@0.0.1. But if A&#039;s author and B&#039;s author are not the same person, there&#039;s no way for A&#039;s author to say that she does not want to pull in newly published versions of C when B hasn&#039;t changed at all.
+
+</p>
+<p>In this case, A&#039;s author can use
+
+</p>
+<pre><code># npm shrinkwrap</code></pre>
+<p>This generates npm-shrinkwrap.json, which will look something like this:
+
+</p>
+<pre><code>{
+    &quot;name&quot;: &quot;A&quot;,
+    &quot;dependencies&quot;: {
+        &quot;B&quot;: {
+            &quot;version&quot;: &quot;0.0.1&quot;,
+            &quot;dependencies&quot;: {
+                &quot;C&quot;: {  &quot;version&quot;: &quot;0.1.0&quot; }
+            }
+        }
+    }
+}</code></pre>
+<p>The shrinkwrap command has locked down the dependencies based on what&#039;s currently installed in node_modules.  <strong>When &quot;npm install&quot; installs a package with a npm-shrinkwrap.json file in the package root, the shrinkwrap file (rather than package.json files) completely drives the installation of that package and all of its dependencies (recursively).</strong>  So now the author publishes A@0.1.0, and subsequent installs of this package will use B@0.0.1 and C@0.1.0, regardless the dependencies and versions listed in A&#039;s, B&#039;s, and C&#039;s package.json files.  If the authors of B and C publish new versions, they won&#039;t be used to install A because the shrinkwrap refers to older versions.  Even if you generate a new shrinkwrap, it will still reference the older versions, since &quot;npm shrinkwrap&quot; uses what&#039;s installed locally rather than what&#039;s available in the registry. 
+
+</p>
+<h4>Using shrinkwrapped packages</h4>
+<p>Using a shrinkwrapped package is no different than using any other package: you can &quot;npm install&quot; it by hand, or add a dependency to your package.json file and &quot;npm install&quot; it.
+
+</p>
+<h4>Building shrinkwrapped packages</h4>
+<p>To shrinkwrap an existing package:
+
+</p>
+<ol>
+<li>Run &quot;npm install&quot; in the package root to install the current versions of all dependencies.</li>
+<li>Validate that the package works as expected with these versions.</li>
+<li>Run &quot;npm shrinkwrap&quot;, add npm-shrinkwrap.json to git, and publish your package.</li>
+</ol>
+<p>To add or update a dependency in a shrinkwrapped package:
+
+</p>
+<ol>
+<li>Run &quot;npm install&quot; in the package root to install the current versions of all dependencies.</li>
+<li>Add or update dependencies. &quot;npm install&quot; each new or updated package individually and then update package.json.</li>
+<li>Validate that the package works as expected with the new dependencies.</li>
+<li>Run &quot;npm shrinkwrap&quot;, commit the new npm-shrinkwrap.json, and publish your package.</li>
+</ol>
+<p>You can still use <a href="https://npmjs.com/doc/outdated.html">npm outdated(1)</a> to view which dependencies have newer versions available.
+
+</p>
+<p>For more details, check out the full docs on <a href="https://npmjs.com/doc/shrinkwrap.html">npm shrinkwrap</a>, from which much of the above is taken.
+
+</p>
+<h2>Why not just check <code>node_modules</code> into git?</h2>
+<p>One previously <a href="http://www.mikealrogers.com/posts/nodemodules-in-git.html">proposed solution</a> is to &quot;npm install&quot; your dependencies during development and commit the results into source control. Then you deploy your app from a specific git SHA knowing you&#039;ve got exactly the same bits that you tested in development. This does address the problem, but it has its own issues: for one, binaries are tricky because you need to &quot;npm install&quot; them to get their sources, but this builds the [system-dependent] binary too. You can avoid checking in the binaries and use &quot;npm rebuild&quot; at build time, but we&#039;ve had a lot of difficulty trying to do this.<a href="#note2-note" name="note2-top">[2]</a> At best, this is second-class treatment for binary modules, which are critical for many important types of Node applications.<a href="#note3-note" name="note3-top">[3]</a>
+
+</p>
+<p>Besides the issues with binary modules, this approach just felt wrong to many of us. There&#039;s a reason we don&#039;t check binaries into source control, and it&#039;s not just because they&#039;re platform-dependent. (After all, we could build and check in binaries for all supported platforms and operating systems.) It&#039;s because that approach is error-prone and redundant: error-prone because it introduces a new human failure mode where someone checks in a source change but doesn&#039;t regenerate all the binaries, and redundant because the binaries can always be built from the sources alone. An important principle of software version control is that you don&#039;t check in files derived directly from other files by a simple transformation.<a href="#note4-note" name="note4-top">[4]</a> Instead, you check in the original sources and automate the transformations via the build process.
+
+</p>
+<p>Dependencies are just like binaries in this regard: they&#039;re files derived from a simple transformation of something else that is (or could easily be) already available: the name and version of the dependency. Checking them in has all the same problems as checking in binaries: people could update package.json without updating the checked-in module (or vice versa). Besides that, adding new dependencies has to be done by hand, introducing more opportunities for error (checking in the wrong files, not checking in certain files, inadvertently changing files, and so on). Our feeling was: why check in this whole dependency tree (and create a mess for binary add-ons) when we could just check in the package name and version and have the build process do the rest?
+
+</p>
+<p>Finally, the approach of checking in node_modules doesn&#039;t really scale for us. We&#039;ve got at least a dozen repos that will use restify, and it doesn&#039;t make sense to check that in everywhere when we could instead just specify which version each one is using. There&#039;s another principle at work here, which is <strong>separation of concerns</strong>: each repo specifies <em>what</em> it needs, while the build process figures out <em>where to get it</em>.
+
+</p>
+<h2>What if an author republishes an existing version of a package?</h2>
+<p>We&#039;re not suggesting deploying a shrinkwrapped package directly and running &quot;npm install&quot; to install from shrinkwrap in production. We already have a build process to deal with binary modules and other automateable tasks. That&#039;s where we do the &quot;npm install&quot;. We tar up the result and distribute the tarball. Since we test each build before shipping, we won&#039;t deploy something we didn&#039;t test.
+
+</p>
+<p>It&#039;s still possible to pick up newly published versions of existing packages at build time. We assume force publish is not that common in the first place, let alone force publish that breaks compatibility. If you&#039;re worried about this, you can use git SHAs in the shrinkwrap or even consider maintaining a mirror of the part of the npm registry that you use and require human confirmation before mirroring unpublishes.
+
+</p>
+<h2>Final thoughts</h2>
+<p>Of course, the details of each use case matter a lot, and the world doesn&#039;t have to pick just one solution. If you like checking in node_modules, you should keep doing that. We&#039;ve chosen the shrinkwrap route because that works better for us.
+
+</p>
+<p>It&#039;s not exactly news that Joyent is heavy on Node. Node is the heart of our SmartDataCenter (SDC) product, whose public-facing web portal, public API, Cloud Analytics, provisioning, billing, heartbeating, and other services are all implemented in Node. That&#039;s why it&#039;s so important to us to have robust components (like <a href="https://github.com/trentm/node-bunyan">logging</a> and <a href="http://mcavage.github.com/node-restify/">REST</a>) and tools for <a href="http://dtrace.org/blogs/dap/2012/01/13/playing-with-nodev8-postmortem-debugging/">understanding production failures postmortem</a>, <a href="http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/">profile Node apps in production</a>, and now managing Node dependencies. Again, we&#039;re interested to hear feedback from others using these tools.
+
+</p>
+<hr />
+Dave Pacheco blogs at <a href="http://dtrace.org/blogs/dap/">dtrace.org</a>.
+
+<p><a href="#note1-top" name="note1-note">[1]</a> Much of this section is taken directly from the &quot;npm shrinkwrap&quot; documentation.
+
+</p>
+<p><a href="#note2-top" name="note2-note">[2]</a> We&#039;ve had a lot of trouble with checking in node_modules with binary dependencies. The first problem is figuring out exactly which files <em>not</em> to check in (<em>.o, </em>.node, <em>.dynlib, </em>.so, *.a, ...). When <a href="https://twitter.com/#!/mcavage">Mark</a> went to apply this to one of our internal services, the &quot;npm rebuild&quot; step blew away half of the dependency tree because it ran &quot;make clean&quot;, which in dependency <a href="http://ldapjs.org/">ldapjs</a> brings the repo to a clean slate by blowing away its dependencies. Later, a new (but highly experienced) engineer on our team was tasked with fixing a bug in our Node-based DHCP server. To fix the bug, we went with a new dependency. He tried checking in node_modules, which added 190,000 lines of code (to this repo that was previously a few hundred LOC). And despite doing everything he could think of to do this correctly and test it properly, the change broke the build because of the binary modules. So having tried this approach a few times now, it appears quite difficult to get right, and as I pointed out above, the lack of actual documentation and real world examples suggests others either aren&#039;t using binary modules (which we know isn&#039;t true) or haven&#039;t had much better luck with this approach.
+
+</p>
+<p><a href="#note3-top" name="note3-note">[3]</a> Like a good Node-based distributed system, our architecture uses lots of small HTTP servers. Each of these serves a REST API using <a href="http://mcavage.github.com/node-restify/">restify</a>. restify uses the binary module <a href="https://github.com/chrisa/node-dtrace-provider">node-dtrace-provider</a>, which gives each of our services <a href="http://mcavage.github.com/node-restify/#DTrace">deep DTrace-based observability for free</a>. So literally almost all of our components are or will soon be depending on a binary add-on. Additionally, the foundation of <a href="http://dtrace.org/blogs/dap/2011/03/01/welcome-to-cloud-analytics/">Cloud Analytics</a> are a pair of binary modules that extract data from <a href="https://github.com/bcantrill/node-libdtrace">DTrace</a> and <a href="https://github.com/bcantrill/node-kstat">kstat</a>. So this isn&#039;t a corner case for us, and we don&#039;t believe we&#039;re exceptional in this regard. The popular <a href="https://github.com/pietern/hiredis-node">hiredis</a> package for interfacing with redis from Node is also a binary module.
+
+</p>
+<p><a href="#note4-top" name="note4-note">[4]</a> Note that I said this is an important principle for <em>software version control</em>, not using git in general. People use git for lots of things where checking in binaries and other derived files is probably fine. Also, I&#039;m not interested in proselytizing; if you want to do this for software version control too, go ahead. But don&#039;t do it out of ignorance of existing successful software engineering practices.</p>
diff --git a/locale/uk/blog/npm/npm-1-0-global-vs-local-installation.md b/locale/uk/blog/npm/npm-1-0-global-vs-local-installation.md
new file mode 100755
index 0000000000000..380eb5f486010
--- /dev/null
+++ b/locale/uk/blog/npm/npm-1-0-global-vs-local-installation.md
@@ -0,0 +1,67 @@
+---
+title: "npm 1.0: Global vs Local installation"
+author: Isaac Schlueter
+date: 2011-03-24T06:07:13.000Z
+status: publish
+category: npm
+slug: npm-1-0-global-vs-local-installation
+layout: blog-post.hbs
+---
+
+<p><i>npm 1.0 is in release candidate mode.  <a href="http://groups.google.com/group/npm-/browse_thread/thread/43d3e76d71d1f141">Go get it!</a></i></p>
+
+<p>More than anything else, the driving force behind the npm 1.0 rearchitecture was the desire to simplify what a package installation directory structure looks like.</p>
+
+<p>In npm 0.x, there was a command called <code>bundle</code> that a lot of people liked. <code>bundle</code> let you install your dependencies locally in your project, but even still, it was basically a hack that never really worked very reliably.</p>
+
+<p>Also, there was that activation/deactivation thing.  That&#8217;s confusing.</p>
+
+<h2>Two paths</h2>
+
+<p>In npm 1.0, there are two ways to install things:</p>
+
+<ol> <li>globally &#8212;- This drops modules in <code>{prefix}/lib/node_modules</code>, and puts executable files in <code>{prefix}/bin</code>, where <code>{prefix}</code> is usually something like <code>/usr/local</code>. It also installs man pages in <code>{prefix}/share/man</code>, if they&#8217;re supplied.</li> <li>locally &#8212;- This installs your package in the current working directory. Node modules go in <code>./node_modules</code>, executables go in <code>./node_modules/.bin/</code>, and man pages aren&#8217;t installed at all.</li> </ol>
+
+<h2>Which to choose</h2>
+
+<p>Whether to install a package globally or locally depends on the <code>global</code> config, which is aliased to the <code>-g</code> command line switch.</p>
+
+<p>Just like how global variables are kind of gross, but also necessary in some cases, global packages are important, but best avoided if not needed.</p>
+
+<p>In general, the rule of thumb is:</p>
+
+<ol> <li>If you&#8217;re installing something that you want to use <em>in</em> your program, using <code>require('whatever')</code>, then install it locally, at the root of your project.</li> <li>If you&#8217;re installing something that you want to use in your <em>shell</em>, on the command line or something, install it globally, so that its binaries end up in your <code>PATH</code> environment variable.</li> </ol>
+
+<h2>When you can't choose</h2>
+
+<p>Of course, there are some cases where you want to do both. <a href="http://coffeescript.org/">Coffee-script</a> and <a href="http://expressjs.com/">Express</a> both are good examples of apps that have a command line interface, as well as a library. In those cases, you can do one of the following:</p>
+
+<ol> <li>Install it in both places. Seriously, are you that short on disk space? It&#8217;s fine, really. They&#8217;re tiny JavaScript programs.</li> <li>Install it globally, and then <code>npm link coffee-script</code> or <code>npm link express</code> (if you&#8217;re on a platform that supports symbolic links.) Then you only need to update the global copy to update all the symlinks as well.</li> </ol>
+
+<p>The first option is the best in my opinion.  Simple, clear, explicit.  The second is really handy if you are going to re-use the same library in a bunch of different projects.  (More on <code>npm link</code> in a future installment.)</p>
+
+<p>You can probably think of other ways to do it by messing with environment variables. But I don&#8217;t recommend those ways. Go with the grain.</p>
+
+<h2 id="slight_exception_it8217s_not_always_the_cwd">Slight exception: It&#8217;s not always the cwd.</h2>
+
+<p>Let&#8217;s say you do something like this:</p>
+
+<pre style="background:#333!important;color:#ccc!important;overflow:auto!important;padding:2px!important;"><code>cd ~/projects/foo     # go into my project
+npm install express   # ./node_modules/express
+cd lib/utils          # move around in there
+vim some-thing.js     # edit some stuff, work work work
+npm install redis     # ./lib/utils/node_modules/redis!? ew.</code></pre>
+
+<p>In this case, npm will install <code>redis</code> into <code>~/projects/foo/node_modules/redis</code>. Sort of like how git will work anywhere within a git repository, npm will work anywhere within a package, defined by having a <code>node_modules</code> folder.</p>
+
+<h2>Test runners and stuff</h2>
+
+<p>If your package's <code>scripts.test</code> command uses a command-line program installed by one of your dependencies, not to worry.  npm makes <code>./node_modules/.bin</code> the first entry in the <code>PATH</code> environment variable when running any lifecycle scripts, so this will work fine, even if your program is not globally installed:
+
+<pre style="background:#333!important;color:#ccc!important;overflow:auto!important;padding:2px!important;"><code>{ "name" : "my-program"
+, "version" : "1.2.3"
+, "dependencies": { "express": "*", "coffee-script": "*" }
+, "devDependencies": { "vows": "*" }
+, "scripts":
+  { "test": "vows test/*.js"
+  , "preinstall": "cake build" } }</code></pre>
diff --git a/locale/uk/blog/npm/npm-1-0-link.md b/locale/uk/blog/npm/npm-1-0-link.md
new file mode 100755
index 0000000000000..24a16427b21ce
--- /dev/null
+++ b/locale/uk/blog/npm/npm-1-0-link.md
@@ -0,0 +1,117 @@
+---
+title: "npm 1.0: link"
+author: Isaac Schlueter
+date: 2011-04-07T00:40:33.000Z
+status: publish
+category: npm
+slug: npm-1-0-link
+layout: blog-post.hbs
+---
+
+<p><i>npm 1.0 is in release candidate mode. <a href="http://groups.google.com/group/npm-/browse_thread/thread/43d3e76d71d1f141">Go get it!</a></i></p>
+
+<p>In npm 0.x, there was a command called <code>link</code>. With it, you could &#8220;link-install&#8221; a package so that changes would be reflected in real-time. This is especially handy when you&#8217;re actually building something. You could make a few changes, run the command again, and voila, your new code would be run without having to re-install every time.</p>
+
+<p>Of course, compiled modules still have to be rebuilt. That&#8217;s not ideal, but it&#8217;s a problem that will take more powerful magic to solve.</p>
+
+<p>In npm 0.x, this was a pretty awful kludge. Back then, every package existed in some folder like:</p>
+
+<pre><code>prefix/lib/node/.npm/my-package/1.3.6/package
+</code></pre>
+
+<p>and the package&#8217;s version and name could be inferred from the path. Then, symbolic links were set up that looked like:</p>
+
+<pre><code>prefix/lib/node/my-package@1.3.6 -&gt; ./.npm/my-package/1.3.6/package
+</code></pre>
+
+<p>It was easy enough to point that symlink to a different location. However, since the <em>package.json file could change</em>, that meant that the connection between the version and the folder was not reliable.</p>
+
+<p>At first, this was just sort of something that we dealt with by saying, &#8220;Relink if you change the version.&#8221; However, as more and more edge cases arose, eventually the solution was to give link packages this fakey version of &#8220;9999.0.0-LINK-hash&#8221; so that npm knew it was an impostor. Sometimes the package was treated as if it had the 9999.0.0 version, and other times it was treated as if it had the version specified in the package.json.</p>
+
+<h2 id="a_better_way">A better way</h2>
+
+<p>For npm 1.0, we backed up and looked at what the actual use cases were. Most of the time when you link something you want one of the following:</p>
+
+<ol>
+<li>globally install this package I&#8217;m working on so that I can run the command it creates and test its stuff as I work on it.</li>
+<li>locally install my thing into some <em>other</em> thing that depends on it, so that the other thing can <code>require()</code> it.</li>
+</ol>
+
+<p>And, in both cases, changes should be immediately apparent and not require any re-linking.</p>
+
+<p><em>Also</em>, there&#8217;s a third use case that I didn&#8217;t really appreciate until I started writing more programs that had more dependencies:</p>
+
+<ol start="3"> <li><p>Globally install something, and use it in development in a bunch of projects, and then update them all at once so that they all use the latest version. </ol>
+
+<p>Really, the second case above is a special-case of this third case.</p>
+
+<h2 id="link_devel_global">Link devel &rarr; global</h2>
+
+<p>The first step is to link your local project into the global install space. (See <a href="http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/">global vs local installation</a> for more on this global/local business.)</p>
+
+<p>I do this as I&#8217;m developing node projects (including npm itself).</p>
+
+<pre><code>cd ~/dev/js/node-tap  # go into the project dir
+npm link              # create symlinks into {prefix}
+</code></pre>
+
+<p>Because of how I have my computer set up, with <code>/usr/local</code> as my install prefix, I end up with a symlink from <code>/usr/local/lib/node_modules/tap</code> pointing to <code>~/dev/js/node-tap</code>, and the executable linked to <code>/usr/local/bin/tap</code>.</p>
+
+<p>Of course, if you <a href="http://blog.nodejs.org/2011/04/04/development-environment/">set your paths differently</a>, then you&#8217;ll have different results. (That&#8217;s why I tend to talk in terms of <code>prefix</code> rather than <code>/usr/local</code>.)</p>
+
+<h2 id="link_global_local">Link global &rarr; local</h2>
+
+<p>When you want to link the globally-installed package into your local development folder, you run <code>npm link pkg</code> where <code>pkg</code> is the name of the package that you want to install.</p>
+
+<p>For example, let&#8217;s say that I wanted to write some tap tests for my node-glob package. I&#8217;d <em>first</em> do the steps above to link tap into the global install space, and <em>then</em> I&#8217;d do this:</p>
+
+<pre><code>cd ~/dev/js/node-glob  # go to the project that uses the thing.
+npm link tap           # link the global thing into my project.
+</code></pre>
+
+<p>Now when I make changes in <code>~/dev/js/node-tap</code>, they&#8217;ll be immediately reflected in <code>~/dev/js/node-glob/node_modules/tap</code>.</p>
+
+<h2 id="link_to_stuff_you_don8217t_build">Link to stuff you <em>don&#8217;t</em> build</h2>
+
+<p>Let&#8217;s say I have 15 sites that all use express. I want the benefits of local development, but I also want to be able to update all my dev folders at once. You can globally install express, and then link it into your local development folder.</p>
+
+<pre><code>npm install express -g  # install express globally
+cd ~/dev/js/my-blog     # development folder one
+npm link express        # link the global express into ./node_modules
+cd ~/dev/js/photo-site  # other project folder
+npm link express        # link express into here, as well
+
+                        # time passes
+                        # TJ releases some new stuff.
+                        # you want this new stuff.
+
+npm update express -g   # update the global install.
+                        # this also updates my project folders.
+</code></pre>
+
+<h2 id="caveat_not_for_real_servers">Caveat: Not For Real Servers</h2>
+
+<p>npm link is a development tool. It&#8217;s <em>awesome</em> for managing packages on your local development box. But deploying with npm link is basically asking for problems, since it makes it super easy to update things without realizing it.</p>
+
+<h2 id="caveat_2_sorry_windows">Caveat 2: Sorry, Windows!</h2>
+
+<p>I highly doubt that a native Windows node will ever have comparable symbolic link support to what Unix systems provide.  I know that there are junctions and such, and I've heard legends about symbolic links on Windows 7.</p>
+
+<p>When there is a native windows port of Node, if that native windows port has `fs.symlink` and `fs.readlink` support that is exactly identical to the way that they work on Unix, then this should work fine.</p>
+
+<p>But I wouldn't hold my breath.  Any bugs about this not working on a native Windows system (ie, not Cygwin) will most likely be closed with <code>wontfix</code>.</p>
+
+
+<h2 id="aside_credit_where_credit8217s_due">Aside: Credit where Credit&#8217;s Due</h2>
+
+<p>Back before the Great Package Management Wars of Node 0.1, before npm or kiwi or mode or seed.js could do much of anything, and certainly before any of them had more than 2 users, Mikeal Rogers invited me to the Couch.io offices for lunch to talk about this npm registry thingie I&#8217;d mentioned wanting to build. (That is, to convince me to use CouchDB for it.)</p>
+
+<p>Since he was volunteering to build the first version of it, and since couch is pretty much the ideal candidate for this use-case, it was an easy sell.</p>
+
+<p>While I was there, he said, &#8220;Look. You need to be able to link a project directory as if it was installed as a package, and then have it all Just Work. Can you do that?&#8221;</p>
+
+<p>I was like, &#8220;Well, I don&#8217;t know&#8230; I mean, there&#8217;s these edge cases, and it doesn&#8217;t really fit with the existing folder structure very well&#8230;&#8221;</p>
+
+<p>&#8220;Dude. Either you do it, or I&#8217;m going to have to do it, and then there&#8217;ll be <em>another</em> package manager in node, instead of writing a registry for npm, and it won&#8217;t be as good anyway. Don&#8217;t be python.&#8221;</p>
+
+<p>The rest is history.</p>
diff --git a/locale/uk/blog/npm/npm-1-0-released.md b/locale/uk/blog/npm/npm-1-0-released.md
new file mode 100755
index 0000000000000..abc105708d448
--- /dev/null
+++ b/locale/uk/blog/npm/npm-1-0-released.md
@@ -0,0 +1,39 @@
+---
+title: "npm 1.0: Released"
+author: Isaac Schlueter
+date: 2011-05-01T15:09:45.000Z
+status: publish
+category: npm
+slug: npm-1-0-released
+layout: blog-post.hbs
+---
+
+<p>npm 1.0 has been released. Here are the highlights:</p>
+
+<ul> <li><a href="http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/">Global vs local installation</a></li> <li><a href="http://blog.nodejs.org/2011/03/17/npm-1-0-the-new-ls/">ls displays a tree</a>, instead of being a remote search</li> <li>No more &#8220;activation&#8221; concept - dependencies are nested</li> <li><a href="http://blog.nodejs.org/2011/04/06/npm-1-0-link/">Updates to link command</a></li> <li>Install script cleans up any 0.x cruft it finds. (That is, it removes old packages, so that they can be installed properly.)</li> <li>Simplified &#8220;search&#8221; command. One line per package, rather than one line per version.</li> <li>Renovated &#8220;completion&#8221; approach</li> <li>More help topics</li> <li>Simplified folder structure</li> </ul>
+
+<p>The focus is on npm being a development tool, rather than an apt-wannabe.</p>
+
+<h2 id="installing_it">Installing it</h2>
+
+<p>To get the new version, run this command:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl https://npmjs.com/install.sh | sh </code></pre>
+
+<p>This will prompt to ask you if it&#8217;s ok to remove all the old 0.x cruft. If you want to not be asked, then do this:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl https://npmjs.com/install.sh | clean=yes sh </code></pre>
+
+<p>Or, if you want to not do the cleanup, and leave the old stuff behind, then do this:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>curl https://npmjs.com/install.sh | clean=no sh </code></pre>
+
+<p>A lot of people in the node community were brave testers and helped make this release a lot better (and swifter) than it would have otherwise been. Thanks :)</p>
+
+<h2 id="code_freeze">Code Freeze</h2>
+
+<p>npm will not have any major feature enhancements or architectural changes <span style="border-bottom:1px dotted;cursor:default;" title="That is, the freeze ends no sooner than November 1, 2011">for at least 6 months</span>. There are interesting developments planned that leverage npm in some ways, but it&#8217;s time to let the client itself settle. Also, I want to focus attention on some other problems for a little while.</p>
+
+<p>Of course, <a href="https://github.com/isaacs/npm/issues">bug reports</a> are always welcome.</p>
+
+<p>See you at NodeConf!</p>
diff --git a/locale/uk/blog/npm/npm-1-0-the-new-ls.md b/locale/uk/blog/npm/npm-1-0-the-new-ls.md
new file mode 100755
index 0000000000000..b2b72067e91fa
--- /dev/null
+++ b/locale/uk/blog/npm/npm-1-0-the-new-ls.md
@@ -0,0 +1,147 @@
+---
+title: "npm 1.0: The New 'ls'"
+author: Isaac Schlueter
+date: 2011-03-18T06:22:17.000Z
+status: publish
+category: npm
+slug: npm-1-0-the-new-ls
+layout: blog-post.hbs
+---
+
+<p><em>This is the first in a series of hopefully more than 1 posts, each detailing some aspect of npm 1.0.</em></p>
+
+<p>In npm 0.x, the <code>ls</code> command was a combination of both searching the registry as well as reporting on what you have installed.</p>
+
+<p>As the registry has grown in size, this has gotten unwieldy.  Also, since npm 1.0 manages dependencies differently, nesting them in <code>node_modules</code> folder and installing locally by default, there are different things that you want to view.</p>
+
+<p>The functionality of the <code>ls</code> command was split into two different parts.  <code>search</code> is now the way to find things on the registry (and it only reports one line per package, instead of one line per version), and <code>ls</code> shows a tree view of the packages that are installed locally.</p>
+
+<p>Here&#8217;s an example of the output:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls
+npm@1.0.0 /Users/isaacs/dev-src/js/npm
+├── semver@1.0.1 
+├─┬ ronn@0.3.5 
+│ └── opts@1.2.1 
+└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span> 
+  ├─┬ connect@1.1.0 
+  │ ├── qs@0.0.7 
+  │ └── mime@1.2.1 
+  ├── mime@1.2.1 
+  └── qs@0.0.7
+</code></pre>
+
+<p>This is after I&#8217;ve done <code>npm install semver ronn express</code> in the npm source directory.  Since express isn&#8217;t actually a dependency of npm, it shows up with that &#8220;extraneous&#8221; marker.</p>
+
+<p>Let&#8217;s see what happens when we create a broken situation:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ rm -rf ./node_modules/express/node_modules/connect
+$ npm ls
+npm@1.0.0 /Users/isaacs/dev-src/js/npm
+├── semver@1.0.1 
+├─┬ ronn@0.3.5 
+│ └── opts@1.2.1 
+└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span> 
+  ├── <span style="background:#000;color:#f00;">UNMET DEPENDENCY</span> connect &gt;= 1.1.0 &lt; 2.0.0
+  ├── mime@1.2.1 
+  └── qs@0.0.7
+</code></pre>
+
+<p>Tree views are great for human readability, but some times you want to pipe that stuff to another program.  For that output, I took the same datastructure, but instead of building up a treeview string for each line, it spits out just the folders like this:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -p
+/Users/isaacs/dev-src/js/npm
+/Users/isaacs/dev-src/js/npm/node_modules/semver
+/Users/isaacs/dev-src/js/npm/node_modules/ronn
+/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts
+/Users/isaacs/dev-src/js/npm/node_modules/express
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/qs
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/mime
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/mime
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/qs
+</code></pre>
+
+<p>Since you sometimes want a bigger view, I added the <code>--long</code> option to (shorthand: <code>-l</code>) to spit out more info:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -l
+npm@1.0.0 
+│ /Users/isaacs/dev-src/js/npm
+│ A package manager for node
+│ git://github.com/isaacs/npm.git
+│ https://npmjs.com/
+├── semver@1.0.1 
+│   ./node_modules/semver
+│   The semantic version parser used by npm.
+│   git://github.com/isaacs/node-semver.git
+├─┬ ronn@0.3.5 
+│ │ ./node_modules/ronn
+│ │ markdown to roff and html converter
+│ └── opts@1.2.1 
+│     ./node_modules/ronn/node_modules/opts
+│     Command line argument parser written in the style of commonjs. To be used with node.js
+└─┬ express@2.0.0rc3 <span style="background:#000;color:#0f0;">extraneous</span> 
+  │ ./node_modules/express
+  │ Sinatra inspired web development framework
+  ├─┬ connect@1.1.0 
+  │ │ ./node_modules/express/node_modules/connect
+  │ │ High performance middleware framework
+  │ │ git://github.com/senchalabs/connect.git
+  │ ├── qs@0.0.7 
+  │ │   ./node_modules/express/node_modules/connect/node_modules/qs
+  │ │   querystring parser
+  │ └── mime@1.2.1 
+  │     ./node_modules/express/node_modules/connect/node_modules/mime
+  │     A comprehensive library for mime-type mapping
+  ├── mime@1.2.1 
+  │   ./node_modules/express/node_modules/mime
+  │   A comprehensive library for mime-type mapping
+  └── qs@0.0.7 
+      ./node_modules/express/node_modules/qs
+      querystring parser
+
+$ npm ls -lp
+/Users/isaacs/dev-src/js/npm:npm@1.0.0::::
+/Users/isaacs/dev-src/js/npm/node_modules/semver:semver@1.0.1::::
+/Users/isaacs/dev-src/js/npm/node_modules/ronn:ronn@0.3.5::::
+/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts:opts@1.2.1::::
+/Users/isaacs/dev-src/js/npm/node_modules/express:express@2.0.0rc3:EXTRANEOUS:::
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect:connect@1.1.0::::
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/qs:qs@0.0.7::::
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/connect/node_modules/mime:mime@1.2.1::::
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/mime:mime@1.2.1::::
+/Users/isaacs/dev-src/js/npm/node_modules/express/node_modules/qs:qs@0.0.7::::
+</code></pre>
+
+<p>And, if you want to get at the globally-installed modules, you can use ls with the global flag:</p>
+
+<pre style="background:#333;color:#ccc;overflow:auto;padding:2px;"><code>$ npm ls -g
+/usr/local
+├─┬ A@1.2.3 -&gt; /Users/isaacs/dev-src/js/A
+│ ├── B@1.2.3 -&gt; /Users/isaacs/dev-src/js/B
+│ └─┬ npm@0.3.15 
+│   └── semver@1.0.1 
+├─┬ B@1.2.3 -&gt; /Users/isaacs/dev-src/js/B
+│ └── A@1.2.3 -&gt; /Users/isaacs/dev-src/js/A
+├── glob@2.0.5 
+├─┬ npm@1.0.0 -&gt; /Users/isaacs/dev-src/js/npm
+│ ├── semver@1.0.1 
+│ └─┬ ronn@0.3.5 
+│   └── opts@1.2.1 
+└── supervisor@0.1.2 -&gt; /Users/isaacs/dev-src/js/node-supervisor
+
+$ npm ls -gpl
+/usr/local:::::
+/usr/local/lib/node_modules/A:A@1.2.3::::/Users/isaacs/dev-src/js/A
+/usr/local/lib/node_modules/A/node_modules/npm:npm@0.3.15::::/Users/isaacs/dev-src/js/A/node_modules/npm
+/usr/local/lib/node_modules/A/node_modules/npm/node_modules/semver:semver@1.0.1::::/Users/isaacs/dev-src/js/A/node_modules/npm/node_modules/semver
+/usr/local/lib/node_modules/B:B@1.2.3::::/Users/isaacs/dev-src/js/B
+/usr/local/lib/node_modules/glob:glob@2.0.5::::
+/usr/local/lib/node_modules/npm:npm@1.0.0::::/Users/isaacs/dev-src/js/npm
+/usr/local/lib/node_modules/npm/node_modules/semver:semver@1.0.1::::/Users/isaacs/dev-src/js/npm/node_modules/semver
+/usr/local/lib/node_modules/npm/node_modules/ronn:ronn@0.3.5::::/Users/isaacs/dev-src/js/npm/node_modules/ronn
+/usr/local/lib/node_modules/npm/node_modules/ronn/node_modules/opts:opts@1.2.1::::/Users/isaacs/dev-src/js/npm/node_modules/ronn/node_modules/opts
+/usr/local/lib/node_modules/supervisor:supervisor@0.1.2::::/Users/isaacs/dev-src/js/node-supervisor
+</code></pre>
+
+<p>Those <code>-&gt;</code> flags are indications that the package is link-installed, which will be covered in the next installment.</p>
diff --git a/locale/uk/blog/npm/peer-dependencies.md b/locale/uk/blog/npm/peer-dependencies.md
new file mode 100755
index 0000000000000..3158b7a810abb
--- /dev/null
+++ b/locale/uk/blog/npm/peer-dependencies.md
@@ -0,0 +1,137 @@
+---
+category: npm
+title: Peer Dependencies
+date: 2013-02-08T00:00:00.000Z
+author: Domenic Denicola
+slug: peer-dependencies
+layout: blog-post.hbs
+---
+
+<i>Reposted from [Domenic's
+blog](http://domenic.me/2013/02/08/peer-dependencies/) with
+permission.  Thanks!</i>
+
+npm is awesome as a package manager. In particular, it handles sub-dependencies very well: if my package depends on
+`request` version 2 and `some-other-library`, but `some-other-library` depends on `request` version 1, the resulting
+dependency graph looks like:
+
+```
+├── request@2.12.0
+└─┬ some-other-library@1.2.3
+  └── request@1.9.9
+```
+
+This is, generally, great: now `some-other-library` has its own copy of `request` v1 that it can use, while not
+interfering with my package's v2 copy. Everyone's code works!
+
+## The Problem: Plugins
+
+There's one use case where this falls down, however: *plugins*. A plugin package is meant to be used with another "host"
+package, even though it does not always directly *use* the host package. There are many examples of this pattern in the
+Node.js package ecosystem already:
+
+- Grunt [plugins](http://gruntjs.com/#plugins-all)
+- Chai [plugins](http://chaijs.com/plugins)
+- LevelUP [plugins](https://github.com/rvagg/node-levelup/wiki/Modules)
+- Express [middleware](http://expressjs.com/api.html#middleware)
+- Winston [transports](https://github.com/flatiron/winston/blob/master/docs/transports.md)
+
+Even if you're not familiar with any of those use cases, surely you recall "jQuery plugins" from back when you were a
+client-side developer: little `<script>`s you would drop into your page that would attach things to `jQuery.prototype`
+for your later convenience.
+
+In essence, plugins are designed to be used with host packages. But more importantly, they're designed to be used with
+*particular versions* of host packages. For example, versions 1.x and 2.x of my `chai-as-promised` plugin work with
+`chai` version 0.5, whereas versions 3.x work with `chai` 1.x. Or, in the faster-paced and less-semver–friendly world of
+Grunt plugins, version 0.3.1 of `grunt-contrib-stylus` works with `grunt` 0.4.0rc4, but breaks when used with `grunt`
+0.4.0rc5 due to removed APIs.
+
+As a package manager, a large part of npm's job when installing your dependencies is managing their versions. But its
+usual model, with a `"dependencies"` hash in `package.json`, clearly falls down for plugins. Most plugins never actually
+depend on their host package, i.e. grunt plugins never do `require("grunt")`, so even if plugins did put down their host
+package as a dependency, the downloaded copy would never be used. So we'd be back to square one, with your application
+possibly plugging in the plugin to a host package that it's incompatible with.
+
+Even for plugins that do have such direct dependencies, probably due to the host package supplying utility APIs,
+specifying the dependency in the plugin's `package.json` would result in a dependency tree with multiple copies of the
+host package—not what you want. For example, let's pretend that `winston-mail` 0.2.3 specified `"winston": "0.5.x"` in
+its `"dependencies"` hash, since that's the latest version it was tested against. As an app developer, you want the
+latest and greatest stuff, so you look up the latest versions of `winston` and of `winston-mail`, putting them in your
+`package.json` as
+
+```json
+{
+  "dependencies": {
+    "winston": "0.6.2",
+    "winston-mail": "0.2.3"
+  }
+}
+```
+
+But now, running `npm install` results in the unexpected dependency graph of
+
+```
+├── winston@0.6.2
+└─┬ winston-mail@0.2.3
+  └── winston@0.5.11
+```
+
+I'll leave the subtle failures that come from the plugin using a different Winston API than the main application to
+your imagination.
+
+## The Solution: Peer Dependencies
+
+What we need is a way of expressing these "dependencies" between plugins and their host package. Some way of saying, "I
+only work when plugged in to version 1.2.x of my host package, so if you install me, be sure that it's alongside a
+compatible host." We call this relationship a *peer dependency*.
+
+The peer dependency idea has been kicked around for [literally](https://github.com/isaacs/npm/issues/930)
+[years](https://github.com/isaacs/npm/issues/1400). After
+[volunteering](https://github.com/isaacs/npm/issues/1400#issuecomment-5932027) to get this done "over the weekend" nine
+months ago, I finally found a free weekend, and now peer dependencies are in npm!
+
+Specifically, they were introduced in a rudimentary form in npm 1.2.0, and refined over the next few releases into
+something I'm actually happy with. Today Isaac packaged up npm 1.2.10 into
+[Node.js 0.8.19](http://blog.nodejs.org/2013/02/06/node-v0-8-19-stable/), so if you've installed the latest version of
+Node, you should be ready to use peer dependencies!
+
+As proof, I present you the results of trying to install [`jitsu`](https://npmjs.org/package/jitsu) 0.11.6 with npm
+1.2.10:
+
+```
+npm ERR! peerinvalid The package flatiron does not satisfy its siblings' peerDependencies requirements!
+npm ERR! peerinvalid Peer flatiron-cli-config@0.1.3 wants flatiron@~0.1.9
+npm ERR! peerinvalid Peer flatiron-cli-users@0.1.4 wants flatiron@~0.3.0
+```
+
+As you can see, `jitsu` depends on two Flatiron-related packages, which themselves peer-depend on conflicting versions
+of Flatiron. Good thing npm was around to help us figure out this conflict, so it could be fixed in version 0.11.7!
+
+## Using Peer Dependencies
+
+Peer dependencies are pretty simple to use. When writing a plugin, figure out what version of the host package you
+peer-depend on, and add it to your `package.json`:
+
+```json
+{
+  "name": "chai-as-promised",
+  "peerDependencies": {
+    "chai": "1.x"
+  }
+}
+```
+
+Now, when installing `chai-as-promised`, the `chai` package will come along with it. And if later you try to install
+another Chai plugin that only works with 0.x versions of Chai, you'll get an error. Nice!
+
+One piece of advice: peer dependency requirements, unlike those for regular dependencies, *should be lenient*. You
+should not lock your peer dependencies down to specific patch versions. It would be really annoying if one Chai plugin
+peer-depended on Chai 1.4.1, while another depended on Chai 1.5.0, simply because the authors were lazy and didn't spend
+the time figuring out the actual minimum version of Chai they are compatible with.
+
+The best way to determine what your peer dependency requirements should be is to actually follow
+[semver](http://semver.org/). Assume that only changes in the host package's major version will break your plugin. Thus,
+if you've worked with every 1.x version of the host package, use `"~1.0"` or `"1.x"` to express this. If you depend on
+features introduced in 1.5.2, use `">= 1.5.2 < 2"`.
+
+Now go forth, and peer depend!
diff --git a/locale/uk/blog/release/index.md b/locale/uk/blog/release/index.md
new file mode 100755
index 0000000000000..6e9a656d4ab2b
--- /dev/null
+++ b/locale/uk/blog/release/index.md
@@ -0,0 +1,6 @@
+---
+title: Releases
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/release/v0.10.0.md b/locale/uk/blog/release/v0.10.0.md
new file mode 100755
index 0000000000000..c2e38cc4a9728
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.0.md
@@ -0,0 +1,490 @@
+---
+title: Node v0.10.0 (Stable)
+category: release
+version: 0.10.0
+date: 2013-03-11T16:00:00.000Z
+slug: node-v0-10-0-stable
+author: Isaac Z. Schlueter
+layout: blog-post.hbs
+---
+
+I am pleased to announce a new stable version of Node.
+
+This branch brings significant improvements to many areas, with a
+focus on API polish, ease of use, and backwards compatibility.
+
+For a very brief overview of the relevant API changes since v0.8,
+please see [the API changes wiki
+page](https://github.com/joyent/node/wiki/Api-changes-between-v0.8-and-v0.10).
+
+## Streams2
+
+In a [previous post](http://blog.nodejs.org/2012/12/20/streams2/), we
+introduced the
+"[Streams2](http://blog.nodejs.org/2012/12/20/streams2/)" API changes.
+If you haven't reviewed the changes, please go read that now (at least
+the tl;dr section).
+
+The changes to the stream interface have been a long time in the
+making.  Even from the earliest days of Node, we've all sort of known
+that this whole "data events come right away" and "pause() is
+advisory" stuff was unnecessarily awful.  In v0.10, we finally bit the
+bullet and committed to making drastic changes in order to make these
+things better.
+
+More importantly, all streams in Node-core are built using the same
+set of easily-extended base classes, so their behavior is much more
+consistent, and it's easier than ever to create streaming interfaces
+in your own userland programs.
+
+In fact, the Streams2 API was developed while using it for modules in
+the npm registry.  At the time of this writing, [37 published Node
+modules](https://npmjs.org/browse/depended/readable-stream) already
+are using the
+[readable-stream](https://npmjs.org/package/readable-stream) library
+as a dependency.  The readable-stream npm package allows you to use
+the new Stream interface in your legacy v0.8 codebase.
+
+## Domains and Error Handling
+
+The `domain` module has been elevated from "Experimental" to
+"Unstable" status.  It's been given more of a first-class treatment
+internally, making it easier to handle some of the edge cases that we
+found using Domains for error handling in v0.8.  Specifically, domain
+error handler no longer relies on `process.on('uncaughtException')`
+being raised, and the C++ code in Node is domain-aware.
+
+If you're not already using Domains to catch errors in your programs,
+and you've found yourself wishing that you could get better debugging
+information when errors are thrown (especially in the midst of lots of
+requests and asynchronous calls), then definitely check it out.
+
+## Faster process.nextTick
+
+In v0.8 (and before), the `process.nextTick()` function scheduled its
+callback using a spinner on the event loop.  This *usually* caused the
+callback to be fired before any other I/O.  However, it was not
+guaranteed.
+
+As a result, a lot of programs (including some parts of Node's
+internals) began using `process.nextTick` as a "do later, but before
+any actual I/O is performed" interface.  Since it usually works that
+way, it seemed fine.
+
+However, under load, it's possible for a server to have a lot of I/O
+scheduled, to the point where the `nextTick` gets preempted for
+something else.  This led to some odd errors and race conditions,
+which could not be fixed without changing the semantics of nextTick.
+
+So, that's what we did.  In v0.10, `nextTick` handlers are run right
+after each call from C++ into JavaScript.  That means that, if your
+JavaScript code calls `process.nextTick`, then the callback will fire
+as soon as the code runs to completion, but *before* going back to
+the event loop.  The race is over, and all is good.
+
+However, there are programs out in the wild that use recursive calls
+to `process.nextTick` to avoid pre-empting the I/O event loop for
+long-running jobs.  In order to avoid breaking horribly right away,
+Node will now print a deprecation warning, and ask you to use
+`setImmediate` for these kinds of tasks instead.
+
+## Latency and Idle Garbage Collection
+
+One of the toughest things to get right in a garbage collected
+language is garbage collection.  In order to try to avoid excessive
+memory usage, Node used to try to tell V8 to collect some garbage
+whenever the event loop was idle.
+
+However, knowing exactly when to do this is extremely difficult.
+There are different degrees of "idleness", and if you get it wrong,
+you can easily end up spending massive amounts of time collecting
+garbage when you'd least expect.  In practice, disabling the
+`IdleNotification` call yields better performance without any
+excessive memory usage, because V8 is pretty good at knowing when it's
+the best time to run GC.
+
+So, in v0.10, we just ripped that feature out.  (According to another
+point of view, we fixed the bug that it was ever there in the first
+place.)  As a result, latency is much more predictable and stable.
+You won't see a difference in the benchmarks as a result of this, but
+you'll probably find that your app's response times are more reliable.
+
+
+## Performance and Benchmarks
+
+When the Streams2 feature first landed in master, it disrupted a lot
+of things.  We focused first on correctness rather than speed, and as
+a result of that, we got a correct implementation that was
+significantly slower.
+
+We have a consistent rule in Node, that it cannot be allowed to get
+slower for our main use cases.  It took a lot of work, but over the
+last few months, we've managed to get v0.10 to an appropriate level of
+performance, without sacrificing the API goals that we had in mind.
+
+Benchmarks are complicated beasts.  Until this release, we've gotten
+by with a pretty ad-hoc approach to running benchmarks.  However, as
+we started actually having to track down regressions, the need for a
+more comprehensive approach was obvious.
+
+Work is underway to figure out the optimum way to get statistically
+significant benchmark results in an automated way.  As it is, we're
+still seeing significant jitter in some of the data, so take the red
+and green colors with a grain of salt.
+
+The benchmarks below were run on an Apple 13-inch, Late 2011 MacBook
+Pro with a 2.8 GHz Intel Core i7 processor, 8GB of 1333MHz DDR3 RAM,
+running OS X Lion 10.7.5 (11G63b).  The numbers are slightly different
+on Linux and SmartOS, but the conclusions are the same.  The [raw data
+is available](https://nodejs.org/benchmarks-v0.10-vs-v0.8/), as well.
+
+## Benchmarks: http
+
+Node is for websites, and websites run over HTTP, so this is the one
+that people usually care the most about:
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+http/cluster.js type=bytes length=4: <span style="background-color:#0f0;color:#000">v0.10: 16843</span> v0.8: 16202 ................. <span style="background-color:#0f0;color:#000">3.96%</span>
+http/cluster.js type=bytes length=1024: <span style="background-color:#0f0;color:#000">v0.10: 15505</span> v0.8: 15065 .............. <span style="background-color:#0f0;color:#000">2.92%</span>
+http/cluster.js type=bytes length=102400: v0.10: 1555.2 <span style="background-color:#f00;color:#fff">v0.8: 1566.3</span> ......... <span style="background-color:#f00;color:#fff">-0.71%</span>
+http/cluster.js type=buffer length=4: <span style="background-color:#0f0;color:#000">v0.10: 15308</span> v0.8: 14763 ................ <span style="background-color:#0f0;color:#000">3.69%</span>
+http/cluster.js type=buffer length=1024: <span style="background-color:#0f0;color:#000">v0.10: 15039</span> v0.8: 14830 ............. <span style="background-color:#0f0;color:#000">1.41%</span>
+http/cluster.js type=buffer length=102400: <span style="background-color:#0f0;color:#000">v0.10: 7584.6</span> v0.8: 7433.6 ......... <span style="background-color:#0f0;color:#000">2.03%</span>
+http/simple.js type=bytes length=4: <span style="background-color:#0f0;color:#000">v0.10: 12343</span> v0.8: 11761 .................. <span style="background-color:#0f0;color:#000">4.95%</span>
+http/simple.js type=bytes length=1024: <span style="background-color:#0f0;color:#000">v0.10: 11051</span> v0.8: 10287 ............... <span style="background-color:#0f0;color:#000">7.43%</span>
+http/simple.js type=bytes length=102400: v0.10: 853.19 <span style="background-color:#f00;color:#fff">v0.8: 892.75</span> .......... <span style="background-color:#f00;color:#fff">-4.43%</span>
+http/simple.js type=buffer length=4: <span style="background-color:#0f0;color:#000">v0.10: 11316</span> v0.8: 10728 ................. <span style="background-color:#0f0;color:#000">5.48%</span>
+http/simple.js type=buffer length=1024: <span style="background-color:#0f0;color:#000">v0.10: 11199</span> v0.8: 10429 .............. <span style="background-color:#0f0;color:#000">7.38%</span>
+http/simple.js type=buffer length=102400: <span style="background-color:#0f0;color:#000">v0.10: 4942.1</span> v0.8: 4822.9 .......... <span style="background-color:#0f0;color:#000">2.47%</span>
+</pre>
+
+What we see here is that, overall, HTTP is faster.  It's just slightly
+slower (1-5%) when sending extremely large string messages (ie
+`type=bytes` rather than `type=buffer`).  But otherwise, things are
+about the same, or slightly faster.
+
+## Benchmarks: fs
+
+The fs.ReadStream throughput is massively improved, and less affected
+by the chunk size argument:
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+fs/read-stream buf size=1024: <span style="background-color:#0f0;color:#000">v0.10</span>: 1106.6 v0.8: 60.597 ................... <span style="background-color:#0f0;color:#000">1726.12%</span>
+fs/read-stream buf size=4096: <span style="background-color:#0f0;color:#000">v0.10</span>: 1107.9 v0.8: 235.51 .................... <span style="background-color:#0f0;color:#000">370.44%</span>
+fs/read-stream buf size=65535: <span style="background-color:#0f0;color:#000">v0.10</span>: 1108.2 v0.8: 966.84 .................... <span style="background-color:#0f0;color:#000">14.62%</span>
+fs/read-stream buf size=1048576: <span style="background-color:#0f0;color:#000">v0.10</span>: 1103.3 v0.8: 959.66 .................. <span style="background-color:#0f0;color:#000">14.97%</span>
+fs/read-stream asc size=1024: <span style="background-color:#0f0;color:#000">v0.10</span>: 1081.5 v0.8: 62.218 ................... <span style="background-color:#0f0;color:#000">1638.21%</span>
+fs/read-stream asc size=4096: <span style="background-color:#0f0;color:#000">v0.10</span>: 1082.3 v0.8: 174.78 .................... <span style="background-color:#0f0;color:#000">519.21%</span>
+fs/read-stream asc size=65535: <span style="background-color:#0f0;color:#000">v0.10</span>: 1083.9 v0.8: 627.91 .................... <span style="background-color:#0f0;color:#000">72.62%</span>
+fs/read-stream asc size=1048576: <span style="background-color:#0f0;color:#000">v0.10</span>: 1083.2 v0.8: 627.49 .................. <span style="background-color:#0f0;color:#000">72.62%</span>
+fs/read-stream utf size=1024: <span style="background-color:#0f0;color:#000">v0.10</span>: 46.553 v0.8: 16.944 .................... <span style="background-color:#0f0;color:#000">174.74%</span>
+fs/read-stream utf size=4096: <span style="background-color:#0f0;color:#000">v0.10</span>: 46.585 v0.8: 32.933 ..................... <span style="background-color:#0f0;color:#000">41.45%</span>
+fs/read-stream utf size=65535: <span style="background-color:#0f0;color:#000">v0.10</span>: 46.57 v0.8: 45.832 ...................... <span style="background-color:#0f0;color:#000">1.61%</span>
+fs/read-stream utf size=1048576: <span style="background-color:#0f0;color:#000">v0.10</span>: 46.576 v0.8: 45.884 ................... <span style="background-color:#0f0;color:#000">1.51%</span>
+</pre>
+
+The fs.WriteStream throughput increases considerably, for most
+workloads.  As the size of the chunk goes up, the speed is limited by
+the underlying system and the cost of string conversion, so v0.8 and
+v0.10 converge.  But for smaller chunk sizes (like you'd be more
+likely to see in real applications), v0.10 is a significant
+improvement.
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+fs/write-stream buf size=2: <span style="background-color:#0f0;color:#000">v0.10</span>: 0.12434 v0.8: 0.10097 ..................... <span style="background-color:#0f0;color:#000">23.15%</span>
+fs/write-stream buf size=1024: <span style="background-color:#0f0;color:#000">v0.10</span>: 59.926 v0.8: 49.822 .................... <span style="background-color:#0f0;color:#000">20.28%</span>
+fs/write-stream buf size=65535: <span style="background-color:#0f0;color:#000">v0.10</span>: 180.41 v0.8: 179.26 .................... <span style="background-color:#0f0;color:#000">0.64%</span>
+fs/write-stream buf size=1048576: <span style="background-color:#0f0;color:#000">v0.10</span>: 181.49 v0.8: 176.73 .................. <span style="background-color:#0f0;color:#000">2.70%</span>
+fs/write-stream asc size=2: <span style="background-color:#0f0;color:#000">v0.10</span>: 0.11133 v0.8: 0.08123 ..................... <span style="background-color:#0f0;color:#000">37.06%</span>
+fs/write-stream asc size=1024: <span style="background-color:#0f0;color:#000">v0.10</span>: 53.023 v0.8: 36.708 .................... <span style="background-color:#0f0;color:#000">44.45%</span>
+fs/write-stream asc size=65535: <span style="background-color:#0f0;color:#000">v0.10</span>: 178.54 v0.8: 174.36 .................... <span style="background-color:#0f0;color:#000">2.39%</span>
+fs/write-stream asc size=1048576: <span style="background-color:#0f0;color:#000">v0.10</span>: 185.27 v0.8: 183.65 .................. <span style="background-color:#0f0;color:#000">0.88%</span>
+fs/write-stream utf size=2: <span style="background-color:#0f0;color:#000">v0.10</span>: 0.11165 v0.8: 0.080079 .................... <span style="background-color:#0f0;color:#000">39.43%</span>
+fs/write-stream utf size=1024: <span style="background-color:#0f0;color:#000">v0.10</span>: 45.166 v0.8: 32.636 .................... <span style="background-color:#0f0;color:#000">38.39%</span>
+fs/write-stream utf size=65535: <span style="background-color:#0f0;color:#000">v0.10</span>: 176.1 v0.8: 175.34 ..................... <span style="background-color:#0f0;color:#000">0.43%</span>
+fs/write-stream utf size=1048576: v0.10: 182.3 <span style="background-color:#f00;color:#fff">v0.8</span>: 182.82 .................. <span style="background-color:#f00;color:#fff">-0.28%</span>
+</pre>
+
+## Benchmark: tls
+
+We switched to a newer version of OpenSSL, and the CryptoStream
+implementation was significantly changed to support the Stream2
+interface.
+
+The throughput of TLS connections is massively improved:
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+tls/throughput.js dur=5 type=buf size=2: <span style="background-color:#0f0;color:#000">v0.10: 0.90836</span> v0.8: 0.32381 ....... <span style="background-color:#0f0;color:#000">180.52%</span>
+tls/throughput.js dur=5 type=buf size=1024: <span style="background-color:#0f0;color:#000">v0.10: 222.84</span> v0.8: 116.75 ....... <span style="background-color:#0f0;color:#000">90.87%</span>
+tls/throughput.js dur=5 type=buf size=1048576: <span style="background-color:#0f0;color:#000">v0.10: 403.17</span> v0.8: 360.42 .... <span style="background-color:#0f0;color:#000">11.86%</span>
+tls/throughput.js dur=5 type=asc size=2: <span style="background-color:#0f0;color:#000">v0.10: 0.78323</span> v0.8: 0.28761 ....... <span style="background-color:#0f0;color:#000">172.32%</span>
+tls/throughput.js dur=5 type=asc size=1024: <span style="background-color:#0f0;color:#000">v0.10: 199.7</span> v0.8: 102.46 ........ <span style="background-color:#0f0;color:#000">94.91%</span>
+tls/throughput.js dur=5 type=asc size=1048576: <span style="background-color:#0f0;color:#000">v0.10: 375.85</span> v0.8: 317.81 .... <span style="background-color:#0f0;color:#000">18.26%</span>
+tls/throughput.js dur=5 type=utf size=2: <span style="background-color:#0f0;color:#000">v0.10: 0.78503</span> v0.8: 0.28834 ....... <span style="background-color:#0f0;color:#000">172.26%</span>
+tls/throughput.js dur=5 type=utf size=1024: <span style="background-color:#0f0;color:#000">v0.10: 182.43</span> v0.8: 100.3 ........ <span style="background-color:#0f0;color:#000">81.88%</span>
+tls/throughput.js dur=5 type=utf size=1048576: <span style="background-color:#0f0;color:#000">v0.10: 333.05</span> v0.8: 301.57 .... <span style="background-color:#0f0;color:#000">10.44%</span>
+</pre>
+
+However, the speed at which we can make connections is somewhat
+reduced:
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+tls/tls-connect.js concurrency=1 dur=5: v0.10: 433.05 <span style="background-color:#f00;color:#fff">v0.8: 560.43</span> .......... <span style="background-color:#f00;color:#fff">-22.73%</span>
+tls/tls-connect.js concurrency=10 dur=5: v0.10: 438.38 <span style="background-color:#f00;color:#fff">v0.8: 577.93</span> ......... <span style="background-color:#f00;color:#fff">-24.15%</span>
+</pre>
+
+At this point, it seems like the connection speed is related to the
+new version of OpenSSL, but we'll be tracking that further.
+
+TLS still has more room for improvement, but this throughput increase
+is a huge step.
+
+## Benchmark: net
+
+The net throughput tests tell an interesting story.  When sending
+ascii messages, they're much faster.
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+net/net-c2s.js len=102400 type=asc dur=5: <span style="background-color:#0f0;color:#000">v0.10: 3.6551</span> v0.8: 2.0478 ......... <span style="background-color:#0f0;color:#000">78.49%</span>
+net/net-c2s.js len=16777216 type=asc dur=5: <span style="background-color:#0f0;color:#000">v0.10: 3.2428</span> v0.8: 2.0503 ....... <span style="background-color:#0f0;color:#000">58.16%</span>
+net/net-pipe.js len=102400 type=asc dur=5: <span style="background-color:#0f0;color:#000">v0.10: 4.4638</span> v0.8: 3.0798 ........ <span style="background-color:#0f0;color:#000">44.94%</span>
+net/net-pipe.js len=16777216 type=asc dur=5: <span style="background-color:#0f0;color:#000">v0.10: 3.9449</span> v0.8: 2.8906 ...... <span style="background-color:#0f0;color:#000">36.48%</span>
+net/net-s2c.js len=102400 type=asc dur=5: <span style="background-color:#0f0;color:#000">v0.10: 3.6306</span> v0.8: 2.0415 ......... <span style="background-color:#0f0;color:#000">77.84%</span>
+net/net-s2c.js len=16777216 type=asc dur=5: <span style="background-color:#0f0;color:#000">v0.10: 3.2271</span> v0.8: 2.0636 ....... <span style="background-color:#0f0;color:#000">56.38%</span>
+</pre>
+
+When sending Buffer messages, they're just slightly slower.  (This
+difference is less than the typical variability of the test, but they
+were run 20 times and outliers were factored out for this post.)
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+net/net-c2s.js len=102400 type=buf dur=5: v0.10: 5.5597 <span style="background-color:#f00;color:#fff">v0.8: 5.6967</span> ......... <span style="background-color:#f00;color:#fff">-2.40%</span>
+net/net-c2s.js len=16777216 type=buf dur=5: v0.10: 6.1843 <span style="background-color:#f00;color:#fff">v0.8: 6.4595</span> ....... <span style="background-color:#f00;color:#fff">-4.26%</span>
+net/net-pipe.js len=102400 type=buf dur=5: v0.10: 5.6898 <span style="background-color:#f00;color:#fff">v0.8: 5.986</span> ......... <span style="background-color:#f00;color:#fff">-4.95%</span>
+net/net-pipe.js len=16777216 type=buf dur=5: <span style="background-color:#0f0;color:#000">v0.10: 5.9643</span> v0.8: 5.9251 ....... <span style="background-color:#0f0;color:#000">0.66%</span>
+net/net-s2c.js len=102400 type=buf dur=5: v0.10: 5.473 <span style="background-color:#f00;color:#fff">v0.8: 5.6492</span> .......... <span style="background-color:#f00;color:#fff">-3.12%</span>
+net/net-s2c.js len=16777216 type=buf dur=5: v0.10: 6.1986 <span style="background-color:#f00;color:#fff">v0.8: 6.3236</span> ....... <span style="background-color:#f00;color:#fff">-1.98%</span>
+</pre>
+
+When sending utf-8 messages, they're a bit slower than that:
+
+<pre style="background-color:#333;color:#eee;font-size:12px">
+net/net-c2s.js len=102400 type=utf dur=5: v0.10: 2.2671 <span style="background-color:#f00;color:#fff">v0.8: 2.4606</span> ......... <span style="background-color:#f00;color:#fff">-7.87%</span>
+net/net-c2s.js len=16777216 type=utf dur=5: v0.10: 1.7434 <span style="background-color:#f00;color:#fff">v0.8: 1.8771</span> ....... <span style="background-color:#f00;color:#fff">-7.12%</span>
+net/net-pipe.js len=102400 type=utf dur=5: v0.10: 3.1679 <span style="background-color:#f00;color:#fff">v0.8: 3.5401</span> ....... <span style="background-color:#f00;color:#fff">-10.51%</span>
+net/net-pipe.js len=16777216 type=utf dur=5: v0.10: 2.5615 <span style="background-color:#f00;color:#fff">v0.8: 2.7002</span> ...... <span style="background-color:#f00;color:#fff">-5.14%</span>
+net/net-s2c.js len=102400 type=utf dur=5: v0.10: 2.2495 <span style="background-color:#f00;color:#fff">v0.8: 2.4578</span> ......... <span style="background-color:#f00;color:#fff">-8.48%</span>
+net/net-s2c.js len=16777216 type=utf dur=5: v0.10: 1.7733 <span style="background-color:#f00;color:#fff">v0.8: 1.8975</span> ....... <span style="background-color:#f00;color:#fff">-6.55%</span>
+</pre>
+
+You might suspect that this is a result of the new Streams
+implementation.  However, running the same benchmarks without using
+any of the code in Node's `lib/` folder, just calling into the C++
+bindings directly, yields consistently similar results.
+
+This slight regression comes along with significant improvements in
+everything that sits on *top* of TCP (that is, TLS and HTTP).
+
+Keep an eye out for more work in this area.  Fast is never fast
+enough!
+
+
+## Continuous Integration
+
+To support a higher degree of stability, and hopefully catch issues
+sooner, we have a Jenkins instance running every commit through the
+test suite, on each operating system we support.  You can watch the
+action at [the Node Jenkins web portal](http://jenkins.nodejs.org/).
+
+Coming soon, we'll have automatically generated nightly builds every
+day, and eventually, the entire release process will be automated.
+
+While we're pretty rigorous about running tests and benchmarks, it's
+easy for things to slip by, and our ad-hoc methods are not cutting it
+any longer.  This promises a much lower incidence of the sort of
+regressions that delayed the release of v0.10 for several months.
+
+
+## Growing Out
+
+A year ago, we said that the innovation in the Node universe would be
+happening in userland modules.  Now, we've finally taken that to its
+logical conclusion, and moved our iteration on **core** modules into
+userland as well.  Things like `readable-stream` and `tlsnappy` allow
+us to get much more user-testing, experimentation, and contributions
+to a feature.
+
+The userland module can live on as a compatibility layer so that
+libraries can use the new features, even if they need to support older
+versions of Node.  This is a remarkably effective way to do node-core
+development.  Future developments will continue to be iterated in
+userland modules.
+
+## Growing Up <a name="enterprise"></a>
+
+The question comes up pretty often whether Node is "ready for prime
+time" yet.  I usually answer that it depends on your requirements for
+"prime time", but Node has been powering some high profile sites, and
+the options for "real" companies using Node for The Business are
+better than ever.
+
+It would be out of scope to try to provide an exhaustive list of all
+the companies using Node, and all of the options for support and
+training.  However, here are a few resources that are quickly
+expanding to fill the "Enterprise Node" space.
+
+For those looking for commercial support,
+[StrongLoop](http://strongloop.com/) (Ben Noordhuis & Bert Belder's
+company) has released a distribution containing node v0.10 that they
+will support on Windows, Mac, Red Hat/Fedora, Debian/Ubuntu and
+multiple cloud platforms. You can [download their Node distribution
+here](http://strongloop.com/products#downloads).
+
+[The Node Firm](http://thenodefirm.com) is a worldwide network of key
+Node contributors and community members that help organizations
+succeed with Node.  Through corporate training, consulting,
+architectural guidance, and [ongoing consulting
+subscriptions](http://thenodefirm.com/nodejs-consulting-subscriptions),
+they have helped Skype, Qualcomm, and others quickly and effectively
+embrace Node.
+
+Node would not be what it is without [npm](https://npmjs.org/), and
+npm would not be what it is without the registry of published modules.
+However, relying on the public registry is problematic for many
+enterprise use-cases.  [Iris npm](https://www.irisnpm.com/) is a fully
+managed private npm registry, from [Iris
+Couch](http://www.iriscouch.com), the team that runs the public npm
+registry in production.
+
+[Joyent](http://joyent.com), the company you probably know as the
+custodian of the Node project, provides high performance cloud
+infrastructure specializing in real-time web and mobile applications.
+Joyent uses Node extensively throughout their stack, and provides
+impressive [post-mortem debugging and real-time performance analysis
+tools](http://dtrace.org/blogs/dap/2012/05/31/debugging-node-js-in-production-fluent-slides/)
+for Node.js applications.  They are also my employer, so I'd probably
+have to get a "real" job if they weren't sponsoring Node :)
+
+## Next Up: v0.12
+
+The focus of Node v0.12 will be to make HTTP better.  Node's current
+HTTP implementation is pretty good, and clearly sufficient to do a lot
+of interesting things with.  However:
+
+1. The codebase is a mess.  We share a lot of code between the Client
+   and Server implementations, but do so in a way that makes it
+   unnecessarily painful to read the code or fix bugs.  It will be
+   split up so that client and server are clearly separated, and have
+   cleaner interfaces.
+2. The socket pooling behavior is confusing and weird.  We will be
+   adding configurable socket pooling as a standalone utility.  This
+   will allow us to implement KeepAlive behavior in a more reasonable
+   manner, as well as providing something that you can use in your own
+   programs.
+
+There is some experimentation going on in the
+[tlsnappy](https://github.com/indutny/tlsnappy) module, which may make
+its way back into the core TLS implementation and speed things up
+considerably.
+
+## 1.0
+
+After 0.12, the next major stable release will be 1.0.  At that point,
+very little will change in terms of the day-to-day operation of the
+project, but it will mark a significant milestone in terms of our
+stability and willingness to add new features.  However, we've already
+gotten strict about maintaining backwards compatibility, so this won't
+really be so much of a shift.
+
+New versions will still come out, especially to pull in new versions
+of our dependencies, and bugs will continue to be fixed.  There's been
+talk of pinning our release cycles to V8, and automating the release
+process in some interesting ways.
+
+The goal of Node has always been to eventually be "finished" with the
+core program.  Of course, that's a rather lofty goal, perhaps even
+impossible.  But as we take Node to more places, and use it in more
+ways, we're getting closer to the day when the relevant innovation
+happens outside of the core Node program.
+
+Stability in the platform enables growth on top of it.
+
+And now, the traditional release notes:
+
+## 2013.03.11, Version 0.10.0 (Stable)
+
+* npm: Upgrade to 1.2.14
+
+* core: Append filename properly in dlopen on windows (isaacs)
+
+* zlib: Manage flush flags appropriately (isaacs)
+
+* domains: Handle errors thrown in nested error handlers (isaacs)
+
+* buffer: Strip high bits when converting to ascii (Ben Noordhuis)
+
+* win/msi: Enable modify and repair (Bert Belder)
+
+* win/msi: Add feature selection for various Node parts (Bert Belder)
+
+* win/msi: use consistent registry key paths (Bert Belder)
+
+* child_process: support sending dgram socket (Andreas Madsen)
+
+* fs: Raise EISDIR on Windows when calling fs.read/write on a dir (isaacs)
+
+* unix: fix strict aliasing warnings, macro-ify functions (Ben Noordhuis)
+
+* unix: honor UV_THREADPOOL_SIZE environment var (Ben Noordhuis)
+
+* win/tty: fix typo in color attributes enumeration (Bert Belder)
+
+* win/tty: don't touch insert mode or quick edit mode (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.10.0/node-v0.10.0.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.0/node-v0.10.0.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.0/node-v0.10.0-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.0/x64/node-v0.10.0-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.0/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.0/node-v0.10.0-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.0/node-v0.10.0-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.0/node-v0.10.0-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.0/node-v0.10.0-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.0/
+
+Website: https://nodejs.org/docs/v0.10.0/
+
+Documentation: https://nodejs.org/docs/v0.10.0/api/
+
+Shasums:
+
+```
+b9e9bca99cdb5563cad3d3f04baa262e317b827c  node-v0.10.0-darwin-x64.tar.gz
+0227c9bc3df5b62267b9d4e3b0a92b3a70732229  node-v0.10.0-darwin-x86.tar.gz
+9f5f7350d6f889ea8e794516ecfea651e8e53d24  node-v0.10.0-linux-x64.tar.gz
+cc5f1cd6a2f2530bc400e761144bbaf8fcb66cc4  node-v0.10.0-linux-x86.tar.gz
+42c14b7eab398976b1ac0a8e6e96989059616af5  node-v0.10.0-sunos-x64.tar.gz
+ddcadbac66d1acea48aa6c5462d0a0d7308ea823  node-v0.10.0-sunos-x86.tar.gz
+70eacf2cca7abec79fac4ca502e8d99590a2108a  node-v0.10.0-x86.msi
+c48c269b9b0f0a95e6e9234d4597d1c8a1c45c5a  node-v0.10.0.pkg
+7321266347dc1c47ed2186e7d61752795ce8a0ef  node-v0.10.0.tar.gz
+f8c6f55469551243ea461f023cc57c024f57fef2  node.exe
+253ae79e411fcfddcf28861559ececb4b335db64  node.exp
+acb8febb5ea714c065f201ced5423b0838fdf1b6  node.lib
+0fdad1400036dd26d720070f783d3beeb3bb9c0a  node.pdb
+abcaf8ef606655a05e73ee5d06715ffd022aad22  x64/node-v0.10.0-x64.msi
+e5d0c235629b26430b6e07c07ee2c7dcda82f35e  x64/node.exe
+43b3fb3a6aaf6a04f578ee607a9455c1e23acf08  x64/node.exp
+87dd6eb6c8127a1af0dcca639961441fc303d75a  x64/node.lib
+50aca715777fa42b854e6cfc56b6199a54aabd3c  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.1.md b/locale/uk/blog/release/v0.10.1.md
new file mode 100755
index 0000000000000..888f589e84b32
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.1.md
@@ -0,0 +1,85 @@
+---
+date: 2013-03-21T16:09:59.000Z
+version: 0.10.1
+category: release
+title: Node v0.10.1 (Stable)
+slug: node-v0-10-1-stable
+layout: blog-post.hbs
+---
+
+2013.03.21, Version 0.10.1 (Stable)
+
+* npm: upgrade to 1.2.15
+
+* crypto: Improve performance of non-stream APIs (Fedor Indutny)
+
+* tls: always reset this.ssl.error after handling (Fedor Indutny)
+
+* tls: Prevent mid-stream hangs (Fedor Indutny, isaacs)
+
+* net: improve arbitrary tcp socket support (Ben Noordhuis)
+
+* net: handle 'finish' event only after 'connect' (Fedor Indutny)
+
+* http: Don't hot-path end() for large buffers (isaacs)
+
+* fs: Missing cb errors are deprecated, not a throw (isaacs)
+
+* fs: make write/appendFileSync correctly set file mode (Raymond Feng)
+
+* stream: Return self from readable.wrap (isaacs)
+
+* stream: Never call decoder.end() multiple times (Gil Pedersen)
+
+* windows: enable watching signals with process.on('SIGXYZ') (Bert Belder)
+
+* node: revert removal of MakeCallback (Trevor Norris)
+
+* node: Unwrap without aborting in handle fd getter (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.10.1/node-v0.10.1.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.1/node-v0.10.1.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.1/node-v0.10.1-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.1/x64/node-v0.10.1-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.1/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.1/node-v0.10.1-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.1/node-v0.10.1-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.1/node-v0.10.1-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.1/node-v0.10.1-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.1/
+
+Website: https://nodejs.org/docs/v0.10.1/
+
+Documentation: https://nodejs.org/docs/v0.10.1/api/
+
+Shasums:
+```
+e213170fe5ec7721b31149fba1a7a691c50b5379  node-v0.10.1-darwin-x64.tar.gz
+5526d189fa3180e11731e1aebb0f22c1c2fb3d8d  node-v0.10.1-darwin-x86.tar.gz
+ec0818d8f151d933ec79961374bf74d9855305a5  node-v0.10.1-linux-x64.tar.gz
+b6345e86bc52575f8cc275cda36b1295ed544139  node-v0.10.1-linux-x86.tar.gz
+e94cb3ab3ac5a8026564152798070e06f1ba3119  node-v0.10.1-sunos-x64.tar.gz
+a894eaca7f49077e48b1786071dbdf57a2ea704c  node-v0.10.1-sunos-x86.tar.gz
+3f64590730d8e24e57530192479fd39dafde13b5  node-v0.10.1-x86.msi
+b41c576c473a1ae44c3061fe4799362239f00d8f  node-v0.10.1.pkg
+d4d9ef3b70452112246ea2043ef75943611e3537  node-v0.10.1.tar.gz
+c034695812148c3fafe8b208203355d16289d1a7  node.exe
+9fac94cbe9431ca518fdb1eed1a1b240a58ac781  node.exp
+3571d5d7f9940f48b75f9a9b1fac8c8661e8ace2  node.lib
+74f9ea112e2da1c1837180422a20630bc92bd5c9  node.pdb
+0958d68900b80419e2af7a5448c4a451af06d0b4  x64/node-v0.10.1-x64.msi
+cc074b6c99cb1df01707ea12e986cf5bb4dc3c05  x64/node.exe
+f2746fea78ffb346e8ea979ea09924dc4408bcb9  x64/node.exp
+1f1d9d1ba0d9383ecc93e8d8a481b13db39dc5f8  x64/node.lib
+39a0a5a699e4a8cba44e618f6be6bd79f36a370f  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.10.md b/locale/uk/blog/release/v0.10.10.md
new file mode 100755
index 0000000000000..c557ebce39653
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.10.md
@@ -0,0 +1,66 @@
+---
+date: 2013-06-04T21:37:25.000Z
+version: 0.10.10
+category: release
+title: Node v0.10.10 (Stable)
+slug: node-v0-10-10-stable
+layout: blog-post.hbs
+---
+
+2013.06.04, Version 0.10.10 (Stable)
+
+* uv: Upgrade to 0.10.10
+
+* npm: Upgrade to 1.2.25
+
+* url: Properly parse certain oddly formed urls (isaacs)
+
+* stream: unshift('') is a noop (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.10.10/node-v0.10.10.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.10/node-v0.10.10.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.10/node-v0.10.10-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.10/x64/node-v0.10.10-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.10/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.10/node-v0.10.10-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.10/node-v0.10.10-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.10/node-v0.10.10-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.10/node-v0.10.10-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.10/
+
+Website: https://nodejs.org/docs/v0.10.10/
+
+Documentation: https://nodejs.org/docs/v0.10.10/api/
+
+Shasums:
+
+```
+d632cad2adb5b4eef7a94bc9e549579586b381f5  node-v0.10.10-darwin-x64.tar.gz
+6f74d0ca1a3bc810a4e73267451c0177be405874  node-v0.10.10-darwin-x86.tar.gz
+b8a1f1954027b88b9545f3a2161543635f2120e7  node-v0.10.10-linux-x64.tar.gz
+aae6893ee82cee09eec0351b770d4857e31e46b7  node-v0.10.10-linux-x86.tar.gz
+0004745f5c0f96efc85f2bd9d9df24b1b706f77e  node-v0.10.10-sunos-x64.tar.gz
+a4e623f6688fde7f30d720ac4b1228546da823db  node-v0.10.10-sunos-x86.tar.gz
+1f09e829c92274de13270a7519e9e1cd5788e0a8  node-v0.10.10-x86.msi
+24f7573e92060565ba84b7700efc4d9cf566e5ba  node-v0.10.10.pkg
+c21643a57b1ec9eca56e6deac22fe075616e0e9c  node-v0.10.10.tar.gz
+419fc85e5e16139260f7b2080ffbb66550fbe93f  node.exe
+bb2782228bf4f8783f9e6a9d1171f8ff0835c9b9  node.exp
+28ce8d1f8156e6a8bf38844738f4a76499e0d2ce  node.lib
+eb58da2b123bc7aaceaa37a7a0bcc048d8d8dcc1  node.pdb
+781f75fc1c7499edb8d7e247d774266d57514d21  x64/node-v0.10.10-x64.msi
+14b75f31d14ca2e0fb90308e98a3567c6de0434e  x64/node.exe
+c5723e00cc875543ae263121d34d204690561860  x64/node.exp
+df523e092ee9ff13b3acf4f4b574d043c0da6d9a  x64/node.lib
+db2a8874a3bc7cd21b8b29bc7faa5f75c8af0414  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.11.md b/locale/uk/blog/release/v0.10.11.md
new file mode 100755
index 0000000000000..82eca86ec0d05
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.11.md
@@ -0,0 +1,73 @@
+---
+date: 2013-06-13T18:34:24.000Z
+version: 0.10.11
+category: release
+title: Node v0.10.11 (Stable)
+slug: node-v0-10-11-stable
+layout: blog-post.hbs
+---
+
+2013.06.13, Version 0.10.11 (Stable)
+
+* uv: upgrade to 0.10.11
+
+* npm: Upgrade to 1.2.30
+
+* openssl: add missing configuration pieces for MIPS (Andrei Sedoi)
+
+* Revert "http: remove bodyHead from 'upgrade' events" (isaacs)
+
+* v8: fix pointer arithmetic undefined behavior (Trevor Norris)
+
+* crypto: fix utf8/utf-8 encoding check (Ben Noordhuis)
+
+* net: Fix busy loop on POLLERR|POLLHUP on older linux kernels (Ben Noordhuis, isaacs)
+
+
+
+Source Code: https://nodejs.org/dist/v0.10.11/node-v0.10.11.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.11/node-v0.10.11.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.11/node-v0.10.11-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.11/x64/node-v0.10.11-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.11/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.11/node-v0.10.11-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.11/node-v0.10.11-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.11/node-v0.10.11-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.11/node-v0.10.11-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.11/
+
+Website: https://nodejs.org/docs/v0.10.11/
+
+Documentation: https://nodejs.org/docs/v0.10.11/api/
+
+Shasums:
+
+```
+c460678436e513ef5b8b8513abd74c75d8ebf7bb  node-v0.10.11-darwin-x64.tar.gz
+edd321fc6d7525774a12433e943db3a7817a19b9  node-v0.10.11-darwin-x86.tar.gz
+1388e8a2b6b4b2043db4fc382959d43e7c32e28e  node-v0.10.11-linux-x64.tar.gz
+2923e08deeb08a5ce1a29607c00f8b8e4fbd16c8  node-v0.10.11-linux-x86.tar.gz
+4d12e60a9bf4c9c418d88951733a6a51201b789d  node-v0.10.11-sunos-x64.tar.gz
+842e283ea724a6d69a17e18426c32e6fd4b0734b  node-v0.10.11-sunos-x86.tar.gz
+bbc874e7ad72d980a19ee76dc1d9012d801f1d8f  node-v0.10.11-x86.msi
+05d0a697a183f809a949832a0fd98e1e30d53e72  node-v0.10.11.pkg
+4f646bb3418d1c177ce28cdbc61e71de35b38aea  node-v0.10.11.tar.gz
+e2eec3e170e1d26622231ee3f0b632485756a5f0  node.exe
+8957dd0c31c115819f9387250f038a1e6259cfa9  node.exp
+930ba687c31f09dd199c0cfb2ac492f57c0f640f  node.lib
+6bd963cff4baba07cb05d7e6aa566aebe8db5519  node.pdb
+016356e656ac8091900637e3fb64ddc3dd53cfb5  x64/node-v0.10.11-x64.msi
+a845f30c9f0100b6f4d79080c72068ff497c5c23  x64/node.exe
+00719da33432ae9a264407c89239ce5a76e21df0  x64/node.exp
+1f96e883134197c27aada23847b049491dd46b13  x64/node.lib
+83989e612f56b0a8e90e4fad8cb1a7d8b0bdfcd0  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.12.md b/locale/uk/blog/release/v0.10.12.md
new file mode 100755
index 0000000000000..33a4b8276dd9b
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.12.md
@@ -0,0 +1,70 @@
+---
+date: 2013-06-18T18:12:19.000Z
+version: 0.10.12
+category: release
+title: Node v0.10.12 (Stable)
+slug: node-v0-10-12-stable
+layout: blog-post.hbs
+---
+
+2013.06.18, Version 0.10.12 (Stable)
+
+* npm: Upgrade to 1.2.32
+
+* readline: make `ctrl + L` clear the screen (Yuan Chuan)
+
+* v8: add setVariableValue debugger command (Ben Noordhuis)
+
+* net: Do not destroy socket mid-write (isaacs)
+
+* v8: fix build for mips32r2 architecture (Andrei Sedoi)
+
+* configure: fix cross-compilation host_arch_cc() (Andrei Sedoi)
+
+
+Source Code: https://nodejs.org/dist/v0.10.12/node-v0.10.12.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.12/node-v0.10.12.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.12/node-v0.10.12-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.12/x64/node-v0.10.12-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.12/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.12/node-v0.10.12-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.12/node-v0.10.12-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.12/node-v0.10.12-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.12/node-v0.10.12-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.12/
+
+Website: https://nodejs.org/docs/v0.10.12/
+
+Documentation: https://nodejs.org/docs/v0.10.12/api/
+
+Shasums:
+
+```
+e3c28629938d70dac535dca0b78199ae7e4e7cf6  node-v0.10.12-darwin-x64.tar.gz
+d777c8c50270b7c834ee9ca95c186d30e181f885  node-v0.10.12-darwin-x86.tar.gz
+c5b9cbb9b6329767f11a89c14e09afa795e3f9e9  node-v0.10.12-linux-x64.tar.gz
+f7a7ac317ab3a8406ec11ec118c38971d5e4c508  node-v0.10.12-linux-x86.tar.gz
+c5f446d6768298ad0d917f920f422a1e82d92fce  node-v0.10.12-sunos-x64.tar.gz
+05725a5255f762193838dac7175cbba418ef77c7  node-v0.10.12-sunos-x86.tar.gz
+3403fed2cedf23764de50e17d0eeb5c960e88b79  node-v0.10.12-x86.msi
+8e7cfecf737886014616d7c683bbb8a5ef38f4f7  node-v0.10.12.pkg
+3e4f692fb9156c0cee4dd35bd8a6be4ff89a29de  node-v0.10.12.tar.gz
+d1cb17e753a5e0370c9ffe7f753e5c9b1d5bb9ff  node.exe
+af802e62b0da817543f5a4d51304d7fc49b4e56c  node.exp
+737eb43e0daed76112e8371f85176151dc380ac5  node.lib
+b273075995dba44e7ae02641c3c8ba4c6301be8d  node.pdb
+e109532cc9d83599d7ebe18c325d14bdc7087ae8  x64/node-v0.10.12-x64.msi
+1d902d66ecfd78c5bfef4181bab075119377006d  x64/node.exe
+3d79a1f3a94c31f73c095d9b3fd83ae80e14042f  x64/node.exp
+80295d8b0cb4922dbae01d85a0726f2721f0db00  x64/node.lib
+2b5663f50946b13a1df4d9fcf7f9edd9605e130c  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.13.md b/locale/uk/blog/release/v0.10.13.md
new file mode 100755
index 0000000000000..2302f73bf0b12
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.13.md
@@ -0,0 +1,79 @@
+---
+date: 2013-07-09T21:24:47.000Z
+version: 0.10.13
+category: release
+title: Node v0.10.13 (Stable)
+slug: node-v0-10-13-stable
+layout: blog-post.hbs
+---
+
+2013.07.09, Version 0.10.13 (Stable)
+
+* uv: Upgrade to v0.10.12
+
+* npm: Upgrade to 1.3.2
+
+* windows: get proper errno (Ben Noordhuis)
+
+* tls: only wait for finish if we haven't seen it (Timothy J Fontaine)
+
+* http: Dump response when request is aborted (isaacs)
+
+* http: use an unref'd timer to fix delay in exit (Peter Rust)
+
+* zlib: level can be negative (Brian White)
+
+* zlib: allow zero values for level and strategy (Brian White)
+
+* buffer: add comment explaining buffer alignment (Ben Noordhuis)
+
+* string_bytes: properly detect 64bit (Timothy J Fontaine)
+
+* src: fix memory leak in UsingDomains() (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.13/node-v0.10.13.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.13/node-v0.10.13.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.13/node-v0.10.13-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.13/x64/node-v0.10.13-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.13/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.13/node-v0.10.13-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.13/node-v0.10.13-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.13/node-v0.10.13-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.13/node-v0.10.13-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.13/
+
+Website: https://nodejs.org/docs/v0.10.13/
+
+Documentation: https://nodejs.org/docs/v0.10.13/api/
+
+Shasums:
+```
+ae0b5d8e9afc57da259c7f30d266c968c16479bb  node-v0.10.13-darwin-x64.tar.gz
+5e5629a546f9aa2c1e11883021c416a6e0e12ad2  node-v0.10.13-darwin-x86.tar.gz
+83b8f07aa7981694e557a9aae7e5bc4c312d800c  node-v0.10.13-linux-x64.tar.gz
+ec016d282d85036151dc096cd5cee6c8bd20fdd8  node-v0.10.13-linux-x86.tar.gz
+3464241dc541bbf094ed11c0cd2ef8edb6419ee7  node-v0.10.13-sunos-x64.tar.gz
+abca9f52cfac47cc0b3e92e3bc18b578a92915e6  node-v0.10.13-sunos-x86.tar.gz
+5d020e9d3ef1021216e5cc294449c1a699b3f458  node-v0.10.13-x86.msi
+841803a64e824f84361d4e7f6e1abd8ff31056ca  node-v0.10.13.pkg
+f73d5f134296ed0aa16cbec5d727f94587844155  node-v0.10.13.tar.gz
+19beeb0f418b226a7ec7f15cdc0dccdf5f0d9e55  node.exe
+eca52e8f39d4ac5bf3d07f6b50722f41b0494cc9  node.exp
+2c47530c0d7c8e60f5c0daa78c105772b5638c9d  node.lib
+23c917f0c2c0e85677fb85583668b5e695315ced  node.pdb
+76cc14f56a3225e51f25b60faebe971cfb3ca322  x64/node-v0.10.13-x64.msi
+e96c1687d447ed642ffd85134c0d949428a0b400  x64/node.exe
+1962db68f17ffbd44c0ff82c0ff75b4ffe338319  x64/node.exp
+95f162082c359d8610dd59ea634d4bd80d40c8aa  x64/node.lib
+3ec49f4849d5fdb3e1acbcff8e3eb02d9d55d332  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.14.md b/locale/uk/blog/release/v0.10.14.md
new file mode 100755
index 0000000000000..a87ffcb61f146
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.14.md
@@ -0,0 +1,75 @@
+---
+date: 2013-07-25T20:35:41.000Z
+version: 0.10.14
+category: release
+title: Node v0.10.14 (Stable)
+slug: node-v0-10-14-stable
+layout: blog-post.hbs
+---
+
+2013.07.25, Version 0.10.14 (Stable)
+
+* uv: Upgrade to v0.10.13
+
+* npm: Upgrade to v1.3.5
+
+* os: Don't report negative times in cpu info (Ben Noordhuis)
+
+* fs: Handle large UID and GID (Ben Noordhuis)
+
+* url: Fix edge-case when protocol is non-lowercase (Shuan Wang)
+
+* doc: Streams API Doc Rewrite (isaacs)
+
+* node: call MakeDomainCallback in all domain cases (Trevor Norris)
+
+* crypto: fix memory leak in LoadPKCS12 (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.10.14/node-v0.10.14.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.14/node-v0.10.14.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.14/node-v0.10.14-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.14/x64/node-v0.10.14-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.14/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.14/node-v0.10.14-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.14/node-v0.10.14-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.14/node-v0.10.14-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.14/node-v0.10.14-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.14/
+
+Website: https://nodejs.org/docs/v0.10.14/
+
+Documentation: https://nodejs.org/docs/v0.10.14/api/
+
+Shasums:
+```
+f6a13dc93f677e9d71f15570ea3db2244c09b26e  node-v0.10.14-darwin-x64.tar.gz
+c7a456bb7bd7a3d46e4d4ed65b19458e8c937431  node-v0.10.14-darwin-x86.tar.gz
+9797f93df6085796ccad0f84a65fcdee46aaeedf  node-v0.10.14-linux-x64.tar.gz
+f40ade7d212be254a67994f86f598b1c1c0b7b4c  node-v0.10.14-linux-x86.tar.gz
+c187f1385224e8d4bc2b465d9677c060b399e268  node-v0.10.14-sunos-x64.tar.gz
+bd8edd17eff8928ccd0adedbe63ddf3631324148  node-v0.10.14-sunos-x86.tar.gz
+7654aacdcdc832387e479b2c3de731b3b6ca3d01  node-v0.10.14-x86.msi
+90892d5672a75baa761afd2f238c06d4fa58cfef  node-v0.10.14.pkg
+b5d27b36d25bd7d45e1bb52ce0e0fdfb49dde370  node-v0.10.14.tar.gz
+f2de9c77ed3914fd9139668581f970f8df698687  node.exe
+b2a767985060c0719569d8fcfe7ad7e5548d952c  node.exp
+fa035fd44672547f8424df4a461f0a48c4cfdb97  node.lib
+aaaf7b82f826dd2a0358223ea7f1a70ccf93bc77  node.pdb
+9758a6374055ebfb5a2d788e1f95ebb267a5c20b  pkgsrc/nodejs-ia32-0.10.14.tgz
+d8ca87abc993a042030d63bcae08e85a30eef4b8  pkgsrc/nodejs-x64-0.10.14.tgz
+b372293ff300dacae79c44603e878726e282b3a2  x64/node-v0.10.14-x64.msi
+293a240db1cd280907a16956d4d6bb72ad9ef02a  x64/node.exe
+9d03fa6d751359e174586190e757efbf61869d50  x64/node.exp
+8b4e097f17d4efe13a05bff7534bb23738821a9d  x64/node.lib
+0323632950aa90ed4bb083774b487f6287dae7a5  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.15.md b/locale/uk/blog/release/v0.10.15.md
new file mode 100755
index 0000000000000..2c1b175d49e65
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.15.md
@@ -0,0 +1,61 @@
+---
+date: 2013-07-25T23:57:47.000Z
+version: 0.10.15
+category: release
+title: Node v0.10.15 (Stable)
+slug: node-v0-10-15-stable
+layout: blog-post.hbs
+---
+
+2013.07.25, Version 0.10.15 (Stable)
+
+* src: fix process.getuid() return value (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.15/node-v0.10.15.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.15/node-v0.10.15.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.15/node-v0.10.15-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.15/x64/node-v0.10.15-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.15/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.15/node-v0.10.15-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.15/node-v0.10.15-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.15/node-v0.10.15-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.15/node-v0.10.15-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.15/
+
+Website: https://nodejs.org/docs/v0.10.15/
+
+Documentation: https://nodejs.org/docs/v0.10.15/api/
+
+Shasums:
+```
+b812ba5b966b89180d1391a9de5ccd075fc84c65  node-v0.10.15-darwin-x64.tar.gz
+f07bed2a59040d7adf3a647c953c3942b132da5c  node-v0.10.15-darwin-x86.tar.gz
+d236ed82967eefa726ec144301728b6a32ab8d8d  node-v0.10.15-linux-x64.tar.gz
+5629f83b10dc95d899268c3387895085270bb9e1  node-v0.10.15-linux-x86.tar.gz
+408e52074146cfed792f20ea54e9eca4419164af  node-v0.10.15-sunos-x64.tar.gz
+01ed71a5b019c6a2b51750c2e287613be1df0d92  node-v0.10.15-sunos-x86.tar.gz
+18c72b9394a943136ad5446599c732bc5fd5af9a  node-v0.10.15-x86.msi
+9dba40ed9c511faa215586d0b0f535d4ae55016c  node-v0.10.15.pkg
+14174896de074c244b0ed2251a95d7163d5a5e87  node-v0.10.15.tar.gz
+fad9611a7f656b8097c97de7b2ed016f3f33c6f9  node.exe
+ee48f297215ce12ba87998ccc06760ab3e667573  node.exp
+11f354ebcccfb88133a529e6e1337185a3b60550  node.lib
+230fc683b097afd33583ede1ec1f41fe4dae414b  node.pdb
+9d349103a53f444d1f9835989e22ebf2c906e3c0  pkgsrc/nodejs-ia32-0.10.15.tgz
+bb1397b448bf2a58ce62fc3c51fb14633e840bbd  pkgsrc/nodejs-x64-0.10.15.tgz
+7c6fbdfe5c0154477f1dd8acd915c8c13766b9ae  x64/node-v0.10.15-x64.msi
+f273ef837b2bc3b8cf5b1b7a363b510cb230a9be  x64/node.exe
+57fcec104d9fd3af53286f15353c7cd75e961382  x64/node.exp
+86afa3785280a25d183ff46bfea3a845b6b506c0  x64/node.lib
+f6bc69a9c20c3965fd4969040cde9b43c7de50ff  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.16.md b/locale/uk/blog/release/v0.10.16.md
new file mode 100755
index 0000000000000..cf3633ee45bcf
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.16.md
@@ -0,0 +1,77 @@
+---
+date: 2013-08-16T19:45:21.000Z
+version: 0.10.16
+category: release
+title: Node v0.10.16 (Stable)
+slug: node-v0-10-16-stable
+layout: blog-post.hbs
+---
+
+2013.08.16, Version 0.10.16 (Stable)
+
+* v8: back-port fix for CVE-2013-2882
+
+* npm: Upgrade to 1.3.8
+
+* crypto: fix assert() on malformed hex input (Ben Noordhuis)
+
+* crypto: fix memory leak in randomBytes() error path (Ben Noordhuis)
+
+* events: fix memory leak, don't leak event names (Ben Noordhuis)
+
+* http: Handle hex/base64 encodings properly (isaacs)
+
+* http: improve chunked res.write(buf) performance (Ben Noordhuis)
+
+* stream: Fix double pipe error emit (Eran Hammer)
+
+
+Source Code: https://nodejs.org/dist/v0.10.16/node-v0.10.16.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.16/node-v0.10.16.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.16/node-v0.10.16-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.16/x64/node-v0.10.16-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.16/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.16/node-v0.10.16-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.16/node-v0.10.16-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.16/node-v0.10.16-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.16/node-v0.10.16-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.16/
+
+Website: https://nodejs.org/docs/v0.10.16/
+
+Documentation: https://nodejs.org/docs/v0.10.16/api/
+
+Shasums:
+
+```
+c76d0cac292784dcff16642e5b8e9b6e50bd2d1f  node-v0.10.16-darwin-x64.tar.gz
+0405727606cc0bfd86fe16226235d6a17cf03524  node-v0.10.16-darwin-x86.tar.gz
+f651398c19cc56915c996660c8977a1da3c5cfaa  node-v0.10.16-linux-arm-pi.tar.gz
+784ac3b09eedc9ea2eda6d9bc8f7dd9760f40002  node-v0.10.16-linux-x64.tar.gz
+8628a9679b0dd8b5521eb7009751f501b10db924  node-v0.10.16-linux-x86.tar.gz
+49ebccdd4cf1b2433f64caf6430c0be050bf843c  node-v0.10.16-sunos-x64.tar.gz
+caf9d90e133e02f041f50056fa2be6575c606923  node-v0.10.16-sunos-x86.tar.gz
+85ed82a3f0ce7fbdc6875b7d7b35474ff52ae76a  node-v0.10.16-x86.msi
+9e993cf61047dd5c1c1736ce372c90d184b55616  node-v0.10.16.pkg
+646fd7ce38091ec9bd0c5d080a9da522edaabff7  node-v0.10.16.tar.gz
+2eab45f17ad076d73c699e0b7029ef2ccb902cd6  node.exe
+7f9b2b152aeb31d99f9cb728475852dcf08e4e42  node.exp
+17dabe6f59c2216170c37192ce709636d9458ce8  node.lib
+1b0488a644f3c45010f1da2f0fbd6915f55c646e  node.pdb
+c1535895c7f1b12e08432d9e7d760fa45d185013  pkgsrc/nodejs-ia32-0.10.16.tgz
+68d9af8ea312603a483a15c057ccdffd39fe5ea4  pkgsrc/nodejs-x64-0.10.16.tgz
+de4511ff2319f2b2e72664f0fa5cdbb97a79ca51  x64/node-v0.10.16-x64.msi
+fd35dfd384a111dc52c8563125cdbe69577276b0  x64/node.exe
+69b9866f0059fb7c6319d1f9bbea3886a27f29f5  x64/node.exp
+6e19ddfb75eaeb41b4c18769b20ca6de997b5cd6  x64/node.lib
+9e6b02883df774732ed1131c19e762cb309db917  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.17.md b/locale/uk/blog/release/v0.10.17.md
new file mode 100755
index 0000000000000..b77c3045c35eb
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.17.md
@@ -0,0 +1,95 @@
+---
+date: 2013-08-21T23:37:31.000Z
+version: 0.10.17
+category: release
+title: Node v0.10.17 (Stable)
+slug: node-v0-10-17-stable
+layout: blog-post.hbs
+---
+
+2013.08.21, Version 0.10.17 (Stable)
+
+* uv: Upgrade v0.10.14
+
+* http_parser: Do not accept PUN/GEM methods as PUT/GET (Chris Dickinson)
+
+* tls: fix assertion when ssl is destroyed at read (Fedor Indutny)
+
+* stream: Throw on 'error' if listeners removed (isaacs)
+
+* dgram: fix assertion on bad send() arguments (Ben Noordhuis)
+
+* readline: pause stdin before turning off terminal raw mode (Daniel Chatfield)
+
+
+Source Code: https://nodejs.org/dist/v0.10.17/node-v0.10.17.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.17/node-v0.10.17.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.17/node-v0.10.17-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.17/x64/node-v0.10.17-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.17/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.17/node-v0.10.17-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.17/node-v0.10.17-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.17/node-v0.10.17-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.17/node-v0.10.17-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.17/
+
+Website: https://nodejs.org/docs/v0.10.17/
+
+Documentation: https://nodejs.org/docs/v0.10.17/api/
+
+Shasums:
+```
+8502c5ec4878154b5896fca6a14ff6c83c3774a1  node-v0.10.17-darwin-x64.tar.gz
+6d785ae86ea050159dfd85841a4faac830be8a2a  node-v0.10.17-darwin-x86.tar.gz
+244dc1a25dcd2cc252ae9315bb2da07b41381c5c  node-v0.10.17-linux-x64.tar.gz
+109c32b514fab374b73972dda4f4d27a33e20d5d  node-v0.10.17-linux-x86.tar.gz
+2e046a6e05520c7be941365830517db90b791999  node-v0.10.17-sunos-x64.tar.gz
+907d73aa0e84717c342327265f0b665d09b50154  node-v0.10.17-sunos-x86.tar.gz
+ac8f653545b58d009e19522e3ead8886d151b59d  node-v0.10.17-x86.msi
+32f160364990489e1f79593e1cdcea9dfde28125  node-v0.10.17.pkg
+c9d31d5415d2cf7a09fd7abebf9f01259e9dd93b  node-v0.10.17.tar.gz
+33a5e3a86c391fc30080e796c46a74cefbd9104c  node.exe
+004ebfa938b3f14984b964dcaba061d10c32f12c  node.exp
+3dd092b26c742f20006fc2085b329a3e32d8e3d9  node.lib
+a8d997936e240626c56df8c6c8d55b659003a644  node.pdb
+165fecaab04a09a4df6b731f0e4b264bdb281644  pkgsrc/nodejs-ia32-0.10.17.tgz
+0c813098a93090823b513147de7f41f920dd8569  pkgsrc/nodejs-x64-0.10.17.tgz
+3cf665ad6c8f7d3040c2bfea8791f77c40c8f2a0  x64/node-v0.10.17-x64.msi
+95baf773a34f85014eb67d026b7b9cd0396f96f5  x64/node.exe
+ebdbcea161d44368c224fce448bf3d85e5a54f21  x64/node.exp
+49d12cb3d5be6f6707b7f5c89952f81bddb69a68  x64/node.lib
+0c0ef15eb6705c81137187c597cb0105bd2bc352  x64/node.pdb
+```
+
+Shasums:
+```
+8502c5ec4878154b5896fca6a14ff6c83c3774a1  node-v0.10.17-darwin-x64.tar.gz
+6d785ae86ea050159dfd85841a4faac830be8a2a  node-v0.10.17-darwin-x86.tar.gz
+244dc1a25dcd2cc252ae9315bb2da07b41381c5c  node-v0.10.17-linux-x64.tar.gz
+109c32b514fab374b73972dda4f4d27a33e20d5d  node-v0.10.17-linux-x86.tar.gz
+2e046a6e05520c7be941365830517db90b791999  node-v0.10.17-sunos-x64.tar.gz
+907d73aa0e84717c342327265f0b665d09b50154  node-v0.10.17-sunos-x86.tar.gz
+ac8f653545b58d009e19522e3ead8886d151b59d  node-v0.10.17-x86.msi
+32f160364990489e1f79593e1cdcea9dfde28125  node-v0.10.17.pkg
+c9d31d5415d2cf7a09fd7abebf9f01259e9dd93b  node-v0.10.17.tar.gz
+33a5e3a86c391fc30080e796c46a74cefbd9104c  node.exe
+004ebfa938b3f14984b964dcaba061d10c32f12c  node.exp
+3dd092b26c742f20006fc2085b329a3e32d8e3d9  node.lib
+a8d997936e240626c56df8c6c8d55b659003a644  node.pdb
+165fecaab04a09a4df6b731f0e4b264bdb281644  pkgsrc/nodejs-ia32-0.10.17.tgz
+0c813098a93090823b513147de7f41f920dd8569  pkgsrc/nodejs-x64-0.10.17.tgz
+3cf665ad6c8f7d3040c2bfea8791f77c40c8f2a0  x64/node-v0.10.17-x64.msi
+95baf773a34f85014eb67d026b7b9cd0396f96f5  x64/node.exe
+ebdbcea161d44368c224fce448bf3d85e5a54f21  x64/node.exp
+49d12cb3d5be6f6707b7f5c89952f81bddb69a68  x64/node.lib
+0c0ef15eb6705c81137187c597cb0105bd2bc352  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.18.md b/locale/uk/blog/release/v0.10.18.md
new file mode 100755
index 0000000000000..bf79e6703ba26
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.18.md
@@ -0,0 +1,65 @@
+---
+date: 2013-09-04T18:24:48.000Z
+version: 0.10.18
+category: release
+title: Node v0.10.18 (Stable)
+slug: node-v0-10-18-stable
+layout: blog-post.hbs
+---
+
+2013.09.04, Version 0.10.18 (Stable)
+
+* uv: Upgrade to v0.10.15
+
+* stream: Don't crash on unset _events property (isaacs)
+
+* stream: Pass 'buffer' encoding with decoded writable chunks (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.10.18/node-v0.10.18.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.18/node-v0.10.18.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.18/node-v0.10.18-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.18/x64/node-v0.10.18-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.18/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.18/node-v0.10.18-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.18/node-v0.10.18-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.18/node-v0.10.18-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.18/node-v0.10.18-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.18/
+
+Website: https://nodejs.org/docs/v0.10.18/
+
+Documentation: https://nodejs.org/docs/v0.10.18/api/
+
+Shasums:
+```
+c0219a68aa25369f4c83c5bdbb5ccc0db2cb8230  node-v0.10.18-darwin-x64.tar.gz
+32261191c3b9f0988d4f132e442969714da3281f  node-v0.10.18-darwin-x86.tar.gz
+07923fa9613b2976b3be3a1bbe36d21b9f69f3c9  node-v0.10.18-linux-x64.tar.gz
+4d4c6f485a110bf28e273020c20987c6045d2c57  node-v0.10.18-linux-x86.tar.gz
+7b61c0c12fa99f8d0ab6ed0153359ed1c914e224  node-v0.10.18-sunos-x64.tar.gz
+9f57be4b041058ea941b7f4c6f0a2ad9f431d46f  node-v0.10.18-sunos-x86.tar.gz
+fd50e0563e1ccf3efc903a33df40f86b6bfe2e62  node-v0.10.18-x86.msi
+ff71d0e8003fc1b4674f98ceb912fba2161c8224  node-v0.10.18.pkg
+0bc3c544ca1707ea4b8bd601706304e9c0609fe5  node-v0.10.18.tar.gz
+ed35cc393d930fa05f4e1fbcadfa53e2837d59cb  node.exe
+5bb6f7af79fefa21ce936bdd60355d8d097c6cb6  node.exp
+3581c8563d475642d07657fd639f48e595d2693d  node.lib
+7eb7f20b9e4dfb7d866b6d84916931630159230c  node.pdb
+192d7996c413e72a7f525039eca75ebdf0d5bc1f  pkgsrc/nodejs-ia32-0.10.18.tgz
+6c508f63bd76627ece633d04957a29bce52521c7  pkgsrc/nodejs-x64-0.10.18.tgz
+8b845fe8723480f740d2efbfac3da11cb712ce66  x64/node-v0.10.18-x64.msi
+dab63ee4c72612392cfa26c48808d45859cf6b4a  x64/node.exe
+90e37b4c9c7ea0e96a7035aa6473405da245006c  x64/node.exp
+1c19d9d5c6e7ced70742875a43085306b91d402d  x64/node.lib
+4e90849c7c96c4d2caffb64f062d91d14d152261  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.19.md b/locale/uk/blog/release/v0.10.19.md
new file mode 100755
index 0000000000000..47bebb8f49c3b
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.19.md
@@ -0,0 +1,73 @@
+---
+date: 2013-09-24T22:09:23.000Z
+version: 0.10.19
+category: release
+title: Node v0.10.19 (Stable)
+slug: node-v0-10-19-stable
+layout: blog-post.hbs
+---
+
+2013.09.24, Version 0.10.19 (Stable)
+
+* uv: Upgrade to v0.10.17
+
+* npm: upgrade to 1.3.11
+
+* readline: handle input starting with control chars (Eric Schrock)
+
+* configure: add mips-float-abi (soft, hard) option (Andrei Sedoi)
+
+* stream: objectMode transforms allow falsey values (isaacs)
+
+* tls: prevent duplicate values returned from read (Nathan Rajlich)
+
+* tls: NPN protocols are now local to connections (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.10.19/node-v0.10.19.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.19/node-v0.10.19.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.19/node-v0.10.19-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.19/x64/node-v0.10.19-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.19/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.19/node-v0.10.19-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.19/node-v0.10.19-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.19/node-v0.10.19-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.19/node-v0.10.19-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.19/
+
+Website: https://nodejs.org/docs/v0.10.19/
+
+Documentation: https://nodejs.org/docs/v0.10.19/api/
+
+Shasums:
+```
+74f1db96742fcc0128d1c14d3cb808ef5c847749  node-v0.10.19-darwin-x64.tar.gz
+71ef9bd63d3926a2b78a43a5d077838c43e7e2ea  node-v0.10.19-darwin-x86.tar.gz
+ebc6dc67276f7461dbd45496924b36949c75e7e0  node-v0.10.19-linux-x64.tar.gz
+226b507f554fa5cc07296c30f08db76f5eaeb157  node-v0.10.19-linux-x86.tar.gz
+3b324613b79d1c4ab3b9414b0644a3a559c2aec9  node-v0.10.19-sunos-x64.tar.gz
+83cb3e58e9ac925ea22c8533cabc712625faa3f7  node-v0.10.19-sunos-x86.tar.gz
+dcbe7db6d0c93f83f539f38807cd3c1923969721  node-v0.10.19-x86.msi
+e6397e1df4e74864e3f0e5fc7bd24178828497f4  node-v0.10.19.pkg
+39478caf7024af6d992007457540f8941104c5d9  node-v0.10.19.tar.gz
+0fe9364b443e76f7364f8694751da15479417bdf  node.exe
+63555cdb67c2fd63411726dc691b08af520b27f6  node.exp
+c4d33b56cff97c47b12df3ad237977a57d4c798d  node.lib
+19a603db8f8c30b1736124740a6a1c856f2d21d8  node.pdb
+ca32da0335ecb09ab7316b6e18f23461e298768e  pkgsrc/nodejs-ia32-0.10.19.tgz
+b0b05a7f74d980720677a3232e82e23df211c122  pkgsrc/nodejs-x64-0.10.19.tgz
+45aed04478346035e8dc7933d120ab636d56eac4  x64/node-v0.10.19-x64.msi
+b81788c17fec167b77883dcbaf8c629ad7560c4d  x64/node.exe
+086761bf6ff4622714d24d7979548a37aaaea57e  x64/node.exp
+cc554a431039952207adfcb3997a7366ad7182e8  x64/node.lib
+02d18f042f3d25663ea4d979dff8120435982079  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.2.md b/locale/uk/blog/release/v0.10.2.md
new file mode 100755
index 0000000000000..7ab5f9a3c56d7
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.2.md
@@ -0,0 +1,90 @@
+---
+date: 2013-03-28T20:00:39.000Z
+version: 0.10.2
+category: release
+title: Node v0.10.2 (Stable)
+slug: node-v0-10-2-stable
+layout: blog-post.hbs
+---
+
+2013.03.28, Version 0.10.2 (Stable)
+
+* npm: Upgrade to 1.2.15
+
+* uv: Upgrade to 0.10.3
+
+* tls: handle SSL_ERROR_ZERO_RETURN (Fedor Indutny)
+
+* tls: handle errors before calling C++ methods (Fedor Indutny)
+
+* tls: remove harmful unnecessary bounds checking (Marcel Laverdet)
+
+* crypto: make getCiphers() return non-SSL ciphers (Ben Noordhuis)
+
+* crypto: check randomBytes() size argument (Ben Noordhuis)
+
+* timers: do not calculate Timeout._when property (Alexey Kupershtokh)
+
+* timers: fix off-by-one ms error (Alexey Kupershtokh)
+
+* timers: handle signed int32 overflow in enroll() (Fedor Indutny)
+
+* stream: Fix stall in Transform under very specific conditions (Gil Pedersen)
+
+* stream: Handle late 'readable' event listeners (isaacs)
+
+* stream: Fix early end in Writables on zero-length writes (isaacs)
+
+* domain: fix domain callback from MakeCallback (Trevor Norris)
+
+* child_process: don't emit same handle twice (Ben Noordhuis)
+
+* child_process: fix sending utf-8 to child process (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.2/node-v0.10.2.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.2/node-v0.10.2.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.2/node-v0.10.2-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.2/x64/node-v0.10.2-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.2/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.2/node-v0.10.2-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.2/node-v0.10.2-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.2/node-v0.10.2-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.2/node-v0.10.2-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.2/
+
+Website: https://nodejs.org/docs/v0.10.2/
+
+Documentation: https://nodejs.org/docs/v0.10.2/api/
+
+Shasums:
+
+```
+860ed25d3e77d4676b5512f87f3f98b6783ee258  node-v0.10.2-darwin-x64.tar.gz
+811eb3b66651dfffeaf928496e8eecab5c9304fb  node-v0.10.2-darwin-x86.tar.gz
+2914731bdbe809483ed9da2578ce19121494e437  node-v0.10.2-linux-x64.tar.gz
+dbf039ee15e423738db4ffc9c498d6b0ad54da07  node-v0.10.2-linux-x86.tar.gz
+17bc5bf26af7da790e6b0c4cbb2b73ea1c9f2ed5  node-v0.10.2-sunos-x64.tar.gz
+5e02e35cc15ae56953921ad4c8e45b849c736e20  node-v0.10.2-sunos-x86.tar.gz
+2adb1bf5919fb8adeaf96edd8a8ed16d71a3f8f8  node-v0.10.2-x86.msi
+73ff97a4d2d3bb1f468db2654b5b59a28f868cce  node-v0.10.2.pkg
+759a05eff48ff0b54e55748012c5c45502f7cecd  node-v0.10.2.tar.gz
+6c1336a61395747fed20a12c8977a2b2ecf23354  node.exe
+f0775d4f649ee9c3d5614fdb26e64bc7d000cd5d  node.exp
+9860c6eb9062fbdc50b515f4ccab179f74dd3ec8  node.lib
+d41d99a3921022533c1760e15447ce3acf050a7d  node.pdb
+1dbd11a5278831356daca035fe5bbbe1062798b4  x64/node-v0.10.2-x64.msi
+d36abd4ecf02c522e8c75fce24eab1ce800d6458  x64/node.exe
+295a950fe3c1c3ceb04249474388b891bf2a39ed  x64/node.exp
+b64eabafc3f9498552b3ea97bd0d922db1f90f75  x64/node.lib
+1f31d6c0079e9f2c9a6de3d956649d83ca6e7a25  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.20.md b/locale/uk/blog/release/v0.10.20.md
new file mode 100755
index 0000000000000..77c9f5e9e2dc6
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.20.md
@@ -0,0 +1,62 @@
+---
+date: 2013-09-30T22:05:41.000Z
+version: 0.10.20
+category: release
+title: Node v0.10.20 (Stable)
+slug: node-v0-10-20-stable
+layout: blog-post.hbs
+---
+
+2013.09.30, Version 0.10.20 (Stable)
+
+* tls: fix sporadic hang and partial reads (Fedor Indutny)
+  - fixes "npm ERR! cb() never called!"
+
+
+Source Code: https://nodejs.org/dist/v0.10.20/node-v0.10.20.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.20/node-v0.10.20.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.20/node-v0.10.20-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.20/x64/node-v0.10.20-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.20/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.20/node-v0.10.20-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.20/node-v0.10.20-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.20/node-v0.10.20-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.20/node-v0.10.20-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.20/
+
+Website: https://nodejs.org/docs/v0.10.20/
+
+Documentation: https://nodejs.org/docs/v0.10.20/api/
+
+Shasums:
+```
+6f827b5bb1184160a58e0aac711791b610c30afd  node-v0.10.20-darwin-x64.tar.gz
+89869942f09351a5256f9ff68c3e1c363f108e7a  node-v0.10.20-darwin-x86.tar.gz
+b7c0a79acddfaeda8af221acdd18640ef5c62e8a  node-v0.10.20-linux-x64.tar.gz
+709cd1a646447036abe3f57ea6e33bb1d411c229  node-v0.10.20-linux-x86.tar.gz
+dbe318556bc7a4d7ea47947600edcdb375a92d8e  node-v0.10.20-sunos-x64.tar.gz
+b003527f645bfc8c65d890854e20c92edc1feb86  node-v0.10.20-sunos-x86.tar.gz
+34015dac5e517492fec6584cacd2d9864056107e  node-v0.10.20-x86.msi
+a0408be15afd0b5d34b8762edab6420339a8c4ff  node-v0.10.20.pkg
+d8777ac318627c1413f01358ea5c455f0f86e4b5  node-v0.10.20.tar.gz
+5f61f783345dc3663b03322d6387800d96560cd5  node.exe
+bb81cb60eae4c6be9238aa05b5245f29609b6f96  node.exp
+e06eab29b27de1908aa2cf624d438e15ee126640  node.lib
+2495f7a88f0085df5206c0d0cb44131cf9715156  node.pdb
+6036d6b1f2cf34a5055ed59b6519cb09cc6f86ff  pkgsrc/nodejs-ia32-0.10.20.tgz
+9b743d9a5d80758e8cd9d436e165c9569fa9d0fd  pkgsrc/nodejs-x64-0.10.20.tgz
+1b574ef4fe2ad61ce398415599f8f376b576e65d  x64/node-v0.10.20-x64.msi
+7137043329a25c36ad24d11d8e4ce6e5ff8a72b2  x64/node.exe
+624c5bdb06ddd726457fa7b04197069ba021016b  x64/node.exp
+f61da5166124895495bd72520d6b6f730acc1cbc  x64/node.lib
+efa36de57eda469254fab252f24ef67c17f96f00  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.21.md b/locale/uk/blog/release/v0.10.21.md
new file mode 100755
index 0000000000000..dd5c705516119
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.21.md
@@ -0,0 +1,74 @@
+---
+date: 2013-10-18T22:39:23.000Z
+version: 0.10.21
+category: release
+title: Node v0.10.21 (Stable)
+slug: node-v0-10-21-stable
+layout: blog-post.hbs
+---
+
+This release contains a security fix for the http server implementation, please
+upgrade as soon as possible. Details will be released soon.
+
+2013.10.18, Version 0.10.21 (Stable)
+
+* uv: Upgrade to v0.10.18
+
+* crypto: clear errors from verify failure (Timothy J Fontaine)
+
+* dtrace: interpret two byte strings (Dave Pacheco)
+
+* fs: fix fs.truncate() file content zeroing bug (Ben Noordhuis)
+
+* http: provide backpressure for pipeline flood (isaacs)
+
+* tls: fix premature connection termination (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.21/node-v0.10.21.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.21/node-v0.10.21.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.21/node-v0.10.21-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.21/x64/node-v0.10.21-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.21/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.21/node-v0.10.21-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.21/node-v0.10.21-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.21/node-v0.10.21-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.21/node-v0.10.21-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.21/
+
+Website: https://nodejs.org/docs/v0.10.21/
+
+Documentation: https://nodejs.org/docs/v0.10.21/api/
+
+Shasums:
+```
+fb1318fb7721aa292310599e7c6696edebcfd70d  node-v0.10.21-darwin-x64.tar.gz
+486235cc54d269d1961dfb150b1479ec14e83541  node-v0.10.21-darwin-x86.tar.gz
+7528d2fa240a5dd88d37e4847cebec50ef40c8eb  node-v0.10.21-linux-x64.tar.gz
+b372abf9d9c53bfe675e2c3f71dcfdece44edddd  node-v0.10.21-linux-x86.tar.gz
+cb873cdff3f30aa198b52c8be3588745d2ee3933  node-v0.10.21-sunos-x64.tar.gz
+020d202d7066b68f160d0ceebe8cc8306de25956  node-v0.10.21-sunos-x86.tar.gz
+037ea0e3be3512da2bc94aa765fa89d61da3e275  node-v0.10.21-x86.msi
+de2bd0e858f99098ef24f99f972b8088c1f0405c  node-v0.10.21.pkg
+b7fd2a3660635af40e3719ca0db49280d10359b2  node-v0.10.21.tar.gz
+a0e3988170beee1273a2fb6d650bf17db8495c67  node.exe
+99332a03aeba8a22254d671665b9b2161a64bd84  node.exp
+263dafeec907bd1f28ceb8272b9caaadceacb4d6  node.lib
+76d578bf352772dc4db9ebb95fb61cf18e34c80d  node.pdb
+b6d11b67ce7aaff5c7a456a4c85c80849a3d576e  pkgsrc/nodejs-ia32-0.10.21.tgz
+b116825d1d2cbcfd567f730b1c2452424508b062  pkgsrc/nodejs-x64-0.10.21.tgz
+29632c5a21a4ebf89703e417852306a676f6ede8  x64/node-v0.10.21-x64.msi
+033b0a2b57e031a9e47f0b28eb4dc50a5389b592  x64/node.exe
+f62b53229d77eaddf1f3a7909ef6533eea0e2295  x64/node.exp
+8d5cfe83c3bc78ddcf79de9d065d1b4f2af9347e  x64/node.lib
+6844e78e9ba80bfa48f6c150544e3e73d83dd316  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.22.md b/locale/uk/blog/release/v0.10.22.md
new file mode 100755
index 0000000000000..2c9c85a1384a7
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.22.md
@@ -0,0 +1,77 @@
+---
+date: 2013-11-12T20:52:56.000Z
+version: 0.10.22
+category: release
+title: Node v0.10.22 (Stable)
+slug: node-v0-10-22-stable
+layout: blog-post.hbs
+---
+
+2013.11.12, Version 0.10.22 (Stable)
+
+* npm: Upgrade to 1.3.14
+
+* uv: Upgrade to v0.10.19
+
+* child_process: don't assert on stale file descriptor events (Fedor Indutny)
+
+* darwin: Fix "Not Responding" in Mavericks activity monitor (Fedor Indutny)
+
+* debugger: Fix bug in sb() with unnamed script (Maxim Bogushevich)
+
+* repl: do not insert duplicates into completions (Maciej Małecki)
+
+* src: Fix memory leak on closed handles (Timothy J Fontaine)
+
+* tls: prevent stalls by using read(0) (Fedor Indutny)
+
+* v8: use correct timezone information on Solaris (Maciej Małecki)
+
+
+Source Code: https://nodejs.org/dist/v0.10.22/node-v0.10.22.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.22/node-v0.10.22.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.22/node-v0.10.22-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.22/x64/node-v0.10.22-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.22/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.22/node-v0.10.22-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.22/node-v0.10.22-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.22/node-v0.10.22-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.22/node-v0.10.22-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.22/
+
+Website: https://nodejs.org/docs/v0.10.22/
+
+Documentation: https://nodejs.org/docs/v0.10.22/api/
+
+Shasums:
+```
+3082a8d13dfafa7212a7f75bd0a83447fb4d7b99  node-v0.10.22-darwin-x64.tar.gz
+dca37fa37c8ce3c0df68e74643ed822bec7a12b3  node-v0.10.22-darwin-x86.tar.gz
+3739f75bbb85c920a237ceb1c34cb872409d61f7  node-v0.10.22-linux-x64.tar.gz
+7e99b654c21bc2a5cbccc33f1bae3ce6e26b3d12  node-v0.10.22-linux-x86.tar.gz
+3dfb3585386ca0645ba02b5ad06014ddccda8cbe  node-v0.10.22-sunos-x64.tar.gz
+e6004f073fc81826335dc0c8fba04a82beada0bc  node-v0.10.22-sunos-x86.tar.gz
+3beff0c7893e39df54e416307b624eb642bffa62  node-v0.10.22-x86.msi
+b4433b98f87f3f06130adad410e2fb5f959bbf37  node-v0.10.22.pkg
+d7c6a39dfa714eae1f8da7a00c9a07efd74a03b3  node-v0.10.22.tar.gz
+0ff278f5d6225d2be2a51bd4c7ba8fa0d15e98a4  node.exe
+6cded62495794c53f6642745d34cbeb7a28266b1  node.exp
+caaa11790ac8ec40d074e141afa7ffa611f216b4  node.lib
+3c7592832d403c93a17b29852f2c828760a45128  node.pdb
+f335aef2844a6bf9d8d5a9782e7c631d730acc2e  pkgsrc/nodejs-ia32-0.10.22.tgz
+6d47f98efd86faa71e1e9887aa63916e884bb2a8  pkgsrc/nodejs-x64-0.10.22.tgz
+c3c169304c6371ee7bd119151bcbced61a322394  x64/node-v0.10.22-x64.msi
+307de602a091fa2af3adaa64812200e32ee00fdc  x64/node.exe
+67440fca57eb4be5800434245ef1a5d16f5aea01  x64/node.exp
+e6ee29859cd069ff5b8bf749a598112d9f09ed3c  x64/node.lib
+fee98420155b88c0c4b11616aa416d2328cec97d  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.23.md b/locale/uk/blog/release/v0.10.23.md
new file mode 100755
index 0000000000000..c2a23a4a8ad25
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.23.md
@@ -0,0 +1,89 @@
+---
+date: 2013-12-12T06:10:46.000Z
+version: 0.10.23
+category: release
+title: Node v0.10.23 (Stable)
+slug: node-v0-10-23-stable
+layout: blog-post.hbs
+---
+
+2013.12.12, Version 0.10.23 (Stable)
+
+* uv: Upgrade to v0.10.20 (Timothy J Fontaine)
+
+* npm: Upgrade to 1.3.17 (isaacs)
+
+* gyp: update to 78b26f7 (Timothy J Fontaine)
+
+* build: include postmortem symbols on linux (Timothy J Fontaine)
+
+* crypto: Make Decipher._flush() emit errors. (Kai Groner)
+
+* dgram: fix abort when getting `fd` of closed dgram (Fedor Indutny)
+
+* events: do not accept NaN in setMaxListeners (Fedor Indutny)
+
+* events: avoid calling `once` functions twice (Tim Wood)
+
+* events: fix TypeError in removeAllListeners (Jeremy Martin)
+
+* fs: report correct path when EEXIST (Fedor Indutny)
+
+* process: enforce allowed signals for kill (Sam Roberts)
+
+* tls: emit 'end' on .receivedShutdown (Fedor Indutny)
+
+* tls: fix potential data corruption (Fedor Indutny)
+
+* tls: handle `ssl.start()` errors appropriately (Fedor Indutny)
+
+* tls: reset NPN callbacks after SNI (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.10.23/node-v0.10.23.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.23/node-v0.10.23.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.23/node-v0.10.23-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.23/x64/node-v0.10.23-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.23/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.23/node-v0.10.23-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.23/node-v0.10.23-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.23/node-v0.10.23-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.23/node-v0.10.23-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.23/
+
+Website: https://nodejs.org/docs/v0.10.23/
+
+Documentation: https://nodejs.org/docs/v0.10.23/api/
+
+Shasums:
+```
+80980a23ec1915a0d4522fd4423a2eee25bf9ba5  node-v0.10.23-darwin-x64.tar.gz
+c9c0f6772f2bda746d3997f4d821da9090dcd2a3  node-v0.10.23-darwin-x86.tar.gz
+4c7d17ae61c753750e8f5ae989e3d80f7c8f89ea  node-v0.10.23-linux-x64.tar.gz
+afa901a312350ec8b271d402261a7882e1d3640b  node-v0.10.23-linux-x86.tar.gz
+30d5e06cfed35eea80d5ee4643858c157d104a85  node-v0.10.23-sunos-x64.tar.gz
+2c4ce154b8595848119bb63164ca021f4fe8457e  node-v0.10.23-sunos-x86.tar.gz
+d51b641354a41243830ff6e3bdd1e03a7758fc38  node-v0.10.23-x86.msi
+a7711fbb958350011641c218dae64c0c6f1f80a8  node-v0.10.23.pkg
+8717942d1bdfa8902ce65cd33b4293d16b486c64  node-v0.10.23.tar.gz
+12d1e0a6373bb2b67129c7f0ebc514b793b106af  node.exe
+9f107c4dba21fee76bbb5ac2fe552d40e6ae5e70  node.exp
+52b4c463f8b667c24a54a0d8cd583b677706ae3c  node.lib
+ec619173e2e867b929d4178ecbe561639aed4cb2  node.pdb
+837ff717c2842c32e0804ce6c131404fc8599d8d  pkgsrc/nodejs-ia32-0.10.23.tgz
+395e9fe9e32874a24febffa17adacd7e1e387e63  pkgsrc/nodejs-x64-0.10.23.tgz
+56892aadf1c9d2d2bc637ee87bd08775a139b252  x64/node-v0.10.23-x64.msi
+663d9dd7face6399f5c0b7d6082ec2d5b4acc2c3  x64/node.exe
+601b564b73df1f4a871ed55e2e2c9aee5b28f04d  x64/node.exp
+523e3f96f45132d2e5e2eb39a1dbd0c5bf6b8822  x64/node.lib
+2624cddcbd23c84d947af2bf2b91b1e0b64e3602  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.24.md b/locale/uk/blog/release/v0.10.24.md
new file mode 100755
index 0000000000000..eb102adaff225
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.24.md
@@ -0,0 +1,71 @@
+---
+date: 2013-12-19T17:02:48.000Z
+version: 0.10.24
+category: release
+title: Node v0.10.24 (Stable)
+slug: node-v0-10-24-stable
+layout: blog-post.hbs
+---
+
+2013.12.18, Version 0.10.24 (Stable)
+
+* uv: Upgrade to v0.10.21
+
+* npm: upgrade to 1.3.21
+
+* v8: backport fix for CVE-2013-{6639|6640}
+
+* build: unix install node and dep library headers (Timothy J Fontaine)
+
+* cluster, v8: fix --logfile=%p.log (Ben Noordhuis)
+
+* module: only cache package main (Wyatt Preul)
+
+
+Source Code: https://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.24/node-v0.10.24.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.24/node-v0.10.24-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.24/x64/node-v0.10.24-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.24/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.24/node-v0.10.24-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.24/node-v0.10.24-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.24/node-v0.10.24-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.24/node-v0.10.24-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.24/
+
+Website: https://nodejs.org/docs/v0.10.24/
+
+Documentation: https://nodejs.org/docs/v0.10.24/api/
+
+Shasums:
+```
+4a233e4e51ec24de3b2c3196b9128781665b4edc  node-v0.10.24-darwin-x64.tar.gz
+1b018a372d919462e8ebef29a0de4816a83e38ff  node-v0.10.24-darwin-x86.tar.gz
+423018f6a60b18d0dddf3007c325e0cc8cf55099  node-v0.10.24-linux-x64.tar.gz
+fb99761ce4cef4a43743c1ed630b185545152264  node-v0.10.24-linux-x86.tar.gz
+9719b2b636d8f5caf5495e967cbe167fd16eb160  node-v0.10.24-sunos-x64.tar.gz
+84d7645d88dad9050f72c01d5f783cc018a8dc2b  node-v0.10.24-sunos-x86.tar.gz
+4b3cd142e691033308bfab237b6bf79a1a7f5c10  node-v0.10.24-x86.msi
+74aba302d8b34e1fc93b3e0babc3f5d9bd8c09f3  node-v0.10.24.pkg
+d162d01eb173cb5a0e7e46c9d706421c4c771039  node-v0.10.24.tar.gz
+782c0b437f1d4205d7ba012e02157fb984d656b0  node.exe
+c3bf16e3e2e268340a96fca869a1e3ce3ead46b5  node.exp
+b81ceddb831981b200f04403718b2adcd24fd5ed  node.lib
+1c009c51c273512eb76ef3a1e36d5d1ccf1e4094  node.pdb
+8c90873802c40ecadb304002401ba857ad728f9c  pkgsrc/nodejs-ia32-0.10.24.tgz
+94eda460e90dd59886ee2543bb55c8baea6daf1c  pkgsrc/nodejs-x64-0.10.24.tgz
+9b36fd16d8a6eb95c375ced0e1929b88b3dbb3e6  x64/node-v0.10.24-x64.msi
+43c51bf9ff7c6aa421c4c89a4b14e0ab1cb0527a  x64/node.exe
+74d67c1cad72c0231fdc3498a0ca90c09e49abfb  x64/node.exp
+724463c1a1bd3ad386e1089f53c7fa0ca16c38b6  x64/node.lib
+58a6bcec861c0a8d20e90db348d3a4fbd49e88cc  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.25.md b/locale/uk/blog/release/v0.10.25.md
new file mode 100755
index 0000000000000..084dd433dd78e
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.25.md
@@ -0,0 +1,75 @@
+---
+date: 2014-01-23T19:43:30.000Z
+version: 0.10.25
+category: release
+title: Node v0.10.25 (Stable)
+slug: node-v0-10-25-stable
+layout: blog-post.hbs
+---
+
+2014.01.23, Version 0.10.25 (Stable)
+
+* uv: Upgrade to v0.10.23
+
+* npm: Upgrade to v1.3.24
+
+* v8: Fix enumeration for objects with lots of properties
+
+* child_process: fix spawn() optional arguments (Sam Roberts)
+
+* cluster: report more errors to workers (Fedor Indutny)
+
+* domains: exit() only affects active domains (Ryan Graham)
+
+* src: OnFatalError handler must abort() (Timothy J Fontaine)
+
+* stream: writes may return false but forget to emit drain (Yang Tianyang)
+
+
+Source Code: https://nodejs.org/dist/v0.10.25/node-v0.10.25.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.25/node-v0.10.25.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.25/node-v0.10.25-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.25/x64/node-v0.10.25-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.25/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.25/node-v0.10.25-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.25/node-v0.10.25-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.25/node-v0.10.25-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.25/node-v0.10.25-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.25/
+
+Website: https://nodejs.org/docs/v0.10.25/
+
+Documentation: https://nodejs.org/docs/v0.10.25/api/
+
+Shasums:
+```
+b347508376ceef724b464e6009ec2daead7ea572  node-v0.10.25-darwin-x64.tar.gz
+f7b3c7a36b45a83360bcd9e541e64bf18ef29272  node-v0.10.25-darwin-x86.tar.gz
+7c75e7e13561be1222bddd438a84a8f228fe1bc3  node-v0.10.25-linux-x64.tar.gz
+16a2c861de5b27ef907dc18253fcd4f33d506662  node-v0.10.25-linux-x86.tar.gz
+05bdc1cd7933ccfa95c2f1f058ff0125eacbdc2d  node-v0.10.25-sunos-x64.tar.gz
+250a48c9a2b6c6a8a6feebb0d7d33f96bf8d82f4  node-v0.10.25-sunos-x86.tar.gz
+ce78cc8b49e339f71888f627c4e985dda0a83e27  node-v0.10.25-x86.msi
+abab975e86250b51a7434d229d13b30acdf4e82e  node-v0.10.25.pkg
+1e330b4fbb6f7bb858a0b37d8573dd4956f40885  node-v0.10.25.tar.gz
+e3779ed14a68dc6f711ead628fe11a127d09547c  node.exe
+35521b6142d39fa371aba7d1fda87a1836db78e4  node.exp
+35eb46e5d04fdb1c1417876d1712b85eea6be03c  node.lib
+cc749498572b4cf4b277225404beefdd75a4e903  node.pdb
+9bf1bf3a59a3f0dc0fd32f9504e8011e5b4ebc42  pkgsrc/nodejs-ia32-0.10.25.tgz
+f4a6e7d561c321b917c1b6a021fe38cd330a374e  pkgsrc/nodejs-x64-0.10.25.tgz
+aab984860cc02e1d27a0932c4c8d34e5e3551ebf  x64/node-v0.10.25-x64.msi
+d2f884d75d5f30693f62625787f27fb2a8824178  x64/node.exe
+75cdbe43984c9a9f6c5f1e5875fa7422c97b2d62  x64/node.exp
+108c2d9dd6ecf7cad83c4cb5cd62303f51c5570a  x64/node.lib
+a7c37dadc994c281d08f6a55bfbd01ecf738fe66  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.26.md b/locale/uk/blog/release/v0.10.26.md
new file mode 100755
index 0000000000000..577a6fa03235b
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.26.md
@@ -0,0 +1,85 @@
+---
+date: 2014-02-19T00:40:22.000Z
+version: 0.10.26
+category: release
+title: Node v0.10.26 (Stable)
+slug: node-v0-10-26-stable
+layout: blog-post.hbs
+---
+
+2014.02.18, Version 0.10.26 (Stable)
+
+* uv: Upgrade to v0.10.25 (Timothy J Fontaine)
+
+* npm: upgrade to 1.4.3 (isaacs)
+
+* v8: support compiling with VS2013 (Fedor Indutny)
+
+* cares: backport TXT parsing fix (Fedor Indutny)
+
+* crypto: throw on SignFinal failure (Fedor Indutny)
+
+* crypto: update root certificates (Ben Noordhuis)
+
+* debugger: Fix breakpoint not showing after restart (Farid Neshat)
+
+* fs: make unwatchFile() insensitive to path (iamdoron)
+
+* net: do not re-emit stream errors (Fedor Indutny)
+
+* net: make Socket destroy() re-entrance safe (Jun Ma)
+
+* net: reset `endEmitted` on reconnect (Fedor Indutny)
+
+* node: do not close stdio implicitly (Fedor Indutny)
+
+* zlib: avoid assertion in close (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.10.26/node-v0.10.26.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.26/node-v0.10.26.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.26/node-v0.10.26-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.26/x64/node-v0.10.26-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.26/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.26/node-v0.10.26-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.26/node-v0.10.26-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.26/node-v0.10.26-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.26/node-v0.10.26-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.26/
+
+Website: https://nodejs.org/docs/v0.10.26/
+
+Documentation: https://nodejs.org/docs/v0.10.26/api/
+
+Shasums:
+```
+6806b3ed47c3f68de83685835ed455ed02ec0598  node-v0.10.26-darwin-x64.tar.gz
+efdfe5c4f7d8e7443775aa57408eeadd3d4294a2  node-v0.10.26-darwin-x86.tar.gz
+d15d39e119bdcf75c6fc222f51ff0630b2611160  node-v0.10.26-linux-x64.tar.gz
+b3bebee7f256644266fccce04f54e2825eccbfc0  node-v0.10.26-linux-x86.tar.gz
+846ba8173fd0f6499800765f4679130465f4584b  node-v0.10.26-sunos-x64.tar.gz
+e5bf3dae6a0597bb8be029f6f0119bea2f1612f0  node-v0.10.26-sunos-x86.tar.gz
+2521fc37951c7e37a3c78394721887f9b17ac634  node-v0.10.26-x86.msi
+ff7512f49bb9f1ec2bc3f974588421305f1e28c7  node-v0.10.26.pkg
+2340ec2dce1794f1ca1c685b56840dd515a271b2  node-v0.10.26.tar.gz
+180824e6714b814d793b0875a7035331806ec1b7  node.exe
+a86480a61151535811e262df3792a2fba8bd9040  node.exp
+b93834766d19b4b842ddd19234c1f78931c049d9  node.lib
+b19628922c8ccf7168c13ece5b38b1d5c8393e41  node.pdb
+e112d4059671f6b5c1b56803c4bbb65c890cae49  pkgsrc/nodejs-ia32-0.10.26.tgz
+6a5eb9fe688332f4d078dae356a77015f9740c35  pkgsrc/nodejs-x64-0.10.26.tgz
+6a98fb6a3b35cfb6950e49d845613e6d0ad8eda5  x64/node-v0.10.26-x64.msi
+dfdccf3ee14adf23d1a4b96889f98d6b9bcc0c59  x64/node.exe
+c6f15581d5345209432dda8a28ea7e32592f51b3  x64/node.exp
+35820c8b4c2e9c61dc03fbd25b431b2b699b1507  x64/node.lib
+b0ad9d72a8f42d4dd65c529e296077038daa87dc  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.27.md b/locale/uk/blog/release/v0.10.27.md
new file mode 100755
index 0000000000000..b4ea1ce87d409
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.27.md
@@ -0,0 +1,89 @@
+---
+date: 2014-05-01T22:29:37.000Z
+version: 0.10.27
+category: release
+title: Node v0.10.27 (Stable)
+slug: node-v0-10-27-stable
+layout: blog-post.hbs
+---
+
+2014.05.01, Version 0.10.27 (Stable)
+
+* npm: upgrade to v1.4.8
+
+* openssl: upgrade to 1.0.1g
+
+* uv: update to v0.10.27
+
+* dns: fix certain txt entries (Fedor Indutny)
+
+* assert: Ensure reflexivity of deepEqual (Mike Pennisi)
+
+* child_process: fix deadlock when sending handles (Fedor Indutny)
+
+* child_process: fix sending handle twice (Fedor Indutny)
+
+* crypto: do not lowercase cipher/hash names (Fedor Indutny)
+
+* dtrace: workaround linker bug on FreeBSD (Fedor Indutny)
+
+* http: do not emit EOF non-readable socket (Fedor Indutny)
+
+* http: invoke createConnection when no agent (Nathan Rajlich)
+
+* stream: remove useless check (Brian White)
+
+* timer: don't reschedule timer bucket in a domain (Greg Brail)
+
+* url: treat  the same as / (isaacs)
+
+* util: format as Error if instanceof Error (Rod Vagg)
+
+
+Source Code: https://nodejs.org/dist/v0.10.27/node-v0.10.27.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.27/node-v0.10.27.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.27/node-v0.10.27-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.27/x64/node-v0.10.27-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.27/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.27/node-v0.10.27-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.27/node-v0.10.27-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.27/node-v0.10.27-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.27/node-v0.10.27-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.27/
+
+Website: https://nodejs.org/docs/v0.10.27/
+
+Documentation: https://nodejs.org/docs/v0.10.27/api/
+
+Shasums:
+```
+74a33b3a095370b6a42f74527817ad4c57110c21  node-v0.10.27-darwin-x64.tar.gz
+77c76d4433d9d2ebdf3b6b41da61ef869b9c080c  node-v0.10.27-darwin-x86.tar.gz
+5e5328172491bb6861376a751b530ed35a45d128  node-v0.10.27-linux-x64.tar.gz
+6e5b2d22dc720398fc52266395ad04da61df564f  node-v0.10.27-linux-x86.tar.gz
+bd441a809c2256cca4f23d0d53f7599d1684da1f  node-v0.10.27-sunos-x64.tar.gz
+7a116e9f128cbc2e46ae9c21bc5adc9054ef4c0d  node-v0.10.27-sunos-x86.tar.gz
+36771e0712ccc5363bb97674d44c36d784901cb7  node-v0.10.27-x86.msi
+a0ff5292c46e7ea984362e9fd54fa7f8ae981760  node-v0.10.27.pkg
+b9429a86d774d06cccd840e6bd189f9106928a87  node-v0.10.27.tar.gz
+6d61a07a184d1103fe8f801ca75053a44ab514fc  node.exe
+618c4152b7729cf41b3e53b2bb8f172ba017e128  node.exp
+65845a7ef3582c1ccd3943f6b2d8e804a8317f31  node.lib
+3eacd9aef672410ed42ccc807f81a79ec130013e  node.pdb
+f8e8097df171f108c6f8925d2fce061ac5caf9de  pkgsrc/nodejs-ia32-0.10.27.tgz
+323e2d72943381bb89fa29f8305697854b423537  pkgsrc/nodejs-x64-0.10.27.tgz
+911832602bf8e65bc7e2b2e34c7dd1af17b427e5  x64/node-v0.10.27-x64.msi
+92f3aa0c7664489d7e796206be04fa2dec1f61e3  x64/node.exe
+82f6409c91d2294c7e450a5b83701c9988a40a45  x64/node.exp
+181c71e5277614dd60b2c04067008d38030708eb  x64/node.lib
+12855dc1d77372367d2ef917dd06e9db3a628a71  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.28.md b/locale/uk/blog/release/v0.10.28.md
new file mode 100755
index 0000000000000..153393f769b1b
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.28.md
@@ -0,0 +1,61 @@
+---
+date: 2014-05-02T14:45:51.000Z
+version: 0.10.28
+category: release
+title: Node v0.10.28 (Stable)
+slug: node-v0-10-28-stable
+layout: blog-post.hbs
+---
+
+2014.05.01, Version 0.10.28 (Stable)
+
+* npm: upgrade to v1.4.9
+
+
+Source Code: https://nodejs.org/dist/v0.10.28/node-v0.10.28.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.28/node-v0.10.28.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.28/node-v0.10.28-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.28/x64/node-v0.10.28-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.28/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.28/node-v0.10.28-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.28/node-v0.10.28-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.28/node-v0.10.28-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.28/node-v0.10.28-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.28/
+
+Website: https://nodejs.org/docs/v0.10.28/
+
+Documentation: https://nodejs.org/docs/v0.10.28/api/
+
+Shasums:
+```
+6eff580cc8460741155d42ef1ef537961194443f  node-v0.10.28-darwin-x64.tar.gz
+d95ed3e8305ba459015549ef8a925ffbb889ef35  node-v0.10.28-darwin-x86.tar.gz
+4b9cf9437decea3d9913b694ea2e9b0a06ced2dd  node-v0.10.28-linux-x64.tar.gz
+3daec68e972abc299882b73fa6360387c5145a97  node-v0.10.28-linux-x86.tar.gz
+17898dcf188d4b672bf5d2ec2f8e7a0abb6ccbcf  node-v0.10.28-sunos-x64.tar.gz
+19075b6ce07fb3a331b2f710ddddd07f86a5a5cd  node-v0.10.28-sunos-x86.tar.gz
+0c9ebeecf7cfad99fad1af7e7043fcd6fac8eef9  node-v0.10.28-x86.msi
+f94bb307f8c4aa408c4702704461533f1d4fa793  node-v0.10.28.pkg
+ef08a75f6359a16e672cae684e0804ca7f4554b7  node-v0.10.28.tar.gz
+57e565d7a2c10dd9299c15b98ab752e01ab3b4e0  node.exe
+97de4ea47677773ee21c2361b88fa8751f613bb3  node.exp
+20614aa1b6505e3c6921897bab09117b86da9c29  node.lib
+10bfcfa936d25a12f0778f472c3439c2aaac0ff9  node.pdb
+9aa42387fb7d18a74059ffef85f9d8ca316525b6  pkgsrc/nodejs-ia32-0.10.28.tgz
+b987cd71d9ca1aeb513343b459a3e5f7b8c4df1d  pkgsrc/nodejs-x64-0.10.28.tgz
+6122b245f2237268a3ad10e8b008752888713906  x64/node-v0.10.28-x64.msi
+8017b24d8e6955bbfc2dc28f7a57c3d03e159020  x64/node.exe
+8da812d32830442a0aafa3c3be85ca3ee7ce43c4  x64/node.exp
+8961ea28d99d05dd85c3bf1ac4dd88fb4e23be3b  x64/node.lib
+02d57f356d754da2e5ba8885243ad7a9a67bad38  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.29.md b/locale/uk/blog/release/v0.10.29.md
new file mode 100755
index 0000000000000..54649eec8cf7d
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.29.md
@@ -0,0 +1,84 @@
+---
+date: 2014-06-16T15:06:10.000Z
+version: 0.10.29
+category: release
+title: Node v0.10.29 (Stable)
+slug: node-v0-10-29-stable
+layout: blog-post.hbs
+---
+
+2014.06.05, Version 0.10.29 (Stable)
+
+* openssl: to 1.0.1h (CVE-2014-0224)
+
+* npm: upgrade to 1.4.14
+
+* utf8: Prevent Node from sending invalid UTF-8 (Felix Geisendörfer)
+  - *NOTE* this introduces a breaking change, previously you could construct
+invalid UTF-8 and invoke an error in a client that was expecting valid
+UTF-8, now unmatched surrogate pairs are replaced with the unknown UTF-8
+character. To restore the old functionality simply have NODE_INVALID_UTF8
+environment variable set.
+
+* child_process: do not set args before throwing (Greg Sabia Tucker)
+
+* child_process: spawn() does not throw TypeError (Greg Sabia Tucker)
+
+* constants: export O_NONBLOCK (Fedor Indutny)
+
+* crypto: improve memory usage (Alexis Campailla)
+
+* fs: close file if fstat() fails in readFile() (cjihrig)
+
+* lib: name EventEmitter prototype methods (Ben Noordhuis)
+
+* tls: fix performance issue (Alexis Campailla)
+
+
+Source Code: https://nodejs.org/dist/v0.10.29/node-v0.10.29.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.29/node-v0.10.29.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.29/node-v0.10.29-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.29/x64/node-v0.10.29-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.29/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.29/node-v0.10.29-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.29/node-v0.10.29-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.29/node-v0.10.29-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.29/node-v0.10.29-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.29/
+
+Website: https://nodejs.org/docs/v0.10.29/
+
+Documentation: https://nodejs.org/docs/v0.10.29/api/
+
+Shasums:
+```
+45a26f4c01086275dba4657e3c347eb8648beda5  node-v0.10.29-darwin-x64.tar.gz
+cdfd3cbb5b4a5c99fed4b5f29bb0d9f39af0ad15  node-v0.10.29-darwin-x86.tar.gz
+570c45653fec04d29d2208bb2967bc88b2821537  node-v0.10.29-linux-x64.tar.gz
+81a0f08f9b4485d0a7ed0c049c79110b93ae03bc  node-v0.10.29-linux-x86.tar.gz
+44cf39e6eba77b23abf31f0780b85d83f6e8d93a  node-v0.10.29-sunos-x64.tar.gz
+c91a5b34dec50f91102a1cc846b79cb50d6460af  node-v0.10.29-sunos-x86.tar.gz
+dd512e5ceb74988ede95517554888f2b3d716ff4  node-v0.10.29-x86.msi
+7401f3047373813cf788fa4de487d0766cef76f7  node-v0.10.29.pkg
+0d5dc62090404f7c903f29779295758935529242  node-v0.10.29.tar.gz
+7e1fc5162e177aa32d626635e941aa2791092035  node.exe
+9f83dbfc6db23f1fa701259359cbb8593e6edb58  node.exp
+b9090fd83fcd66a91ecde139acb14c741c4b4af7  node.lib
+2599a5723ea8aac115f72e48f053e0d7ac1dd5c7  node.pdb
+9387d64902a3c7ff97ce3bc07f519b238ab9df4f  pkgsrc/nodejs-ia32-0.10.29.tgz
+cc4c90afe93456176c9ea984a08aefd065d85b34  pkgsrc/nodejs-x64-0.10.29.tgz
+c6ae603f73ccb2e33fed2d34fbcf55fd8d952775  x64/node-v0.10.29-x64.msi
+1bf313dfb5259e8712ed1f0783739070f5c1453d  x64/node.exe
+14c902ddaa40a1c37826691d691e594d0d657fe8  x64/node.exp
+0bf14903526c93fcfe4bab57844b4046ce922b31  x64/node.lib
+af759c0b56d829439b08b46877641000bbff81d6  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.3.md b/locale/uk/blog/release/v0.10.3.md
new file mode 100755
index 0000000000000..61d45c4dc99fb
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.3.md
@@ -0,0 +1,80 @@
+---
+date: 2013-04-03T18:24:08.000Z
+version: 0.10.3
+category: release
+title: Node v0.10.3 (Stable)
+slug: node-v0-10-3-stable
+layout: blog-post.hbs
+---
+
+2013.04.03, Version 0.10.3 (Stable)
+
+* npm: Upgrade to 1.2.17
+
+* child_process: acknowledge sent handles (Fedor Indutny)
+
+* etw: update prototypes to match dtrace provider (Timothy J Fontaine)
+
+* dtrace: pass more arguments to probes (Dave Pacheco)
+
+* build: allow building with dtrace on osx (Dave Pacheco)
+
+* http: Remove legacy ECONNRESET workaround code (isaacs)
+
+* http: Ensure socket cleanup on client response end (isaacs)
+
+* tls: Destroy socket when encrypted side closes (isaacs)
+
+* repl: isSyntaxError() catches "strict mode" errors (Nathan Rajlich)
+
+* crypto: Pass options to ctor calls (isaacs)
+
+* src: tie process.versions.uv to uv_version_string() (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.3/node-v0.10.3.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.3/node-v0.10.3.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.3/node-v0.10.3-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.3/x64/node-v0.10.3-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.3/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.3/node-v0.10.3-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.3/node-v0.10.3-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.3/node-v0.10.3-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.3/node-v0.10.3-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.3/
+
+Website: https://nodejs.org/docs/v0.10.3/
+
+Documentation: https://nodejs.org/docs/v0.10.3/api/
+
+Shasums:
+
+```
+9b2f0936ee60aa65f6a5053e82440508aa9be0a7  node-v0.10.3-darwin-x64.tar.gz
+f0392db831ca58c1f7b2d857d7e8cc601ea8b022  node-v0.10.3-darwin-x86.tar.gz
+9a375e77f9994fbd4afd741bae64c548f2a43a64  node-v0.10.3-linux-x64.tar.gz
+3323da517271e45a3850b169b10ef3d254a263a9  node-v0.10.3-linux-x86.tar.gz
+0026e2453a3940ed16b9569b8187943ccf0aeb45  node-v0.10.3-sunos-x64.tar.gz
+af88ad2dc98368b36f1aafc7b79f8378169fc56e  node-v0.10.3-sunos-x86.tar.gz
+e057c8841ddbe4dc8bc155a28b7e07dbe3d108d1  node-v0.10.3-x86.msi
+a37575d47de5696b8abb2e12dc3e9d0cdb5d17f6  node-v0.10.3.pkg
+4a1feb4ac18ede9e7193921f59fc181c88b1c7ba  node-v0.10.3.tar.gz
+9d9266d1e69bfe24837c67ff755f055fd049cd48  node.exe
+8762416a5e0d71e285215efde181c7242f3f2c6f  node.exp
+5c05f332070a77900010f15c1074c4e86e20fa0d  node.lib
+a8dc61535f6ae5fd13bce9cdca989ffc113a4080  node.pdb
+b834751b2e9f18e6ef38cf9fe5331e6073e3cab2  x64/node-v0.10.3-x64.msi
+932c30a53f546717f00de063ee09fc8ce603dd2a  x64/node.exe
+a3e91038e027c91a555116d2c20742eea2e9378f  x64/node.exp
+d60bb0f9026df9dcc17cff0267964032aaf46712  x64/node.lib
+f645a2d63179ae749defe13c653cf1777dd9021a  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.30.md b/locale/uk/blog/release/v0.10.30.md
new file mode 100755
index 0000000000000..fced0a43f2392
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.30.md
@@ -0,0 +1,106 @@
+---
+date: 2014-07-31T18:11:40.000Z
+version: 0.10.30
+category: release
+title: Node v0.10.30 (Stable)
+slug: node-v0-10-30-stable
+layout: blog-post.hbs
+---
+
+2014.07.31, Version 0.10.30 (Stable)
+
+* uv: Upgrade to v0.10.28
+
+* npm: Upgrade to v1.4.21
+
+* v8: Interrupts must not mask stack overflow.
+
+* Revert "stream: start old-mode read in a next tick" (Fedor Indutny)
+
+* buffer: fix sign overflow in `readUIn32BE` (Fedor Indutny)
+
+* buffer: improve {read,write}{U}Int* methods (Nick Apperson)
+
+* child_process: handle writeUtf8String error (Fedor Indutny)
+
+* deps: backport 4ed5fde4f from v8 upstream (Fedor Indutny)
+
+* deps: cherry-pick eca441b2 from OpenSSL (Fedor Indutny)
+
+* lib: remove and restructure calls to isNaN() (cjihrig)
+
+* module: eliminate double `getenv()` (Maciej Małecki)
+
+* stream2: flush extant data on read of ended stream (Chris Dickinson)
+
+* streams: remove unused require('assert') (Rod Vagg)
+
+* timers: backport f8193ab (Julien Gilli)
+
+* util.h: interface compatibility (Oguz Bastemur)
+
+* zlib: do not crash on write after close (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.10.30/node-v0.10.30.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.30/node-v0.10.30.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.30/node-v0.10.30-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.30/x64/node-v0.10.30-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.30/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.30/node-v0.10.30-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.30/node-v0.10.30-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.30/node-v0.10.30-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.30/node-v0.10.30-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.30/
+
+Website: https://nodejs.org/docs/v0.10.30/
+
+Documentation: https://nodejs.org/docs/v0.10.30/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+4a16fc8768594cad5b4635e709afa035c2ffc0a1  node-v0.10.30-darwin-x64.tar.gz
+92111c64e874c2bee24f35aa4bf8ba665d76e73e  node-v0.10.30-darwin-x86.tar.gz
+35c3a2156e4ed7561a68efc70ee73069afe47174  node-v0.10.30-linux-x64.tar.gz
+d7f222b3519df636be8e47e8ddb2c2ecb03f4060  node-v0.10.30-linux-x86.tar.gz
+866541db248ced6b076e9fa13d6125159007a6a6  node-v0.10.30-sunos-x64.tar.gz
+6abad0a47c67a5eec24ba3022108b53bcb00b376  node-v0.10.30-sunos-x86.tar.gz
+0824d4d86ee38b58871344676162d797f4d74abb  node-v0.10.30-x86.msi
+9f20513f167c0e8ebb7ea5e9f633272e72e3bec4  node-v0.10.30.pkg
+bcef88d76c39147c79a28aa9e5d484564eb3ba7e  node-v0.10.30.tar.gz
+50ad72fd5646d92ae9afcd39ffb084f6de925903  node.exe
+22bd794611288027a6a1d995295f8f2ea092cb9e  node.exp
+88cfd5e9d42d006df4c0709e3b10ec2d198578d9  node.lib
+0f753fee3f82e98c232017a2977bb730bf73b42e  node.pdb
+ea4c28e8c5f6eaa296be82aba8f52d5a90cd9633  openssl-cli.exe
+abe93255f729922b55449f8c867ee9e82ae32cad  openssl-cli.pdb
+4843e84a9170f503289df25029a32a1876106e7f  pkgsrc/nodejs-ia32-0.10.30.tgz
+d283ef358257cc22ab421158d82906d388b024a8  pkgsrc/nodejs-x64-0.10.30.tgz
+674491bd761a4c3e7485d2284e110ad8e7974bc0  x64/node-v0.10.30-x64.msi
+b88ff4594e46a6e5403c84cd36805b8cf644f1df  x64/node.exe
+a77dd6018caca01cdebfad41062ae62b4d9e73b9  x64/node.exp
+46b4b56efa01d4feed4ea6a45b21e7e2fca6e5c8  x64/node.lib
+d922b71c9a900b3e8ead4ae3c4ed262612c92085  x64/node.pdb
+17678b0cba89ccec0478085257016b2b9c3f8c59  x64/openssl-cli.exe
+428b5fa970ef89265fa738062af401b7f4f0216f  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlPahtAACgkQfTP/nQJGQG0xFwCdFNK+Lw1hSjrlilasgcTdzeYf
+MEcAn1mliYSkRCFDrC2YLz8qsyrXY6tK
+=xxqm
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.31.md b/locale/uk/blog/release/v0.10.31.md
new file mode 100755
index 0000000000000..020e5ac14e82b
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.31.md
@@ -0,0 +1,86 @@
+---
+date: 2014-08-19T22:12:08.000Z
+version: 0.10.31
+category: release
+title: Node v0.10.31 (Stable)
+slug: node-v0-10-31-stable
+layout: blog-post.hbs
+---
+
+2014.08.19, Version 0.10.31 (Stable)
+
+* v8: backport CVE-2013-6668
+
+* openssl: Update to v1.0.1i
+
+* npm: Update to v1.4.23
+
+* cluster: disconnect should not be synchronous (Sam Roberts)
+
+* fs: fix fs.readFileSync fd leak when get RangeError (Jackson Tian)
+
+* stream: fix Readable.wrap objectMode falsy values (James Halliday)
+
+* timers: fix timers with non-integer delay hanging. (Julien Gilli)
+
+
+Source Code: https://nodejs.org/dist/v0.10.31/node-v0.10.31.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.31/node-v0.10.31.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.31/node-v0.10.31-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.31/x64/node-v0.10.31-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.31/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.31/node-v0.10.31-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.31/node-v0.10.31-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.31/node-v0.10.31-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.31/node-v0.10.31-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.31/
+
+Website: https://nodejs.org/docs/v0.10.31/
+
+Documentation: https://nodejs.org/docs/v0.10.31/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+863b3fa120f4122319c0caeead2c0ea609b08f72  node-v0.10.31-darwin-x64.tar.gz
+ad2b5fc039f7a2377b38f63ec4a8c681e2ec78f7  node-v0.10.31-darwin-x86.tar.gz
+0a47909aff7d52759972b0de915b624ede092ae2  node-v0.10.31-linux-x64.tar.gz
+7b6841e2ecdee8bd4dd441a43671f50d878d2d84  node-v0.10.31-linux-x86.tar.gz
+761dcfc520035cdd82f3813b9aac6645758e1319  node-v0.10.31-sunos-x64.tar.gz
+d854aea39eba1d567f4a8d09cfdadba9bc4c55cb  node-v0.10.31-sunos-x86.tar.gz
+bdec11406e09f5c86f117d263dd19bdcefbf2ca6  node-v0.10.31-x86.msi
+02819349cb1add9a80678478f9f1001747745497  node-v0.10.31.pkg
+80f2160b0525763b557742aa73d8dacf1a71e53c  node-v0.10.31.tar.gz
+96ce878618748fb893828cf2beafe7306123edd8  node.exe
+4313e2a9187781dfe39f6297e7826597b006dbb1  node.exp
+9d0e24717526cacbb45a72f743f6dd927dc27633  node.lib
+896d652532c5ca4a284fe768015d35a9ee31b205  node.pdb
+d394cb4b0c2503cbad4e5b9db88b506f36520190  openssl-cli.exe
+046e7d5e4a0db4f14f79c448d6eabe8ad9eb51bd  openssl-cli.pdb
+3d472f087c60904238de60af375054e187494913  x64/node-v0.10.31-x64.msi
+8fd456e9d10ce9da4433695d655ac56abf5816fa  x64/node.exe
+928bf1c65f853f9891697627a53325fa74506318  x64/node.exp
+fef0f550723e281b790408322b42358457598a53  x64/node.lib
+b20b8c41581ee2eeb326217eb2a76fd762eaec67  x64/node.pdb
+dacf285e445ca3cf9bf2147446d1c6621ec5e251  x64/openssl-cli.exe
+9fc30c82e3cfecf5e4e40bc7b45a20161113b66d  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlPzy7EACgkQfTP/nQJGQG1cxgCfQrq3/t+zd4tbXgqTiaYZTz07
+LIgAn0VWYPZzTsdIeu4F2sH+r8UNRdXr
+=zSrD
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.32.md b/locale/uk/blog/release/v0.10.32.md
new file mode 100755
index 0000000000000..72aa587e89bad
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.32.md
@@ -0,0 +1,86 @@
+---
+date: 2014-09-16T23:52:44.000Z
+version: 0.10.32
+category: release
+title: Node v0.10.32 (Stable)
+slug: node-v0-10-32-stable
+layout: blog-post.hbs
+---
+
+2014.09.16, Version 0.10.32 (Stable)
+
+* npm: Update to 1.4.28
+
+* v8: fix a crash introduced by previous release (Fedor Indutny)
+
+* configure: add --openssl-no-asm flag (Fedor Indutny)
+
+* crypto: use domains for any callback-taking method (Chris Dickinson)
+
+* http: do not send `0rnrn` in TE HEAD responses (Fedor Indutny)
+
+* querystring: fix unescape override (Tristan Berger)
+
+* url: Add support for RFC 3490 separators (Mathias Bynens)
+
+
+Source Code: https://nodejs.org/dist/v0.10.32/node-v0.10.32.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.32/node-v0.10.32.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.32/node-v0.10.32-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.32/x64/node-v0.10.32-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.32/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.32/node-v0.10.32-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.32/node-v0.10.32-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.32/node-v0.10.32-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.32/node-v0.10.32-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.32/
+
+Website: https://nodejs.org/docs/v0.10.32/
+
+Documentation: https://nodejs.org/docs/v0.10.32/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+e2e1e876514ee33b2dd019c25dcb4bc7cdaff414  node-v0.10.32-darwin-x64.tar.gz
+ff48e0be62f42e03218bbb00d5088251088f93bd  node-v0.10.32-darwin-x86.tar.gz
+fadefc15a992d21bd19d0d3ec174390d1e7fcb72  node-v0.10.32-linux-x64.tar.gz
+40fa3f0b0a3eaa3a6da7975b7935d0809d0e8ac7  node-v0.10.32-linux-x86.tar.gz
+b171f2285b5088f125a36e88b5313364302882e8  node-v0.10.32-sunos-x64.tar.gz
+ef213a76b4945ab13edb6833af47d8f77b4841ac  node-v0.10.32-sunos-x86.tar.gz
+f2538f0037c017f245db6b54c6b8198bec2868c9  node-v0.10.32-x86.msi
+6171c86864205400e5b670c1218614bb0c969107  node-v0.10.32.pkg
+1d748171ba2a9568853ccec442c5f62c46fccc20  node-v0.10.32.tar.gz
+2cb67e294fa7929bb5e51a3f51d53e6e8731bdc9  node.exe
+00d6d8a5137ec5d37660c16b72f756a9e2bc92fe  node.exp
+3688c7f807641af9f0c3858e34f5fc97ce8109fd  node.lib
+3b3746d07c24d25b0a00f9a5a2a2967554d3d8cb  node.pdb
+0fd292fd5911d1ef3d27dc60cf246c0dde2e8124  openssl-cli.exe
+8d51cd58f156a07785a618e3f9065e2d6ea24ee6  openssl-cli.pdb
+df83faf27410a6fb7f099c29338c52b7d4224e2f  x64/node-v0.10.32-x64.msi
+0a52577221e7c5272cac2e5ef324c031ab23f13d  x64/node.exe
+88682bc4dc10208fd2fb8505a1aa4155ab0e5790  x64/node.exp
+1ea6d44876afdaf263e378918f1edc35630561f7  x64/node.lib
+d1c5e98f218b3fec0ff3e6489ded94b8353191d6  x64/node.pdb
+14664ceeed377f0d0e5f3f5ad00b56e80ac7c323  x64/openssl-cli.exe
+653a3719ac038f9d05737c717cd44af9043d38c1  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlQYzUAACgkQfTP/nQJGQG23+ACffME3MVg4mQsWHq5vY7HAms+b
+brkAn32kNnqtOqV3QQ31xdJ+/4RLKLi/
+=R3H/
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.33.md b/locale/uk/blog/release/v0.10.33.md
new file mode 100755
index 0000000000000..3c63e54c916a8
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.33.md
@@ -0,0 +1,146 @@
+---
+date: 2014-10-23T19:12:33.000Z
+version: 0.10.33
+category: release
+title: Node v0.10.33 (Stable)
+slug: node-v0-10-33-stable
+layout: blog-post.hbs
+---
+
+This release handles the recent POODLE vulnerability by disabling SSLv2/SSLv3
+by default for the most predominate uses of TLS in Node.js.
+
+It took longer than expected to get this release accomplished in a way that
+would provide appropriate default security settings, while minimizing the
+surface area for the behavior change we were introducing. It was also important
+that we validated that our changes were being applied in the variety of
+configurations we support in our APIs.
+
+With this release, we are confident that the only behavior change is that of
+the default allowed protocols do not include SSLv2 or SSLv3. Though you are
+still able to programatically consume those protocols if necessary.
+
+Included is the documentation that you can find at
+https://nodejs.org/api/tls.html#tls_protocol_support that describes how this
+works going forward for client and server implementations.
+
+layout: blog-post.hbs
+---
+
+Node.js is compiled with SSLv2 and SSLv3 protocol support by default, but these
+protocols are **disabled**. They are considered insecure and could be easily
+compromised as was shown by [CVE-2014-3566][]. However, in some situations, it
+may cause problems with legacy clients/servers (such as Internet Explorer 6).
+If you wish to enable SSLv2 or SSLv3, run node with the `--enable-ssl2` or
+`--enable-ssl3` flag respectively.  In future versions of Node.js SSLv2 and
+SSLv3 will not be compiled in by default.
+
+There is a way to force node into using SSLv3 or SSLv2 only mode by explicitly
+specifying `secureProtocol` to `'SSLv3_method'` or `'SSLv2_method'`.
+
+The default protocol method Node.js uses is `SSLv23_method` which would be more
+accurately named `AutoNegotiate_method`. This method will try and negotiate
+from the highest level down to whatever the client supports.  To provide a
+secure default, Node.js (since v0.10.33) explicitly disables the use of SSLv3
+and SSLv2 by setting the `secureOptions` to be
+`SSL_OP_NO_SSLv3|SSL_OP_NO_SSLv2` (again, unless you have passed
+`--enable-ssl3`, or `--enable-ssl2`, or `SSLv3_method` as `secureProtocol`).
+
+If you have set `securityOptions` to anything, we will not override your
+options.
+
+The ramifications of this behavior change:
+
+ * If your application is behaving as a secure server, clients who are `SSLv3`
+only will now not be able to appropriately negotiate a connection and will be
+refused. In this case your server will emit a `clientError` event. The error
+message will include `'wrong version number'`.
+ * If your application is behaving as a secure client and communicating with a
+server that doesn't support methods more secure than SSLv3 then your connection
+won't be able to negotiate and will fail. In this case your client will emit a
+an `error` event. The error message will include `'wrong version number'`.
+
+layout: blog-post.hbs
+---
+
+2014.10.20, Version 0.10.33 (Stable)
+
+* openssl: Update to 1.0.1j (Addressing multiple CVEs)
+
+* uv: Update to v0.10.29
+
+* child_process: properly support optional args (cjihrig)
+
+* crypto: Disable autonegotiation for SSLv2/3 by default (Fedor Indutny,
+Timothy J Fontaine, Alexis Campailla)
+
+This is a behavior change, by default we will not allow the negotiation to
+SSLv2 or SSLv3. If you want this behavior, run Node.js with either
+`--enable-ssl2` or `--enable-ssl3` respectively.
+
+This does not change the behavior for users specifically requesting
+`SSLv2_method` or `SSLv3_method`. While this behavior is not advised, it is
+assumed you know what you're doing since you're specifically asking to use
+these methods.
+
+
+Source Code: https://nodejs.org/dist/v0.10.33/node-v0.10.33.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.33/node-v0.10.33.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.33/node-v0.10.33-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.33/x64/node-v0.10.33-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.33/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.33/node-v0.10.33-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.33/node-v0.10.33-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.33/node-v0.10.33-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.33/node-v0.10.33-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.33/
+
+Website: https://nodejs.org/docs/v0.10.33/
+
+Documentation: https://nodejs.org/docs/v0.10.33/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+03e72005a4ed612aa7a984d840f148bfb76f3c5f  node-v0.10.33-darwin-x64.tar.gz
+f40319ad8720d350ea45e56d5d9018c244482ddc  node-v0.10.33-darwin-x86.tar.gz
+4eba69caf7368d7f388700eb02996f85b06f457a  node-v0.10.33-linux-x64.tar.gz
+62a58b74851350a935e781d216484966b04ae097  node-v0.10.33-linux-x86.tar.gz
+aea7f541e21b57a07b15ab8d825c43f04a2f7440  node-v0.10.33-sunos-x64.tar.gz
+97b1d889a299afd6f0c0bb320646d92b7c498d01  node-v0.10.33-sunos-x86.tar.gz
+8a637d14609208d31fe466cd4961bec58a8f8f9b  node-v0.10.33-x86.msi
+81fcb80d7181768a7211a337c084b4a0b139dd74  node-v0.10.33.pkg
+69aeeade5fef622c3150cfc2b4a8f70eea1ef1ec  node-v0.10.33.tar.gz
+69275030a0549c27189a8f25396997deb70462ad  node.exe
+13dc334420abeaab9b7b3d184e0c5126250ce4e7  node.exp
+0379528f6d65eef73ceaeaf9acfe327648a9bc83  node.lib
+c23021453a5331954929cff26f7a7f5131af4351  node.pdb
+0fe937289a228a5bbc4fc97664eabbdc3a9792e5  openssl-cli.exe
+e1cff728f900bda134973666f75aae52a2d60e86  openssl-cli.pdb
+6173345fb3c8388abb2a415b99bb4962ebd8e123  x64/node-v0.10.33-x64.msi
+a4142d8a122317cc2e32caa643def2797e5f2cd7  x64/node.exe
+e067c6d6904a15a494b6b9f3e84cb07dc738c2ea  x64/node.exp
+63567e086a965f3ae452b6caace401592cd8c0ec  x64/node.lib
+e2cedfc1dd02f1d365314b162167ffb12d1cb0b1  x64/node.pdb
+68d60b60f03e703184a10d0a6adff69d9302b93e  x64/openssl-cli.exe
+4cd9e8bcf4fa9134a2e84473ec3d7d4b4cd31013  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlRJUxYACgkQfTP/nQJGQG2eNwCdGAIzkYTGHFohi2PVWKIKYmmq
+bvoAnAulTmcNMMLlXi1+Nmtt5SGyZIL8
+=0QtW
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.34.md b/locale/uk/blog/release/v0.10.34.md
new file mode 100755
index 0000000000000..05815675997c9
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.34.md
@@ -0,0 +1,92 @@
+---
+date: 2014-12-17T22:15:16.000Z
+version: 0.10.34
+category: release
+title: Node v0.10.34 (Stable)
+slug: node-v0-10-34-stable
+layout: blog-post.hbs
+---
+
+2014.12.17, Version 0.10.34 (Stable)
+
+* uv: update to v0.10.30
+
+* zlib: upgrade to v1.2.8
+
+* child_process: check execFile args is an array (Sam Roberts)
+
+* child_process: check fork args is an array (Sam Roberts)
+
+* crypto: update root certificates (Ben Noordhuis)
+
+* domains: fix issues with abort on uncaught (Julien Gilli)
+
+* timers: Avoid linear scan in _unrefActive. (Julien Gilli)
+
+* timers: fix unref() memory leak (Trevor Norris)
+
+* v8: add api for aborting on uncaught exception (Julien Gilli)
+
+* debugger: fix when using "use strict" (Julien Gilli)
+
+
+Source Code: https://nodejs.org/dist/v0.10.34/node-v0.10.34.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.34/node-v0.10.34.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.34/node-v0.10.34-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.34/x64/node-v0.10.34-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.34/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.34/node-v0.10.34-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.34/node-v0.10.34-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.34/node-v0.10.34-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.34/node-v0.10.34-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.34/
+
+Website: https://nodejs.org/docs/v0.10.34/
+
+Documentation: https://nodejs.org/docs/v0.10.34/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+8df2fdb333dd8edee59ceaf72738e3773c7863e6  node-v0.10.34-darwin-x64.tar.gz
+03168c2157baff928a397b85d8a7e6731b270f9a  node-v0.10.34-darwin-x86.tar.gz
+f064a252827c8129126f0e8ab3c8bf46f92506ec  node-v0.10.34-linux-x64.tar.gz
+fe0343f97c35aeb2c72bfd997dafde947ff44c23  node-v0.10.34-linux-x86.tar.gz
+4b3ccf37886f8056800ed174688c8782f9857d52  node-v0.10.34-sunos-x64.tar.gz
+ea891434436ed91d806201eb329d3c98f7e3c6b6  node-v0.10.34-sunos-x86.tar.gz
+7609d6dda6071e499a54656bbf85f16ed097c106  node-v0.10.34-x86.msi
+56e2aec59ac526d3daf607c7f50c2faf3e857cff  node-v0.10.34.pkg
+a342eb4d653ab48ba016c0c0c259565c822881cc  node-v0.10.34.tar.gz
+c71dce9dd3f3fbff34506a4edc3e37c59e31d7bd  node.exe
+ffc836802c3b2e25b38f4f73c0f044fef345e152  node.exp
+3e24f9c69826f320d303795c3564994e4311879f  node.lib
+8ccb4fdaaaec797e0762cea38112af5456fe3f7e  node.pdb
+fa0d0c098f475d6e1d6ad74c301a2361a9ac9888  openssl-cli.exe
+72772212ff62ecbf76ca468f402184e3f364de51  openssl-cli.pdb
+c54153231d0003792c4431cea38b9cb733a142b5  x64/node-v0.10.34-x64.msi
+b84684c92ed41a883452eb65a3010223378eb1ca  x64/node.exe
+c95e2dd11dc216c4b2d5a76852d2a0e7a8b247bc  x64/node.exp
+41db33520c33c576e4591771c371ae5f2644cadf  x64/node.lib
+d2ebec3f34e1a7e7969bfbe3330140f253b3cf9c  x64/node.pdb
+b678c997ad7747c4c35dc8c8362730fca5bad97c  x64/openssl-cli.exe
+f38f6eaae3aa2b11f3835b67f2dce04f4fc0fab8  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlSR/MIACgkQfTP/nQJGQG3ViACcC47u19WHh+vC4rfwJOoaRBFq
+4fUAnAm48HaJGYQ3sUlJlEq68LCwJfgL
+=yduE
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.35.md b/locale/uk/blog/release/v0.10.35.md
new file mode 100755
index 0000000000000..27d7566362de3
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.35.md
@@ -0,0 +1,78 @@
+---
+date: 2014-12-24T01:30:03.000Z
+version: 0.10.35
+category: release
+title: Node v0.10.35 (Stable)
+slug: node-v0-10-35-stable
+layout: blog-post.hbs
+---
+
+2014.12.22, Version 0.10.35 (Stable)
+
+* tls: re-add 1024-bit SSL certs removed by f9456a2 (Chris Dickinson)
+
+* timers: don't close interval timers when unrefd (Julien Gilli)
+
+* timers: don't mutate unref list while iterating it (Julien Gilli)
+
+
+Source Code: https://nodejs.org/dist/v0.10.35/node-v0.10.35.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.35/node-v0.10.35.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.35/node-v0.10.35-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.35/x64/node-v0.10.35-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.35/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.35/node-v0.10.35-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.35/node-v0.10.35-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.35/node-v0.10.35-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.35/node-v0.10.35-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.35/
+
+Website: https://nodejs.org/docs/v0.10.35/
+
+Documentation: https://nodejs.org/docs/v0.10.35/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+98f61cb09685ed45f2db6e0fc5ccbdd273204091  node-v0.10.35-darwin-x64.tar.gz
+8616029e0bb79dea1a974f97e42399fe24d3f4d7  node-v0.10.35-darwin-x86.tar.gz
+3a202a749492e48542d2c28220e43ef6dae084bc  node-v0.10.35-linux-x64.tar.gz
+c71823a584aa4cc778d73ff4ea89ed2b6f0ac250  node-v0.10.35-linux-x86.tar.gz
+56f2837da0cf1a302e7b3e6da770fba875a13a62  node-v0.10.35-sunos-x64.tar.gz
+d5713e3933a4ddfd9573a5326a2a5043fb50184f  node-v0.10.35-sunos-x86.tar.gz
+fca0fcf21a0dcd4ae02b319804a99e3cfeb83ee3  node-v0.10.35-x86.msi
+3781eae7bcbf55d87b528b3a0b3c9524f94e66a4  node-v0.10.35.pkg
+bcad4ebf56516676f93b28377f03d3b3ea52795c  node-v0.10.35.tar.gz
+16a363d39f08fa5119f3ca82dcd08a6d67110bcb  node.exe
+43197d7d92e9a6eead6060288173941041dac9a4  node.exp
+c0cc751dcc915234b15cfc210cdd459b78148435  node.lib
+9ff7f9e7959c196a97cc53400d86602da7f5a74d  node.pdb
+bfc708da1114ac539cd43738145d8cc1f5e39f6f  openssl-cli.exe
+f54d55939d9493f934dc36baa169429df8fb47f4  openssl-cli.pdb
+c95e8041b5b16488eb2522fa072061690f6ef0cb  x64/node-v0.10.35-x64.msi
+7f31dd9c636e658f7386e8f8b2ef3be885158c55  x64/node.exe
+6df8b6b95024e5f0bd7f39cd5a83341ae227e8aa  x64/node.exp
+82fa5ea193f4aac3267b58c8c5f581952ae46fea  x64/node.lib
+e6e4df82798d36343f0f0e872a36d15172e86f70  x64/node.pdb
+ae6917172865a8fa3ddfdf3bc93a863043742fa9  x64/openssl-cli.exe
+b9bb9409cbf63c20b2c2e7db9f5f323cfd400771  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlSYki4ACgkQfTP/nQJGQG0BYQCeNpRS2Bj8IJPfRomoaXMJgr+f
+p/IAoOukOg36PqphzVe2C2kEUcIxb2H1
+=fA07
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.36.md b/locale/uk/blog/release/v0.10.36.md
new file mode 100755
index 0000000000000..0d8bf1d69be5a
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.36.md
@@ -0,0 +1,78 @@
+---
+date: 2015-01-26T20:26:06.000Z
+version: 0.10.36
+category: release
+title: Node v0.10.36 (Stable)
+slug: node-v0-10-36-stable
+layout: blog-post.hbs
+---
+
+2015.01.26, Version 0.10.36 (Stable)
+
+* openssl: update to 1.0.1l
+
+* v8: Fix debugger and strict mode regression (Julien Gilli)
+
+* v8: don't busy loop in cpu profiler thread (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.36/node-v0.10.36.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.36/node-v0.10.36.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.36/node-v0.10.36-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.36/x64/node-v0.10.36-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.36/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.36/node-v0.10.36-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.36/node-v0.10.36-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.36/node-v0.10.36-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.36/node-v0.10.36-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.36/
+
+Website: https://nodejs.org/docs/v0.10.36/
+
+Documentation: https://nodejs.org/docs/v0.10.36/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+ff5e9ab73aa025473d5601e6b71a13d0208caae9  node-v0.10.36-darwin-x64.tar.gz
+e6d81d13d8917b94d17c503b4a7cc640c82cb1f1  node-v0.10.36-darwin-x86.tar.gz
+350df861e161c34b97398fc1b440f3d80f174cf9  node-v0.10.36-linux-x64.tar.gz
+1d486043f200ae2d666e15f3e55ba9c0f07d67e3  node-v0.10.36-linux-x86.tar.gz
+925d107a0292355d2f06385ebed071b70bd23d13  node-v0.10.36-sunos-x64.tar.gz
+91202baf7c4ef7d2c11954fbcb716daa1058ae79  node-v0.10.36-sunos-x86.tar.gz
+80b1db379635f10f2f6e031b996539db47340b0b  node-v0.10.36-x86.msi
+2596c17e373ba3e57023272c7f8fb2132ff4e157  node-v0.10.36.pkg
+7e89d33ad0e56f6ca517f43a4a7b56079db18420  node-v0.10.36.tar.gz
+5ee17e953525551ca059f2c768db1b867362d804  node.exe
+cf4dbb65e4eeed1b4ce7be20830f6c1d7db6fb08  node.exp
+965af2cfb72e68449d1cc55d7e1e44087b901b34  node.lib
+e07b30c6c810a20d8312261b723d0097a7e42532  node.pdb
+ebdf10d8edc1c44a62cee8422351c1cd4e6a0fa0  openssl-cli.exe
+b70949a5f041a3d95d26b95675757883f57079e6  openssl-cli.pdb
+2e89fadf70f9fbcecd7ebb9abaf6f98bdeaf84ab  x64/node-v0.10.36-x64.msi
+d4b5bcdf92433f273d64e067468666fa63f5e21b  x64/node.exe
+43cf4a20f52e80c4a4eecbb1b88dbfdc83067b77  x64/node.exp
+bea04b572bcb7b8dfce1fc7360b64feb3a6b9b83  x64/node.lib
+7fb057fd7466cdc62510ed75c340fca5e12feb58  x64/node.pdb
+a61d7b8d8a59eba15bcd616c9a3eb7fde8941aff  x64/openssl-cli.exe
+df7091913d9d013ceb20b18184ea69856d435daa  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlTGm+oACgkQfTP/nQJGQG1l3wCgme2qcVmnzwI76xf4XFP1Cv7J
+96EAnRBumCd17whHm5PgSzopMtqvu0+g
+=E09G
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.37.md b/locale/uk/blog/release/v0.10.37.md
new file mode 100755
index 0000000000000..82807e01c1c5e
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.37.md
@@ -0,0 +1,99 @@
+---
+date: 2015-03-14T18:09:24.000Z
+version: 0.10.37
+category: release
+title: Node v0.10.37 (Maintenance)
+slug: node-v0-10-37-stable
+layout: blog-post.hbs
+---
+
+2015.03.11, Version 0.10.37 (Maintenance)
+
+This release comes with a fix for
+[CVE-2015-0278](https://bugzilla.redhat.com/show_bug.cgi?id=1194651), which
+was a vulnerability in libuv < 0.10.34 caused by insufficient priviledges
+dropping. More info about this type of issues can be found in [the CERT secure
+coding guide](https://www.securecoding.cert.org/confluence/display/c/POS36-C.+Observe+correct+revocation+order+while+relinquishing+privileges).
+
+* uv: update to 0.10.36 (CVE-2015-0278)
+
+* domains: fix stack clearing after error handled (Jonas Dohse)
+
+* buffer: reword Buffer.concat error message (Chris Dickinson)
+
+* console: allow Object.prototype fields as labels (Julien Gilli)
+
+* V8: log version in profiler log file (Ben Noordhuis)
+
+* http: fix performance regression for GET requests (Florin-Cristian Gavrila)
+
+
+Source Code: https://nodejs.org/dist/v0.10.37/node-v0.10.37.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.37/node-v0.10.37.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.37/node-v0.10.37-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.37/x64/node-v0.10.37-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.37/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.37/node-v0.10.37-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.37/node-v0.10.37-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.37/node-v0.10.37-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.37/node-v0.10.37-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.37/
+
+Website: https://nodejs.org/docs/v0.10.37/
+
+Documentation: https://nodejs.org/docs/v0.10.37/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+a7ac414715a1b6a45a6c285b1f13001050ccad5f  node-v0.10.37-darwin-x64.tar.gz
+c45048cf791996fe0328b79f4e811eeab23ebf14  node-v0.10.37-darwin-x86.tar.gz
+249044358cad8273015ae6c6ea1f12d170ab799b  node-v0.10.37-linux-x64.tar.gz
+e4a559811935e4430b70eea090a4f696ac3b0db6  node-v0.10.37-linux-x86.tar.gz
+cbc29c56004c1cf39b47e6c83b04d4b2f3573126  node-v0.10.37-sunos-x64.tar.gz
+fad304ebebaaaf644b0a52c1735f3e2bf75be085  node-v0.10.37-sunos-x86.tar.gz
+8a76acf1711e61e7a79e1c954970773ba849b18b  node-v0.10.37-x86.msi
+7d10d1682e7eea46321f72d3b77cca5008eda087  node-v0.10.37.pkg
+6535468508594e57a27d2f13d02f437dc7b00e2d  node-v0.10.37.tar.gz
+226db2e396e562ce22985945d73c530c4c0201f5  node.exe
+28d91cf2f58df8d379eee9ae78e202bfac2bc0fb  node.exp
+44d848597da44d6fb9872ca3c7156f1aaf67b736  node.lib
+3bfd0b245987a388d0158106f76f231f31fb40de  node.pdb
+d735860e19223d8ee4f251664d2faa7dafbfe4a5  openssl-cli.exe
+65a2536188371974e07ff7f5dff9b24567f19f1e  openssl-cli.pdb
+2e8c2b71887729a889c0d269fa8f15b990e20f49  x64/node-v0.10.37-x64.msi
+f30dae0ddc89251ea25b0e5d63641ffaaa950b89  x64/node.exe
+ab3094bc285a291d3a60f73e5b10804f4d36f28a  x64/node.exp
+246bc9ebc69c5e3cf2a3570b72dc2be42009f0e1  x64/node.lib
+9a3b5db03976eca32a411b4ba47f91bbe954d882  x64/node.pdb
+fbd16e45eb26c01c41dc6124bb29ac03600f7373  x64/openssl-cli.exe
+8bb94314fdc66e425282e14b942df80ff8fc2c6f  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVARH+AAoJEFCjBR+IjGKNv7UP/A2kldN2nr5aErTi3r9J3khf
+z9ix+zPtOnY0tEdo+eWvD5T/qnwpzlK31h8LJORvBoUy5gF+H8/YbUhx3ffndNCK
+YLhuUXVFD5560n1Gb2h8vPq/ooa4qB7sMe/v19ptIQTXf023l16RJLQc3FptITi2
+rl3DL8XcX2gd7lYaCrlLcSgPpW+9j2vUKObh+Z0vFIbHR4bvvnQcXuEwoJyoGDZG
+hg5e4A2tz3zQJNtYOAfsIH4qpES6zGgX/uTIF08uXRfmWEqf4SZ0v2MSBUQHC2Lg
+7wlfaFLiW638pzjNMMsR7y51rs5bhQBYOJZAZGYuD8oDE2JXN1uI3eofs1rh43/T
+sSM8SKGg1l1C6/fo/uLs6VMQyK+j5j1OdWUFw5jP/Tj9GdONFfCQSHlq0Spjr49t
++unJXF6oN6Oc7maYYfxsWs0SfNnzhvWBFwRvmv5HU9bS/zfOHguRcET61xMI3HEc
+cJf1CTN0Pl9KJMCu3vhWAZL23t4pJiSlg94RvRBErgK53AiT8tRfPdofDj4mtJl6
+IYcJRFsF8Wu0Ez4LsyBFaurLjCPfXjg5Ju4ww3AkdvJ/RuRU5nyu22X9Z8a68lop
+F8NSIi8lr6GZoIyiI0tYPzj/uAlOfj6CWk3wOcSRErEd6/joGfYG1tgA+33yRpbD
+41gTBTIr961/1GMvkfZY
+=A1UM
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.38.md b/locale/uk/blog/release/v0.10.38.md
new file mode 100755
index 0000000000000..448dcc0238ccb
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.38.md
@@ -0,0 +1,87 @@
+---
+date: 2015-03-23T21:43:54.000Z
+version: 0.10.38
+category: release
+title: Node v0.10.38 (Maintenance)
+slug: node-v0-10-38-maintenance
+layout: blog-post.hbs
+---
+
+This release upgrades OpenSSL to version 1.0.1m, which includes fixes for
+[several CVEs that were disclosed
+recently](https://www.openssl.org/news/secadv_20150319.txt).
+
+2015.03.23, Version 0.10.38 (Maintenance)
+
+* openssl: upgrade to 1.0.1m (Addressing multiple CVEs)
+
+
+Source Code: https://nodejs.org/dist/v0.10.38/node-v0.10.38.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.38/node-v0.10.38.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.38/node-v0.10.38-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.38/x64/node-v0.10.38-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.38/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.38/node-v0.10.38-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.38/node-v0.10.38-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.38/node-v0.10.38-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.38/node-v0.10.38-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.38/
+
+Website: https://nodejs.org/docs/v0.10.38/
+
+Documentation: https://nodejs.org/docs/v0.10.38/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+402cff55fbff191dad26d5be7eb0e85e577e523b  node-v0.10.38-darwin-x64.tar.gz
+b5a2343bf17518a50126df219e5f7ac6c52f9fb9  node-v0.10.38-darwin-x86.tar.gz
+01552572a90d4c875c13b1002cd89d081777cc18  node-v0.10.38-linux-x64.tar.gz
+62cec3eaf69b728c7ad3fd33fed51e1207711592  node-v0.10.38-linux-x86.tar.gz
+edb4752b033f7c4e3a036c44d5ebe29015c339c3  node-v0.10.38-sunos-x64.tar.gz
+857394b9b5d12f002b334e9002400137f1106284  node-v0.10.38-sunos-x86.tar.gz
+a43e9cd0e3d139249299cc8993816136774095e0  node-v0.10.38-x86.msi
+5487794362734b6752f0b4c48d0f47f74e0d7e4e  node-v0.10.38.pkg
+e277de0c48ea3ab8b2eba85cd6e144ad94af0ba9  node-v0.10.38.tar.gz
+de6c8ce8ca4b9dd0e8e27abcb828827a6d35c380  node.exe
+039302c3153e1f0a0ea616b1100cf4842c94ce98  node.exp
+16e2f5ce2ccae3d00c89b184c2463408a048aff2  node.lib
+0bdf9107f4f722791d6070de19086532d9f99f8c  node.pdb
+dbf4b9122ba9c25c1565107b22d17b7f2224a6de  openssl-cli.exe
+fa30a547be5025e93b1128473e2e39a054060ff8  openssl-cli.pdb
+deaf8d1fa744535bfdca226c020f4241a414f387  x64/node-v0.10.38-x64.msi
+56ce452ba1e21b1a4fa2f0105f7ac76951816a21  x64/node.exe
+1f6121da15e24cbbeb39c014b4ec72b6aaed7845  x64/node.exp
+3fa25463d54fc127780b9cc532998857cba663e6  x64/node.lib
+c7f261fff9d255974ec3be1b0133053ed890f5ad  x64/node.pdb
+dba0f64430fe01217667ed68e60626fac5cead8f  x64/openssl-cli.exe
+c25d8fad5c2b0152f4e01bd577c60aada98c21d9  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVEIkMAAoJEFCjBR+IjGKNVF8QAKD0mgy9E5rCHdMXW+rMvxa6
+KniwDVcJJQbhXOkZMWHZZgaz/EKB+5IH9P8MBvD6hRN2t4eKKAX2o4MWlNJHLr63
+x0Cu2hEhbR/Xc5FimG10zCu3nEtfiYhMXhG2QlLfs9X18IaDaYO19yE2XS8qjwwH
+PPo9jJkWzFtRPPL/4DkcNKmLgVQyTEMH3Em1MZZAALEgiYcySUTn0+2Bru0Ab7kV
+2Vrbn9d2ZR0Qg9hbV9JGjPcmdAR1d+NoXp9Bw+ZUaIa4k59f5WqQKVAUHzw4QRSH
+wJfA5bOlbNm4l2DB+aKvCHN+Y3kqo9xH/3eH3LcnVMX7vcmJqqDUI57vVYPEi1ZW
+x5AcIPM84cGRMNA0rS+jWbS8oi+7AvGEQZm/rX30m75RMWSpqdmyhEina7B5WI2I
+cEwaltFW15zjUvZqLIPL5rN9j/QC87GZ2gqgWclGuDH5lzU2H6CoieAP0JAK8ny0
+cLLGa2SZS3Tt2oIVw/+KiQ9RKgk70mk8+CIkUyGhRtGiQ4GFDqMUYjjK5/G32QuH
+fKE0Bs3KdiIkxjRdzuW40fHQTjtERa3gzYQUBA3walYjhjKtu4uburc/8DW1wTR0
+HurzRflJ2ILrA2to8AnU57FjA3g8Dq5u1QdFksixHxCOdMu05UQ4rRd0eVwcQfZc
+w5Usx1Q+lMwpWd/yYe66
+=jL5j
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.39.md b/locale/uk/blog/release/v0.10.39.md
new file mode 100755
index 0000000000000..a0e64309cae9c
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.39.md
@@ -0,0 +1,110 @@
+---
+date: 2015-06-22T16:45:28.000Z
+version: 0.10.39
+category: release
+title: Node v0.10.39 (Maintenance)
+slug: node-v0-10-39-maintenance
+layout: blog-post.hbs
+---
+
+With this new release, OpenSSL has been upgraded to 1.0.1o to fix [several
+security vulnerabilities](http://openssl.org/news/secadv_20150611.txt). Two of
+them affect Node.js directly: Logjam and CVE-2015-1788.
+
+Regarding Logjam, OpenSSL has added protection for TLS clients by rejecting
+handshakes with DH parameters shorter than 768 bits. It means that _upgrading
+to this release of Node.js may prevent TLS clients written in node from
+connecting to servers using short DH parameters_.
+
+Although it is a breaking change in a maintenance version, the Node.js TSC
+determined that this is the best path forward to ensure the security of
+software written with this and future maintenance versions of node. Should you
+encounter any issue with this release related to TLS clients not being able to
+connect to servers using short DH keys, please create an issue at
+https://github.com/joyent/node/issues.
+
+As for CVE-2015-1788, before this release, TLS programs (including servers)
+written with Node.js are vulnerable to Denial Of Service attacks.
+
+2015.06.18, Version 0.10.39 (Maintenance)
+
+* openssl: upgrade to 1.0.1o (Addressing multiple CVEs)
+
+* install: fix source path for openssl headers (Oguz Bastemur)
+
+* install: make sure opensslconf.h is overwritten (Oguz Bastemur)
+
+* timers: fix timeout when added in timer's callback (Julien Gilli)
+
+* windows: broadcast WM_SETTINGCHANGE after install (Mathias Küsel)
+
+
+Source Code: https://nodejs.org/dist/v0.10.39/node-v0.10.39.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.39/node-v0.10.39.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.39/node-v0.10.39-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.39/x64/node-v0.10.39-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.39/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.39/node-v0.10.39-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.39/node-v0.10.39-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.39/node-v0.10.39-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.39/node-v0.10.39-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.39/
+
+Website: https://nodejs.org/docs/v0.10.39/
+
+Documentation: https://nodejs.org/docs/v0.10.39/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+f51855f96e3b69af87112161f155ac270eb5bd33  node-v0.10.39-darwin-x64.tar.gz
+8316054cdd8cc482f3c6b89434c1fe224039bd26  node-v0.10.39-darwin-x86.tar.gz
+97583ea9daf469bcb1691ac8a34fe5b64a8deaf5  node-v0.10.39-linux-x64.tar.gz
+d3038a590e99a6eb877b41b39aba503464766347  node-v0.10.39-linux-x86.tar.gz
+7b8d190a2e17ad809c7b892178d5410f99328f76  node-v0.10.39-sunos-x64.tar.gz
+de09892495d8f6dec3031142ba47d5d02c8f53e7  node-v0.10.39-sunos-x86.tar.gz
+2e019ab13a78fb994a8c6c10e72979b56ddaaf0d  node-v0.10.39-x86.msi
+2c1a7c3aea6dac03e49181f20c45b7d1315068a2  node-v0.10.39.pkg
+b53d33b5e1b980b2fe9009fec810187eaa6b8144  node-v0.10.39.tar.gz
+d556c55a815960e0ab705aa9225da996f47f3ef9  node.exe
+75201237f362bb27af9652487fb5e74b90edc1ba  node.exp
+16d7d5029a0e9a0e21e04a522493a3d973a7eed0  node.lib
+4e95ba82cc3fbd26d7da93549c7222ff941760a5  node.pdb
+b779fd3b7a70c688b7ab0313f2a62edac9b4cbe1  openssl-cli.exe
+9642c12bbdbb03c163c5d3d9e539243730af0595  openssl-cli.pdb
+b1183e7597b9b9724bb1d9892843322afeca95aa  x64/node-v0.10.39-x64.msi
+eb76635c7bd9a321ac6f97043226ece73bbc4df4  x64/node.exe
+fe6ae97961692d595706665533e23cc4d94d2087  x64/node.exp
+9ded23cb299cf5d03e0f7783b5d195b1a3a91ff4  x64/node.lib
+11832ff8d3409742a90be94738031ebb51c857ad  x64/node.pdb
+438e8cf3732b0116a7bee074afc6fbc48c45f0fb  x64/openssl-cli.exe
+1855d0a946882b9a4d39d57893ab4e2e3a3c9f02  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJViDuaAAoJEFCjBR+IjGKNff8P/jOOp4smwRKWfpi3stsorvlX
+3jk/WNXOIUO/qnx5cJA0XrAxzmL+fOOWXlMaacJfAEiy96EQHryjuCasy1nrT+Ae
+7qDoXJCnuCgnconV2RIP0otZmlHyTmxRA7DYwbhpOcScCqJoO4HV6fDo50pU+Bdg
+HBb5/M3Pm6Cep2Iuv54I1p0mbGVubZxfxmsjkLoEv4KIzmVFit65pZBSA+9DaomK
+QqTCnvWg/lCmnSrQQWTTFC0crqB6eO9PP/v63KUQc3G5K/FjhIfJ6j+PPvlBjOfx
+N37bxC6YJgVD0axyrxvh2VEhmsJZ06JiI1PUdp91C8klbOp6jeCLFFi5axA0Gjmr
+HN6ES5IfnZH26pUFB5M97Cydug+3tM9YPa9jVHwJUdgzNrSVxSlgdQHi4xVHnrTL
+xEESXQQWL7kYE+t9oy6i9B93FphsQvqiuI5i4QXj1WabCOEgywVWyZF741wkC8Lu
+Y/97CvcPNWoDHR7H+cbrO3B4iedFpKDaxNb1vrpZRgTHiohrkW8Ec2VB00RgCvJi
+pPKGxsv70Wby5V8at120CsPLuGW8xCihMpYRkSEyIZodrq0YCtN87COvPe7GpyFk
+PnfMhk0U9ANfeMFMK3qcDT+iQAHuLLmD3/aEN6RHc5b2fwyXc4+SqT55jpyegbb4
+TbGw60glPAi+FQhZZoF0
+=I4d1
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.4.md b/locale/uk/blog/release/v0.10.4.md
new file mode 100755
index 0000000000000..23eb9b25426db
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.4.md
@@ -0,0 +1,88 @@
+---
+date: 2013-04-11T17:52:56.000Z
+version: 0.10.4
+category: release
+title: Node v0.10.4 (Stable)
+slug: node-v0-10-4-stable
+layout: blog-post.hbs
+---
+
+2013.04.11, Version 0.10.4 (Stable)
+
+* uv: Upgrade to 0.10.4
+
+* npm: Upgrade to 1.2.18
+
+* v8: Avoid excessive memory growth in JSON.parse (Fedor Indutny)
+
+* child_process, cluster: fix O(n*m) scan of cmd string (Ben Noordhuis)
+
+* net: fix socket.bytesWritten Buffers support (Fedor Indutny)
+
+* buffer: fix offset checks (Łukasz Walukiewicz)
+
+* stream: call write cb before finish event (isaacs)
+
+* http: Support write(data, 'hex') (isaacs)
+
+* crypto: dh secret should be left-padded (Fedor Indutny)
+
+* process: expose NODE_MODULE_VERSION in process.versions (Rod Vagg)
+
+* crypto: fix constructor call in crypto streams (Andreas Madsen)
+
+* net: account for encoding in .byteLength (Fedor Indutny)
+
+* net: fix buffer iteration in bytesWritten (Fedor Indutny)
+
+* crypto: zero is not an error if writing 0 bytes (Fedor Indutny)
+
+* tls: Re-enable check of CN-ID in cert verification (Tobias Müllerleile)
+
+
+Source Code: https://nodejs.org/dist/v0.10.4/node-v0.10.4.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.4/node-v0.10.4.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.4/node-v0.10.4-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.4/x64/node-v0.10.4-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.4/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.4/node-v0.10.4-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.4/node-v0.10.4-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.4/node-v0.10.4-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.4/node-v0.10.4-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.4/
+
+Website: https://nodejs.org/docs/v0.10.4/
+
+Documentation: https://nodejs.org/docs/v0.10.4/api/
+
+Shasums:
+
+```
+0bebde7d5d698e93fd96ad1b5d223166cd0c5892  node-v0.10.4-darwin-x64.tar.gz
+8d847a68f8178b102c72c3f35861f496e12fe455  node-v0.10.4-darwin-x86.tar.gz
+28e3a4d2702a13454a3c1d9e1035ee07ef8764bc  node-v0.10.4-linux-x64.tar.gz
+839be3dfe4504072e372b2a3f597e0b0f4e26331  node-v0.10.4-linux-x86.tar.gz
+94d68094afacb70b71a3393f07f81eff6e8a14f1  node-v0.10.4-sunos-x64.tar.gz
+6b287dcdb9498cb7d59acbab8faaea4455ffe2c4  node-v0.10.4-sunos-x86.tar.gz
+1863868f40d4e3af876d21976d9b06a9e99d1dcf  node-v0.10.4-x86.msi
+bafb80cff0ada4cdfd98c917459d627d7df408d5  node-v0.10.4.pkg
+901c1410b7c28a79644292567d3384255f3a6274  node-v0.10.4.tar.gz
+73b5f6eaea8417f4b937bf99812263dc170696e0  node.exe
+85064a019b8e6416152ae609ace81469331f773c  node.exp
+e5b26b8480c3979ddab5ea3bf6bfb0fbef9ecb54  node.lib
+0098965a1a2206a1fc148ab776d182018b80d0ba  node.pdb
+31bd64f33436fa543f0599f80c5df97c14b10224  x64/node-v0.10.4-x64.msi
+8280dbeb5a1296fe3496f57376a619467c4c6263  x64/node.exe
+e317e0db2693e42851f3774a20dc98e02a9a90fe  x64/node.exp
+7f0aa389465ac7983a4c099671bb52c7a6988676  x64/node.lib
+a7fb9a08d6337225dd8c5b1db5fb95a2f39fd773  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.40.md b/locale/uk/blog/release/v0.10.40.md
new file mode 100755
index 0000000000000..25b6601cf3877
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.40.md
@@ -0,0 +1,91 @@
+---
+date: 2015-07-09T21:57:30.000Z
+version: 0.10.40
+category: release
+title: Node v0.10.40 (Maintenance)
+slug: node-v0-10-40-maintenance
+layout: blog-post.hbs
+---
+
+This release upgrades OpenSSL to version 1.0.1p, which fixes a security
+vulnerability (CVE-2015-1793). More details about the vulnerability can be
+found [on OpenSSL's website](http://openssl.org/news/secadv_20150709.txt).
+
+2015.07.09, Version 0.10.40 (Maintenance)
+
+* openssl: upgrade to 1.0.1p (CVE-2015-1793)
+
+* V8: back-port JitCodeEvent patch from upstream (Ben Noordhuis)
+
+* win,msi: create npm folder in AppData directory (Steven Rockarts)
+
+
+Source Code: https://nodejs.org/dist/v0.10.40/node-v0.10.40.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.40/node-v0.10.40.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.40/node-v0.10.40-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.40/x64/node-v0.10.40-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.40/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.40/node-v0.10.40-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.40/node-v0.10.40-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.40/node-v0.10.40-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.40/node-v0.10.40-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.40/
+
+Website: https://nodejs.org/docs/v0.10.40/
+
+Documentation: https://nodejs.org/docs/v0.10.40/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+806f588415bd246fe3ce09f2e5e4058e0340f528  node-v0.10.40-darwin-x64.tar.gz
+33bc43201294f4f6bad40c1f24b33ac9134ca279  node-v0.10.40-darwin-x86.tar.gz
+b48fdcf8421dc0834d371ab22d9d71f647c5e210  node-v0.10.40-linux-x64.tar.gz
+5604060e5a611ecded9516107069dd41511a377d  node-v0.10.40-linux-x86.tar.gz
+ab3de94a85d808af84a1c141a2fb6f68f7a7e4c6  node-v0.10.40-sunos-x64.tar.gz
+3f8aad4331088f496dbb736f38a53557a0208311  node-v0.10.40-sunos-x86.tar.gz
+54912b14b3e6184ee13200257d52bc1447f70c02  node-v0.10.40-x86.msi
+fa2100b3ea6ba4bf90a19dae9df95b3d299fc0f2  node-v0.10.40.pkg
+b5086ffabd628eb2f76808171cfdf0390f8cd935  node-v0.10.40.tar.gz
+43f9cc9ac48298eacc4c5ea06019f741a5a9208e  node.exe
+489db10965b9216f38a14a94d43a5ce7430d77f7  node.exp
+97d0a62b816465fe11a7df61e0a8b5e9d3ac3cca  node.lib
+3211a329e7c0123c0806638a5b3dd813cb6b7b3f  node.pdb
+82b08ce94498bd112f07498ad12162db659cb816  openssl-cli.exe
+704da37a22d7e1a6addfea8af1f5a41494d74d55  openssl-cli.pdb
+037634b6620e04f82c383f037f3787fa55b23085  x64/node-v0.10.40-x64.msi
+fff288e67c2e68661b8e7629424c76c879444fd2  x64/node.exe
+2f483929469e378a49e62162ea71183b4335e373  x64/node.exp
+f163cfc4f8a8db63cb656efb4a034d33ba764750  x64/node.lib
+cfc5b981aaabbc8eeed5ae33baf1539365b31d33  x64/node.pdb
+c9b822d4bf1848471c58e6206be9e5178bf9ffb7  x64/openssl-cli.exe
+2039071281de24a659622afc399d1ecc0bcd67c0  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVnu46AAoJEFCjBR+IjGKNjlAP/2WOSNOzBOrd3JM5Dpr1mWgz
+X7s3ldKctDdATJR563USrZ4LpkHqUpbIul8gemU9ncxxpt4DQsjpTWgGjwCl9Zoj
+HxuwTnJI+J/9Hqgk8CYEuvPrsLzYgUOmZ0jwGlXg5DQS86amgaxr7Jh6Klq+wTTw
+mMsNDI096pPFN3tGGUjNbiVeyaJjsDLwdXkxRkGplH2jyaGa1MEggd2fwmO7WWAS
+LJprVMq3SlPWkWmMGIr8xppVwd9SiQMuJ/9ep3G2f6u2T0EFtImGoY6bxGe98yup
+RNg2arwl4nl3XkZqUSQUyCsVVrzYQzlvb0gCI+nqqynqpP2tuo7XiELF9DFKnK76
+lSoosotLhZTTedWDa/r8B0Ne6Ou8vG4KmnoMt72Xxf9RZafvv2pYy9HyB7FbhSYF
+vMPsF/3oF7mmgjv5Eu9xkr98XK2Yxid9SiM7kGTOo2i1kDLpHjN2h0bDVjhAHJ7D
+U2FOm3ZxaVvAn4EF+KHqPAKRgOxZjgZ3gZmqShpbxoIWKdIBxxreYSUG6Z5iaCQM
+/qlsZj15opKjZIsMtDsLw02dOus+xmVi67pz4wx2/y6xeOkf4DiAzdKL6WSZmC5N
+CN7DUXu6Uj68mBGCZFCL5a6jKO//DH6jWEAQEL3PqJH5VSVIpAyvWsuuPetCsKYk
+En8uXZ6p+A/Z6+Aofbwu
+=vEVE
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.41.md b/locale/uk/blog/release/v0.10.41.md
new file mode 100755
index 0000000000000..9b24f52f48fdf
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.41.md
@@ -0,0 +1,120 @@
+---
+date: 2015-12-04T03:01:00.000Z
+version: 0.10.41
+category: release
+title: Node v0.10.41 (Maintenance)
+slug: node-v0-10-41
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+**This is an important security release**. All Node.js users should consult our [December Security Release Summary](/en/blog/vulnerability/december-2015-security-releases/) for details on patched vulnerabilities.
+
+### New build infrastructure
+
+This is the first v0.10 release made with the new build infrastructure operated by the Node.js Foundation. Even though we have done our best to ensure that the build processes and tools are as close as possible to the previous infrastructure, it is possible that some unexpected issues arise from the changes. Please file bug reports on the [Node.js GitHub repository](https://github.com/nodejs/node) if you have trouble upgrading from v0.10.40 to v0.10.41.
+
+### Notable changes
+
+* **build**: Add support for Microsoft Visual Studio 2015
+* **npm**: Upgrade to v1.4.29 from v1.4.28. A special one-off release as part of the strategy to get a version of npm into Node.js v0.10.x that works with the current registry (https://github.com/nodejs/LTS/issues/37). This version of npm prints out a banner each time it is run. The banner warns that the next standard release of Node.js v0.10.x will ship with a version of npm v2.
+* **openssl**: Upgrade to 1.0.1q, containing fixes CVE-2015-3194 "Certificate verify crash with missing PSS parameter", a potential denial-of-service vector for Node.js TLS servers using client authentication; TLS clients are also impacted. Details are available at <http://openssl.org/news/secadv/20151203.txt>. (Ben Noordhuis) https://github.com/nodejs/node/pull/4133
+
+### Commits
+
+* [[`16ca0779f5`](https://github.com/nodejs/node/commit/16ca0779f5)] - src/node.cc: fix build error without OpenSSL support (Jörg Krause) [nodejs/node-v0.x-archive#25862](https://github.com/nodejs/node-v0.x-archive/pull/25862)
+* [[`c559c7911d`](https://github.com/nodejs/node/commit/c559c7911d)] - **build**: backport tools/release.sh (Rod Vagg) [#3965](https://github.com/nodejs/node/pull/3965)
+* [[`268d2b4637`](https://github.com/nodejs/node/commit/268d2b4637)] - **build**: backport config for new CI infrastructure (Rod Vagg) [#3965](https://github.com/nodejs/node/pull/3965)
+* [[`c88a0b26da`](https://github.com/nodejs/node/commit/c88a0b26da)] - **build**: update manifest to include Windows 10 (Lucien Greathouse) [#2838](https://github.com/nodejs/node/pull/2838)
+* [[`8564a9f5f7`](https://github.com/nodejs/node/commit/8564a9f5f7)] - **build**: gcc version detection on openSUSE Tumbleweed (Henrique Aparecido Lavezzo) [nodejs/node-v0.x-archive#25671](https://github.com/nodejs/node-v0.x-archive/pull/25671)
+* [[`9c7bd6de56`](https://github.com/nodejs/node/commit/9c7bd6de56)] - **build**: run-ci makefile rule (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`ffa1e1f31d`](https://github.com/nodejs/node/commit/ffa1e1f31d)] - **build**: support flaky tests in test-ci (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`100dd19e61`](https://github.com/nodejs/node/commit/100dd19e61)] - **build**: support Jenkins via test-ci (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`ec861f6f90`](https://github.com/nodejs/node/commit/ec861f6f90)] - **build**: make release process easier for multi users (Julien Gilli) [nodejs/node-v0.x-archive#25638](https://github.com/nodejs/node-v0.x-archive/pull/25638)
+* [[`d7ae79a452`](https://github.com/nodejs/node/commit/d7ae79a452)] - **build,win**: fix node.exe resource version (João Reis) [#3053](https://github.com/nodejs/node/pull/3053)
+* [[`6ac47aa9f5`](https://github.com/nodejs/node/commit/6ac47aa9f5)] - **build,win**: try next MSVS version on failure (João Reis) [#2910](https://github.com/nodejs/node/pull/2910)
+* [[`e669b27740`](https://github.com/nodejs/node/commit/e669b27740)] - **crypto**: replace rwlocks with simple mutexes (Ben Noordhuis) [#2723](https://github.com/nodejs/node/pull/2723)
+* [[`ce0a48826e`](https://github.com/nodejs/node/commit/ce0a48826e)] - **deps**: upgrade to openssl 1.0.1q (Ben Noordhuis) [#4132](https://github.com/nodejs/node/pull/4132)
+* [[`b68781e500`](https://github.com/nodejs/node/commit/b68781e500)] - **deps**: upgrade npm to 1.4.29 (Forrest L Norvell) [#3639](https://github.com/nodejs/node/pull/3639)
+* [[`7cf0d9c1d9`](https://github.com/nodejs/node/commit/7cf0d9c1d9)] - **deps**: fix openssl for MSVS 2015 (Andy Polyakov) [nodejs/node-v0.x-archive#25857](https://github.com/nodejs/node-v0.x-archive/pull/25857)
+* [[`9ee8a14f9e`](https://github.com/nodejs/node/commit/9ee8a14f9e)] - **deps**: fix gyp to work on MacOSX without XCode (Shigeki Ohtsu) [nodejs/node-v0.x-archive#25857](https://github.com/nodejs/node-v0.x-archive/pull/25857)
+* [[`a525c7244e`](https://github.com/nodejs/node/commit/a525c7244e)] - **deps**: update gyp to 25ed9ac (João Reis) [nodejs/node-v0.x-archive#25857](https://github.com/nodejs/node-v0.x-archive/pull/25857)
+* [[`6502160294`](https://github.com/nodejs/node/commit/6502160294)] - **dns**: allow v8 to optimize lookup() (Brian White) [nodejs/node-v0.x-archive#8942](https://github.com/nodejs/node-v0.x-archive/pull/8942)
+* [[`5d829a63ab`](https://github.com/nodejs/node/commit/5d829a63ab)] - **doc**: backport README.md (Rod Vagg) [#3965](https://github.com/nodejs/node/pull/3965)
+* [[`62c8948109`](https://github.com/nodejs/node/commit/62c8948109)] - **doc**: fix Folders as Modules omission of index.json (Elan Shanker) [nodejs/node-v0.x-archive#8868](https://github.com/nodejs/node-v0.x-archive/pull/8868)
+* [[`572663f303`](https://github.com/nodejs/node/commit/572663f303)] - **https**: don't overwrite servername option (skenqbx) [nodejs/node-v0.x-archive#9368](https://github.com/nodejs/node-v0.x-archive/pull/9368)
+* [[`75c84b2439`](https://github.com/nodejs/node/commit/75c84b2439)] - **test**: add test for https agent servername option (skenqbx) [nodejs/node-v0.x-archive#9368](https://github.com/nodejs/node-v0.x-archive/pull/9368)
+* [[`841a6dd264`](https://github.com/nodejs/node/commit/841a6dd264)] - **test**: mark more tests as flaky (Alexis Campailla) [nodejs/node-v0.x-archive#25807](https://github.com/nodejs/node-v0.x-archive/pull/25807)
+* [[`a7fee30da1`](https://github.com/nodejs/node/commit/a7fee30da1)] - **test**: mark test-tls-securepair-server as flaky (Alexis Campailla) [nodejs/node-v0.x-archive#25807](https://github.com/nodejs/node-v0.x-archive/pull/25807)
+* [[`7df57703dd`](https://github.com/nodejs/node/commit/7df57703dd)] - **test**: mark test-net-error-twice flaky on SmartOS (Julien Gilli) [nodejs/node-v0.x-archive#25760](https://github.com/nodejs/node-v0.x-archive/pull/25760)
+* [[`e10892cccc`](https://github.com/nodejs/node/commit/e10892cccc)] - **test**: make test-abort-fatal-error non flaky (Julien Gilli) [nodejs/node-v0.x-archive#25755](https://github.com/nodejs/node-v0.x-archive/pull/25755)
+* [[`a2f879f197`](https://github.com/nodejs/node/commit/a2f879f197)] - **test**: mark recently failing tests as flaky (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`e7010bdf92`](https://github.com/nodejs/node/commit/e7010bdf92)] - **test**: runner should return 0 on flaky tests (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`c283c9bbb3`](https://github.com/nodejs/node/commit/c283c9bbb3)] - **test**: support writing test output to file (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`eeaed586bb`](https://github.com/nodejs/node/commit/eeaed586bb)] - **test**: runner support for flaky tests (Alexis Campailla) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`3bb8174b94`](https://github.com/nodejs/node/commit/3bb8174b94)] - **test**: refactor to use common testcfg (Timothy J Fontaine) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`df59d43586`](https://github.com/nodejs/node/commit/df59d43586)] - **tools**: pass constant to logger instead of string (Johan Bergström) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`d103d4ed9a`](https://github.com/nodejs/node/commit/d103d4ed9a)] - **tools**: fix test.py after v8 upgrade (Ben Noordhuis) [nodejs/node-v0.x-archive#25686](https://github.com/nodejs/node-v0.x-archive/pull/25686)
+* [[`8002192b4e`](https://github.com/nodejs/node/commit/8002192b4e)] - **win**: manifest node.exe for Windows 8.1 (Alexis Campailla) [#2838](https://github.com/nodejs/node/pull/2838)
+* [[`66ec1dae8f`](https://github.com/nodejs/node/commit/66ec1dae8f)] - **win**: add MSVS 2015 support (Rod Vagg) [nodejs/node-v0.x-archive#25857](https://github.com/nodejs/node-v0.x-archive/pull/25857)
+* [[`e192f61514`](https://github.com/nodejs/node/commit/e192f61514)] - **win**: fix custom actions for WiX older than 3.9 (João Reis) [nodejs/node-v0.x-archive#25569](https://github.com/nodejs/node-v0.x-archive/pull/25569)
+* [[`16bcd68dc5`](https://github.com/nodejs/node/commit/16bcd68dc5)] - **win**: fix custom actions on Visual Studio != 2013 (Julien Gilli) [nodejs/node-v0.x-archive#25569](https://github.com/nodejs/node-v0.x-archive/pull/25569)
+* [[`517986c2f4`](https://github.com/nodejs/node/commit/517986c2f4)] - **win**: backport bringing back xp/2k3 support (Bert Belder) [nodejs/node-v0.x-archive#25569](https://github.com/nodejs/node-v0.x-archive/pull/25569)
+* [[`10f251e8dd`](https://github.com/nodejs/node/commit/10f251e8dd)] - **win**: backport set env before generating projects (Alexis Campailla) [nodejs/node-v0.x-archive#25569](https://github.com/nodejs/node-v0.x-archive/pull/25569)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.10.41/node-v0.10.41-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.10.41/x64/node-v0.10.41-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.10.41/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.10.41/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.10.41/node-v0.10.41.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.10.41/node-v0.10.41-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.10.41/node-v0.10.41-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.41/node-v0.10.41-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.41/node-v0.10.41-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.10.41/node-v0.10.41-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.10.41/node-v0.10.41-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.10.41/node-v0.10.41.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.10.41/<br>
+Documentation: https://nodejs.org/docs/v0.10.41/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+9c5898b1b354b139794f10594e84e94e991971a54d179b2e9f746319ffac56aa  node.exe
+14e149298807914ed19dc9f21634213b5063a818e792ce3c49ae97cac4369c69  node.exp
+3f8993ccd878d174a835d5cae866aef0a422d8bac5a34e80ea52b9e2d59d56ce  node.lib
+ddfb1017678ef1fd3849f94782a5e030a2bce67ed7d5ad0b58b9d77cb761802a  node.pdb
+f55050a8774828846670fea91695a8da754768021cf1121cf91f788bb3e89d20  node-v0.10.41-darwin-x64.tar.gz
+d0deae5ea05b8fae90ca98851e55dbd0fe8b88dab5ed658ebdb61d3e47bc0a5e  node-v0.10.41-darwin-x86.tar.gz
+2d8f14df7ae2fd999d0b0f9c1b2129f749976325b392bec3cb62827ac639fcaf  node-v0.10.41-headers.tar.gz
+ebda18d4c6545ac42b3404d629504feea0b2b9e7c7fa68de2a5bcc9059a6dc6c  node-v0.10.41-linux-x64.tar.gz
+5ab658a14106c4625cadf6976dde223ef5b332d60b03413515764b783eb452ef  node-v0.10.41-linux-x86.tar.gz
+be6021fe1a80862429771ca9f4d088172ad00edf9977663f1c444a84c963500d  node-v0.10.41.pkg
+9621df2ffed088f87632c5f4d176e5d49438fce5aeb7b4ce8d2eff0de153a5bf  node-v0.10.41-sunos-x64.tar.gz
+a5f5ed4d8200e231323db083f3f2735cec13ac6584523b94ac953ad0e4874b66  node-v0.10.41-sunos-x86.tar.gz
+79f694e2a5c42543b75d0c69f6860499d7593136d0f6b59e7163b9e66fb2c995  node-v0.10.41.tar.gz
+fc51bf38e59d987b1b9db961bee9d88e77f8f0ccff56708ed2d9d0a72392c366  node-v0.10.41-x86.msi
+759cd124a5531b90a35e8d56f10e41ec3840c3b37e4b1c425ca67fa421931120  openssl-cli.exe
+04bbdfa2be16892d43307d5df3c0fdaa3604acaf11d0b002252362cba8b83420  openssl-cli.pdb
+4d07bd6392f3c01898c0786343330de7a6ea7a833645914d5040aeaba5179a66  x64/node.exe
+65d0ccd489710bd87d4676778c98758e0769b5716567fd05e88b616553babb1d  x64/node.exp
+6890afff5ba7b5bc04633fa8dec2bbb4d3547035660cd84882f24045ebfbeb36  x64/node.lib
+9963d814a03572c83e434dea2dceb02b7a2cf517c7efe12b4221860707b3c343  x64/node.pdb
+783533a090fe300e576cefed2a3eb20c5161f3a59b63f8e7b91262d1b94e0846  x64/node-v0.10.41-x64.msi
+16b4aa6a3e24f91934439f0145c05f324ea8a1d14df22f49bc999e6c1df85789  x64/openssl-cli.exe
+4e2282b67be0f9b6d788909c79003ab7d120eb717ca27d53bddf07aa9bdfb65d  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWYP1dAAoJEMJzeS99g1Rd6hMH/i1BBJpXYRCNv96xaEL+xBhr
+T5FHnj3X8etyuTlnEi/EmXbK1xAzH6K6mY2/X61bQpDlg7q24xT3mCI/4WvmyDAG
+9gRcmW1Mcv+OcoBXWxQoRBw9d8MukoNjokFJ+29d753UyEq4xr7HAKOpW9L/motI
+HdpUonfYqrHzSemhmkD3rL832GcyReRPF3/pkTzfh8Ss22cV255DG0VPRNgU12Fz
+J8ztBizg23iAzJOMHb5Tq8tDUgvUt6W46qRm4hqniTOaB9O7e52+k967jgvi5xmm
+TkRPiYggUprEYQh1pxHX4GEYeVBXNnACpc/keck0dVOhpGfnB4iYy4/P246Vz3w=
+=Tkdg
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.10.42.md b/locale/uk/blog/release/v0.10.42.md
new file mode 100755
index 0000000000000..d5b24777fa720
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.42.md
@@ -0,0 +1,101 @@
+---
+date: 2016-02-09T17:34:00.212Z
+version: 0.10.42
+category: release
+title: Node v0.10.42 (LTS)
+slug: node-v0-10-42
+layout: blog-post.hbs
+author: James M Snell
+---
+
+This is an important security release. For full details see https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ for details on patched vulnerabilities.
+
+### Notable changes
+
+* http: fix defects in HTTP header parsing for requests and responses that can allow request smuggling (CVE-2016-2086) or response splitting (CVE-2016-2216). HTTP header parsing now aligns more closely with the HTTP spec including restricting the acceptable characters.
+* http-parser: upgrade from 1.0 to 1.1
+* openssl: upgrade from 1.0.1q to 1.0.1r. To mitigate against the Logjam attack, TLS clients now reject Diffie-Hellman handshakes with parameters shorter than 1024-bits, up from the previous limit of 768-bits.
+* src:
+  - introduce new `--security-revert={cvenum}` command line flag for selective reversion of specific CVE fixes
+  - allow the fix for CVE-2016-2216 to be selectively reverted using `--security-revert=CVE-2016-2216`
+* build:
+  - xz compressed tar files will be made available from nodejs.org for v0.10 builds from v0.10.42 onward
+  - A headers.tar.gz file will be made available from nodejs.org for v0.10 builds from v0.10.42 onward, a future change to node-gyp will be required to make use of these
+
+### Commits
+
+* [fdc332183e] - build: enable xz compressed tarballs where possible (Rod Vagg) https://github.com/nodejs/node/pull/4894
+* [2d35b421b5] - deps: upgrade openssl sources to 1.0.1r (Shigeki Ohtsu) https://github.com/joyent/node/pull/25368
+* [b31c0f3ea4] - deps: update http-parser to version 1.1 (James M Snell)
+* [616ec1d6b0] - doc: clarify v0.10.41 openssl tls security impact (Rod Vagg) https://github.com/nodejs/node/pull/4153
+* [ccb3c2377c] - http: strictly forbid invalid characters from headers (James M Snell)
+* [f0af0d1f96] - src: avoid compiler warning in node_revert.cc (James M Snell)
+* [df80e856c6] - src: add --security-revert command line flag (James M Snell)
+* [ff58dcdd74] - tools: backport tools/install.py for headers (Richard Lau) https://github.com/nodejs/node/pull/4149
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.10.42/node-v0.10.42-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.10.42/x64/node-v0.10.42-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.10.42/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.10.42/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.10.42/node-v0.10.42.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.10.42/node-v0.10.42-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.10.42/node-v0.10.42-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.42/node-v0.10.42-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.42/node-v0.10.42-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.10.42/node-v0.10.42-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.10.42/node-v0.10.42-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.10.42/node-v0.10.42.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.10.42/<br>
+Documentation: https://nodejs.org/docs/v0.10.42/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+------BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+f0280e1f5c2568e5fda9f911ab8341b47914a21d30f854136299f510dc843816  node.exe
+aed0f1ba2e58ceec1c06050f5f0d3eaad6630da2457d2bf1bb839e68f33fd7b0  node.exp
+647609c5f6d885752d4374cf5fd67de72c896b43f888c4c37db9e6bd90633c50  node.lib
+5b4b8f3f88ef533ebb7e9baecdd8e9ae8e8f53559320e77ea176a607be4d6858  node.pdb
+356b4891c7060b6a68cf126837689807c30d43b709120b7fe6f167404612eb5a  node-v0.10.42-darwin-x64.tar.gz
+cb794c57c5af5c06ef4b24bbbc423dd155867e2e01ee266f2da8e8c6aa5a33d3  node-v0.10.42-darwin-x64.tar.xz
+ff61d24f80db9c5e6b007103751cdb8ac6cb3ff4180972ce1532bcb934847e0c  node-v0.10.42-darwin-x86.tar.gz
+7c67fc5992f5b038bebfd7274b7d4197011470562737d46b9a006876692513d1  node-v0.10.42-darwin-x86.tar.xz
+64d3e067cda5a675b44cee9875d1d72f8a29ed8bc19e476a16467336b832bfb3  node-v0.10.42-headers.tar.gz
+5add37eb5d1f8f9ac061524dcbe8a87a17b9af19f9521f622fdc491cbf23dc32  node-v0.10.42-headers.tar.xz
+a9b80fb22efc483b6aef282ebb0254b5d9b092ed8091521977af593069a81d53  node-v0.10.42-linux-x64.tar.gz
+fd049d9f6a53497092568c81c77a85c3035911ff687eeece95e98b59fb543ec6  node-v0.10.42-linux-x64.tar.xz
+5e528360a59314e2357184a8582d4d9dd1aa1c77687145bcf11b23e28f4ddd00  node-v0.10.42-linux-x86.tar.gz
+f19ee1f785ea79d26187c8956e01a9362bbfbcb117d98d6bd6c6927a6d33906a  node-v0.10.42-linux-x86.tar.xz
+600b983bf2802d29d175da885fb0b5905195b322dc0c2d45c510ef5de356fb66  node-v0.10.42.pkg
+af15246d6889db4449dc46d5c4a549bb56b19481cbb801d30a09153ba71b88e1  node-v0.10.42-sunos-x64.tar.gz
+5c15420d3fa7253f966cd29ea9d863d383ce05bca040c517c204a4abbc31d353  node-v0.10.42-sunos-x64.tar.xz
+3333f1fd394bdde5aafa424d945b002b0d0876e17396f864af9c230c81aac08b  node-v0.10.42-sunos-x86.tar.gz
+ae9ceedb9f80eda4d14fb29b3b862b29acf1a45666b34d53867aad80c05ef1b6  node-v0.10.42-sunos-x86.tar.xz
+ebc1d53698f80c5a7b0b948e1108d7858f93d2d9ebf4541c12688d85704de105  node-v0.10.42.tar.gz
+9b4cc1b5bc397d80dfe217625b04bb6212a3b5a8b1e0eb36000a30d7ae567b8a  node-v0.10.42.tar.xz
+8fc72fa366d886cf41a80bcc0b78b37e3eb7a0eb78a9b80e8d328accec430150  node-v0.10.42-x86.msi
+aefe011af949fa65cc89df70815f61abe3839841a069f85d4db6e9f55281bc6d  openssl-cli.exe
+5d6869db2027e9a7a5a912d597a5772d2630515315119affb96d4ff91cacd9ed  openssl-cli.pdb
+94d2835c74d6dd8c4e457a0f4c48be9fec48c15d185b6e2874794d1e9a19561f  x64/node.exe
+d44a2acd401c0e2c388cf58607f90b275728b4e51650bd4516dce13de436c5e0  x64/node.exp
+e1526036dc9acc16072f2da806a240b8b93fbe1e67368e10b0cfb96703f579d3  x64/node.lib
+8ea78b09fa6014542b4eba8b8d03243effa2099425d41d66c7368b2a008abe06  x64/node.pdb
+93609d2b7c127121150a3d65f123da0038d80ab870bf9844c05130bd9d2e7c71  x64/node-v0.10.42-x64.msi
+4c4b7452a192e5b1b4596fa3375baa100a88bba7f81fb95c3c7f8641b818dbb3  x64/openssl-cli.exe
+14fbf4dad971c6bfe64c46bd667613f8c0756c1d425bbef740b4fc213e30ea5a  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWuhvlAAoJEHNBsVwHCHesU7sH/jkm32kqNQA+qV4V4nO4W2XQ
+m+RHBfLKoXzw26amM17I9UNtbjzEcwfmVj060qmdjZgofer/aFx+cP43SpiVPVmG
+BD4jfp46wqsd4v4R+ZBwQV/GppTU/Xsfux4k5h7ied2oIoSJsUQhhBNdUk4GZj2/
+iDPhIe/3ugBFJVnT+YGGmM/y7V9L8hz91K+jxmkGx0p2EQZchkYSXYWONXv9pVbz
+VNhLmW7H7/afuIqBlsA327Q4ZdGAgqVqLqiPGkwzRQOob2+Wlb7nHsger7VnMh9S
+XJf42E17IDB3zVD2HHPzaSti3BC+Jm18i0PwBqE3YksTnPPxry70GGmSm7OK6iY=
+=NYfo
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.10.43.md b/locale/uk/blog/release/v0.10.43.md
new file mode 100755
index 0000000000000..5eef47ca10b2c
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.43.md
@@ -0,0 +1,99 @@
+---
+date: 2016-03-04T01:47:40.622Z
+version: 0.10.43
+category: release
+title: Node v0.10.43 (Maintenance)
+slug: node-v0-10-43
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+This release contains security updates. OpenSSL 1.0.1s fixes some low-severity defects that impact Node.js. See our [impact assessment](http://nodejs.org/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016/#_-update-29-jan-2016-_-openssl-impact-assessment) for full details.
+
+### Notable changes:
+
+* **http_parser**: Update to http-parser 1.2 to fix an unintentionally strict limitation of allowable header characters. (James M Snell) [nodejs/node#5242](https://github.com/nodejs/node/pull/5242)
+* **domains**:
+  - Prevent an exit due to an exception being thrown rather than emitting an `'uncaughtException'` event on the `process` object when no error handler is set on the domain within which an error is thrown and an `'uncaughtException'` event listener is set on `process`. (Julien Gilli) [nodejs/node#3887](https://github.com/nodejs/node/pull/3887)
+  - Fix an issue where the process would not abort in the proper function call if an error is thrown within a domain with no error handler and `--abort-on-uncaught-exception` is used. (Julien Gilli) [nodejs/node#3887](https://github.com/nodejs/node/pull/3887)
+* **openssl**: Upgrade from 1.0.1r to 1.0.1s (Ben Noordhuis) [nodejs/node#5508](https://github.com/nodejs/node/pull/5508)
+  - Fix a double-free defect in parsing malformed DSA keys that may potentially be used for DoS or memory corruption attacks. It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0705
+  - Fix a defect that can cause memory corruption in certain very rare cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()` functions. It is believed that Node.js is not invoking the code paths that use these functions so practical attacks via Node.js using this defect are _unlikely_ to be possible. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0797
+  - Fix a defect that makes the CacheBleed Attack (https://ssrg.nicta.com.au/projects/TS/cachebleed/) possible. This defect enables attackers to execute side-channel attacks leading to the potential recovery of entire RSA private keys. It only affects the Intel Sandy Bridge (and possibly older) microarchitecture when using hyper-threading. Newer microarchitectures, including Haswell, are unaffected. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0702
+  - Remove SSLv2 support, the `--enable-ssl2` command line argument will now produce an error. The DROWN Attack (https://drownattack.com/) creates a vulnerability where SSLv2 is enabled by a server, even if a client connection is not using SSLv2. The SSLv2 protocol is widely considered unacceptably broken and should not be supported. More information is available at https://www.openssl.org/news/vulnerabilities.html#2016-0800
+
+Commits:
+
+* [[`3123e9a6df`](https://github.com/nodejs/node/commit/3123e9a6df)] - 2016-03-04 Version 0.10.43 (Maintenance) Release (Rod Vagg) [#5404](https://github.com/nodejs/node/pull/5404)
+* [[`164157abbb`](https://github.com/nodejs/node/commit/164157abbb)] - **build**: update Node.js logo on OSX installer (Rod Vagg) [#5401](https://github.com/nodejs/node/pull/5401)
+* [[`f8cb0dcf67`](https://github.com/nodejs/node/commit/f8cb0dcf67)] - **crypto,tls**: remove SSLv2 support (Ben Noordhuis) [#5529](https://github.com/nodejs/node/pull/5529)
+* [[`42ded2a590`](https://github.com/nodejs/node/commit/42ded2a590)] - **deps**: upgrade openssl to 1.0.1s (Ben Noordhuis) [#5508](https://github.com/nodejs/node/pull/5508)
+* [[`1e45a6111c`](https://github.com/nodejs/node/commit/1e45a6111c)] - **deps**: update http-parser to version 1.2 (James M Snell) [#5242](https://github.com/nodejs/node/pull/5242)
+* [[`6db377b2f4`](https://github.com/nodejs/node/commit/6db377b2f4)] - **doc**: remove SSLv2 descriptions (Shigeki Ohtsu) [#5541](https://github.com/nodejs/node/pull/5541)
+* [[`563c359f5c`](https://github.com/nodejs/node/commit/563c359f5c)] - **domains**: fix handling of uncaught exceptions (Julien Gilli) [#3887](https://github.com/nodejs/node/pull/3887)
+* [[`e483f3fd26`](https://github.com/nodejs/node/commit/e483f3fd26)] - **test**: fix hanging http obstext test (Ben Noordhuis) [#5511](https://github.com/nodejs/node/pull/5511)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.10.43/node-v0.10.43-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.10.43/x64/node-v0.10.43-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.10.43/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.10.43/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.10.43/node-v0.10.43.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.10.43/node-v0.10.43-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.10.43/node-v0.10.43-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.43/node-v0.10.43-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.43/node-v0.10.43-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.10.43/node-v0.10.43-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.10.43/node-v0.10.43-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.10.43/node-v0.10.43.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.10.43/<br>
+Documentation: https://nodejs.org/docs/v0.10.43/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+d08256e94e7f0006495f48f04bfde0f08fe57bb3d6f881ffd5d3e7382a437379  node.exe
+89582528585db5cd105165d2bd839fa2475a651ef9deafc540cfdea4044e83d1  node.exp
+3485a706ccc62694872f7cb78101cc62ce29ab1128281b9942da6b166edd51a5  node.lib
+7aefcedfb06e629decc774cf7a9b1c4684d59f58fbab8f95a746b674add99901  node.pdb
+c7fb30129206fa2d74d72d3c1a86fa5cb768a1165c41be9f7c724e35c3b53ca9  node-v0.10.43-darwin-x64.tar.gz
+00457f6102e70c696baf375a48a4299d5d065a2e2f78c08545a1983ba674c398  node-v0.10.43-darwin-x64.tar.xz
+a62a819832db4d6a1e9c10d286faa74c2917288a011dc7aca0476725b85cc0ae  node-v0.10.43-darwin-x86.tar.gz
+fd1ccdce22c88ac673eec684a9aab1ffafb75873b52591913f9dc8262488a329  node-v0.10.43-darwin-x86.tar.xz
+5c6f56f2230e9ef64a443d45dd66526e2614fce4d11a711a5bc89ecc31be05f2  node-v0.10.43-headers.tar.gz
+4fbe1416a85e5bf0685eb8c4dadd3c8fa222d987eaf312861b74fa35a039ed6a  node-v0.10.43-headers.tar.xz
+8a439e17af1971432798ec79a70abf8fa21e03e2aa994bb7150bc088bfa482f2  node-v0.10.43-linux-x64.tar.gz
+1f704fd493a4b8747227f5e1966d4a56192a07036357e1165bd1140760ca919e  node-v0.10.43-linux-x64.tar.xz
+142bdf1cb8793bd7c7da7974c73bd2d466933f8d5b496d9a28d3b1e343b62bd0  node-v0.10.43-linux-x86.tar.gz
+75b33151e4ad29aff26d210d772d683d4ef69a83a1a1b38cdbe8856a0a2ebfc6  node-v0.10.43-linux-x86.tar.xz
+cd16c330369500c9f3225f20bf8a5d2a644d059c407804067bd52b6d91a6cc49  node-v0.10.43.pkg
+f6cf66e77e1def7fa854ddb83a176d89f9a5b349fbb1e0bcdb742778c31e1510  node-v0.10.43-sunos-x64.tar.gz
+5feaa499d5a5ff6ed5922d9ce02809151115a2ec3c06e23d1544e8c62badbd8b  node-v0.10.43-sunos-x64.tar.xz
+b3badbc35d085723a2ad30847c5109398363b13649e199db6d22fe5f56e74c52  node-v0.10.43-sunos-x86.tar.gz
+94bdc514b30d32cfb362186bc89a9b818c616f540a9b28556e15f0819d3257eb  node-v0.10.43-sunos-x86.tar.xz
+c672452a61dd37cf2779bc158b65a5a22af343da19fec1cddf9bced382a2595a  node-v0.10.43.tar.gz
+6c5185cbfad3538484c9d97eec0110b5cd5826126f15b776015dfee1f51cd32a  node-v0.10.43.tar.xz
+d961a479d01f0fb145b77a6abf62f66e33b75383dc99ac7bed94c8bd75d854fd  node-v0.10.43-x86.msi
+77755d041c76dd2c8bc277916dea5ee269efaa784671aa068c15164a30d9f351  openssl-cli.exe
+04235831f2699980489a760063754adc54acb0eace4cafc2e552a6f2efe62c3e  openssl-cli.pdb
+4648414b546844ddf329d497ca10e7bce3abd63bf6b4995c1318cb2a4c33229d  x64/node.exe
+73d9783523050e8e450220568743da6300cfa0f5f45fb04501b77dfa1c1f8360  x64/node.exp
+5ef4d9d80f2e79d94ad69386e72d027a75c727f8736ac6221cb5702b09e4ae6b  x64/node.lib
+6acf585f3d1cb1116649c3bc18e2764b3d05cb8e21f349cd2704e5d21536e46c  x64/node.pdb
+e9216efaf78d63ed9eaf6eb31ae166845847886717dc5d3ef98e647032290b8f  x64/node-v0.10.43-x64.msi
+d042372ccedff1b5a20847f535d0835b520c08dd3cbc9505752cc3b7122b168d  x64/openssl-cli.exe
+fd5aeebfb38888f3e0d1d85fd2cc2bddca47be1c5f721d33edc876e9315f6ffc  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJW2OiLAAoJEMJzeS99g1RdjM4H/1VPMHeLCmkUupVP3s0FKtEs
+bmoIPabUlRXW0JZRL9q1LRk7AhAc9SQjVwpYYCnjYEQhDzsYC4RKs8R19YEcIC/E
+N8r7r6hZ7k9Tqh6gA67Mh9Hc6CswfjYp46yAMtC7C6aYHYPDPJPU4/KML+Rsg4WI
+sBfsAWcDxWVtbh+Ef00PAadWeHEXzFd4hXdk2DNVonvTQZFW9JrN6/qEp3u75rz1
+Z6ilBto4Wr80IFrCKfvUCO7ChKx4SXHxkMtJYzDUo0F0mVTEL6f9n9PdiDd8Pwrf
+3NTlOdnFUoLTVKQFKRlkQyjx5Ud+0ve0+5capSZ6jMDSXHS/enfY8BUvNZUqWAU=
+=Dong
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.10.44.md b/locale/uk/blog/release/v0.10.44.md
new file mode 100755
index 0000000000000..6da8fab78b864
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.44.md
@@ -0,0 +1,90 @@
+---
+date: 2016-04-01T04:35:44.441Z
+version: 0.10.44
+category: release
+title: Node v0.10.44 (Maintenance)
+slug: node-v0-10-44
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+**This is a security release**, upgrading the bundled version of npm due to a credentials leak vulnerability. Further information can be found in our post: http://nodejs.org/en/blog/vulnerability/npm-tokens-leak-march-2016/
+
+Please note that **the version of npm included in this release does not have the correct version string**. As such executing `npm -v` will report `2.15.0` rather than `2.15.1`, which is incorrect. The source code included in this release is in fact the source for `2.15.1`, including the security fix.
+
+### Notable changes:
+
+* **npm**: Upgrade to v2.15.1. Fixes a security flaw in the use of authentication tokens in HTTP requests that would allow an attacker to set up a server that could collect tokens from users of the command-line interface. Authentication tokens have previously been sent with every request made by the CLI for logged-in users, regardless of the destination of the request. This update fixes this by only including those tokens for requests made against the registry or registries used for the current install. IMPORTANT: This is a major upgrade to npm v2 LTS from the previously deprecated npm v1. (Forrest L Norvell) https://github.com/nodejs/node/pull/5967
+* **openssl**: OpenSSL v1.0.1s disables the EXPORT and LOW ciphers as they are obsolete and not considered safe. This release of Node.js turns on `OPENSSL_NO_WEAK_SSL_CIPHERS` to fully disable the 27 ciphers included in these lists which can be used in SSLv3 and higher. Full details can be found in our LTS discussion on the matter (https://github.com/nodejs/LTS/issues/85). (Shigeki Ohtsu) https://github.com/nodejs/node/pull/5712
+
+Commits:
+
+* [feceb77d7e] - deps: upgrade npm in LTS to 2.15.1 (Forrest L Norvell) https://github.com/nodejs/node/pull/5968
+* [0847954331] - deps: Disable EXPORT and LOW ciphers in openssl (Shigeki Ohtsu) https://github.com/nodejs/node/pull/5712
+* [6bb86e727a] - test: change tls tests not to use LOW cipher (Shigeki Ohtsu) https://github.com/nodejs/node/pull/5712
+* [905bec29ad] - win,build: support Visual C++ Build Tools 2015 (João Reis) https://github.com/nodejs/node/pull/5627
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.10.44/node-v0.10.44-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.10.44/x64/node-v0.10.44-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.10.44/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.10.44/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.10.44/node-v0.10.44.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.10.44/node-v0.10.44-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.10.44/node-v0.10.44-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.44/node-v0.10.44-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.44/node-v0.10.44-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.10.44/node-v0.10.44-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.10.44/node-v0.10.44-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.10.44/node-v0.10.44.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.10.44/<br>
+Documentation: https://nodejs.org/docs/v0.10.44/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+ad1ab74e1315828a7fd1452e565791a0544ca6c86c76ddd9275287c84ccaca74  node.exe
+e9142dda53c17fb84a30438a4f4b69f8f474750d1cf32b4057edaea2309b3aec  node.exp
+5b2b75d133380996a6c0433944c61d47777389bbcba9ffdd20ef0c37a28f1565  node.lib
+cf46dd07a29abfadf9096d5b29878618433cc6ef5307f523ae283e7b1150e660  node.pdb
+cc9916991a16395c4a561db6d091a9a1e9af13e66dddbd03d3c687d0ab3e52a9  node-v0.10.44-darwin-x64.tar.gz
+d9aa4cdae49798b45818ddcd38cc8781a591e2b1c6d6c9c9599205353771d602  node-v0.10.44-darwin-x64.tar.xz
+7c582b190050d268b4fa4d1a4e4b3456be1a9c224407a4ef61258af6e95f01d8  node-v0.10.44-darwin-x86.tar.gz
+e1920de5cf492079a44113c5f5bf4954b73ad8ae26a79c196bb915ce31766a85  node-v0.10.44-darwin-x86.tar.xz
+1f61b9a97e4a4100ad601661d3e53556fc8287c36cc56a7c9bf1617b30c5eed4  node-v0.10.44-headers.tar.gz
+28192921448ec80632ec5a34aca438136b7384e35878fbf4c8486825590e67ef  node-v0.10.44-headers.tar.xz
+b5f4acc54e5527d793463e05b5435f11dd1f0997168aa71d53a1ff1a06c7b144  node-v0.10.44-linux-x64.tar.gz
+1c72d19eb4c505a3e6c76038b9c25fc1fee09829215f67e040e363996b160c14  node-v0.10.44-linux-x64.tar.xz
+8eb2b47928f56b0a7bbbde72074af84bc8864544b75f991facc3fbf4d7ed0c99  node-v0.10.44-linux-x86.tar.gz
+45c300fafc8a71c240c94ca8b43701edf5fbdaa1d80ac449b96d46922b61ce0f  node-v0.10.44-linux-x86.tar.xz
+53a918e31ea61cf5106b3cfcedbe5b331cbca0f6508abbf02a77a9bbdc78aeb3  node-v0.10.44.pkg
+ee2867b193b53ffab308bea6f0e4c197222903ae308b1748eceaa786402d6c15  node-v0.10.44-sunos-x64.tar.gz
+3ce6599f526e1cca2fe2d736e946c34c1f830926987cabd8c22066dc5511ba99  node-v0.10.44-sunos-x64.tar.xz
+0b385a3aa1f9122bca205515917a2406ab24782ecbbb886ceb5dcba93f3a9758  node-v0.10.44-sunos-x86.tar.gz
+c2cd71e47ac8e2565e4c176e78f22c6ff45752dd0ddc32fa4251f4d6fa17d18a  node-v0.10.44-sunos-x86.tar.xz
+4155639d71e690cafd885f58a8be3bf97a93c28875212aac991923d3ee589be8  node-v0.10.44.tar.gz
+25b2cd910822723e972a3990d5687b7ff48581ad2f77aa1942d99a1b024f434a  node-v0.10.44.tar.xz
+7052fecac6a3c4969d62dc655f1ae4c98bc00323e16e9a3ec4dfabd85da2e2fa  node-v0.10.44-x86.msi
+977af6c6b87b2cedbbe43292eb2a9533c9bb385af0d7f4cb503d2a73266437c8  openssl-cli.exe
+83e2e5209f110f77cfb1b5198312dce7714084979b31285b7718b08fd8c4e9c5  openssl-cli.pdb
+e1044fc4768ea380d2a4dfd10f35ac90194333a753b7ca740a81840aa5ecfa98  x64/node.exe
+a386a731e0880be60531af7ad291f9ab5cb1829d9a73247e5ee7b4fd5fc734b5  x64/node.exp
+d11f6d920a9a1484248415fba80c74b2836ef66325935b0d3d4b4248a4be268a  x64/node.lib
+47ee02bb149e6622dabcb2c26dcf0c32b9b8419118d6f3ea2d4d3eeca4d6229f  x64/node.pdb
+b98c678fdd2a18b380f277d635f3720df4b4c967b6fa204979f1c62f418b9940  x64/node-v0.10.44-x64.msi
+3fd5077d54b1f1ada05e3022c5730344b22efbd1ecd63f6db63506a48c0ebcc5  x64/openssl-cli.exe
+6a08f8e77a6754938cbe5cbad656b5a39aae62e8ca54af144340bf6b372212a9  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJW/fmNAAoJEMJzeS99g1Rd2OMH/1ao48kMN6+E+mMR+aG6hxir
+AKUSHVYHqVt2WG5/9XJHCRNTnE5D+xCX9heF+PgFtZGpzoJRfwho7TTn+XlFD/4i
+4UAPPfJW4mOo4rdywQ6Ry8hqJnBS3Ewyj6ABvdcBPyrJCQf7ZOhi6QEJQwx70yMA
+TKWUaEQGhMmQB+zKhmfWuVjFIv+ZW7z/fOW6v/51QGF0zuOrwcboABXUFiIxsyNq
+XgG1TkZhj1jZeaR7YAyk5NxMLhblz9FC5JaaqutoA1VFcPopDMOFbV3rwZKWe1yo
+wqJYf6JKhenBRM+P9rRUl7wlVBSjHBW9SP+BOzL7ETQG1ebhYsCLytz+9gNtX0E=
+=gzZT
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.10.45.md b/locale/uk/blog/release/v0.10.45.md
new file mode 100755
index 0000000000000..29a8d68ed6767
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.45.md
@@ -0,0 +1,92 @@
+---
+date: 2016-05-06T13:22:08.238Z
+version: 0.10.45
+category: release
+title: Node v0.10.45 (Maintenance)
+slug: node-v0-10-45
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes:
+
+* **npm**: Correct erroneous version number in v2.15.1 code (Forrest L Norvell) https://github.com/nodejs/node/pull/5987
+* **openssl**: Upgrade to v1.0.1t, addressing security vulnerabilities (Shigeki Ohtsu) https://github.com/nodejs/node/pull/6553
+  - Fixes CVE-2016-2107 "Padding oracle in AES-NI CBC MAC check"
+  - See https://nodejs.org/en/blog/vulnerability/openssl-may-2016/ for full details
+
+Commits:
+
+* [[`3cff81c7d6`](https://github.com/nodejs/node/commit/3cff81c7d6)] - **deps**: completely upgrade npm in LTS to 2.15.1 (Forrest L Norvell) [#5987](https://github.com/nodejs/node/pull/5987)
+* [[`7c22f19009`](https://github.com/nodejs/node/commit/7c22f19009)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [joyent/node#25368](https://github.com/joyent/node/pull/25368)
+* [[`5d78366937`](https://github.com/nodejs/node/commit/5d78366937)] - **deps**: update openssl asm files (Shigeki Ohtsu) [#6553](https://github.com/nodejs/node/pull/6553)
+* [[`2bc2427cb7`](https://github.com/nodejs/node/commit/2bc2427cb7)] - **deps**: fix openssl assembly error on ia32 win32 (Fedor Indutny) [joyent/node#25654](https://github.com/joyent/node/pull/25654)
+* [[`8df4b0914c`](https://github.com/nodejs/node/commit/8df4b0914c)] - **deps**: separate sha256/sha512-x86_64.pl for openssl (Shigeki Ohtsu) [joyent/node#25654](https://github.com/joyent/node/pull/25654)
+* [[`11eefefb17`](https://github.com/nodejs/node/commit/11eefefb17)] - **deps**: copy all openssl header files to include dir (Shigeki Ohtsu) [#6553](https://github.com/nodejs/node/pull/6553)
+* [[`61ccc27b54`](https://github.com/nodejs/node/commit/61ccc27b54)] - **deps**: upgrade openssl sources to 1.0.1t (Shigeki Ohtsu) [#6553](https://github.com/nodejs/node/pull/6553)
+* [[`aa02438274`](https://github.com/nodejs/node/commit/aa02438274)] - **openssl**: fix keypress requirement in apps on win32 (Shigeki Ohtsu) [joyent/node#25654](https://github.com/joyent/node/
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.10.45/node-v0.10.45-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.10.45/x64/node-v0.10.45-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.10.45/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.10.45/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.10.45/node-v0.10.45.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.10.45/node-v0.10.45-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.10.45/node-v0.10.45-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.45/node-v0.10.45-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.45/node-v0.10.45-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.10.45/node-v0.10.45-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.10.45/node-v0.10.45-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.10.45/node-v0.10.45.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.10.45/<br>
+Documentation: https://nodejs.org/docs/v0.10.45/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+5cfddcfcdb0e5a09c54ba1c52a935c43d182b54e013fc0d621d44a710222dc00  node.exe
+743c46a6145b25b088ff5a18e3403fa02c4ce9c033b284c762ccd1329de85c37  node.exp
+3c7b5f96e272d71b1eaca89a111d19f0e682193306c71687f63a695f40abff07  node.lib
+fc15a8a784db0f23617544f663130af8e9d1155eb2ad706fe8387de1d7b62719  node.pdb
+d1ab69f49365a0dc6b10a363965452f37f3589adee19974940cbd2b991965e70  node-v0.10.45-darwin-x64.tar.gz
+f8acb114faea28a6d58b35025e3fd37b5bb9e8fa9eac4a3796d225c16ba541de  node-v0.10.45-darwin-x64.tar.xz
+3db0e42736fbdedc8a985269595251d9c4e4860594ce1eee4a692f8621ee5918  node-v0.10.45-darwin-x86.tar.gz
+9544df4ab211e81601a02b681bf8fdec834efde4174ecf0a3f69fec9eab012eb  node-v0.10.45-darwin-x86.tar.xz
+94028ba548c1faabb6cb92143392784d3ad07829c16852f5404933eed7d73da7  node-v0.10.45-headers.tar.gz
+31d4d84a543bd60ca6c738e1ef243b2b04f87e41566349b8242933812107bcca  node-v0.10.45-headers.tar.xz
+54d095d12b6227460f08ec81e50f9db930ec51fa05af1b7722fa85bd2cabb5d7  node-v0.10.45-linux-x64.tar.gz
+2fd840bf79480863904860c63f615615077dbc88bd44669eb93c9bf216b4eaf0  node-v0.10.45-linux-x64.tar.xz
+0d21b8e9d4213021cd954908098d07407052da1b7a97d6c585f89752c49505b4  node-v0.10.45-linux-x86.tar.gz
+2e63e46a818777c3ba57a10406e6e1ab6ceee3b4b861eb195574659e5302ddae  node-v0.10.45-linux-x86.tar.xz
+39a4cea90fcd2564db4969a0dd6fe0d57c5593d1758796b8d41dfdda6597baca  node-v0.10.45.pkg
+019a1c40daff7b05efb2bd27c586d9ba9c5fe5048550b74e67e171d1495d4e30  node-v0.10.45-sunos-x64.tar.gz
+69197c4adf23ff4a3c6c8fa5c35b9ab4d9906015624ef7a8a37d6573535d6116  node-v0.10.45-sunos-x64.tar.xz
+39a0790a7e533dd77f473c009c11458a5205cfc438777139a5e9658be63dfee2  node-v0.10.45-sunos-x86.tar.gz
+b764e0ad9a80a4a02abcfd33565aaf49d0345c43d8ce7e00b35e8a82cfa1102c  node-v0.10.45-sunos-x86.tar.xz
+d184bb74758d4ac69826823934cda1d46e81402fc16ebdb2ecacdc1a8fe0b568  node-v0.10.45.tar.gz
+a71070ea7aece9c94450b45102f2d1be42f0add168dd9c9701e9032d363bd4fa  node-v0.10.45.tar.xz
+4c3e6c53fb65d789c522e0c4fe03341faae66707b436c389c5d5fd9298baa369  node-v0.10.45-x86.msi
+c17e3353d44951611f8929afcedcd3fc9237fe7672037efbbbaab7b1a2d2f007  openssl-cli.exe
+1897ea9e230f334a198f71526632a9c1ee16647fa94e6868cdd15ad9e6aa254f  openssl-cli.pdb
+949c8455152d1f217708cfcbbfc1be0c54f83b4e71d5cfa142f32d758587bbf6  x64/node.exe
+e62c0a6e0d2dd3cfbe5e6d99c71109b79ba72f328079a7d89c6994d71348d029  x64/node.exp
+ec4811d93e8508826d98de116bdf0dc858dda3c179c9333d6b5566e1e606c9e4  x64/node.lib
+303a39cdc16070aca53a6ab5e8064b6a57f2ac6813dfcd58d3770129d0900515  x64/node.pdb
+2f1e8d851bcaf5f1bc3e0498b241d0db53281223333b9a891b64818ab51a2044  x64/node-v0.10.45-x64.msi
+264166624c9bcc38fbed31da56ed86e8ba16238b81700f86f6f35d89cb039f21  x64/openssl-cli.exe
+0628dee6ddc474eca219a5d5069de1a6f2f3abcb3cd0eee06597e183672e6b5c  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJXLJomAAoJEMJzeS99g1Rdty4IANVJ53QRd5tUepWjxjIwZ6e7
+2r2oYSO6uihZkyddV+447KDzxYsGkdg0z4DS3BD7ym78hl4EEMlE/x8wPWBrZKAr
+yACZu2U/3ivXYyEOvdV0nlLeUNGMeugTtVxhxSMbf7fK22zeLvLCC9Q4735zhG37
+kAF7mw6Sszr+zCMV5eqh5MfYIwaCduck4TfG5ibc8fAQ4A4nUTF6jC0JRbcPXKku
+7oT7ol7u8w97Im3ZynvwZZ2yQPAqSxssKjWuLnSmt+Wng7bUregjK04QNCaa8HEV
+uPY0qIVSAS2rr1R12dOgqKhgO90gKoUa1qtWGivlvO2HH3JILWMjopb+mu0ZkIc=
+=HZGA
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.10.46.md b/locale/uk/blog/release/v0.10.46.md
new file mode 100755
index 0000000000000..c9d018560716c
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.46.md
@@ -0,0 +1,87 @@
+---
+date: 2016-06-23T23:24:09.245Z
+version: 0.10.46
+category: release
+title: Node v0.10.46 (Maintenance)
+slug: node-v0-10-46
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes:
+
+This is a security release. All Node.js users should consult the security release summary at https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/ for details on patched vulnerabilities.
+
+* **libuv**: (CVE-2014-9748) Fixes a bug in the read/write locks implementation for Windows XP and Windows 2003 that can lead to undefined and potentially unsafe behaviour. More information can be found at https://github.com/libuv/libuv/issues/515 or at <https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/>.
+* **V8**: (CVE-2016-1669) Fixes a potential Buffer overflow vulnerability discovered in V8, more details can be found in the CVE at https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1669 or at <https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/>.
+
+### Commits:
+
+* [3374f57973] - deps: update libuv to 0.10.37 (Saúl Ibarra Corretgé) https://github.com/nodejs/node/pull/7293
+* [fcb9145e29] - deps: backport 3a9bfec from v8 upstream (Myles Borins) https://github.com/nodejs/node-private/pull/43
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.10.46/node-v0.10.46-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.10.46/x64/node-v0.10.46-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.10.46/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.10.46/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.10.46/node-v0.10.46.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.10.46/node-v0.10.46-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.10.46/node-v0.10.46-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.46/node-v0.10.46-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.46/node-v0.10.46-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.10.46/node-v0.10.46-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.10.46/node-v0.10.46-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.10.46/node-v0.10.46.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.10.46/<br>
+Documentation: https://nodejs.org/docs/v0.10.46/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+6223e65d3c97abd3c4584e37e6e91deb06402b4ed8298ca728656fbf8e9c2d29  node.exe
+49017608135cf3fcaec7d3d0d0162144fb536f46fe4b4fcde753f6f6b685380e  node.exp
+c9012f2ad8bcbe57dcf0cffc279983166cd5b4ff68e04e6dd275656ea5f4e423  node.lib
+12dbd22685728dc0615a43f034980f09235af73f3990ff4eea341caa12a4e792  node.pdb
+ab9eafa76c4c9a2e0d43e6727d82b331157dc7f43fde9a3f2a4881102df9ff3a  node-v0.10.46-darwin-x64.tar.gz
+9789eabb0791595c5ef4e53029366c48dffd9c787e057ce04c6b2ff86ed635c5  node-v0.10.46-darwin-x64.tar.xz
+32c03a60eac3f1650d4a9219fc8510119bff19262255b868ee23850ef56cd0c9  node-v0.10.46-darwin-x86.tar.gz
+7180853680a4c98eedfd8621f46636575cc5079290762c1c65365d296e473eb7  node-v0.10.46-darwin-x86.tar.xz
+3eb90851301b108912cb00ff3e4f6d38fa4cb4b4c47abe0e9df93d26d1c0ea17  node-v0.10.46-headers.tar.gz
+1efaee6f824b1169ef95d3331a34de87aecf91dee0b7dd88e9928206015d75f3  node-v0.10.46-headers.tar.xz
+58116256f3060703e2e71f2cb5dc265a1d9fab7854a4eee15e78a95a0a87c750  node-v0.10.46-linux-x64.tar.gz
+4695d96a5a90cb7f0e647e717d2a80ef0645b0bca17221d83186a29653acc868  node-v0.10.46-linux-x64.tar.xz
+a0d9ffa349bd8ce0b5ab783f5a3c14787c22037900761ff296fd30c7a8645d21  node-v0.10.46-linux-x86.tar.gz
+fd2bf8af94cfe6373a034faed3ea9d9543a45395efb23de7042f7eaead10c064  node-v0.10.46-linux-x86.tar.xz
+726a8c2c10048c661d0adf716143e971252345c9f9f4a4cb3812ac2360915890  node-v0.10.46.pkg
+cb76c6e27ff0a078fa50f5dcacace83b1dd48201210554deaca2556dcf3b31bc  node-v0.10.46-sunos-x64.tar.gz
+3177f38d34a9297aa5978e3c4156083ab6d00bc03736f2e64da4e875bad9818f  node-v0.10.46-sunos-x64.tar.xz
+8bce341355320ac2ea9835db561489e35ae9a7d6b9f20c6504ba654a36232886  node-v0.10.46-sunos-x86.tar.gz
+0ee4784f835c1b7f2f77246a4f96c21f07ac38682f07991fd180fc85f0ef6f60  node-v0.10.46-sunos-x86.tar.xz
+1164f2a4b663c9c0244033bfa649304a4a4e5a5ed6fab509d63084609d53198f  node-v0.10.46.tar.gz
+9b0e6079fc3282491028d29ae019fc7ba8de187dc3acda22a5cfd7d145cbffd9  node-v0.10.46.tar.xz
+1792740f39fadbfecd589f2a0a3434a606a7e679c426a7f7c294be20bc2062b6  node-v0.10.46-x86.msi
+a085504b31f1458dd30355089b878136161c6277993db6d019d63191323172ce  openssl-cli.exe
+237bb683d9d9ae4f65f7e66c06259257b17ddb980288571e5f8125827defc3b7  openssl-cli.pdb
+af7a469a545fbacfae860f90c869b584f00ccd588719db8d35595315c40b847b  x64/node.exe
+0312e9641369145ba375d01becaa2cf9fab12cfe40bdd2141f90127d9625ff9f  x64/node.exp
+c29442e5b948f1b40c249b05c83e91bfc82708f774a88240e2b80951a78a02b5  x64/node.lib
+236e386d7510a86b246afa0072514fb5730c55a82f5bd73701270c1eb41a7ec1  x64/node.pdb
+2b6a9260b2c75de118d2d2a6c927f93aae734a92f19bc0f05f1d6855546021c4  x64/node-v0.10.46-x64.msi
+a5f5c8aa5e344f55058bbe6c201111bc9af12e4e1112adc32bf7f92d19452f23  x64/openssl-cli.exe
+b6fd80416d334a68df975f1a0c565891c21504c3a620365f172384a11f0e8a54  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJXbG7mAAoJEMJzeS99g1RdIj8IAImQmP6gxicw0z42G4l7HGu2
+TLFSR/xDgY7k8kYaS+sJifNQcN1BBcSOZW43kSPQ6zwY6V0on/dJ1fLPxtWAmeUC
+WVFmIu5HG9GcKILPZi95hYmY1zlxhnlRzivSkU5WXI0MSSn8INwvd8AQAqR1DQG/
+4/YNGklUap71APfPY8VORiBBJfrW/5JbHdNTdeN8tHrB1BbHwXOiroSKaRLcwew6
+K3rjYQaJPtl1ota7+1ITtRsdwsL1eb390zfqpQzmabWyN1JSek+x0oVSUqjfRdhB
+rVahHhv1D7Muz9KomglrjtSE5Cg+EWat/nfAFCzZhdhqRCvGWZD+UPsy/NkWD90=
+=qS4n
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.10.5.md b/locale/uk/blog/release/v0.10.5.md
new file mode 100755
index 0000000000000..af713f38d8c24
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.5.md
@@ -0,0 +1,76 @@
+---
+date: 2013-04-23T21:05:49.000Z
+version: 0.10.5
+category: release
+title: Node v0.10.5 (Stable)
+slug: node-v0-10-5-stable
+layout: blog-post.hbs
+---
+
+2013.04.23, Version 0.10.5 (Stable)
+
+* uv: Upgrade to 0.10.5 (isaacs)
+
+* build: added support for Visual Studio 2012 (Miroslav Bajtoš)
+
+* http: Don't try to destroy nonexistent sockets (isaacs)
+
+* crypto: LazyTransform on properties, not methods (isaacs)
+
+* assert: put info in err.message, not err.name (Ryan Doenges)
+
+* dgram: fix no address bind() (Ben Noordhuis)
+
+* handle_wrap: fix NULL pointer dereference (Ben Noordhuis)
+
+* os: fix unlikely buffer overflow in os.type() (Ben Noordhuis)
+
+* stream: Fix unshift() race conditions (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.10.5/node-v0.10.5.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.5/node-v0.10.5.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.5/node-v0.10.5-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.5/x64/node-v0.10.5-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.5/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.5/node-v0.10.5-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.5/node-v0.10.5-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.5/node-v0.10.5-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.5/node-v0.10.5-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.5/
+
+Website: https://nodejs.org/docs/v0.10.5/
+
+Documentation: https://nodejs.org/docs/v0.10.5/api/
+
+Shasums:
+
+```
+b3a5122fdfa67a7b69c4c80e5cca4c8d700c9461  node-v0.10.5-darwin-x64.tar.gz
+c95d027af3d774c8650be634b9fe2555c3381c88  node-v0.10.5-darwin-x86.tar.gz
+6bdc5d48368a4425f289c3babe457bb427cb2476  node-v0.10.5-linux-x64.tar.gz
+99643f86f6441436822a0feebd397a3c515d03f9  node-v0.10.5-linux-x86.tar.gz
+72a41a467dcfd96b4244ef8089cf03cf68fa0788  node-v0.10.5-sunos-x64.tar.gz
+6388c920ce5500f6523b718c864ccee2f3c4e72e  node-v0.10.5-sunos-x86.tar.gz
+1dc49f8689c90c84fd335d8023d7c9f01b0183ab  node-v0.10.5-x86.msi
+4a7c59c37afa8ac7b6f2d1d83b34de30f24642ae  node-v0.10.5.pkg
+99b92864f4a277debecb4c872ea7202c9aa6996f  node-v0.10.5.tar.gz
+6f094dd0ce62bcdbf6f36cc67413b1b194d98616  node.exe
+9b1b33512631bc58f6480db5587832c79851afc5  node.exp
+01788dd89217706b9ca8e7ef9f9136d06236a191  node.lib
+1890ff369a65222539ddfd705a40699ca37d476a  node.pdb
+368e7b7b56cb2c05dc818449cf7962a36b1a9cb7  x64/node-v0.10.5-x64.msi
+8624e85306a27079bf4cc3ff25c6914fd59a4e29  x64/node.exe
+c9c0c0b45eebdfaf93b5e6bda38b23052308dab3  x64/node.exp
+0fb687c156204c59e26dff2302f8f9fab73cc3f2  x64/node.lib
+afdecf9ffdce0c28815ae5fc24d6e0defa71ed32  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.6.md b/locale/uk/blog/release/v0.10.6.md
new file mode 100755
index 0000000000000..61c6f918fd1ff
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.6.md
@@ -0,0 +1,68 @@
+---
+date: 2013-05-14T21:32:31.000Z
+version: 0.10.6
+category: release
+title: Node v0.10.6 (Stable)
+slug: node-v0-10-6-stable
+layout: blog-post.hbs
+---
+
+2013.05.14, Version 0.10.6 (Stable)
+
+* module: Deprecate require.extensions (isaacs)
+
+* stream: make Readable.wrap support objectMode, empty streams (Daniel Moore)
+
+* child_process: fix handle delivery (Ben Noordhuis)
+
+* crypto: Fix performance regression (isaacs)
+
+* src: DRY string encoding/decoding (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.10.6/node-v0.10.6.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.6/node-v0.10.6.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.6/node-v0.10.6-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.6/x64/node-v0.10.6-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.6/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.6/node-v0.10.6-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.6/node-v0.10.6-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.6/node-v0.10.6-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.6/node-v0.10.6-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.6/
+
+Website: https://nodejs.org/docs/v0.10.6/
+
+Documentation: https://nodejs.org/docs/v0.10.6/api/
+
+Shasums:
+
+```
+24982edc3b6aafd019273fa5e8a2031353314b56  node-v0.10.6-darwin-x64.tar.gz
+e208c5dc83864a7f35f9df60ee35642bc7dd689c  node-v0.10.6-darwin-x86.tar.gz
+ab2ad473f5aa0f1c5adb50b9ea47fd05010bca2c  node-v0.10.6-linux-x64.tar.gz
+29cdac417449f088e6e6fa67d57c9205d8bff6c5  node-v0.10.6-linux-x86.tar.gz
+66e3a9e53af6d8f27c690a77c329a2bd108965ac  node-v0.10.6-sunos-x64.tar.gz
+05bda089f4f702deddb8e593653676ede5f0e10b  node-v0.10.6-sunos-x86.tar.gz
+6ceb80be28c63f2c57e8479755d206400b205c46  node-v0.10.6-x86.msi
+cd0acf9b332c30aba6a72979d3373e342fad6b95  node-v0.10.6.pkg
+fa06101af8890eeaf997bd2620d7742b71a7223c  node-v0.10.6.tar.gz
+a2a2befa62b3cd2da9c2e51204df017e0f0c0cae  node.exe
+8401647a2f8fb3486fa08d7e603822ae12cf6dee  node.exp
+8ab923eb23584310874a4f63d71244cca5bfc0f8  node.lib
+b9042fec324b202853f7f1d8b1d26ea49d944913  node.pdb
+647a2ea899113e14d8f0894aa969ffd3a5d407c6  x64/node-v0.10.6-x64.msi
+021048aa29fce5ce200b22896fd5f1b053f0d40c  x64/node.exe
+adbdc6112b3172c259a3fa9e07b7d456a0c65beb  x64/node.exp
+226af9033a41c96c68ade96cecedcf1289414424  x64/node.lib
+cca201bfe38713ffde4a0cad70cb3a5325097257  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.7.md b/locale/uk/blog/release/v0.10.7.md
new file mode 100755
index 0000000000000..04a7edeea12bb
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.7.md
@@ -0,0 +1,68 @@
+---
+date: 2013-05-17T21:36:03.000Z
+version: 0.10.7
+category: release
+title: Node v0.10.7 (Stable)
+slug: node-v0-10-7-stable
+layout: blog-post.hbs
+---
+
+2013.05.17, Version 0.10.7 (Stable)
+
+* uv: upgrade to v0.10.7
+
+* npm: Upgrade to 1.2.21
+
+* crypto: Don't ignore verify encoding argument (isaacs)
+
+* buffer, crypto: fix default encoding regression (Ben Noordhuis)
+
+* timers: fix setInterval() assert (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.10.7/node-v0.10.7.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.7/node-v0.10.7.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.7/node-v0.10.7-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.7/x64/node-v0.10.7-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.7/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.7/node-v0.10.7-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.7/node-v0.10.7-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.7/node-v0.10.7-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.7/node-v0.10.7-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.7/
+
+Website: https://nodejs.org/docs/v0.10.7/
+
+Documentation: https://nodejs.org/docs/v0.10.7/api/
+
+Shasums:
+
+```
+95d64001ccd5a17c2c25f1ae4b0358b6131e7cb8  node-v0.10.7-darwin-x64.tar.gz
+c34f991cc0752679002f763b2b3c8927babb08d8  node-v0.10.7-darwin-x86.tar.gz
+673c287bcf671eced6aa94637b7c91e5149f4c56  node-v0.10.7-linux-x64.tar.gz
+9f14d4f9add721148f0c15f093d3e6b1fa3820c9  node-v0.10.7-linux-x86.tar.gz
+1fb7dc4195a9dd228039f5f7ca2cb9f7c35b105a  node-v0.10.7-sunos-x64.tar.gz
+d84cd8afb50df44483b9dab0c65d5c81f07ac4a2  node-v0.10.7-sunos-x86.tar.gz
+d7794a7da103d639fdec4b9e7236a5a0a4330297  node-v0.10.7-x86.msi
+0524ad9268095c9ed435708268e6aad7968309f7  node-v0.10.7.pkg
+f2bde505faf6ffed3084c8e550a9e6d4311f13d5  node-v0.10.7.tar.gz
+5f50384766dd5435dba4989d95032452754150bf  node.exe
+809f12f84c8495d101ce6ae443890e8533695ab0  node.exp
+5a7355e2f75ae3f72deab75f4c9f93e4e5325584  node.lib
+6e45953bd7488a4236c43fea93b05da0854158a7  node.pdb
+fc5e3b2b1c74e53f1d214a9e2d5af30fe5247381  x64/node-v0.10.7-x64.msi
+aa67bbd421f26b37fa09ce30d5e626106677853e  x64/node.exe
+b289989a156d4d7055554962e6f00ba3e380aeea  x64/node.exp
+0dbecc5007c9e28ad488d2058157f8360eaed958  x64/node.lib
+e4b63472787a3db6a3d85237e8c7fb4d973f797b  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.8.md b/locale/uk/blog/release/v0.10.8.md
new file mode 100755
index 0000000000000..f983b504737d0
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.8.md
@@ -0,0 +1,78 @@
+---
+date: 2013-05-24T22:43:01.000Z
+version: 0.10.8
+category: release
+title: Node v0.10.8 (Stable)
+slug: node-v0-10-8-stable
+layout: blog-post.hbs
+---
+
+2013.05.24, Version 0.10.8 (Stable)
+
+* v8: update to 3.14.5.9
+
+* uv: upgrade to 0.10.8
+
+* npm: Upgrade to 1.2.23
+
+* http: remove bodyHead from 'upgrade' events (Nathan Zadoks)
+
+* http: Return true on empty writes, not false (isaacs)
+
+* http: save roundtrips, convert buffers to strings (Ben Noordhuis)
+
+* configure: respect the --dest-os flag consistently (Nathan Rajlich)
+
+* buffer: throw when writing beyond buffer (Trevor Norris)
+
+* crypto: Clear error after DiffieHellman key errors (isaacs)
+
+* string_bytes: strip padding from base64 strings (Trevor Norris)
+
+
+Source Code: https://nodejs.org/dist/v0.10.8/node-v0.10.8.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.8/node-v0.10.8.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.8/node-v0.10.8-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.8/x64/node-v0.10.8-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.8/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.8/node-v0.10.8-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.8/node-v0.10.8-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.8/node-v0.10.8-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.8/node-v0.10.8-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.8/
+
+Website: https://nodejs.org/docs/v0.10.8/
+
+Documentation: https://nodejs.org/docs/v0.10.8/api/
+
+Shasums:
+
+```
+c1b81939e55d42fd7a90ec88ab23fd7a411ed77c  node-v0.10.8-darwin-x64.tar.gz
+4474b8d4222efd6f6076243a4aa78e72760ee01a  node-v0.10.8-darwin-x86.tar.gz
+898283b1ba8a9732c98ce38a89dc15af23291702  node-v0.10.8-linux-x64.tar.gz
+2e15464289f618245fc6f420191490c144d81be3  node-v0.10.8-linux-x86.tar.gz
+9a36b001ce5eef52641b836a42d1fc69c516d329  node-v0.10.8-sunos-x64.tar.gz
+490d9a6d2a300fd2750a4a227288aed67a767713  node-v0.10.8-sunos-x86.tar.gz
+96218cb0c14fbcaa76165fbe5a3af402883f898b  node-v0.10.8-x86.msi
+a713f339195dd009d2614fac25b61bc88295f063  node-v0.10.8.pkg
+d650a09ae868bb04f424e3560658c15b9a885b5b  node-v0.10.8.tar.gz
+38034b7a6bca2dbe3aaacc3cc8aa9920394baaf7  node.exe
+19cd4ae9f3edeaa259e5ca84abd28dea400a91d7  node.exp
+1ccffaf0ff0f4bb11e8d23a2938366fd87b3e583  node.lib
+079f617ef81507a6b5fe7e8bd1f5a2f109a574ec  node.pdb
+985d55d1ba49f47354ba13a419d678bf73634ef9  x64/node-v0.10.8-x64.msi
+25d4d74c73cd57346094979e5c51c5b16d6dcb83  x64/node.exe
+19587e8301371e721695c7aed335f74c6873dfaf  x64/node.exp
+4a002dd8a1742431fc99a2a92580a3040a796f2c  x64/node.lib
+8d18200f9fe81805fe81201355d9f3509bd0c81b  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.10.9.md b/locale/uk/blog/release/v0.10.9.md
new file mode 100755
index 0000000000000..f6071acd6ee34
--- /dev/null
+++ b/locale/uk/blog/release/v0.10.9.md
@@ -0,0 +1,70 @@
+---
+date: 2013-05-30T18:12:12.000Z
+version: 0.10.9
+category: release
+title: Node v0.10.9 (Stable)
+slug: node-v0-10-9-stable
+layout: blog-post.hbs
+---
+
+2013.05.30, Version 0.10.9 (Stable)
+
+* npm: Upgrade to 1.2.24
+
+* uv: Upgrade to v0.10.9
+
+* repl: fix JSON.parse error check (Brian White)
+
+* tls: proper .destroySoon (Fedor Indutny)
+
+* tls: invoke write cb only after opposite read end (Fedor Indutny)
+
+* tls: ignore .shutdown() syscall error (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.10.9/node-v0.10.9.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.10.9/node-v0.10.9.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.10.9/node-v0.10.9-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.10.9/x64/node-v0.10.9-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.10.9/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.10.9/node-v0.10.9-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.10.9/node-v0.10.9-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.10.9/node-v0.10.9-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.10.9/node-v0.10.9-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.10.9/
+
+Website: https://nodejs.org/docs/v0.10.9/
+
+Documentation: https://nodejs.org/docs/v0.10.9/api/
+
+Shasums:
+
+```
+b527f5cf879fd834cb70cec630fce34eb30b5a02  node-v0.10.9-darwin-x64.tar.gz
+b2c9b14aa4a2aa17dd63f2ebe5a4f27171eb64f7  node-v0.10.9-darwin-x86.tar.gz
+4626105fbf907c76314bf487460662e5c97e14ea  node-v0.10.9-linux-x64.tar.gz
+29a4aa89ca61b5a4f3c520f0f798b8b19ce2d3d3  node-v0.10.9-linux-x86.tar.gz
+6d755df136dec6dc085cc6b214154245402a5372  node-v0.10.9-sunos-x64.tar.gz
+2dadf9feca00bb3e681ea31ebd4086ab926a1c39  node-v0.10.9-sunos-x86.tar.gz
+5ff6c7ed7174af8502f54f4476bf8de616180625  node-v0.10.9-x86.msi
+7d945ed2102fcfab28e26dca5f4698b6cf0b921a  node-v0.10.9.pkg
+e4b2bb8c42da2ec90e6fd81da1e6b382ba499608  node-v0.10.9.tar.gz
+889e9c4cb614c79fb728816790a622d13ce9ca88  node.exe
+3b9b15f8ab5fc5378e05301f465114d93ade237a  node.exp
+3c8034b9e4eef1f46d186a266a60690edd17b1f4  node.lib
+b9f1d9452f2815b43df98b40ab1b6cf2c358ad8a  node.pdb
+4b767d596c8a395fe22215d065f9d31b3a5b9423  x64/node-v0.10.9-x64.msi
+e763bc24888254ddd992a4b7302d1ad4538ad920  x64/node.exe
+eec159254e209f172bca37dc547f0bfcfa1bd87c  x64/node.exp
+6ae5f3a36ffba256cb8077c47a218749449f798c  x64/node.lib
+5c2283b50c74a8b43708fdc29cb5c314fbe2d018  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.0.md b/locale/uk/blog/release/v0.11.0.md
new file mode 100755
index 0000000000000..b06752871fb28
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.0.md
@@ -0,0 +1,89 @@
+---
+date: 2013-03-28T21:52:55.000Z
+version: 0.11.0
+category: release
+title: Node v0.11.0 (Unstable)
+slug: node-v0-11-0-stable
+layout: blog-post.hbs
+---
+
+2013.03.28, Version 0.11.0 (Unstable)
+
+* V8: update to 3.17.13
+
+* os: use %SystemRoot% or %windir% in os.tmpdir() (Suwon Chae)
+
+* util: fix util.inspect() line width calculation (Marcin Kostrzewa)
+
+* buffer: remove _charsWritten (Trevor Norris)
+
+* fs: uv_[fl]stat now reports subsecond resolution (Timothy J Fontaine)
+
+* fs: Throw if error raised and missing callback (bnoordhuis)
+
+* tls: expose SSL_CTX_set_timeout via tls.createServer (Manav Rathi)
+
+* tls: remove harmful unnecessary bounds checking (Marcel Laverdet)
+
+* buffer: write ascii strings using WriteOneByte (Trevor Norris)
+
+* dtrace: fix generation of v8 constants on freebsd (Fedor Indutny)
+
+* dtrace: x64 ustack helper (Fedor Indutny)
+
+* readline: handle wide characters properly (Nao Iizuka)
+
+* repl: Use a domain to catch async errors safely (isaacs)
+
+* repl: emit 'reset' event when context is reset (Sami Samhuri)
+
+* util: custom `inspect()` method may return an Object (Nathan Rajlich)
+
+* console: `console.dir()` bypasses inspect() methods (Nathan Rajlich)
+
+
+Source Code: https://nodejs.org/dist/v0.11.0/node-v0.11.0.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.0/node-v0.11.0.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.0/node-v0.11.0-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.0/x64/node-v0.11.0-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.0/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.0/node-v0.11.0-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.0/node-v0.11.0-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.0/node-v0.11.0-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.0/node-v0.11.0-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.0/
+
+Website: https://nodejs.org/docs/v0.11.0/
+
+Documentation: https://nodejs.org/docs/v0.11.0/api/
+
+Shasums:
+```
+4889d63a4a08d146d59cd057b1c8b341ceac07cf  node-v0.11.0-darwin-x64.tar.gz
+4ef64fa36c095edfa3c6da852ed1ec46c6f3cf23  node-v0.11.0-darwin-x86.tar.gz
+04c4d1fb71f98dfc921d9558667a727ca1aa6586  node-v0.11.0-linux-x64.tar.gz
+b1507837292e23464e2d184007f2567db3db1483  node-v0.11.0-linux-x86.tar.gz
+cd195da08ea5208a6c08b95511fa888d750f4cd7  node-v0.11.0-sunos-x64.tar.gz
+4698b9a6cb911cbea3deac38ea191cef3051b3ab  node-v0.11.0-sunos-x86.tar.gz
+829649fe65133459c7fc231b8d048f19ae870c7b  node-v0.11.0-x86.msi
+7958b8212aaa9787724c552197d37cf5602ff645  node-v0.11.0.pkg
+0402aae18f847238409e9d1a5ddd806beb5fe678  node-v0.11.0.tar.gz
+320778de3329437815daa4f86d1a89db33458126  node.exe
+1f4f509a9dc48c519064ca7f2deddeaff2b6b15b  node.exp
+5f83864acae194c0652a61af71262bd1ba55a04c  node.lib
+0d100a18ba569e5e9bb9e216355959261c4cd77b  node.pdb
+b55553c83e12f253f23dec4d998b05bd673db83b  x64/node-v0.11.0-x64.msi
+7100ef58f9a8428d2bdd9d4de8ffb679d0198b1e  x64/node.exe
+12bf810852e7097bde1bf4bff6cd7f802603cdb9  x64/node.exp
+28f83178241353dc727ba6d8ff38f9b9177be79a  x64/node.lib
+6c0f43db501facc3d9ed542a090f9ba2e84bdc41  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.1.md b/locale/uk/blog/release/v0.11.1.md
new file mode 100755
index 0000000000000..083bc60071513
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.1.md
@@ -0,0 +1,78 @@
+---
+date: 2013-04-19T16:11:40.000Z
+version: 0.11.1
+category: release
+title: Node v0.11.1 (Unstable)
+slug: node-v0-11-1-unstable
+layout: blog-post.hbs
+---
+
+**Note**: This version does not work on 64-bit Windows systems  Expect
+a fix for this bug in the next v0.11 release.  As this is an unstable
+release, we opted to push out the changes for other systems, rather
+than delay.
+
+2013.04.19, Version 0.11.1 (Unstable)
+
+* V8: upgrade to 3.18.0
+
+* uv: Upgrade to v0.11.1
+
+* http: split into multiple separate modules (Timothy J Fontaine)
+
+* http: escape unsafe characters in request path (Ben Noordhuis)
+
+* url: Escape all unwise characters (isaacs)
+
+* build: depend on v8 postmortem-metadata if enabled (Paddy Byers)
+
+* etw: update prototypes to match dtrace provider (Timothy J Fontaine)
+
+* buffer: change output of Buffer.prototype.toJSON() (David Braun)
+
+* dtrace: actually use the _handle.fd value (Timothy J Fontaine)
+
+* dtrace: pass more arguments to probes (Dave Pacheco)
+
+* build: allow building with dtrace on osx (Dave Pacheco)
+
+* zlib: allow passing options to convenience methods (Kyle Robinson Young)
+
+
+Source Code: https://nodejs.org/dist/v0.11.1/node-v0.11.1.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.1/node-v0.11.1.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.1/node-v0.11.1-x86.msi
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.1/node-v0.11.1-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.1/node-v0.11.1-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.1/node-v0.11.1-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.1/node-v0.11.1-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.1/
+
+Website: https://nodejs.org/docs/v0.11.1/
+
+Documentation: https://nodejs.org/docs/v0.11.1/api/
+
+Shasums:
+
+```
+83f440046d64619b974487e3445d541fa1310ec6  node-v0.11.1-darwin-x64.tar.gz
+684118ba684d21f07bf1095727a15457d301edf9  node-v0.11.1-darwin-x86.tar.gz
+2c71490f3664421f58145f2945018efeb4d43652  node-v0.11.1-linux-x64.tar.gz
+07b7ed48a50792605229efb2c256a3681d242b0e  node-v0.11.1-linux-x86.tar.gz
+bbe383ba0954f47812ff5d853069069901d8160d  node-v0.11.1-sunos-x64.tar.gz
+6782ff3bdd3af79d8ba8c8b0f352ca2106fcfafc  node-v0.11.1-sunos-x86.tar.gz
+47bf9b530d662f67b7b07729d83cd4f5575846b8  node-v0.11.1-x86.msi
+b98e549850355be6a107044ca6a000518599a982  node-v0.11.1.pkg
+fe13c36f4d9116ed718af9894aab989d74a9d91c  node-v0.11.1.tar.gz
+655ab3f0ce8227ffd68714491c2dd5aa7bdc0d10  node.exe
+43a8f8a9cf53c0a2318b2288b6ba0e0f2a052858  node.exp
+d54e5b303a0568f803ad09aa802b7f95b676180c  node.lib
+08098d40b362018f5df09f302d85c5834f127292  node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.10.md b/locale/uk/blog/release/v0.11.10.md
new file mode 100755
index 0000000000000..8134140415cce
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.10.md
@@ -0,0 +1,109 @@
+---
+date: 2014-01-01T00:20:57.000Z
+version: 0.11.10
+category: release
+title: Node v0.11.10 (Unstable)
+slug: node-v0-11-10-unstable
+layout: blog-post.hbs
+---
+
+2013.12.31, Version 0.11.10 (Unstable)
+
+* http_parser: update to 2.2
+
+* uv: Upgrade to v0.11.17
+
+* v8: Upgrade to 3.22.24.10
+
+* buffer: optimize writeInt* methods (Paul Loyd)
+
+* child_process: better error handling (Alexis Campailla)
+
+* cluster: do not synchronously emit 'setup' event (Sam Roberts)
+
+* cluster: restore backwards compatibility and various fixes (Sam Roberts)
+
+* crypto: remove unnecessary OpenSSL_add_all_digests (Yorkie)
+
+* crypto: support GCM authenticated encryption mode. (Ingmar Runge)
+
+* dns: add resolveSoa and 'SOA' rrtype (Tuğrul Topuz)
+
+* events: move EE c'tor guts to EventEmitter.init (Bert Belder)
+
+* http: DELETE shouldn't default to chunked encoding (Lalit Kapoor)
+
+* http: parse the status message in a http response. (Cam Swords)
+
+* node: fix removing AsyncListener in callback (Vladimir Kurchatkin)
+
+* node: follow specification, zero-fill ArrayBuffers (Trevor Norris)
+
+* openssl: use ASM optimized routines (Fedor Indutny)
+
+* process: allow nextTick infinite recursion (Trevor Norris)
+
+* querystring: remove `name` from `stringify()` (Yorkie)
+
+* timers: setImmediate v8 optimization fix (pflannery)
+
+* tls: add serialNumber to getPeerCertificate() (Ben Noordhuis)
+
+* tls: reintroduce socket.encrypted (Fedor Indutny)
+
+* tls: fix handling of asterisk in SNI context (Fedor Indutny)
+
+* util: Format negative zero as '-0' (David Chan)
+
+* vm: fix race condition in timeout (Alexis Campailla)
+
+* windows: fix dns lookup of localhost with ipv6 (Alexis Campailla)
+
+
+Source Code: https://nodejs.org/dist/v0.11.10/node-v0.11.10.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.10/node-v0.11.10.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.10/node-v0.11.10-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.10/x64/node-v0.11.10-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.10/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.10/node-v0.11.10-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.10/node-v0.11.10-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.10/node-v0.11.10-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.10/node-v0.11.10-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.10/
+
+Website: https://nodejs.org/docs/v0.11.10/
+
+Documentation: https://nodejs.org/docs/v0.11.10/api/
+
+Shasums:
+```
+4f7d0d43c1ee7593035ddb3cf09020a18a03c794  node-v0.11.10-darwin-x64.tar.gz
+3b7100bcff39e39b6db5118805fcfc76d8524da2  node-v0.11.10-darwin-x86.tar.gz
+3df4cb183a78bb975c831155d3c0aa29a274dec4  node-v0.11.10-linux-x64.tar.gz
+12fc680b0a26cc73b4df0a0e9544b0db2bc06e96  node-v0.11.10-linux-x86.tar.gz
+145417c8d801174a42255dc273da962cde94ffc9  node-v0.11.10-sunos-x64.tar.gz
+981baba494e9be8978fa1bb336b3048367e809ce  node-v0.11.10-sunos-x86.tar.gz
+5f4d96c37cfb1423cc844f52e0547cb5bca99dd8  node-v0.11.10-x86.msi
+8bd455fb7539609a7ee6bed87875a908fd6221ea  node-v0.11.10.pkg
+b860f511e4fc657a64594fc9f3f1225c1a140e5e  node-v0.11.10.tar.gz
+80976bffed871310a86d31694e2767ccbe9f6c35  node.exe
+f11675958a492a83f057f356dd224ad507e82c61  node.exp
+5a80c4ab5b1d0984b3a118536ca6421b4b9bc14f  node.lib
+207daafc40fba36200504fa52869b9c41cdbf5c9  node.pdb
+3aa165e2d235888037f8099abd5bc9dca4b12100  pkgsrc/nodejs-ia32-0.11.10.tgz
+1d5ef599b93c7d8c0d34ff2ab3dd4255babfaf72  pkgsrc/nodejs-x64-0.11.10.tgz
+a6b16441721c34bae732b2b14134d0e1fd9706de  x64/node-v0.11.10-x64.msi
+933ff8a0a42c6e69fcbd51b9eaae4e4d14f043ae  x64/node.exe
+31c9abd54e5ba431f0645fa04d315f15dc010107  x64/node.exp
+66bec5eae9033972463a6bd89183aa97bb84bfd1  x64/node.lib
+43fbac8665dfcd121e547f56b1434a1c6039091d  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.11.md b/locale/uk/blog/release/v0.11.11.md
new file mode 100755
index 0000000000000..dd26c1990083c
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.11.md
@@ -0,0 +1,109 @@
+---
+date: 2014-01-29T03:46:04.000Z
+version: 0.11.11
+category: release
+title: Node v0.11.11 (Unstable)
+slug: node-v0-11-11-unstable
+layout: blog-post.hbs
+---
+
+2014.01.29, Version 0.11.11 (Unstable)
+
+* v8: Upgrade to 3.22.24.19
+
+* http_parser: Upgrade to 2.2.1
+
+* openssl: Upgrade to 1.0.1f
+
+* uv: Upgrade to 0.11.18
+
+* async-listener: revamp of subsystem (Trevor Norris)
+
+* node: do not ever close stdio (Fedor Indutny)
+
+* http: use writev on chunked encoding (Trevor Norris)
+
+* async_wrap/timers: remove Add/RemoveAsyncListener (Trevor Norris)
+
+* child_process: better error reporting for exec (Fedor Indutny)
+
+* crypto: add newline to cert and key if not present (Fedor Indutny)
+
+* crypto: clear error in GetPeerCertificate (Fedor Indutny)
+
+* crypto: honor default ciphers in client mode (Jacob Hoffman-Andrews)
+
+* crypto: introduce .setEngine(engine, [flags]) (Fedor Indutny)
+
+* crypto: support custom pbkdf2 digest methods (Ben Noordhuis)
+
+* domain: fix off-by-one in Domain.exit() (Ryan Graham)
+
+* http: concatenate duplicate headers by default (Alex Kocharin)
+
+* http: do not emit EOF non-readable socket (Fedor Indutny)
+
+* node: fix argument parsing with -p arg (Alexis Campailla)
+
+* path: improve POSIX path.join() performance (Jo Liss)
+
+* tls: emit `clientError` on early socket close (Fedor Indutny)
+
+* tls: introduce `.setMaxSendFragment(size)` (Fedor Indutny)
+
+* tls: make cert/pfx optional in tls.createServer() (Ben Noordhuis)
+
+* tls: process accumulated input (Fedor Indutny)
+
+* tls: show human-readable error messages (Ben Noordhuis)
+
+* util: handle escaped forward slashes correctly (Tom Gallacher)
+
+
+Source Code: https://nodejs.org/dist/v0.11.11/node-v0.11.11.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.11/node-v0.11.11.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.11/node-v0.11.11-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.11/x64/node-v0.11.11-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.11/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.11/node-v0.11.11-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.11/node-v0.11.11-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.11/node-v0.11.11-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.11/node-v0.11.11-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.11/
+
+Website: https://nodejs.org/docs/v0.11.11/
+
+Documentation: https://nodejs.org/docs/v0.11.11/api/
+
+Shasums:
+```
+b14d62e992a12cb552277770942a89b94c9edddd  node-v0.11.11-darwin-x64.tar.gz
+62ebf588c1909f0d820e975ee88cd506c0c8de30  node-v0.11.11-darwin-x86.tar.gz
+cb0f4477d6ec96993e0b538885e960027872a936  node-v0.11.11-linux-x64.tar.gz
+ac9e91f268f1ac1bad79a0c817d5d8689ece1095  node-v0.11.11-linux-x86.tar.gz
+e25eab9e2e560d02b0ca57a219a0eba3d4e3d14d  node-v0.11.11-sunos-x64.tar.gz
+3a1ce4e226edf56fb7811ebe13da9163ae0a1460  node-v0.11.11-sunos-x86.tar.gz
+a0b237df15b1ce07049f72b4a49b4ab5109dfe67  node-v0.11.11-x86.msi
+78807abf9b4faeea4b405ad9fb13daab09306772  node-v0.11.11.pkg
+65b257ec6584bf339f06f58a8a02ba024e13f283  node-v0.11.11.tar.gz
+33fa2097f75f5077bb1ef34930594a591d922a7f  node.exe
+192b4503b351fd9a98a136f697e85c4372c71bd1  node.exp
+bd9a3482a6be8b5708172450abe9358a3956816e  node.lib
+d51780e8f3a936d2dd28fa00f832424ad6e7ca42  node.pdb
+a687afbb8e4d5a3a120a812e889dae2f0eca2fa4  pkgsrc/nodejs-ia32-0.11.11.tgz
+3da73af5f7059000b1a898259de9e7197b6e9bac  pkgsrc/nodejs-x64-0.11.11.tgz
+9fa14e245795b7adf0dfebe317490fefd40bfbe9  x64/node-v0.11.11-x64.msi
+e19bcf90ef4d864a11744648cadb864911ee5f4e  x64/node.exe
+83e31621bfc45b9b86f4724a3255cf3afdb3236a  x64/node.exp
+c778c1853e45686e5fefb463a419658ff9b966e1  x64/node.lib
+ced8fe51cd619d07c53c0f1f1fdcfc5ff3c70373  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.12.md b/locale/uk/blog/release/v0.11.12.md
new file mode 100755
index 0000000000000..1cfc5396d9f1f
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.12.md
@@ -0,0 +1,123 @@
+---
+date: 2014-03-12T14:56:30.000Z
+version: 0.11.12
+category: release
+title: Node v0.11.12 (Unstable)
+slug: node-v0-11-12-unstable
+layout: blog-post.hbs
+---
+
+2014.03.11, Version 0.11.12 (Unstable)
+
+* uv: Upgrade to v0.11.22 (Timothy J Fontaine)
+
+* buffer: allow toString to accept Infinity for end (Brian White)
+
+* child_process: add spawnSync/execSync (Bert Belder, Timothy J Fontaine)
+
+* cluster: handle bind errors on Windows (Alexis Campailla)
+
+* contextify: handle infinite recursion errors (Fedor Indutny)
+
+* crypto: allow custom generator for DiffieHellman (Brian White)
+
+* crypto: allow setting add'l authenticated data (Brian White)
+
+* crypto: fix CipherFinal return value check (Brian White)
+
+* crypto: make NewSessionDoneCb public (Fedor Indutny)
+
+* dgram: pass the bytes sent to the send callback (Timothy J Fontaine)
+
+* dns: validate arguments in resolver (Kenan Sulayman)
+
+* dns: verify argument is valid function in resolve (Kenan Sulayman)
+
+* http: avoid duplicate keys in writeHead (David Björklund)
+
+* net: add localPort to connect options (Timothy J Fontaine)
+
+* node: do not print SyntaxError hints to stderr (Fedor Indutny)
+
+* node: invoke `beforeExit` again if loop was active (Fedor Indutny)
+
+* node: make AsyncListenerInst field more explicit (Trevor Norris)
+
+* os: networkInterfaces include scopeid for ipv6 (Xidorn Quan)
+
+* process: allow changing `exitCode` in `on('exit')` (Fedor Indutny)
+
+* readline: fix `line` event, if input emit 'end' (Yazhong Liu)
+
+* src: add tracing.v8.on('gc') statistics hooks (Ben Noordhuis)
+
+* src: add v8.getHeapStatistics() function (Ben Noordhuis)
+
+* src: emit 'beforeExit' event on process object (Ben Noordhuis)
+
+* src: move AsyncListener from process to tracing (Trevor Norris)
+
+* tls: fix crash in SNICallback (Fedor Indutny)
+
+* tls: introduce asynchronous `newSession` (Fedor Indutny)
+
+* util: show meaningful values for boxed primitives (Nathan Rajlich)
+
+* vm: don't copy Proxy object from parent context (Ben Noordhuis)
+
+* windows: make stdout/sterr pipes blocking (Alexis Campailla)
+
+* zlib: add sync versions for convenience methods (Nikolai Vavilov)
+
+
+Source Code: https://nodejs.org/dist/v0.11.12/node-v0.11.12.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.12/node-v0.11.12.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.12/node-v0.11.12-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.12/x64/node-v0.11.12-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.12/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.12/node-v0.11.12-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.12/node-v0.11.12-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.12/node-v0.11.12-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.12/node-v0.11.12-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.12/
+
+Website: https://nodejs.org/docs/v0.11.12/
+
+Documentation: https://nodejs.org/docs/v0.11.12/api/
+
+Shasums:
+```
+058930a3993e91bc6e79a0874b2c1a0b103469b1  node-v0.11.12-darwin-x64.tar.gz
+0e6210a19ac94920e0357716f3600722de63763b  node-v0.11.12-darwin-x86.tar.gz
+b9d2eae74df55bdb252fab239d2c496aec329aad  node-v0.11.12-linux-x64.tar.gz
+d0f22e5821f0b105300415283143e9da4937dca2  node-v0.11.12-linux-x86.tar.gz
+7b9e432212e7ad04e1e4a00b0747cfe5e1ad50d0  node-v0.11.12-sunos-x64.tar.gz
+66e4af23c0489b258b87d8cd2eee350294e6c3f5  node-v0.11.12-sunos-x86.tar.gz
+5452d6aadbef3b4a65bb147407a0fd1657a7fb15  node-v0.11.12-x86.msi
+3522b87d7c10527182bc9f1cff313a737c1a37bb  node-v0.11.12.pkg
+d991057af05dd70feb2126469ce279a2fe869e86  node-v0.11.12.tar.gz
+6544c0c193a80f7450fa8f36f8080cbe062d27bb  node.exe
+c27b3dee963e5ec0c3b25e42292b3679e4e2f50b  node.exp
+c52a86505b53edc9d8fe6f65916fc77165e404d1  node.lib
+65ceb13db7ff0706a5ea3611ac2cbd84afe6798c  node.pdb
+d943ecaf3fd55b198c617e01f52bdee480d1c9b7  openssl-cli.exe
+97628b29758cbbdddab027215f441a623f95e35e  openssl-cli.pdb
+d02987fe0852a85e63acdbd45d7178ad55d6fe0b  pkgsrc/nodejs-ia32-0.11.12.tgz
+4076893ac96718edbc2f2ed1f20953a8ec66cf48  pkgsrc/nodejs-x64-0.11.12.tgz
+e88f8ae5a722e135083ed3d0085e2d15ea527125  x64/node-v0.11.12-x64.msi
+ea6fc65061aafcf4e4b58d58a3e7eee9c4866a0b  x64/node.exe
+3c7cc6b0fcd1e304e6ccdc179e5a7df24909910e  x64/node.exp
+7b906562dc52d9e5825de3e4ce46ac114f7f76d3  x64/node.lib
+06a0d0b1c941f805dd48f9b85c8baef1e0e936d4  x64/node.pdb
+90f3d8c4f470b5a46934e90a7b0f983afc6fa0ec  x64/openssl-cli.exe
+c5df898ab9dd3ed28826aa7be715c0ae52842f10  x64/openssl-cli.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.14.md b/locale/uk/blog/release/v0.11.14.md
new file mode 100755
index 0000000000000..0a6ac0029d6be
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.14.md
@@ -0,0 +1,238 @@
+---
+date: 2014-09-25T00:12:24.000Z
+version: 0.11.14
+category: release
+title: Node v0.11.14 (Unstable)
+slug: node-v0-11-14-unstable
+layout: blog-post.hbs
+---
+
+2014.09.24, Version 0.11.14 (Unstable)
+
+* uv: Upgrade to v1.0.0-rc1
+
+* http_parser: Upgrade to v2.3.0
+
+* npm: Upgrade to v2.0.0
+
+* openssl: Upgrade to v1.0.1i
+
+* v8: Upgrade to 3.26.33
+
+* Add fast path for simple URL parsing (Gabriel Wicke)
+
+* Added support for options parameter in console.dir() (Xavi Magrinyà)
+
+* Cluster: fix shared handles on Windows (Alexis Campailla)
+
+* buffer: Fix incorrect Buffer.compare behavior (Feross Aboukhadijeh)
+
+* buffer: construct new buffer from buffer toJSON() output (cjihrig)
+
+* buffer: improve Buffer constructor (Kang-Hao Kenny)
+
+* build: linking CoreFoundation framework for OSX (Thorsten Lorenz)
+
+* child_process: accept uid/gid everywhere (Fedor Indutny)
+
+* child_process: add path to spawn ENOENT Error (Ryan Cole)
+
+* child_process: copy spawnSync() cwd option to proper buffer (cjihrig)
+
+* child_process: do not access stderr when stdio set to 'ignore' (cjihrig)
+
+* child_process: don't throw on EAGAIN (Charles)
+
+* child_process: don't throw on EMFILE/ENFILE (Ben Noordhuis)
+
+* child_process: use full path for cmd.exe on Win32 (Ed Morley)
+
+* cluster: allow multiple calls to setupMaster() (Ryan Graham)
+
+* cluster: centralize removal from workers list. (Julien Gilli)
+
+* cluster: enable error/message events using .worker (cjihrig)
+
+* cluster: include settings object in 'setup' event (Ryan Graham)
+
+* cluster: restore v0.10.x setupMaster() behaviour (Ryan Graham)
+
+* cluster: support options in Worker constructor (cjihrig)
+
+* cluster: test events emit on cluster.worker (Sam Roberts)
+
+* console: console.dir() accepts options object (Xavi Magrinyà)
+
+* crypto: add `honorCipherOrder` argument (Fedor Indutny)
+
+* crypto: allow padding in RSA methods (Fedor Indutny)
+
+* crypto: clarify RandomBytes() error msg (Mickael van der Beek)
+
+* crypto: never store pointer to conn in SSL_CTX (Fedor Indutny)
+
+* crypto: unsigned value can't be negative (Brian White)
+
+* dgram: remove new keyword from errnoException (Jackson Tian)
+
+* dns: always set variable family in lookup() (cjihrig)
+
+* dns: include host name in error message if available (Maciej Małecki)
+
+* dns: introduce lookupService function (Saúl Ibarra Corretgé)
+
+* dns: send lookup c-ares errors to callback (Chris Dickinson)
+
+* dns: throw if hostname is not string or falsey (cjihrig)
+
+* events: Output the event that is leaking (Arnout Kazemier)
+
+* fs: close file if fstat() fails in readFile() (cjihrig)
+
+* fs: fs.readFile should not throw uncaughtException (Jackson Tian)
+
+* http: add 308 status_code, see RFC7238 (Yazhong Liu)
+
+* http: don't default OPTIONS to chunked encoding (Nick Muerdter)
+
+* http: fix bailout for writeHead (Alex Kocharin)
+
+* http: remove unused code block (Fedor Indutny)
+
+* http: write() after end() emits an error. (Julien Gilli)
+
+* lib, src: add vm.runInDebugContext() (Ben Noordhuis)
+
+* lib: noisy deprecation of child_process customFds (Ryan Graham)
+
+* module: don't require fs several times (Robert Kowalski)
+
+* net,dgram: workers can listen on exclusive ports (cjihrig)
+
+* net,stream: add isPaused, don't read() when paused (Chris Dickinson)
+
+* net: Ensure consistent binding to IPV6 if address is absent (Raymond Feng)
+
+* net: add remoteFamily for socket (Jackson Tian)
+
+* net: don't emit listening if handle is closed (Eli Skeggs)
+
+* net: don't prefer IPv4 addresses during resolution (cjihrig)
+
+* net: don't throw on net.Server.close() (cjihrig)
+
+* net: reset `errorEmitted` on reconnect (Ed Umansky)
+
+* node: set names for prototype methods (Trevor Norris)
+
+* node: support v8 microtask queue (Vladimir Kurchatkin)
+
+* path: fix slice OOB in trim (Lucio M. Tato)
+
+* path: isAbsolute() should always return boolean (Herman Lee)
+
+* process: throw TypeError if kill pid not a number (Sam Roberts)
+
+* querystring: custom encode and decode (fengmk2)
+
+* querystring: do not add sep for empty array (cjihrig)
+
+* querystring: remove prepended ? from query field (Ezequiel Rabinovich)
+
+* readline: fix close event of readline.Interface() (Yazhong Liu)
+
+* readline: fixes scoping bug (Dan Kaplun)
+
+* readline: implements keypress buffering (Dan Kaplun)
+
+* repl: fix multi-line input (Fedor Indutny)
+
+* repl: fix overwrite for this._prompt (Yazhong Liu)
+
+* repl: proper `setPrompt()` and `multiline` support (Fedor Indutny)
+
+* stream: don't try to finish if buffer is not empty (Vladimir Kurchatkin)
+
+* stream: only end reading on null, not undefined (Jonathan Reem)
+
+* streams: set default hwm properly for Duplex (Andrew Oppenlander)
+
+* string_bytes: ucs2 support big endian (Andrew Low)
+
+* tls, crypto: add DHE support (Shigeki Ohtsu)
+
+* tls: `checkServerIdentity` option (Trevor Livingston)
+
+* tls: add DHE-RSA-AES128-SHA256 to the def ciphers (Shigeki Ohtsu)
+
+* tls: better error reporting at cert validation (Fedor Indutny)
+
+* tls: support multiple keys/certs (Fedor Indutny)
+
+* tls: throw an error, not string (Jackson Tian)
+
+* udp: make it possible to receive empty udp packets (Andrius Bentkus)
+
+* url: treat  the same as / (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.11.14/node-v0.11.14.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.14/node-v0.11.14.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.14/node-v0.11.14-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.14/x64/node-v0.11.14-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.14/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.14/node-v0.11.14-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.14/node-v0.11.14-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.14/node-v0.11.14-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.14/node-v0.11.14-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.14/
+
+Website: https://nodejs.org/docs/v0.11.14/
+
+Documentation: https://nodejs.org/docs/v0.11.14/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+aef6375b86ab40102ff6b879b60c042399fd6606  node-v0.11.14-darwin-x64.tar.gz
+c0f1a9d8614513eeb9014aa385e01fd9177227bd  node-v0.11.14-darwin-x86.tar.gz
+b3f2a9029e2a6cb3816be5ddcc9cf3dd87e145d6  node-v0.11.14-linux-x64.tar.gz
+0c0e69ff51ce33afa192e030e082d4da34ab8060  node-v0.11.14-linux-x86.tar.gz
+0308c18297398578de67abff012a7797bdbeb073  node-v0.11.14-sunos-x64.tar.gz
+6411add5321401e774cb2ce2c8ca79f3a072dfc9  node-v0.11.14-sunos-x86.tar.gz
+ec3fad6d8714ba6d9182974f0ee249d0e8d194b7  node-v0.11.14-x86.msi
+38bc708503a91f17f3ea7b0a3a77028582d43a48  node-v0.11.14.pkg
+159860fd6d27c9abf2254529e22fe67e385809d6  node-v0.11.14.tar.gz
+b00d35d90de8ee133d282e5f15d038ffccc43b41  node.exe
+1e7a51f619dd5f7b0d903267f87ed25d3171ccb1  node.exp
+7999caa1359645cae722b03b38ebdfdd5b1972c0  node.lib
+14fd5b212d48d9f42d9d24adb7b3a325d0472fe3  node.pdb
+00c1cc43acf4853fdd2be5b549d3be0157b5f212  openssl-cli.exe
+1ebfdc1d8572c2a167111bb11496b67cbf1177bf  openssl-cli.pdb
+3f05fc2f4aa95e688bde41c3264ef9295f307ad0  x64/node-v0.11.14.20140819-x64.msi
+7c808b88a4c1042ba806dfc32a79ced8cffce180  x64/node.exe
+6b8f97668b44cc18ca5c3829a4082c620037d2c6  x64/node.exp
+53368a3f8c37d6a716b6d78be1a20fc1e692c22a  x64/node.lib
+8c524ce3726e503e4900658241983f364e5aed06  x64/node.pdb
+aa1db1b7a5d2d5416c6a44023865f02f34812c29  x64/openssl-cli.exe
+90b865ed6df55bde36d24ee7405bdc54b49b8c1e  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlQjWPEACgkQfTP/nQJGQG0K1ACgoowg2K3mogTE3N3SZROZiGFb
+NpMAn3ehnOxErnTUWrWUyuLZ4A7Ypv2u
+=JFiI
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.11.15.md b/locale/uk/blog/release/v0.11.15.md
new file mode 100755
index 0000000000000..6d6644647bcf5
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.15.md
@@ -0,0 +1,233 @@
+---
+date: 2015-01-20T23:42:57.000Z
+version: 0.11.15
+category: release
+title: Node v0.11.15 (Unstable)
+slug: node-v0-11-15-unstable
+layout: blog-post.hbs
+---
+
+2015.01.20, Version 0.11.15 (Unstable)
+
+* v8: Upgrade to 3.28.73
+
+* uv: Upgrade to 1.0.2
+
+* npm: Upgrade to v2.1.6
+
+* uv: float patch to revert tty breakage (Trevor Norris)
+
+* v8: re-implement debugger-agent (Fedor Indutny)
+
+* v8: apply floating irhydra patch (Fedor Indutny)
+
+* v8: fix postmortem-metadata generator (Refael Ackermann)
+
+* debugger: fix unhandled error in setBreakpoint (Miroslav Bajtoš)
+
+* async-wrap: add event hooks (Trevor Norris)
+
+* async-wrap: expose async-wrap as binding (Trevor Norris)
+
+* buffer, doc: misc. fix and cleanup (Trevor Norris)
+
+* buffer: add generic functions for (u)int ops (Yazhong Liu)
+
+* buffer: fix and cleanup fill() (Trevor Norris)
+
+* buffer: mv floating point read/write checks to JS (Trevor Norris)
+
+* build, i18n: improve Intl build, add "--with-intl" (Steven R. Loomis)
+
+* build: add small-icu support for binary packages (Julien Gilli)
+
+* build: do not generate support for libuv's probes (Julien Gilli)
+
+* build: i18n: add icu config options (Steven R. Loomis)
+
+* build: i18n: support little-endian machines (Steven Loomis)
+
+* build: vcbuild fix "The input line is too long." (Alexis Campailla)
+
+* child_process: improve spawn() argument handling (cjihrig)
+
+* cluster: avoid race enabling debugger in worker (Timothy J Fontaine)
+
+* cluster: cluster.disconnect() should check status (Sam Roberts)
+
+* cluster: do not signal children in debug mode (Fedor Indutny)
+
+* cluster: don't assert if worker has no handles (Sam Roberts)
+
+* core: fix usage of uv_cwd (Saúl Ibarra Corretgé)
+
+* core: replace uv_fs_readdir with uv_fs_scandir (Saúl Ibarra Corretgé)
+
+* crypto: createDiffieHellman throw for bad args (Trevor Norris)
+
+* crypto: lower RSS usage for TLSCallbacks (Fedor Indutny)
+
+* crypto: store thread id as pointer-sized (Alexis Campailla)
+
+* dns: propagate domain for c-ares methods (Chris Dickinson)
+
+* fs: fix symlink error message (Vladimir Kurchatkin)
+
+* http: Improve _addHeaderLines method (Jackson Tian)
+
+* http: cleanup setHeader() (Trevor Norris)
+
+* http: rename flush to flushHeaders (Timothy J Fontaine)
+
+* lib,src: fix spawnSync ignoring its 'env' option (Juanjo)
+
+* modules: adding load linked modules feature (Thorsten Lorenz)
+
+* net: Make server.connections un-enumerable (Patrick Mooney)
+
+* net: add pauseOnConnect option to createServer() (cjihrig)
+
+* net: make connect() input validation synchronous (cjihrig)
+
+* node: avoid automatic microtask runs (Vladimir Kurchatkin)
+
+* node: fix throws before timer module is loaded (Trevor Norris)
+
+* openssl: fix keypress requirement in apps on win32 (Fedor Indutny)
+
+* path: added parse() and format() functions (Rory Bradford)
+
+* path: allow calling platform specific methods (Timothy J Fontaine)
+
+* path: don't lower-cases drive letters (Bert Belder)
+
+* path: refactor normalizeArray() (Nathan Woltman)
+
+* process: pid can be a string in process.kill() (Sam Roberts)
+
+* readline: fix performance issue when large line (Jicheng Li)
+
+* readline: should not require an output stream. (Julien Gilli)
+
+* smalloc: check if obj has external data (Vladimir Kurchatkin)
+
+* smalloc: don't allow to dispose typed arrays (Vladimir Kurchatkin)
+
+* smalloc: fix bad assert for zero length data (Trevor Norris)
+
+* smalloc: fix copyOnto optimization (Vladimir Kurchatkin)
+
+* src: all wrap's now use actual FunctionTemplate (Trevor Norris)
+
+* src: fix VC++ warning C4244 (Rasmus Christian Pedersen)
+
+* src: remove Async Listener (Trevor Norris)
+
+* stream: switch _writableState.buffer to queue (Chris Dickinson)
+
+* streams: make setDefaultEncoding() throw (Brian White)
+
+* streams: set default encoding for writable streams (Johnny Ray)
+
+* tls: remove tls.createSecurePair code deprecation (Jackson Tian)
+
+* tls_wrap: ignore ZERO_RETURN after close_notify (Fedor Indutny)
+
+* url: change hostname regex to negate invalid chars (Jonathan Johnson)
+
+* url: fixed encoding for slash switching emulation. (Evan Rutledge Borden)
+
+* url: improve parsing speed (CGavrila)
+
+* url: make query() consistent (Gabriel Wicke)
+
+* url: support `path` for url.format (Yazhong Liu)
+
+* util: add es6 Symbol support for `util.inspect` (gyson)
+
+
+Source Code: https://nodejs.org/dist/v0.11.15/node-v0.11.15.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.15/node-v0.11.15.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.15/node-v0.11.15-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.15/x64/node-v0.11.15-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.15/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.15/node-v0.11.15-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.15/node-v0.11.15-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.15/node-v0.11.15-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.15/node-v0.11.15-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.15/
+
+Website: https://nodejs.org/docs/v0.11.15/
+
+Documentation: https://nodejs.org/docs/v0.11.15/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+5eaa3274e376ad2b92e2a23543951efd4c4139cf  genccode.exe
+27cb2cfb67c92aa6760c1338ab7c34aab5397f36  genccode.pdb
+c5a20b41673283e6f813e7357cd52027a7624f00  genrb.exe
+5f5e15d4139c70a0a430137ee35311d3c2ebb64b  genrb.pdb
+301c0dee7582a340e352d8823c2a49dc9c3c2b7c  iculslocs.exe
+4f5502491ccbe09ac354c05b77c09d74ef2e47fb  iculslocs.pdb
+85fd3ef552fd2ca2e3b2ca4d11f909cd9e952a0c  icupkg.exe
+2d69e816c4209615b6280ae147b0b2f1e36f443d  icupkg.pdb
+bd82a1a110a46264c6a614b36bfafdb26e5ca323  node-v0.11.15-darwin-x64.tar.gz
+0992691dee9dfa2fdb749b4ccc69a536f3dee783  node-v0.11.15-darwin-x86.tar.gz
+edd10d65f2d1fd2d355fc79faa47584344cdc92d  node-v0.11.15-linux-x64.tar.gz
+ee189a6fb39c961a2ed9cb1b093e5ddc2c14b736  node-v0.11.15-linux-x86.tar.gz
+f505231036859d19e145338f6ddbcd34346553af  node-v0.11.15-sunos-x64.tar.gz
+d395682bd993da095b5ca0f917ee692e6ed579b1  node-v0.11.15-sunos-x86.tar.gz
+a7644dbb064bea957254d0f4f934dc6f840977f7  node-v0.11.15-x86.msi
+72374399795101bdcbd5d861ec4f7e8854584141  node-v0.11.15.pkg
+59af71738620c94f07340b9f6276dbd56591e9fb  node-v0.11.15.tar.gz
+f4c5042527ef4e2c49f0ffaa5a739b27a9813fa4  node.exe
+9086161ac68bc196c9e232a67f98ba7c10e57acd  node.exp
+ba37668d856cadbf91e368871aee9cd5b025765f  node.lib
+020a907ff40f4b4f9594ea27540972892d8b7548  node.pdb
+1190d6596676284950f484f463c5bc8bbee2587c  openssl-cli.exe
+aff88e0d020b1706b946dc6d57e5fb6b06296822  openssl-cli.pdb
+1858619cb97551908d69c5ddcba36fd23ea9063f  x64/genccode.exe
+4eefa250fde44a13ebbdb21cb84e59fa1efd77df  x64/genccode.pdb
+268d9e0766b5d999ed37a7604a02a0146e53d09a  x64/genrb.exe
+6acc17c0fbf7f15e1982b0359fdc8578edb12349  x64/genrb.pdb
+06aff6123272fedbb4c7e2a43debb46b7e6a9c98  x64/iculslocs.exe
+2bf92f86776997f6e887738b4cfa1238db1deafb  x64/iculslocs.pdb
+c615fc5fc4e41e3855e136f6af441c981be9507a  x64/icupkg.exe
+ca293fc02e68e58ea5bbbb9d4d989eddacce1b70  x64/icupkg.pdb
+3cb93ecbff3336d26526556d3b77bfcb96c4e4fc  x64/node-v0.11.15-x64.msi
+ef6c5e5d1ea49c0f661a6bcc3fd3a5b2c97e70fa  x64/node.exe
+3cd0d9fe8a7f4d31b6009b528552305c23ac6b8b  x64/node.exp
+15cecbe8d197eb61edf1600583f1f0a4eb671d48  x64/node.lib
+3fb1a15f61aefd807f1187339ab9e7b647e7a6a2  x64/node.pdb
+7cbf49d56d33a659a4a8a22ecc761094e06ac212  x64/openssl-cli.exe
+3c03ad8791bc31f197a5476dbfec2b2a0f29c69b  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJUvufyAAoJEFCjBR+IjGKNDMgP/iSnV72vBSzQ88ixJ6xy+qoF
+pecQmfd+NPm9zDW86TlVnTyNGE/M9xCs3wQsN50dnGcnVNG/oELeC1NiZ139uvRd
+abUFcjwT9iXSAQtAkioaQT0pyaxnEtBu7y99wz0J5bxcsAwNpvtr1jNcJEvJHMkS
+0fdbYGFD5gpPn95j+Cye+8/ZUeyKRdiQCOgE4/KJS3MLqbw1E5lqqYmHpqanhqoD
+UXz40VQ9IRbfi/4E5Fs8N73DMW5JuDIc6Zn+27/Pm+OYPzI3/16UooeeWtQC9W2i
+QjZQYQtSwrzgXXov4rY0HEa2krm9+Kd9tiHhQT3CBaEfQs0s03FbdWxI8jEgAp4k
+kuZzWJix3OkkR+0hfxgYtD6Id1MK9e3ozW2BSCub6To77l7FMzUlOExmR3f/4g54
+E9dC0Sagv4G6lpc7/vSM0rmGmA6iwWBN/feDnGia2SxQESGbBhxS4DxVSZWmTN8u
+Ca029CUAXacKtCN59wyMKOGzEKJfFnyMlGbwAp0tujbdykvsGW4/6Mf5dpYkfEkP
+yMJqGuahvRFnl0pHebIA8eaXaPcp6KRTsv49RHAVWsG10qvUqbQzMe7k8D89smEN
+1X3ijrf+4uNfD+RNBKdmCu1lPhTiOTKpP7XHgWnqw6HTzO7ery4oE04CnFgQ7Ffv
+onofJvSmBRIlesVvJHSk
+=PwEC
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.11.16.md b/locale/uk/blog/release/v0.11.16.md
new file mode 100755
index 0000000000000..a8b4c2fe17357
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.16.md
@@ -0,0 +1,93 @@
+---
+date: 2015-01-30T17:05:17.000Z
+version: 0.11.16
+category: release
+title: Node v0.11.16 (Unstable)
+slug: node-v0-11-16-unstable
+layout: blog-post.hbs
+---
+
+2015.01.29, Version 0.11.16 (Unstable)
+
+* openssl: Upgrade to 1.0.1l
+
+* npm: Upgrade to 2.3.0
+
+* url: revert support of `path` for url.format (Julien Gilli)
+
+* assert: use util.inspect() to create error messages (cjihrig)
+
+* net: throw on invalid socket timeouts (cjihrig)
+
+* url: fix parsing of ssh urls (Evan Lucas)
+
+
+Source Code: https://nodejs.org/dist/v0.11.16/node-v0.11.16.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.16/node-v0.11.16.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.16/node-v0.11.16-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.16/x64/node-v0.11.16-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.16/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.16/node-v0.11.16-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.16/node-v0.11.16-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.16/node-v0.11.16-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.16/node-v0.11.16-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.16/
+
+Website: https://nodejs.org/docs/v0.11.16/
+
+Documentation: https://nodejs.org/docs/v0.11.16/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+ce58cf758cab75ee46dcbe61c4010ffea8ce25ba  node-v0.11.16-darwin-x64.tar.gz
+4b3a4ec8baabb22f8c2d60b56d89c62c7823b213  node-v0.11.16-darwin-x86.tar.gz
+e3b09fc832a3af04cbfcec6329941b5f80eeeb2d  node-v0.11.16-linux-x64.tar.gz
+d470dce6cde5f379c32b251f9f748f5ae3102332  node-v0.11.16-linux-x86.tar.gz
+8ec3178ea5ac7f3513351b9fb8b7bc1e3f8d7914  node-v0.11.16-sunos-x64.tar.gz
+c5b3870760ed1055ac91d6c3a18b3458a065d713  node-v0.11.16-sunos-x86.tar.gz
+3df4ba6b635a7b37d0e7dc56bc5a15bf92a16835  node-v0.11.16-x86.msi
+d2467525fdf2019f54406fde4b060493768cdc65  node-v0.11.16.pkg
+3c3e66773b4eccbe1e5b6da9a7c39a5ead51e155  node-v0.11.16.tar.gz
+63900715b0c375ca514639dc028ce99febc51314  node.exe
+99f9c8542207b52be34d9832a4c311e3376a31e5  node.exp
+e0b6950bb1063686f118a83727a992f08b1a05a6  node.lib
+3035e059b1664195d1a6c7817577f8fc36703548  node.pdb
+753b6e5b08a778a726a5109dfe11a1f7a8276e2c  openssl-cli.exe
+d874143e14c4f93b5e9bd39b4a5f4c07a5492296  openssl-cli.pdb
+30e50735103889bc92a698546caa4de8968c9a6f  x64/node-v0.11.16-x64.msi
+c7e71d54507ee6e4b1119ec13bcbe33ee23e8be7  x64/node.exe
+70e514f9524deb07338d4a529107aa8a6ffd2e1b  x64/node.exp
+24dc180b2848b6e181f3ab192f6c1d3535a1c7ba  x64/node.lib
+7e8515e3e1e0b57ef8a2aa298434fcda0b7d453b  x64/node.pdb
+0b15f0749d95b07ad860d586fd18915e97103ff8  x64/openssl-cli.exe
+d7664f3b528397ff377665dd9f3b2dfaa6b5c4c9  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJUy7m8AAoJEFCjBR+IjGKNgAgQAJGK6z/qc3ZvB02hkMtZI419
+Rypw1Sh++WB/+OGbUO6bfvAEPMM3SSZDDQkoNnGg1DEf+sQziFIqlrb3z2E/dCww
+/GoM+ySfz3lci7G2a+QS/fEsbFwlliSsNv9q3ngZB6M1cxDvhm7/QjO+wlJP056E
+EtiZczmo9AWYAhg8psLy/KH18owGPOs65PmH7mP3Un1bW0J3xxTrOnKktfjSiNNP
+utCpyQzEqJ/LsPaenf5gUNLyyUltXfsPkr4V1gab0pGM/Ic77OhceMOAEw3CIns3
+hvSRpgG+W5IO3+2nvWnX3qEfylcuDcy9ZltPKFLVtbcPXVr9ilW39dJQ0EwXJ/Im
+rRgH2xUEYGye0/lBrRddZ6awHKgSwAGN8JbDId2n93mcgiGzEVfe6BcfRQ7tgOpV
+AXPD+bFd0Eeia7gt63otr/k4aHTaT8P51vKh7lyDsFTvwpaGLzuvO5fTHTRSdoMC
+oynILl7DRPi32f2N1w9Ek54L8N9ZODhxoIXDRCS5Oep2JsbucPqncC7jbiJKjPK2
+OkzKWC0bwVlda0leAaeJrNjNPJSvpSKEk/Vo1Dzl3HcSEmVoRTivYV4vdkwhrkEp
+EPBp3m7iPeNrNKLdibt/16lxNrp67RuIh1gMtIWuu4piuR8+36j1F6LocDmNoOEg
+sqYr4G14o86ztVhqYw/C
+=xcfK
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.11.2.md b/locale/uk/blog/release/v0.11.2.md
new file mode 100755
index 0000000000000..4f0ed5da0daf0
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.2.md
@@ -0,0 +1,90 @@
+---
+date: 2013-05-13T22:53:06.000Z
+version: 0.11.2
+category: release
+title: Node v0.11.2 (Unstable)
+slug: node-v0-11-2-unstable
+layout: blog-post.hbs
+---
+
+2013.05.13, Version 0.11.2 (Unstable)
+
+* uv: Upgrade to 0.11.2
+
+* V8: Upgrade to 3.19.0
+
+* npm: Upgrade to 1.2.21
+
+* build: Makefile should respect configure --prefix (Timothy J Fontaine)
+
+* cluster: use round-robin load balancing (Ben Noordhuis)
+
+* debugger, cluster: each worker has new debug port (Miroslav Bajtoš)
+
+* debugger: `restart` with custom debug port (Miroslav Bajtoš)
+
+* debugger: breakpoints in scripts not loaded yet (Miroslav Bajtoš)
+
+* event: EventEmitter#setMaxListeners() returns this (Sam Roberts)
+
+* events: add EventEmitter.defaultMaxListeners (Ben Noordhuis)
+
+* install: Support $(PREFIX) install target directory prefix (Olof Johansson)
+
+* os: Include netmask in os.networkInterfaces() (Ben Kelly)
+
+* path: add path.isAbsolute(path) (Ryan Doenges)
+
+* stream: Guarantee ordering of 'finish' event (isaacs)
+
+* streams: introduce .cork/.uncork/._writev (Fedor Indutny)
+
+* vm: add support for timeout argument (Andrew Paprocki)
+
+
+Source Code: https://nodejs.org/dist/v0.11.2/node-v0.11.2.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.2/node-v0.11.2.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.2/node-v0.11.2-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.2/x64/node-v0.11.2-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.2/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.2/node-v0.11.2-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.2/node-v0.11.2-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.2/node-v0.11.2-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.2/node-v0.11.2-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.2/
+
+Website: https://nodejs.org/docs/v0.11.2/
+
+Documentation: https://nodejs.org/docs/v0.11.2/api/
+
+Shasums:
+
+```
+ddc85fd6ed70057c64d7c9cd64bb94f28596d163  node-v0.11.2-darwin-x64.tar.gz
+9893a3a3598d2e5ed24bfee8642b72c37808dbae  node-v0.11.2-darwin-x86.tar.gz
+f81189c30aa268f2b43572e1795fedd50f3495c3  node-v0.11.2-linux-x64.tar.gz
+6322bf3be78f907a3b5e06f38af1b33c52957612  node-v0.11.2-linux-x86.tar.gz
+3becca01532e104081ca51a265f07e77b6e9e25f  node-v0.11.2-sunos-x64.tar.gz
+9489238384edb456d9a603e5bef1128dfafe69b1  node-v0.11.2-sunos-x86.tar.gz
+76421e22cff4d4f4d1cb2ce3e3566e2c9004cdee  node-v0.11.2-x86.msi
+a23d607f7b433197533cd6d88c981c75463efff8  node-v0.11.2.pkg
+1d1080598431062ccb4bbbf7ecbb7596fe664c67  node-v0.11.2.tar.gz
+b45a04167d32887c32a2479c4567af394627c8ad  node.exe
+c65ce6e073e173ae5769fe4dd9ff83f2f56ce05d  node.exp
+31f569697cb8447492e3172e614c3c4cfff81d09  node.lib
+c98f8a717ef9d660ff3d45e86e2ee396ca02e721  node.pdb
+7caabd3a774c96a8126f10d2e184727bd5160526  x64/node-v0.11.2-x64.msi
+3b049227e3c392fdb88de9a5da7ad1ec14c82d17  x64/node.exe
+c95f9746e180c064a5225ab83cca604bf918e59a  x64/node.exp
+78c94386c312ded2f7cb0c84951535b67e36fecf  x64/node.lib
+ad774b472a3cfa03374aac2d1dac19f9599ad2f8  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.3.md b/locale/uk/blog/release/v0.11.3.md
new file mode 100755
index 0000000000000..620b60ed893d5
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.3.md
@@ -0,0 +1,104 @@
+---
+date: 2013-06-26T23:55:29.000Z
+version: 0.11.3
+category: release
+title: Node v0.11.3 (Unstable)
+slug: node-v0-11-3-unstable
+layout: blog-post.hbs
+---
+
+2013.06.26, Version 0.11.3 (Unstable)
+
+* uv: Upgrade to v0.11.5
+
+* c-ares: upgrade to 1.10.0
+
+* v8: upgrade to v3.19.13
+
+* punycode: update to v1.2.3 (Mathias Bynens)
+
+* debugger: break on uncaught exception (Miroslav Bajtos)
+
+* child_process: emit 'disconnect' asynchronously (Ben Noordhuis)
+
+* dtrace: enable uv's probes if enabled (Timothy J Fontaine)
+
+* dtrace: unify dtrace and systemtap interfaces (Timothy J Fontaine)
+
+* buffer: New API for backing data store (Trevor Norris)
+
+* buffer: return `this` in fill() for chainability (Brian White)
+
+* build: fix include order for building on windows (Timothy J Fontaine)
+
+* build: add android support (Linus Mårtensson)
+
+* readline: strip ctrl chars for prompt width calc (Krzysztof Chrapka)
+
+* tls: introduce TLSSocket based on tls_wrap binding (Fedor Indutny)
+
+* tls: add localAddress and localPort properties (Ben Noordhuis)
+
+* crypto: free excessive memory in NodeBIO (Fedor Indutny)
+
+* process: remove maxTickDepth (Trevor Norris)
+
+* timers: use uv_now instead of Date.now (Timothy J Fontaine)
+
+* util: Add debuglog, deprecate console lookalikes (isaacs)
+
+* module: use path.sep instead of a custom solution (Robert Kowalski)
+
+* http: don't escape request path, reject bad chars (Ben Noordhuis)
+
+* net: emit dns 'lookup' event before connect (Ben Noordhuis)
+
+* dns: add getServers and setServers (Timothy J Fontaine)
+
+
+Source Code: https://nodejs.org/dist/v0.11.3/node-v0.11.3.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.3/node-v0.11.3.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.3/node-v0.11.3-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.3/x64/node-v0.11.3-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.3/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.3/node-v0.11.3-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.3/node-v0.11.3-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.3/node-v0.11.3-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.3/node-v0.11.3-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.3/
+
+Website: https://nodejs.org/docs/v0.11.3/
+
+Documentation: https://nodejs.org/docs/v0.11.3/api/
+
+Shasums:
+
+```
+8320d6167f4c49d85b42bde41a201dabc125540d  node-v0.11.3-darwin-x64.tar.gz
+df9a540da0f5eb80682b5f63a8f7c841876ae9b2  node-v0.11.3-darwin-x86.tar.gz
+76839ea31e90046c80af088b36c619eae622a6c0  node-v0.11.3-linux-x64.tar.gz
+fd571ebfcdf5d7e35a2fbd972967ac24326ecb39  node-v0.11.3-linux-x86.tar.gz
+85c03b89d61245ddfc911784a358e32a8a801c4f  node-v0.11.3-sunos-x64.tar.gz
+58f7824fdbe8b57e13865630c11100ac920474f9  node-v0.11.3-sunos-x86.tar.gz
+507bbb003c755865f2b9cfc7a656ec9b142624fd  node-v0.11.3-x86.msi
+613ac2e985738ac06859394daf64347594b1e073  node-v0.11.3.pkg
+4b82d58ed3ce38fa67a8484b42cfd47179b6a4a5  node-v0.11.3.tar.gz
+e8628e45ee979ed0e666ff4ddce82444251afc85  node.exe
+e883f3f4b110e78cd11d03848003829fd7377ddb  node.exp
+5e82f6ef29379d8d39fb0661a0533bdbed412432  node.lib
+cc3ee23230b947159282161481491f39f9a36c85  node.pdb
+2f7adfe4cfb69efc5d9f0b94b18787a0e14c3021  x64/node-v0.11.3-x64.msi
+625fd4ab66816e57b08d73853a9438ea9e16f720  x64/node.exe
+dbc8cc48c651b342980b408fdc07da01e6e3e67e  x64/node.exp
+9203d66c50a34c1658928d525d1f1d2eaae9718c  x64/node.lib
+9b1261772868734a7962848e1d1db55efde2bce9  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.4.md b/locale/uk/blog/release/v0.11.4.md
new file mode 100755
index 0000000000000..52a9e4cf16e8d
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.4.md
@@ -0,0 +1,91 @@
+---
+date: 2013-07-12T21:34:13.000Z
+version: 0.11.4
+category: release
+title: Node v0.11.4 (Unstable)
+slug: node-v0-11-4-unstable
+layout: blog-post.hbs
+---
+
+2013.07.12, Version 0.11.4 (Unstable)
+
+* npm: Upgrade to 1.3.4
+
+* v8: Upgrade to v3.20.2
+
+* c-ares: Upgrade to piscisaureus/cares@805d153
+
+* timers: setImmediate process full queue each turn (Ben Noordhuis)
+
+* http: Add agent.get/request methods (isaacs)
+
+* http: Proper KeepAlive behavior (isaacs)
+
+* configure: fix the --without-ssl option (Nathan Rajlich)
+
+* buffer: propagate originating parent (Trevor Norris)
+
+* tls_wrap: return Error not throw for missing cert (Timothy J Fontaine)
+
+* src: enable native v8 typed arrays (Ben Noordhuis)
+
+* stream: objectMode transform should allow falsey values (Jeff Barczewski)
+
+* slab_allocator: remove SlabAllocator (Trevor Norris)
+
+* crypto: fix memory leak in LoadPKCS12 (Fedor Indutny)
+
+* tls: export TLSSocket (Fedor Indutny)
+
+* zlib: allow changing of level and strategy (Brian White)
+
+* zlib: allow custom flush type for flush() (Brian White)
+
+
+Source Code: https://nodejs.org/dist/v0.11.4/node-v0.11.4.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.4/node-v0.11.4.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.4/node-v0.11.4-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.4/x64/node-v0.11.4-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.4/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.4/node-v0.11.4-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.4/node-v0.11.4-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.4/node-v0.11.4-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.4/node-v0.11.4-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.4/
+
+Website: https://nodejs.org/docs/v0.11.4/
+
+Documentation: https://nodejs.org/docs/v0.11.4/api/
+
+Shasums:
+```
+0035d18e2dcf9aad669b1c7c07319e17abfe3762  ./node-v0.11.4.tar.gz
+a7be873e87c6f4721892791a047331018f851986  ./node-v0.11.4.pkg
+fbfcf8a599c765ba924ddbe1ba8c143053b5342e  ./node-v0.11.4-linux-x64.tar.gz
+7df3de8dfb8547ba11e8dec16380ac1ca9978e82  ./node-v0.11.4-linux-x86.tar.gz
+f272e7d87ab9b0baa41b10561d34b3aeadfcd0fa  ./node-v0.11.4-darwin-x86.tar.gz
+7f56d5a7e6b73e22950610ae6c1dd00edd4940bc  ./node-v0.11.4-darwin-x64.tar.gz
+0b919bae82fa7ab9a17bf694fa44080b2612a0d4  ./node-v0.11.4-sunos-x86.tar.gz
+5283e2c1f8a9e51fa864957d1ed28bb1549a7ab9  ./node-v0.11.4-sunos-x64.tar.gz
+50374dcf0932465ce0ac8d124df8ecd34eeea6a1  ./node-v0.11.4-x86.msi
+42a9430e7500d8e4b0a78428594082f5deeab4d6  ./node.pdb
+4eda314346e201890fde54fc55f8db7896cb9288  ./node.exp
+8c1631b168d855fc93a952a8a1a91946d2596278  ./node.exe
+bb76a0d00c3c8c10f8c49c46e7d684b8850ac90a  ./node.lib
+2f2bf4bc58da9be63e9840b113b4d665a6019bad  ./x64/node-v0.11.4-x64.msi
+31273870a763aa55d611a366ade2ca6c39bac2f5  ./x64/node.exp
+a90905f911e2f741c34699c62f28ffab48565559  ./x64/node.pdb
+d325667dcbdf50c92fc8c3034df3808f734179fa  ./x64/node.exe
+9a9a0fc005cf4c09154f3171be74b4153579c6fe  ./x64/node.lib
+0d3f96506def112ff1344f87d7271122412ff899  ./pkgsrc/nodejs-x64-0.11.4.tgz
+28b1eb61fe7b9901a809a137424c4e05bd8f6fa6  ./pkgsrc/nodejs-ia32-0.11.4.tgz
+```
diff --git a/locale/uk/blog/release/v0.11.5.md b/locale/uk/blog/release/v0.11.5.md
new file mode 100755
index 0000000000000..f6332bdfc794e
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.5.md
@@ -0,0 +1,91 @@
+---
+date: 2013-08-07T00:05:46.000Z
+version: 0.11.5
+category: release
+title: Node v0.11.5 (Unstable)
+slug: node-v0-11-5-unstable
+layout: blog-post.hbs
+---
+
+2013.08.06, Version 0.11.5 (Unstable)
+
+* v8: upgrade to 3.20.11
+
+* uv: upgrade to v0.11.7
+
+* buffer: return offset for end of last write (Trevor Norris)
+
+* build: embed the mdb_v8.so into the binary (Timothy J Fontaine)
+
+* build: fix --without-ssl build (Ben Noordhuis)
+
+* child_process: add 'shell' option to .exec() (Ben Noordhuis)
+
+* dgram: report send errors to cb, don't pass bytes (Ben Noordhuis)
+
+* fs: write strings directly to disk (Trevor Norris)
+
+* https: fix default port (Koichi Kobayashi)
+
+* openssl: use asm for sha, md5, rmd (Fedor Indutny)
+
+* os: add mac address to networkInterfaces() output (Brian White)
+
+* smalloc: introduce smalloc module (Trevor Norris)
+
+* stream: Simplify flowing, passive data listening (streams3) (isaacs)
+
+* tls: asynchronous SNICallback (Fedor Indutny)
+
+* tls: share tls tickets key between cluster workers (Fedor Indutny)
+
+* util: don't throw on circular %j input to format() (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.11.5/node-v0.11.5.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.5/node-v0.11.5.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.5/node-v0.11.5-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.5/x64/node-v0.11.5-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.5/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.5/node-v0.11.5-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.5/node-v0.11.5-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.5/node-v0.11.5-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.5/node-v0.11.5-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.5/
+
+Website: https://nodejs.org/docs/v0.11.5/
+
+Documentation: https://nodejs.org/docs/v0.11.5/api/
+
+Shasums:
+```
+a48c7c1ffa0344ab4c7f9b3466ed76d8b7ce4385  node-v0.11.5-darwin-x64.tar.gz
+c18ef8b45a4a6a8afebaa0c43f7388f20c6dee92  node-v0.11.5-darwin-x86.tar.gz
+caa13a498ef32b09c717c86c7b9e5be1feb34a42  node-v0.11.5-linux-x64.tar.gz
+1b55090713d6cb4fadab080f4e50bc5e2b9ee2fe  node-v0.11.5-linux-x86.tar.gz
+7cfc4574dd70517d46856c03751e362e61049d70  node-v0.11.5-sunos-x64.tar.gz
+443e4e51a49e34b5d62b7ead3e0b1079cae05dd9  node-v0.11.5-sunos-x86.tar.gz
+1042917fb1fa5ae8d387f918924a8dcd15f4d6a3  node-v0.11.5-x86.msi
+0e832e2e466c1ffffed1e7ed781fb9366339d053  node-v0.11.5.pkg
+5cd49ac41bb6929a43aaf77037d051fe794e5ad3  node-v0.11.5.tar.gz
+432da8b8e801ec8660ddbeb73524fc8cb74da8ea  node.exe
+1d724ca5211148180ba0154575648edd758ec2c8  node.exp
+ef12c19e95e671debfa96afe3496afbb8f16283d  node.lib
+12fefe001a90260ca6e403aa27d770611d2bdd51  node.pdb
+96e15938a6845895cde1ca6db64ba86350bd4d06  pkgsrc/nodejs-ia32-0.11.5.tgz
+960ade5a3cf7ac7b1b35755f204e9adfb784cc4a  pkgsrc/nodejs-x64-0.11.5.tgz
+151ab6ffe45d84918edd9c95bda378fdefe170b8  x64/node-v0.11.5-x64.msi
+c2b0f6130539a6ad22206308050b34a44026ce26  x64/node.exe
+89c631942ec57e30165ddbb637da0100493c3f7b  x64/node.exp
+719b857474a8e3eb7269778414d7af2aee855ede  x64/node.lib
+f2eebec1949f4d7da59d3a2135207ac4c2fe0161  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.6.md b/locale/uk/blog/release/v0.11.6.md
new file mode 100755
index 0000000000000..014e4141252e4
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.6.md
@@ -0,0 +1,113 @@
+---
+date: 2013-08-21T21:11:09.000Z
+version: 0.11.6
+category: release
+title: Node v0.11.6 (Unstable)
+slug: node-v0-11-6-unstable
+layout: blog-post.hbs
+---
+
+2013.08.21, Version 0.11.6 (Unstable)
+
+* uv: Upgrade to v0.11.8
+
+* v8: upgrade v8 to 3.20.14.1
+
+* build: disable SSLv2 by default (Ben Noordhuis)
+
+* build: don't auto-destroy existing configuration (Ben Noordhuis)
+
+* crypto: add TLS 1.1 and 1.2 to secureProtocol list (Matthias Bartelmeß)
+
+* crypto: fix memory leak in randomBytes() error path (Ben Noordhuis)
+
+* dgram: don't call into js when send cb is omitted (Ben Noordhuis)
+
+* dgram: fix regression in string argument handling (Ben Noordhuis)
+
+* domains: performance improvements (Trevor Norris)
+
+* events: EventEmitter = require('events') (Jake Verbaten)
+
+* http: Add write()/end() callbacks (isaacs)
+
+* http: Consistent 'finish' event semantics (isaacs)
+
+* http: Prefer 'binary' over 'ascii' (isaacs)
+
+* http: Support legacy agent.addRequest API (isaacs)
+
+* http: Write hex/base64 chunks properly (isaacs)
+
+* http: add agent.maxFreeSockets option (isaacs)
+
+* http: provide access to raw headers/trailers (isaacs)
+
+* http: removed headers stay removed (James Halliday)
+
+* http,timers: improve callback performance (Ben Noordhuis)
+
+* net: family option in net.connect (Vsevolod Strukchinsky)
+
+* readline: pause stdin before turning off terminal raw mode (Daniel Chatfield)
+
+* smalloc: allow different external array types (Trevor Norris)
+
+* smalloc: expose ExternalArraySize (Trevor Norris)
+
+* stream: Short-circuit buffer pushes when flowing (isaacs)
+
+* tls: handle errors on socket before releasing it (Fedor Indutny)
+
+* util: fix isPrimitive check (Trevor Norris)
+
+* util: isObject should always return boolean (Trevor Norris)
+
+
+Source Code: https://nodejs.org/dist/v0.11.6/node-v0.11.6.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.6/node-v0.11.6.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.6/node-v0.11.6-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.6/x64/node-v0.11.6-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.6/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.6/node-v0.11.6-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.6/node-v0.11.6-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.6/node-v0.11.6-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.6/node-v0.11.6-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.6/
+
+Website: https://nodejs.org/docs/v0.11.6/
+
+Documentation: https://nodejs.org/docs/v0.11.6/api/
+
+Shasums:
+```
+5bab906e0ec1d5d2c2a750f17253955ba8c590b1  ./node-v0.11.6-darwin-x64.tar.gz
+085a4ecf18ec3200e6e8bd140b3dc7f9fa65f8b5  ./node-v0.11.6-darwin-x86.tar.gz
+c162932132977820e06b856ba9cc84c7d4b57749  ./node-v0.11.6-linux-x64.tar.gz
+ed188f465c62da99d870bf8fa17fbd0d543d8d2e  ./node-v0.11.6-linux-x86.tar.gz
+0f52a91353d2c51b4d59c07b2a3b5d2e26060c93  ./node-v0.11.6-sunos-x64.tar.gz
+eac97868a552eae2dad92d633d0b78e069d05bed  ./node-v0.11.6-sunos-x86.tar.gz
+3bdcfd9305fca8bc81197c53c5aff4c4a0745966  ./node-v0.11.6-x86.msi
+92abb4a4cc83bf9d3f1ed2f86a8aecd19672e7cf  ./node-v0.11.6.pkg
+4f3a643b4913ef085175aef180c3bfd9259a4357  ./node-v0.11.6.tar.gz
+8051915c27eaee334a3d89a32fe1593e2b01182b  ./node.exe
+29f62a9272ae7679118f4a21c536eb2384fa3af4  ./node.exp
+dc060de643dec7f17a696c533d9443bfdf25ee61  ./node.lib
+6438410f3685c585379e44b8bf39240ff0e65175  ./node.pdb
+dddfd481d376a215f0e039143ff1d22b317ca1d3  ./pkgsrc/nodejs-ia32-0.11.6.tgz
+634c9249428fde318e9087eebc9d50401c110521  ./pkgsrc/nodejs-x64-0.11.6.tgz
+90b58cb39a655591c240388942b629ff725fb076  ./x64/node-v0.11.6-x64.msi
+faeda12db9ca90a89dbd1d131702be39a883e7a2  ./x64/node.exe
+d6ab6da893cefd30795163a4e0d5585a996f13ec  ./x64/node.exp
+f8f598114199b8876ef2cf7414eee488fcf713b9  ./x64/node.lib
+e09f49b3d3b881f2c3dcdff24369176572cc7338  ./x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.7.md b/locale/uk/blog/release/v0.11.7.md
new file mode 100755
index 0000000000000..d28f2920215ce
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.7.md
@@ -0,0 +1,95 @@
+---
+date: 2013-09-04T22:18:08.000Z
+version: 0.11.7
+category: release
+title: Node v0.11.7 (Unstable)
+slug: node-v0-11-7-unstable
+layout: blog-post.hbs
+---
+
+2013.08.21, Version 0.11.7 (Unstable)
+
+* uv: upgrade to v0.11.13
+
+* v8: upgrade to 3.20.17
+
+* buffer: adhere to INSPECT_MAX_BYTES (Timothy J Fontaine)
+
+* buffer: fix regression for large buffer creation (Trevor Norris)
+
+* buffer: don't throw if slice length too long (Trevor Norris)
+
+* buffer: Buffer(buf) constructor copies into the proper buffer (Ben Noordhuis)
+
+* cli: remove --max-stack-size (Ben Noordhuis)
+
+* cli: unknown command line options are errors (Ben Noordhuis)
+
+* child_process: exec accept buffer as an encoding (Seth Fitzsimmons)
+
+* crypto: make randomBytes/pbkdf2 callbacks domain aware (Ben Noordhuis)
+
+* domain: deprecate domain.dispose(). (Forrest L Norvell)
+
+* fs: Expose birthtime on stat objects (isaacs)
+
+* http: Only send connection:keep-alive if necessary (isaacs)
+
+* repl: Catch syntax errors better (isaacs, Nathan Rajlich)
+
+* stream: change default highWaterMark for objectMode to 16 (Mathias Buus)
+
+* stream: make setEncoding/pause/resume chainable (Julian Gruber, isaacs)
+
+* util: pass opts to custom inspect functions (Timothy J Fontaine)
+
+* vm: rewritten to behave like Contextify (Domenic Denicola)
+
+
+Source Code: https://nodejs.org/dist/v0.11.7/node-v0.11.7.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.7/node-v0.11.7.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.7/node-v0.11.7-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.7/x64/node-v0.11.7-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.7/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.7/node-v0.11.7-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.7/node-v0.11.7-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.7/node-v0.11.7-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.7/node-v0.11.7-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.7/
+
+Website: https://nodejs.org/docs/v0.11.7/
+
+Documentation: https://nodejs.org/docs/v0.11.7/api/
+
+Shasums:
+```
+7ce3cf1297b6a8cda2aa134424890dcc6eaacc12  node-v0.11.7-darwin-x64.tar.gz
+183b4a29eb65dabb5de732f2ab15cdac8c5e5c94  node-v0.11.7-darwin-x86.tar.gz
+7d39c046388e7ec6bb2d53a575a0c9ed1d4a9bcc  node-v0.11.7-linux-x64.tar.gz
+4cf9a367b614b76722324ec6a3beb3295412100c  node-v0.11.7-linux-x86.tar.gz
+1d98fa4117f3ac7c7f081eea22a016c8549b27c1  node-v0.11.7-sunos-x64.tar.gz
+9c04eb5ca9485370d757b0be94b223b5a0180b7a  node-v0.11.7-sunos-x86.tar.gz
+f131bca701ad9dac61d8929362a3c8cde41845de  node-v0.11.7-x86.msi
+95c1ab2d08f3ba1bb514469ad8786af6ecb18f57  node-v0.11.7.pkg
+a3b0d7fb818754ad55f06a02745d7ec53986de64  node-v0.11.7.tar.gz
+33371cadab85e7c3864d5eafae4041a9ca0f3ca2  node.exe
+823487bfaa44f10770ecc9c8deec1bbe63bc955e  node.exp
+194c286bf8ef6608a891dc2c27cd38471da780a3  node.lib
+0491c4e8d45fe420cc065be4de05dbcff0d4223a  node.pdb
+d8b2d7e034d6031c083fb3c88c251f179b18b4ca  pkgsrc/nodejs-ia32-0.11.7.tgz
+a9e7822718212a22b5630057efcba174041db9ff  pkgsrc/nodejs-x64-0.11.7.tgz
+44e7eeafb0982f81778a15ece00c8f25cc4d00f5  x64/node-v0.11.7-x64.msi
+88067c4d19af87f5645a3f8bc81ec7d1610580de  x64/node.exe
+d150573f7567a0da4418d5086410fecabcc1fae8  x64/node.exp
+e0482e1cca25faacaa1111e2de647025bca5e7f5  x64/node.lib
+e9a87b9b7aa1ff220ce4b4b5cb0758c9071c8ce2  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.8.md b/locale/uk/blog/release/v0.11.8.md
new file mode 100755
index 0000000000000..ddcd0ad210801
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.8.md
@@ -0,0 +1,99 @@
+---
+date: 2013-10-30T15:54:47.000Z
+version: 0.11.8
+category: release
+title: Node v0.11.8 (Unstable)
+slug: node-v0-11-8-unstable
+layout: blog-post.hbs
+---
+
+2013.10.30, Version 0.11.8 (Unstable)
+
+* uv: Upgrade to v0.11.14
+
+* v8: upgrade 3.21.18.3
+
+* assert: indicate if exception message is generated (Glen Mailer)
+
+* buffer: add buf.toArrayBuffer() API (Trevor Norris)
+
+* cluster: fix premature 'disconnect' event (Ben Noordhuis)
+
+* crypto: add SPKAC support (Jason Gerfen)
+
+* debugger: count space for line numbers correctly (Alex Kocharin)
+
+* debugger: make busy loops SIGUSR1-interruptible (Ben Noordhuis)
+
+* debugger: repeat last command (Alex Kocharin)
+
+* debugger: show current line, fix for #6150 (Alex Kocharin)
+
+* dgram: send() can accept strings (Trevor Norris)
+
+* dns: rename domain to hostname (Ben Noordhuis)
+
+* dns: set hostname property on error object (Ben Noordhuis)
+
+* dtrace, mdb_v8: support more string, frame types (Dave Pacheco)
+
+* http: add statusMessage (Patrik Stutz)
+
+* http: expose supported methods (Ben Noordhuis)
+
+* http: provide backpressure for pipeline flood (isaacs)
+
+* process: Add exitCode property (isaacs)
+
+* tls: socket.renegotiate(options, callback) (Fedor Indutny)
+
+* util: format as Error if instanceof Error (Rod Vagg)
+
+
+Source Code: https://nodejs.org/dist/v0.11.8/node-v0.11.8.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.8/node-v0.11.8.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.8/node-v0.11.8-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.8/x64/node-v0.11.8-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.8/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.8/node-v0.11.8-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.8/node-v0.11.8-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.8/node-v0.11.8-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.8/node-v0.11.8-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.8/
+
+Website: https://nodejs.org/docs/v0.11.8/
+
+Documentation: https://nodejs.org/docs/v0.11.8/api/
+
+Shasums:
+```
+1911bc1407fd116318edaa0cfd01bd664b2b352c  node-v0.11.8-darwin-x64.tar.gz
+bac43c31e257e9f2deffb08c4154f522d5925825  node-v0.11.8-darwin-x86.tar.gz
+1b2dac1788f3aad51ec643854ae57771792e6647  node-v0.11.8-linux-x64.tar.gz
+1f674dd1ac15561dbf99ecf80d00e2cfcdc1a23b  node-v0.11.8-linux-x86.tar.gz
+51d29f3624b18e75cf5736eedd62a55931551251  node-v0.11.8-sunos-x64.tar.gz
+b995b05a3b14373c61faf4cd5c05157e06f410c8  node-v0.11.8-sunos-x86.tar.gz
+5f6fd1f68d9f61c889c7a0148a6bfbb681a119b5  node-v0.11.8-x86.msi
+95097ea074fa1b20c3bd46eae33a24935842149b  node-v0.11.8.pkg
+21d3927c78adaaf3fe7cc9602ffb0a85de7f6ea0  node-v0.11.8.tar.gz
+f735cf8b6404428087ba759dc21818b4d968e2ba  node.exe
+c632e716ac2b303a4e2f3e0c81819b4020c9e0df  node.exp
+dea16a4911693689c3981e19ae2fa77ea2884797  node.lib
+0a5bfce12045512b1f4a0341d1381459e9731321  node.pdb
+25b8d468c1ef53332834a46aaae0ee1820771871  pkgsrc/nodejs-ia32-0.11.8.tgz
+fb16a45a0a467aa7661048a3d00d4e81c35bbf56  pkgsrc/nodejs-x64-0.11.8.tgz
+b4b2c453404f5aa0d37fbce5d55ac1e030f3e7cc  x64/node-v0.11.8-x64.msi
+799da7eb400d91b7eec157d25da0e138630f27e4  x64/node.exe
+6482cce41d8a98ba55daaccc581929df018f2edf  x64/node.exp
+7e2bb85b6ca45c4df487b9cca7d420e87170b272  x64/node.lib
+1aa3a1f9d767e81dbdd1af1d13f221830c467d68  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.11.9.md b/locale/uk/blog/release/v0.11.9.md
new file mode 100755
index 0000000000000..99b880c1dae3a
--- /dev/null
+++ b/locale/uk/blog/release/v0.11.9.md
@@ -0,0 +1,95 @@
+---
+date: 2013-11-21T00:40:35.000Z
+version: 0.11.9
+category: release
+title: Node v0.11.9 (Unstable)
+slug: node-v0-11-9-unstable
+layout: blog-post.hbs
+---
+
+2013.11.20, Version 0.11.9 (Unstable)
+
+* uv: upgrade to v0.11.15 (Timothy J Fontaine)
+
+* v8: upgrade to 3.22.24.5 (Timothy J Fontaine)
+
+* buffer: remove warning when no encoding is passed (Trevor Norris)
+
+* build: make v8 use random seed for hash tables (Ben Noordhuis)
+
+* crypto: build with shared openssl without NPN (Ben Noordhuis)
+
+* crypto: update root certificates (Ben Noordhuis)
+
+* debugger: pass on v8 debug switches (Ben Noordhuis)
+
+* domain: use AsyncListener API (Trevor Norris)
+
+* fs: add recursive subdirectory support to fs.watch (Nick Simmons)
+
+* fs: make fs.watch() non-recursive by default (Ben Noordhuis)
+
+* http: cleanup freeSockets when socket destroyed (fengmk2)
+
+* http: force socket encoding to be null (isaacs)
+
+* http: make DELETE requests set `req.method` (Nathan Rajlich)
+
+* node: add AsyncListener support (Trevor Norris)
+
+* src: remove global HandleScope that hid memory leaks (Ben Noordhuis)
+
+* tls: add ECDH ciphers support (Erik Dubbelboer)
+
+* tls: do not default to 'localhost' servername (Fedor Indutny)
+
+* tls: more accurate wrapping of connecting socket (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.11.9/node-v0.11.9.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.11.9/node-v0.11.9.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.11.9/node-v0.11.9-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.11.9/x64/node-v0.11.9-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.11.9/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.11.9/node-v0.11.9-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.11.9/node-v0.11.9-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.11.9/node-v0.11.9-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.11.9/node-v0.11.9-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.11.9/
+
+Website: https://nodejs.org/docs/v0.11.9/
+
+Documentation: https://nodejs.org/docs/v0.11.9/api/
+
+Shasums:
+```
+3a1af0d716042d617e51a82b43b2f97542f6c03a  node-v0.11.9-darwin-x64.tar.gz
+580696c5b2f30c8394cdee265c4888ad67e03b89  node-v0.11.9-darwin-x86.tar.gz
+585df0690254afc22b29d7dc5f12fcb50f1bb588  node-v0.11.9-linux-x64.tar.gz
+16fb7e69b90b6b6ac84a9120202918f197d4c0c0  node-v0.11.9-linux-x86.tar.gz
+bff51e2ab3752f4ae338adca14c2c453294e6017  node-v0.11.9-sunos-x64.tar.gz
+9a7ada5c862174d6ce4b524d5816e26a36b763a8  node-v0.11.9-sunos-x86.tar.gz
+3a4de2ae0dd8268592546b4fdcbd78f1cbc68118  node-v0.11.9-x86.msi
+8c70de5cd39ecd33e6c02d4b0f6ca4010d21372e  node-v0.11.9.pkg
+b4fc0e38ccde4edae45db198f331499055d77ca2  node-v0.11.9.tar.gz
+9a4b04f0d40251696fac9161567e97c228d4e57d  node.exe
+96bfa67a417599c96818461d6d27f50401a74a36  node.exp
+5f56ef7c2204ea75916876f6ab9e641b312dff11  node.lib
+2db6eb844b36d96a0e34370ad1d311a57facd3d6  node.pdb
+4a3590db0e6131739661628632ae1b8d70e2247b  pkgsrc/nodejs-ia32-0.11.9.tgz
+3ce0291cf0972ac5a2c0543fd1672d8b20569891  pkgsrc/nodejs-x64-0.11.9.tgz
+9b736ec896e6b1b5856730869471c7e736f6ce78  x64/node-v0.11.9-x64.msi
+1ec3593262b6e281457748ff3f3f195cd682592d  x64/node.exe
+1cf9ba6d503d5f8b18bfc2c1554bce04eba8a536  x64/node.exp
+0a3e79ceecd05add6dab97bb6d9f460a61adddbc  x64/node.lib
+2037b32bbcb14e24d10c6cb2abe128bc9a85a932  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.12.0.md b/locale/uk/blog/release/v0.12.0.md
new file mode 100755
index 0000000000000..d4d82311be496
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.0.md
@@ -0,0 +1,184 @@
+---
+date: 2015-02-06T22:03:56.000Z
+version: 0.12.0
+category: release
+title: Node v0.12.0 (Stable)
+slug: node-v0-12-0-stable
+layout: blog-post.hbs
+---
+
+We are excited to announce the availability of Node.js v0.12! It has been a
+long process, and we want to thank contributors and all of the community who
+waited patiently for this event. Node.js has such a vibrant and enthusiastic
+community, and we're very lucky to have you all supporting us.
+
+Node.js has seen many changes between v0.10 and v0.12. There is [a listing of
+changes documented on the wiki](https://github.com/joyent/node/wiki/API-changes-between-v0.10-and-v0.12). Note that this release includes API updates
+that may require dependency updates. Following are some highlights:
+
+ * Streams 3
+  - The Streams implementation now works the way you thought it already should,
+  without introducing any changes to the API. Basically this means no more
+  getting stuck in "old mode", there are only streams that are flowing or not.
+  - Streams now support the use of cork and uncork mechanisms to prevent
+  flushing writes out to the system if an application is going to be
+  performing many writes in a row. There is an implicit uncork performed when
+  you end a writable stream.
+ * HTTP
+  - `maxSockets` are no longer limited to 5. The default is now set to
+  `Infinity` with the developer and the operating system given control over
+  how many simultaneous connections an application can keep open to a given
+  host.
+  - Proper KeepAlive support means that sockets will stay open until they
+  timeout at the configured time, are closed by the remote side, or the
+  process exits. Developer's no longer have to make sure requests have been
+  pipelined to keep the socket open, or use an alternative module to get that
+  support.
+  - Developers can also now explicitly `flushHeaders` to ensure time to first
+  byte is low and proxied connections are held open.
+ * Cluster
+  - Now has two modes of operation, the new default is a round robin
+  distribution mechanism where the master accepts new connections and
+  distributes them to your workers. If you want you can still opt back into
+  the old method where your workers are responsible for acception connections.
+ * TLS
+  - We have the new TLSWrap mechanism under the hood, this eliminates quite a
+  few of the hops back and forth between JavaScript and our C++
+  implementations.
+  - Added APIs for asynchronous SNI callbacks, OCSP stapling, and storage
+  events.
+ * Buffer
+  - We use a more accurate mechanism for allocating memory for buffers now,
+  which means you'll see less overhead and impact from holding onto to small
+  slices of Buffers. This reduces the amount of memory pressure on the system,
+  which means GC runs are quicker, which means Node.js is on CPU less, and
+  thus lower latency for your applications.
+ * child_process
+  - `spawnSync`/`execSync` have been added to facilitate synchronous child
+  processes, warning your node process won't make forward progress while
+  waiting for the child to exit, caveat emptor!
+ * Crypto
+  - Added APIs for loading custom engines for use with compiled in OpenSSL.
+  - More APIs support supplying the pass phrases.
+  - Added APIs for RSA public/private key encryption/decryption.
+ * VM
+  - The module is now based on the Contextify module, which shares values from
+  the sandbox to avoid missing changes inside the execution from appearing in
+  the parent context.
+ * Initial support for [ECMAScript Internationalization API 1.0
+ (ECMA-402)](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl)
+  - By default, Node.js v0.12.0 binaries are shipped with ECMA-402 support,
+  but only for the English language. In other words, the ECMA-402 API is
+  working as you would expect, but only data for the English language is
+  included. You can find more info on how to include more languages [in
+  the Wiki](https://github.com/joyent/node/wiki/Intl).
+
+These are just *some* of the changes you can find in this release of v0.12,
+and it's thanks to the hard work of the community and the members of team
+curating Node.js.
+
+We are also pleased to report that this release of Node.js has tests passing
+on all of our supported platforms. On the one hand, this seems obvious (what
+are tests for if not to verify before you release it?!), but this is actually
+the first release of Node.js that has operated under this constraint.
+Requiring that all tests pass before releasing Node.js marks an important
+development for the project, and is essential for building a solid path moving
+forward.
+
+We'll obviously be spending a couple weeks firefighting any immediate issues
+for v0.12, but the team is excited to start pulling in the items and
+discussing what the roadmap will look like next for Node.js. We want to make
+sure we're scoping future versions of Node.js so we can have confidence in
+knowing we're on the right path and that we're ready to release based on the
+standards we have set for ourselves.
+
+Quite a few members of the team will be attending
+[NodeSummit](http://nodesummit.com) February 9th through the 11th in San
+Francisco. If you're around for that event please make sure to find us and
+give us feedback on what you would like to see from Node.js.
+
+Source Code: https://nodejs.org/dist/v0.12.0/node-v0.12.0.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.0/node-v0.12.0.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.0/node-v0.12.0-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.0/x64/node-v0.12.0-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.0/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.0/node-v0.12.0-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.0/node-v0.12.0-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.0/node-v0.12.0-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.0/node-v0.12.0-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.0/
+
+Website: https://nodejs.org/docs/v0.12.0/
+
+Documentation: https://nodejs.org/docs/v0.12.0/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+4f53a1dac68057d700964707adb5e54302969dab  genccode.exe
+146930a2bdb88a3e12cb8d3a359e7197bbbde695  genccode.pdb
+6ec82639faae028e5d9c90e123f7220e7e915187  genrb.exe
+817c5b18f4cd8d2eed80815fc030a1342b4f88cd  genrb.pdb
+151036790bd98204764d302f3df2ab2685db6f54  iculslocs.exe
+228a3dcf968f6c552788fafc1ef84baee3e7450e  iculslocs.pdb
+8665404bb5cf3e730ba633c5b8184250bae1cafd  icupkg.exe
+819de4c86d0aad67cf62e5f4913910f1112ef1c9  icupkg.pdb
+596eff06fefc11ef10f345ea37e7e05f72533c67  node-v0.12.0-darwin-x64.tar.gz
+dddd5306a0c7e551aae8a8685b365f8c25a9d63a  node-v0.12.0-darwin-x86.tar.gz
+64fb5260a4a0f914b62a80066d7955856a04703a  node-v0.12.0-linux-x64.tar.gz
+765cb24d17625221ecdd8518907c265b99ce18d2  node-v0.12.0-linux-x86.tar.gz
+6964fe9bd299eea2844e0dc0bb6f5cae70e1f03c  node-v0.12.0-sunos-x64.tar.gz
+3988db298cfe614370481ab5abba3bd83b65570f  node-v0.12.0-sunos-x86.tar.gz
+20d936afd83f819c92826afdc87815a3c96884d2  node-v0.12.0-x86.msi
+8879163ab75f611abb49e250f3158c6a98e37d25  node-v0.12.0.pkg
+d08810034d170c19759cb38bfc9442ab6b0ebc7a  node-v0.12.0.tar.gz
+c54021b701cebc3ba713c920531ca4fdc96cf9fe  node.exe
+cce4bba695a8d4953977b3bf5193a9f16b24e003  node.exp
+4983bf4ef56b1af2e5e9db9e67c62250b5455016  node.lib
+ffa621154420292dcdd39cc4bd91a5e08bc5f622  node.pdb
+05bbc6228fb49005b2fd0858544d0dc42e6b6f0c  openssl-cli.exe
+0bd5916cbadeab0f5995728142279049e6e9d866  openssl-cli.pdb
+84bce5da7c5cc563d224d0d80e05a9c9fc3614b2  x64/genccode.exe
+9bc57d86caba460d6b0dc864db832956cf68096c  x64/genccode.pdb
+4ae96a5ec2619f9cd60e127cb4ad9e0147dcf58c  x64/genrb.exe
+4ff14345e733f266ed86679e88e8461825bc0c2d  x64/genrb.pdb
+4ba7525312c7e7d1d489f89af8d9b98d743d2397  x64/iculslocs.exe
+1a2cebefcaee90e81be67bc079b48a37b5a7f63a  x64/iculslocs.pdb
+251d768eba9543da5ae9a8d5617c9fc58069d413  x64/icupkg.exe
+f4647ad8db148b89475634000e0c0cd7f8f47b04  x64/icupkg.pdb
+a34650db220cb1886bb497edb72474e83a4dbe77  x64/node-v0.12.0-x64.msi
+71cf52c0ff9e1457364962697fb8798925241828  x64/node.exe
+dbd4614bf15b037c0ed2cb631bad0282e420c3ff  x64/node.exp
+709ff6f74f10b184e09c45e893a77248455fb452  x64/node.lib
+e14399d9cc5df344e6c4dd557ec2a8c62973b6d3  x64/node.pdb
+a014b76f8c36768a15532ccb5e8d5e904bc4dbb0  x64/openssl-cli.exe
+0827c6819bc7a2b100f14ffbe0b431e955c73b89  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJU1To8AAoJEFCjBR+IjGKNPIQQAJOepQMZctwstD1iiUcrKRo4
+iZMgdHUe4bcBcGfkeB2X8RD4WYIoYxfL/6EF7IfjapiQc8W3Zo1IlTQqRFR1RqRz
+HayhDQu5qPSE6EygT0le6eFbVsn7V1SdP+91umZ+kJVlUal0Li0ZWzSs94iFaok/
+SBgV92WegQBzGwYTxHa/tN2nJ8xkSJDSaqxmiavj+5Ve2phOuKo+vxYnP9viXIT4
+MsohnZyovm4BaOg/DWj8Jn5X42SVzhEiLDjZQxxku64IzjZPjflsYbuBIM8hMnb8
+FwIp92Cp48qsm/l4EX8PN6FLoXo+M82kT3i4rY2XLl7MxwUv4jrh4LTTHG+pPi9X
+LEu58em/xgp/IN+cobc4vs5yWKB98FQNOL+F6ketqyLQwfyr20kDuovcNqiuJX5V
+SIaeU7qyykFoj2qERU0Mk1v0FgLUTjlwwH5h9IcjagV4JFywcIJiNriibz/Ta6rA
+d2KzKyva3rnj4eL4Wa4F9yyLCX9j3sWCE/ZMuVb2NJnYl7RPgr3M+PEcMQVJbdUx
+b1lz+Yyo+NuXUXR9j9OtXscXVrSa8Bqxtc3heXajDzWbGdU8ZPW3DhULtQcPFAth
+DLolLXEcJn6QOQSC06Y+D3LZ3jJbSX0jGb6bvQLksRkPltSSI5VgHSBjlGGkyEVt
+UpmTqbfBdzs1UfeGwL6N
+=nSHJ
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.1.md b/locale/uk/blog/release/v0.12.1.md
new file mode 100755
index 0000000000000..55e0514fbd209
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.1.md
@@ -0,0 +1,87 @@
+---
+date: 2015-03-24T02:45:44.000Z
+version: 0.12.1
+category: release
+title: Node v0.12.1 (Stable)
+slug: node-v0-12-1-stable
+layout: blog-post.hbs
+---
+
+This release upgrades OpenSSL to version 1.0.1m, which includes fixes for
+[several CVEs that were disclosed
+recently](https://www.openssl.org/news/secadv_20150319.txt).
+
+2015.03.23, Version 0.12.1 (Stable)
+
+* openssl: upgrade to 1.0.1m (Addressing multiple CVES)
+
+
+Source Code: https://nodejs.org/dist/v0.12.1/node-v0.12.1.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.1/node-v0.12.1.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.1/node-v0.12.1-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.1/x64/node-v0.12.1-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.1/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.1/node-v0.12.1-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.1/node-v0.12.1-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.1/node-v0.12.1-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.1/node-v0.12.1-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.1/
+
+Website: https://nodejs.org/docs/v0.12.1/
+
+Documentation: https://nodejs.org/docs/v0.12.1/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+3ca64f6895fcb345ebbb89a23bee5ac2bb9eb633  node-v0.12.1-darwin-x64.tar.gz
+0915abf1956014ad5db6b9645ccafdb87c65ade2  node-v0.12.1-darwin-x86.tar.gz
+79880ff2bc95a674bd0701a6dd4ed38f8366db27  node-v0.12.1-linux-x64.tar.gz
+1faad9bf54724934b0cd047d29fe521a26aa4323  node-v0.12.1-linux-x86.tar.gz
+05c7abc865d84c350eab0a1e0a0d6e26ba64a60d  node-v0.12.1-sunos-x64.tar.gz
+bc2d34d2ae3ebd4b12d207c39bc9b9b0e6d8e93d  node-v0.12.1-sunos-x86.tar.gz
+1c93cd3f14fad40b4bb8e8656b5ffd98504ea2a2  node-v0.12.1-x86.msi
+bfad329e12205a60fdf47434224aab5e8ef6ad60  node-v0.12.1.pkg
+9b544043d78af7a41e41092b9d550dd412dfb461  node-v0.12.1.tar.gz
+d8dbc104cfb7c2516ca75294316986760cf62f67  node.exe
+566e9a77711a2102fa498bc8a488f80032707d13  node.exp
+8216848e37c6db01779603168e7a1aff3c6a62aa  node.lib
+9caaefaf2f412a26b66472e35058ca61a2aba3bd  node.pdb
+5bcae5ce9d3a7f3fb5787261b14375691a7270c6  openssl-cli.exe
+61085ef9411e7a60cdf7365994e722a952f2d9c5  openssl-cli.pdb
+2ba47a75e8f8cf118c0564641449bface77ed07f  x64/node-v0.12.1-x64.msi
+a1565f6e11d0eeb305b7537eaa2f415440674167  x64/node.exe
+b9eda020ce16e5b772d395b3fe031e5fe3cfcd92  x64/node.exp
+14af74ac1de04dcaed580479e2ce674d6ff48316  x64/node.lib
+64a9ce8a60e3f9450e95fb4196103a67d92776d9  x64/node.pdb
+edc781c1d327d750c2fd7586e3d55a44304f02bd  x64/openssl-cli.exe
+991b40e4280dcb414ff6c5573890ecc0dea48e73  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVEM/HAAoJEFCjBR+IjGKNQ5AP/RKV0YhN+Wm4d9abBPZuJQAm
+tlwwEqXs8XNyFy3Ap7j0ZTnoGKTAFrcekTOFraGBMNhUVeJN2626mE0kIPAf32Ot
+8lb0xuEdqcKBlgOOdz2UivJebGZagKfqES3feqp2BSQXVn+fDHEYDvaDRZyc0ybW
+PJ2+Ro+S7+Tso3kn1kViBiNXTJgR2FoXMSpo45qvXesIm7lctOeULoAcEmttNUsc
+du+xDN2Xn5PSNtoga12kWwubpyB3A2xeL7Xuim9+jZfcERgunAUFqYBryf7h9ejZ
+iqMQkj6EIPq/9yWK8Gjkszbi8xTn/cSxqcADM9TPjLMnqwHallFe/0vEKkYmr8KO
+YwzKW51Y/qp66J5PdXynmyh5o9mGcXNws03fan5gp5KTjQGtNmIj7TsUAz1AsWvt
+E1A7w26pUAc9Spb21oVgtJiJVceVL+lSYe9JKefPySCl45TbU/cKegbhd0xJMmp+
+LvgYuefWOYszW0UhzxWqNZ84CPatAZSSm74nP+hcinvh4UYXI0RaZmyNAk4a8p25
+4COamjrA3KSDFBsjVxhYv25JAruEeKvqPvoe+gyuJiBSEWOY7Q4/TwiZiQb5/fQq
+5wPkMzH/SeAtGutNvfjfrfkc5IEL0luYbpphLAz5eZHcGFgkq13BauBiTuOn+Ay/
+DNawF60FJ2KhPAMMZZ2u
+=4n9M
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.10.md b/locale/uk/blog/release/v0.12.10.md
new file mode 100755
index 0000000000000..e333b0f72adcd
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.10.md
@@ -0,0 +1,101 @@
+---
+date: 2016-02-09T17:33:00.212Z
+version: 0.12.10
+category: release
+title: Node v0.12.10 (LTS)
+slug: node-v0-12-10
+layout: blog-post.hbs
+author: James M Snell
+---
+
+This is an important security release. For full details see https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ for details on patched vulnerabilities.
+
+Notable changes:
+
+* http: fix defects in HTTP header parsing for requests and responses that can allow request smuggling (CVE-2016-2086) or response splitting (CVE-2016-2216). HTTP header parsing now aligns more closely with the HTTP spec including restricting the acceptable characters.
+* http-parser: upgrade from 2.3.0 to 2.3.1
+* openssl: upgrade from 1.0.1q to 1.0.1r. To mitigate against the Logjam attack, TLS clients now reject Diffie-Hellman handshakes with parameters shorter than 1024-bits, up from the previous limit of 768-bits.
+* src:
+  - introduce new `--security-revert={cvenum}` command line flag for selective reversion of specific CVE fixes
+  - allow the fix for CVE-2016-2216 to be selectively reverted using `--security-revert=CVE-2016-2216`
+* build:
+  - xz compressed tar files will be made available from nodejs.org for v0.12 builds from v0.12.10 onward
+  - A headers.tar.gz file will be made available from nodejs.org for v0.12 builds from v0.12.10 onward, a future change to node-gyp will be required to make use of these
+
+Commits:
+
+* [4312848bff] - build: enable xz compressed tarballs where possible (Rod Vagg) https://github.com/nodejs/node/pull/4894
+* [247626245c] - deps: upgrade openssl sources to 1.0.1r (Shigeki Ohtsu) https://github.com/joyent/node/pull/25368
+* [744c9749fc] - deps: update http-parser to version 2.3.1 (James M Snell)
+* [d1c56ec7d1] - doc: clarify v0.12.9 notable items (Rod Vagg) https://github.com/nodejs/node/pull/4154
+* [e128d9a5b4] - http: strictly forbid invalid characters from headers (James M Snell)
+* [bdb9f2cf89] - src: avoiding compiler warnings in node_revert.cc (James M Snell)
+* [23bced1fb3] - src: add --security-revert command line flag (James M Snell)
+* [f41a3c73e7] - tools: backport tools/install.py for headers (Richard Lau) https://github.com/nodejs/node/pull/4149
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.10/node-v0.12.10-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.10/x64/node-v0.12.10-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.10/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.10/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.10/node-v0.12.10.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.10/node-v0.12.10-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.10/node-v0.12.10-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.10/node-v0.12.10-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.10/node-v0.12.10-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.10/node-v0.12.10-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.10/node-v0.12.10-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.10/node-v0.12.10.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.10/<br>
+Documentation: https://nodejs.org/docs/v0.12.10/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+8a9c7fe990c1028e7c6d5bf61413027904a0fff67e23ba7c7c6d5fbb16cd4884  node.exe
+c2b369b4fdb12c3ac14a6214c48c901e4805366a361c6cae5bb24215bf282318  node.exp
+6919172dc22ad2690836a3988bf138cfc80ba484490a05a6eafda0a4909936d1  node.lib
+5809753f1a8b6e3e311c41a066f0eb8f90b5b569896b6f1945af0971de9b2e4d  node.pdb
+c95df35ca1ed7b4b0ded815c1d49f36defcb1fdb882f6a8ef6106a07e3f2ffef  node-v0.12.10-darwin-x64.tar.gz
+b4ae523d81ced4935e0c7184bafcc1eb199d08ccfc70267a0dab546c33c18831  node-v0.12.10-darwin-x64.tar.xz
+d4abd2b778c9d803676ad6121e6fdbc625b9ea73e845b0ecd761c162e86150ca  node-v0.12.10-darwin-x86.tar.gz
+0bc827d4c494274855b01ff2fab4ad311fe3c0b50cc0b62bb7736c7c890d2f15  node-v0.12.10-darwin-x86.tar.xz
+c8e99589d96f9ad598c2d602e3dcac4bb0147a709da4da89a1f2b7f667f4b415  node-v0.12.10-headers.tar.gz
+8c44114a3f5747475a042fd2f2333d4671223638a0dfa3cb264bf32f9a7c91c5  node-v0.12.10-headers.tar.xz
+8fb4d6ed8934f0b0c92c26878511e1d340b068ee966c131ba0fccc1199f4349d  node-v0.12.10-linux-x64.tar.gz
+a993b72902eb1bdd50f1615026b6372a0d28302c15841b04e11bedab379709c0  node-v0.12.10-linux-x64.tar.xz
+6f3ea401d2f488afb6adc57a3056df8658c1c9a57a368637cbc215ed3133c3b7  node-v0.12.10-linux-x86.tar.gz
+99d0c121cd58b2d44080f78692dfb400e5098190f453709707594debd1359154  node-v0.12.10-linux-x86.tar.xz
+afa45162c741898c7fc382093f29e68503edfa48cd67541d9c2c4081197fba02  node-v0.12.10.pkg
+d67f17540c711eb150b8a389af1b4e6ecdcab66a1648b7ce925af98ab52b2698  node-v0.12.10-sunos-x64.tar.gz
+2840f181594a0bd8b9cade785e9b6502591da68dc5a3ed3f2773637eb7df980b  node-v0.12.10-sunos-x64.tar.xz
+beca24cc3615c5b1858817d121bd91eecdc3af5b98ed0c4c171e1ef60afac049  node-v0.12.10-sunos-x86.tar.gz
+3cb4a9cbfd0f724c3ba6e4ca2c6c70bb6d7c103dea682acf9c8ca1125133e1a2  node-v0.12.10-sunos-x86.tar.xz
+edbd3710512ec7518a3de4cabf9bfee6d12f278eef2e4b53422c7b063f6b976d  node-v0.12.10.tar.gz
+f6318e5413982d40358a1b479458ebdd4bb523ae572c1149ce0e73cb58661978  node-v0.12.10.tar.xz
+b888d17dbf04e43f521dbff8a68b24fae37027f6cd6b5a80430bc64fc5e7da40  node-v0.12.10-x86.msi
+6153b53d72ea6cfbd6fd4a591787831c32fdd610d851fa2312eece6ac4686929  openssl-cli.exe
+668479f90904e088ead0258de2941e597ba08aa61a1eed3ed96622c4c6d3bb25  openssl-cli.pdb
+79687fe8d08a439f5167ab474a1238b6423cdb4f72cbc94213cfd6c21cf729f0  x64/node.exe
+90116c88db51255a9c20158fd7b577769241b576d5642e269c465342c20f7025  x64/node.exp
+490482c06c1ae913e3f78006aa9d41d67659e5499a4155cef2ff2ab49caf8921  x64/node.lib
+58d9088252d3d5cc12647448491b6e287f9cd6a573be7b59f98ceb13fed15e2e  x64/node.pdb
+a3b49281f8f07eddf310c621feb55f98bd07f7ad252d5afa215212cf3f6e12d2  x64/node-v0.12.10-x64.msi
+3cf691f703fc23c71263f8f02fd8780891a0e0f6cae37b4e15353446a47014b7  x64/openssl-cli.exe
+ab634d22bd0a6bbf8a1adbd144f621e600deabf957d08effed729f88db3763ab  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWuhv7AAoJEHNBsVwHCHes2HwH/i14nZes3/aej0uw3Yu2vhU6
+X+MSyaZ4/Nrd+5YWy2BYXyVwO/PK7g508nGUqf5I4zEfmw8nwBYqyuf6891YeTR/
+rD5yKhldt/lnWFLu6L8g4FKSPo3Zf0Vb1EB/xgL04VHlP6Pjh0/AOU5VS6Rvk9is
+TerO4AHbYFYMkI7/xeSSPGxwhGEP5grBxOogJNRyHTfbav04VEg+kLwH59CSaYvM
+PdHEvb03fOhJBDsuK1I0yADvLqtiVeUoarWO9h4HVbt2+8haPaDFpHfGREEOwyxn
+hTZJUpoHMDTADd8Fzxpqbu2IPBhZwc01QUyCju8FUSTxAScCxNM1bYpuqDr934M=
+=w69g
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.12.11.md b/locale/uk/blog/release/v0.12.11.md
new file mode 100755
index 0000000000000..3b1bfe9fa2933
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.11.md
@@ -0,0 +1,105 @@
+---
+date: 2016-03-03T18:07:44.257Z
+version: 0.12.11
+category: release
+title: Node v0.12.11 (LTS)
+slug: node-v0-12-11
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+This release contains security updates. OpenSSL 1.0.1s fixes some low-severity defects that impact Node.js. See our [impact assessment](http://nodejs.org/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016/#_-update-29-jan-2016-_-openssl-impact-assessment) for full details.
+
+### Notable changes:
+
+* **http_parser**: Update to http-parser 2.3.2 to fix an unintentionally strict limitation of allowable header characters. (James M Snell) [nodejs/node#5241](https://github.com/nodejs/node/pull/5241)
+* **domains**:
+  - Prevent an exit due to an exception being thrown rather than emitting an 'uncaughtException' event on the `process` object when no error handler is set on the domain within which an error is thrown and an 'uncaughtException' event listener is set on `process`. (Julien Gilli) [nodejs/node#3885](https://github.com/nodejs/node/pull/3885)
+  - Fix an issue where the process would not abort in the proper function call if an error is thrown within a domain with no error handler and `--abort-on-uncaught-exception` is used. (Julien Gilli) [nodejs/node#3885](https://github.com/nodejs/node/pull/3885)
+* **openssl**: Upgrade from 1.0.1r to 1.0.1s (Ben Noordhuis) [nodejs/node#5509](https://github.com/nodejs/node/pull/5509)
+  - Fix a double-free defect in parsing malformed DSA keys that may potentially be used for DoS or memory corruption attacks. It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0705
+  - Fix a defect that can cause memory corruption in certain very rare cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()` functions. It is believed that Node.js is not invoking the code paths that use these functions so practical attacks via Node.js using this defect are _unlikely_ to be possible. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0797
+  - Fix a defect that makes the CacheBleed Attack (https://ssrg.nicta.com.au/projects/TS/cachebleed/) possible. This defect enables attackers to execute side-channel attacks leading to the potential recovery of entire RSA private keys. It only affects the Intel Sandy Bridge (and possibly older) microarchitecture when using hyper-threading. Newer microarchitectures, including Haswell, are unaffected. More info is available at https://www.openssl.org/news/vulnerabilities.html#2016-0702
+
+
+Commits:
+
+* [[`1ab6653db9`](https://github.com/nodejs/node/commit/1ab6653db9)] - **build**: update Node.js logo on OSX installer (Rod Vagg) [#5401](https://github.com/nodejs/node/pull/5401)
+* [[`fcc64792ae`](https://github.com/nodejs/node/commit/fcc64792ae)] - **child_process**: guard against race condition (Rich Trott) [#5153](https://github.com/nodejs/node/pull/5153)
+* [[`6c468df9af`](https://github.com/nodejs/node/commit/6c468df9af)] - **child_process**: fix data loss with readable event (Brian White) [#5037](https://github.com/nodejs/node/pull/5037)
+* [[`61a22019c2`](https://github.com/nodejs/node/commit/61a22019c2)] - **deps**: upgrade openssl to 1.0.1s (Ben Noordhuis) [#5509](https://github.com/nodejs/node/pull/5509)
+* [[`fa26b13df7`](https://github.com/nodejs/node/commit/fa26b13df7)] - **deps**: update to http-parser 2.3.2 (James M Snell) [#5241](https://github.com/nodejs/node/pull/5241)
+* [[`46c8e2165f`](https://github.com/nodejs/node/commit/46c8e2165f)] - **deps**: backport 1f8555 from v8's upstream (Trevor Norris) [#3945](https://github.com/nodejs/node/pull/3945)
+* [[`ce58c2c31a`](https://github.com/nodejs/node/commit/ce58c2c31a)] - **doc**: remove SSLv2 descriptions (Shigeki Ohtsu) [#5541](https://github.com/nodejs/node/pull/5541)
+* [[`018e4e0b1a`](https://github.com/nodejs/node/commit/018e4e0b1a)] - **domains**: fix handling of uncaught exceptions (Julien Gilli) [#3885](https://github.com/nodejs/node/pull/3885)
+* [[`d421e85dc9`](https://github.com/nodejs/node/commit/d421e85dc9)] - **lib**: fix cluster handle leak (Rich Trott) [#5152](https://github.com/nodejs/node/pull/5152)
+* [[`3a48f0022f`](https://github.com/nodejs/node/commit/3a48f0022f)] - **node**: fix leaking Context handle (Trevor Norris) [#3945](https://github.com/nodejs/node/pull/3945)
+* [[`28dddabf6a`](https://github.com/nodejs/node/commit/28dddabf6a)] - **src**: fix build error without OpenSSL support (Jörg Krause) [#4201](https://github.com/nodejs/node/pull/4201)
+* [[`a79baf03cd`](https://github.com/nodejs/node/commit/a79baf03cd)] - **src**: use global SealHandleScope (Trevor Norris) [#3945](https://github.com/nodejs/node/pull/3945)
+* [[`be39f30447`](https://github.com/nodejs/node/commit/be39f30447)] - **test**: add test-domain-exit-dispose-again back (Julien Gilli) [#4278](https://github.com/nodejs/node/pull/4278)
+* [[`da66166b9a`](https://github.com/nodejs/node/commit/da66166b9a)] - **test**: fix test-domain-exit-dispose-again (Julien Gilli) [#3991](https://github.com/nodejs/node/pull/3991)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.11/node-v0.12.11-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.11/x64/node-v0.12.11-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.11/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.11/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.11/node-v0.12.11.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.11/node-v0.12.11-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.11/node-v0.12.11-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.11/node-v0.12.11-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.11/node-v0.12.11-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.11/node-v0.12.11-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.11/node-v0.12.11-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.11/node-v0.12.11.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.11/<br>
+Documentation: https://nodejs.org/docs/v0.12.11/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+17c2d6926976279707d5576a82eb59c4dadc5b8adaef562744fc14fa19e3ab5a  node.exe
+f6a93ff89cdd8532a63f81d1e97a8394c6da6353ab0cdbf6ce83d69bfdbecc13  node.exp
+6524b6acf14f93ad15fa26a938ae13867cab17f8d031f03d5cad12c6b752244e  node.lib
+8fc934c37296fb639b080d0ba474ba5d6521cc32f0fd01e1514880f45a7e5b1b  node.pdb
+68b949f6c308eb1ad28e96926fca68e3ac0dfb7ec997945f4e26db99fe3ad711  node-v0.12.11-darwin-x64.tar.gz
+4011d2c1c24f19c8f6ec8c93616ed0259b5c8f56b32f9f043b0706a4891065ee  node-v0.12.11-darwin-x64.tar.xz
+057f701678c0fe0c596eaa517e8b7ba771bdca89d99a7ace8df8e1064784727b  node-v0.12.11-darwin-x86.tar.gz
+64181afbb0e9bf4087582b24f8332ae60a92d65fbf03f2ae4064c27e0df8ad09  node-v0.12.11-darwin-x86.tar.xz
+4d3985bddfbdc867eb1f226e74c3a507db01410f95aaa566da18ada9bfd51d02  node-v0.12.11-headers.tar.gz
+0d6c113200170e80e1fa7aac4830f513ff93269d96c7a32e9f5c30ac6c45ac0b  node-v0.12.11-headers.tar.xz
+d98b76b7721a60471801e07e1f90af4fd479e8e42a632d419ede0a7b3c603cc0  node-v0.12.11-linux-x64.tar.gz
+6122af4237461982e80111583c1b845ec8276c95dfd241f1e96c1cbcda671586  node-v0.12.11-linux-x64.tar.xz
+ecf627bf67bfd231e549869c6e2963acd5551d15d5cf1116b0649d3d14ddde19  node-v0.12.11-linux-x86.tar.gz
+5f376924c3e70a0b8283a0bcda15f2b32ff63adaa195a26a77bf309f04122d65  node-v0.12.11-linux-x86.tar.xz
+f6c2b066b9d75ed9b352849ff5044819bd527fceada669210999310aada9a280  node-v0.12.11.pkg
+6a68d6ad04c9b73ed72e88e39002bbaa95ffc423c6cf47e3c3da5edd0abbc701  node-v0.12.11-sunos-x64.tar.gz
+688f63d22fa8b2094225ffe049e5b7b584b899e5ede565b6f001d019c0e9c0da  node-v0.12.11-sunos-x64.tar.xz
+9e61254d7437c2498817225c62dc6cfc065bd3b2404a213d8d305419bca07a6c  node-v0.12.11-sunos-x86.tar.gz
+a0b32c1e606ce31d61faf4eb340aeecd0fc973a7c6fb4b45dd6a9aa1fac48ba5  node-v0.12.11-sunos-x86.tar.xz
+e49049d82f2a11fa164549d907d4739fe1293d53c07f48bd70e1df237b238a68  node-v0.12.11.tar.gz
+ad36d2fee86171582b7a3c7470a0c565bd816dc02518e1b64aa5f21a0fdf86ce  node-v0.12.11.tar.xz
+fbc814fe197618421015807e487ee5b30eeaca5224511680342e9eb178afd252  node-v0.12.11-x86.msi
+df06cd0f64660802d20cbff3655ce89dc1f302fa9fce05140ee00663d8a54c50  openssl-cli.exe
+f5386b0f3bd3591b5d65a0f7c8167f50c3a8c9dc8dab08fd8abcdd2b001ea1b7  openssl-cli.pdb
+46893f15c3ef27631646f47f380ad1e2ad344c2b337a85d228aa94ae58349f8a  x64/node.exe
+c9e771b9eddb0f7b0da929a3c3f27bdc8836da6e436e3980f97854e09c496f38  x64/node.exp
+e25a49dbaa616bd4cf9e7bb46ea3ec06e8cc68b255e2893772d40182896ec7bb  x64/node.lib
+965a585155a296f81c82b77c4df2d17680660aca3f074cd3c0a0b34adc339c4c  x64/node.pdb
+b9496d61e09ae852f27d7571c3be39a834befa7587607ae229d41f0e3bd56f59  x64/node-v0.12.11-x64.msi
+2e22479b9681caedfa271b9b414d5e4e6fc8b185ce560c57be10a61c98388e39  x64/openssl-cli.exe
+32ebc22dec65750c3e43ba944dd3fdd6fffefc303c6142a0f131d215b86b613d  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJW2HuxAAoJEMJzeS99g1Rd6MUH/jMQgOKWaO1+70aTA3g8/3yX
+S4Gj05FZiDTF8HO6Svrbka5hpU8BkuJAsL3sp+E4+cIwGdYyA73hzq8qN4Gwm0X8
+nmRpMfY1T+Goeox2m7D2rcrM88yeTRxtD7mM2sg32lDGUGwI0CiIEpYcA3BFF6tj
+Km7NlZahyiXaGEh6hUWcbkwHuoMEHKrACiMRb9RNOE0pdpdeXvoSYli7KBn8JZAl
+cQaK/KJxxUWeywnDzPcsg+gN4CQlnnKm6Tawtu++v6FWLcS8WTktd81Jue4knbks
+JoC+Bb4h2rvDR1/8o+Jjc95MnGvIx/MB5tFyY1tDEDjQxsC1oZXcUz4P5pjlnqE=
+=KKkY
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.12.12.md b/locale/uk/blog/release/v0.12.12.md
new file mode 100755
index 0000000000000..d0e77c6da3c8d
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.12.md
@@ -0,0 +1,84 @@
+---
+date: 2016-03-09T03:05:35.527Z
+version: 0.12.12
+category: release
+title: Node v0.12.12 (LTS)
+slug: node-v0-12-12
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes:
+
+* **openssl**: Fully remove SSLv2 support, the `--enable-ssl2` command line argument will now produce an error. The DROWN Attack (https://drownattack.com/) creates a vulnerability where SSLv2 is enabled by a server, even if a client connection is not using SSLv2. The SSLv2 protocol is widely considered unacceptably broken and should not be supported. More information is available at https://www.openssl.org/news/vulnerabilities.html#2016-0800
+
+Note that the upgrade to OpenSSL 1.0.1s in Node.js v0.12.11 removed internal SSLv2 support. The change in this release was originally intended for v0.12.11. The `--enable-ssl2` command line argument now produces an error rather than being a no-op.
+
+Commits:
+
+* [[`dbfc9d9241`](https://github.com/nodejs/node/commit/dbfc9d9241)] - **crypto,tls**: remove SSLv2 support (Ben Noordhuis) [#5536](https://github.com/nodejs/node/pull/5536)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.12/node-v0.12.12-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.12/x64/node-v0.12.12-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.12/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.12/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.12/node-v0.12.12.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.12/node-v0.12.12-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.12/node-v0.12.12-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.12/node-v0.12.12-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.12/node-v0.12.12-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.12/node-v0.12.12-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.12/node-v0.12.12-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.12/node-v0.12.12.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.12/<br>
+Documentation: https://nodejs.org/docs/v0.12.12/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+99a07e9ead255544d673ea2e95e8bb5f954e3714ba86cc36b2f4d6486b2f47e3  node.exe
+603c73dc0f82be261b15bbc42d225ab11e0435e91c9a5d49a5d6d0c1aeeef971  node.exp
+9fbad4381435c36c812ebe9b1a0e5a127578f15166575b5e0deb93e03ca47c55  node.lib
+91bf5f577d3dbff52e5e031b61c5769722d9cf4edb74ca01bf6d89792adef41b  node.pdb
+b9b7b7c8f9c35fd6492bd5e60ec485ca8bf60f678651c7b6c46a3d8cf561e13c  node-v0.12.12-darwin-x64.tar.gz
+52a92e5747ba02d8eee7d52cc18d4716933f6b559486c87300c9cd6ecbb3c72a  node-v0.12.12-darwin-x64.tar.xz
+a2faf1180ffa50dbce0ca0a63b4285982b9fd87623dcda400c8f7e2be3abaa0a  node-v0.12.12-darwin-x86.tar.gz
+d3b6db79d3cc535902313065c9aca3aa0c2d251b145a860a897a67e7bb23e521  node-v0.12.12-darwin-x86.tar.xz
+47d6bc7eb3e50fb7175f111882dd181088f252e7c6fc3b36c3f70c4d0e91df28  node-v0.12.12-headers.tar.gz
+453d814f3b288aedcc4a3db2f43d496d71d44703e7eb3e19405cc6df197c2a80  node-v0.12.12-headers.tar.xz
+a3d51cc26060fe46f9ebe69c750b20fe1f6f27a936db6046a73b8a9715bf3559  node-v0.12.12-linux-x64.tar.gz
+dde6ae22a4f5fb55f616a55b6220f7aca371ad8b3cba8738fae6573be5beb688  node-v0.12.12-linux-x64.tar.xz
+5c69b9f4d51fe7e54afe3c1a83263a03270ad5b09070c8d0769c4e1942c8fec9  node-v0.12.12-linux-x86.tar.gz
+59da55338059b4200759e34be7b873ad33d1cb7963fa6cdf38182b35524e79e1  node-v0.12.12-linux-x86.tar.xz
+986b53f0f229bf92eb44c1be58f86133489964cda6707c5ff48c3db075615ebb  node-v0.12.12.pkg
+ef361aec4a2c1e3789662e7605928717af76b4d0ed360d4facb75a606ac0a2de  node-v0.12.12-sunos-x64.tar.gz
+eadfacdbfda12b72fba9d74e49e74085fca7149dd7c13923be4e38235d3937c4  node-v0.12.12-sunos-x64.tar.xz
+f6d0fa1fe8cfc197fbe86c8f7517b42d610efb341218fad1b24bc7f08cc4433f  node-v0.12.12-sunos-x86.tar.gz
+eb4a72771e443825a95319b5db90e6f86de8cb2cb9298fd66e455716d9ca12a1  node-v0.12.12-sunos-x86.tar.xz
+61e4c176fd882498778b1a3907a5fe5c9e95e6cc8438b0d053d953aed3620273  node-v0.12.12.tar.gz
+5977adab4fec36abcc18053b1b8c1deac4c94016d7b19942a986291d58685db6  node-v0.12.12.tar.xz
+e47cac6c6159795eb774c110e89268c1f2a6045e5d53e55520ca7c3b79312761  node-v0.12.12-x86.msi
+be1df6904aa8a32dc5bf03d409e43abbf5fa9be225ac6d79c67d0493a34f1ab0  openssl-cli.exe
+6770ee8c31689680a3bc56834538be4a0dd261b852f0649a9f3ffdf7fa82c0de  openssl-cli.pdb
+9f8bf3bf37fb9c0cddbbb1a52bb6293e46f762c7eee419ce5b1dfed6a36e794e  x64/node.exe
+126cc3d2fa2d16e71e0ed8853540b7d34c276568f71fa78009d7d03a52b003e5  x64/node.exp
+d2155736da8f7c8e7b90468b8d2e995a07116308430236ac0fb04577ae830443  x64/node.lib
+552d5ae85a0f0d58707fbcec209fb47aedd18884ae60cd1fccd4d48211d7619e  x64/node.pdb
+65039c4b0a54aaf2a978798486e148e23193117ecd95f291acf5103277801cdf  x64/node-v0.12.12-x64.msi
+c525bc746ddee61f8dde934da2760426a152a006576349235d866fdf7864fbb2  x64/openssl-cli.exe
+16fca9b60b0e7696d7d265980cdef193ee50e5497b75d43740a491f521dde3a8  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJW35GxAAoJEMJzeS99g1Rd3WYIAIlC8yL88A20lhFMjG71i3OJ
+h2VvvFrOmXMTZIpnVSNtTjh2dtD80FWcThfXTF1mfA1d3GYlBBl+DBQfOkJsPOSp
+cwudVUymamOA0eB9JbHRbhEWjTwXXD0KnT7GeXw/3BLIDaHOgUHkD5kYPMJcS0EJ
+0C+mnJr0VNCDVASNx/n38FtnJg5yKfqSYyrCiYIpXQ2QaFZ0HxwrDTCvwi1C1nFJ
+Bcif4EHuOb/L2ARjqM777joim0YJFbyaV+6G99zdSIfO/hDu8aVIx58USqtRfvi1
+x5ZRa6E1e2xgKIlKDdA9zfc2prC54NfXdx29Svr89rahwC0VqTy2t5NgV8/JaFQ=
+=pzlZ
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.12.13.md b/locale/uk/blog/release/v0.12.13.md
new file mode 100755
index 0000000000000..f933322cc013a
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.13.md
@@ -0,0 +1,96 @@
+---
+date: 2016-04-01T00:12:07.721Z
+version: 0.12.13
+category: release
+title: Node v0.12.13 (LTS)
+slug: node-v0-12-13
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+**This is a security release**, upgrading the bundled version of npm due to a credentials leak vulnerability. Further information can be found in our post: http://nodejs.org/en/blog/vulnerability/npm-tokens-leak-march-2016/
+
+Node.js v0.12.13 will be the **final Active-LTS release for the v0.12 release line**, from next month, v0.12 moves in to Maintenance. This change impacts on the types of changes that will be accepted in to v0.12 releases, restricting them primarily to critical security and stability fixes. v0.12 will remain supported until the end of 2016 but it is important that you begin planning your move to a new release line as soon as possible. **v4 (LTS "Argon")** is recommended at this stage.
+
+**Update**: **the version of npm included in this release does not have the correct version string**. As such executing `npm -v` will report `2.15.0` rather than `2.15.1`, which is incorrect. The source code included in this release is in fact the source for `2.15.1`, including the security fix.
+
+### Notable changes:
+
+* **npm**: Upgrade to v2.15.1. Fixes a security flaw in the use of authentication tokens in HTTP requests that would allow an attacker to set up a server that could collect tokens from users of the command-line interface. Authentication tokens have previously been sent with every request made by the CLI for logged-in users, regardless of the destination of the request. This update fixes this by only including those tokens for requests made against the registry or registries used for the current install. (Forrest L Norvell) https://github.com/nodejs/node/pull/5967
+* **openssl**: OpenSSL v1.0.1s disables the EXPORT and LOW ciphers as they are obsolete and not considered safe. This release of Node.js turns on `OPENSSL_NO_WEAK_SSL_CIPHERS` to fully disable the 27 ciphers included in these lists which can be used in SSLv3 and higher. Full details can be found in our LTS discussion on the matter (https://github.com/nodejs/LTS/issues/85). (Shigeki Ohtsu) https://github.com/nodejs/node/pull/5712
+
+Commits:
+
+* [2ce29165a1] - deps: upgrade npm in LTS to 2.15.1 (Forrest L Norvell)
+* [a115779026] - deps: Disable EXPORT and LOW ciphers in openssl (Shigeki Ohtsu) https://github.com/nodejs/node/pull/5712
+* [ab907eb5a8] - test: skip cluster-disconnect-race on Windows (Gibson Fahnestock) https://github.com/nodejs/node/pull/5621
+* [9c06db7444] - test: change tls tests not to use LOW cipher (Shigeki Ohtsu) https://github.com/nodejs/node/pull/5712
+* [154098a3dc] - test: bp fix for test-http-get-pipeline-problem.js (Michael Dawson) https://github.com/nodejs/node/pull/3013
+* [ff2bed6e86] - win,build: support Visual C++ Build Tools 2015 (João Reis) https://github.com/nodejs/node/pull/5627
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.13/node-v0.12.13-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.13/x64/node-v0.12.13-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.13/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.13/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.13/node-v0.12.13.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.13/node-v0.12.13-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.13/node-v0.12.13-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.13/node-v0.12.13-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.13/node-v0.12.13-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.13/node-v0.12.13-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.13/node-v0.12.13-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.13/node-v0.12.13.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.13/<br>
+Documentation: https://nodejs.org/docs/v0.12.13/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+b6e84fce06882ec5da0870d7ed7b70541d9de505e767dc2fbd9605518d27d869  node.exe
+efbee64b1c5602f1ef50a26358e3a007c79892070b4500df4c3454635ce4fd9b  node.exp
+4edacd81a4df404cded210d35b2fbd28835f2b849bc43dad89252e4f3f2a0a59  node.lib
+9a6ef0d67a661253cbdb3fc92f99c5d06e569f6db86407f34df0e47b7a7e923f  node.pdb
+e842a8eb8b7658d177675de9d054de4d7fb7d6c77edfcda7d83adb95b029bf3d  node-v0.12.13-darwin-x64.tar.gz
+41d2f04872c1c1079856be475bdbdee5c63ac227cc2c08b94a6b48bac0469a2d  node-v0.12.13-darwin-x64.tar.xz
+8ecdcd3b29ef0d3264bb48c0834bc024016d19a8f5c040fa6b51328191f39a60  node-v0.12.13-darwin-x86.tar.gz
+33aeb892d0d0c044cc2dbfba4a234821ea9dcb09d4310e5b15fe0752d8b87e98  node-v0.12.13-darwin-x86.tar.xz
+bf6a8de61b08935e91ac345e2dcd54c95d1def963b5db9a8bb33cf75963e13e6  node-v0.12.13-headers.tar.gz
+19f6106b69a442da72ae9cf7f8ca9cef75d9a19348bd8c378ce1df50dad258b3  node-v0.12.13-headers.tar.xz
+3e8b6ee32fc9a726bfe6f3961bcccf3d2b6d0ddd68326abb4434039f16e10f09  node-v0.12.13-linux-x64.tar.gz
+6953bdca60cb703551d04078090a3347a0a8a820fded61bfb94005462251a7f2  node-v0.12.13-linux-x64.tar.xz
+8300b9cbe363bf2a5fd987e7d05a88cb60842ad5b0ea6cbf3f4342eef547feed  node-v0.12.13-linux-x86.tar.gz
+5618b0987a3b214c063578aa4e1905ba49ea2546894dd1b3277f659a3d563d03  node-v0.12.13-linux-x86.tar.xz
+ca6395291862af79808b42d91a6f6e2ab7ec7ca5187c6de13d9a2cc2b47956f8  node-v0.12.13.pkg
+9b40e2b657e560901c6cccf3c93d01a5055cb4d011ccfefe1b977dae7935ea42  node-v0.12.13-sunos-x64.tar.gz
+961be780775a91b453c260aca11c4ea24ce64b077ac3ee0970c0faa418a8c865  node-v0.12.13-sunos-x64.tar.xz
+83f862b0383ba6c9a15f32a043de48288b087c0f368117eac36d66779491a910  node-v0.12.13-sunos-x86.tar.gz
+15eca8c6c3aa8b2e2262b77c6047be97802b5fd6f2e23d73bf0a3daa856cae4f  node-v0.12.13-sunos-x86.tar.xz
+0a972ed6442cb526aa7aa1bcb10aa536b65bd90ab4956b5a1aa51b4b7bb071bd  node-v0.12.13.tar.gz
+d0a4ebff052016c81184b6b880009f299263fc1a2f2bca35483b67bb886c6556  node-v0.12.13.tar.xz
+03502f5cf6d3c6b8dc112558219af0ceba6af5793e1fb8139a6567780eded07d  node-v0.12.13-x86.msi
+4288ca4a92e3b79365b4be8fe5bc2d34066db7f1027dbcdfe42b7350eb5e1363  openssl-cli.exe
+5588b16ed5e0ad2ddd7b025353922bcedd7567fde3680175dee78046debcdfcd  openssl-cli.pdb
+75c0fc30a9454cecd40f43b3da8060eff1d22b1e7e2616afd9625678026a3880  x64/node.exe
+fc6a706dda6b96c4c3da96107b48580c4e5c9327667d5234c033f68ae5f54215  x64/node.exp
+8bf8cf62ef9629fd686008233fe5a97dff0b093f81cc2979aae9f1490f4b499d  x64/node.lib
+71396d3e53c3cfa93e95f81b464f7acd97d1e2454f2bfa7c0a9c407ada2bf18b  x64/node.pdb
+0c77dedd115776b7c5e1661a1c9c3ecc4cb5a119820b0919d190ba8fe15137f4  x64/node-v0.12.13-x64.msi
+d1ee99c0c37c7ac017725ec69169beba8d9358af9ba61ed0cf3e058cd3dfd224  x64/openssl-cli.exe
+7c6ebb541559eedf977109418f017bf035567936efee6f576516580a52a73a3b  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJW/bxoAAoJEMJzeS99g1Rd258H/Rj9sMrQ7HNLrLJdEGHr7rqW
+vxfmkHHX3dWS8IqrsoupeskSJeW4YLW8tB5MYKDJiU5hsjwPR6it4oDs8xvxmsaG
+UrZiTqTiFGNJ0Q6atxcBvkKJ0bUKGmyg9sHnFG1YbrfXryAG7usy1Ko2lzrh4WUt
+e8FokEoOMVYySJQxg+V8MrrNXwW3T9qPlW3cnPC3lTYS1wh9nTQgBeb8DnWaSMdD
+lkE8AmCbsM3KSM5qADbOEgjBP9VGJhFCBAtl5LZjlXs7/fca3GTCfTqPrqI4+pSn
+Qlv+t2nQMn5hd1U9oiROKrneVwMQwMBmRjx8m6c4dQ0rpm4paYrp/H2snfW2LHw=
+=Gzpx
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.12.14.md b/locale/uk/blog/release/v0.12.14.md
new file mode 100755
index 0000000000000..fa37cbe790adf
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.14.md
@@ -0,0 +1,94 @@
+---
+date: 2016-05-06T13:54:37.236Z
+version: 0.12.14
+category: release
+title: Node v0.12.14 (Maintenance)
+slug: node-v0-12-14
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes:
+
+* **npm**: Correct erroneous version number in v2.15.1 code (Forrest L Norvell) https://github.com/nodejs/node/pull/5988
+* **openssl**: Upgrade to v1.0.1t, addressing security vulnerabilities (Shigeki Ohtsu) https://github.com/nodejs/node/pull/6553
+  - Fixes CVE-2016-2107 "Padding oracle in AES-NI CBC MAC check"
+  - Fixes CVE-2016-2105 "EVP_EncodeUpdate overflow"
+  - See https://nodejs.org/en/blog/vulnerability/openssl-may-2016/ for full details
+
+### Commits:
+
+* [[`3e99ee1b47`](https://github.com/nodejs/node/commit/3e99ee1b47)] - **deps**: completely upgrade npm in LTS to 2.15.1 (Forrest L Norvell) [#5988](https://github.com/nodejs/node/pull/5988)
+* [[`2b63396e1f`](https://github.com/nodejs/node/commit/2b63396e1f)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [joyent/node#25368](https://github.com/joyent/node/pull/25368)
+* [[`f21705df58`](https://github.com/nodejs/node/commit/f21705df58)] - **deps**: update openssl asm files (Shigeki Ohtsu) [#6553](https://github.com/nodejs/node/pull/6553)
+* [[`02b6a6bc27`](https://github.com/nodejs/node/commit/02b6a6bc27)] - **deps**: fix openssl assembly error on ia32 win32 (Fedor Indutny) [joyent/node#25654](https://github.com/joyent/node/pull/25654)
+* [[`1aecc668b0`](https://github.com/nodejs/node/commit/1aecc668b0)] - **deps**: separate sha256/sha512-x86_64.pl for openssl (Shigeki Ohtsu) [joyent/node#25654](https://github.com/joyent/node/pull/25654)
+* [[`39380836a0`](https://github.com/nodejs/node/commit/39380836a0)] - **deps**: copy all openssl header files to include dir (Shigeki Ohtsu) [#6553](https://github.com/nodejs/node/pull/6553)
+* [[`08c8ae44a8`](https://github.com/nodejs/node/commit/08c8ae44a8)] - **deps**: upgrade openssl sources to 1.0.1t (Shigeki Ohtsu) [#6553](https://github.com/nodejs/node/pull/6553)
+* [[`f5a961ab13`](https://github.com/nodejs/node/commit/f5a961ab13)] - **openssl**: fix keypress requirement in apps on win32 (Shigeki Ohtsu) [joyent/node#25654](https://github.com/joyent/node/pull/25654)
+* [[`810fb211a7`](https://github.com/nodejs/node/commit/810fb211a7)] - **tools**: remove obsolete npm test-legacy command (Kat Marchán) [#5988](https://github.com/nodejs/node/pull/5988)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.14/node-v0.12.14-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.14/x64/node-v0.12.14-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.14/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.14/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.14/node-v0.12.14.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.14/node-v0.12.14-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.14/node-v0.12.14-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.14/node-v0.12.14-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.14/node-v0.12.14-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.14/node-v0.12.14-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.14/node-v0.12.14-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.14/node-v0.12.14.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.14/<br>
+Documentation: https://nodejs.org/docs/v0.12.14/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+83c5d843c5ba7bd8f1d43711356208eaeda0230e3587fa4a27aac5ae14308d2d  node.exe
+47cd92a1db9b8782c3e40e4e6ac85c706ea7e2dcf13e0c7803031885cd3893a1  node.exp
+3883d0af51df19e7a44d69d8dacec56ba065c41bfb05f7b1f49c53bae8637d3e  node.lib
+d1d9a6fc90707fa364f690decc010d950667841f85e49f088c79829124b914af  node.pdb
+b4de40b8fe9cf748b36b9d7764c06f1fc955c73e3547c4eaab3d90a818663e1c  node-v0.12.14-darwin-x64.tar.gz
+9c2270a1d92e22f03a8ccc8698ded7947056583336885912ba2f0840cf07fc38  node-v0.12.14-darwin-x64.tar.xz
+2ac52efd90931ea04dd01947e19c6320e519967a813f7274eb699bf468fe226d  node-v0.12.14-darwin-x86.tar.gz
+8209c23acb175dde1424ccd73945179393cd22791c3d51e24dfeb03f77c955d5  node-v0.12.14-darwin-x86.tar.xz
+75f927b98a955207f261d03de5966b167e893da80e641695e6b9d6da44312452  node-v0.12.14-headers.tar.gz
+072d68b05038fec7a443240947501b0be12bd33d1b958b1946caa80824beb4ed  node-v0.12.14-headers.tar.xz
+0f1f20f6989d32b4b67835f527ae3bf165c1c4a6a7dc3961d489288817956bae  node-v0.12.14-linux-x64.tar.gz
+a0b93224939fb638091b4e20c87a75e1c042314d419686f5040b8a48ed7f2112  node-v0.12.14-linux-x64.tar.xz
+212a3a5d1cdd34b71476dd615d95da9209b8a5e490dbe6141926e15f1ccfe386  node-v0.12.14-linux-x86.tar.gz
+a85432f5da612184baee47d93870b7796776ed15d61670dbec6640621ed4722a  node-v0.12.14-linux-x86.tar.xz
+59f7d1426e63ff266b5d7f7ccb3a5b5bc7eea2b1c5d6ed44dd45370235ab4357  node-v0.12.14.pkg
+906a44e9f6024c3f9af05a8aac5ba10c25d84bf56b9fb08c5fc1c26c5a8b9d27  node-v0.12.14-sunos-x64.tar.gz
+100f724b5f2d1dc263aa70f3cf77af873097157a22d15c883c5cd39e2ffe2520  node-v0.12.14-sunos-x64.tar.xz
+f042bee409d4da3114571dfff496a954ea6cd614e7fb78fd3d9b50d799396757  node-v0.12.14-sunos-x86.tar.gz
+59ca5e14f1b126887b7c4944ab0423f06011ff7acb3c142bfc486dd85a9f3718  node-v0.12.14-sunos-x86.tar.xz
+0a55e57cbd3ffa67525c0d93ac7076d3b2ac70887b11c5c97be3e1953cb50b1d  node-v0.12.14.tar.gz
+ed57a1917fb089726b31735e138fb41d897b3c834cfc7c895390b2d273623f1a  node-v0.12.14.tar.xz
+5b23e0733ab87adc09bbac9eb1d1341616a346c4ca8a69b4b3539b559de9c7b2  node-v0.12.14-x86.msi
+d676d494a36ddfd21041cc07e9fa80f6d21b6fbd5a71f84611f980c410019639  openssl-cli.exe
+086f4795edcb076669065a064006085ce415d4d56d89298599a0880ff0d7154a  openssl-cli.pdb
+19b2327c0068c8fcd3a8be7a724527627e346ca8e57fb1e3e39b7f80e94bd486  x64/node.exe
+61b31c6af9d606bcef77d4a9afa531a597570f92cd5afeeff4e7a4223c2326c8  x64/node.exp
+a838e4a513fcbfcbb6f8aad96f240bc4389940e95186b80383e32711accbb6ae  x64/node.lib
+2e3cc6017f2f6cc806fae5a27bc2d696fd780558f6c5c1fa7c0df82e6c0084df  x64/node.pdb
+53da9c08f72c6260d31b7c70812cc2ad17d5e203860fe1b7c6c85f0ec3d6e2ea  x64/node-v0.12.14-x64.msi
+524ce8394e20e8f7a6fd681c7d509e77d015bd16510caaff954a983f0d171a29  x64/openssl-cli.exe
+75404fbe3ec01c52e9373b766e59d55bada0404f8f14396e6bcaaefd4e00491a  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJXLKGsAAoJEMJzeS99g1RdI20IANwgtd3Q8omZiXhnSMSMNqt3
+AZybwyOKOfGTqxmbmRxlSsllp46lWoj0l+kp0NfiSopXe/+waCpyeIemUtaF9Ag3
+3gAtWP3cnw4rPv6CEG1IJu5Q1nHq1HKgMUcW+L5PUCN869SXO/ZREYtAwX4fjg/X
+lhqqAss7117nV7vQ1TbkLynEm8uT2S2kOQ8UjKpazp0IobPpSoc0XiodsAkNHKpt
+UGSxFKIaAjlF9JsuQw91AYIBJ3658aQw3LnIckymO8xirZE5ek1X8ReuuwhDUszQ
+ibXwwI09/AGCfhakitr3NmGG+Pg6gc/UEASTJtxPCVRcrKFcJ5tIWRynaRgV1uM=
+=ESJj
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.12.15.md b/locale/uk/blog/release/v0.12.15.md
new file mode 100755
index 0000000000000..5fa9a6a324bea
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.15.md
@@ -0,0 +1,93 @@
+---
+date: 2016-06-23T23:26:28.211Z
+version: 0.12.15
+category: release
+title: Node v0.12.15 (Maintenance)
+slug: node-v0-12-15
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes:
+
+This is a security release. All Node.js users should consult the security release summary at https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/ for details on patched vulnerabilities.
+
+* **libuv**: (CVE-2014-9748) Fixes a bug in the read/write locks implementation for Windows XP and Windows 2003 that can lead to undefined and potentially unsafe behaviour. More information can be found at https://github.com/libuv/libuv/issues/515 or at <https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/>.
+* **V8**: (CVE-2016-1669) Fixes a potential Buffer overflow vulnerability discovered in V8, more details can be found in the CVE at https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1669 or at <https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/>.
+
+### Commits:
+
+* [da8501edf6] - deps: backport bd1777fd from libuv upstream (Rod Vagg)
+* [9207a00f8e] - deps: backport 85adf43e from libuv upstream (Rod Vagg)
+* [9627f34230] - deps: backport 98239224 from libuv upstream (Rod Vagg)
+* [5df21b2e36] - deps: backport 9a4fd268 from libuv upstream (Rod Vagg)
+* [e75de35057] - deps: backport 3eb6764a from libuv upstream (Rod Vagg)
+* [a113e02f16] - deps: backport 3a9bfec from v8 upstream (Ben Noordhuis)
+* [8138055c88] - test: fix test failure due to expired certificates (Ben Noordhuis) https://github.com/nodejs/node/pull/7195
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.15/node-v0.12.15-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.15/x64/node-v0.12.15-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.15/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.15/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.15/node-v0.12.15.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.15/node-v0.12.15-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.15/node-v0.12.15-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.15/node-v0.12.15-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.15/node-v0.12.15-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.15/node-v0.12.15-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.15/node-v0.12.15-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.15/node-v0.12.15.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.15/<br>
+Documentation: https://nodejs.org/docs/v0.12.15/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+ff39a5428a1aec5aedcd6645aff0f66ef86b5bf12775794b4dec22b1e4231cc5  node.exe
+a1a45e5e9522f5206adc9df964c985d45469418f9daa99b4c589f004817a7e5d  node.exp
+ad9ee3ad0341b60b63d17880c8e294dea07310939d8e827942f6389080e4c675  node.lib
+0ebb993fb2a9a0dce45d7c1b9d23be182f2e9ec9a233e1ccf4f959e50848126d  node.pdb
+125551969069284099d402d85e36e1637d9dd6f19105261f87b8f8b2020b3433  node-v0.12.15-darwin-x64.tar.gz
+976c5a044e2fcc9dedf59e7747dd7ace34ea1070b53be32e39ff262203ddf448  node-v0.12.15-darwin-x64.tar.xz
+2026bdd953a783d78e2036f67f95590d3334f06541371bbbc87d3ec4991e60e9  node-v0.12.15-darwin-x86.tar.gz
+61438f804d21fb08817d9d355efcd6092e7ea25544b564ad2ab525c2f42c6786  node-v0.12.15-darwin-x86.tar.xz
+bb5d26514a2c217eb5895efe4884d533e10f31d31949947c67857da515e03422  node-v0.12.15-headers.tar.gz
+b895244ddec40ad8a9c9c80ad307bc11386da0c90b1df4eab0e8748eca4f4a26  node-v0.12.15-headers.tar.xz
+ab2dc52174552e3959f15a438918b32b59e49409e5640f2acb1a3b9c85cf2a95  node-v0.12.15-linux-x64.tar.gz
+86117cd5bf3018fc7f981afedb2d36af8b826c5b6d0a5f8bebff7078de0d1e97  node-v0.12.15-linux-x64.tar.xz
+0ea7a2860311596a13e202fef507ec2a55db9ddbb1d9cb27fa19b7e61d56ee20  node-v0.12.15-linux-x86.tar.gz
+907ec2c93f7ee1428f0d7363e53269554225700891787c3df144d280399357c7  node-v0.12.15-linux-x86.tar.xz
+99987c0cb118cf360c01d647228064bc383ff70fb09f895760b4f7d89f618cf0  node-v0.12.15.pkg
+6114f3282e6650210cdfedf7ddf7d5dc62ad80b49475b4e2938afce790338d04  node-v0.12.15-sunos-x64.tar.gz
+ebc62db636d77ea1b1b1f9072e65d83d905173a5e47e0bfeb9bef376a1626d69  node-v0.12.15-sunos-x64.tar.xz
+29b2fc6d75847ae879bda550f1308bc34abb3ce094030ace93b44a3caba7b2e1  node-v0.12.15-sunos-x86.tar.gz
+4a2dc68c698f232d40c728192348a387c77fb3a061c9c82f80ea67b55105b338  node-v0.12.15-sunos-x86.tar.xz
+c446d40d9b0eb876dab9a87c3dbd1935dc85155d2ad991b36ddd6c5ca3825a5e  node-v0.12.15.tar.gz
+f4ce0c4bb217a32d074916d291381b16e1b9a0bb2be0317ce28e471e0f42a0ac  node-v0.12.15.tar.xz
+957d8888fe5e954e0036fc6bce9d38021c6b81a64ec5c8daec1bb561211a2abd  node-v0.12.15-x86.msi
+101a9c6d29f83c09902ed946b8c05ca0941dbebadc11909df9190d240d438287  openssl-cli.exe
+68ca7a598387e0b7ba65d5c32ac77b1a0d54a1d37850ffbe8181b739cd433939  openssl-cli.pdb
+6f2cf6fc8de004be17f6b2be4a0b269c7cc5588d436fb62d4b4a38e44ce69733  x64/node.exe
+d7c248428c3a36f641499d384f959b5d4d90c37099ad3078035992e4c46a1e95  x64/node.exp
+b26f0fe2ebc9ffa111507136c5b1d83f09bec1609f4c1f27da540b2c57942e62  x64/node.lib
+5b558f66fb670849f560d881b35b5b3072c95e2a12ba655c511f5b5c96ac2bf0  x64/node.pdb
+96a410825adabb6e95d79c25ce5198dc72a9813f7a43c03add6e9a2e6c2d3acd  x64/node-v0.12.15-x64.msi
+e641cc163b32c625ad9a11aa0c2b2046e1fef68452056f453eda787b30c2c491  x64/openssl-cli.exe
+d1c9aaa0fa29e04eadf49134773fe5f2089ee35353fd8ddcafcfe6adc8880ca0  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJXbG8PAAoJEMJzeS99g1Rd8jEIAKNsH/0exEI7r5+wD0ZoDOhX
+m8IltzyytMIUZ2v23TcxLqjnRjPGZEmceFrSQsv8MyyjjNh+RupgxZYE2FFJDFqS
++TZWBgFX38hWsu6Ha3U9IJA0bjCp+p/Q0I92i77JG7OqIeCsniWhBeOzzhf3RVRG
+525ZdonP8mWIt/MmXT2+v4jjYbUqOQDAWd/IR9U/8GZrlZOB8LMSm/+4sQUIYZql
+mOj9o1fETcKSWlJXOgkOFqYzumrz6ZSkI6YRVMuB1aBFVi9/4r95OlwmE3pZ2cIE
+RsTPQfHvI3I6b8duuY0qEa/mDBSlTQtVAVo0ptYpBbuMouV7zdqd5JgAMUyjdqg=
+=1zpB
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v0.12.2.md b/locale/uk/blog/release/v0.12.2.md
new file mode 100755
index 0000000000000..c91fc68c8de68
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.2.md
@@ -0,0 +1,121 @@
+---
+date: 2015-03-31T23:22:18.000Z
+version: 0.12.2
+category: release
+title: Node v0.12.2 (Stable)
+slug: node-v0-12-2-stable
+layout: blog-post.hbs
+---
+
+2015.03.31, Version 0.12.2 (Stable)
+
+* uv: Upgrade to 1.4.2
+
+* npm: Upgrade to 2.7.4
+
+* V8: Fix --max_old_space_size=4096 integer overflow (Andrei Sedoi)
+
+* asyncwrap: fix constructor condition for early ret (Trevor Norris)
+
+* buffer: align chunks on 8-byte boundary (Fedor Indutny)
+
+* buffer: fix pool offset adjustment (Trevor Norris)
+
+* console: allow Object.prototype fields as labels (Colin Ihrig)
+
+* fs: make F_OK/R_OK/W_OK/X_OK not writable (Jackson Tian)
+
+* fs: properly handle fd passed to truncate() (Bruno Jouhier)
+
+* http: fix assert on data/end after socket error (Fedor Indutny)
+
+* lib: fix max size check in Buffer constructor (Ben Noordhuis)
+
+* lib: fix stdio/ipc sync i/o regression (Ben Noordhuis)
+
+* module: replace NativeModule.require (Herbert Vojčík)
+
+* net: allow port 0 in connect() (cjihrig)
+
+* net: unref timer in parent sockets (Fedor Indutny)
+
+* path: refactor for performance and consistency (Nathan Woltman)
+
+* smalloc: extend user API (Trevor Norris)
+
+* src: fix for SIGINT crash on FreeBSD (Fedor Indutny)
+
+* src: fix builtin modules failing with --use-strict (Julien Gilli)
+
+* watchdog: fix timeout for early polling return (Saúl Ibarra Corretgé)
+
+
+Source Code: https://nodejs.org/dist/v0.12.2/node-v0.12.2.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.2/node-v0.12.2.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.2/node-v0.12.2-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.2/x64/node-v0.12.2-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.2/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.2/node-v0.12.2-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.2/node-v0.12.2-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.2/node-v0.12.2-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.2/node-v0.12.2-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.2/
+
+Website: https://nodejs.org/docs/v0.12.2/
+
+Documentation: https://nodejs.org/docs/v0.12.2/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+bfdba242dbef3c6b2567c3cffd06fa4dcdab93ba  node-v0.12.2-darwin-x64.tar.gz
+f6d3ab76516b800ee7f30c7b53f53a8c53914b70  node-v0.12.2-darwin-x86.tar.gz
+0873180db9ebfe5b46f83de96ec67f9982f8e26e  node-v0.12.2-linux-x64.tar.gz
+916b1d9ecc2ba935836436aeafa8a6a64dfbc3a3  node-v0.12.2-linux-x86.tar.gz
+52440341044462f0089c06416a4ac720312939b9  node-v0.12.2-sunos-x64.tar.gz
+f0df61d6d5825ba62d0ef8adca6898dd95afba0d  node-v0.12.2-sunos-x86.tar.gz
+bdc711c0c8e6a48ff54a03350175070d0d55bb13  node-v0.12.2-x86.msi
+c88904207f5ddb7c1286cb1bf5ae5c3b7488b3cd  node-v0.12.2.pkg
+a969f17a0a6c9238584f8946d96e8d39be8eb957  node-v0.12.2.tar.gz
+2a11914845de4fdcd542da1ee1850bdaa9365e44  node.exe
+be95280eeb97abc7e490c21f75c45eb963261006  node.exp
+d6ba806609e3702be043951560964895088d7c16  node.lib
+ca2f0b4504d137df4c72193cc4e09993d458beee  node.pdb
+d877da4f9f05c57039ea1dc876fd7d776228d10e  openssl-cli.exe
+92de0ab27f9304852bee902094c054967bc8a378  openssl-cli.pdb
+994a1461df5dd7de79f8072b14103642d0d5cbfe  x64/node-v0.12.2-x64.msi
+bb7ff2003522667be0c6990358d37fda654ca552  x64/node.exe
+8b94fd4aa06a74517815832c7b2079c4c0a476b9  x64/node.exp
+527400175a806ff3b0db15a70eea68950f199743  x64/node.lib
+b509a605aea12234f33e8311ea28af8fb05ec42e  x64/node.pdb
+6f67c2dee109c16e47109fc8ae8efd165a530a7f  x64/openssl-cli.exe
+48da80165e13ada3c41760e903200ae52190d534  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVGyv+AAoJEFCjBR+IjGKNJYsP/2nF/1489IXga69k2PkyDwaa
+hFiWHpASH0hmcnoISDeMOwCLQIiqUsVx4a3ou5Dd844MNyPSDlzL4mvUYhAEklVZ
+xZHvWqvqdkMkUFQY6Safz/ZN19667uVr0n5yzjkjtp1kONfUHA+PDIimFFXD0NQx
+oUssDP2qnfr8IoCWGp8oY0BaHiw3VN1F1P5KWt3G3nkIcNeeoSp1MYl5OX5zxSo5
+mj9Y2i9qaIE3NAkkX5GJxNytbj82VJjlR6517zJ7z34EbevtvLk/5F1whOuE/Ipq
+Qa2xmQlKtC1FrH3EV4v0TVyZzJyy8PZDmLQZIxkQJHdJc511zf1MZ1j0lBUBbf+c
+xCYyg1IVpntOF9KAzXpV9k3Ffv9vdGbWMkGUaUfAsSmU6Pu86l96cYKtRTUT7zGv
+Bw+wWsvmIOnT1EIRvzK+lCDrTfNEhDEyhItGWiWS8UobEtvuXoCEriI32LYPPa6o
+CC8q18VzKonn5t0ixjkrx4JN/Vtx4f5nDNRbi3397uiUilVLc6c0MYwO7lgpv8Xw
+Ztj4z+epqoyqKTbRUHH8euuQkW0G25Of0a/By1AGPWVxxmYv1XM/2qdkWJcZnijO
+3pDu3K4GheyMSvFlqzt9uEZYAXVKAEiHG3Z2MyEQVLvjHN0ug7w+X87YU0DBJlRi
+5iAY7/T05CiLJ1+f4Czn
+=yvpO
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.3.md b/locale/uk/blog/release/v0.12.3.md
new file mode 100755
index 0000000000000..277b2092d4aa4
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.3.md
@@ -0,0 +1,101 @@
+---
+date: 2015-05-14T02:34:02.000Z
+version: 0.12.3
+category: release
+title: Node v0.12.3 (Stable)
+slug: node-v0-12-3-0.12.3
+layout: blog-post.hbs
+---
+
+2015.05.13, Version 0.12.3 (Stable)
+
+* V8: update to 3.28.71.19
+
+* uv: upgrade to 1.5.0
+
+* npm: upgrade to 2.9.1
+
+* V8: don't busy loop in v8 cpu profiler thread (Mike Tunnicliffe)
+
+* V8: fix issue with let bindings in for loops (adamk)
+
+* debugger: don't spawn child process in remote mode (Jackson Tian)
+
+* net: do not set V4MAPPED on FreeBSD (Julien Gilli)
+
+* repl: make 'Unexpected token' errors recoverable (Julien Gilli)
+
+* src: backport ignore ENOTCONN on shutdown race (Ben Noordhuis)
+
+* src: fix backport of SIGINT crash fix on FreeBSD (Julien Gilli)
+
+
+Source Code: https://nodejs.org/dist/v0.12.3/node-v0.12.3.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.3/node-v0.12.3.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.3/node-v0.12.3-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.3/x64/node-v0.12.3-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.3/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.3/node-v0.12.3-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.3/node-v0.12.3-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.3/node-v0.12.3-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.3/node-v0.12.3-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.3/
+
+Website: https://nodejs.org/docs/v0.12.3/
+
+Documentation: https://nodejs.org/docs/v0.12.3/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+ff48b814cdc54a1df10c60a476b2f6833549551a  node-v0.12.3-darwin-x64.tar.gz
+a3a808aff450aa04f535fec9517faeca01492e15  node-v0.12.3-darwin-x86.tar.gz
+bb07dacb0802386719cf619125546ea483f4eb93  node-v0.12.3-linux-x64.tar.gz
+4d5c42df29277526ed32d866d7b2491242706c14  node-v0.12.3-linux-x86.tar.gz
+df6a9b56c2be1a1c423786917eccaac10c786d3f  node-v0.12.3-sunos-x64.tar.gz
+124324b3387993512a111fed776d979a89254b1d  node-v0.12.3-sunos-x86.tar.gz
+410d37d74775bf0401b06ecc01f71d181c9c99e6  node-v0.12.3-x86.msi
+8a64eab15c0c0c74d480f75c5362c06ce3e5e1ac  node-v0.12.3.pkg
+b0b02a254c06ebf2b1695900181baa3ffd206584  node-v0.12.3.tar.gz
+38901d7f5738f39ed69312215a133e3007300be2  node.exe
+4f2d0b3214b4ded6dac35144f22610db2f1be438  node.exp
+f3d8801fc939fe3178311fe4f7aa23d7cca4a82a  node.lib
+8f71bbb0353bf56bbafabe7b32719e0534386e02  node.pdb
+30b4bbcf7fdf02647e99bdfa3724329a61bf6328  openssl-cli.exe
+42c3329db1002b48749c1519d17b51418045f850  openssl-cli.pdb
+3677034221eeb300d7cd0cf2aaf3d172ab05fd11  x64/node-v0.12.3-x64.msi
+044c4b67a835ca3873df3844a074230a825aae5f  x64/node.exe
+a7e22fa741c1ab8fcfe7c51610dad63b666a93f9  x64/node.exp
+5a1fcc12bccd5fc61d63381c02b0c676e509f18c  x64/node.lib
+af0451dd1db225c7c46e5ace67d8de1cacf66349  x64/node.pdb
+88a06524bac25b80e776ab4f393df175fa5d6940  x64/openssl-cli.exe
+e29b5871e9822a74dc2ea34eb3771a4a870f307d  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVVAmKAAoJEFCjBR+IjGKN/80P/ilLD8gRvTw8bY+6QumWnjJx
+4pOcthnjp1z4Dh/0zdKN82vDaogXfzjhE0ZxwwJboWKkN6ME6tc+ayAeEEX3Dtia
+OUIUSHRx5+MlrcdBjE61TPdfUiiKRh7b185iyDotD5En41zcVhG+QWC72MeMo1aP
+uF0lwO067gWJojypl75IFSlgnT3GtUWL1ojY4rCu8Cz0mzaED0OjdiZ4pJGg5c0y
+hcwjwHZ73c9pXwzDFRjUH2BruWBYI7bWtyh7vMfNMTEOkjSEYLM1OX7fVeBBbSE4
+RLTxjuZnQXx1GWIfjU1mWbjAOPOO/ON95IrFzD+EY4eh1kYK4H0Bq3Mz0eR8oxlt
+Ird4X79JbghmsvLVX2KInCIixdJMNhI5ahWpHwMnAKJxlCSbxGJwIWkxHWFNCGs7
+j62pFZqPhB3e6Z8DTADOYam3ZzIW0BN33W61u26I4yehOpKVbSGyiwkfpp9vzoKJ
+uxqiaWFeh4ytJOtnr4zJMe80Tgz5BllvNy4t8SIEUEJZDNFvBQqFamj5rol9CCvJ
+DzVm2NOXAmHM6DVLkUofYOB6fc517NLt3c0j8Wm8TXbxNGrQlaEjSCB4CY2n1BDB
+BNf/te7frV4emtwE3R5+UA+3xgZkdmUiniguGigceIqupKH3O7wlTTLk0N3JNssd
+MvSLfPrzlji20kOJojKr
+=N8jX
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.4.md b/locale/uk/blog/release/v0.12.4.md
new file mode 100755
index 0000000000000..db06f7b058f5f
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.4.md
@@ -0,0 +1,87 @@
+---
+date: 2015-05-23T06:47:12.000Z
+version: 0.12.4
+category: release
+title: Node v0.12.4 (Stable)
+slug: node-v0-12-4-stable
+layout: blog-post.hbs
+---
+
+2015.05.22, Version 0.12.4 (Stable)
+
+* npm: upgrade to 2.10.1
+
+* V8: revert v8 Array.prototype.values() removal (cjihrig)
+
+* win: bring back xp/2k3 support (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.12.4/node-v0.12.4.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.4/node-v0.12.4.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.4/node-v0.12.4-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.4/x64/node-v0.12.4-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.4/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.4/node-v0.12.4-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.4/node-v0.12.4-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.4/node-v0.12.4-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.4/node-v0.12.4-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.4/
+
+Website: https://nodejs.org/docs/v0.12.4/
+
+Documentation: https://nodejs.org/docs/v0.12.4/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+bebda08e40413c17585fc333ba2ca55305b9d7ad  node-v0.12.4-darwin-x64.tar.gz
+79b097ba53bc50bf33b70767bc716c326952d683  node-v0.12.4-darwin-x86.tar.gz
+9a832e42b8910a02573fea80bde29f86f7c71173  node-v0.12.4-linux-x64.tar.gz
+6ea26f3ec48dc06abaedb0c918b1c0d9caafd836  node-v0.12.4-linux-x86.tar.gz
+48934e6cf627fb1b2a54360b96f5545ad8401b2b  node-v0.12.4-sunos-x64.tar.gz
+4c5e434001b11553313187aa58eeafc2f7003fae  node-v0.12.4-sunos-x86.tar.gz
+dbddd67f61c0a5428ad1078b9f7ffe43c4722f07  node-v0.12.4-x86.msi
+39d360a8910707fa8dbdcc975d9eaa5225334943  node-v0.12.4.pkg
+147ff79947752399b870fcf3f1fc37102100b545  node-v0.12.4.tar.gz
+c90d0a4a6e2e1b117f4959b8a20f01ab395af7a0  node.exe
+382a83f002a7a3b4cdaf652b8e17b5d50a28f690  node.exp
+0ac9dc8819b0b7ec4259167827952de6f99e1553  node.lib
+aab3ce0768bf1ffa6f5e9be10cc2e9d07bfb44a4  node.pdb
+806b363c427149ff67e725708111ff16aabfdadc  openssl-cli.exe
+5882b1d72395628cafb061d32b14fbc22b8a4094  openssl-cli.pdb
+69f15439af92c5e0beec02dc8145b74d98c103dd  x64/node-v0.12.4-x64.msi
+cf6aba37acb1f1699ec87ea279da872953aab948  x64/node.exe
+8005ad9da1702cc74bf37a0fd2e8c8dd01abc78e  x64/node.exp
+83cfd2d1cd51e94d7be5abe1593d845e5d72ef98  x64/node.lib
+4f3a46c2f6416b0554f24e08b9b599655a3f4c9e  x64/node.pdb
+6aff9aff978b1ff2d35b55d060d89b53d5e48678  x64/openssl-cli.exe
+dd18b2b7eb0435071abb75893af197d15b33303f  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVYCJhAAoJEFCjBR+IjGKN+UcQALEW1e3M0huwiU9gdCNhzfO/
+BwoWtdLl+303lBRfQBpzOxJjqEZ+dA+GC0wTRO11Mq9B0Rx3gp1B9gjwoA/8W3ky
+2BNICC9BBc8vL1r7I5XaH6U7YOhMru/XkL/8rOJYUBRod3o+4irAvOS9Xe9nRbII
+TKHOfaIqFvPTZMQgC2VW/GIVFE+JmY/7JZlVd1hCTKAHLk+PcaT9t3C1wyJO7qHV
+S0r5Hs2kT4xSxgsGx7jfBFAtqM/kXF5C/oBFefSpTQFm3n6qWmlTr6X+IogKrlud
+iBl1bV29kGkImzSPv1rDr8IJ3/tQdPNzzt5RFiWD8ezXjzu3dMI5SioPzRmXy+uw
+DvaUE3ub8dzgqImybUFx5+BpqiWQEhIBEnBFWEmDq1yabqxRM1xJiQOz2Ui6i1Ms
+C90WGm2uXQFVZasaVrDnbQfFtSSpuvEBmByNIe7fbZ92YnSLFhQ26TvZ6xDt/Ef/
+uwFAx8HE1cbke2hUAgZjj3NWeNsCFyyrMsaQnU6pJOxPgJJmr/04lvw3e1IIaF37
+3BN3sRlHgs+iRwMdxpaCwJKfY4cIVZl+Ezm1kJ9ekQyhIlSl+tJBHzJYCQDcpVYd
+A2zw5k2w5uWbiEuFuacgvTtoCiXQiaxBESufvvzAOiSnb+8JcPvrpPmB1eOnWO2J
+H1c+UgMLjJvkLtI7gHs8
+=Lr9D
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.5.md b/locale/uk/blog/release/v0.12.5.md
new file mode 100755
index 0000000000000..3037ca8d208b4
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.5.md
@@ -0,0 +1,116 @@
+---
+date: 2015-06-22T19:52:51.000Z
+version: 0.12.5
+category: release
+title: Node v0.12.5 (Stable)
+slug: node-v0-12-5-stable
+layout: blog-post.hbs
+---
+
+With this new release, OpenSSL has been upgraded to 1.0.1o to fix [several
+security vulnerabilities](http://openssl.org/news/secadv_20150611.txt). Two of
+them affect Node.js directly: Logjam and CVE-2015-1788.
+
+Regarding Logjam, OpenSSL has added protection for TLS clients by rejecting
+handshakes with DH parameters shorter than 768 bits. It means that _upgrading
+to this release of Node.js may prevent TLS clients written in node from
+connecting to servers using short DH parameters_.
+
+Although it is a breaking change in a stable version, the Node.js TSC
+determined that this is the best path forward to ensure the security of
+software written with this and future stable versions of node. Should you
+encounter any issue with this release related to TLS clients not being able to
+connect to servers using short DH keys, please create an issue at
+https://github.com/joyent/node/issues.
+
+As for CVE-2015-1788, before this release, TLS programs (including servers)
+written with Node.js are vulnerable to Denial Of Service attacks.
+
+2015.06.22, Version 0.12.5 (Stable)
+
+* openssl: upgrade to 1.0.1o (Addressing multiple CVEs)
+
+* npm: upgrade to 2.11.2
+
+* uv: upgrade to 1.6.1
+
+* V8: avoid deadlock when profiling is active (Dmitri Melikyan)
+
+* install: fix source path for openssl headers (Oguz Bastemur)
+
+* install: make sure opensslconf.h is overwritten (Oguz Bastemur)
+
+* timers: fix timeout when added in timer's callback (Julien Gilli)
+
+* windows: broadcast WM_SETTINGCHANGE after install (Mathias Küsel)
+
+
+Source Code: https://nodejs.org/dist/v0.12.5/node-v0.12.5.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.5/node-v0.12.5.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.5/node-v0.12.5-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.5/x64/node-v0.12.5-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.5/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.5/node-v0.12.5-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.5/node-v0.12.5-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.5/node-v0.12.5-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.5/node-v0.12.5-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.5/
+
+Website: https://nodejs.org/docs/v0.12.5/
+
+Documentation: https://nodejs.org/docs/v0.12.5/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+a31674f017aa7bfff6d73d2d62501e78e19f2856  node-v0.12.5-darwin-x64.tar.gz
+648c4da8bdb6bf0daadfa11a1f59dc5f354179f3  node-v0.12.5-darwin-x86.tar.gz
+d06b46e4b9064b12c3cdb65defaf27b968262856  node-v0.12.5-linux-x64.tar.gz
+2b5e20fcb362f34df5508b8334d52514701aa15f  node-v0.12.5-linux-x86.tar.gz
+2dbc96c33dced5dc4632588035f92afdedaf0ff0  node-v0.12.5-sunos-x64.tar.gz
+27eda0e7cd5cd748919055b22683ce0770ce1906  node-v0.12.5-sunos-x86.tar.gz
+dd45f1fad6a32686afee6fc9b3353380481a9bec  node-v0.12.5-x86.msi
+f5888618555f97c3d67366f11abaf097491ae6f4  node-v0.12.5.pkg
+baecde8c2d297aa001a2a8ba2f2d086d970a13eb  node-v0.12.5.tar.gz
+f4c8c81c60ed4ad1be2f2df93c0a99c9ba94a1e7  node.exe
+2e6912adf6b1cfa3c818770bcd3c09882afcbf7c  node.exp
+e88ff96166822f75d31b246358e13e814ddfc2d9  node.lib
+9007edd47eeaa4d14329d879f4248ac42869676f  node.pdb
+45e946f6ad94e2225c2f2c5081bd6bfa5dad3a5f  openssl-cli.exe
+27ea2047ef5ccf0ebdb8b1a9c61e0c35d36c2c6c  openssl-cli.pdb
+689e1dbedf5dac5b900584e878024ab3f31111a6  x64/node-v0.12.5-x64.msi
+00652c22276b1e7b0b307437219efc3431446100  x64/node.exe
+8888e187bfb8dc1f18f6e1284c46014bf97dbadb  x64/node.exp
+c9ba1d50d1c962c169a0d47c8ab1f834ab637621  x64/node.lib
+149ec0193bef26c57dc420dfe00f928bb4b7a579  x64/node.pdb
+5cc07312c39b18ba27229919114b6b09724c9fb3  x64/openssl-cli.exe
+590fb71ca72c876bbaad5e5ee6fe85acf406fe40  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJViGeDAAoJEFCjBR+IjGKN4OIP/iCxMMLAKTqlrSma5wiztO82
+1ff4yE8rCs0jiGZVgTucmaI7j5fGFHJi1sbsBqqAeda3IYAEq+lL180YioHR8KlS
+47cTvqeTnjIj1JhzhhRcGxs17IyK7YFJJmEQ+54XdYDB0dHDJM/UXy8ySiCxBdTf
+c1Kzi6OGp7qmSAOdIo76q63AxWzKL5jVrxkBBmtyJFr6EW4xTkz98GDLaK+GeBHT
+cdpcInYbtJpWNm/8XOfZqAR0tW4HZ6tYHuSxvaZh18YDd+SNsQgLCmR56pLEMkaw
+frgfNje37r6jjx1f1GkpbdQHSVjFUZiiwTyKP7eTDMrjttRuYZk+VUCyh/abqZZ3
+dfz9Ue22z5ZJyb9L3adrYATrGKBfkhwljcAgYCaGXOokKRZis8BkZJIQUbHI/jZr
+/p2hg413EWYoV+ra0a6qjci0JufNJ5Y+02K3XS+qr0lGS4WICEgtni3p0VhWkKO4
+ppYgJD4QhQVyH22fi0LklMoX2VO/iyDaNUKHOOHC1QnGQy/5bIGWE4IcSTWFXIpa
+hXJT/UmGe7WXup+AQ53E2jzFK2xKX5qnRBGZWjUKQE+nT4o06QNbupZfMckGc8YO
+yF1TCguhR+1oglGZbLyvPfCDuD8gJcI76LhDFkoztQbAmiNZql4CbmOw+R5ebDe+
+E2abSYUpsCAZCr+Edudl
+=Vxgb
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.6.md b/locale/uk/blog/release/v0.12.6.md
new file mode 100755
index 0000000000000..9a69bb061491d
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.6.md
@@ -0,0 +1,88 @@
+---
+date: 2015-07-04T02:34:23.000Z
+version: 0.12.6
+category: release
+title: Node v0.12.6 (Stable)
+slug: node-v0-12-6-stable
+layout: blog-post.hbs
+---
+
+This release of Node.js fixes a bug that triggers an out-of-band write in V8's
+utf-8 decoder. This bug impacts all Buffer to String conversions. This is an
+important security update as this bug can be used to cause a denial of service
+attack.
+
+2015.07.03, Version 0.12.6 (Stable)
+
+* V8: fix out-of-band write in utf8 decoder
+
+
+Source Code: https://nodejs.org/dist/v0.12.6/node-v0.12.6.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.6/node-v0.12.6.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.6/node-v0.12.6-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.6/x64/node-v0.12.6-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.6/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.6/node-v0.12.6-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.6/node-v0.12.6-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.6/node-v0.12.6-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.6/node-v0.12.6-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.6/
+
+Website: https://nodejs.org/docs/v0.12.6/
+
+Documentation: https://nodejs.org/docs/v0.12.6/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+4c7f2c26ecb37c3faf27413988daa06b2d34d86c  node-v0.12.6-darwin-x64.tar.gz
+1cf8e13dc58bae4172f17072183a811473a51f98  node-v0.12.6-darwin-x86.tar.gz
+7ac240fc08527328ed295548acdae72495eae4c9  node-v0.12.6-linux-x64.tar.gz
+042e30fe3bb89b6e9b16dcbf2d582e23920156d9  node-v0.12.6-linux-x86.tar.gz
+e285a0dc4049559adb1712475d425177db718cfe  node-v0.12.6-sunos-x64.tar.gz
+0bba5dfe3b253c9dac7fba0b8211da1fb7c66348  node-v0.12.6-sunos-x86.tar.gz
+2f2bfca619fe5dec144bc02908e8fbbe7039b7d3  node-v0.12.6-x86.msi
+617954505b0e14e97019f93e51805de0c7244809  node-v0.12.6.pkg
+a0099d22dc927e18c0e385612afdd14e9173417b  node-v0.12.6.tar.gz
+8b7079ff7b07916cc6f8c5773f4fa296b3554ba9  node.exe
+3e95afb369b4280d6d80bd8d08d011bc76a99b4d  node.exp
+1b0569e1927a0f92399f4e85c8d71c527cc04c86  node.lib
+3806b90544b8d36c83fd0939cea939b47a704e17  node.pdb
+9a14f0286179b86434e1863a77fdac43b8175511  openssl-cli.exe
+8f051e9d75df074a89fb8f317c0ccac62f21c219  openssl-cli.pdb
+4c22a0c3860b17f1d7d1338c70723bce6c1f5a73  x64/node-v0.12.6-x64.msi
+30b4219fcdd1845915d783b5a390ed7d7a0a7802  x64/node.exe
+561dbf27a64932b2d5c74883bd7023c0029ac184  x64/node.exp
+424206c71c4bda5fc40b3e189d0be35763afd291  x64/node.lib
+d84c6d0e754b2b3380f400f602a8c5db4485822d  x64/node.pdb
+3a0ff161d82f3dea3d061862b05fd4b7843f0115  x64/openssl-cli.exe
+6de5fc6adb9ebb7ab27da074a8eacf6bcf2f21f8  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVl0YfAAoJEFCjBR+IjGKNm2MP/3d2JyJlA4d+frA5cZhSL22W
+KneQKNn4riWDj6OMUsFTw4IEagrec0eHUEWjk20Lk1xsChkTEnC3XT72VGYC61Yh
+PEAxllVLR2QdEMV+yqGoPr4PEnkYNYJEf6DVaKWnhy4QwhGxqa1m008eT0aqfBHq
+bzaz4wOaWoH9eKo5Hx/9DNaNphxtt5CkPTCbLjMH8X/fVAfXE1vnr+ZYHpyR6qVW
+TyFWjwdDwbtfQm2iAIs2mXIUviCrkjSDNsXlrHqlGLVIiBf0isnzXnZMpduDHRU1
+Wq2pMGz4m4nHyalHmJriKhf3XG1M3qF59fUC1WteeEBJXvq5nATXV664fbtrRvmp
+P/LpU+gnFeX/lj3ut1AyVBcMTSYC99igkPQyU8a5L4d0D0TPHS6X/AkQVQfsjv7p
+9YaXCr1tbWf6xRqijt6bP8jeQ5BDZQ2Xr7rpefCRrdSKrCRCQ63chK8iWhf5CtWu
+zQNOmitHgshR5RPSdYDSmklrycPQOTraStPD7UfN3GewkahvuGjd3JXHMBskrY/e
+WSm6jb7C2xSqL9SrfS+4aQ24Ombh8TyqxgEytZ0vYPpT+BUC91Ifk4lp54CGhmlX
+JlPh1rFL07wYUdd5OWRtnJntlvOQaVM1VlUZEUv+ri/enp8Nxzt7A6Y7JfnmdHE2
+yqbPp1djFFWrTZ3du0Ed
+=jCxm
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.7.md b/locale/uk/blog/release/v0.12.7.md
new file mode 100755
index 0000000000000..a2b3acb4a6999
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.7.md
@@ -0,0 +1,94 @@
+---
+date: 2015-07-09T23:51:47.000Z
+version: 0.12.7
+category: release
+title: Node v0.12.7 (Stable)
+slug: node-v0-12-7-stable
+layout: blog-post.hbs
+---
+
+In addition to upgrading npm and fixing a couple of bugs, this release
+upgrades OpenSSL to version 1.0.1p, which fixes a security vulnerability
+(CVE-2015-1793). More details about the vulnerability can be found [on
+OpenSSL's website](http://openssl.org/news/secadv_20150709.txt).
+
+2015.07.09, Version 0.12.7 (Stable)
+
+* openssl: upgrade to 1.0.1p (CVE-2015-1793)
+
+* npm: upgrade to 2.11.3
+
+* V8: cherry-pick JitCodeEvent patch from upstream (Ben Noordhuis)
+
+* win,msi: create npm folder in AppData directory (Steven Rockarts)
+
+
+Source Code: https://nodejs.org/dist/v0.12.7/node-v0.12.7.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.12.7/node-v0.12.7.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.12.7/node-v0.12.7-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.12.7/x64/node-v0.12.7-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.12.7/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.7/node-v0.12.7-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.7/node-v0.12.7-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.12.7/node-v0.12.7-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.12.7/node-v0.12.7-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.12.7/
+
+Website: https://nodejs.org/docs/v0.12.7/
+
+Documentation: https://nodejs.org/docs/v0.12.7/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+37af2e7e748a81921f8956f1938dc5977e422ed8  node-v0.12.7-darwin-x64.tar.gz
+8bf1caba4d474bfbff75a75c6b3fc1e413e34a8e  node-v0.12.7-darwin-x86.tar.gz
+0a861a6ded50c8cda32ac39c3a54699c767742e6  node-v0.12.7-linux-x64.tar.gz
+cb2ba2e004fc03f634e56618194e4c2c025cfe22  node-v0.12.7-linux-x86.tar.gz
+eb79ed6811ce07743d64b3fb16d762dcbb40a91f  node-v0.12.7-sunos-x64.tar.gz
+5a706660fd9392274c8c7d8f21bcebbf7735d1f4  node-v0.12.7-sunos-x86.tar.gz
+7aa06c0d54c97e5193bafc927dbe1bede308da97  node-v0.12.7-x86.msi
+f6d9b8865905f4f419a9228a960af061f69a6fd5  node-v0.12.7.pkg
+6d59007212a964c7a4defc5520aedacdbcb008e1  node-v0.12.7.tar.gz
+fac6dbd4b88451228b93d8c217b20de2759cb116  node.exe
+05ceb63dce379bc71c9726635efcb95983bac891  node.exp
+4b38821ec6ca2dd77637516f11f92637551987ce  node.lib
+a7c984b68063571f53bc5782cf30c94f1b32d2ec  node.pdb
+cb10067b40b9db47ed1873850ddc96d0c913e985  openssl-cli.exe
+bad044c9864ba0181094bbc6d9f6ebe55ceb9e91  openssl-cli.pdb
+05cfffda323563c42ff2e461a8e98ee984ad15d1  x64/node-v0.12.7-x64.msi
+55e8a906450bf7027808e6cdff259bafd1844306  x64/node.exe
+7c04fddb306c69d1701cf2f52cc89c6098894d6f  x64/node.exp
+ac2985d01aa77eef104db97d583eef5018430a1b  x64/node.lib
+8761ac5ad6074e7c559641572cf19ca2f3e8ea98  x64/node.pdb
+6724328166b1e3a2c967023759ee50d0c2d076b3  x64/openssl-cli.exe
+e377127c7c2d5eae46228074879c6fa77d9fa221  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJVnwkCAAoJEFCjBR+IjGKN48IP/A2aw749kfIzMN5X1x90rTfu
+1OoMPFyp5a3Tg4nq9cbiBHQd6oWsMOqiPLiK+cgxtFtPz9cMTvJwDtZlcE6jD+5T
+Dbo756zmUGz3euJcpKGVag/Nr+hx8X7ADHLdbaHv5RmJ17aQ/zIRxe9lt+8xrK0g
+Ms4my5QfJV5w7+eheDw8/71vHSaUoGbW44PWV98ub74NPdPLnlyvRIFqs//rRahX
+VduAq/BepH3CWhTEgMeMu4fEPLiIXgEna5GaFQ1zg5/B4XaJuFNiDP6xede7VQwt
+VkwtrTl1yMkH6Guw6f0hrdFalTa3E9SELIQCnZDKj2fT3eJUdtHg82TmrIU/v934
+FOFNSU07CJOI8H3cFPEgFtbf05Eyh2axZq/GFvgTMIKpaAtK66RF4/vpoWvezyK0
+yIou+59zhL2n3tdO5OUZzZ47843sT2UXH+pOB7xmCu4EYhCve0pPZf30UXzYU46P
+RQEsLRIhVPPYszCnStYMWroLBF2zfprbn5pILCYtJbeafFz3U20IbFgPhc7xnWtQ
+FiJS0lNdjc8B0yZIiTg59FyudADojWu37gXCYGlD9pyb03GSzG7CIPr206rNwjcR
+gW0cbSCtfDdiTo0Za6+ZZdhMW2mf+7MwW2LdXiJiWasj8gAQeIXqXJiWdxQLb2ZV
+uAV+X2VgKWk7UCom3i/Y
+=fmln
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.8.md b/locale/uk/blog/release/v0.12.8.md
new file mode 100755
index 0000000000000..7dfa825260551
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.8.md
@@ -0,0 +1,150 @@
+---
+date: 2015-11-24T23:59:09.993Z
+version: v0.12.8
+category: release
+title: Node v0.12.8 (LTS)
+slug: node-v0-12-8
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+This release of v0.12.8 represents the first release of the v0.12 line since it has moved from _Stable_ to _LTS_ (Long-term Support) status. According to the new [LTS plan](https://github.com/nodejs/LTS/#readme) for the Node.js project, v0.12 will continue as LTS until the end of 2015 at which point it will switch to _Maintenance_ and continue as such until the end of 2016 when support will cease.
+
+During LTS, changes included in v0.12.x releases will be limited to bug fixes, security updates, npm updates (limited to npm v2 LTS), documentation updates, and certain performance improvements that can be demonstrated to not break existing applications. After moving to Maintenance mode at the end of 2015, only critical bugs, critical security fixes, and documentation updates will be included.
+
+The Node.js core team will continue to ensure that v0.12 remains a viable platform for production deployment until the end of 2016. However, users of v0.12 should be working on plan to migrate to at least v4 LTS (Argon) as soon as practical.
+
+## New build infrastructure
+
+This is the first v0.12 release made with the new build infrastructure operated by the Node.js Foundation. Even though we have done our best to ensure that the build processes and tools are as close as possible to the previous infrastructure, it is possible that some unexpected issues arise from the changes. Please file bug reports on the [Node.js GitHub repository](https://github.com/nodejs/node) if you have trouble upgrading from v0.12.7 to v0.12.8.
+
+## Commits
+
+* [[`7d11208f68`](https://github.com/nodejs/node/commit/7d11208f68)] - **build**: backport tools/release.sh (Rod Vagg) [#3642](https://github.com/nodejs/node/pull/3642)
+* [[`6fb0b92fa0`](https://github.com/nodejs/node/commit/6fb0b92fa0)] - **build**: backport config for new CI infrastructure (Rod Vagg) [#3642](https://github.com/nodejs/node/pull/3642)
+* [[`83441616a5`](https://github.com/nodejs/node/commit/83441616a5)] - **build**: fix --without-ssl compile time error (Ben Noordhuis) [#3825](https://github.com/nodejs/node/pull/3825)
+* [[`8887666b0b`](https://github.com/nodejs/node/commit/8887666b0b)] - **build**: update manifest to include Windows 10 (Lucien Greathouse) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`08afe4ec8e`](https://github.com/nodejs/node/commit/08afe4ec8e)] - **build**: add MSVS 2015 support (Rod Vagg) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`4f2456369c`](https://github.com/nodejs/node/commit/4f2456369c)] - **build**: work around VS2015 issue in ICU <56 (Steven R. Loomis) [nodejs/node-v0.x-archive#25804](https://github.com/nodejs/node-v0.x-archive/pull/25804)
+* [[`15030f26fd`](https://github.com/nodejs/node/commit/15030f26fd)] - **build**: Intl: bump ICU4C from 54 to 55 (backport) (Steven R. Loomis) [nodejs/node-v0.x-archive#25856](https://github.com/nodejs/node-v0.x-archive/pull/25856)
+* [[`1083fa70f0`](https://github.com/nodejs/node/commit/1083fa70f0)] - **build**: run-ci makefile rule (Alexis Campailla) [nodejs/node-v0.x-archive#25653](https://github.com/nodejs/node-v0.x-archive/pull/25653)
+* [[`2d2494cf14`](https://github.com/nodejs/node/commit/2d2494cf14)] - **build**: support flaky tests in test-ci (Alexis Campailla) [nodejs/node-v0.x-archive#25653](https://github.com/nodejs/node-v0.x-archive/pull/25653)
+* [[`b25d26f2ef`](https://github.com/nodejs/node/commit/b25d26f2ef)] - **build**: support Jenkins via test-ci (Alexis Campailla) [nodejs/node-v0.x-archive#25653](https://github.com/nodejs/node-v0.x-archive/pull/25653)
+* [[`7e4b47f38a`](https://github.com/nodejs/node/commit/7e4b47f38a)] - **build,win**: fix node.exe resource version (João Reis) [#3053](https://github.com/nodejs/node/pull/3053)
+* [[`e07c86e240`](https://github.com/nodejs/node/commit/e07c86e240)] - **build,win**: try next MSVS version on failure (João Reis) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`b5a0abcfdf`](https://github.com/nodejs/node/commit/b5a0abcfdf)] - **child_process**: clone spawn options argument (cjihrig) [nodejs/node-v0.x-archive#9159](https://github.com/nodejs/node-v0.x-archive/pull/9159)
+* [[`8b81f98c41`](https://github.com/nodejs/node/commit/8b81f98c41)] - **configure**: add --without-mdb flag (cgalibern) [nodejs/node-v0.x-archive#25707](https://github.com/nodejs/node-v0.x-archive/pull/25707)
+* [[`071c860c2b`](https://github.com/nodejs/node/commit/071c860c2b)] - **crypto**: replace rwlocks with simple mutexes (Ben Noordhuis) [#2723](https://github.com/nodejs/node/pull/2723)
+* [[`ca97fb6be3`](https://github.com/nodejs/node/commit/ca97fb6be3)] - **deps**: upgrade npm to 2.14.9 (Forrest L Norvell) [#3684](https://github.com/nodejs/node/pull/3684)
+* [[`583734342e`](https://github.com/nodejs/node/commit/583734342e)] - **deps**: fix openssl for MSVS 2015 (Andy Polyakov) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`02c262a4c6`](https://github.com/nodejs/node/commit/02c262a4c6)] - **deps**: fix gyp to work on MacOSX without XCode (Shigeki Ohtsu) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`f0fba0bce8`](https://github.com/nodejs/node/commit/f0fba0bce8)] - **deps**: update gyp to 25ed9ac (João Reis) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`f693565813`](https://github.com/nodejs/node/commit/f693565813)] - **deps**: upgrade to npm 2.13.4 (Kat Marchán) [nodejs/node-v0.x-archive#25825](https://github.com/nodejs/node-v0.x-archive/pull/25825)
+* [[`618b142679`](https://github.com/nodejs/node/commit/618b142679)] - **deps,v8**: fix compilation in VS2015 (João Reis) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`64459c0fe8`](https://github.com/nodejs/node/commit/64459c0fe8)] - **doc**: backport README.md (Rod Vagg) [#3642](https://github.com/nodejs/node/pull/3642)
+* [[`2860c53562`](https://github.com/nodejs/node/commit/2860c53562)] - **doc**: fixed child_process.exec doc (Tyler Anton) [nodejs/node-v0.x-archive#14088](https://github.com/nodejs/node-v0.x-archive/pull/14088)
+* [[`4a91fa11a3`](https://github.com/nodejs/node/commit/4a91fa11a3)] - **doc**: Update docs for os.platform() (George Kotchlamazashvili) [nodejs/node-v0.x-archive#25777](https://github.com/nodejs/node-v0.x-archive/pull/25777)
+* [[`b03ab02fe8`](https://github.com/nodejs/node/commit/b03ab02fe8)] - **doc**: Change the link for v8 docs to v8dox.com (Chad Walker) [nodejs/node-v0.x-archive#25811](https://github.com/nodejs/node-v0.x-archive/pull/25811)
+* [[`1fd8f37efd`](https://github.com/nodejs/node/commit/1fd8f37efd)] - **doc**: buffer, adding missing backtick (Dyana Rose) [nodejs/node-v0.x-archive#25811](https://github.com/nodejs/node-v0.x-archive/pull/25811)
+* [[`162d0db3bb`](https://github.com/nodejs/node/commit/162d0db3bb)] - **doc**: tls.markdown, adjust version from v0.10.39 to v0.10.x (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`eda2560cdc`](https://github.com/nodejs/node/commit/eda2560cdc)] - **doc**: additional refinement to readable event (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`881d9bea01`](https://github.com/nodejs/node/commit/881d9bea01)] - **doc**: readable event clarification (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`b6378f0c75`](https://github.com/nodejs/node/commit/b6378f0c75)] - **doc**: stream.unshift does not reset reading state (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`4952e2b4d2`](https://github.com/nodejs/node/commit/4952e2b4d2)] - **doc**: clarify Readable._read and Readable.push (fresheneesz) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`14000b97d4`](https://github.com/nodejs/node/commit/14000b97d4)] - **doc**: two minor stream doc improvements (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`6b6bd21497`](https://github.com/nodejs/node/commit/6b6bd21497)] - **doc**: Clarified read method with specified size argument. (Philippe Laferriere) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`16f547600a`](https://github.com/nodejs/node/commit/16f547600a)] - **doc**: Document http.request protocol option (Ville Skyttä) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`618e4ecda9`](https://github.com/nodejs/node/commit/618e4ecda9)] - **doc**: add a note about readable in flowing mode (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`0b165be37b`](https://github.com/nodejs/node/commit/0b165be37b)] - **doc**: fix line wrapping in buffer.markdown (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`70dd13f88d`](https://github.com/nodejs/node/commit/70dd13f88d)] - **doc**: add CleartextStream deprecation notice (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`418cde0765`](https://github.com/nodejs/node/commit/418cde0765)] - **doc**: mention that mode is ignored if file exists (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`85bcb281e4`](https://github.com/nodejs/node/commit/85bcb281e4)] - **doc**: improve http.abort description (James M Snell) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`5ccb429ee8`](https://github.com/nodejs/node/commit/5ccb429ee8)] - **doc, comments**: Grammar and spelling fixes (Ville Skyttä) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`a24db43101`](https://github.com/nodejs/node/commit/a24db43101)] - **docs**: event emitter behavior notice (Samuel Mills (Henchman)) [nodejs/node-v0.x-archive#25467](https://github.com/nodejs/node-v0.x-archive/pull/25467)
+* [[`8cbf7cb021`](https://github.com/nodejs/node/commit/8cbf7cb021)] - **docs**: events clarify emitter.listener() behavior (Benjamin Steephenson) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`b7229debbe`](https://github.com/nodejs/node/commit/b7229debbe)] - **docs**: Fix default options for fs.createWriteStream() (Chris Neave) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`f0453caea2`](https://github.com/nodejs/node/commit/f0453caea2)] - **domains**: port caeb677 from v0.10 to v0.12 (Jeremy Whitlock) [nodejs/node-v0.x-archive#25835](https://github.com/nodejs/node-v0.x-archive/pull/25835)
+* [[`261fa3620f`](https://github.com/nodejs/node/commit/261fa3620f)] - **src**: fix intermittent SIGSEGV in resolveTxt (Evan Lucas) [nodejs/node-v0.x-archive#9300](https://github.com/nodejs/node-v0.x-archive/pull/9300)
+* [[`1f7257b02d`](https://github.com/nodejs/node/commit/1f7257b02d)] - **test**: mark test-https-aws-ssl flaky on linux (João Reis) [nodejs/node-v0.x-archive#25893](https://github.com/nodejs/node-v0.x-archive/pull/25893)
+* [[`cf435d55db`](https://github.com/nodejs/node/commit/cf435d55db)] - **test**: mark test-signal-unregister as flaky (Alexis Campailla) [nodejs/node-v0.x-archive#25750](https://github.com/nodejs/node-v0.x-archive/pull/25750)
+* [[`ceb6a8c131`](https://github.com/nodejs/node/commit/ceb6a8c131)] - **test**: fix test-debug-port-from-cmdline (João Reis) [nodejs/node-v0.x-archive#25748](https://github.com/nodejs/node-v0.x-archive/pull/25748)
+* [[`22997731e6`](https://github.com/nodejs/node/commit/22997731e6)] - **test**: add regression test for #25735 (Fedor Indutny) [nodejs/node-v0.x-archive#25739](https://github.com/nodejs/node-v0.x-archive/pull/25739)
+* [[`39e05639f4`](https://github.com/nodejs/node/commit/39e05639f4)] - **test**: mark http-pipeline-flood flaky on win32 (Julien Gilli) [nodejs/node-v0.x-archive#25707](https://github.com/nodejs/node-v0.x-archive/pull/25707)
+* [[`78d256e7f5`](https://github.com/nodejs/node/commit/78d256e7f5)] - **test**: unmark tests that are no longer flaky (João Reis) [nodejs/node-v0.x-archive#25676](https://github.com/nodejs/node-v0.x-archive/pull/25676)
+* [[`a9b642cf5b`](https://github.com/nodejs/node/commit/a9b642cf5b)] - **test**: runner should return 0 on flaky tests (Alexis Campailla) [nodejs/node-v0.x-archive#25653](https://github.com/nodejs/node-v0.x-archive/pull/25653)
+* [[`b48639befd`](https://github.com/nodejs/node/commit/b48639befd)] - **test**: support writing test output to file (Alexis Campailla) [nodejs/node-v0.x-archive#25653](https://github.com/nodejs/node-v0.x-archive/pull/25653)
+* [[`caa16b41d6`](https://github.com/nodejs/node/commit/caa16b41d6)] - **(SEMVER-MINOR)** **tls**: prevent server from using dhe keys < 768 (Michael Dawson) [#3890](https://github.com/nodejs/node/pull/3890)
+* [[`0363cf4a80`](https://github.com/nodejs/node/commit/0363cf4a80)] - **tls**: Closing parent socket also closes the tls sock (Devin Nakamura) [nodejs/node-v0.x-archive#25642](https://github.com/nodejs/node-v0.x-archive/pull/25642)
+* [[`75697112e8`](https://github.com/nodejs/node/commit/75697112e8)] - **tls**: do not hang without `newSession` handler (Fedor Indutny) [nodejs/node-v0.x-archive#25739](https://github.com/nodejs/node-v0.x-archive/pull/25739)
+* [[`d998a65058`](https://github.com/nodejs/node/commit/d998a65058)] - **tools**: pass constant to logger instead of string (Johan Bergström) [nodejs/node-v0.x-archive#25653](https://github.com/nodejs/node-v0.x-archive/pull/25653)
+* [[`1982ed6e63`](https://github.com/nodejs/node/commit/1982ed6e63)] - **v8**: port fbff705 from v0.10 to v0.12 (Jeremy Whitlock) [nodejs/node-v0.x-archive#25835](https://github.com/nodejs/node-v0.x-archive/pull/25835)
+* [[`44d7054252`](https://github.com/nodejs/node/commit/44d7054252)] - **win**: fix custom actions for WiX older than 3.9 (João Reis) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`586c4d8b8e`](https://github.com/nodejs/node/commit/586c4d8b8e)] - **win**: fix custom actions on Visual Studio != 2013 (Julien Gilli) [#2843](https://github.com/nodejs/node/pull/2843)
+* [[`14db629497`](https://github.com/nodejs/node/commit/14db629497)] - **win,msi**: correct installation path registry keys (João Reis) [nodejs/node-v0.x-archive#25640](https://github.com/nodejs/node-v0.x-archive/pull/25640)
+* [[`8e80528453`](https://github.com/nodejs/node/commit/8e80528453)] - **win,msi**: change InstallScope to perMachine (João Reis) [nodejs/node-v0.x-archive#25640](https://github.com/nodejs/node-v0.x-archive/pull/25640)
+* [[`35bbe98401`](https://github.com/nodejs/node/commit/35bbe98401)] - Update addons.markdown (Max Deepfield) [nodejs/node-v0.x-archive#25885](https://github.com/nodejs/node-v0.x-archive/pull/25885)
+* [[`9a6f1ce416`](https://github.com/nodejs/node/commit/9a6f1ce416)] - comma (Julien Valéry) [nodejs/node-v0.x-archive#25811](https://github.com/nodejs/node-v0.x-archive/pull/25811)
+* [[`d384bf8f84`](https://github.com/nodejs/node/commit/d384bf8f84)] - Update assert.markdown (daveboivin) [nodejs/node-v0.x-archive#25811](https://github.com/nodejs/node-v0.x-archive/pull/25811)
+* [[`89b22ccbe1`](https://github.com/nodejs/node/commit/89b22ccbe1)] - Fixed typo (Andrew Murray) [nodejs/node-v0.x-archive#25811](https://github.com/nodejs/node-v0.x-archive/pull/25811)
+* [[`5ad05af380`](https://github.com/nodejs/node/commit/5ad05af380)] - Update util.markdown (Daniel Rentz) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`cb660ab3d3`](https://github.com/nodejs/node/commit/cb660ab3d3)] - Update child_process.markdown, spelling (Jared Fox) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`59c67fe3cd`](https://github.com/nodejs/node/commit/59c67fe3cd)] - updated documentation for fs.createReadStream (Michele Caini) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`53b6a615a5`](https://github.com/nodejs/node/commit/53b6a615a5)] - Documentation update about Buffer initialization (Sarath) [nodejs/node-v0.x-archive#25591](https://github.com/nodejs/node-v0.x-archive/pull/25591)
+* [[`b8d47a7b6f`](https://github.com/nodejs/node/commit/b8d47a7b6f)] - fix (Fedor Indutny) [nodejs/node-v0.x-archive#25739](https://github.com/nodejs/node-v0.x-archive/pull/25739)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.8/node-v0.12.8-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.8/x64/node-v0.12.8-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.8/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.8/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.8/node-v0.12.8.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.8/node-v0.12.8-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.8/node-v0.12.8-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.8/node-v0.12.8-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.8/node-v0.12.8-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.8/node-v0.12.8-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.8/node-v0.12.8-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.8/node-v0.12.8.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.8/<br>
+Documentation: https://nodejs.org/docs/v0.12.8/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+c510a03310053182b20af10e4400877421255c1a72d9c98d8ad87bb7602fcdf5  node.exe
+495c1e492874bac2cdaf0bbb6507476bc33ec2b8c30799d9dc50692d4d5ab553  node.exp
+60d6248a9073130e6c16ae79eafcce53acabe5565249364855242e15aa7de86b  node.lib
+aa790268a830e32678a851356dc9a848b2caa26b64ccf2a897f9a63447322cc0  node.pdb
+857155d09d62b59c675baf4091a4e76af0972f8c99a26259a18e3ac99575697b  node-v0.12.8-darwin-x64.tar.gz
+2ec14c53fa69836caf79822b2de071659fadb2c105b1344371b404df398bad39  node-v0.12.8-darwin-x86.tar.gz
+9ad0c77d0c5c2236ba42519dbd7375e9462412e812b6c60e776fcc129ef97084  node-v0.12.8-headers.tar.gz
+99f9f8792850867a21caeaf12b1f84da9f64d0cf0ac602920facc0fc4b81e8b4  node-v0.12.8-linux-x64.tar.gz
+b82e3b4a01f9be1f130d97cf6a8534ae727396448fb1bfeb7eb74ec58592bd88  node-v0.12.8-linux-x86.tar.gz
+94c46f6418175d43b47229b57d54c25d2ed9bb9a6cd51331de0c3b7df86be1e2  node-v0.12.8.pkg
+c8ca60698f99b7dc7722b94c5b4110636d08d3a20cb3df80807bd420e2c34376  node-v0.12.8-sunos-x64.tar.gz
+8d9553a684b6717f0f0f2f5dcc8ed78139db50129e1402ce6033e2494c06cfd3  node-v0.12.8-sunos-x86.tar.gz
+e0c96a6702978e2ed7f031315bebeb86b042e2c80e66d99af8ad864dc0e56436  node-v0.12.8.tar.gz
+d9c97de01f95bd99fcb9a21dc36db1916c46db6a4b1992f235c01acc1dba8b0c  node-v0.12.8-x86.msi
+4ce3651ccb4c0c3ffc968d2580ea9cd219a4697b0bd3e3c18b3e478d80402cfe  openssl-cli.exe
+745e656d36508a38ec307a81f540425d3e0befa1c8614d86cdc3dcb38de2cd3c  openssl-cli.pdb
+5d0455af75857a96d53593f23defb38e55706697cd638e0b442f6d7208864256  x64/node.exe
+c546e1e8f21ac580c30b8ca7d1653b180b6dd9ba07cca0fd661fa5c0c432f4f4  x64/node.exp
+44173c6b7b0978e28bb78b865954ec8d68a9b8843daf8586c67b520bc4f0c0a6  x64/node.lib
+f5f0ba7d83ff186fed1bae22700218d406335f8a668975993c0a94ec6fc4a959  x64/node.pdb
+d0b235299d85527b30f5901e059b4f56cf289b1f99d49d404b7776aa53f873f1  x64/node-v0.12.8-x64.msi
+2dc5b7ceaa8ae58d77c00701d97c5d52c2d369410f94a1b3f43b4e6aa7e01c3d  x64/openssl-cli.exe
+8bbc2c70d4afa149b58f60aa8ca5d835540a46bb92759b950a9d18c626db329f  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWVPhlAAoJEMJzeS99g1RdJlsIAN9VwrQTaxTbUcenm2KPUMPA
+1Va6Fj3BBERCTPuHxLf+XJIAz9qlMsJLRU1y7tqdzjUKDWBf5007RYY5KGmc0m0H
+oKKu1lnT+jc87IAYveBD/QldXibPwCc9e0rou7iO3OUPtttXRHlSMw/tYSkzg2ba
+x3E/wCQlNQmrAOrRdBd0Qzi3nlnosIWAoCMp8Hbw0TkjUD4LOq0zFCl/5AK+qnB6
+jiXpSWNXTciOhRb779NmF7UHYbrdjeEhOxcLE8ODq9U4PsBZXVZKaU2rQ4Lp/CAk
+wabJBZ3RQKT6okzbhlz0TbgbsjZ4VeVCpDJWVA4gBlEboXDoF9IWJ37hu+qqEaE=
+=vHgI
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.12.9.md b/locale/uk/blog/release/v0.12.9.md
new file mode 100755
index 0000000000000..de586b5e43b4b
--- /dev/null
+++ b/locale/uk/blog/release/v0.12.9.md
@@ -0,0 +1,79 @@
+---
+date: 2015-12-04T03:02:00.000Z
+version: 0.12.9
+category: release
+title: Node v0.12.9 (LTS)
+slug: node-v0-12-9
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+**This is an important security release**. All Node.js users should consult our [December Security Release Summary](/en/blog/vulnerability/december-2015-security-releases/) for details on patched vulnerabilities.
+
+### Notable changes
+
+* **http**: Fix a bug where an HTTP socket may no longer have an associated parser but a pipelined request triggers a pause or resume, a potential denial-of-service vector. (Fedor Indutny)
+* **openssl**: Upgrade to 1.0.1q, fixes CVE-2015-3194 "Certificate verify crash with missing PSS parameter", a potential denial-of-service vector for Node.js TLS servers using client authentication; TLS clients are also impacted. Details are available at <http://openssl.org/news/secadv/20151203.txt>. (Ben Noordhuis) https://github.com/nodejs/node/pull/4133
+
+### Commits
+
+* [[`8d24a14f2c`](https://github.com/nodejs/node/commit/8d24a14f2c)] - **deps**: upgrade to openssl 1.0.1q (Ben Noordhuis) [#4133](https://github.com/nodejs/node/pull/4133)
+* [[`dfc6f4a9af`](https://github.com/nodejs/node/commit/dfc6f4a9af)] - **http**: fix pipeline regression (Fedor Indutny)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v0.12.9/node-v0.12.9-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v0.12.9/x64/node-v0.12.9-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v0.12.9/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v0.12.9/x64/node.exe<br>
+Mac OS X Universal Installer: https://nodejs.org/dist/v0.12.9/node-v0.12.9.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v0.12.9/node-v0.12.9-darwin-x64.tar.gz<br>
+Mac OS X 32-bit Binary: https://nodejs.org/dist/v0.12.9/node-v0.12.9-darwin-x86.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v0.12.9/node-v0.12.9-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v0.12.9/node-v0.12.9-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.12.9/node-v0.12.9-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.12.9/node-v0.12.9-sunos-x64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v0.12.9/node-v0.12.9.tar.gz<br>
+Other release files: https://nodejs.org/dist/v0.12.9/<br>
+Documentation: https://nodejs.org/docs/v0.12.9/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+ca0bb8e1a2c1e5c23bbd1f8f6e4859f279532a820767f2a356fafd74c7a96dc9  node.exe
+9a197cf39b61dec42fcdccf3b3f6f3289c9720186647d4474e39fa0e575bb0a6  node.exp
+3ece6db1d6dc791c414d84324f41d3b3bae6ae57bd1c6185e9fb1802fbc5ef37  node.lib
+c8435274e80cdb80cced49ef724f3c53b3f1439eb3b8fca022f0b18b4bcea3b7  node.pdb
+8a40582c8f346f4acb08ab29bdc171db5fea55603999e02be1ebfcdd2ed3ca83  node-v0.12.9-darwin-x64.tar.gz
+a89d21abe0eaae1fd4cd4753a7ccde5bb60188148742281f1b36830bb02d50fd  node-v0.12.9-darwin-x86.tar.gz
+0da8dd9dd5bbfa821d4e957a0687f3cc39bc6cbc45f75d6751107142141426ca  node-v0.12.9-headers.tar.gz
+3416451924c9c996e1d7224f5e5507df84b90dc730d4760e3f4daac1bd4c44df  node-v0.12.9-linux-x64.tar.gz
+07b25b4a886b1b04d427b2b6414c9e4a913f53bb9574c26f010b35984b70df10  node-v0.12.9-linux-x86.tar.gz
+8fa10d973e2dc7296fb5620ddede5a55e87a332762593437ab8db61051045e67  node-v0.12.9.pkg
+460a75865d6155dc39794204214c567a239b319122caf116a60f870f0987b720  node-v0.12.9-sunos-x64.tar.gz
+039c710094ac76bea7027cf37daceb5708e46cac0bd082d7004c9710ad77ad1f  node-v0.12.9-sunos-x86.tar.gz
+35daad301191e5f8dd7e5d2fbb711d081b82d1837d59837b8ee224c256cfe5e4  node-v0.12.9.tar.gz
+1f57e2fff78519569abced323c6206fc1bd32a1d374c6a05537b2873a88a7928  node-v0.12.9-x86.msi
+a765092067696be8b49736b6fce2986350a1c7581be105cf935d85636bbe809e  openssl-cli.exe
+ee5c379a4a6f5d8640af18d811566b5dacd0ae242e70928114b95825bacd3fd4  openssl-cli.pdb
+e8b4a1307332a65c5c699c1b4a4006ffd12f187a3ab9cad8f5d8e2c408a488e6  x64/node.exe
+8eb895b612690d8ab2fd06c89d3f289f4e07a9a9292bb9f8cd6c6b8cc09bd05d  x64/node.exp
+e12d3ae12103ab7d879f4c1f6ac1da77239c73cc4599fe142a7b465837ce23b6  x64/node.lib
+a2d7f30af6c1e97e306cc3481e4caa2fa7e8380344acee9f8e25a6121a2df01a  x64/node.pdb
+0d9913cb6ec8f0ea0cc9718e569a465397884b8a68863e21276866b8d394553f  x64/node-v0.12.9-x64.msi
+8943965f64d7495c6e8097916558826095472ecf64cd9bdc6ea52bd706aa086f  x64/openssl-cli.exe
+98ad5e5ff48f486a0844db9398776021c3ba23c384d3a7a2d1229e37563394c2  x64/openssl-cli.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWYPz5AAoJEMJzeS99g1RdYvMH/jyTZyBiFjtNrkETy4BlfhMr
+LYmB22yTK9wTyb4SNwta1TO8WXOHg9NwH4VVAHXgBrMeIpgV8DJyGjHW2AhibFyB
+NohDdcyIbzCciR07AsA9Vqa1u9ZFUNLzH/+5389eIINyhJTUB1gtlKxX/IbQ+luS
++Iy99sEu8RiaOmwus7vsY0agvatm7k8nUOVheQlXUh8OH3nYxqDKzTxdzxJm1j9k
+cL0RWYErA5b/LRLeRAHJG9uz81Jd/EiArhe+7FBLTrJVl69Ruk/nPeUrbKR/D2MC
+Kjd5mEfYSGwDV9YcGecLDq7CQAhscaBqQyFoynE8dOB46wW2PyV9NkYPC5TP9RE=
+=F7h4
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.4.10.md b/locale/uk/blog/release/v0.4.10.md
new file mode 100755
index 0000000000000..53b1642cc0288
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.10.md
@@ -0,0 +1,28 @@
+---
+version: 0.4.10
+title: Node v0.4.10
+author: ryandahl
+date: 2011-07-20T14:36:38.000Z
+status: publish
+category: release
+slug: node-v0-4-10
+layout: blog-post.hbs
+---
+
+2011.07.19, Version 0.4.10 (stable)
+<ul><li>#394 Fix Buffer drops last null character in UTF-8
+<li>#829 Backport r8577 from V8 (Ben Noordhuis)
+<li>#877 Don't wait for HTTP Agent socket pool to establish connections.
+<li>#915 Find kqueue on FreeBSD correctly (Brett Kiefer) 
+<li>#1085 HTTP: Fix race in abort/dispatch code (Stefan Rusu)
+<li>#1274 debugger improvement (Yoshihiro Kikuchi)
+<li>#1291 Properly respond to HEAD during end(body) hot path (Reid Burke)
+<li>#1304 TLS: Fix race in abort/connection code (Stefan Rusu)
+<li>#1360 Allow _ in url hostnames.
+<li>Revert 37d529f8 - unbreaks debugger command parsing.
+<li>Bring back global execScript
+<li>Doc improvements</ul>
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.10.tar.gz">https://nodejs.org/dist/node-v0.4.10.tar.gz</a>
+Website: <a href="https://nodejs.org/docs/v0.4.10">https://nodejs.org/docs/v0.4.10</a>
+Documentation: <a href="https://nodejs.org/docs/v0.4.10/api">https://nodejs.org/docs/v0.4.10/api</a>
diff --git a/locale/uk/blog/release/v0.4.11.md b/locale/uk/blog/release/v0.4.11.md
new file mode 100755
index 0000000000000..c0508d42cb680
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.11.md
@@ -0,0 +1,42 @@
+---
+version: 0.4.11
+title: Node v0.4.11
+author: ryandahl
+date: 2011-08-18T08:44:42.000Z
+status: publish
+category: release
+slug: node-v0-4-11
+layout: blog-post.hbs
+---
+
+2011.08.17, Version 0.4.11 (stable)
+<ul><li><a href="http://github.com/joyent/node/issues/738">#738</a> Fix crypto encryption/decryption with Base64. (SAWADA Tadashi)
+
+<li><a href="http://github.com/joyent/node/issues/1202">#1202</a> net.createConnection defer DNS lookup error events to next tick (Ben Noordhuis)
+
+<li><a href="http://github.com/joyent/node/issues/1374">#1374</a> fix setting ServerResponse.statusCode in writeHead (Trent Mick)
+
+<li><a href="http://github.com/joyent/node/issues/1417">#1417</a> Fix http.ClientRequest crashes if end() was called twice
+
+<li><a href="http://github.com/joyent/node/issues/1497">#1497</a> querystring: Replace 'in' test with 'hasOwnProperty' (isaacs)
+
+<li><a href="http://github.com/joyent/node/issues/1546">#1546</a> http perf improvement
+
+<li>fix memleak in libeio (Tom Hughes)
+
+<li>cmake improvements (Tom Hughes)
+
+<li>node_net.cc: fix incorrect sizeof() (Tom Hughes)
+
+<li>Windows/cygwin: no more GetConsoleTitleW errors on XP (Bert Belder)
+
+<li>Doc improvements (koichik, Logan Smyth, Ben Noordhuis, Arnout Kazemier)</ul>
+
+
+
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.11.tar.gz">https://nodejs.org/dist/node-v0.4.11.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.11/">https://nodejs.org/docs/v0.4.11/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.11/api/">https://nodejs.org/docs/v0.4.11/api/</a>
diff --git a/locale/uk/blog/release/v0.4.12.md b/locale/uk/blog/release/v0.4.12.md
new file mode 100755
index 0000000000000..12afdbfcc5d83
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.12.md
@@ -0,0 +1,32 @@
+---
+version: 0.4.12
+title: Node v0.4.12
+author: ryandahl
+date: 2011-09-16T00:32:07.000Z
+status: publish
+category: release
+slug: node-v0-4-12
+layout: blog-post.hbs
+---
+
+2011.09.15, Version 0.4.12 (stable)
+
+<ul>
+<li>Improve docs
+<li>#1563 overflow in ChildProcess custom_fd.
+<li>#1569, parse error on multi-line HTTP headers. (Ben Noordhuis)
+<li>#1586 net: Socket write encoding case sensitivity (koichik)
+<li>#1610 Remove DigiNotar CA from trusted list (isaacs)
+<li>#1624 buffer: Avoid overrun with 'binary' encoding. (koichik)
+<li>#1633 buffer: write() should always set _charsWritten. (koichik)
+<li>#1707 hasOwnProperty usage security hole in querystring (isaacs)
+<li>#1719 Drain OpenSSL error queue
+<li>Fix error reporting in net.Server.listen</ul>
+
+
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.12.tar.gz">https://nodejs.org/dist/node-v0.4.12.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.12/">https://nodejs.org/docs/v0.4.12/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.12/api/">https://nodejs.org/docs/v0.4.12/api/</a>
diff --git a/locale/uk/blog/release/v0.4.3.md b/locale/uk/blog/release/v0.4.3.md
new file mode 100755
index 0000000000000..76bc70f7c0541
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.3.md
@@ -0,0 +1,36 @@
+---
+version: 0.4.3
+title: Node v0.4.3
+author: ryandahl
+date: 2011-03-19T05:17:59.000Z
+status: publish
+category: release
+slug: node-v0-4-3
+layout: blog-post.hbs
+---
+
+2011.03.18, Version 0.4.3 (stable)
+<ul>
+<li> Don't decrease server connection counter again if destroy() is called more  than once GH-431 (Andreas Reich, Anders Conbere)
+<li> Documentation improvements (koichik)
+<li> Fix bug with setMaxListeners GH-682
+<li> Start up memory footprint improvement. (Tom Hughes)
+<li> Solaris improvements.
+<li> Buffer::Length(Buffer*) should not invoke itself recursively GH-759 (Ben Noordhuis)
+<li> TLS: Advertise support for client certs GH-774 (Theo Schlossnagle)
+<li> HTTP Agent bugs: GH-787, GH-784, GH-803.
+<li> Don't call GetMemoryUsage every 5 seconds.
+<li> Upgrade V8 to 3.1.8.3
+</ul>
+
+
+
+Download: https://nodejs.org/dist/node-v0.4.3.tar.gz
+
+Website: https://nodejs.org/docs/v0.4.3/
+
+Documentation: https://nodejs.org/docs/v0.4.3/api
+
+<a href="https://groups.google.com/d/topic/nodejs/JrYQCQtf6lM/discussion">Announcement</a>
+
+<a href="https://github.com/joyent/node/tree/v0.4.3">commit</a>
diff --git a/locale/uk/blog/release/v0.4.4.md b/locale/uk/blog/release/v0.4.4.md
new file mode 100755
index 0000000000000..6f4c16b2690f1
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.4.md
@@ -0,0 +1,30 @@
+---
+version: 0.4.4
+title: Node v0.4.4
+author: ryandahl
+date: 2011-03-26T15:58:45.000Z
+status: publish
+category: release
+slug: node-v0-4-4
+layout: blog-post.hbs
+---
+
+2011.03.26, Version 0.4.4 (stable)
+<ul>
+<li> CryptoStream.end shouldn't throw if not writable GH-820
+<li> Drop out if connection destroyed before connect() GH-819
+<li> expose https.Agent
+<li> Correctly setsid in tty.open GH-815
+<li> Bug fix for failed buffer construction
+<li> Added support for removing .once listeners (GH-806)
+<li> Upgrade V8 to 3.1.8.5</ul>
+
+
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.4.tar.gz">https://nodejs.org/dist/node-v0.4.4.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.4/">https://nodejs.org/docs/v0.4.4</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.4/api/">https://nodejs.org/docs/v0.4.4/api</a>
+
+<a href="https://groups.google.com/d/topic/nodejs/LlQCYhDEPAc/discussion">announcement</a>
diff --git a/locale/uk/blog/release/v0.4.5.md b/locale/uk/blog/release/v0.4.5.md
new file mode 100755
index 0000000000000..788c31d760046
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.5.md
@@ -0,0 +1,32 @@
+---
+version: 0.4.5
+title: node v0.4.5
+author: ryandahl
+date: 2011-04-02T09:04:58.000Z
+status: publish
+category: release
+slug: node-v0-4-5
+layout: blog-post.hbs
+---
+
+2011.04.01, Version 0.4.5 (stable)
+<ul>
+<li> Fix listener leak in stream.pipe() (Mikeal Rogers)
+<li> Retain buffers in fs.read/write() GH-814 (Jorge Chamorro Bieling)
+<li> TLS performance improvements
+<li> SlowBuffer.prototype.slice bug GH-843
+<li> process.stderr.write should return true
+<li> Immediate pause/resume race condition GH-535 (isaacs)
+<li> Set default host header properly GH-721 (isaacs)
+<li> Upgrade V8 to 3.1.8.8</ul>
+
+
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.5.tar.gz">https://nodejs.org/dist/node-v0.4.5.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.5">https://nodejs.org/docs/v0.4.5</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.5/api">https://nodejs.org/docs/v0.4.5/api</a>
+
+
+<a href="https://groups.google.com/d/topic/nodejs/aOC7SRLJhQY/discussion">announcement</a>
diff --git a/locale/uk/blog/release/v0.4.6.md b/locale/uk/blog/release/v0.4.6.md
new file mode 100755
index 0000000000000..7e15461664a9b
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.6.md
@@ -0,0 +1,30 @@
+---
+version: 0.4.6
+title: Node v0.4.6
+author: ryandahl
+date: 2011-04-14T12:00:30.000Z
+status: publish
+category: release
+slug: node-v0-4-6
+layout: blog-post.hbs
+---
+
+2011.04.13, Version 0.4.6 (stable)
+<ul><li> Don't error on ENOTCONN from shutdown() #670
+<li> Auto completion of built-in debugger suggests prefix match rather than partial match. (koichik)
+<li> circular reference in vm modules. #822 (Jakub Lekstan)
+<li> http response.readable should be false after 'end' #867 (Abe Fettig)
+<li> Implement os.cpus() and os.uptime() on Solaris (Scott McWhirter)
+<li> fs.ReadStream: Allow omission of end option for range reads #801 (Felix Geisendörfer)
+<li> Buffer.write() with UCS-2 should not be write partial char #916 (koichik)
+<Li> Pass secureProtocol through on tls.Server creation (Theo Schlossnagle)
+<li> TLS use RC4-SHA by default
+<li> Don't strangely drop out of event loop on HTTPS client uploads #892
+<li> Doc improvements
+<li> Upgrade v8 to 3.1.8.10</ul>
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.6.tar.gz">https://nodejs.org/dist/node-v0.4.6.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.6/">https://nodejs.org/docs/v0.4.6/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.6/api/">https://nodejs.org/docs/v0.4.6/api/</a>
diff --git a/locale/uk/blog/release/v0.4.7.md b/locale/uk/blog/release/v0.4.7.md
new file mode 100755
index 0000000000000..8fb22f27e8004
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.7.md
@@ -0,0 +1,26 @@
+---
+version: 0.4.7
+title: Node v0.4.7
+author: ryandahl
+date: 2011-04-23T07:47:55.000Z
+status: publish
+category: release
+slug: node-v0-4-7
+layout: blog-post.hbs
+---
+
+2011.04.22, Version 0.4.7 (stable)
+<ul><li> Don't emit error on ECONNRESET from read() #670
+<li> Fix: Multiple pipes to the same stream were broken #929 (Felix Geisendörfer)
+<li> URL parsing/formatting corrections #954 (isaacs)
+<li> make it possible to do repl.start('', stream) (Wade Simmons)
+<li> Add os.loadavg for SunOS (Robert Mustacchi)
+<li> Fix timeouts with floating point numbers #897  (Jorge Chamorro Bieling)
+<li> Improve docs.</ul>
+
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.7.tar.gz">https://nodejs.org/dist/node-v0.4.7.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.7/">https://nodejs.org/docs/v0.4.7/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.7/api">https://nodejs.org/docs/v0.4.7/api</a>
diff --git a/locale/uk/blog/release/v0.4.8.md b/locale/uk/blog/release/v0.4.8.md
new file mode 100755
index 0000000000000..13b2f98d0c8a6
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.8.md
@@ -0,0 +1,58 @@
+---
+version: 0.4.8
+title: Node v0.4.8
+author: ryandahl
+date: 2011-05-21T14:06:00.000Z
+status: publish
+category: release
+slug: node-v0-4-8
+layout: blog-post.hbs
+---
+
+2011.05.20, Version 0.4.8 (stable)
+
+* #974 Properly report traceless errors (isaacs)
+
+* #983 Better JSON.parse error detection in REPL (isaacs)
+
+* #836 Agent socket errors bubble up to req only if req exists
+
+* #1041 Fix event listener leak check timing (koichik)
+
+* #1038 Fix dns.resolve() with 'PTR' throws Error: Unknown type "PTR"
+  (koichik)
+
+* #1073 Share SSL context between server connections (Fedor Indutny)
+
+* Disable compression with OpenSSL. Improves memory perf.
+
+* Implement os.totalmem() and os.freemem() for SunOS (Alexandre Marangone)
+
+* Fix a special characters in URL regression (isaacs)
+
+* Fix idle timeouts in HTTPS (Felix Geisendörfer)
+
+* SlowBuffer.write() with 'ucs2' throws ReferenceError. (koichik)
+
+* http.ServerRequest 'close' sometimes gets an error argument
+  (Felix Geisendörfer)
+
+* Doc improvements
+
+* cleartextstream.destroy() should close(2) the socket. Previously was being
+  mapped to a shutdown(2) syscall.
+
+* No longer compile out asserts and debug statements in normal build.
+
+* Debugger improvements.
+
+* Upgrade V8 to 3.1.8.16.
+
+
+
+
+Website: <a href="https://nodejs.org/docs/v0.4.8/">https://nodejs.org/docs/v0.4.8/</a>
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.8.tar.gz">https://nodejs.org/dist/node-v0.4.8.tar.gz</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.8/api/">https://nodejs.org/docs/v0.4.8/api/</a>
diff --git a/locale/uk/blog/release/v0.4.9.md b/locale/uk/blog/release/v0.4.9.md
new file mode 100755
index 0000000000000..713d6319f1695
--- /dev/null
+++ b/locale/uk/blog/release/v0.4.9.md
@@ -0,0 +1,33 @@
+---
+version: 0.4.9
+title: Node v0.4.9
+author: ryandahl
+date: 2011-06-29T18:41:05.000Z
+status: publish
+category: release
+slug: node-v0-4-9
+layout: blog-post.hbs
+---
+
+2011.06.29, Version 0.4.9 (stable)<ul>
+<li> Improve documentation
+<li> #1095 error handling bug in stream.pipe() (Felix Geisendörfer)
+<li> #1097 Fix a few leaks in node_crypto.cc (Ben Noordhuis)
+<li> #562 #1078 Parse file:// urls properly (Ryan Petrello)
+<li> #880 Option to disable SSLv2 (Jérémy Lal)
+<li> #1087 Disabling SSL compression disabled with early OpenSSLs.
+<li> #1144 debugger: don't allow users to input non-valid commands (Siddharth Mahendraker)
+<li> Perf improvement for util.inherits
+<li> #1166 Support for signature verification with RSA/DSA public keys (Mark Cavage)
+<li> #1177 Remove node_modules lookup optimization to better support nested project structures (Mathias Buus)
+<li> #1203 Add missing scope.Close to fs.sendfileSync
+<li> #1187 Support multiple 'link' headers
+<li> #1196 Fix -e/--eval can't load module from node_modules (Koichi Kobayashi)
+<li> Upgrade V8 to 3.1.8.25, upgrade http-parser.</ul>
+
+
+Download: <a href="https://nodejs.org/dist/node-v0.4.9.tar.gz">https://nodejs.org/dist/node-v0.4.9.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.4.9">https://nodejs.org/docs/v0.4.9</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.4.9/api">https://nodejs.org/docs/v0.4.9/api</a>
diff --git a/locale/uk/blog/release/v0.5.0.md b/locale/uk/blog/release/v0.5.0.md
new file mode 100755
index 0000000000000..19df612352218
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.0.md
@@ -0,0 +1,42 @@
+---
+version: 0.5.0
+title: Node v0.5.0 (Unstable)
+author: ryandahl
+date: 2011-07-06T09:23:17.000Z
+status: publish
+category: release
+slug: node-v0-5-0-unstable
+layout: blog-post.hbs
+---
+
+2011.07.05, Version 0.5.0 (unstable)
+
+<li> New non-default libuv backend to support IOCP on Windows. Use <code>--use-uv</code> to enable.
+<li> deprecate http.cat
+<li> docs improved.
+<li> add child_process.fork
+<li> add fs.utimes() and fs.futimes() support (Ben Noordhuis)
+<li> add process.uptime() (Tom Huges)
+<li> add path.relative (Tony Huang)
+<li> add os.getNetworkInterfaces()
+<li> add remoteAddress and remotePort for client TCP connections (Brian White)
+<li> add secureOptions flag, setting ciphers, SSL_OP_CRYPTOPRO_TLSEXT_BUG to TLS (Theo Schlossnagle)
+<li> add process.arch (Nathan Rajlich)
+<li> add reading/writing of floats and doubles from/to buffers (Brian White)
+<li> Allow script to be read from stdin
+<li> #477 add Buffer::fill method to do memset (Konstantin Käfer)
+<li> #573 Diffie-Hellman support to crypto module (Håvard Stranden)
+<li> #695 add 'hex' encoding to buffer (isaacs)
+<li> #851 Update how REPLServer uses contexts (Ben Weaver)
+<li> #853 add fs.lchow, fs.lchmod, fs.fchmod, fs.fchown (isaacs)
+<li> #889 Allow to remove all EventEmitter listeners at once (Felix Geisendörfer)
+<li> #926 OpenSSL NPN support (Fedor Indutny)
+<li> #955 Change ^C handling in REPL (isaacs)
+<li> #979 add support for Unix Domain Sockets to HTTP (Mark Cavage)
+<li> #1173 #1170 add AMD, asynchronous module definition (isaacs)
+<li> DTrace probes: support X-Forwarded-For (Dave Pacheco) </ul>
+Download: <a href="https://nodejs.org/dist/node-v0.5.0.tar.gz">https://nodejs.org/dist/node-v0.5.0.tar.gz</a>
+
+Website: <a href="https://nodejs.org/docs/v0.5.0/">https://nodejs.org/docs/v0.5.0/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.5.0/api/">https://nodejs.org/docs/v0.5.0/api/</a>
diff --git a/locale/uk/blog/release/v0.5.1.md b/locale/uk/blog/release/v0.5.1.md
new file mode 100755
index 0000000000000..700d2b53c97f3
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.1.md
@@ -0,0 +1,33 @@
+---
+version: 0.5.1
+title: Node v0.5.1
+author: ryandahl
+date: 2011-07-15T06:48:08.000Z
+status: publish
+category: release
+slug: node-v0-5-1
+layout: blog-post.hbs
+---
+
+2011.07.14, Version 0.5.1 (unstable)
+<ul><li> #1233 Fix os.totalmem on FreeBSD amd64 (Artem Zaytsev)
+<li> #1149 IDNA and Punycode support in url.parse (Jeremy Selier, Ben Noordhuis, isaacs)
+<li> Export $CC and $CXX to uv and V8's build systems
+<li> Include pthread-win32 static libraries in build (Igor Zinkovsky)
+<li> #1199, #1094 Fix fs can't handle large file on 64bit platform (koichik)
+<li> #1281 Make require a public member of module (isaacs)
+<li> #1303 Stream.pipe returns the destination (Elijah Insua)
+<li> #1229 Addons should not -DEV_MULTIPLICITY=0 (Brian White)
+<li> libuv backend improvements
+<li> Upgrade V8 to 3.4.10</ul>
+
+
+
+
+Download: <a href="https://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz">https://nodejs.org/dist/v0.5.1/node-v0.5.1.tar.gz</a>
+
+Windows Build: <a href="https://nodejs.org/dist/v0.5.1/node.exe">https://nodejs.org/dist/v0.5.1/node.exe</a>
+
+Documentation: <a href="https://nodejs.org/dist/v0.5.1/docs/api/">https://nodejs.org/dist/v0.5.1/docs/api/</a>
+
+Website: <a href="https://nodejs.org/dist/v0.5.1/docs">https://nodejs.org/dist/v0.5.1/docs</a>
diff --git a/locale/uk/blog/release/v0.5.10.md b/locale/uk/blog/release/v0.5.10.md
new file mode 100755
index 0000000000000..6586db8636387
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.10.md
@@ -0,0 +1,44 @@
+---
+version: 0.5.10
+title: Node v0.5.10
+author: ryandahl
+date: 2011-10-22T02:12:31.000Z
+status: publish
+category: release
+slug: node-v0-5-10
+layout: blog-post.hbs
+---
+
+2011.10.21, Version 0.5.10 (unstable)
+<ul><li>Remove cmake build system, support for Cygwin, legacy code base, process.ENV, process.ARGV, process.memoryUsage().vsize, os.openOSHandle</li>
+<li>Documentation improvments (Igor Zinkovsky, Bert Belder, Ilya Dmitrichenko, koichik, Maciej Małecki, Guglielmo Ferri, isaacs)</li>
+<li>Performance improvements (Daniel Ennis, Bert Belder, Ben Noordhuis) </li>
+<li>Long process.title support (Ben Noordhuis)</li>
+<li>net: register net.Server callback only once (Simen Brekken)</li>
+<li>net: fix connect queue bugs (Ben Noordhuis)</li>
+<li>debugger: fix backtrace err handling (Fedor Indutny)</li>
+<li>Use getaddrinfo instead of c-ares for dns.lookup</li>
+<li>Emit 'end' from crypto streams on close</li>
+<li>repl: print out `undefined` (Nathan Rajlich)</li>
+<li>#1902 buffer: use NO_NULL_TERMINATION flag (koichik)</li>
+<li>#1907 http: Added support for HTTP PATCH verb (Thomas Parslow)</li>
+<li>#1644 add GetCPUInfo on windows (Karl Skomski)</li>
+<li>#1484, #1834, #1482, #771 Don't use a separate context for the repl.  (isaacs)</li>
+<li>#1882 zlib Update 'availOutBefore' value, and test (isaacs)</li>
+<li>#1888 child_process.fork: don't modify args (koichik)</li>
+<li>#1516 tls: requestCert unusable with Firefox and Chrome (koichik)</li>
+<li>#1467 tls: The TLS API is inconsistent with the TCP API (koichik)</li>
+<li>#1894 net: fix error handling in listen() (koichik)</li>
+<li>#1860 console.error now goes through uv_tty_t</li>
+<li>Upgrade V8 to 3.7.0</li>
+<li>Upgrade GYP to r1081</li></ul>
+
+
+
+Download: <a href="https://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz">https://nodejs.org/dist/v0.5.10/node-v0.5.10.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.10/node.exe">https://nodejs.org/dist/v0.5.10/node.exe</a>
+
+Website: <a href="https://nodejs.org/docs/v0.5.10/">https://nodejs.org/docs/v0.5.10/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.5.10/api/">https://nodejs.org/docs/v0.5.10/api/</a>
diff --git a/locale/uk/blog/release/v0.5.2.md b/locale/uk/blog/release/v0.5.2.md
new file mode 100755
index 0000000000000..325fc7d51cb62
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.2.md
@@ -0,0 +1,30 @@
+---
+version: 0.5.2
+title: Node v0.5.2
+author: ryandahl
+date: 2011-07-22T18:40:22.000Z
+status: publish
+category: release
+slug: node-v0-5-2
+layout: blog-post.hbs
+---
+
+2011.07.22, Version 0.5.2 (unstable)
+<ul><li>libuv improvements; named pipe support
+<li>#1242 check for SSL_COMP_get_compression_methods() (Ben Noordhuis)
+<li>#1348 remove require.paths (isaacs)
+<li>#1349 Delimit NODE_PATH with ; on Windows (isaacs)
+<li>#1335 Remove EventEmitter from C++
+<li>#1357 Load json files with require() (isaacs)
+<li>#1374 fix setting ServerResponse.statusCode in writeHead (Trent Mick)
+<li>Fixed: GC was being run too often.
+<li>Upgrade V8 to 3.4.14
+<li>doc improvements</ul>
+
+Download: <a href="https://nodejs.org/dist/v0.5.2/node-v0.5.2.tar.gz">https://nodejs.org/dist/v0.5.2/node-v0.5.2.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.2/node.exe">https://nodejs.org/dist/v0.5.2/node.exe</a>
+
+Website: <a href="https://nodejs.org/dist/v0.5.2/docs/">https://nodejs.org/dist/v0.5.2/docs/</a>
+
+Documentation: <a href="https://nodejs.org/dist/v0.5.2/docs/api">https://nodejs.org/dist/v0.5.2/docs/api</a>
diff --git a/locale/uk/blog/release/v0.5.3.md b/locale/uk/blog/release/v0.5.3.md
new file mode 100755
index 0000000000000..0e3843543eaa3
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.3.md
@@ -0,0 +1,56 @@
+---
+version: 0.5.3
+title: Node v0.5.3
+author: ryandahl
+date: 2011-08-02T15:03:06.000Z
+status: publish
+category: release
+slug: node-v0-5-3
+layout: blog-post.hbs
+---
+
+2011.08.01, Version 0.5.3 (unstable)
+
+<ul><li>Fix crypto encryption/decryption with Base64. (SAWADA Tadashi)
+
+<li>#243 Add an optional length argument to Buffer.write() (koichik)
+
+<li>#657 convert nonbuffer data to string in fs.writeFile/Sync (Daniel Pihlström)
+
+<li>Add process.features, remove process.useUV (Ben Noordhuis)
+
+<li>#324 Fix crypto hmac to accept binary keys + add test cases from rfc 2202 and 4231 (Stefan Bühler)
+
+<li>Add Socket::bytesRead, Socket::bytesWritten (Alexander Uvarov)
+
+<li>#572 Don't print result of --eval in CLI (Ben Noordhuis)
+
+<li>#1223 Fix http.ClientRequest crashes if end() was called twice (koichik)
+
+<li>#1383 Emit 'close' after all connections have closed (Felix Geisendörfer)
+
+<li>Add sprintf-like util.format() function (Ben Noordhuis)
+
+<li>Add support for TLS SNI (Fedor Indutny)
+
+<li>New http agent implementation. Off by default the command line flag <code>--use-http2</code> will enable it. <code>make test-http2</code> will run the tests for the new implementation. (Mikeal Rogers)
+
+<li>Revert AMD compatibility. (isaacs)
+
+<li>Windows: improvements, child_process support.
+
+<li>Remove pkg-config file.
+
+<li>Fix startup time regressions.
+
+<li>doc improvements</ul>
+
+
+
+Download: <a href="https://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz">https://nodejs.org/dist/v0.5.3/node-v0.5.3.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.3/node.exe">https://nodejs.org/dist/v0.5.3/node.exe</a>
+
+Website: <a href="https://nodejs.org/dist/v0.5.3/docs">https://nodejs.org/dist/v0.5.3/docs</a>
+
+Documentation: <a href="https://nodejs.org/dist/v0.5.3/docs/api">https://nodejs.org/dist/v0.5.3/docs/api</a>
diff --git a/locale/uk/blog/release/v0.5.4.md b/locale/uk/blog/release/v0.5.4.md
new file mode 100755
index 0000000000000..270a3ad2479b3
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.4.md
@@ -0,0 +1,39 @@
+---
+version: 0.5.4
+title: Node v0.5.4
+author: ryandahl
+date: 2011-08-12T15:38:26.000Z
+status: publish
+category: release
+slug: node-v0-5-4
+layout: blog-post.hbs
+---
+
+2011.08.12, Version 0.5.4 (unstable)
+
+<ul><li>libuv/Windows compatibility improvements
+
+<li>Build on Microsoft Visual Studio via GYP. Use generate-projects.bat in the to build sln files. (Peter Bright, Igor Zinkovsky)
+
+<li>Make Mikeal's HTTP agent client the default. Use old HTTP client with <code>--use-http1</code>
+
+<li>Fixes https host header default port handling. (Mikeal Rogers)
+
+<li>#1440 strip byte order marker when loading *.js and *.json files (Ben Noordhuis)
+
+<li>#1434 Improve util.format() compatibility with browser. (Koichi Kobayashi)
+
+<li>Provide unchecked uint entry points for integer Buffer.read/writeInt methods. (Robert Mustacchi)
+
+<li>CMake improvements (Tom Huges)
+
+<li>Upgrade V8 to 3.5.4.</ul>
+
+
+Download: <a href="https://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz">https://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.4/node.exe">https://nodejs.org/dist/v0.5.4/node.exe</a>
+
+Website: <a href="https://nodejs.org/dist/v0.5.4/docs">https://nodejs.org/dist/v0.5.4/docs</a>
+
+Documentation: <a href="https://nodejs.org/dist/v0.5.4/docs/api">https://nodejs.org/dist/v0.5.4/docs/api</a>
diff --git a/locale/uk/blog/release/v0.5.5.md b/locale/uk/blog/release/v0.5.5.md
new file mode 100755
index 0000000000000..b2b8305c0e717
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.5.md
@@ -0,0 +1,43 @@
+---
+version: 0.5.5
+title: Node v0.5.5
+author: bennoordhuis
+date: 2011-08-27T06:20:10.000Z
+status: publish
+category: release
+slug: node-v0-5-5
+layout: blog-post.hbs
+---
+
+<p>2011.08.26, Version 0.5.5 (unstable)</p>
+<ul>
+<li>typed arrays, implementation from Plesk
+<li>fix IP multicast on SunOS
+<li>fix DNS lookup order: IPv4 first, IPv6 second (--use-uv only)
+<li>remove support for UNIX datagram sockets (--use-uv only)
+<li>UDP support for Windows (Bert Belder)
+<li>#1572 improve tab completion for objects in the REPL (Nathan Rajlich)
+<li>#1563 fix buffer overflow in child_process module (reported by Dean McNamee)
+<li>#1546 fix performance regression in http module (reported by Brian Geffon)
+<li>#1491 add PBKDF2 crypto support (Glen Low)
+<li>#1447 remove deprecated http.cat() function (Mikeal Rogers)
+<li>#1140 fix incorrect dispatch of vm.runInContext's filename argument<br />
+  (Antranig Basman)</p>
+<li>#1140 document vm.runInContext() and vm.createContext() (Antranig Basman)
+<li>#1428 fix os.freemem() on 64 bits freebsd (Artem Zaytsev)
+<li>#1164 make all DNS lookups async, fixes uncatchable exceptions<br />
+  (Koichi Kobayashi)</p>
+<li>fix incorrect ssl shutdown check (Tom Hughes)
+<li>various cmake fixes (Tom Hughes)
+<li>improved documentation (Koichi Kobayashi, Logan Smyth, Fedor Indutny,<br />
+  Mikeal Rogers, Maciej Małecki, Antranig Basman, Mickaël Delahaye)</p>
+<li>upgrade libuv to commit 835782a
+<li>upgrade V8 to 3.5.8
+</ul>
+<p>Download: <a href="https://nodejs.org/dist/node-v0.5.5.tar.gz">https://nodejs.org/dist/node-v0.5.5.tar.gz</a></p>
+<p>Windows Executable: <a href="https://nodejs.org/dist/v0.5.5/node.exe">https://nodejs.org/dist/v0.5.5/node.exe</a></p>
+<p>Website: <a href="https://nodejs.org/docs/v0.5.5/">https://nodejs.org/docs/v0.5.5/</a></p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.5.5/api/">https://nodejs.org/docs/v0.5.5/api/</a></p>
+<br /><br />
+
+<b>Update:</b> The <code>.exe</code> has a bug that results in incompatibility with Windows XP and Server 2003. This has been reported in <a href="https://github.com/joyent/node/issues/1592">issue #1592</a> and fixed. A new binary was made that is compatibile with the older Windows: <a href="https://nodejs.org/dist/v0.5.5/node-186364e.exe">https://nodejs.org/dist/v0.5.5/node-186364e.exe</a>.
diff --git a/locale/uk/blog/release/v0.5.6.md b/locale/uk/blog/release/v0.5.6.md
new file mode 100755
index 0000000000000..70e67aa7b8c3b
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.6.md
@@ -0,0 +1,52 @@
+---
+version: 0.5.6
+title: Node v0.5.6 (unstable)
+author: piscisaureus
+date: 2011-09-09T23:30:39.000Z
+status: publish
+category: release
+slug: node-v0-5-6
+layout: blog-post.hbs
+---
+
+2011.09.08, Version 0.5.6 (unstable)
+<ul>
+    <li>#345, #1635, #1648 Documentation improvements (Thomas Shinnick, Abimanyu Raja, AJ ONeal, Koichi Kobayashi, Michael Jackson, Logan Smyth, Ben Noordhuis)</li>
+    <li>#650 Improve path parsing on windows (Bert Belder)</li>
+    <li>#752 Remove headers sent check in OutgoingMessage.getHeader() (Peter Lyons)</li>
+    <li>#1236, #1438, #1506, #1513, #1621, #1640, #1647 Libuv-related bugs fixed (Jorge Chamorro Bieling, Peter Bright, Luis Lavena, Igor Zinkovsky)</li>
+    <li>#1296, #1612 crypto: Fix BIO's usage. (Koichi Kobayashi)</li>
+    <li>#1345 Correctly set socket.remoteAddress with libuv backend (Bert Belder)</li>
+    <li>#1429 Don't clobber quick edit mode on windows (Peter Bright)</li>
+    <li>#1503 Make libuv backend default on unix, override with `node --use-legacy`</li>
+    <li>#1565 Fix fs.stat for paths ending with \ on windows (Igor Zinkovsky)</li>
+    <li>#1568 Fix x509 certificate subject parsing (Koichi Kobayashi)</li>
+    <li>#1586 Make socket write encoding case-insensitive (Koichi Kobayashi)</li>
+    <li>#1591, #1656, #1657 Implement fs in libuv, remove libeio and pthread-win32 dependency on windows (Igor Zinkovsky, Ben Noordhuis, Ryan Dahl, Isaac Schlueter)</li>
+    <li>#1592 Don't load-time link against CreateSymbolicLink on windows (Peter Bright)</li>
+    <li>#1601 Improve API consistency when dealing with the socket underlying a HTTP client request (Mikeal Rogers)</li>
+    <li>#1610 Remove DigiNotar CA from trusted list (Isaac Schlueter)</li>
+    <li>#1617 Added some win32 os functions (Karl Skomski)</li>
+    <li>#1624 avoid buffer overrun with 'binary' encoding (Koichi Kobayashi)</li>
+    <li>#1633 make Buffer.write() always set _charsWritten (Koichi Kobayashi)</li>
+    <li>#1644 Windows: set executables to be console programs (Peter Bright)</li>
+    <li>#1651 improve inspection for sparse array (Koichi Kobayashi)</li>
+    <li>#1672 set .code='ECONNRESET' on socket hang up errors (Ben Noordhuis)</li>
+    <li>Add test case for foaf+ssl client certificate (Niclas Hoyer)</li>
+    <li>Added RPATH environment variable to override run-time library paths (Ashok Mudukutore)</li>
+    <li>Added TLS client-side session resumption support (Sean Cunningham)</li>
+    <li>Added additional properties to getPeerCertificate (Nathan Rixham, Niclas Hoyer)</li>
+    <li>Don't eval repl command twice when an error is thrown (Nathan Rajlich)</li>
+    <li>Improve util.isDate() (Nathan Rajlich)</li>
+    <li>Improvements in libuv backend and bindings, upgrade libuv to bd6066cb349a9b3a1b0d87b146ddaee06db31d10</li>
+    <li>Show warning when using lib/sys.js (Maciej Malecki)</li>
+    <li>Support plus sign in url protocol (Maciej Malecki)</li>
+    <li>Upgrade V8 to 3.6.2</li>
+</ul>
+Download: <a href="https://nodejs.org/dist/v0.5.6/node-v0.5.6.tar.gz">https://nodejs.org/dist/v0.5.6/node-v0.5.6.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.6/node.exe">https://nodejs.org/dist/v0.5.6/node.exe</a>
+
+Website: <a href="https://nodejs.org/docs/v0.5.6/">https://nodejs.org/docs/v0.5.6/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.5.6/api/">https://nodejs.org/docs/v0.5.6/api/</a>
diff --git a/locale/uk/blog/release/v0.5.7.md b/locale/uk/blog/release/v0.5.7.md
new file mode 100755
index 0000000000000..bf3f17bd1f6c7
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.7.md
@@ -0,0 +1,38 @@
+---
+version: 0.5.7
+title: Node v0.5.7 (unstable)
+author: ryandahl
+date: 2011-09-17T01:57:03.000Z
+status: publish
+category: release
+slug: node-v0-5-7-unstable
+layout: blog-post.hbs
+---
+
+2011.09.16, Version 0.5.7 (unstable)
+<ul>
+<li>Upgrade V8 to 3.6.4
+<li>Improve Windows compatibility
+<li>Documentation improvements
+<li>Debugger and REPL improvements (Fedor Indutny)
+<li>Add legacy API support: net.Stream(fd), process.stdout.writable, process.stdout.fd
+<li>Fix mkdir EEXIST handling (isaacs)
+<li>Use net_uv instead of net_legacy for stdio
+<li>Do not load readline from util.inspect
+<li>#1673 Fix bug related to V8 context with accessors (Fedor Indutny)
+<li>#1634 util: Fix inspection for Error (koichik)
+<li>#1645 fs: Add positioned file writing feature to fs.WriteStream (Thomas Shinnick)
+<li>#1637 fs: Unguarded fs.watchFile cache statWatchers checking fixed (Thomas Shinnick)
+<li>#1695 Forward customFds to ChildProcess.spawn
+<li>#1707 Fix hasOwnProperty security problem in querystring (isaacs)
+<li>#1719 Drain OpenSSL error queue</ul>
+
+
+
+Download: <a href="https://nodejs.org/dist/v0.5.7/node-v0.5.7.tar.gz">https://nodejs.org/dist/v0.5.7/node-v0.5.7.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.7/node.exe">https://nodejs.org/dist/v0.5.7/node.exe</a>
+
+Website: <a href="https://nodejs.org/docs/v0.5.7/">https://nodejs.org/docs/v0.5.7/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.5.7/api/">https://nodejs.org/docs/v0.5.7/api/</a>
diff --git a/locale/uk/blog/release/v0.5.8.md b/locale/uk/blog/release/v0.5.8.md
new file mode 100755
index 0000000000000..596e86803664d
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.8.md
@@ -0,0 +1,29 @@
+---
+version: 0.5.8
+title: Node v0.5.8
+author: ryandahl
+date: 2011-09-30T23:47:11.000Z
+status: publish
+category: release
+slug: node-v0-5-8
+layout: blog-post.hbs
+---
+
+2011.09.30, Version 0.5.8 (unstable)<ul><li>zlib bindings (isaacs)
+<li>Windows supports TTY ANSI escape codes (Bert Belder)
+<li>Debugger improvements (Fedor Indutny)
+<li>crypto: look up SSL errors with ERR_print_errors() (Ben Noordhuis)
+<li>dns callbacks go through MakeCallback now
+<li>Raise an error when a malformed package.json file is found. (Ben Leslie)
+<li>buffers: handle bad length argument in constructor (Ben Noordhuis)
+<li>#1726, unref process.stdout
+<li>Doc improvements (Ben Noordhuis, Fedor Indutny, koichik)
+<li>Upgrade libuv to fe18438</ul>
+
+Download: <a href="https://nodejs.org/dist/v0.5.8/node-v0.5.8.tar.gz">https://nodejs.org/dist/v0.5.8/node-v0.5.8.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.8/node.exe">https://nodejs.org/dist/v0.5.8/node.exe</a>
+
+Website: <a href="https://nodejs.org/docs/v0.5.8/">https://nodejs.org/docs/v0.5.8/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.5.8/api/">https://nodejs.org/docs/v0.5.8/api/</a>
diff --git a/locale/uk/blog/release/v0.5.9.md b/locale/uk/blog/release/v0.5.9.md
new file mode 100755
index 0000000000000..60a9877d2e078
--- /dev/null
+++ b/locale/uk/blog/release/v0.5.9.md
@@ -0,0 +1,30 @@
+---
+version: 0.5.9
+title: Node v0.5.9
+author: ryandahl
+date: 2011-10-11T02:06:21.000Z
+status: publish
+category: release
+slug: node-v0-5-9
+layout: blog-post.hbs
+---
+
+2011.10.10, Version 0.5.9 (unstable)
+<ul><li>fs.watch interface backed by kqueue, inotify, and ReadDirectoryChangesW (Igor Zinkovsky, Ben Noordhuis)</li>
+<li>add dns.resolveTxt (Christian Tellnes)</li>
+<li>Remove legacy http library (Ben Noordhuis)</li>
+<li>child_process.fork returns and works on Windows. Allows passing handles.  (Igor Zinkovsky, Bert Belder)</li>
+<li>#1774 Lint and clean up for --harmony_block_scoping (Tyler Larson, Colton Baker)</li>
+<li>#1813 Fix ctrl+c on Windows (Bert Belder)</li>
+<li>#1844 unbreak --use-legacy (Ben Noordhuis)</li>
+<li>process.stderr now goes through libuv. Both process.stdout and process.stderr are blocking when referencing a TTY.</li>
+<li>net_uv performance improvements (Ben Noordhuis, Bert Belder)</li></ul>
+
+
+Download: <a href="https://nodejs.org/dist/v0.5.9/node-v0.5.9.tar.gz">https://nodejs.org/dist/v0.5.9/node-v0.5.9.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.5.9/node.exe">https://nodejs.org/dist/v0.5.9/node.exe</a>
+
+Website: <a href="https://nodejs.org/docs/v0.5.9/">https://nodejs.org/docs/v0.5.9/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.5.9/api/">https://nodejs.org/docs/v0.5.9/api/</a>
diff --git a/locale/uk/blog/release/v0.6.0.md b/locale/uk/blog/release/v0.6.0.md
new file mode 100755
index 0000000000000..f5772cbfaf9f1
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.0.md
@@ -0,0 +1,83 @@
+---
+version: 0.6.0
+title: Node v0.6.0
+author: ryandahl
+date: 2011-11-05T09:07:10.000Z
+status: publish
+category: release
+slug: node-v0-6-0
+layout: blog-post.hbs
+---
+
+We are happy to announce the third stable branch of Node v0.6. We will be freezing JavaScript, C++, and binary interfaces for all v0.6 releases.
+
+The major differences between v0.4 and v0.6 are<ul>
+<li>Native Windows support using I/O Completion Ports for sockets.
+<li>Integrated load balancing over multiple processes. <a href="https://nodejs.org/docs/v0.6.0/api/cluster.html">docs</a>
+<li>Better support for IPC between Node instances <a href="https://nodejs.org/docs/v0.6.0/api/child_processes.html#child_process.fork">docs</a>
+<li>Improved command line debugger <a href="https://nodejs.org/docs/v0.6.0/api/debugger.html">docs</a>
+<li>Built-in binding to zlib for compression <a href="https://nodejs.org/docs/v0.6.0/api/zlib.html">docs</a>
+<li>Upgrade v8 from 3.1 to 3.6</ul>
+
+In order to support Windows we reworked much of the core architecture. There was some fear that our work would degrade performance on UNIX systems but this was not the case. Here is a Linux system we benched for demonstration:
+
+<table><tr> <th></th> <th>v0.4.12 (linux)</th><th>v0.6.0 (linux)</th></tr>
+<tr> <td>http_simple.js /bytes/1024</td> <td>5461 r/s</td> <td>6263 r/s</td> </tr>
+<tr> <td>io.js read </td> <td>19.75 mB/s</td> <td>26.63 mB/s</td> </tr>
+<tr> <td>io.js write </td> <td>21.60 mB/s</td> <td>17.40 mB/s</td> </tr>
+<tr> <td>startup.js </td> <td>74.7 ms</td> <td>49.6 ms</td> </tr></table>
+
+Bigger is better in http and io benchmarks, smaller is better in startup. The http benchmark was done with 600 clients on a 10GE network served from three load generation machines.
+
+In the last version of Node, v0.4, we could only run Node on Windows with Cygwin. Therefore we've gotten massive improvements by targeting the native APIs. Benchmarks on the same machine:
+
+<table><tr><th></th><th>v0.4.12 (windows)</th><th>v0.6.0 (windows)</th></tr>
+<tr> <td>http_simple.js /bytes/1024</td> <td>3858 r/s</td> <td>5823 r/s</td> </tr>
+<tr> <td>io.js read </td> <td>12.41 mB/s</td> <td>26.51 mB/s</td> </tr>
+<tr> <td>io.js write </td> <td>12.61 mB/s</td> <td>33.58 mB/s</td> </tr>
+<tr> <td>startup.js </td> <td>152.81 ms</td> <td>52.04 ms</td> </tr></table>
+
+We consider this a good intermediate stage for the Windows port. There is still work to be done. For example, we are not yet providing users with a blessed path for building addon modules in MS Visual Studio.  Work will continue in later releases.
+
+For users upgrading code bases from v0.4 to v0.6 <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6">we've documented</a> most of the issues that you will run into. Most people find the change painless. Despite the long list of changes most core APIs remain untouched. 
+
+Our release cycle will be tightened dramatically now. Expect to see a new stable branch in January. We wish to eventually have our releases in sync with Chrome and V8's 6 week cycle.
+
+Thank you to everyone who contributed code, tests, docs, or sent in bug reports.
+
+Here are the changes between v0.5.12 and v0.6.0:
+
+2011.11.04, Version 0.6.0 (stable)
+<ul><li>print undefined on undefined values in REPL (Nathan Rajlich)</li>
+<li>doc improvements (koichik, seebees, bnoordhuis, Maciej Małecki, Jacob Kragh)</li>
+<li>support native addon loading in windows (Bert Belder)</li>
+<li>rename getNetworkInterfaces() to networkInterfaces() (bnoordhuis)</li>
+<li>add pending accepts knob for windows (igorzi)</li>
+<li>http.request(url.parse(x)) (seebees)</li>
+<li>#1929 zlib Respond to 'resume' events properly (isaacs)</li>
+<li>stream.pipe: Remove resume and pause events</li>
+<li>test fixes for windows (igorzi)</li>
+<li>build system improvements (bnoordhuis)</li>
+<li>#1936 tls: does not emit 'end' from EncryptedStream (koichik)</li>
+<li>#758 tls: add address(), remoteAddress/remotePort</li>
+<li>#1399 http: emit Error object after .abort() (bnoordhuis)</li>
+<li>#1999 fs: make mkdir() default to 0777 permissions (bnoordhuis)</li>
+<li>#2001 fix pipe error codes</li>
+<li>#2002 Socket.write should reset timeout timer</li>
+<li>stdout and stderr are blocking when associated with file too.</li>
+<li>remote debugger support on windows (Bert Belder)</li>
+<li>convenience methods for zlib (Matt Robenolt)</li>
+<li>process.kill support on windows (igorzi)</li>
+<li>process.uptime() support on windows (igorzi)</li>
+<li>Return IPv4 addresses before IPv6 addresses from getaddrinfo</li>
+<li>util.inspect improvements (Nathan Rajlich)</li>
+<li>cluster module api changes</li>
+<li>Downgrade V8 to 3.6.6.6</li></ul>
+
+Download: <a href="https://nodejs.org/dist/v0.6.0/node-v0.6.0.tar.gz">https://nodejs.org/dist/v0.6.0/node-v0.6.0.tar.gz</a>
+
+Windows Executable: <a href="https://nodejs.org/dist/v0.6.0/node.exe">https://nodejs.org/dist/v0.6.0/node.exe</a>
+
+Website: <a href="https://nodejs.org/docs/v0.6.0/">https://nodejs.org/docs/v0.6.0/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.6.0/api/">https://nodejs.org/docs/v0.6.0/api/</a>
diff --git a/locale/uk/blog/release/v0.6.1.md b/locale/uk/blog/release/v0.6.1.md
new file mode 100755
index 0000000000000..3a3d5b6d1e43a
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.1.md
@@ -0,0 +1,36 @@
+---
+version: 0.6.1
+title: Node v0.6.1
+author: ryandahl
+date: 2011-11-11T23:34:15.000Z
+status: publish
+category: release
+slug: node-v0-6-1
+layout: blog-post.hbs
+---
+
+2011.11.11, Version 0.6.1 (stable)
+<ul><li>doc improvements (Eric Lovett, Ben Noordhuis, Scott Anderson, Yoji SHIDARA)</li>
+<li>crypto: make thread-safe (Ben Noordhuis)</li>
+<li>fix process.kill error object</li>
+<li>debugger: correctly handle source with multi-byte characters (Shigeki Ohtsu)</li>
+<li>make stdout and stderr non-destroyable (Igor Zinkovsky)</li>
+<li>fs: don't close uninitialized fs.watch handle (Ben Noordhuis)</li>
+<li>#2026 fix man page install on BSDs (Ben Noordhuis)</li>
+<li>#2040 fix unrecognized errno assert in uv_err_name</li>
+<li>#2043 fs: mkdir() should call callback if mode is omitted</li>
+<li>#2045 fs: fix fs.realpath on windows to return on error (Benjamin Pasero)</li>
+<li>#2047 minor cluster improvements</li>
+<li>#2052 readline get window columns correctly</li>
+<li>Upgrade V8 to 3.6.6.7</li></ul>
+
+
+Source Code: <a href="https://nodejs.org/dist/v0.6.1/node-v0.6.1.tar.gz">https://nodejs.org/dist/v0.6.1/node-v0.6.1.tar.gz</a>
+
+Windows Installer: <a href="https://nodejs.org/dist/v0.6.1/node-v0.6.1.msi">https://nodejs.org/dist/v0.6.1/node-v0.6.1.msi</a>
+
+Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.1/node-v0.6.1.pkg">https://nodejs.org/dist/v0.6.1/node-v0.6.1.pkg</a>
+
+Website: <a href="https://nodejs.org/docs/v0.6.1/">https://nodejs.org/docs/v0.6.1/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.6.1/api/">https://nodejs.org/docs/v0.6.1/api/</a>
diff --git a/locale/uk/blog/release/v0.6.10.md b/locale/uk/blog/release/v0.6.10.md
new file mode 100755
index 0000000000000..c66d9e4d12834
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.10.md
@@ -0,0 +1,33 @@
+---
+version: 0.6.10
+title: Node v0.6.10
+author: Isaac Schlueter
+date: 2012-02-03T01:22:03.000Z
+status: publish
+category: release
+slug: node-v0-6-10
+layout: blog-post.hbs
+---
+
+<p>2012.02.02, Version 0.6.10 (stable)</p>
+
+<ul>
+<li><p>Update V8 to 3.6.6.20</p></li>
+<li><p>Add npm msysgit bash shim to msi installer (isaacs)</p></li>
+<li><p>buffers: fix intermittent out of bounds error (Ben Noordhuis)</p></li>
+<li><p>buffers: honor length argument in base64 decoder (Ben Noordhuis)</p></li>
+<li><p>windows: Fix path.exists regression (Bert Belder)</p></li>
+<li><p>Make QueryString.parse run faster (Philip Tellis)</p></li>
+<li><p>http: avoid freeing http-parser objects too early (koichik)</p></li>
+<li><p>timers: add v0.4 compatibility hack (Ben Noordhuis)</p></li>
+<li><p>Proper EPERM error code support (Igor Zinkovsky, Brandon Philips)</p></li>
+<li><p>dgram: Implement udp multicast methods on windows (Bert Belder)</p></li>
+</ul><p>Source Code: <a href="https://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz">https://nodejs.org/dist/v0.6.10/node-v0.6.10.tar.gz</a></p>
+
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.10/node-v0.6.10.msi">https://nodejs.org/dist/v0.6.10/node-v0.6.10.msi</a></p>
+
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg">https://nodejs.org/dist/v0.6.10/node-v0.6.10.pkg</a></p>
+
+<p>Website: <a href="https://nodejs.org/docs/v0.6.10/">https://nodejs.org/docs/v0.6.10/</a></p>
+
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.10/api/">https://nodejs.org/docs/v0.6.10/api/</a></p>
diff --git a/locale/uk/blog/release/v0.6.11.md b/locale/uk/blog/release/v0.6.11.md
new file mode 100755
index 0000000000000..ceb910827bb55
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.11.md
@@ -0,0 +1,67 @@
+---
+version: 0.6.11
+title: Version 0.6.11 (stable)
+author: Isaac Schlueter
+date: 2012-02-17T21:32:55.000Z
+status: publish
+category: release
+slug: version-0-6-11-stable
+layout: blog-post.hbs
+---
+
+<p>2012.02.17 Version 0.6.11 (stable)
+
+</p>
+<ul>
+<li><p>http: allow multiple WebSocket RFC6455 headers (Einar Otto Stangvik)</p>
+</li>
+<li><p>http: allow multiple WWW-Authenticate headers (Ben Noordhuis)</p>
+</li>
+<li><p>windows: support unicode argv and environment variables (Bert Belder)</p>
+</li>
+<li><p>tls: mitigate session renegotiation attacks (Ben Noordhuis)</p>
+</li>
+<li><p>tcp, pipe: don&#39;t assert on uv_accept() errors (Ben Noordhuis)</p>
+</li>
+<li><p>tls: Allow establishing secure connection on the existing socket (koichik)</p>
+</li>
+<li><p>dgram: handle close of dgram socket before DNS lookup completes (Seth Fitzsimmons)</p>
+</li>
+<li><p>windows: Support half-duplex pipes (Igor Zinkovsky)</p>
+</li>
+<li><p>build: disable omit-frame-pointer on solaris systems (Dave Pacheco)</p>
+</li>
+<li><p>debugger: fix --debug-brk (Ben Noordhuis)</p>
+</li>
+<li><p>net: fix large file downloads failing (koichik)</p>
+</li>
+<li><p>fs: fix ReadStream failure to read from existing fd (Christopher Jeffrey)</p>
+</li>
+<li><p>net: destroy socket on DNS error (Stefan Rusu)</p>
+</li>
+<li><p>dtrace: add missing translator (Dave Pacheco)</p>
+</li>
+<li><p>unix: don&#39;t flush tty on switch to raw mode (Ben Noordhuis)</p>
+</li>
+<li><p>windows: reset brightness when reverting to default text color (Bert Belder)</p>
+</li>
+<li><p>npm: update to 1.1.1</p>
+
+<p>- Update which, fstream, mkdirp, request, and rimraf<br>- Fix #2123 Set path properly for lifecycle scripts on windows<br>- Mark the root as seen, so we don&#39;t recurse into it. Fixes #1838. (Martin Cooper)</p>
+
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz">https://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.11/node-v0.6.11.msi">https://nodejs.org/dist/v0.6.11/node-v0.6.11.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg">https://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.11/">https://nodejs.org/docs/v0.6.11/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.11/api/">https://nodejs.org/docs/v0.6.11/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.12.md b/locale/uk/blog/release/v0.6.12.md
new file mode 100755
index 0000000000000..781a504c6e628
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.12.md
@@ -0,0 +1,69 @@
+---
+version: 0.6.12
+title: Version 0.6.12 (stable)
+author: Isaac Schlueter
+date: 2012-03-02T21:22:49.000Z
+status: publish
+category: release
+slug: version-0-6-12-stable
+layout: blog-post.hbs
+---
+
+<p>2012.03.02 Version 0.6.12 (stable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.6.6.24</p>
+</li>
+<li><p>dtrace ustack helper improvements (Dave Pacheco)</p>
+</li>
+<li><p>API Documentation refactor (isaacs)</p>
+</li>
+<li><p>#2827 net: fix race write() before and after connect() (koichik)</p>
+</li>
+<li><p>#2554 #2567 throw if fs args for &#39;start&#39; or &#39;end&#39; are strings (AJ ONeal)</p>
+</li>
+<li><p>punycode: Update to v1.0.0 (Mathias Bynens)</p>
+</li>
+<li><p>Make a fat binary for the OS X pkg (isaacs)</p>
+</li>
+<li><p>Fix hang on accessing process.stdin (isaacs)</p>
+</li>
+<li><p>repl: make tab completion work on non-objects (Nathan Rajlich)</p>
+</li>
+<li><p>Fix fs.watch on OS X (Ben Noordhuis)</p>
+</li>
+<li><p>Fix #2515 nested setTimeouts cause premature process exit (Ben Noordhuis)</p>
+</li>
+<li><p>windows: fix time conversion in stat (Igor Zinkovsky)</p>
+</li>
+<li><p>windows: fs: handle EOF in read (Brandon Philips)</p>
+</li>
+<li><p>windows: avoid IOCP short-circuit on non-ifs lsps (Igor Zinkovsky)</p>
+</li>
+<li><p>Upgrade npm to 1.1.4 (isaacs)</p>
+<p>
+- windows fixes<br>
+- Bundle nested bundleDependencies properly<br>
+- install: support --save with url install targets<br>
+- shrinkwrap: behave properly with url-installed modules<br>
+- support installing uncompressed tars or single file modules from urls etc.<br>
+- don&#39;t run make clean on rebuild<br>
+- support HTTPS-over-HTTP proxy tunneling<br>
+</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz">https://nodejs.org/dist/v0.6.12/node-v0.6.12.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.12/node-v0.6.12.msi">https://nodejs.org/dist/v0.6.12/node-v0.6.12.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg">https://nodejs.org/dist/v0.6.12/node-v0.6.12.pkg</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.12/">https://nodejs.org/docs/v0.6.12/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.12/api/">https://nodejs.org/docs/v0.6.12/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.13.md b/locale/uk/blog/release/v0.6.13.md
new file mode 100755
index 0000000000000..f67aa704778d2
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.13.md
@@ -0,0 +1,53 @@
+---
+version: 0.6.13
+title: Version 0.6.13 (stable)
+author: Isaac Schlueter
+date: 2012-03-15T17:37:02.000Z
+status: publish
+category: release
+slug: version-0-6-13-stable
+layout: blog-post.hbs
+---
+
+<p>2012.03.15 Version 0.6.13 (stable)
+
+</p>
+<ul>
+<li><p>Windows: Many libuv test fixes (Bert Belder)</p>
+</li>
+<li><p>Windows: avoid uv_guess_handle crash in when fd &lt; 0 (Bert Belder)</p>
+</li>
+<li><p>Map EBUSY and ENOTEMPTY errors (Bert Belder)</p>
+</li>
+<li><p>Windows: include syscall in fs errors (Bert Belder)</p>
+</li>
+<li><p>Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)</p>
+</li>
+<li><p>Update npm to 1.1.9</p>
+<p>
+- upgrade node-gyp to 0.3.5 (Nathan Rajlich)<br>
+- Fix isaacs/npm#2249 Add cache-max and cache-min configs<br>
+- Properly redirect across https/http registry requests<br>
+- log config usage if undefined key in set function (Kris Windham)<br>
+- Add support for os/cpu fields in package.json (Adam Blackburn)<br>
+- Automatically node-gyp packages containing a binding.gyp<br>
+- Fix failures unpacking in UNC shares<br>
+- Never create un-listable directories<br>
+- Handle cases where an optionalDependency fails to build
+</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz">https://nodejs.org/dist/v0.6.13/node-v0.6.13.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.13/node-v0.6.13.msi">https://nodejs.org/dist/v0.6.13/node-v0.6.13.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg">https://nodejs.org/dist/v0.6.13/node-v0.6.13.pkg</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.13/">https://nodejs.org/docs/v0.6.13/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.13/api/">https://nodejs.org/docs/v0.6.13/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.14.md b/locale/uk/blog/release/v0.6.14.md
new file mode 100755
index 0000000000000..aff33b54cfd77
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.14.md
@@ -0,0 +1,58 @@
+---
+version: 0.6.14
+title: Version 0.6.14 (stable)
+author: Isaac Schlueter
+date: 2012-03-23T18:22:22.000Z
+status: publish
+category: release
+slug: version-0-6-14-stable
+layout: blog-post.hbs
+---
+
+<p>2012.03.22 Version 0.6.14 (stable)
+
+</p>
+<ul>
+<li><p>net: don&#39;t crash when queued write fails (Igor Zinkovsky)</p>
+</li>
+<li><p>sunos: fix EMFILE on process.memoryUsage() (Bryan Cantrill)</p>
+</li>
+<li><p>crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)</p>
+</li>
+<li><p>unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)</p>
+</li>
+<li><p>Add UV_ENOSPC and mappings to it (Bert Belder)</p>
+</li>
+<li><p>http-parser: Fix response body is not read (koichik)</p>
+</li>
+<li><p>Upgrade npm to 1.1.12</p>
+<p>
+- upgrade node-gyp to 0.3.7<br>
+- work around AV-locked directories on Windows<br>
+- Fix isaacs/npm#2293 Don&#39;t try to &#39;uninstall&#39; /<br>
+- Exclude symbolic links from packages.<br>
+- Fix isaacs/npm#2275 Spurious &#39;unresolvable cycle&#39; error.<br>
+- Exclude/include dot files as if they were normal files
+</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz">https://nodejs.org/dist/v0.6.14/node-v0.6.14.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.14/node-v0.6.14.msi">https://nodejs.org/dist/v0.6.14/node-v0.6.14.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.6.14/x64/">https://nodejs.org/dist/v0.6.14/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg">https://nodejs.org/dist/v0.6.14/node-v0.6.14.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.6.14/">https://nodejs.org/dist/v0.6.14/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.14/">https://nodejs.org/docs/v0.6.14/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.14/api/">https://nodejs.org/docs/v0.6.14/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.15.md b/locale/uk/blog/release/v0.6.15.md
new file mode 100755
index 0000000000000..ea48653eda5e5
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.15.md
@@ -0,0 +1,56 @@
+---
+version: 0.6.15
+title: Version 0.6.15 (stable)
+author: Isaac Schlueter
+date: 2012-04-09T17:39:18.000Z
+status: publish
+category: release
+slug: version-0-6-15-stable
+layout: blog-post.hbs
+---
+
+<p>2012.04.09 Version 0.6.15 (stable)
+
+</p>
+<ul>
+<li><p>Update npm to 1.1.16</p>
+</li>
+<li><p>Show licenses in binary installers.</p>
+</li>
+<li><p>unix: add uv_fs_read64, uv_fs_write64 and uv_fs_ftruncate64 (Ben Noordhuis)</p>
+</li>
+<li><p>add 64bit offset fs functions (Igor Zinkovsky)</p>
+</li>
+<li><p>windows: don&#39;t report ENOTSOCK when attempting to bind an udp handle twice (Bert Belder)</p>
+</li>
+<li><p>windows: backport pipe-connect-to-file fixes from master (Bert Belder)</p>
+</li>
+<li><p>windows: never call fs event callbacks after closing the watcher (Bert Belder)</p>
+</li>
+<li><p>fs.readFile: don&#39;t make the callback before the fd is closed (Bert Belder)</p>
+</li>
+<li><p>windows: use 64bit offsets for uv_fs apis (Igor Zinkovsky)</p>
+</li>
+<li><p>Fix #2061: segmentation fault on OS X due to stat size mismatch (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz">https://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.15/node-v0.6.15.msi">https://nodejs.org/dist/v0.6.15/node-v0.6.15.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.6.15/x64/">https://nodejs.org/dist/v0.6.15/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg">https://nodejs.org/dist/v0.6.15/node-v0.6.15.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.6.15/">https://nodejs.org/dist/v0.6.15/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.15/">https://nodejs.org/docs/v0.6.15/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.15/api/">https://nodejs.org/docs/v0.6.15/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.16.md b/locale/uk/blog/release/v0.6.16.md
new file mode 100755
index 0000000000000..422e63081c107
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.16.md
@@ -0,0 +1,62 @@
+---
+version: 0.6.16
+title: Version 0.6.16 (stable)
+author: Isaac Schlueter
+date: 2012-04-30T18:13:50.000Z
+status: publish
+category: release
+slug: version-0-6-16-stable
+layout: blog-post.hbs
+---
+
+<p>2012.04.30 Version 0.6.16 (stable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.6.6.25</p>
+</li>
+<li><p>Upgrade npm to 1.1.18</p>
+</li>
+<li><p>Windows: add mappings for UV_ENOENT (Bert Belder)</p>
+</li>
+<li><p>linux: add IN_MOVE_SELF to inotify event mask (Ben Noordhuis)</p>
+</li>
+<li><p>unix: call pipe handle connection cb on accept() error (Ben Noordhuis)</p>
+</li>
+<li><p>unix: handle EWOULDBLOCK (Ben Noordhuis)</p>
+</li>
+<li><p>map EWOULDBLOCK to UV_EAGAIN (Ben Noordhuis)</p>
+</li>
+<li><p>Map ENOMEM to UV_ENOMEM (isaacs)</p>
+</li>
+<li><p>Child process: support the <code>gid</code> and <code>uid</code> options (Bert Belder)</p>
+</li>
+<li><p>test: cluster: add worker death event test (Ben Noordhuis)</p>
+</li>
+<li><p>typo in node_http_parser (isaacs)</p>
+</li>
+<li><p>http_parser: Eat CRLF between requests, even on connection:close. (Ben Noordhuis)</p>
+</li>
+<li><p>don&#39;t check return value of unsetenv (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz">https://nodejs.org/dist/v0.6.16/node-v0.6.16.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.16/node-v0.6.16.msi">https://nodejs.org/dist/v0.6.16/node-v0.6.16.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.6.16/x64/">https://nodejs.org/dist/v0.6.16/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg">https://nodejs.org/dist/v0.6.16/node-v0.6.16.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.6.16/">https://nodejs.org/dist/v0.6.16/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.16/">https://nodejs.org/docs/v0.6.16/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.16/api/">https://nodejs.org/docs/v0.6.16/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.17.md b/locale/uk/blog/release/v0.6.17.md
new file mode 100755
index 0000000000000..a9431096fd7c4
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.17.md
@@ -0,0 +1,50 @@
+---
+version: 0.6.17
+title: Version 0.6.17 (stable)
+author: Isaac Schlueter
+date: 2012-05-04T20:33:12.000Z
+status: publish
+category: release
+slug: version-0-6-17-stable
+layout: blog-post.hbs
+---
+
+<p>2012.05.04 Version 0.6.17 (stable)
+
+</p>
+<ul>
+<li><p>Upgrade npm to 1.1.21</p>
+</li>
+<li><p>uv: Add support for EROFS errors (Ben Noordhuis, Maciej Małecki)</p>
+</li>
+<li><p>uv: Add support for EIO and ENOSPC errors (Fedor Indutny)</p>
+</li>
+<li><p>windows: Add support for EXDEV errors (Bert Belder)</p>
+</li>
+<li><p>http: Fix client memory leaks (isaacs, Vincent Voyer)</p>
+</li>
+<li><p>fs: fix file descriptor leak in sync functions (Ben Noordhuis)</p>
+</li>
+<li><p>fs: fix ReadStream / WriteStream double close bug (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz">https://nodejs.org/dist/v0.6.17/node-v0.6.17.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.17/node-v0.6.17.msi">https://nodejs.org/dist/v0.6.17/node-v0.6.17.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.6.17/x64/">https://nodejs.org/dist/v0.6.17/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg">https://nodejs.org/dist/v0.6.17/node-v0.6.17.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.6.17/">https://nodejs.org/dist/v0.6.17/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.17/">https://nodejs.org/docs/v0.6.17/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.17/api/">https://nodejs.org/docs/v0.6.17/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.18.md b/locale/uk/blog/release/v0.6.18.md
new file mode 100755
index 0000000000000..b4099a0b0e602
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.18.md
@@ -0,0 +1,62 @@
+---
+version: 0.6.18
+title: Version 0.6.18 (stable)
+author: Isaac Schlueter
+date: 2012-05-15T17:06:13.000Z
+status: publish
+category: release
+slug: version-0-6-18-stable
+layout: blog-post.hbs
+---
+
+<p>2012.05.15 Version 0.6.18 (stable)
+
+</p>
+<ul>
+<li><p>windows: skip GetFileAttributes call when opening a file (Bert Belder)</p>
+</li>
+<li><p>crypto: add PKCS12/PFX support (Sambasiva Suda)</p>
+</li>
+<li><p>#3240: child_process: delete NODE_CHANNEL_FD from env in spawn (Ben Noordhuis)</p>
+</li>
+<li><p>windows: add test for path.normalize with UNC paths (Bert Belder)</p>
+</li>
+<li><p>windows: make path.normalize convert all slashes to backslashes (Bert Belder)</p>
+</li>
+<li><p>fs: Automatically close FSWatcher on error (Bert Belder)</p>
+</li>
+<li><p>#3258: fs.ReadStream.pause() emits duplicate data event (koichik)</p>
+</li>
+<li><p>pipe_wrap: don&#39;t assert() on pipe accept errors (Ben Noordhuis)</p>
+</li>
+<li><p>Better exception output for module load and process.nextTick (Felix Geisendörfer)</p>
+</li>
+<li><p>zlib: fix error reporting (Ben Noordhuis)</p>
+</li>
+<li><p>http: Don&#39;t destroy on timeout (isaacs)</p>
+</li>
+<li><p>#3231: http: Don&#39;t try to emit error on a null&#39;ed req object (isaacs)</p>
+</li>
+<li><p>#3236: http: Refactor ClientRequest.onSocket (isaacs)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz">https://nodejs.org/dist/v0.6.18/node-v0.6.18.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.18/node-v0.6.18.msi">https://nodejs.org/dist/v0.6.18/node-v0.6.18.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.6.18/x64/">https://nodejs.org/dist/v0.6.18/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg">https://nodejs.org/dist/v0.6.18/node-v0.6.18.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.6.18/">https://nodejs.org/dist/v0.6.18/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.18/">https://nodejs.org/docs/v0.6.18/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.18/api/">https://nodejs.org/docs/v0.6.18/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.6.19.md b/locale/uk/blog/release/v0.6.19.md
new file mode 100755
index 0000000000000..f5f89eb269afc
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.19.md
@@ -0,0 +1,64 @@
+---
+version: 0.6.19
+title: Node Version 0.6.19 (stable)
+author: Isaac Schlueter
+date: 2012-06-06T16:55:37.000Z
+status: publish
+category: release
+slug: node-version-0-6-19-stable
+layout: blog-post.hbs
+---
+
+<p>2012.06.06 Version 0.6.19 (stable)
+
+</p>
+<ul>
+<li><p>npm: upgrade to 1.1.24</p>
+</li>
+<li><p>fs: no end emit after createReadStream.pause() (Andreas Madsen)</p>
+</li>
+<li><p>vm: cleanup module memory leakage (Marcel Laverdet)</p>
+</li>
+<li><p>unix: fix loop starvation under high network load (Ben Noordhuis)</p>
+</li>
+<li><p>unix: remove abort() in ev_unref() (Ben Noordhuis)</p>
+</li>
+<li><p>windows/tty: never report error after forcibly aborting line-buffered read (Bert Belder)</p>
+</li>
+<li><p>windows: skip GetFileAttributes call when opening a file (Bert Belder)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz">https://nodejs.org/dist/v0.6.19/node-v0.6.19.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.19/node-v0.6.19.msi">https://nodejs.org/dist/v0.6.19/node-v0.6.19.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.6.19/x64/">https://nodejs.org/dist/v0.6.19/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg">https://nodejs.org/dist/v0.6.19/node-v0.6.19.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.6.19/">https://nodejs.org/dist/v0.6.19/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.19/">https://nodejs.org/docs/v0.6.19/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.19/api/">https://nodejs.org/docs/v0.6.19/api/</a>
+</p>
+
+<p>Shasums:</p>
+<pre>ef4f5c1e5f12f6ef3478a794d6a81f59669332f9  node-v0.6.19.msi
+781616f33208f532f168633758a648c20e1ea68b  node-v0.6.19.pkg
+f6c5cfbadff4788ac3a95f8263a0c2f4e07444b6  node-v0.6.19.tar.gz
+10f729ca236825821d97556441fa64f994cb4ca8  node.exe
+5b8cd02e5f92ed6512aabdac11766ad8c1abc436  node.exp
+20037e4901de605e08e48d0c85531334912844e3  node.lib
+c44f62852918d449850014d9b29dd073cb6920a5  node.pdb
+04db25c93c5357394941dd2de12cb61959eb82d1  x64/node-v0.6.19.msi
+f77c77f2e470cfc9071853af2f277ba91d660b9c  x64/node.exe
+fcf26a3f984a3f19804e0567414604b77b1d3bac  x64/node.exp
+bfed2a24f253dbac99379d6f22fc8e9e85ade7ed  x64/node.lib
+95226c1cc5170ea05c2e54431040f06c3e95e99f  x64/node.pdb</pre>
diff --git a/locale/uk/blog/release/v0.6.2.md b/locale/uk/blog/release/v0.6.2.md
new file mode 100755
index 0000000000000..62e6146f002fd
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.2.md
@@ -0,0 +1,30 @@
+---
+version: 0.6.2
+title: Node v0.6.2
+author: bennoordhuis
+date: 2011-11-18T23:35:32.000Z
+status: publish
+category: release
+slug: node-v0-6-2
+layout: blog-post.hbs
+---
+
+<p>2011.11.18, Version 0.6.2 (stable)</p>
+<ul>
+<li>doc improvements (Artur Adib, Trevor Burnham, Ryan Emery, Trent Mick)</li>
+<li>timers: remember extra setTimeout() arguments when timeout==0</li>
+<li>punycode: use Mathias Bynens's punycode library, it's more compliant</li>
+<li>repl: improved tab completion (Ryan Emery)</li>
+<li>buffer: fix range checks in .writeInt() functions (Lukasz Walukiewicz)</li>
+<li>tls: make cipher list configurable</li>
+<li>addons: make Buffer and ObjectWrap visible to Windows add-ons (Bert Belder)</li>
+<li>crypto: add PKCS#1 a.k.a RSA public key verification support</li>
+<li>windows: fix stdout writes when redirected to nul</li>
+<li>sunos: fix build on Solaris and Illumos</li>
+<li>Upgrade V8 to 3.6.6.8</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz">https://nodejs.org/dist/v0.6.2/node-v0.6.2.tar.gz</a></p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.2/node-v0.6.2.msi">https://nodejs.org/dist/v0.6.2/node-v0.6.2.msi</a></p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg">https://nodejs.org/dist/v0.6.2/node-v0.6.2.pkg</a></p>
+<p>Website: <a href="https://nodejs.org/docs/v0.6.2/">https://nodejs.org/docs/v0.6.2/</a></p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.2/api/">https://nodejs.org/docs/v0.6.2/api/</a></p>
diff --git a/locale/uk/blog/release/v0.6.20.md b/locale/uk/blog/release/v0.6.20.md
new file mode 100755
index 0000000000000..ea392a623a114
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.20.md
@@ -0,0 +1,54 @@
+---
+version: 0.6.20
+title: Version 0.6.20 (maintenance)
+category: release
+slug: node-v0-6-20-maintenance
+date: 2012-07-10T16:00:00.000Z
+layout: blog-post.hbs
+---
+
+2012.07.10 Version 0.6.20 (maintenance)
+
+* npm: Upgrade to 1.1.37 (isaacs)
+
+* benchmark: Backport improvements made in master (isaacs)
+
+* build: always link with -lz (Trent Mick)
+
+* core: use proper #include directives (Ben Noordhuis)
+
+* cluster: don't silently drop messages when the write queue gets big (Bert Belder)
+
+* windows: don't print error when GetConsoleTitleW returns an empty string (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.6.20/node-v0.6.20.tar.gz
+
+Windows Installer: https://nodejs.org/dist/v0.6.20/node-v0.6.20.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.6.20/x64/
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.20/node-v0.6.20.pkg
+
+Other release files: https://nodejs.org/dist/v0.6.20/
+
+Website: https://nodejs.org/docs/v0.6.20/
+
+Documentation: https://nodejs.org/docs/v0.6.20/api/
+
+Shasums:
+
+```
+5029f30e6af79e7a9a1d45396afbe20229059b47  node-v0.6.20.msi
+370105015bae2a77e4da41564ad3df8fcd0acaec  node-v0.6.20.pkg
+91da1dde9badd5250f3d4829c47757de0caab84b  node-v0.6.20.tar.gz
+efa29addd716c175d945ade5dfa2b9ebd7f6fed8  node.exe
+aab0e367adcc9fdee479dbe67a32c6b27ee35960  node.exp
+ce6c455937f96eb671f44dc731d628849fa8b350  node.lib
+a8db5c269de9c3059684f9aa3de5a4cdbd9b3d12  node.pdb
+22f97ba2c678b4c8a1def251269920ee46c90bca  x64/node-v0.6.20.msi
+276136ae7f6e2e59d0ae26d434e4d6ab65769957  x64/node.exe
+af56811749aa4fe013a36f7bccecfb94587c0afd  x64/node.exp
+a629af1b4f6f4b82e332c35695fff956bd555f3b  x64/node.lib
+3b2d22b20efeb06bf3d86378168d604dbe52eb08  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.6.21.md b/locale/uk/blog/release/v0.6.21.md
new file mode 100755
index 0000000000000..e2a0c8add310d
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.21.md
@@ -0,0 +1,46 @@
+---
+version: 0.6.21
+title: Version 0.6.21 (maintenance)
+category: release
+slug: node-v0-6-21-maintenance
+date: 2012-08-03T21:44:02.000Z
+layout: blog-post.hbs
+---
+
+2012.08.03 Version 0.6.21 (maintenance)
+
+* sunos: work around OS bug to prevent fs.watch() from spinning (Bryan Cantrill)
+
+* net: make pause/resume work with connecting sockets (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.6.21/node-v0.6.21.tar.gz
+
+Windows Installer: https://nodejs.org/dist/v0.6.21/node-v0.6.21.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.6.21/x64/
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.6.21/node-v0.6.21.pkg
+
+Other release files: https://nodejs.org/dist/v0.6.21/
+
+Website: https://nodejs.org/docs/v0.6.21/
+
+Documentation: https://nodejs.org/docs/v0.6.21/api/
+
+Shasums:
+
+```
+04f58b0da23c3db291d84ac55a924332ad83c427  node-v0.6.21.pkg
+31f564bf34c64b07cae3b9a88a87b4a08bab4dc5  node-v0.6.21.tar.gz
+1e3184fe2cfe7140a88b5dcc9c2ec7d32f1f5af5  node.exe
+b8887a056152622c08ee10f5867bd27910260477  node.exp
+c6468ffe2e145e7db1bb3e2d66adb9f5d50271ad  node.lib
+2a896bcb7c83f2fa710650116580daf4ac5e6c4c  node.msi
+207441e8c3dc184c478367b775dc7ece1ee36501  node.pdb
+715ad9946db5f97c54a53bdea6bbe9ba69f2f299  x64/node.exe
+2fa2c2d82fedeec1ed8be5d908b790f473d4a7c2  x64/node.exp
+b403cb71d4cf21e97a78d446403cedc9795bcf69  x64/node.lib
+ef47520dbc6a1a68ec37d290c421031cfd670048  x64/node.msi
+fb15e3991c420f3ae67ade92b11b07bb9112124a  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.6.3.md b/locale/uk/blog/release/v0.6.3.md
new file mode 100755
index 0000000000000..2e8633d8883d0
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.3.md
@@ -0,0 +1,33 @@
+---
+version: 0.6.3
+title: Node v0.6.3
+author: piscisaureus
+date: 2011-11-25T10:54:08.000Z
+status: publish
+category: release
+slug: node-v0-6-3
+layout: blog-post.hbs
+---
+
+2011.11.25, Version 0.6.3 (stable)
+<ul>
+    <li>#2083 Land NPM in Node. It is included in packages/installers and installed on `make install`.</li>
+    <li>#2076 Add logos to windows installer.</li>
+    <li>#1711 Correctly handle http requests without headers. (Ben Noordhuis, Felix Geisendörfer)</li>
+    <li>TLS: expose more openssl SSL context options and constants. (Ben Noordhuis)</li>
+    <li>#2177 Windows: don't kill UDP socket when a packet fails to reach its destination. (Bert Belder)</li>
+    <li>Windows: support paths longer than 260 characters. (Igor Zinkovsky)</li>
+    <li>Windows: correctly resolve drive-relative paths. (Bert Belder)</li>
+    <li>#2166 Don't leave file descriptor open after lchmod. (Isaac Schlueter)</li>
+    <li>#2084 Add OS X .pkg build script to make file.</li>
+    <li>#2160 Documentation improvements. (Ben Noordhuis)</li>
+</ul>
+Source Code: <a href="https://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz">https://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz</a>
+
+Windows Installer: <a href="https://nodejs.org/dist/v0.6.3/node-v0.6.3.msi">https://nodejs.org/dist/v0.6.3/node-v0.6.3.msi</a>
+
+Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg">https://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg</a>
+
+Website: <a href="https://nodejs.org/docs/v0.6.3/">https://nodejs.org/docs/v0.6.3/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.6.3/api/">https://nodejs.org/docs/v0.6.3/api/</a>
diff --git a/locale/uk/blog/release/v0.6.4.md b/locale/uk/blog/release/v0.6.4.md
new file mode 100755
index 0000000000000..a05d5ba620fb4
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.4.md
@@ -0,0 +1,34 @@
+---
+version: 0.6.4
+title: Node v0.6.4
+author: bennoordhuis
+date: 2011-12-02T02:20:14.000Z
+status: publish
+category: release
+slug: node-v0-6-4
+layout: blog-post.hbs
+---
+
+2011.12.02, Version 0.6.4 (stable)
+<ul>
+<li>doc improvements (Kyle Young, Tim Oxley, Roman Shtylman, Mathias Bynens)</li>
+<li>upgrade bundled npm (Isaac Schlueter)</li>
+<li>polish Windows installer (Igor Zinkovsky, Isaac Schlueter)</li>
+<li>punycode: upgrade to v0.2.1 (Mathias Bynens)</li>
+<li>build: add --without-npm flag to configure script</li>
+<li>sys: deprecate module some more, print stack trace if NODE_DEBUG=sys</li>
+<li>cli: add -p switch, prints result of --eval</li>
+<li>#1997: fix Blowfish ECB encryption and decryption (Ingmar Runge)</li>
+<li>#2223: fix socket 'close' event being emitted twice</li>
+<li>#2224: fix RSS memory usage &gt; 4 GB reporting (Russ Bradberry)</li>
+<li>#2225: fix util.inspect() object stringification bug (Nathan Rajlich)</li>
+</ul>
+Source Code: <a href="https://nodejs.org/dist/v0.6.4/node-v0.6.4.tar.gz">https://nodejs.org/dist/v0.6.4/node-v0.6.4.tar.gz</a>
+
+Windows Installer: <a href="https://nodejs.org/dist/v0.6.4/node-v0.6.4.msi">https://nodejs.org/dist/v0.6.4/node-v0.6.4.msi</a>
+
+Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.4/node-v0.6.4.pkg">https://nodejs.org/dist/v0.6.4/node-v0.6.4.pkg</a>
+
+Website: <a href="https://nodejs.org/docs/v0.6.4/">https://nodejs.org/docs/v0.6.4/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.6.4/api/">https://nodejs.org/docs/v0.6.4/api/</a>
diff --git a/locale/uk/blog/release/v0.6.5.md b/locale/uk/blog/release/v0.6.5.md
new file mode 100755
index 0000000000000..b91747b987afd
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.5.md
@@ -0,0 +1,24 @@
+---
+version: 0.6.5
+title: Node v0.6.5
+author: ryandahl
+date: 2011-12-04T08:59:57.000Z
+status: publish
+category: release
+slug: node-v0-6-5
+layout: blog-post.hbs
+---
+
+2011.12.04, Version 0.6.5 (stable)
+<ul><li>npm workaround Windows antivirus software (isaacs)
+<li>Upgrade V8 to 3.6.6.11</ul>
+
+Source Code: <a href="https://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz">https://nodejs.org/dist/v0.6.5/node-v0.6.5.tar.gz</a>
+
+Windows Installer: <a href="https://nodejs.org/dist/v0.6.5/node-v0.6.5.msi">https://nodejs.org/dist/v0.6.5/node-v0.6.5.msi</a>
+
+Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.5/node-v0.6.5.pkg">https://nodejs.org/dist/v0.6.5/node-v0.6.5.pkg</a>
+
+Website: <a href="https://nodejs.org/docs/v0.6.5/">https://nodejs.org/docs/v0.6.5/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.6.5/api/">https://nodejs.org/docs/v0.6.5/api/</a>
diff --git a/locale/uk/blog/release/v0.6.6.md b/locale/uk/blog/release/v0.6.6.md
new file mode 100755
index 0000000000000..c61292a36912d
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.6.md
@@ -0,0 +1,35 @@
+---
+version: 0.6.6
+title: Node v0.6.6
+author: Isaac Schlueter
+date: 2011-12-15T19:07:57.000Z
+status: publish
+category: release
+slug: node-v0-6-6
+layout: blog-post.hbs
+---
+
+2011.12.14, Version 0.6.6 (stable)
+
+<ul>
+<li>npm update to 1.1.0-beta-4 (Isaac Z. Schlueter)</li>
+<li>cli: fix output of --help (Ben Noordhuis)</li>
+<li>new website</li>
+<li>pause/resume semantics for stdin (Isaac Z. Schlueter)</li>
+<li>Travis CI integration (Maciej Małecki)</li>
+<li>child_process: Fix bug regarding closed stdin (Ben Noordhuis)</li>
+<li>Enable upgrades in MSI. (Igor Zinkovsky)</li>
+<li>net: Fixes memory leak (Ben Noordhuis)</li>
+<li>fs: handle fractional or NaN ReadStream buffer size (Ben Noordhuis)</li>
+<li>crypto: fix memory leaks in PBKDF2 error path (Ben Noordhuis)</li>
+</ul>
+
+Source Code: <a href="https://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz">https://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz</a>
+
+Windows Installer: <a href="https://nodejs.org/dist/v0.6.6/node-v0.6.6.msi">https://nodejs.org/dist/v0.6.6/node-v0.6.6.msi</a>
+
+Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.6/node-v0.6.6.pkg">https://nodejs.org/dist/v0.6.6/node-v0.6.6.pkg</a>
+
+Website: <a href="https://nodejs.org/docs/v0.6.6/">https://nodejs.org/docs/v0.6.6/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.6.6/api/">https://nodejs.org/docs/v0.6.6/api/</a>
diff --git a/locale/uk/blog/release/v0.6.7.md b/locale/uk/blog/release/v0.6.7.md
new file mode 100755
index 0000000000000..7d7d87f82e98b
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.7.md
@@ -0,0 +1,44 @@
+---
+version: 0.6.7
+title: Node v0.6.7
+author: Isaac Schlueter
+date: 2012-01-07T01:54:49.000Z
+status: publish
+category: release
+slug: node-v0-6-7
+layout: blog-post.hbs
+---
+
+<p>2012.01.06, Version 0.6.7 (stable)</p>
+
+<ul>
+<li><p>V8 hash collision fix (Breaks MIPS) (Bert Belder, Erik Corry)</p></li>
+<li><p>Upgrade V8 to 3.6.6.15</p></li>
+<li><p>Upgrade npm to 1.1.0-beta-10 (isaacs)</p></li>
+<li><p>many doc updates (Ben Noordhuis, Jeremy Martin, koichik, Dave Irvine,
+Seong-Rak Choi, Shannen, Adam Malcontenti-Wilson, koichik)</p></li>
+<li><p>Fix segfault in <code>node_http_parser.cc</code></p></li>
+<li><p>dgram, timers: fix memory leaks (Ben Noordhuis, Yoshihiro Kikuchi)</p></li>
+<li><p>repl: fix repl.start not passing the <code>ignoreUndefined</code> arg (Damon Oehlman)</p></li>
+<li><p>#1980: Socket.pause null reference when called on a closed Stream (koichik)</p></li>
+<li><p>#2263: XMLHttpRequest piped in a writable file stream hang (koichik)</p></li>
+<li><p>#2069: http resource leak (koichik)</p></li>
+<li><p>buffer.readInt global pollution fix (Phil Sung)</p></li>
+<li><p>timers: fix performance regression (Ben Noordhuis)</p></li>
+<li><p>#2308, #2246: node swallows openssl error on request (koichik)</p></li>
+<li><p>#2114: timers: remove _idleTimeout from item in .unenroll() (James Hartig)</p></li>
+<li><p>#2379: debugger: Request backtrace w/o refs (Fedor Indutny)</p></li>
+<li><p>simple DTrace ustack helper (Dave Pacheco)</p></li>
+<li><p>crypto: rewrite HexDecode without snprintf (Roman Shtylman)</p></li>
+<li><p>crypto: don&#8217;t ignore DH init errors (Ben Noordhuis)</p></li>
+</ul>
+
+<p>Source Code: <a href="https://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz">https://nodejs.org/dist/v0.6.7/node-v0.6.7.tar.gz</a></p>
+
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.7/node-v0.6.7.msi">https://nodejs.org/dist/v0.6.7/node-v0.6.7.msi</a></p>
+
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg">https://nodejs.org/dist/v0.6.7/node-v0.6.7.pkg</a></p>
+
+<p>Website: <a href="https://nodejs.org/docs/v0.6.7/">https://nodejs.org/docs/v0.6.7/</a></p>
+
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.7/api/">https://nodejs.org/docs/v0.6.7/api/</a></p>
diff --git a/locale/uk/blog/release/v0.6.8.md b/locale/uk/blog/release/v0.6.8.md
new file mode 100755
index 0000000000000..9edacecdad242
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.8.md
@@ -0,0 +1,34 @@
+---
+version: 0.6.8
+title: Node v0.6.8
+author: Isaac Schlueter
+date: 2012-01-20T03:59:53.000Z
+status: publish
+category: release
+slug: node-v0-6-8
+layout: blog-post.hbs
+---
+
+<p>2012.01.19, Version 0.6.8 (stable)</p>
+
+<ul>
+<li><p>Update V8 to 3.6.6.19</p></li>
+<li><p>Numeric key hash collision fix for V8 (Erik Corry, Fedor Indutny)</p></li>
+<li><p>Add missing TTY key translations for F1-F5 on Windows (Brandon Benvie)</p></li>
+<li><p>path.extname bugfix with . and .. paths (Bert Belder)</p></li>
+<li><p>cluster: don't always kill the master on uncaughtException (Ben Noordhuis)</p></li>
+<li><p>Update npm to 1.1.0-2 (isaacs)</p></li>
+<li><p>typed arrays: set class name (Ben Noordhuis)</p></li>
+<li><p>zlib binding cleanup (isaacs, Bert Belder)</p></li>
+<li><p>dgram: use slab memory allocator (Michael Bernstein)</p></li>
+<li><p>fix segfault #2473</p></li>
+<li><p>#2521 60% improvement in fs.stat on Windows (Igor Zinkovsky)</p></li>
+</ul><p>Source Code: <a href="https://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz">https://nodejs.org/dist/v0.6.8/node-v0.6.8.tar.gz</a></p>
+
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.8/node-v0.6.8.msi">https://nodejs.org/dist/v0.6.8/node-v0.6.8.msi</a></p>
+
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg">https://nodejs.org/dist/v0.6.8/node-v0.6.8.pkg</a></p>
+
+<p>Website: <a href="https://nodejs.org/docs/v0.6.8/">https://nodejs.org/docs/v0.6.8/</a></p>
+
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.8/api/">https://nodejs.org/docs/v0.6.8/api/</a></p>
diff --git a/locale/uk/blog/release/v0.6.9.md b/locale/uk/blog/release/v0.6.9.md
new file mode 100755
index 0000000000000..2f6a5e7229080
--- /dev/null
+++ b/locale/uk/blog/release/v0.6.9.md
@@ -0,0 +1,33 @@
+---
+version: 0.6.9
+title: Node v0.6.9
+author: Isaac Schlueter
+date: 2012-01-28T00:58:18.000Z
+status: publish
+category: release
+slug: node-v0-6-9
+layout: blog-post.hbs
+---
+
+<p>2012.01.27, Version 0.6.9 (stable)</p>
+
+<ul>
+<li>
+<p>dgram: Bring back missing functionality for Unix (Dan VerWeire,
+Roman Shtylman, Ben Noordhuis)</p>
+<p>- Note: Windows UDP support not yet complete.</p></li>
+<li><p>http: Fix parser memory leak (koichik)</p></li>
+<li><p>zlib: Fix #2365 crashes on invalid input (Nicolas LaCasse)</p></li>
+<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>
+<li><p>Documentation Restyling (Matthew Fitzsimmons)</p></li>
+<li><p>Update npm to 1.1.0-3 (isaacs)</p></li>
+<li><p>Windows: fix regression in stat() calls to C:\ (Bert Belder)</p></li>
+</ul><p>Source Code: <a href="https://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz">https://nodejs.org/dist/v0.6.9/node-v0.6.9.tar.gz</a></p>
+
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.6.9/node-v0.6.9.msi">https://nodejs.org/dist/v0.6.9/node-v0.6.9.msi</a></p>
+
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg">https://nodejs.org/dist/v0.6.9/node-v0.6.9.pkg</a></p>
+
+<p>Website: <a href="https://nodejs.org/docs/v0.6.9/">https://nodejs.org/docs/v0.6.9/</a></p>
+
+<p>Documentation: <a href="https://nodejs.org/docs/v0.6.9/api/">https://nodejs.org/docs/v0.6.9/api/</a></p>
diff --git a/locale/uk/blog/release/v0.7.0.md b/locale/uk/blog/release/v0.7.0.md
new file mode 100755
index 0000000000000..6402dfbbaaa7c
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.0.md
@@ -0,0 +1,32 @@
+---
+version: 0.7.0
+title: Node v0.7.0 (Unstable)
+author: ryandahl
+date: 2012-01-17T03:58:28.000Z
+status: publish
+category: release
+slug: node-v0-7-0-unstable
+layout: blog-post.hbs
+---
+
+<strong>This is the first release in the unstable v0.7 series. Almost all users will want to remain using the stable v0.6 releases.</strong>
+
+2012.01.16, Version 0.7.0 (unstable)
+<ul>
+<li>Upgrade V8 to 3.8.6
+<li>Use GYP build system on unix (Ben Noordhuis)
+<li>Experimental isolates support (Ben Noordhuis)
+<li>Improvements to Cluster API (Andreas Madsen)
+<li>Use isolates for internal debugger (Fedor Indutny)
+<li>Bug fixes</ul>
+
+
+Source Code: <a href="https://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz">https://nodejs.org/dist/v0.7.0/node-v0.7.0.tar.gz</a>
+
+Windows Installer: <a href="https://nodejs.org/dist/v0.7.0/node-v0.7.0.msi">https://nodejs.org/dist/v0.7.0/node-v0.7.0.msi</a>
+
+Macintosh Installer: <a href="https://nodejs.org/dist/v0.7.0/node-v0.7.0.pkg">https://nodejs.org/dist/v0.7.0/node-v0.7.0.pkg</a>
+
+Website: <a href="https://nodejs.org/docs/v0.7.0/">https://nodejs.org/docs/v0.7.0/</a>
+
+Documentation: <a href="https://nodejs.org/docs/v0.7.0/api/">https://nodejs.org/docs/v0.7.0/api/</a>
diff --git a/locale/uk/blog/release/v0.7.1.md b/locale/uk/blog/release/v0.7.1.md
new file mode 100755
index 0000000000000..9a502ea6b69d1
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.1.md
@@ -0,0 +1,33 @@
+---
+version: 0.7.1
+title: Node v0.7.1
+author: Isaac Schlueter
+date: 2012-01-24T01:35:59.000Z
+status: publish
+category: release
+slug: node-v0-7-1
+layout: blog-post.hbs
+---
+
+<p>2012.01.23, Version 0.7.1 (unstable)</p>
+
+<ul>
+<li><p>Update V8 to 3.8.8</p></li>
+<li><p>Install node-waf by default (Fedor Indutny)</p></li>
+<li><p>crypto: Add ability to turn off PKCS padding (Ingmar Runge)</p></li>
+<li><p>v8: implement VirtualMemory class on SunOS (Ben Noordhuis)</p></li>
+<li><p>Add cluster.setupMaster (Andreas Madsen)</p></li>
+<li><p>move <code>path.exists*</code> to <code>fs.exists*</code> (Maciej Małecki)</p></li>
+<li><p>typed arrays: set class name (Ben Noordhuis)</p></li>
+<li><p>libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)</p></li>
+</ul>
+
+<p>Source: <a href="https://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz">https://nodejs.org/dist/v0.7.1/node-v0.7.1.tar.gz</a></p>
+
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.1/node-v0.7.1.msi">https://nodejs.org/dist/v0.7.1/node-v0.7.1.msi</a></p>
+
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg">https://nodejs.org/dist/v0.7.1/node-v0.7.1.pkg</a></p>
+
+<p>Website: <a href="https://nodejs.org/docs/v0.7.1/">https://nodejs.org/docs/v0.7.1/</a></p>
+
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.1/api/">https://nodejs.org/docs/v0.7.1/api/</a></p>
diff --git a/locale/uk/blog/release/v0.7.10.md b/locale/uk/blog/release/v0.7.10.md
new file mode 100755
index 0000000000000..494b1d6f16197
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.10.md
@@ -0,0 +1,89 @@
+---
+version: 0.7.10
+title: Version 0.7.10 (unstable)
+author: Isaac Schlueter
+date: 2012-06-11T16:00:25.000Z
+status: publish
+category: release
+slug: version-0-7-10-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.06.11, Version 0.7.10 (unstable)
+
+</p>
+<p>This is the second-to-last release on the 0.7 branch.  Version 0.8.0
+will be released some time next week.  As other even-numbered Node
+releases before it, the v0.8.x releases will maintain API and binary
+compatibility.
+
+</p>
+<p>The major changes are detailed in
+<a href="https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8">https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8</a>
+
+</p>
+<p>Please try out this release.  There will be very few changes between
+this and the v0.8.x release family.  This is the last chance to comment
+on the API before it is locked down for stability.
+
+
+</p>
+<ul>
+<li><p>Roll V8 back to 3.9.24.31</p>
+</li>
+<li><p>build: x64 target should always pass -m64 (Robert Mustacchi)</p>
+</li>
+<li><p>add NODE_EXTERN to node::Start (Joel Brandt)</p>
+</li>
+<li><p>repl: Warn about running npm commands (isaacs)</p>
+</li>
+<li><p>slab_allocator: fix crash in dtor if V8 is dead (Ben Noordhuis)</p>
+</li>
+<li><p>slab_allocator: fix leak of Persistent handles (Shigeki Ohtsu)</p>
+</li>
+<li><p>windows/msi: add node.js prompt to startmenu (Jeroen Janssen)</p>
+</li>
+<li><p>windows/msi: fix adding node to PATH (Jeroen Janssen)</p>
+</li>
+<li><p>windows/msi: add start menu links when installing (Jeroen Janssen)</p>
+</li>
+<li><p>windows: don&#39;t install x64 version into the &#39;program files (x86)&#39; folder (Matt Gollob)</p>
+</li>
+<li><p>domain: Fix #3379 domain.intercept no longer passes error arg to cb (Marc Harter)</p>
+</li>
+<li><p>fs: make callbacks run in global context (Ben Noordhuis)</p>
+</li>
+<li><p>fs: enable fs.realpath on windows (isaacs)</p>
+</li>
+<li><p>child_process: expose UV_PROCESS_DETACHED as options.detached (Charlie McConnell)</p>
+</li>
+<li><p>child_process: new stdio API for .spawn() method (Fedor Indutny)</p>
+</li>
+<li><p>child_process: spawn().ref() and spawn().unref() (Fedor Indutny)</p>
+</li>
+<li><p>Upgrade npm to 1.1.25</p>
+</li>
+<ul><li>Enable npm link on windows</li>
+<li>Properly remove sh-shim on Windows</li>
+<li>Abstract out registry client and logger</li></ul>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz">https://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.10/node-v0.7.10.msi">https://nodejs.org/dist/v0.7.10/node-v0.7.10.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.10/x64/">https://nodejs.org/dist/v0.7.10/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg">https://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.10/">https://nodejs.org/dist/v0.7.10/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.10/">https://nodejs.org/docs/v0.7.10/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.10/api/">https://nodejs.org/docs/v0.7.10/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.11.md b/locale/uk/blog/release/v0.7.11.md
new file mode 100755
index 0000000000000..ef17e57ae5ed2
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.11.md
@@ -0,0 +1,83 @@
+---
+version: 0.7.11
+title: Version 0.7.11 (unstable)
+author: Isaac Schlueter
+date: 2012-06-15T19:45:20.000Z
+status: publish
+category: release
+slug: version-0-7-11-unstable
+layout: blog-post.hbs
+---
+
+<p>This is the most stable 0.7 release yet.  Please try it out.
+
+</p>
+<p>Version 0.8 will be out very soon.  You can follow the remaining issues
+on the github issue tracker.
+
+</p>
+<p><a href="https://github.com/joyent/node/issues?milestone=10&amp;state=open">https://github.com/joyent/node/issues?milestone=10&amp;state=open</a>
+
+</p>
+<p>2012.06.15, Version 0.7.11 (unstable)
+
+</p>
+<ul>
+<li><p>V8: Upgrade to v3.11.10</p>
+</li>
+<li><p>npm: Upgrade to 1.1.26</p>
+</li>
+<li><p>doc: Improve cross-linking in API docs markdown (Ben Kelly)</p>
+</li>
+<li><p>Fix #3425: removeAllListeners should delete array (Reid Burke)</p>
+</li>
+<li><p>cluster: don&#39;t silently drop messages when the write queue gets big (Bert Belder)</p>
+</li>
+<li><p>Add Buffer.concat method (isaacs)</p>
+</li>
+<li><p>windows: make symlinks tolerant to forward slashes (Bert Belder)</p>
+</li>
+<li><p>build: Add node.d and node.1 to installer (isaacs)</p>
+</li>
+<li><p>cluster: rename worker.unqiueID to worker.id (Andreas Madsen)</p>
+</li>
+<li><p>Windows: Enable ETW events on Windows for existing DTrace probes. (Igor Zinkovsky)</p>
+</li>
+<li><p>test: bundle node-weak in test/gc so that it doesn&#39;t need to be downloaded (Nathan Rajlich)</p>
+</li>
+<li><p>Make many tests pass on Windows (Bert Belder)</p>
+</li>
+<li><p>Fix #3388 Support listening on file descriptors (isaacs)</p>
+</li>
+<li><p>Fix #3407 Add os.tmpDir() (isaacs)</p>
+</li>
+<li><p>Unbreak the snapshotted build on Windows (Bert Belder)</p>
+</li>
+<li><p>Clean up child_process.kill throws (Bert Belder)</p>
+</li>
+<li><p>crypto: make cipher/decipher accept buffer args (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz">https://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg">https://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi">https://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi</a>
+
+</p>
+<p>Windows x64 Installer: <a href="https://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi">https://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.11/x64/">https://nodejs.org/dist/v0.7.11/x64/</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.11/">https://nodejs.org/dist/v0.7.11/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.11/">https://nodejs.org/docs/v0.7.11/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.11/api/">https://nodejs.org/docs/v0.7.11/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.12.md b/locale/uk/blog/release/v0.7.12.md
new file mode 100755
index 0000000000000..09f08dcbcdad6
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.12.md
@@ -0,0 +1,59 @@
+---
+version: 0.7.12
+title: Version 0.7.12
+author: Isaac Schlueter
+date: 2012-06-19T23:31:09.000Z
+status: publish
+category: release
+slug: version-0-7-12
+layout: blog-post.hbs
+---
+
+<p>2012.06.19, Version 0.7.12 (unstable)  </p>
+<p>This is the last release on the 0.7 branch.  Version 0.8.0 will be released some time later this week, barring any major problems.  </p>
+<p>As with other even-numbered Node releases before it, the v0.8.x releases will maintain API and binary compatibility.  </p>
+<p>The major changes between v0.6 and v0.8 are detailed in <a href="https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8">https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8</a>  </p>
+<p>Please try out this release.  There will be very virtually no changes between this and the v0.8.x release family.  This is the last chance to comment before it is locked down for stability.  The API is effectively frozen now.  </p>
+<p>This version adds backwards-compatible shims for binary addons that use libeio and libev directly.  If you find that binary modules that could compile on v0.6 can not compile on this version, please let us know. Note that libev is officially deprecated in v0.8, and will be removed in v0.9.  You should be porting your modules to use libuv as soon as possible.  </p>
+<p>V8 is on 3.11.10 currently, and will remain on the V8 3.11.x branch for the duration of Node v0.8.x.   </p>
+<ul>   <li><p>npm: Upgrade to 1.1.30<br> - Improved &#39;npm init&#39;<br> - Fix the &#39;cb never called&#39; error from &#39;oudated&#39; and &#39;update&#39;<br> - Add --save-bundle|-B config<br> - Fix isaacs/npm#2465: Make npm script and windows shims cygwin-aware<br> - Fix isaacs/npm#2452 Use --save(-dev|-optional) in npm rm<br> - <code>logstream</code> option to replace removed <code>logfd</code> (Rod Vagg)<br> - Read default descriptions from README.md files </p>
+  </li> <li><p>Shims to support deprecated <code>ev_*</code> and <code>eio_*</code> methods (Ben Noordhuis)</p>
+  </li> <li><p>#3118 net.Socket: Delay pause/resume until after connect (isaacs)</p>
+  </li> <li><p>#3465 Add ./configure --no-ifaddrs flag (isaacs)</p>
+  </li> <li><p>child_process: add .stdin stream to forks (Fedor Indutny)</p>
+  </li> <li><p>build: fix <code>make install DESTDIR=/path</code> (Ben Noordhuis)</p>
+  </li> <li><p>tls: fix off-by-one error in renegotiation check (Ben Noordhuis)</p>
+  </li> <li><p>crypto: Fix diffie-hellman key generation UTF-8 errors (Fedor Indutny)</p>
+  </li> <li><p>node: change the constructor name of process from EventEmitter to process (Andreas Madsen)</p>
+  </li> <li><p>net: Prevent property access throws during close (Reid Burke)</p>
+  </li> <li><p>querystring: improved speed and code cleanup (Felix Böhm)</p>
+  </li> <li><p>sunos: fix assertion errors breaking fs.watch() (Fedor Indutny)</p>
+  </li> <li><p>unix: stat: detect sub-second changes (Ben Noordhuis)</p>
+  </li> <li><p>add stat() based file watcher (Ben Noordhuis)</p>
+  </li> </ul> <p>Source Code: <a href="https://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz">https://nodejs.org/dist/v0.7.12/node-v0.7.12.tar.gz</a>  </p>
+  <p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg">https://nodejs.org/dist/v0.7.12/node-v0.7.12.pkg</a>  </p>
+  <p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi">https://nodejs.org/dist/v0.7.12/node-v0.7.12-x86.msi</a>  </p>
+  <p>Windows x64 Installer: <a href="https://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi">https://nodejs.org/dist/v0.7.12/x64/node-v0.7.12-x64.msi</a>  </p>
+  <p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.12/x64/">https://nodejs.org/dist/v0.7.12/x64/</a>  </p>
+  <p>Other release files: <a href="https://nodejs.org/dist/v0.7.12/">https://nodejs.org/dist/v0.7.12/</a>  </p>
+  <p>Website: <a href="https://nodejs.org/docs/v0.7.12/">https://nodejs.org/docs/v0.7.12/</a>  </p>
+  <p>Documentation: <a href="https://nodejs.org/docs/v0.7.12/api/">https://nodejs.org/docs/v0.7.12/api/</a> </p>
+
+<h2>Shasums</h2>
+
+<pre>ded6a2197b1149b594eb45fea921e8538ba442aa  blog.html
+dfabff0923d4b4f1d53bd9831514c1ac8c4b1876  email.md
+be313d35511e6d7e43cae5fa2b18f3e0d2275ba1  node-v0.7.12-x86.msi
+8f7ba0c8283e3863de32fd5c034f5b599c78f830  node-v0.7.12.pkg
+cb570abacbf4eb7e23c3d2620d00dd3080d9c19d  node-v0.7.12.tar.gz
+e13a6edfcba1c67ffe794982dd20a222ce8ce40f  node.exe
+20906ad76a43eca52795b2a089654a105e11c1e6  node.exp
+acbcbb87b6f7f2af34a3ed0abe6131d9e7a237af  node.lib
+4013d5b25fe36ae4245433b972818686cd9a2205  node.pdb
+6c0a7a2e8ee360e2800156293fb2f6a5c1a57382  npm-1.1.30.tgz
+9d23e42e8260fa20001d5618d2583a62792bf63f  npm-1.1.30.zip
+840157b2d6f7389ba70b07fc9ddc048b92c501cc  x64/node-v0.7.12-x64.msi
+862d42706c21ea83bf73cd827101f0fe598b0cf7  x64/node.exe
+de0af95fac083762f99c875f91bab830dc030f71  x64/node.exp
+3122bd886dfb96f3b41846cef0bdd7e97326044a  x64/node.lib
+e0fa4e42cd19cadf8179e492ca606b7232bbc018  x64/node.pdb</pre>
diff --git a/locale/uk/blog/release/v0.7.2.md b/locale/uk/blog/release/v0.7.2.md
new file mode 100755
index 0000000000000..42a57ce17c3f7
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.2.md
@@ -0,0 +1,35 @@
+---
+version: 0.7.2
+title: Node v0.7.2 (unstable)
+author: Isaac Schlueter
+date: 2012-02-01T21:13:04.000Z
+status: publish
+category: release
+slug: node-v0-7-2-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.02.01, Version 0.7.2 (unstable)</p>
+
+<ul>
+<li><p>Update V8 to 3.8.9</p></li>
+<li><p>Support for sharing streams across Isolates (Igor Zinkovsky)</p></li>
+<li><p>#2636 - Fix case where http_parsers are freed too early (koichik)</p></li>
+<li><p>url: Support for IPv6 addresses in URLs (Łukasz Walukiewicz)</p></li>
+<li><p>child_process: Add disconnect() method to child processes (Andreas Madsen)</p></li>
+<li><p>fs: add O_EXCL support, exclusive open file (Ben Noordhuis)</p></li>
+<li><p>fs: more specific error messages (Tj Holowaychuk)</p></li>
+<li><p>tty: emit 'unknown' key event if key sequence not found (Dan VerWeire, Nathan Rajlich)</p></li>
+<li><p>build: compile release build too if BUILDTYPE=Debug (Ben Noordhuis)</p></li>
+<li><p>module: fix --debug-brk on symlinked scripts (Fedor Indutny)</p></li>
+<li><p>zlib: fix <code>Failed to set dictionary</code> issue (Fedor Indutny)</p></li>
+<li><p>waf: predict target arch for OS X (Fedor Indutny)</p></li>
+</ul><p>Source Code: <a href="https://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz">https://nodejs.org/dist/v0.7.2/node-v0.7.2.tar.gz</a></p>
+
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.2/node-v0.7.2.msi">https://nodejs.org/dist/v0.7.2/node-v0.7.2.msi</a></p>
+
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg">https://nodejs.org/dist/v0.7.2/node-v0.7.2.pkg</a></p>
+
+<p>Website: <a href="https://nodejs.org/docs/v0.7.2/">https://nodejs.org/docs/v0.7.2/</a></p>
+
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.2/api/">https://nodejs.org/docs/v0.7.2/api/</a></p>
diff --git a/locale/uk/blog/release/v0.7.3.md b/locale/uk/blog/release/v0.7.3.md
new file mode 100755
index 0000000000000..8fa4a560db51b
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.3.md
@@ -0,0 +1,42 @@
+---
+version: 0.7.3
+title: Node v0.7.3 (unstable)
+author: Isaac Schlueter
+date: 2012-02-08T01:08:27.000Z
+status: publish
+category: release
+slug: node-v0-7-3
+layout: blog-post.hbs
+---
+
+<p>2012.02.07, Version 0.7.3 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.2</p>
+</li>
+<li><p>Revert support for isolates. (Ben Noordhuis)</p>
+</li>
+<li><p>cluster: Cleanup docs, event handling, and process.disconnect (Andreas Madsen)</p>
+</li>
+<li><p>gyp_addon: link with node.lib on Windows (Nathan Rajlich)</p>
+</li>
+<li><p>http: fix case where http-parser is freed twice (koichik)</p>
+</li>
+<li><p>Windows: disable RTTI and exceptions (Bert Belder)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz">https://nodejs.org/dist/v0.7.3/node-v0.7.3.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.3/node-v0.7.3.msi">https://nodejs.org/dist/v0.7.3/node-v0.7.3.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg">https://nodejs.org/dist/v0.7.3/node-v0.7.3.pkg</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.3/">https://nodejs.org/docs/v0.7.3/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.3/api/">https://nodejs.org/docs/v0.7.3/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.4.md b/locale/uk/blog/release/v0.7.4.md
new file mode 100755
index 0000000000000..2115dab31d7e8
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.4.md
@@ -0,0 +1,53 @@
+---
+version: 0.7.4
+title: Node v0.7.4 (unstable)
+author: Isaac Schlueter
+date: 2012-02-15T19:38:35.000Z
+status: publish
+category: release
+slug: version-0-7-4-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.02.14, Version 0.7.4 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.5</p>
+</li>
+<li><p>Upgrade npm to 1.1.1</p>
+</li>
+<li><p>build: Detect host_arch better (Karl Skomski)</p>
+</li>
+<li><p>debugger: export <code>debug_port</code> to <code>process</code> (Fedor Indutny)</p>
+</li>
+<li><p>api docs: CSS bug fixes (isaacs)</p>
+</li>
+<li><p>build: use -fPIC for native addons on UNIX (Nathan Rajlich)</p>
+</li>
+<li><p>Re-add top-level v8::Locker (Marcel Laverdet)</p>
+</li>
+<li><p>Move images out of the dist tarballs (isaacs)</p>
+</li>
+<li><p>libuv: Remove uv_export and uv_import (Ben Noordhuis)</p>
+</li>
+<li><p>build: Support x64 build on Windows (Igor Zinkovsky)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz">https://nodejs.org/dist/v0.7.4/node-v0.7.4.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.4/node-v0.7.4.msi">https://nodejs.org/dist/v0.7.4/node-v0.7.4.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg">https://nodejs.org/dist/v0.7.4/node-v0.7.4.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.4/">https://nodejs.org/dist/v0.7.4/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.4/">https://nodejs.org/docs/v0.7.4/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.4/api/">https://nodejs.org/docs/v0.7.4/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.5.md b/locale/uk/blog/release/v0.7.5.md
new file mode 100755
index 0000000000000..d6eaa83be47e5
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.5.md
@@ -0,0 +1,65 @@
+---
+version: 0.7.5
+title: Version 0.7.5 (unstable)
+author: Isaac Schlueter
+date: 2012-02-23T22:45:21.000Z
+status: publish
+category: release
+slug: version-0-7-5-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.02.23, Version 0.7.5 (unstable)
+
+</p>
+<ul>
+<li><p>startup speed improvements (Maciej Małecki)</p>
+</li>
+<li><p>crypto: add function getDiffieHellman() (Tomasz Buchert)</p>
+</li>
+<li><p>buffer: support decoding of URL-safe base64 (Ben Noordhuis)</p>
+</li>
+<li><p>Make QueryString.parse() even faster (Brian White)</p>
+</li>
+<li><p>url: decode url entities in auth section (Ben Noordhuis)</p>
+</li>
+<li><p>http: support PURGE request method (Ben Noordhuis)</p>
+</li>
+<li><p>http: Generate Date headers on responses (Mark Nottingham)</p>
+</li>
+<li><p>Fix #2762: Add callback to close function. (Mikeal Rogers)</p>
+</li>
+<li><p>dgram: fix out-of-bound memory read (Ben Noordhuis)</p>
+</li>
+<li><p>repl: add automatic loading of built-in libs (Brandon Benvie)</p>
+</li>
+<li><p>repl: remove double calls where possible (Fedor Indutny)</p>
+</li>
+<li><p>Readline improvements. Related: #2737 #2756 (Colton Baker)</p>
+</li>
+<li><p>build: disable -fomit-frame-pointer on solaris (Dave Pacheco)</p>
+</li>
+<li><p>build: arch detection improvements (Nathan Rajlich)</p>
+</li>
+<li><p>build: Make a fat binary for the OS X <code>make pkg</code>. (Nathan Rajlich)</p>
+</li>
+<li><p>jslint src/ and lib/ on &#39;make test&#39; (isaacs)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz">https://nodejs.org/dist/v0.7.5/node-v0.7.5.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.5/node-v0.7.5.msi">https://nodejs.org/dist/v0.7.5/node-v0.7.5.msi</a>
+
+</p>
+<p>Macintosh Installer: <a href="https://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg">https://nodejs.org/dist/v0.7.5/node-v0.7.5.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.5/">https://nodejs.org/dist/v0.7.5/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.5/">https://nodejs.org/docs/v0.7.5/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.5/api/">https://nodejs.org/docs/v0.7.5/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.6.md b/locale/uk/blog/release/v0.7.6.md
new file mode 100755
index 0000000000000..2f93914f1d847
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.6.md
@@ -0,0 +1,75 @@
+---
+version: 0.7.6
+title: Version 0.7.6 (unstable)
+author: Isaac Schlueter
+date: 2012-03-13T21:12:30.000Z
+status: publish
+category: release
+slug: version-0-7-6-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.03.13, Version 0.7.6 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade v8 to 3.9.17</p>
+</li>
+<li><p>Upgrade npm to 1.1.8</p>
+<p>
+- Add support for os/cpu fields in package.json (Adam Blackburn)<br>
+- Automatically node-gyp packages containing a binding.gyp<br>
+- Fix failures unpacking in UNC shares<br>
+- Never create un-listable directories<br>
+- Handle cases where an optionalDependency fails to build<br>
+</p>
+</li>
+<li><p>events: newListener emit correct fn when using &#39;once&#39; (Roly Fentanes)</p>
+</li>
+<li><p>url: Ignore empty port component (Łukasz Walukiewicz)</p>
+</li>
+<li><p>module: replace &#39;children&#39; array (isaacs)</p>
+</li>
+<li><p>tls: parse multiple values of a key in ssl certificate (Sambasiva Suda)</p>
+</li>
+<li><p>cluster: support passing of named pipes (Ben Noordhuis)</p>
+</li>
+<li><p>Windows: include syscall in fs errors (Bert Belder)</p>
+</li>
+<li><p>http: #2888 Emit end event only once (Igor Zinkovsky)</p>
+</li>
+<li><p>readline: add multiline support (Rlidwka)</p>
+</li>
+<li><p>process: add <code>process.hrtime()</code> (Nathan Rajlich)</p>
+</li>
+<li><p>net, http, https: add localAddress option (Dmitry Nizovtsev)</p>
+</li>
+<li><p>addon improvements (Nathan Rajlich)</p>
+</li>
+<li><p>build improvements (Ben Noordhuis, Sadique Ali, T.C. Hollingsworth, Nathan Rajlich)</p>
+</li>
+<li><p>add support for &quot;SEARCH&quot; request methods (Nathan Rajlich)</p>
+</li>
+<li><p>expose the zlib and http_parser version in process.versions (Nathan Rajlich)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz">https://nodejs.org/dist/v0.7.6/node-v0.7.6.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.6/node-v0.7.6.msi">https://nodejs.org/dist/v0.7.6/node-v0.7.6.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.6/x64/">https://nodejs.org/dist/v0.7.6/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg">https://nodejs.org/dist/v0.7.6/node-v0.7.6.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.6/">https://nodejs.org/dist/v0.7.6/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.6/">https://nodejs.org/docs/v0.7.6/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.6/api/">https://nodejs.org/docs/v0.7.6/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.7.md b/locale/uk/blog/release/v0.7.7.md
new file mode 100755
index 0000000000000..807b57e2666aa
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.7.md
@@ -0,0 +1,74 @@
+---
+version: 0.7.7
+title: Version 0.7.7 (unstable)
+author: Isaac Schlueter
+date: 2012-03-30T18:56:19.000Z
+status: publish
+category: release
+slug: version-0-7-7-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.03.30, Version 0.7.7 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.24.7</p>
+</li>
+<li><p>Upgrade npm to 1.1.15</p>
+</li>
+<li><p>Handle Emoji characters properly (Erik Corry, Bert Belder)</p>
+</li>
+<li><p>readline: migrate ansi/vt100 logic from tty to readline (Nathan Rajlich)</p>
+</li>
+<li><p>readline: Fix multiline handling (Alex Kocharin)</p>
+</li>
+<li><p>add a -i/--interactive flag to force the REPL (Nathan Rajlich)</p>
+</li>
+<li><p>debugger: add breakOnException command (Fedor Indutny)</p>
+</li>
+<li><p>cluster: kill workers when master dies (Andreas Madsen)</p>
+</li>
+<li><p>cluster: add graceful disconnect support (Andreas Madsen)</p>
+</li>
+<li><p>child_process: Separate &#39;close&#39; event from &#39;exit&#39; (Charlie McConnell)</p>
+</li>
+<li><p>typed arrays: add Uint8ClampedArray (Mikael Bourges-Sevenier)</p>
+</li>
+<li><p>buffer: Fix byte alignment issues (Ben Noordhuis, Erik Lundin)</p>
+</li>
+<li><p>tls: fix CryptoStream.setKeepAlive() (Shigeki Ohtsu)</p>
+</li>
+<li><p>Expose http parse error codes (Felix Geisendörfer)</p>
+</li>
+<li><p>events: don&#39;t delete the listeners array (Ben Noordhuis, Nathan Rajlich)</p>
+</li>
+<li><p>process: add process.config to view node&#39;s ./configure settings (Nathan Rajlich)</p>
+</li>
+<li><p>process: process.execArgv to see node&#39;s arguments (Micheil Smith)</p>
+</li>
+<li><p>process: fix process.title setter (Ben Noordhuis)</p>
+</li>
+<li><p>timers: handle negative or non-numeric timeout values (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz">https://nodejs.org/dist/v0.7.7/node-v0.7.7.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.7/node-v0.7.7.msi">https://nodejs.org/dist/v0.7.7/node-v0.7.7.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.7/x64/">https://nodejs.org/dist/v0.7.7/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg">https://nodejs.org/dist/v0.7.7/node-v0.7.7.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.7/">https://nodejs.org/dist/v0.7.7/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.7/">https://nodejs.org/docs/v0.7.7/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.7/api/">https://nodejs.org/docs/v0.7.7/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.8.md b/locale/uk/blog/release/v0.7.8.md
new file mode 100755
index 0000000000000..b7ab34472ffc9
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.8.md
@@ -0,0 +1,74 @@
+---
+version: 0.7.8
+title: Version 0.7.8 (unstable)
+author: Isaac Schlueter
+date: 2012-04-18T17:39:02.000Z
+status: publish
+category: release
+slug: version-0-7-8-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.04.18, Version 0.7.8, (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.9.24.9</p>
+</li>
+<li><p>Upgrade OpenSSL to 1.0.0f</p>
+</li>
+<li><p>Upgrade npm to 1.1.18</p>
+</li>
+<li><p>Show licenses in Binary installers</p>
+</li>
+<li><p>Domains (isaacs)</p>
+</li>
+<li><p>readline: rename &quot;end&quot; to &quot;close&quot; (Nathan Rajlich)</p>
+</li>
+<li><p>tcp: make getsockname() return address family as string (Shigeki Ohtsu)</p>
+</li>
+<li><p>http, https: fix .setTimeout() (ssuda)</p>
+</li>
+<li><p>os: add cross platform EOL character (Mustansir Golawala)</p>
+</li>
+<li><p>typed arrays: unexport SizeOfArrayElementForType() (Aaron Jacobs)</p>
+</li>
+<li><p>net: honor &#39;enable&#39; flag in .setNoDelay() (Ben Noordhuis)</p>
+</li>
+<li><p>child_process: emit error when .kill fails (Andreas Madsen)</p>
+</li>
+<li><p>gyp: fix &#39;argument list too long&#39; build error (Ben Noordhuis)</p>
+</li>
+<li><p>fs.WriteStream: Handle modifications to fs.open (isaacs)</p>
+</li>
+<li><p>repl, readline: Handle newlines better (Nathan Rajlich, Nathan Friedly)</p>
+</li>
+<li><p>build: target OSX 10.5 when building on darwin (Nathan Rajlich)</p>
+</li>
+<li><p>Fix #3052 Handle errors properly in zlib (isaacs)</p>
+</li>
+<li><p>build: add support for DTrace and postmortem (Dave Pacheco)</p>
+</li>
+<li><p>core: add reusable Slab allocator (Ben Noordhuis)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz">https://nodejs.org/dist/v0.7.8/node-v0.7.8.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.8/node-v0.7.8.msi">https://nodejs.org/dist/v0.7.8/node-v0.7.8.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.8/x64/">https://nodejs.org/dist/v0.7.8/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg">https://nodejs.org/dist/v0.7.8/node-v0.7.8.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.8/">https://nodejs.org/dist/v0.7.8/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.8/">https://nodejs.org/docs/v0.7.8/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.8/api/">https://nodejs.org/docs/v0.7.8/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.7.9.md b/locale/uk/blog/release/v0.7.9.md
new file mode 100755
index 0000000000000..a518a113ab656
--- /dev/null
+++ b/locale/uk/blog/release/v0.7.9.md
@@ -0,0 +1,76 @@
+---
+version: 0.7.9
+title: Node Version 0.7.9 (unstable)
+author: Isaac Schlueter
+date: 2012-05-29T17:11:45.000Z
+status: publish
+category: release
+slug: node-version-0-7-9-unstable
+layout: blog-post.hbs
+---
+
+<p>2012.05.28, Version 0.7.9 (unstable)
+
+</p>
+<ul>
+<li><p>Upgrade V8 to 3.11.1</p>
+</li>
+<li><p>Upgrade npm to 1.1.23</p>
+</li>
+<li><p>uv: rework reference counting scheme (Ben Noordhuis)</p>
+</li>
+<li><p>uv: add interface for joining external event loops (Bert Belder)</p>
+</li>
+<li><p>repl, readline: Handle Ctrl+Z and SIGCONT better (Nathan Rajlich)</p>
+</li>
+<li><p>fs: 64bit offsets for fs calls (Igor Zinkovsky)</p>
+</li>
+<li><p>fs: add sync open flags &#39;rs&#39; and &#39;rs+&#39; (Kevin Bowman)</p>
+</li>
+<li><p>windows: enable creating directory junctions with fs.symlink (Igor Zinkovsky, Bert Belder)</p>
+</li>
+<li><p>windows: fix fs.lstat to properly detect symlinks. (Igor Zinkovsky)</p>
+</li>
+<li><p>Fix #3270 Escape url.parse delims (isaacs)</p>
+</li>
+<li><p>http: make http.get() accept a URL (Adam Malcontenti-Wilson)</p>
+</li>
+<li><p>Cleanup vm module memory leakage (Marcel Laverdet)</p>
+</li>
+<li><p>Optimize writing strings with Socket.write (Bert Belder)</p>
+</li>
+<li><p>add support for CESU-8 and UTF-16LE encodings (koichik)</p>
+</li>
+<li><p>path: add path.sep to get the path separator. (Yi, EungJun)</p>
+</li>
+<li><p>net, http: add backlog parameter to .listen() (Erik Dubbelboer)</p>
+</li>
+<li><p>debugger: support mirroring Date objects (Fedor Indutny)</p>
+</li>
+<li><p>addon: add AtExit() function (Ben Noordhuis)</p>
+</li>
+<li><p>net: signal localAddress bind failure in connect (Brian Schroeder)</p>
+</li>
+<li><p>util: handle non-string return value in .inspect() (Alex Kocharin)</p>
+</li>
+</ul>
+<p>Source Code: <a href="https://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz">https://nodejs.org/dist/v0.7.9/node-v0.7.9.tar.gz</a>
+
+</p>
+<p>Windows Installer: <a href="https://nodejs.org/dist/v0.7.9/node-v0.7.9.msi">https://nodejs.org/dist/v0.7.9/node-v0.7.9.msi</a>
+
+</p>
+<p>Windows x64 Files: <a href="https://nodejs.org/dist/v0.7.9/x64/">https://nodejs.org/dist/v0.7.9/x64/</a>
+
+</p>
+<p>Macintosh Installer (Universal): <a href="https://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg">https://nodejs.org/dist/v0.7.9/node-v0.7.9.pkg</a>
+
+</p>
+<p>Other release files: <a href="https://nodejs.org/dist/v0.7.9/">https://nodejs.org/dist/v0.7.9/</a>
+
+</p>
+<p>Website: <a href="https://nodejs.org/docs/v0.7.9/">https://nodejs.org/docs/v0.7.9/</a>
+
+</p>
+<p>Documentation: <a href="https://nodejs.org/docs/v0.7.9/api/">https://nodejs.org/docs/v0.7.9/api/</a>
+</p>
diff --git a/locale/uk/blog/release/v0.8.0.md b/locale/uk/blog/release/v0.8.0.md
new file mode 100755
index 0000000000000..d19dc51c7aad7
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.0.md
@@ -0,0 +1,387 @@
+---
+title: Node v0.8.0
+date: 2012-06-25T16:00:00.000Z
+version: 0.8.0
+category: release
+author: Isaac Z. Schlueter
+slug: node-v0-8-0
+status: publish
+layout: blog-post.hbs
+---
+
+I am thrilled to announce the arrival of a new stable version of
+Node.js.
+
+Compared with the v0.6 releases of Node, this release brings significant
+improvements in many key performance metrics, as well as
+cleanup in several core APIs, and the addition of new debugging
+features.
+
+## tl;dr
+
+With version 0.8.0:
+
+1. Node got a lot faster.
+2. Node got more stable.
+3. You can do stuff with file descriptors again.
+4. The [cluster module](https://nodejs.org/api/cluster.html) is much more
+   awesome.
+5. The [domain module](https://nodejs.org/api/domain.html) was added.
+6. The repl is better.
+7. The build system changed from waf to gyp.
+8. [Some other stuff changed,
+   too.](https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8)
+9. Scroll to the bottom for the links to install it.
+
+## Performance
+
+This version brings a few key enhancements in V8 and libuv that result
+in significantly improved throughput.
+
+All of these benchmarks were run on my OS X laptop, but the results are
+typical of what we're seeing on SmartOS, Linux, and Windows.
+
+```
+# io.js
+
+# 0.6.19, writes
+Wrote 1024 byte buffers: 19.428793471925395 mB/s
+Wrote 4096 byte buffers: 59.737156511350065 mB/s
+Wrote 16384 byte buffers: 83.97010664203543 mB/s
+Wrote 65536 byte buffers: 97.4184120798831 mB/s
+
+# 0.8.0, writes
+Wrote 1024 byte buffers: 61.236987140232706 mB/s +215.19%
+Wrote 4096 byte buffers: 109.05125408942203 mB/s +82.55%
+Wrote 16384 byte buffers: 182.18254691200585 mB/s +116.96%
+Wrote 65536 byte buffers: 181.91740949608877 mB/s +86.74%
+
+# v0.6.19, reads
+Read 1024 byte buffers: 29.96883241428914 mB/s
+Read 4096 byte buffers: 62.34413965087282 mB/s
+Read 16384 byte buffers: 165.7550140891762 mB/s
+Read 65536 byte buffers: 266.73779674579885 mB/s
+
+# v0.8.0, reads
+Read 1024 byte buffers: 57.63688760806916 mB/s +92.32%
+Read 4096 byte buffers: 136.7801942278758 mB/s +119.40%
+Read 16384 byte buffers: 244.8579823702253 mB/s +47.72%
+Read 65536 byte buffers: 302.2974607013301 mB/s +13.33%
+```
+
+The difference is not small.  If you are writing network programs with
+node, and pushing a lot of traffic, you will notice this improvement.
+
+The speed of reading files got quite a bit faster as well:
+
+```
+# v0.6.19
+read the file 110948 times (higher is better)
+90141.32 ns per read (lower is better)
+11093.69 reads per sec (higher is better)
+
+# v0.8.0
+read the file 158193 times (higher is better) +42.58%
+63217.16 ns per read (lower is better) -29.87%
+15818.48 reads per sec (higher is better) +42.59%
+```
+
+And of course, the ubiquitous 'hello, world' http server benchmark got
+significantly faster, especially for large message sizes:
+
+```
+$ TYPE=bytes LENGTH=123 bash benchmark/http.sh  2>&1 | grep Req
+# 0.6.19
+Requests per second:    3317.24 [#/sec] (mean)
+# 0.8.0
+Requests per second:    3795.34 [#/sec] (mean) +14.41%
+
+
+$ TYPE=bytes LENGTH=1024 bash benchmark/http.sh  2>&1 | grep Req
+# v0.6.19
+Requests per second:    3258.42 [#/sec] (mean)
+# 0.8.0
+Requests per second:    3585.62 [#/sec] (mean) +10.04%
+
+
+$ TYPE=bytes LENGTH=123456 bash benchmark/http.sh  2>&1 | grep Req
+# v0.6.19
+Requests per second:    218.51 [#/sec] (mean)
+# 0.8.0
+Requests per second:    749.17 [#/sec] (mean) +242.85%
+```
+
+The difference with Unicode responses is even more pronounced:
+
+```
+$ TYPE=unicode LENGTH=1024 bash benchmark/http.sh  2>&1 | grep Req
+# v0.6.19
+Requests per second:    3228.23 [#/sec] (mean)
+# v0.8.0
+Requests per second:    3317.60 [#/sec] (mean) +2.77%
+
+$ TYPE=unicode LENGTH=12345 bash benchmark/http.sh  2>&1 | grep Req
+# v0.6.19
+Requests per second:    1703.96 [#/sec] (mean)
+# v0.8.0
+Requests per second:    2431.61 [#/sec] (mean) +42.70%
+
+$ TYPE=unicode LENGTH=55555 bash benchmark/http.sh  2>&1 | grep Req
+#v0.6.19
+Requests per second:    161.65 [#/sec] (mean)
+#v0.8.0
+Requests per second:    980.38 [#/sec] (mean) +506.48%
+
+$ TYPE=unicode LENGTH=99999 bash benchmark/http.sh  2>&1 | grep Req
+# v0.6.19
+^C  # lost patience after a few hours
+# v0.8.0
+Requests per second:    252.69 [#/sec] (mean)
+```
+
+The more bytes you're pushing, and the more work you're doing, the more
+win you'll see with node 0.8 over 0.6.
+
+The vast majority of the performance boost is due to improvements in V8.
+They've been very responsive to the needs of the Node.js project.  A lot
+of Node's success is due to being built on such a stellar VM.
+
+
+## Build System
+
+Since its inception Node has used the WAF build system which is a Python
+based system similar to SCons.  The Chrome project recently changed to
+the GYP meta-build system from SCons. GYP generates Makefiles, Visual
+Studio project files, or XCode files depending on the target. V8, being
+part of the Chrome project, now defines its build in GYP.  By using GYP,
+Node is able to:
+
+- integrate with the optimal build system on all platforms,
+- easily able to integrate V8's build process into its own, and
+- define its compilation declaratively for better manageability
+
+GYP was used already in Node v0.6 to build on Windows, but now it
+defines the build on all platforms. Node is still in the process of
+migrating external addon modules to GYP, and node-gyp is included with
+npm.  In future releases, node-waf will be officially deprecated.  If
+you are currently using a wscript in your addon, please migrate to gyp
+as soon as possible.
+
+
+## Stabler
+
+The transition from libev and libeio to libuv in 0.6 was somewhat
+destabilizing for many node internals.  The gambit paid off: libuv is
+the obvious choice in cross-platform asynchronous IO libraries, and
+Node.js is impressively performant on both Windows and Unix.  But it
+made the transition from 0.4 to 0.6 was very rocky for a lot of users.
+Libuv wasn't as mature as node, and it showed in those early releases.
+
+At this point, with very few exceptions, if your v0.6 program doesn't
+run on v0.8, it should be easy and obvious to make whatever changes are
+necessary.  Libuv has come a very long way, and Node 0.8 is a simpler
+and more efficient machine as a result.
+
+See the [migration
+wiki](https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8)
+for details on the specific APIs that changed.
+
+## The Return of File Descriptors
+
+In Node 0.4, there was a `listenFD` method that servers could use to
+listen on a specific file descriptor that was already bound to a socket
+or port. In 0.6, that functionality went away, largely because it was
+very Unix-specific, and couldn't be easily made to work with the new
+cross-platform libuv base.
+
+Since the most common use case for listenFD was as a method for having
+servers in multiple node processes share the same underlying handle, the
+`cluster` module was added in its place.  However, this still left a lot
+of use cases unaddressed, and was a reason why some people could not use
+node 0.6 for their programs.
+
+In 0.8, we've replaced this functionality, as `server.listen({ fd:
+number })`.
+
+The other feature in node 0.4 that got dropped in 0.6 was the ability to
+pass arbitrary file descriptors as a child process's stdio, using the
+`customFds` array.  In Node 0.6, `customFds` could be used to inherit
+the parent's stdio handles, but not to pass arbitrary handles or file
+descriptors to the child's stdio.  Also, there was never a way to pass
+more than the standard `in, out, err` trio, so programs that expected
+FD 4 to be opened in some specific way were out of luck.
+
+In 0.8, we've added the `stdio` array on the `child_process.spawn`
+options.  Pass as many file descriptors, handles, etc. as you like, and
+the child process will see them as already-opened FDs.
+
+## More Powerful Cluster
+
+The cluster module in 0.8 is so much improved over 0.6, it's basically a
+complete rewrite.  The API is mostly backwards compatible, but not
+entirely.  (See the [migration
+wiki](https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8)
+for details.)
+
+Barring these very minor API changes, if you were using cluster in 0.6,
+then your program will still work, but it'll be faster and more
+well-behaved now.  And if you aren't taking advantage of the new
+features in 0.8's cluster, you're really missing out.
+
+There's too much even to do it justice here.  Go read [the API
+docs](https://nodejs.org/api/cluster.html).
+
+## Domains
+
+The original idea for Domains was a way to join multiple different IO
+actions, so that you can have some context when an error occurs.
+
+Since Ryan discussed the feature with node users at NodeConf Summer Camp
+last year, the domains feature has gone through many revisions.  The
+problem is fairly well understood, but most attempts to solve it
+resulted in serious performance regressions, or uncovered difficult edge
+cases.
+
+What we ended up with in 0.8 is a very stripped-down version of this
+idea.  It's entirely opt-in, with minimal performance impact when it's
+used (and none when it isn't).  There are a lot of examples in [the API
+documentation](https://nodejs.org/api/domain.html), so check them out,
+and start handling your crashes smarter.
+
+The domain module is still experimental.  We are looking forward to your
+feedback, so please use it and let us know what you think.
+
+## Repl, Readline, TTY
+
+The Repl, Readline, and TTY modules have all had a major facelift.  The
+interfaces between these three modules are cleaned up and refactored,
+removing a lot of common pain points and making it easier to use for
+debugging your programs.
+
+It may seem minor at times, but a good repl dramatically increases the
+quality of the overall experience.  My personal favorites are:
+
+1. Typing `fs` or `net` or `path` will automatically load the module.
+2. Typing `npm install ...` will give you a helpful message.
+3. It doesn't do that stupid thing where long lines wrap and then the
+   backspace makes it get all confused and crazy.  Instead of that, it
+   does the right thing.
+
+## Looking Forward
+
+Like other even-numbered version families before it, v0.8 will maintain
+API and ABI stability throughout its lifetime.
+
+The v0.6 release family will continue to see releases for critical
+bugfixes and security issues through the end of 2012.  However, it will
+not be the main focus of the core team's attention.
+
+The v0.9 releases will start in the next couple weeks.  The main focus
+of v0.9 will be:
+
+* The HTTP implementation - It has seen a lot of real-world use now, but
+  the http module is in dire need of a cleanup and refactor.  Special
+  attention will be paid to making the interfaces more consistent,
+  improve performance, and increase correctness in more edge cases.
+* The Streams API - The concept of the Stream API is very core to node.
+  However, it is also (like HTTP) a feature that grew up organically,
+  and is now in need of a cleanup.  It is currently too hard to get
+  right, especially regarding error handling.
+* Libuv Streams - The handle interfaces in libuv are going to be
+  refactored for added consistency throughout the codebase and across
+  platforms.
+
+Looking past that, there are a few areas where Node.js still has room
+for improvement in terms of internal consistency, idiomatic JavaScript
+usage, and performance.  None of these are fully-fleshed out ideas yet,
+but these are some of the items on our radar:
+
+* We ought to move to TypedArrays in favor of Buffers.  Buffers will
+  continue to work, but since TypedArray is a JavaScript native, it
+  makes sense to move towards that as the preferred API.
+* SSL performance leaves much to be desired at the moment.  Node's
+  interface with OpenSSL is somewhat naive and leaves a lot of potential
+  optimization on the table.
+* The VM module needs massive improvement.  It lacks features required
+  to emulate a web browser JavaScript context, which means that it is
+  inadequate.
+* The Crypto module still uses some very dated APIs.  In 0.8, it can
+  accept Buffers for many things (finally!) but it still does not
+  present a Node-like streaming interface.
+
+At this point, the scope of Node's feature set is pretty much locked
+down.  We may move things around internally for these cleanup tasks, but
+as you can see, there are no major new features planned.  We've drawn
+our boundaries, and now it's time to continue focusing on improving
+stability and performance of the core, so that more innovation can
+happen in **your** programs.
+
+And now, for those of you who may be wondering what was added since
+v0.7.12, your regularly scheduled release announcement:
+
+## 2012.06.25, Version 0.8.0 (stable)
+
+* V8: upgrade to v3.11.10.10
+
+* npm: Upgrade to 1.1.32
+
+* Deprecate iowatcher (Ben Noordhuis)
+
+* windows: update icon (Bert Belder)
+
+* http: Hush 'MUST NOT have a body' warnings to debug() (isaacs)
+
+* Move blog.nodejs.org content into repository (isaacs)
+
+* Fix #3503: stdin: resume() on pipe(dest) (isaacs)
+
+* crypto: fix error reporting in SetKey() (Fedor Indutny)
+
+* Add --no-deprecation and --trace-deprecation command-line flags (isaacs)
+
+* fs: fix fs.watchFile() (Ben Noordhuis)
+
+* fs: Fix fs.readfile() on pipes (isaacs)
+
+* Rename GYP variable node_use_system_openssl to be consistent (Ryan Dahl)
+
+
+Source Code: https://nodejs.org/dist/v0.8.0/node-v0.8.0.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.0/node-v0.8.0.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.0/node-v0.8.0-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.0/x64/node-v0.8.0-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.0/x64/
+
+Other release files: https://nodejs.org/dist/v0.8.0/
+
+Website: https://nodejs.org/docs/v0.8.0/
+
+Documentation: https://nodejs.org/docs/v0.8.0/api/
+
+Shasums:
+
+```
+b92208b291ad420025c65661a7df51fc618e21ca  license.rtf
+0786bcda79bd651b9981682527a1bbabe0250700  node-v0.8.0-x86.msi
+8f160a742a01fdfc1b1423b3fc742d184f1ab70c  node-v0.8.0-x86.wixpdb
+6035d6d59304add21e462cd7eb89491570b4970d  node-v0.8.0.pkg
+5171fb46fbfee5ac7129c4b17207a3f35a1f57e8  node-v0.8.0.tar.gz
+742100a4ee4cd4d190031a30d9b22b2b69b6872e  node.exe
+52d20d285e9aec53043af0843f5ecc4153210693  node.exp
+6d67a64274d844548cc6099c76181a50feafc233  node.lib
+aa2af08d5ab869e6c8b67f01ed67129c1cad8bce  node.pdb
+b92208b291ad420025c65661a7df51fc618e21ca  x64/license.rtf
+c4d4164d4f78ea68e0e2a85b96f9b355f3b1df8b  x64/node-v0.8.0-x64.msi
+df8bb178ee4cb9562d93fe80bbe59b2acf1b9e6b  x64/node-v0.8.0-x64.wixpdb
+fc07b475d943f7681e1904d6d7d666b41874a6fa  x64/node.exe
+895002806dfb6d5bb141ef0f43cad3b540a4ff6c  x64/node.exp
+686c60d5ae5dad7fcffcdc88049c63b2cd23cffc  x64/node.lib
+75549cffab0c11107348a66ab0d94d4897bd6a27  x64/node.pdb
+```
+
+<ins>Edited by Tim Oxley to provide percentage differences in the
+benchmarks.</ins>
diff --git a/locale/uk/blog/release/v0.8.1.md b/locale/uk/blog/release/v0.8.1.md
new file mode 100755
index 0000000000000..cdb337a1c10e4
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.1.md
@@ -0,0 +1,80 @@
+---
+version: 0.8.1
+title: Version 0.8.1 (stable)
+category: release
+slug: node-v0-8-1-stable
+date: 2012-06-28T22:00:00.000Z
+layout: blog-post.hbs
+---
+
+2012.06.29, Version 0.8.1 (stable)
+
+* V8: upgrade to v3.11.10.12
+
+* npm: upgrade to v1.1.33
+  - Support for parallel use of the cache folder
+  - Retry on registry timeouts or network failures (Trent Mick)
+  - Reduce 'engines' failures to a warning
+  - Use new zsh completion if available (Jeremy Cantrell)
+
+* Fix #3577 Un-break require('sys')
+
+* util: speed up formatting of large arrays/objects (Ben Noordhuis)
+
+* windows: make fs.realpath(Sync) work with UNC paths (Bert Belder)
+
+* build: fix --shared-v8 option (Ben Noordhuis)
+
+* doc: `detached` is a boolean (Andreas Madsen)
+
+* build: use proper python interpreter (Ben Noordhuis)
+
+* build: expand ~ in `./configure --prefix=~/a/b/c` (Ben Noordhuis)
+
+* build: handle CC env var with spaces (Gabriel de Perthuis)
+
+* build: fix V8 build when compiling with gcc 4.5 (Ben Noordhuis)
+
+* build: fix --shared-v8 option (Ben Noordhuis)
+
+* windows msi: Fix icon issue which caused huge file size (Bert Belder)
+
+* unix: assume that dlopen() may clobber dlerror() (Ben Noordhuis)
+
+* sunos: fix memory corruption bugs (Ben Noordhuis)
+
+* windows: better (f)utimes and (f)stat (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.1/node-v0.8.1.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.1/node-v0.8.1.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.1/node-v0.8.1-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.1/x64/node-v0.8.1-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.1/x64/
+
+Other release files: https://nodejs.org/dist/v0.8.1/
+
+Website: https://nodejs.org/docs/v0.8.1/
+
+Documentation: https://nodejs.org/docs/v0.8.1/api/
+
+Shasums:
+
+```
+64f10cb29aaaabda83300c81d61b56a436308126  node-v0.8.1-x86.msi
+75a1afca1221719ec4a9dd8ed35c0e0adbaaf153  node-v0.8.1.pkg
+892790553b8121ba8624d8293d0cb7d8b01094d7  node-v0.8.1.tar.gz
+85ce513182bd66c1aa3e144438022dbe4caa56a7  node.exe
+592426620080c904c55ac83e151a85d42275656e  node.exp
+88a9177dba73597ffc08f30b886542c4d76378e2  node.lib
+6b06ffd2b6e28e34189663af7b3efda5d12dd1bf  node.pdb
+c6d99aa58167c5489e56e2f99da99731fb4f282e  x64/node-v0.8.1-x64.msi
+4266ba03b2b4516d10cbc5d16eb15d5df13ebb47  x64/node.exe
+7a6d0b28be88c6941aae74426199e9fb82ddfaa5  x64/node.exp
+ac21ec0f61baaf584f89a92db403cd9d38ff4850  x64/node.lib
+9e514c4c6c427dd4ae16edf1d2ad7a46ef9893c0  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.10.md b/locale/uk/blog/release/v0.8.10.md
new file mode 100755
index 0000000000000..bc4af62d5d03c
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.10.md
@@ -0,0 +1,96 @@
+---
+title: Node v0.8.10 (Stable)
+date: 2012-09-25T22:36:47.000Z
+slug: node-v0-8-10-stable
+category: release
+version: 0.8.10
+layout: blog-post.hbs
+---
+
+2012.09.25, Version 0.8.10 (Stable)
+
+* npm: Upgrade to 1.1.62
+
+* repl: make invalid RegExps throw in the REPL (Nathan Rajlich)
+
+* v8: loosen artificial mmap constraint (Bryan Cantrill)
+
+* process: fix setuid() and setgid() error reporting (Ben Noordhuis)
+
+* domain: Properly exit() on domain disposal (isaacs)
+
+* fs: fix watchFile() missing deletion events (Ben Noordhuis)
+
+* fs: fix assert in fs.watch() (Ben Noordhuis)
+
+* fs: don't segfault on deeply recursive stat() (Ben Noordhuis)
+
+* http: Remove timeout handler when data arrives (Frédéric Germain)
+
+* http: make the client "res" object gets the same domain as "req" (Nathan Rajlich)
+
+* windows: don't blow up when an invalid FD is used (Bert Belder)
+
+* unix: map EDQUOT to UV_ENOSPC (Charlie McConnell)
+
+* linux: improve /proc/cpuinfo parser (Ben Noordhuis)
+
+* win/tty: reset background brightness when color is set to default (Bert Belder)
+
+* unix: put child process stdio fds in blocking mode (Ben Noordhuis)
+
+* unix: fix EMFILE busy loop (Ben Noordhuis)
+
+* sunos: don't set TCP_KEEPALIVE (Ben Noordhuis)
+
+* tls: Use slab allocator for memory management (Fedor Indutny)
+
+* openssl: Use optimized assembly code for x86 and x64 (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.10/node-v0.8.10.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.10/node-v0.8.10.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.10/node-v0.8.10-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.10/x64/node-v0.8.10-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.10/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.10/node-v0.8.10-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.10/node-v0.8.10-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.10/node-v0.8.10-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.10/node-v0.8.10-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.10/
+
+Website: https://nodejs.org/docs/v0.8.10/
+
+Documentation: https://nodejs.org/docs/v0.8.10/api/
+
+Shasums:
+
+```
+ae327ce5cc9f46e7d1bdd04f06ea299e44f9a0fc  node-v0.8.10-darwin-x64.tar.gz
+812405695e3522bfd998d67b6de2daff55ff0a7b  node-v0.8.10-darwin-x86.tar.gz
+8ef4e489817a79aaea75cffd09cc4b072c38fe2e  node-v0.8.10-linux-x64.tar.gz
+76f289b12ba41730c43b59d286de5cee571c9064  node-v0.8.10-linux-x86.tar.gz
+61e40e8a5e911b26889ad33856029d783388778a  node-v0.8.10-sunos-x64.tar.gz
+2fd06dc2d145fdba6b2800186ffcaebb0fe3b109  node-v0.8.10-sunos-x86.tar.gz
+3e49e1c958815d0144cafe5e43c2fa83e775dd1c  node-v0.8.10-x86.msi
+9605340dca27725110eebcb15fdf61599622e308  node-v0.8.10.pkg
+c596cce77726724441cf7fc98f42df3a5335ab8e  node-v0.8.10.tar.gz
+f6d172e3452e2bf429dc75836a385eff22407c83  node.exe
+ccb8c0e0fa052d8da48ea421cc7a220bb89835f9  node.exp
+7ea077e6ca1216d5e8f42e445f75f0542f7d85c4  node.lib
+d86ad55c37ac1a0975731ab444fc58c93a7bca47  node.pdb
+90fc70b09f92f788fc68a116f589a86ca3309fdb  x64/node-v0.8.10-x64.msi
+4b62cedf4bbbff1ffb8df6d52c9a57255f383ad3  x64/node.exe
+6b4b813c3b065154ce437b7f36a15beceeb76af0  x64/node.exp
+9e7dd3ddca3ba37483ac2125c39a52e72035e1d0  x64/node.lib
+28de8dd05af5e390f5bd63508bd27b7c683177de  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.11.md b/locale/uk/blog/release/v0.8.11.md
new file mode 100755
index 0000000000000..039f4667610fc
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.11.md
@@ -0,0 +1,66 @@
+---
+category: release
+version: v0.8.11
+date: 2012-09-27T17:13:12.000Z
+slug: node-v0.8.11
+title: Node v0.8.11 (Stable)
+layout: blog-post.hbs
+---
+
+This is just a minor bugfix release to correct the regression in
+[v0.8.10](http://blog.nodejs.org/2012/09/25/node-v0-8-10-stable/).
+
+If you haven't yet upgraded to v0.8.10, then please use this release
+instead.
+
+2012.09.27, Version 0.8.11 (Stable)
+
+* fs: Fix stat() size reporting for large files (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.11/node-v0.8.11.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.11/node-v0.8.11.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.11/node-v0.8.11-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.11/x64/node-v0.8.11-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.11/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.11/node-v0.8.11-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.11/node-v0.8.11-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.11/node-v0.8.11-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.11/node-v0.8.11-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.11/
+
+Website: https://nodejs.org/docs/v0.8.11/
+
+Documentation: https://nodejs.org/docs/v0.8.11/api/
+
+Shasums:
+
+```
+3677fdcce837233d4d3d5cdfb8685123ef38fcc2  node-v0.8.11-darwin-x64.tar.gz
+24213b076d5c95a1ee7598c540a454a4d6b1d899  node-v0.8.11-darwin-x86.tar.gz
+380e533b7953767ec3a43109d37615238296d15c  node-v0.8.11-linux-x64.tar.gz
+0d9c1bd3a97aa7a5adf6274271f4a8e7745ff704  node-v0.8.11-linux-x86.tar.gz
+d4dbb70ca6a3e06c763b7be5fffaae1c7630bd69  node-v0.8.11-sunos-x64.tar.gz
+d8fcd334118576a744a57eb1f3565c242810f4f1  node-v0.8.11-sunos-x86.tar.gz
+80a14ed82672d3c5c14f60f41ba3f03d65dde13f  node-v0.8.11-x86.msi
+8a096cdaf7c3e76ee82373214b51a7c7f306de47  node-v0.8.11.pkg
+e9dd36cbbe03c632ee7e9c52e06122fa022981c8  node-v0.8.11.tar.gz
+5bf31a7e2518d06df1dd05f135617db8c32d8a2e  node.exe
+79a21c6de2d8e38937865c4cd36306b92e37c832  node.exp
+31862938d8cd95efe0e6121764c7797a1487fe51  node.lib
+2bbcad390e7fc122be74cb1a116f5420057e9600  node.pdb
+30798c0b6d69b13ba94c3501b222f88212f77149  x64/node-v0.8.11-x64.msi
+1e69c413252121ab475420795023f9799823d3f7  x64/node.exe
+470683d233c9d0295f45f5635203560b242d6f7c  x64/node.exp
+2134bf022d719da1e455585792af8782ffe81d33  x64/node.lib
+1c2a22d0ce3c902f5dae7fde15d32bd9393a2153  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.12.md b/locale/uk/blog/release/v0.8.12.md
new file mode 100755
index 0000000000000..2347bcce7c81d
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.12.md
@@ -0,0 +1,76 @@
+---
+category: release
+version: v0.8.12
+date: 2012-10-12T15:52:06.000Z
+slug: node-v0.8.12
+title: Node v0.8.12 (Stable)
+layout: blog-post.hbs
+---
+
+2012.10.12, Version 0.8.12 (Stable)
+
+* npm: Upgrade to 1.1.63
+
+* crypto: Reduce stability index to 2-Unstable (isaacs)
+
+* windows: fix handle leak in uv_fs_utime (Bert Belder)
+
+* windows: fix application crashed popup in debug version (Bert Belder)
+
+* buffer: report proper retained size in profiler (Ben Noordhuis)
+
+* buffer: fix byteLength with UTF-16LE (koichik)
+
+* repl: make "end of input" JSON.parse() errors throw in the REPL (Nathan Rajlich)
+
+* repl: make invalid RegExp modifiers throw in the REPL (Nathan Rajlich)
+
+* http: handle multiple Proxy-Authenticate values (Willi Eggeling)
+
+
+Source Code: https://nodejs.org/dist/v0.8.12/node-v0.8.12.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.12/node-v0.8.12.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.12/node-v0.8.12-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.12/x64/node-v0.8.12-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.12/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.12/node-v0.8.12-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.12/node-v0.8.12-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.12/node-v0.8.12-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.12/node-v0.8.12-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.12/
+
+Website: https://nodejs.org/docs/v0.8.12/
+
+Documentation: https://nodejs.org/docs/v0.8.12/api/
+
+Shasums:
+
+```
+2d40157436b34e9e347c587de9945e7022eb9acc  node-v0.8.12-darwin-x64.tar.gz
+b6ba1d2e478881e0a5248cb319ce0913ca39a51b  node-v0.8.12-darwin-x86.tar.gz
+5353dfab2005992deee13e6e00a30509c8c86d4b  node-v0.8.12-linux-x64.tar.gz
+9e501b995469d554e3356b6f5f85b72abed83310  node-v0.8.12-linux-x86.tar.gz
+b3e8e655b3c6f0a2c641dcb0e22372edb6f45ffd  node-v0.8.12-sunos-x64.tar.gz
+82c46d12a52e09bda3ad4bd0cdb8ad18480e679a  node-v0.8.12-sunos-x86.tar.gz
+d70e7bc718699651281110cd9f3f13ae50ac36be  node-v0.8.12-x86.msi
+d24d17d34425eb86cc237b8e68fdd5d199cb0ad8  node-v0.8.12.pkg
+719397c7f65365b2ec6510863ac62bd291784910  node-v0.8.12.tar.gz
+ac7151c05730982eb37a7f390386219c4d05b57d  node.exe
+000771bbc1e26f8ac5d11183b6538f25214b64a6  node.exp
+b036c368ff65f96ca44ac0ccf8d742c41ce00a95  node.lib
+98edc84132157d44df7a4d08b6788843fe542961  node.pdb
+d1cccae53dcb54e08a8771ef0f9406e327ac4db3  x64/node-v0.8.12-x64.msi
+0aa3088bd6a55864d25e84091b3a3b796ce20ce9  x64/node.exe
+1d6dc06515cead63a2e547aacc73cfb7ad8003a2  x64/node.exp
+7f55dd2367523c151e4d8492c596f076e0e5d151  x64/node.lib
+e34d679b61c77026dd0f437d3d91a84b83a422d3  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.13.md b/locale/uk/blog/release/v0.8.13.md
new file mode 100755
index 0000000000000..0d68613808bc6
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.13.md
@@ -0,0 +1,78 @@
+---
+category: release
+version: v0.8.13
+date: 2012-10-25T19:26:44.000Z
+slug: node-v0.8.13
+title: Node v0.8.13 (Stable)
+layout: blog-post.hbs
+---
+
+Warning: This version contains a regression in the EventEmitter class.
+Please use 0.8.14 instead.
+
+2012.10.25, Version 0.8.13 (Stable)
+
+* V8: Upgrade to 3.11.10.25
+
+* npm: Upgrade to 1.1.65
+
+* url: parse hostnames that start with - or _ (Ben Noordhuis)
+
+* repl: Fix Windows 8 terminal issue (Bert Belder)
+
+* typed arrays: use signed char for signed int8s (Aaron Jacobs)
+
+* crypto: fix bugs in DiffieHellman (Ben Noordhuis)
+
+* configure: turn on VFPv3 on ARMv7 (Ben Noordhuis)
+
+* Re-enable OpenSSL UI for entering passphrases via tty (Ben Noordhuis)
+
+* repl: ensure each REPL instance gets its own "context" (Nathan Rajlich)
+
+
+Source Code: https://nodejs.org/dist/v0.8.13/node-v0.8.13.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.13/node-v0.8.13.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.13/node-v0.8.13-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.13/x64/node-v0.8.13-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.13/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.13/node-v0.8.13-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.13/node-v0.8.13-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.13/node-v0.8.13-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.13/node-v0.8.13-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.13/
+
+Website: https://nodejs.org/docs/v0.8.13/
+
+Documentation: https://nodejs.org/docs/v0.8.13/api/
+
+Shasums:
+```
+1f396f068e40639f70e5d60e8e33d0cbb5597748  node-v0.8.13-darwin-x64.tar.gz
+afa416c3b6209f3d72926537c85d5943b3b07a0d  node-v0.8.13-darwin-x86.tar.gz
+bdcf8b69ccba2ca326c8ff2921232c1663a79d78  node-v0.8.13-linux-x64.tar.gz
+d1fc168b092234bac665dc65d242f3367dfc0f24  node-v0.8.13-linux-x86.tar.gz
+d3d5b19c133c73f060efa4bbe274195c9579f4be  node-v0.8.13-sunos-x64.tar.gz
+98916b4f0c9855dd02d87223d6369f5fa281cbe5  node-v0.8.13-sunos-x86.tar.gz
+732f70fbb800c8fee6202e939502c0f23f76d4a1  node-v0.8.13-x86.msi
+e2da495a2f8dd4b0cd25810c3b4e6b2e9e71cfe3  node-v0.8.13.pkg
+9112a128d83f3e7d26ba0965eb426de0f18c3149  node-v0.8.13.tar.gz
+f8c75e5877f103a842067adff6f6580d1c250c9b  node.exe
+b950a56fa0a00b78212c5d95e4ca6381f8285df9  node.exp
+6fcfb00aaf78be643330f645d2d83d461bc1cbe7  node.lib
+b6b0d540061e83bbe165afbc25aeeb19b00fbbf2  node.pdb
+8017014664dca6b255724f30827553ca420580af  x64/node-v0.8.13-x64.msi
+8a9fd20b6b24aa3bb8eda8f2f9fa1ede19588a41  x64/node.exe
+74ceab4f7d3192bbd2d13d602fe66e3caf7d08e2  x64/node.exp
+780c395cab41a0ef59bdd82fe39f370fa1c5e839  x64/node.lib
+526bd6fadffcea8f56b0a761ccae01f65b018947  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.14.md b/locale/uk/blog/release/v0.8.14.md
new file mode 100755
index 0000000000000..7611f36d4641d
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.14.md
@@ -0,0 +1,83 @@
+---
+category: release
+version: v0.8.14
+date: 2012-10-25T21:26:44.000Z
+slug: node-v0.8.14
+title: Node v0.8.14 (Stable)
+layout: blog-post.hbs
+---
+
+Note: v0.8.13 contains a regression in the EventEmitter class.  This
+is a bugfix release, but contains no new features.  Most of the
+release notes are copied from v0.8.13, since it didn't live long.
+
+
+2012.10.25, Version 0.8.14 (Stable)
+
+* events: Don't clobber pre-existing _events obj in EE ctor (isaacs)
+
+* V8: Upgrade to 3.11.10.25
+
+* npm: Upgrade to 1.1.65
+
+* url: parse hostnames that start with - or _ (Ben Noordhuis)
+
+* repl: Fix Windows 8 terminal issue (Bert Belder)
+
+* typed arrays: use signed char for signed int8s (Aaron Jacobs)
+
+* crypto: fix bugs in DiffieHellman (Ben Noordhuis)
+
+* configure: turn on VFPv3 on ARMv7 (Ben Noordhuis)
+
+* Re-enable OpenSSL UI for entering passphrases via tty (Ben Noordhuis)
+
+* repl: ensure each REPL instance gets its own "context" (Nathan Rajlich)
+
+
+Source Code: https://nodejs.org/dist/v0.8.14/node-v0.8.14.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.14/node-v0.8.14.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.14/node-v0.8.14-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.14/x64/node-v0.8.14-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.14/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.14/node-v0.8.14-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.14/node-v0.8.14-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.14/node-v0.8.14-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.14/node-v0.8.14-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.14/
+
+Website: https://nodejs.org/docs/v0.8.14/
+
+Documentation: https://nodejs.org/docs/v0.8.14/api/
+
+Shasums:
+
+```
+519a0d5daa52eb3f412f5ea86779a1a7f3f73f3d  node-v0.8.14-darwin-x64.tar.gz
+93c38392cb07e5e7386503e8e8b1932dabcd3f09  node-v0.8.14-darwin-x86.tar.gz
+f737747a3c2b62c5e059d866ea27f2f050a12e0a  node-v0.8.14-linux-x64.tar.gz
+cd9db5907cf0796b5277954cb994789a9815f72c  node-v0.8.14-linux-x86.tar.gz
+b6e1c21c2bc9543255bda936bb7206490085dd6b  node-v0.8.14-sunos-x64.tar.gz
+c16a01e116fda023db9b1cd14f8e9520d39cf2c7  node-v0.8.14-sunos-x86.tar.gz
+3d38d581316bb378f39786a2bf0be5072360ab02  node-v0.8.14-x86.msi
+23d5bd298dc5ef77dbcb4f5a1d4ec35a10c9ab79  node-v0.8.14.pkg
+47a1186004f6ce5e25a8555429d72b15519bc7f1  node-v0.8.14.tar.gz
+0150ec86f83c86a4ce99e33671f1a6c00c19981d  node.exe
+7cc38da3b6d550c6a681f8e7e479f95a109f12c7  node.exp
+d9a92fe10b696beb98fca60bc38183990833106b  node.lib
+03e211e842ae613b3e27a2a0d79ed9cf9c864802  node.pdb
+8df2cc066f6cee53deb43eba92a3a1bfd30e9ae7  x64/node-v0.8.14-x64.msi
+84f44295f9ed0f09ee80fd85b3ad1e0c93212795  x64/node.exe
+b20a8aa61f386166c9ce1b51bb14d97eefd39090  x64/node.exp
+dd254fab57148ad6315d87fd6c8ef6ef45baae35  x64/node.lib
+c4ad89d4d71d82f20c7ce620319ad35aca7e56ad  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.15.md b/locale/uk/blog/release/v0.8.15.md
new file mode 100755
index 0000000000000..1030e33acf647
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.15.md
@@ -0,0 +1,74 @@
+---
+date: 2012-11-26T17:14:49.000Z
+title: Node v0.8.15 (Stable)
+slug: node-v0-8-15
+version: v0.8.15
+category: release
+layout: blog-post.hbs
+---
+
+2012.11.26, Version 0.8.15 (Stable)
+
+* npm: Upgrade to 1.1.66 (isaacs)
+
+* linux: use /proc/cpuinfo for CPU frequency (Ben Noordhuis)
+
+* windows: map WSAESHUTDOWN to UV_EPIPE (Ben Noordhuis)
+
+* windows: map ERROR_GEN_FAILURE to UV_EIO (Bert Belder)
+
+* unix: do not set environ unless one is provided (Charlie McConnell)
+
+* domains: don't crash if domain is set to null (Bert Belder)
+
+* windows: fix the x64 debug build (Bert Belder)
+
+* net, tls: fix connect() resource leak (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.15/node-v0.8.15.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.15/node-v0.8.15.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.15/node-v0.8.15-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.15/x64/node-v0.8.15-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.15/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.15/node-v0.8.15-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.15/node-v0.8.15-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.15/node-v0.8.15-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.15/node-v0.8.15-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.15/
+
+Website: https://nodejs.org/docs/v0.8.15/
+
+Documentation: https://nodejs.org/docs/v0.8.15/api/
+
+Shasums:
+
+```
+084f5132d8f2ad704086285a600790c4de323e59  node-v0.8.15-darwin-x64.tar.gz
+8a17c611d96aba9427de21125c2d1696e937245e  node-v0.8.15-darwin-x86.tar.gz
+cbd126c613eb42438a63a789b380b840793b2c83  node-v0.8.15-linux-x64.tar.gz
+73431db2519d4520c6f8ac7303ec6170e6eb17c6  node-v0.8.15-linux-x86.tar.gz
+1ed591003d0f502131540aadbabd95c22d2d936a  node-v0.8.15-sunos-x64.tar.gz
+0c5908f857a65d5f6e8cfc17e4d8114aa4d9f521  node-v0.8.15-sunos-x86.tar.gz
+5c5447b6ef451cfa4762db00aabd740425ea112d  node-v0.8.15-x86.msi
+1e06dc52609dd106fd3553f4a9d12e66bcac1f45  node-v0.8.15.pkg
+a7874cde1a87497992f1f8ea0fdaa760f617a94f  node-v0.8.15.tar.gz
+9251cc51eaa856bdf7c1a92d49419731e6dec830  node.exe
+e4230b867122b42a16cc27eccadde3996cfdf266  node.exp
+f4f7ca1d11877bcb1e50f0a139a0b7438ea406cb  node.lib
+02bc3e986eebb77fcabde4e492d858e14096ac34  node.pdb
+9c1020cc2c7443238093f0cde3875097788e5c7f  x64/node-v0.8.15-x64.msi
+8a76699adbee52ee704408e6708ff5b5b6ebc02f  x64/node.exe
+b9fba72a0da7d2b25dcdcbcf514b877f1cb6399a  x64/node.exp
+81511b51ef403214f0ba97ed29cb5d45ff6a21f7  x64/node.lib
+1519acd77acd41e03238f6ed9a006d97ade4a055  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.16.md b/locale/uk/blog/release/v0.8.16.md
new file mode 100755
index 0000000000000..d50568d6f6ede
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.16.md
@@ -0,0 +1,68 @@
+---
+category: release
+version: 0.8.16
+date: 2012-12-13T16:47:52.000Z
+title: Node v0.8.16 (Stable)
+slug: node-v0-8-16
+layout: blog-post.hbs
+---
+
+2012.12.13, Version 0.8.16 (Stable)
+
+* npm: Upgrade to 1.1.69
+
+* fs: fix WriteStream/ReadStream fd leaks (Ben Noordhuis)
+
+* crypto: fix leak in GetPeerCertificate (Fedor Indutny)
+
+* buffer: Don't double-negate numeric buffer arg (Trevor Norris)
+
+* net: More accurate IP address validation and IPv6 dotted notation. (Joshua Erickson)
+
+
+Source Code: https://nodejs.org/dist/v0.8.16/node-v0.8.16.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.16/node-v0.8.16.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.16/node-v0.8.16-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.16/x64/node-v0.8.16-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.16/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.16/node-v0.8.16-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.16/node-v0.8.16-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.16/node-v0.8.16-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.16/node-v0.8.16-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.16/
+
+Website: https://nodejs.org/docs/v0.8.16/
+
+Documentation: https://nodejs.org/docs/v0.8.16/api/
+
+Shasums:
+
+```
+8ad2323e7909abaaa1e1f6eefa93a31e253acb20  node-v0.8.16-darwin-x64.tar.gz
+760401fbb405f27a6f4379a999fa2408f30af9fb  node-v0.8.16-darwin-x86.tar.gz
+04d67913ea1ba12fbdf7460342f3b801b12cbf78  node-v0.8.16-linux-x64.tar.gz
+5c5bbd485f4fd8682948e31237d7d59be708e64a  node-v0.8.16-linux-x86.tar.gz
+08b870e5b91b94a8b1b1564367e231b20f2ca2b9  node-v0.8.16-sunos-x64.tar.gz
+72a564cab3dccb0569cbab9888f5746acb3b70f9  node-v0.8.16-sunos-x86.tar.gz
+b3daebf61a421aa05dff9d19e8108def951366dc  node-v0.8.16-x86.msi
+2a37219d45a9a2bfa63ce7a57a0c550996b52833  node-v0.8.16.pkg
+6479366bfbc2b4392f7f496dec55b5ab719308c0  node-v0.8.16.tar.gz
+8998022ec5d46e0d083ff3230baa638fa0c40603  node.exe
+8cf330b21d8ad5c1245d6b4e668ca5fe78875c2d  node.exp
+107feafbbf61f7173e97be29b29f33dc96b33d4b  node.lib
+caa002d5f0896d44a9e976d7c2f97d0e5f0fe366  node.pdb
+5914d679d71a687323ff7b9232767f9df0e9d9aa  x64/node-v0.8.16-x64.msi
+ec1debf6dfbf6051635ca9743981e35357b2af9f  x64/node.exe
+21216676af7d407bc70d44c35c966992b7eaab34  x64/node.exp
+ad443c0bf1bbf3a4d0b0a54f4f8ae7c1c235ee49  x64/node.lib
+fb3651dcf2c871d1fdb8b96d11d5f5db137b654c  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.17.md b/locale/uk/blog/release/v0.8.17.md
new file mode 100755
index 0000000000000..43cdda4a7f78c
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.17.md
@@ -0,0 +1,83 @@
+---
+date: 2013-01-10T01:06:36.000Z
+title: Node v0.8.17 (Stable)
+slug: node-v0-8-17-stable
+category: release
+version: 0.8.17
+layout: blog-post.hbs
+---
+
+This release addresses a potential security vulnerability.
+
+If you do not use TypedArrays, then you're fine (but should still
+upgrade for other reasons, like better performance and npm
+peerDependencies.)
+
+If you use TypedArrays, you should upgrade to v0.8.17 as soon as
+possible.  If user input can affect the size parameter in a
+TypedArray, an integer overflow vulnerability could allow an attacker
+to write to areas of memory outside the intended buffer.  Please
+upgrade ASAP.
+
+2013.01.09, Version 0.8.17 (Stable)
+
+* npm: Upgrade to v1.2.0
+  - peerDependencies (Domenic Denicola)
+  - node-gyp v0.8.2 (Nathan Rajlich)
+  - Faster installs from github user/project shorthands (Nathan Zadoks)
+
+* typed arrays: fix 32 bit size/index overflow (Ben Noordhuis)
+
+* http: Improve performance of single-packet responses (Ben Noordhuis)
+
+* install: fix openbsd man page location (Ben Noordhuis)
+
+* http: bubble up parser errors to ClientRequest (Brian White)
+
+
+Source Code: https://nodejs.org/dist/v0.8.17/node-v0.8.17.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.17/node-v0.8.17.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.17/node-v0.8.17-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.17/x64/node-v0.8.17-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.17/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.17/node-v0.8.17-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.17/node-v0.8.17-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.17/node-v0.8.17-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.17/node-v0.8.17-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.17/
+
+Website: https://nodejs.org/docs/v0.8.17/
+
+Documentation: https://nodejs.org/docs/v0.8.17/api/
+
+Shasums:
+
+```
+1efb55f154e6079c7f2a8991ed73b5069307576a  node-v0.8.17-darwin-x64.tar.gz
+d9e3f502b9121b14743fedc7d48ed15cbda3a3da  node-v0.8.17-darwin-x86.tar.gz
+de5d5d32ef97081b57b652289e097a332e9cc8af  node-v0.8.17-linux-x64.tar.gz
+44824481dbb3ed278e613f805f597e8d14f68d11  node-v0.8.17-linux-x86.tar.gz
+6f3ee5e3a3515f79478c18ad61666bdaf73f8485  node-v0.8.17-sunos-x64.tar.gz
+3bcd62169201e8c6223eeef09633998901692da1  node-v0.8.17-sunos-x86.tar.gz
+befea571ebdf67fa47ef84826334599feb3ed7a3  node-v0.8.17-x86.msi
+71b598cd3a418b8ce78a2158d8ae29a6c7e66be6  node-v0.8.17.pkg
+65d22e4e183cee8888c797300d8fdbb5c530c740  node-v0.8.17.tar.gz
+8bf4e9699d41bcc0fcf822af095c2a944aea3e95  node.exe
+2b659a6864682d6613a94a8c187618a3893401bc  node.exp
+082995b6fc667af51aae11b612390800c8e9636c  node.lib
+bbbab14038a29fa67dfcabfd27802c39428e8f8e  node.pdb
+a220542df0610d848ead007673e19cb24c1e0ac5  x64/node-v0.8.17-x64.msi
+636ab1f211624588d3c5073232f30aa5f93eed10  x64/node.exe
+8540c7b6cfb62b51b52c72813ca30d42b936e656  x64/node.exp
+1e0d70fcf5efa6e4c23c1d8ec768c5a8e6c36874  x64/node.lib
+2b13ba57dbdd942b3198b441fea936f8b8154c29  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.18.md b/locale/uk/blog/release/v0.8.18.md
new file mode 100755
index 0000000000000..33c8b4ef03210
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.18.md
@@ -0,0 +1,70 @@
+---
+category: release
+date: 2013-01-18T20:49:35.000Z
+version: 0.8.18
+title: Node v0.8.18 (Stable)
+slug: node-v0-8-18-stable
+layout: blog-post.hbs
+---
+
+2013.01.18, Version 0.8.18 (Stable)
+
+* npm: Upgrade to v1.2.2
+
+* dns: make error message match errno (Dan Milon)
+
+* tls: follow RFC6125 more stricly (Fedor Indutny)
+
+* buffer: reject negative SlowBuffer offsets (Ben Noordhuis)
+
+* install: add simplejson fallback (Chris Dent)
+
+* http: fix "Cannot call method 'emit' of null" (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.18/node-v0.8.18.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.18/node-v0.8.18.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.18/node-v0.8.18-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.18/x64/node-v0.8.18-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.18/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.18/node-v0.8.18-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.18/node-v0.8.18-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.18/node-v0.8.18-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.18/node-v0.8.18-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.18/
+
+Website: https://nodejs.org/docs/v0.8.18/
+
+Documentation: https://nodejs.org/docs/v0.8.18/api/
+
+Shasums:
+
+```
+ddf4062ec395abd2aab18bdadbf94e0c36b9133d  node-v0.8.18-darwin-x64.tar.gz
+a4f6fc9cfddbcbcfc0733abbee24d9834924e648  node-v0.8.18-darwin-x86.tar.gz
+7fbadf6d78f97ee96a20e7d0072e672d160e745b  node-v0.8.18-linux-x64.tar.gz
+0081950ce52058e1d0bb6609f5dd85819e39b90c  node-v0.8.18-linux-x86.tar.gz
+976bcf6a4f64e12bb570618f4a24ac77e74a592c  node-v0.8.18-sunos-x64.tar.gz
+68e21c766f49673cda6b44afaa0462625336c488  node-v0.8.18-sunos-x86.tar.gz
+1a709f10740c08ec0f88e84fc4c61e908de9fa17  node-v0.8.18-x86.msi
+fb07bfaed311607f9e8003171b870928bf64a801  node-v0.8.18.pkg
+e3bc9b64f60f76a32b7d9b35bf86b5d1b8166717  node-v0.8.18.tar.gz
+72c8a2a99f83e48641d55467a1ad2d8d224f048d  node.exe
+9c3ac616aac6c663b2c82a9bca998c99878ef92f  node.exp
+18fb36d6cc766ed506ddf5b0db67394d05368165  node.lib
+155a12e9822a1d65101680774c27481d2de81f0e  node.pdb
+f95437a1e5684e8b246d8b6b0a6d3d2ffcfd1ac6  x64/node-v0.8.18-x64.msi
+3d2b9f1f2e2971fbefee32ed9783fe6b8c1f7d48  x64/node.exe
+282de6e02f75bae87c3e7dda998b26c25ae8e709  x64/node.exp
+d7612894c40655155e72188bf584dbd8c09b0739  x64/node.lib
+49abf88f55028304e50bfb368d68157aed1d0291  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.19.md b/locale/uk/blog/release/v0.8.19.md
new file mode 100755
index 0000000000000..531854c9d5dad
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.19.md
@@ -0,0 +1,75 @@
+---
+category: release
+date: 2013-02-06T17:47:18.000Z
+version: 0.8.19
+title: Node v0.8.19 (Stable)
+slug: node-v0-8-19-stable
+layout: blog-post.hbs
+---
+
+2013.02.06, Version 0.8.19 (Stable)
+
+* npm: Upgrade to v1.2.10
+
+* zlib: pass object size hint to V8 (Ben Noordhuis)
+
+* zlib: reduce memory consumption, release early (Ben Noordhuis)
+
+* buffer: slow buffer copy compatibility fix (Trevor Norris)
+
+* zlib: don't assert on malformed dictionary (Ben Noordhuis)
+
+* zlib: don't assert on missing dictionary (Ben Noordhuis)
+
+* windows: better ipv6 support (Bert Belder)
+
+* windows: add error mappings related to unsupported protocols (Bert Belder)
+
+* windows: map ERROR_DIRECTORY to UV_ENOENT (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.19/node-v0.8.19.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.19/node-v0.8.19.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.19/node-v0.8.19-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.19/x64/node-v0.8.19-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.19/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.19/node-v0.8.19-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.19/node-v0.8.19-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.19/node-v0.8.19-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.19/node-v0.8.19-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.19/
+
+Website: https://nodejs.org/docs/v0.8.19/
+
+Documentation: https://nodejs.org/docs/v0.8.19/api/
+
+Shasums:
+```
+b97ded53b15196764afd1cc456c5b05a40d8bb2f  node-v0.8.19-darwin-x64.tar.gz
+685a21891320f3bfc1b878247d64c9912f83eb19  node-v0.8.19-darwin-x86.tar.gz
+b66b2bb829f627e3cf05bc19ba8b15092b1deb4d  node-v0.8.19-linux-x64.tar.gz
+dcc0be09cf9d9ab863c720f7470a05baea2f7a18  node-v0.8.19-linux-x86.tar.gz
+67fe40e63cbf0a0a079d8214687fb9848b67bbe2  node-v0.8.19-sunos-x64.tar.gz
+c949abebb61bfbe21d4f51337d2b4c76965bc467  node-v0.8.19-sunos-x86.tar.gz
+0e41157ca1cbc43aafc3ac65bdde5564e2e13de6  node-v0.8.19-x86.msi
+a77d2ac238aba0003144ab2d04fc6d1356c18cc5  node-v0.8.19.pkg
+f4fdbb642055be65579e11cb52c823573efabcf2  node-v0.8.19.tar.gz
+7bafe93904e9741592bc9a593169cabec9cca0dd  node.exe
+0785e45ade6642b4fee320e950795110ef1ca94c  node.exp
+f623019194ff2e9cf975fe007032ece07adb4e49  node.lib
+3ba7c54527b8f15521f9e667867e485ef46ffda4  node.pdb
+d44bff1c52b24d385edd69db14507739e53a654a  x64/node-v0.8.19-x64.msi
+ec60e8b2e68529d3256a94193df62088a986a826  x64/node.exe
+daf65fd50219588877637b414be36e78a859d4e6  x64/node.exp
+c154205667ad7c9063cebeeb98af39f203c8c16e  x64/node.lib
+f4a494678c0da4bad787f25001bb209f37f82722  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.2.md b/locale/uk/blog/release/v0.8.2.md
new file mode 100755
index 0000000000000..d85e896668ab6
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.2.md
@@ -0,0 +1,76 @@
+---
+version: 0.8.2
+title: Version 0.8.2 (stable)
+category: release
+slug: node-v0-8-2-stable
+date: 2012-07-08T22:00:00.000Z
+layout: blog-post.hbs
+---
+
+2012.07.09, Version 0.8.2 (Stable)
+
+* npm: Upgrade to 1.1.36
+
+* readline: don't use Function#call() (Nathan Rajlich)
+
+* Code cleanup to pass 'use strict' (Jonas Westerlund)
+
+* module: add filename to require() json errors (TJ Holowaychuk)
+
+* readline: fix for unicode prompts (Tim Macfarlane)
+
+* timers: fix handling of large timeouts (Ben Noordhuis)
+
+* repl: fix passing an empty line inserting "undefined" into the buffer (Nathan Rajlich)
+
+* repl: fix crashes when buffering command (Maciej Małecki)
+
+* build: rename strict_aliasing to node_no_strict_aliasing (Ben Noordhuis)
+
+* build: disable -fstrict-aliasing for any gcc < 4.6.0 (Ben Noordhuis)
+
+* build: detect cc version with -dumpversion (Ben Noordhuis)
+
+* build: handle output of localized gcc or clang (Ben Noordhuis)
+
+* unix: fix memory corruption in freebsd.c (Ben Noordhuis)
+
+* unix: fix 'zero handles, one request' busy loop (Ben Noordhuis)
+
+* unix: fix busy loop on unexpected tcp message (Ben Noordhuis)
+
+* unix: fix EINPROGRESS busy loop (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.2/node-v0.8.2.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.2/node-v0.8.2.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.2/node-v0.8.2-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.2/x64/node-v0.8.2-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.2/x64/
+
+Other release files: https://nodejs.org/dist/v0.8.2/
+
+Website: https://nodejs.org/docs/v0.8.2/
+
+Documentation: https://nodejs.org/docs/v0.8.2/api/
+
+Shasums:
+
+```
+6571b7aad17ed4860d9ecb7946098dcd569e3eb0  node-v0.8.2-x86.msi
+8436e940b8c3b1dff73bf4d1eee98fd3b1fc6295  node-v0.8.2.pkg
+0e743d21b487151e67950f09198def058db19a1e  node-v0.8.2.tar.gz
+dcc45bee9d4a6b38ccef0f00e4a6028864f07278  node.exe
+5417f98a533c90f2b72ed3a2a002c2c36a65cb75  node.exp
+57700a9555d16ebf5401898c179669654f045c5f  node.lib
+5bf7e8777d715d5d6b40c21ea3969c4244c20879  node.pdb
+6a5fe7efb56c3e17de357e9b9adc8f1c54db895a  x64/node-v0.8.2-x64.msi
+72f04cb5bb25bd568cb7bc42eb5e1365e614b672  x64/node.exe
+6b402ca44a45a3bc1393854d92247bf79eb3df2b  x64/node.exp
+ad39add3918fb31aef25e3a4acfe1da499900143  x64/node.lib
+fa981c97e0c474ede8e7c28904d710cc3ee3390c  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.20.md b/locale/uk/blog/release/v0.8.20.md
new file mode 100755
index 0000000000000..323ca5c5f496c
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.20.md
@@ -0,0 +1,65 @@
+---
+title: Node v0.8.20 (Stable)
+slug: node-v0-8-20-stable
+category: release
+date: 2013-02-15T19:21:42.000Z
+version: 0.8.20
+layout: blog-post.hbs
+---
+
+2013.02.15, Version 0.8.20 (Stable)
+
+* npm: Upgrade to v1.2.11
+
+* http: Do not let Agent hand out destroyed sockets (isaacs)
+
+* http: Raise hangup error on destroyed socket write (isaacs)
+
+* http: protect against response splitting attacks (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.20/node-v0.8.20.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.20/node-v0.8.20.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.20/node-v0.8.20-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.20/x64/node-v0.8.20-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.20/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.20/node-v0.8.20-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.20/node-v0.8.20-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.20/node-v0.8.20-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.20/node-v0.8.20-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.20/
+
+Website: https://nodejs.org/docs/v0.8.20/
+
+Documentation: https://nodejs.org/docs/v0.8.20/api/
+
+Shasums:
+```
+2b87bf077022b8fa1cbcec10ea3866574fed2b75  node-v0.8.20-darwin-x64.tar.gz
+42023ffbdbf36ef69250bd750f112e684eb97008  node-v0.8.20-darwin-x86.tar.gz
+93480cbc67f2c757879228434bce1fd765db7df8  node-v0.8.20-linux-x64.tar.gz
+7fedae5ce4b366d5dcaa7f2e770b3ff739648a51  node-v0.8.20-linux-x86.tar.gz
+fd66ea1bfbe5c8fe8df5ba8cc79cd3fab6e753ac  node-v0.8.20-sunos-x64.tar.gz
+ca6ad9aa92330358f6201191347451ab42fe12cf  node-v0.8.20-sunos-x86.tar.gz
+200ff5e5083df2a6bb4552e673d81b498e9812f0  node-v0.8.20-x86.msi
+54440b1f525da0126b434440ee6433c2b96959ae  node-v0.8.20.pkg
+b780f58f0e3bc43d2380d4a935f2b45350783b37  node-v0.8.20.tar.gz
+8e13b125c3572a1cb46364b3241405cdf7af1a82  node.exe
+f67ea64d6686207dbacb9bb8feacce3ac8899ec8  node.exp
+c338212caf48d945e8e8049c2a0c30e38e8730d6  node.lib
+019b24c60cdb03f9d8209290e7af90e8565999e7  node.pdb
+67fff498c5271033073a3ca9fc01178b5f5c309a  x64/node-v0.8.20-x64.msi
+6ecab177a47ff5c74397799b329c2359b40c7d1f  x64/node.exe
+bcd51345c05a28be5db3553fc578aa3dd52fc97e  x64/node.exp
+825f2ba0bb9d7bd170adef89009b84ee147754e5  x64/node.lib
+50c4cc483cc4b675966c7ec524afacb59ff99164  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.21.md b/locale/uk/blog/release/v0.8.21.md
new file mode 100755
index 0000000000000..59d2d4752e924
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.21.md
@@ -0,0 +1,89 @@
+---
+date: 2013-02-25T21:48:51.000Z
+version: 0.8.21
+category: release
+title: Node v0.8.21 (Stable)
+slug: node-v0-8-21-stable
+layout: blog-post.hbs
+---
+
+2013.02.25, Version 0.8.21 (Stable)
+
+* http: Do not free the wrong parser on socket close (isaacs)
+
+* http: Handle hangup writes more gently (isaacs)
+
+* zlib: fix assert on bad input (Ben Noordhuis)
+
+* test: add TAP output to the test runner (Timothy J Fontaine)
+
+* unix: Handle EINPROGRESS from domain sockets (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.21/node-v0.8.21.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.21/node-v0.8.21.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.21/node-v0.8.21-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.21/x64/node-v0.8.21-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.21/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.21/node-v0.8.21-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.21/node-v0.8.21-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.21/node-v0.8.21-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.21/node-v0.8.21-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.21/
+
+Website: https://nodejs.org/docs/v0.8.21/
+
+Documentation: https://nodejs.org/docs/v0.8.21/api/
+
+Shasums:
+```
+383b9009a587b7390a5a00cef4ece441fb16dd82  node-v0.8.21-darwin-x64.tar.gz
+47654ca8ecc93c846e6f7493a19931b99d5e4b87  node-v0.8.21-darwin-x86.tar.gz
+46d66f3b95f447811e9253d66050859b4bb81ea0  node-v0.8.21-linux-x64.tar.gz
+1f16e50dacd5e942970c28be1e578e6260a116c4  node-v0.8.21-linux-x86.tar.gz
+b24b5e0acc53f004122c0cb2df775c4493b1e048  node-v0.8.21-sunos-x64.tar.gz
+54ca0c94dff35e941fe90d10755427a15d6519ae  node-v0.8.21-sunos-x86.tar.gz
+38c5855c1ebd70fde111d50343a163a03cff9765  node-v0.8.21-x86.msi
+60cd1fb8f43943bd3ed7c07745df1b3e81bafc13  node-v0.8.21.pkg
+8b75377eafb5e77d6dff141c9533202d5a589ce4  node-v0.8.21.tar.gz
+c310779c80d21be7556ec0921d5afca8f64792eb  node.exe
+61b98f9dfbe70184788b6f010ce7667c9cba0fdc  node.exp
+78c37ac837bbb8fefd691e351b3c20f136b212ee  node.lib
+40cc197db5c9fc4ded4509b5ae21bc53d178998e  node.pdb
+ec29a824e51308349f7895c010469f8e59939094  x64/node-v0.8.21-x64.msi
+e4c5563c38a01dac1a97f6366175d1fef86da262  x64/node.exe
+8e51783d5e03148f01db8386102e4ffc4e30deda  x64/node.exp
+a6017052052bb469a50327b4f40c990c25da0932  x64/node.lib
+fb8d24e5208b14d35997bc3b46e325316e6ad94d  x64/node.pdb
+```
+
+Shasums:
+```
+62cd69928ce2da9e8512b3efb96aba353ee54a91  node-v0.8.21-darwin-x64.tar.gz
+62cf9b990f8e424e7fdb1d50a46d779e4d508b23  node-v0.8.21-darwin-x86.tar.gz
+83e92aec4f4a0167e7c5b3ef04388fc33712d97b  node-v0.8.21-linux-x64.tar.gz
+83a8aa10dafa196b372958d1052f61fe1c16c2a4  node-v0.8.21-linux-x86.tar.gz
+588830b0d095c0ef3583d9f7f574426f5b456e2e  node-v0.8.21-sunos-x64.tar.gz
+e4eff5914432da3cf12a833aaa0444693671cca1  node-v0.8.21-sunos-x86.tar.gz
+8146b2254caa814157aa511075dcf7b42d0ecb59  node-v0.8.21-x86.msi
+60cd1fb8f43943bd3ed7c07745df1b3e81bafc13  node-v0.8.21.pkg
+65ab7307f1aee12be4c88e396e2510967a52b1c6  node-v0.8.21.tar.gz
+5d770ad554ee4a73278b2d90029e758e0a676074  node.exe
+17514f32c57c64bd0d367c71ed0e6dc399fc9e12  node.exp
+9404eff8562dfb0a6e0e72167278ac6131be5d3a  node.lib
+94908174f715d2707d48e6d53a1f96f33059f56c  node.pdb
+36750abf56120a63d9fa9b2b75bdc98dfac051f7  x64/node-v0.8.21-x64.msi
+b61b9620e936bc9c19043a02625aed9922aeb653  x64/node.exe
+21a0e855e652e7fbe84e7efc1f7a3542fa870372  x64/node.exp
+f9d017c07030599e3442a958020381a37402dc81  x64/node.lib
+3b35fbac0962aaff46bdd2f06412dcb1f80b9895  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.22.md b/locale/uk/blog/release/v0.8.22.md
new file mode 100755
index 0000000000000..e2548bd260da4
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.22.md
@@ -0,0 +1,65 @@
+---
+date: 2013-03-07T00:16:34.000Z
+version: 0.8.22
+category: release
+title: Node v0.8.22 (Stable)
+slug: node-v0-8-22-stable
+layout: blog-post.hbs
+---
+
+2013.03.07, Version 0.8.22 (Stable)
+
+* npm: Update to 1.2.14
+
+* cluster: propagate bind errors (Ben Noordhuis)
+
+* crypto: don't assert when calling Cipher#final() twice (Ben Noordhuis)
+
+* build, windows: disable SEH (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.22/node-v0.8.22.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.22/node-v0.8.22.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.22/node-v0.8.22-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.22/x64/node-v0.8.22-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.22/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.22/node-v0.8.22-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.22/node-v0.8.22-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.22/node-v0.8.22-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.22/node-v0.8.22-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.22/
+
+Website: https://nodejs.org/docs/v0.8.22/
+
+Documentation: https://nodejs.org/docs/v0.8.22/api/
+
+Shasums:
+```
+c536e71f028213e1dd195f6c143c43d4d92b3fda  node-v0.8.22-darwin-x64.tar.gz
+c3993a424034022a675c8822a44402d1a04567d3  node-v0.8.22-darwin-x86.tar.gz
+fb2cd76139f258ff73980b2940c23e3d05ec7fc3  node-v0.8.22-linux-x64.tar.gz
+540154b5be3a5c378b9c6b5b955942eede604e22  node-v0.8.22-linux-x86.tar.gz
+607943d795c9e4e421e0d2b9b887f81057535f72  node-v0.8.22-sunos-x64.tar.gz
+518a6d6e1cc03ef5c25f408f3a6f7b2ba0e27750  node-v0.8.22-sunos-x86.tar.gz
+7eae67719868fe45d016a04a031bf3e95bd3b05e  node-v0.8.22-x86.msi
+efe68fecb78059b990e03970eaf8df7eb690d662  node-v0.8.22.pkg
+1b7e65da70e2b3c2feacb1b13f673dfe43beb381  node-v0.8.22.tar.gz
+190ead83110217ab9e6c52e6ac08bac8a305d6b3  node.exe
+7e5b75cbe0af651a4200e0fa4a1429466a97df0a  node.exp
+35b92f30e337696ef7c34206a5a808cc4a9d0184  node.lib
+29ced022452a877255aaa0bc395f031b12aa695e  node.pdb
+a4251271f65e3b210426dfa44cfbbc39b79b1efc  x64/node-v0.8.22-x64.msi
+93f9106d855e9b6269a392cfcbd8aca2c7403293  x64/node.exe
+95b77dd57b652d7f11fc8de7bb742fc48ee0223c  x64/node.exp
+03499f2f1d163821927a11ff633ac9a25737910e  x64/node.lib
+405108c20af639582116ef15cb759791298ba4b9  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.23.md b/locale/uk/blog/release/v0.8.23.md
new file mode 100755
index 0000000000000..90518b6bdc6fb
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.23.md
@@ -0,0 +1,72 @@
+---
+date: 2013-04-09T00:32:26.000Z
+version: 0.8.23
+category: release
+title: Node v0.8.23 (Legacy)
+slug: node-v0-8-23-legacy
+layout: blog-post.hbs
+---
+
+2013.04.09, Version 0.8.23 (Legacy)
+
+* npm: Upgrade to v1.2.18
+
+* http: Avoid EE warning on ECONNREFUSED handling (isaacs)
+
+* tls: Re-enable check of CN-ID in cert verification (Tobias Müllerleile)
+
+* child_process: fix sending utf-8 to child process (Ben Noordhuis)
+
+* crypto: check key type in GetPeerCertificate() (Ben Noordhuis)
+
+* win/openssl: mark assembled object files as seh safe (Bert Belder)
+
+* windows/msi: fix msi build issue with WiX 3.7/3.8 (Raymond Feng)
+
+
+Source Code: https://nodejs.org/dist/v0.8.23/node-v0.8.23.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.23/node-v0.8.23.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.23/node-v0.8.23-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.23/x64/node-v0.8.23-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.23/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.23/node-v0.8.23-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.23/node-v0.8.23-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.23/node-v0.8.23-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.23/node-v0.8.23-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.23/
+
+Website: https://nodejs.org/docs/v0.8.23/
+
+Documentation: https://nodejs.org/docs/v0.8.23/api/
+
+Shasums:
+
+```
+64cf0081e4d5d7ac528ce938007f9a7d3d952896  node-v0.8.23-darwin-x64.tar.gz
+698b9dd9ece94cde200c25d881700a23a510883e  node-v0.8.23-darwin-x86.tar.gz
+94ea21cb5425d712b92289a82e0f48541d163fef  node-v0.8.23-linux-x64.tar.gz
+c6880d51464904d782d6438bb451fdc85cb874eb  node-v0.8.23-linux-x86.tar.gz
+9da74301acd0e157a132392bc0e3dd9760400fbe  node-v0.8.23-sunos-x64.tar.gz
+dffe26030f95c6f4c1b39ca9eae7d0882b1caacc  node-v0.8.23-sunos-x86.tar.gz
+0b8534504bc6a00215e21e03650228a37400b228  node-v0.8.23-x86.msi
+033d01b7675f557b9cb49148a860d62f015c63fd  node-v0.8.23.pkg
+13772b9c1060aae5441f11cd3fdbe4e4791612b9  node-v0.8.23.tar.gz
+d0afaf05544c9fa8b4b6df5f1f03feb9167fb493  node.exe
+13067ab2f18797536a38a76e5f8087ec54f45b6c  node.exp
+8a253e09bfa128b09ad0a0a507db8f7c96eba537  node.lib
+51f36628dc6ec058966de7a9f3054617b0ddbb30  node.pdb
+367967503a8963557f647bd9766a980f7c78ff93  x64/node-v0.8.23-x64.msi
+e86d6b984a937b27e1809db551d2159aea19c3d5  x64/node.exe
+29abfe7952dafde326ff52094ec49445f41f5366  x64/node.exp
+d769b0e9af6975dcd860f3a57c3d3cc96c240e46  x64/node.lib
+e4268618e8dea66f2d1fa9bf8b817ae1e7106337  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.24.md b/locale/uk/blog/release/v0.8.24.md
new file mode 100755
index 0000000000000..2eedda034a63e
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.24.md
@@ -0,0 +1,66 @@
+---
+date: 2013-06-04T18:09:55.000Z
+version: 0.8.24
+category: release
+title: Node v0.8.24 (Maintenance)
+slug: node-v0-8-24-maintenance
+layout: blog-post.hbs
+---
+
+2013.06.04, Version 0.8.24 (maintenance)
+
+* npm: Upgrade to v1.2.24
+
+* url: Properly parse certain oddly formed urls (isaacs)
+
+* http: Don't try to destroy nonexistent sockets (isaacs)
+
+* handle_wrap: fix NULL pointer dereference (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.24/node-v0.8.24.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.24/node-v0.8.24.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.24/node-v0.8.24-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.24/x64/node-v0.8.24-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.24/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.24/node-v0.8.24-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.24/node-v0.8.24-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.24/node-v0.8.24-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.24/node-v0.8.24-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.24/
+
+Website: https://nodejs.org/docs/v0.8.24/
+
+Documentation: https://nodejs.org/docs/v0.8.24/api/
+
+Shasums:
+
+```
+bd2f2c1dda9812d773a3d403ca69700d59471746  node-v0.8.24-darwin-x64.tar.gz
+041553ba728039c7876bd109285263e654e95d80  node-v0.8.24-darwin-x86.tar.gz
+4fb7ce5d80d1b9ac5cbe1d7ee1e7697e35536a35  node-v0.8.24-linux-x64.tar.gz
+0cbdb661fde7414b75b5e0d7735405b1e7974b91  node-v0.8.24-linux-x86.tar.gz
+0f48da822862122bc9690bdba063f6cf954c7f5a  node-v0.8.24-sunos-x64.tar.gz
+095fd055c9299906a11f30159443b5be784f9e20  node-v0.8.24-sunos-x86.tar.gz
+cf96df4d163bdb588044245cb5e082e136ed71d7  node-v0.8.24-x86.msi
+82f3c12752b1891bb208677fe7f280f8cbec36ab  node-v0.8.24.pkg
+4035c547a98a9e9b9e7a036abe84f19c78220b8f  node-v0.8.24.tar.gz
+b65113c23b0a653a3befec55e42f7a4a3db691e2  node.exe
+abd8a7ab174c6f3a8508cc0fa725a35aa8258738  node.exp
+1601a02e694f60d6e37adefe29fae75ec4bedf52  node.lib
+b420062ebfe1fc3e9a14a65c76e50d7433ed7120  node.pdb
+93d6cde7e7a72aac47a4053c5e8ceefd23e24344  x64/node-v0.8.24-x64.msi
+fa63de49e8839f581aece864249c61810f9af13f  x64/node.exe
+b3737b22816b6324a44afab9ad6722c604ed317c  x64/node.exp
+f08cdeb9f0414afb23ab4079f584edecc43e32ab  x64/node.lib
+4bdd92ba52fc3d9ff6184df00d9f9f53ef644cde  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.25.md b/locale/uk/blog/release/v0.8.25.md
new file mode 100755
index 0000000000000..43e0c0e2f1baf
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.25.md
@@ -0,0 +1,62 @@
+---
+date: 2013-06-13T20:18:09.000Z
+version: 0.8.25
+category: release
+title: Node v0.8.25 (Maintenance)
+slug: node-v0-8-25-maintenance
+layout: blog-post.hbs
+---
+
+2013.06.13, Version 0.8.25 (maintenance)
+
+* npm: Upgrade to 1.2.30
+
+* child_process: fix handle delivery (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.25/node-v0.8.25.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.25/node-v0.8.25.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.25/node-v0.8.25-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.25/x64/node-v0.8.25-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.25/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.25/node-v0.8.25-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.25/node-v0.8.25-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.25/node-v0.8.25-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.25/node-v0.8.25-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.25/
+
+Website: https://nodejs.org/docs/v0.8.25/
+
+Documentation: https://nodejs.org/docs/v0.8.25/api/
+
+Shasums:
+
+```
+c650dca3031ea09535a5cb95648a9edf43dcb23a  node-v0.8.25-darwin-x64.tar.gz
+d479e24f693331bd09b7a29e9cb2b2140f5f0606  node-v0.8.25-darwin-x86.tar.gz
+5fbf6e7718cb8576682479e002081c23b5ebb299  node-v0.8.25-linux-x64.tar.gz
+c037c589f77e597503a606d66c5ab7a0d1e1b3fb  node-v0.8.25-linux-x86.tar.gz
+ed5709fbd80c167183ca60cf4c435caa49d35034  node-v0.8.25-sunos-x64.tar.gz
+6c2914ec896330e9f6eba65cbec738b042712663  node-v0.8.25-sunos-x86.tar.gz
+26cc19bc19e344e4b51ab33775d00e811bf9b1eb  node-v0.8.25-x86.msi
+4c7ec87036616ec6e96f8c4b7242c86c3380231e  node-v0.8.25.pkg
+df91c9de8f3f14efb4cbe52d3ca8beb754b2a39a  node-v0.8.25.tar.gz
+d111ef9ac2b2cb4d3126f147c2714ce2441d37aa  node.exe
+a8cd86993a6dcf8a22d1cfda2fcd6c4865aac1da  node.exp
+5f8538ebd80078a1eee7dfe11f1b6d21d32f38f8  node.lib
+bc4b361c1594a47902e94dddf8308be5b48b4f81  node.pdb
+a6a559c81802f43cd220b83e13712f71d5f13484  x64/node-v0.8.25-x64.msi
+fb004a281f3914961ce2c08e859c007b5c7d61a5  x64/node.exe
+8954509d45e6a9d160130acc4313a8cb4ee870f4  x64/node.exp
+cc332ca7a4b34ed834e5ad07abdbe1ce79bba5a6  x64/node.lib
+24511046a8504ef65f77cbd30e5bad6b18751148  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.26.md b/locale/uk/blog/release/v0.8.26.md
new file mode 100755
index 0000000000000..f4c19166b2b1b
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.26.md
@@ -0,0 +1,74 @@
+---
+date: 2013-10-18T21:52:30.000Z
+version: 0.8.26
+category: release
+title: Node v0.8.26 (Maintenance)
+slug: node-v0-8-26-maintenance
+layout: blog-post.hbs
+---
+
+This release contains a security fix for the http server implementation, please
+upgrade as soon as possible. Details will be released soon.
+
+2013.10.13, Version 0.8.26 (maintenance)
+
+* v8: Upgrade to 3.11.10.26
+
+* crypto: clear openssl error stack when handled (Ben Noordhuis)
+
+* crypto: clear errors from verify failure (Timothy J Fontaine)
+
+* crypto: fix memory leak in LoadPKCS12 (Fedor Indutny)
+
+* http: provide backpressure for pipeline flood (isaacs)
+
+* http_parser: expose pause/resume method for parser (Timothy J Fontaine)
+
+* readline: pause stdin before turning off terminal raw mode (Daniel Chatfield)
+
+
+Source Code: https://nodejs.org/dist/v0.8.26/node-v0.8.26.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.26/node-v0.8.26.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.26/node-v0.8.26-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.26/x64/node-v0.8.26-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.26/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.26/node-v0.8.26-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.26/node-v0.8.26-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.26/node-v0.8.26-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.26/node-v0.8.26-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.26/
+
+Website: https://nodejs.org/docs/v0.8.26/
+
+Documentation: https://nodejs.org/docs/v0.8.26/api/
+
+Shasums:
+```
+b9fa5fca6282a01d491ab585b6a6a64f23ea4da2  node-v0.8.26-darwin-x64.tar.gz
+ba760b282f38f62ad333c2ecc69d3b296f87cf4a  node-v0.8.26-darwin-x86.tar.gz
+c96470908234656c6060cbe0dab4502f90ca7cd1  node-v0.8.26-linux-x64.tar.gz
+3b5c776ae8632df2a4c67b89bdd37d843135be90  node-v0.8.26-linux-x86.tar.gz
+6b9b6bb2676b37ff63f240931f68aa22e9187e99  node-v0.8.26-sunos-x64.tar.gz
+cb3f975293f9561fdda0b46571aee570576e0406  node-v0.8.26-sunos-x86.tar.gz
+668bbc8240497675bb4ed3b61c6f7fb79772b264  node-v0.8.26-x86.msi
+e51a33c28e2c75b0e40826100e5f6b84d5cf8d98  node-v0.8.26.pkg
+2ec960bcc8cd38da271f83c1b2007c12da5153b3  node-v0.8.26.tar.gz
+860ec0bcb6e89fcee3e45e56e469dd28cfcf400c  node.exe
+ad0e366a82e8570768f5c92d97eebd8fd4a54f8f  node.exp
+559a7b4e3c49b1071d1cd1374cf4bc4bae2aa558  node.lib
+687eeb71782ac36f26aaba60e07bd92f47bfcf36  node.pdb
+b10e28a100ab40169759bd431ccc855de1763fa8  x64/node-v0.8.26-x64.msi
+19b5210e212b3b5473c251786c3d22b8cb919f5f  x64/node.exe
+6129121aad9d48ffa19a712f59e6acb9bff14eb1  x64/node.exp
+4eb1822b10ec3b7a17deff1126725c30c5ef65b1  x64/node.lib
+7f39e38b62ad44c774ae381a661726494b2f066e  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.27.md b/locale/uk/blog/release/v0.8.27.md
new file mode 100755
index 0000000000000..bb19846a5b808
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.27.md
@@ -0,0 +1,62 @@
+---
+date: 2014-06-16T15:33:45.000Z
+version: 0.8.27
+category: release
+title: Node v0.8.27 (Maintenance)
+slug: node-v0-8-27-
+layout: blog-post.hbs
+---
+
+2014.06.09, Version 0.8.27 (maintenance)
+
+* openssl: update to 1.0.0m (CVE-2014-0224)
+
+* utf8: Prevent Node from sending invalid UTF-8 (Felix Geisendörfer)
+  - *NOTE* this introduces a breaking change, previously you could construct
+invalid UTF-8 and invoke an error in a client that was expecting valid
+UTF-8, now unmatched surrogate pairs are replaced with the unknown UTF-8
+character. To restore the old functionality simply have NODE_INVALID_UTF8
+environment variable set.
+
+* tls: fix pool usage race (Fedor Indutny)
+
+* fs: close file if fstat() fails in readFile() (cjihrig)
+
+
+Source Code: https://nodejs.org/dist/v0.8.27/node-v0.8.27.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.27/node-v0.8.27.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.27/node-v0.8.27-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.27/x64/node-v0.8.27-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.27/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.27/node-v0.8.27-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.27/node-v0.8.27-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.27/node-v0.8.27-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.27/node-v0.8.27-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.27/
+
+Website: https://nodejs.org/docs/v0.8.27/
+
+Documentation: https://nodejs.org/docs/v0.8.27/api/
+
+Shasums:
+```
+089e075cd556b6124f27d41045f6c5a4c119f9da  node-v0.8.27-darwin-x64.tar.gz
+88014cb30b27f410b89c99a7ccbf32dd8aa19bfd  node-v0.8.27-darwin-x86.tar.gz
+fe2471f055af273c222c4d982e92ffe32369d41f  node-v0.8.27-linux-x64.tar.gz
+6096cba0eb9f0cb8a3b618aa7dcf7f4c29cda82b  node-v0.8.27-linux-x86.tar.gz
+b775af237c0e6c62969ab7886bab3b0cf1563f11  node-v0.8.27-sunos-x64.tar.gz
+8d396f1e546b104616a0e9f3fd20bc7eaa9a370f  node-v0.8.27-sunos-x86.tar.gz
+9e1acfc8970ef80011257080576321dc136f7236  node-v0.8.27-x86.msi
+04a1961f5a4fa9e953aecd589fe5aea5f17e3a56  node-v0.8.27.pkg
+13ebdc277c76732089982b29fb25941dbee5af3f  node-v0.8.27.tar.gz
+d1a41a081663ecf036390dd2f511fa7b452cc1ad  x64/node-v0.8.27-x64.msi
+```
diff --git a/locale/uk/blog/release/v0.8.28.md b/locale/uk/blog/release/v0.8.28.md
new file mode 100755
index 0000000000000..d76ab3fd58331
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.28.md
@@ -0,0 +1,69 @@
+---
+date: 2014-07-31T18:39:10.000Z
+version: 0.8.28
+category: release
+title: Node v0.8.28 (Maintenance)
+slug: node-v0-8-28-maintenance
+layout: blog-post.hbs
+---
+
+2014.07.31, Version 0.8.28 (maintenance)
+
+* v8: Interrupts must not mask stack overflow. (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.8.28/node-v0.8.28.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.28/node-v0.8.28.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.28/node-v0.8.28-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.28/x64/node-v0.8.28-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.28/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.28/node-v0.8.28-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.28/node-v0.8.28-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.28/node-v0.8.28-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.28/node-v0.8.28-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.28/
+
+Website: https://nodejs.org/docs/v0.8.28/
+
+Documentation: https://nodejs.org/docs/v0.8.28/api/
+
+Shasums:
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+3e6fcb94f48c911774632d33e98e2d635b136b24  node-v0.8.28-darwin-x64.tar.gz
+1254edd0e7778555e2ae5861bc228ab4bf3397ac  node-v0.8.28-darwin-x86.tar.gz
+a17fc55576af625ec12e366b30c4a44870a5f194  node-v0.8.28-linux-x64.tar.gz
+835f784d38675a789ee269e08f266a2ab46aa09c  node-v0.8.28-linux-x86.tar.gz
+39750b9b4d792e42b85dd0a620e781de8de23471  node-v0.8.28-sunos-x64.tar.gz
+1d44e2e66219617ba8565c9a7ef05e999aaab34f  node-v0.8.28-sunos-x86.tar.gz
+77f94aa76d204fa9e8e9b906dd045b157221a1f2  node-v0.8.28-x86.msi
+ea2b94d75658914ddfe6a536ef27d1c016156e2d  node-v0.8.28.tar.gz
+34d7b1561e32a207ed1de8089305d95773ee3762  node.exe
+8fb6bb05c84b5621124e164877b32941ad7a441f  node.exp
+e1cba9b0aafbd9185a84e612df002a95e58d5e68  node.lib
+2f74410204ce93db1ee98ee4c8a560dfaa4a02cb  node.pdb
+ae0f6c7296bd36c91cb8335c07c1f27d95fb056a  x64/node-v0.8.28-x64.msi
+0d2a88f7e331b25d16b30e37d768ecce7aafc23a  x64/node.exe
+374539be666e92b9b0756e9a9d199012dcc3da3e  x64/node.exp
+70f0fa0d13730a5ce261a0153eb665a918544e1a  x64/node.lib
+94000769cd6448b2523e71bb68628a7c10b0ea3c  x64/node.pdb
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+iEYEARECAAYFAlPajJYACgkQfTP/nQJGQG0TGACeIxA8Thy6bJBIgx2SA6FrwiT5
+FFoAoIvg2Zhls64/rs3hUSPeguo2H8zU
+=6O1o
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v0.8.3.md b/locale/uk/blog/release/v0.8.3.md
new file mode 100755
index 0000000000000..11cc5cc6c2ad4
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.3.md
@@ -0,0 +1,74 @@
+---
+category: release
+date: 2012-07-19T17:09:26.413Z
+version: 0.8.3
+title: Version 0.8.3 (Stable)
+slug: node-v0-8-3-stable
+layout: blog-post.hbs
+---
+
+2012.07.19, Version 0.8.3 (Stable)
+
+* V8: upgrade to 3.11.10.15
+
+* npm: Upgrade to 1.1.43
+
+* net: fix net.Server.listen({fd:x}) error reporting (Ben Noordhuis)
+
+* net: fix bogus errno reporting (Ben Noordhuis)
+
+* build: Move npm shebang logic into an npm script (isaacs)
+
+* build: fix add-on loading on freebsd (Ben Noordhuis)
+
+* build: disable unsafe optimizations (Ben Noordhuis)
+
+* build: fix spurious mksnapshot crashes for good (Ben Noordhuis)
+
+* build: speed up genv8constants (Dave Pacheco)
+
+* fs: make unwatchFile() remove a specific listener (Ben Noordhuis)
+
+* domain: Remove first arg from intercepted fn (Toshihiro Nakamura)
+
+* domain: Fix memory leak on error (isaacs)
+
+* events: Fix memory leak from removeAllListeners (Nathan Rajlich)
+
+* zlib: Fix memory leak in Unzip class. (isaacs)
+
+* crypto: Fix memory leak in DecipherUpdate() (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.8.3/node-v0.8.3.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.3/node-v0.8.3.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.3/node-v0.8.3-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.3/x64/node-v0.8.3-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.3/x64/
+
+Other release files: https://nodejs.org/dist/v0.8.3/
+
+Website: https://nodejs.org/docs/v0.8.3/
+
+Documentation: https://nodejs.org/docs/v0.8.3/api/
+
+Shasums:
+
+```
+10d478f3a084bf5e705be3f232c41f3e3d56e57f  node-v0.8.3-x86.msi
+a6b9168eaa817692914d0de6c0d04702d7615681  node-v0.8.3.pkg
+f699d3788e242ed87a9037bae1aa0fa9335e45a9  node-v0.8.3.tar.gz
+60294792588e000d846a4c416617f127d5ba6163  node.exe
+efc7f597745bcf201a7996ecf9f9b94d9112b89f  node.exp
+4c5ea551d88fe21465f7d2e4c6f3d39ee02f2209  node.lib
+fd2c3873bed6872fd36e5906b65dfb4f1cec32fb  node.pdb
+64c6ec7db3f7f24e70ccecdada6f7b966c73134c  x64/node-v0.8.3-x64.msi
+94cd3f41004f1e9b8efd8d4a337b6154c1d5fee2  x64/node.exe
+a6ed8354a14577b9200c780b129e2b66f7b85e39  x64/node.exp
+3427a95bf9b14f56eec3f59aed80077fbde8f67f  x64/node.lib
+9af962968551daad044259641a615697f6588616  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.4.md b/locale/uk/blog/release/v0.8.4.md
new file mode 100755
index 0000000000000..43ca512b6c83a
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.4.md
@@ -0,0 +1,62 @@
+---
+category: release
+date: 2012-07-25T17:21:16.176Z
+version: 0.8.4
+title: Version 0.8.4 (Stable)
+slug: node-v0-8-4-stable
+layout: blog-post.hbs
+---
+
+2012.07.25, Version 0.8.4 (Stable)
+
+* V8: Upgrade to 3.11.10.17
+
+* npm: Upgrade to 1.1.45
+
+* net: fix Socket({ fd: 42 }) api (Ben Noordhuis)
+
+* readline: Remove event listeners on close (isaacs)
+
+* windows: correctly prep long path for fs.exists(Sync) (Bert Belder)
+
+* debugger: wake up the event loop when a debugger command is dispatched (Peter Rybin)
+
+* tls: verify server's identity (Fedor Indutny)
+
+* net: ignore socket.setTimeout(Infinity or NaN) (Fedor Indutny)
+
+
+Source Code: https://nodejs.org/dist/v0.8.4/node-v0.8.4.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.4/node-v0.8.4.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.4/node-v0.8.4-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.4/x64/node-v0.8.4-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.4/x64/
+
+Other release files: https://nodejs.org/dist/v0.8.4/
+
+Website: https://nodejs.org/docs/v0.8.4/
+
+Documentation: https://nodejs.org/docs/v0.8.4/api/
+
+Shasums:
+
+```
+387d7ac58d79dac301960510dfb7ee96fbf39072  node-v0.8.4-x86.msi
+66687da0ef190e8c07d5499ae3c408a6cca7ac30  node-v0.8.4.pkg
+8473e3dd48ab3734e2c92de0518cb80c2cdf750f  node-v0.8.4.tar.gz
+724ec6dc5e86805bfac79c8a702638c353850ea3  node.exe
+9bf483f72ad7884988d0678f7dc5bc000f4d21d2  node.exp
+3b7bd3915b62896e5c2f5701fd5d1c7fb53cdd27  node.lib
+9c3079ee727d471cef9fd91c7067d0a72349bfcb  node.pdb
+236a693074f2c69157e2918d1342a7850fc939ca  npm-1.1.45.tgz
+7126700cb321f688901e7773785eb88274906d50  npm-1.1.45.zip
+e9f414ba043f1daa5eee65506ef33c5377d87a09  x64/node-v0.8.4-x64.msi
+4cc86f21285b7f3d3cbd594ba604f06fb3434502  x64/node.exe
+6bf207a6b587bf1b01f18e9d0f2eefb528d82c2f  x64/node.exp
+e7b0d65992324b0688c61f6e534f3527e7e0b59f  x64/node.lib
+9a0072f528f9055531dee2bfa991882836b235de  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.5.md b/locale/uk/blog/release/v0.8.5.md
new file mode 100755
index 0000000000000..f7273038768be
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.5.md
@@ -0,0 +1,80 @@
+---
+version: 0.8.5
+title: Version 0.8.5 (stable)
+category: release
+slug: node-v0-8-5-stable
+date: 2012-08-02T22:00:45.000Z
+layout: blog-post.hbs
+---
+
+2012.08.02, Version 0.8.5 (Stable)
+
+* node: tag Encode and friends NODE_EXTERN (Ben Noordhuis)
+
+* fs: fix ReadStream / WriteStream missing callback (Gil Pedersen)
+
+* fs: fix readFileSync("/proc/cpuinfo") regression (Ben Noordhuis)
+
+* installer: don't assume bash is installed (Ben Noordhuis)
+
+* Report errors properly from --eval and stdin (isaacs)
+
+* assert: fix throws() throws an error without message property (koichik)
+
+* cluster: fix libuv assert in net.listen() (Ben Noordhuis)
+
+* build: always link sunos builds with libumem (Trent Mick)
+
+* build: improve armv7 / hard-float detection (Adam Malcontenti-Wilson)
+
+* https: Use host header as effective servername (isaacs)
+
+* sunos: work around OS bug to prevent fs.watch() from spinning (Bryan Cantrill)
+
+* linux: fix 'two watchers, one path' segfault (Ben Noordhuis)
+
+* windows: fix memory leaks in many fs functions (Bert Belder)
+
+* windows: don't allow directories to be opened for writing/appending (Bert Belder)
+
+* windows: make fork() work even when not all stdio handles are valid (Bert Belder)
+
+* windows: make unlink() not remove mount points, and improve performance (Bert Belder)
+
+* build: Sign pkg installer for OS X (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.8.5/node-v0.8.5.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.5/node-v0.8.5.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.5/node-v0.8.5-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.5/x64/node-v0.8.5-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.5/x64/
+
+Other release files: https://nodejs.org/dist/v0.8.5/
+
+Website: https://nodejs.org/docs/v0.8.5/
+
+Documentation: https://nodejs.org/docs/v0.8.5/api/
+
+Shasums:
+
+```
+74b470d04c3dac9f5838d4ed61e2fb50e394114a  node-v0.8.5-x86.msi
+28280575b717306b34440c83aace720dccc3047f  node-v0.8.5.pkg
+835ba5ca429e56f65aeb1a5d9730fff105e86337  node-v0.8.5.tar.gz
+c8ce66eefd6d75b44cdf29bb49aeffe4ea534b7f  node.exe
+d3832fb5a7a45d739c9d3faa7e13115bdaaa9cc7  node.exp
+5dee595f12dbfdee14b6e8aebc07a77ee96e5e45  node.lib
+ac62ec2d2508dfcd0c2f5cfcf725286ad876fb7a  node.pdb
+12876d80668b066b460833d096998525d8eceec7  npm-1.1.46.tgz
+4e820e5a99512e194ec30878ede08488211c8391  npm-1.1.46.zip
+95882b6aeab74725197b10d31ff4ee3a0723574c  x64/node-v0.8.5-x64.msi
+9d9c0652e57e05708b59bba78a55bc1237fcfb73  x64/node.exe
+f13f377c432c5a8fb4661abaae3a07c46ac74a66  x64/node.exp
+a17e3e8742ac084e1f7f99f721470e9d6182e75f  x64/node.lib
+4026170fed5a55fad6ee569daa9666cbb9d5ae3d  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.6.md b/locale/uk/blog/release/v0.8.6.md
new file mode 100755
index 0000000000000..37d3ee031b732
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.6.md
@@ -0,0 +1,88 @@
+---
+version: 0.8.6
+title: Version 0.8.6 (stable)
+category: release
+slug: node-v0-8-6-stable
+date: 2012-08-07T19:03:55.905Z
+layout: blog-post.hbs
+---
+
+2012.08.07, Version 0.8.6 (Stable)
+
+This is the first release to include binary distributions for all
+supported Unix operating systems (Linux, Darwin, and SunOS).  To use
+the binary distribution tarballs, you can unpack them directly into a
+destination directory:
+
+    cd ~/node/ # or /usr/local if you're feeling brave
+    tar xzvf /path/to/binary.tar.gz --strip=1
+
+This is an experimental feature.  Please use it and provide feedback.
+
+* npm: Upgrade to v1.1.48
+
+* Add 'make binary' to build binary tarballs for all Unixes (Nathan Rajlich)
+
+* zlib: Emit 'close' on destroy(). (Dominic Tarr)
+
+* child_process: Fix stdout=null when stdio=['pipe'] (Tyler Neylon)
+
+* installer: prevent ETXTBSY errors (Ben Noordhuis)
+
+* installer: honor --without-npm, default install path (Ben Noordhuis)
+
+* net: make pause work with connecting sockets (Bert Belder)
+
+* installer: fix cross-compile installs (Ben Noordhuis)
+
+* net: fix .listen({fd:0}) (Ben Noordhuis)
+
+* windows: map WSANO_DATA to UV_ENOENT (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.6/node-v0.8.6.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.6/node-v0.8.6.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.6/node-v0.8.6-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.6/x64/node-v0.8.6-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.6/x64/
+
+Linux 32-bit Binary Package: https://nodejs.org/dist/v0.8.6/node-v0.8.6-linux-x86.tar.gz
+
+Linux 64-bit Binary Package: https://nodejs.org/dist/v0.8.6/node-v0.8.6-linux-x64.tar.gz
+
+Solaris 32-bit Binary Package: https://nodejs.org/dist/v0.8.6/node-v0.8.6-sunos-x86.tar.gz
+
+Solaris 64-bit Binary Package: https://nodejs.org/dist/v0.8.6/node-v0.8.6-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.6/
+
+Website: https://nodejs.org/docs/v0.8.6/
+
+Documentation: https://nodejs.org/docs/v0.8.6/api/
+
+Shasums:
+
+```
+c23a57601150b3ec59aeeb0eef607d9e430e17c2  node-v0.8.6-darwin-x64.tar.gz
+8f7e4e837f61991eff4605678ab27c82e854bc38  node-v0.8.6-darwin-x86.tar.gz
+32ce9d28d6a294878ce9ee8f23b6fa7ecb3130e7  node-v0.8.6-linux-x64.tar.gz
+6f71518f044705ff1a7d9400a573906a99c5834c  node-v0.8.6-linux-x86.tar.gz
+ec9c02e9713a81d8f4848924cc38e5ed28a06fc4  node-v0.8.6-sunos-x64.tar.gz
+ac96cc4ce3eee4dc54ef7936ad4fd8eb04fbe359  node-v0.8.6-sunos-x86.tar.gz
+0a2aca229c9cb2ec4a4a82ff88de7ea0868d1890  node-v0.8.6-x86.msi
+84127d73a968f5951a9682b592a79779d1396c9e  node-v0.8.6.pkg
+34c7ad2bb5450653748c65840155852d67742258  node-v0.8.6.tar.gz
+42f3b792326efdfc9b0d95eebd7f9f716cadb1c0  node.exe
+fc56e816081ebef450ce7ed92bfd543d53191ac3  node.exp
+e91f1648e4e8f7586790443248326222101c286c  node.lib
+8106b33d1cdae69103ca07b16c7f5d690308d751  node.pdb
+6226474859e1cf2f1314d92b6207183bb36c6007  x64/node-v0.8.6-x64.msi
+3c1ac597956ea9f1e7eab62f85a23e3e436cd0e8  x64/node.exe
+599df091faecff536f52d17463c70e07cf9ed54f  x64/node.exp
+70bac4dcb9f845c8c8cb9443ff09f839fc86aac7  x64/node.lib
+eb59a0ed841c9e93c406b4c636b2048973cbfae4  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.7.md b/locale/uk/blog/release/v0.8.7.md
new file mode 100755
index 0000000000000..fe7f8bc13047f
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.7.md
@@ -0,0 +1,78 @@
+---
+version: 0.8.7
+title: Version 0.8.7 (stable)
+category: release
+slug: node-v0-8-7-stable
+date: 2012-08-15T23:23:16.131Z
+layout: blog-post.hbs
+---
+
+2012.08.15, Version 0.8.7 (Stable)
+
+* npm: Upgrade to 1.1.49
+
+* website: download page (Golo Roden)
+
+* crypto: fix uninitialized memory access in openssl (Ben Noordhuis)
+
+* buffer, crypto: fix buffer decoding (Ben Noordhuis)
+
+* build: compile with -fno-tree-vrp when gcc >= 4.0 (Ben Noordhuis)
+
+* tls: handle multiple CN fields when verifying cert (Ben Noordhuis)
+
+* doc: remove unused util from child_process (Kyle Robinson Young)
+
+* build: rework -fvisibility=hidden detection (Ben Noordhuis)
+
+* windows: don't duplicate invalid stdio handles (Bert Belder)
+
+* windows: fix typos in process-stdio.c (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.7/node-v0.8.7.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.7/node-v0.8.7.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.7/node-v0.8.7-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.7/x64/node-v0.8.7-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.7/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.7/node-v0.8.7-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.7/node-v0.8.7-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.7/node-v0.8.7-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.7/node-v0.8.7-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.7/
+
+Website: https://nodejs.org/docs/v0.8.7/
+
+Documentation: https://nodejs.org/docs/v0.8.7/api/
+
+Shasums:
+
+```
+3ff82e65a845a2d5f27ea57e8a1e29e6d10f5128  node-v0.8.7-darwin-x64.tar.gz
+d72ac02727aaefa094f8d06a0a124078da007df0  node-v0.8.7-darwin-x86.tar.gz
+0882e19157e98c3e2214e772e3ae714125863ae6  node-v0.8.7-linux-x64.tar.gz
+3e388d47f6e79acccfab117cceaeed19ceb1b14c  node-v0.8.7-linux-x86.tar.gz
+ffb81708df10d3c225d8f2ce57965a40db6ca556  node-v0.8.7-sunos-x64.tar.gz
+19df6ae999e4a5c1dada83b72516b3941eeb701e  node-v0.8.7-sunos-x86.tar.gz
+19f90a0cfa41c7eaf683393d46d06aecc2f99f84  node-v0.8.7-x86.msi
+0c2dcf2d5491be7b429681193a13c18de1ba488a  node-v0.8.7.pkg
+58ffb5884304e2f8415d8cee7921c42f66fc8d7b  node-v0.8.7.tar.gz
+ecaee480f0337e92870ca83aed1b49863b3f659d  node.exe
+ea2e25daad114692357383bfc8b4ac910fe02d99  node.exp
+70c8f054a5c42f6d4e3ca5154ca1a360f549d66f  node.lib
+180bcc036cd5deaef49bf12fddeeafc2e78152e3  node.pdb
+12ad712ff9e28eb1bdf7e508ce3a2b872ec37d4d  x64/node-v0.8.7-x64.msi
+c30607099ad4699b11e3ca37f94a9da196a36dc6  x64/node.exe
+f864ed339952604c2205e25927fb4851da5b79b6  x64/node.exp
+ce711929befe756f942a039213aeece2ef3edcc1  x64/node.lib
+11bb755b054bc6ee2e441758f7d42d131cf6d557  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.8.md b/locale/uk/blog/release/v0.8.8.md
new file mode 100755
index 0000000000000..53a5fefa68695
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.8.md
@@ -0,0 +1,80 @@
+---
+version: 0.8.8
+title: Version 0.8.8 (stable)
+category: release
+slug: node-v0-8-8-stable
+date: 2012-08-22T19:50:38.833Z
+layout: blog-post.hbs
+---
+
+2012.08.22, Version 0.8.8 (Stable)
+
+* V8: upgrade to 3.11.10.19
+
+* npm: upgrade to 1.1.59
+
+* windows: fix uninitialized memory access in uv_update_time() (Bert Belder)
+
+* unix, windows: fix memory corruption in fs-poll.c (Ben Noordhuis)
+
+* unix: fix integer overflow in uv_hrtime (Tim Holy)
+
+* sunos: fix uv_cpu_info() on x86_64 (Ben Noordhuis)
+
+* tls: update default cipher list (Ben Noordhuis)
+
+* unix: Fix llvm and older gcc duplicate symbol warnings (Bert Belder)
+
+* fs: fix use after free in stat watcher (Ben Noordhuis)
+
+* build: Fix using manually compiled gcc on OS X (Nathan Rajlich)
+
+* windows: make junctions work again (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.8.8/node-v0.8.8.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.8/node-v0.8.8.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.8/node-v0.8.8-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.8/x64/node-v0.8.8-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.8/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.8/node-v0.8.8-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.8/node-v0.8.8-linux-x64.tar.gz
+
+SunOS 32-bit Binary: https://nodejs.org/dist/v0.8.8/node-v0.8.8-sunos-x86.tar.gz
+
+SunOS 64-bit Binary: https://nodejs.org/dist/v0.8.8/node-v0.8.8-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.8/
+
+Website: https://nodejs.org/docs/v0.8.8/
+
+Documentation: https://nodejs.org/docs/v0.8.8/api/
+
+Shasums:
+
+```
+ecf54d3aad371621446ee0432f7c182a4494a1a3  node-v0.8.8-darwin-x64.tar.gz
+d1aca7c797fd262e2f0c601fe5cc3815622ce801  node-v0.8.8-darwin-x86.tar.gz
+603c36611c54651c149a26dc5bc6f833b0b846d0  node-v0.8.8-linux-x64.tar.gz
+30c66fc26845b14ef99d3e043bb4dfcba605bd45  node-v0.8.8-linux-x86.tar.gz
+cd0d46d232d882dd4afe955bd8acd6c435c2f5fe  node-v0.8.8-sunos-x64.tar.gz
+857facbd156d4f7a49b9e1c5610b4a1f893bf534  node-v0.8.8-sunos-x86.tar.gz
+bb08591a6f973f3699085abb50f6bdc9586f01f9  node-v0.8.8-x86.msi
+14239f6f379953405ca914b129c19b379718ba64  node-v0.8.8.pkg
+5ddafc059d2f774e35e6375f5b61157879a46f0f  node-v0.8.8.tar.gz
+6cc8a0a363c1efa184f6b72970a5d1182b5b44aa  node.exe
+395c73c055886e2e981b46f3c363837613456d82  node.exp
+ca8a9560b3da13ecddbbc2fb15c1b3ab85d7371b  node.lib
+b8e0e35b0ecc7c3514ad8ca4549c57dd8a221be4  node.pdb
+b604a56a236f632cdf55c366a882d3ecb2312fba  x64/node-v0.8.8-x64.msi
+e80c1f4791e80243c5ddc7ea1e92ebd58fc4e10f  x64/node.exe
+8baf5b459e7f2074e0237d40c8c80e89b47660a3  x64/node.exp
+4448fc2bfef66b7334016c0ab2e118c1cbc8544c  x64/node.lib
+0ddddf2c2fcd746827863b2454ddb4a8f6c3844e  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.8.9.md b/locale/uk/blog/release/v0.8.9.md
new file mode 100755
index 0000000000000..3d0135065770f
--- /dev/null
+++ b/locale/uk/blog/release/v0.8.9.md
@@ -0,0 +1,100 @@
+---
+date: 2012-09-11T18:50:17.000Z
+category: release
+version: 0.8.9
+title: Version 0.8.9 (Stable)
+slug: node-v0-8-9-stable
+layout: blog-post.hbs
+---
+
+2012.09.11, Version 0.8.9 (Stable)
+
+* v8: upgrade to 3.11.10.22
+
+* GYP: upgrade to r1477
+
+* npm: Upgrade to 1.1.61
+
+* npm: Don't create world-writable files (isaacs)
+
+* windows: fix single-accept mode for shared server sockets (Bert Belder)
+
+* windows: fix uninitialized memory access in uv_update_time() (Bert Belder)
+
+* windows: don't throw when a signal handler is attached (Bert Belder)
+
+* unix: fix memory leak in udp (Ben Noordhuis)
+
+* unix: map errno ESPIPE (Ben Noordhuis)
+
+* unix, windows: fix memory corruption in fs-poll.c (Ben Noordhuis)
+
+* sunos: fix os.cpus() on x86_64 (Ben Noordhuis)
+
+* child process: fix processes with IPC channel don't emit 'close' (Bert Belder)
+
+* build: add a "--dest-os" option to force a gyp "flavor" (Nathan Rajlich)
+
+* build: set `process.platform` to "sunos" on SunOS (Nathan Rajlich)
+
+* build: fix `make -j` fails after `make clean` (Bearice Ren)
+
+* build: fix openssl configuration for "arm" builds (Nathan Rajlich)
+
+* tls: support unix domain socket/named pipe in tls.connect (Shigeki Ohtsu)
+
+* https: make https.get() accept a URL (koichik)
+
+* http: respect HTTP/1.0 TE header (Ben Noordhuis)
+
+* crypto, tls: Domainify setSNICallback, pbkdf2, randomBytes (Ben Noordhuis)
+
+* stream.pipe: Don't call destroy() unless it's a function (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.8.9/node-v0.8.9.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.8.9/node-v0.8.9.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.8.9/node-v0.8.9-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.8.9/x64/node-v0.8.9-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.8.9/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.8.9/node-v0.8.9-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.8.9/node-v0.8.9-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.8.9/node-v0.8.9-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.8.9/node-v0.8.9-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.8.9/
+
+Website: https://nodejs.org/docs/v0.8.9/
+
+Documentation: https://nodejs.org/docs/v0.8.9/api/
+
+Shasums:
+
+```
+68aa7341807fb114f334151b7a1c8859e96b83d4  node-v0.8.9-darwin-x64.tar.gz
+9e4a9422c1fd71750e9c46235d58aedaac3ba002  node-v0.8.9-darwin-x86.tar.gz
+6236f781632555abf69d77f4bdfeb1e4e83779f3  node-v0.8.9-linux-x64.tar.gz
+7f46084541d4909f44cfef2bb95f1e4f7435629e  node-v0.8.9-linux-x86.tar.gz
+33b0fe68f63519f3c8e6dc4d2aa51c96f62d2a56  node-v0.8.9-sunos-x64.tar.gz
+e05863cb3a7d4add340ad434228f57da04a03b3d  node-v0.8.9-sunos-x86.tar.gz
+104f325d5289c51c6eb6a0634691dcdb39abb1db  node-v0.8.9-x86.msi
+1dd2cf48fb9b1f3e11e6e6750084ad4b2a2b0a85  node-v0.8.9.pkg
+2d3234adceedc2dc87284af88609ede6ecd71734  node-v0.8.9.tar.gz
+2997e2075cd04cf693453ce5664fa37615faa9a7  node.exe
+d2834bd8ed3569b7880211dfe31a4f21cd475ab8  node.exp
+41eac45ae350324de321a85787897bd8aa6b371c  node.lib
+ab6666144b23b2594521d27a95fb36b0904d48a2  node.pdb
+f29db0a61a7bb32a7198ab059eca25b1283b9d6d  x64/node-v0.8.9-x64.msi
+2a7e69cef1bf7bc88109e007406e6feeaaa007b2  x64/node.exe
+0423cd6602684c24e65358b9caa51740af67677b  x64/node.exp
+92155062a70100bfb5cf1389dd93e8851e7f3d0b  x64/node.lib
+cbbee351b84d7da0a91f56d6bbf6805e7b85cc8f  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.0.md b/locale/uk/blog/release/v0.9.0.md
new file mode 100755
index 0000000000000..22f2422607028
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.0.md
@@ -0,0 +1,64 @@
+---
+category: release
+version: 0.9.0
+date: 2012-07-20T18:37:15.000Z
+title: Version 0.9.0 (Unstable)
+slug: version-0-9-0-unstable
+layout: blog-post.hbs
+---
+
+2012.07.20, Version 0.9.0 (Unstable)
+
+* punycode: update to v1.1.1 (Mathias Bynens)
+
+* c-ares: upgrade to 1.9.0 (Saúl Ibarra Corretgé)
+
+* dns: ignore rogue DNS servers reported by windows (Saúl Ibarra Corretgé)
+
+* unix: speed up uv_async_send() (Ben Noordhuis)
+
+* darwin: get cpu model correctly on mac (Xidorn Quan)
+
+* nextTick: Handle tick callbacks before any other I/O (isaacs)
+
+* Enable color customization of `util.inspect` (Pavel Lang)
+
+* tls: Speed and memory improvements (Fedor Indutny)
+
+* readline: Use one history item for reentered line (Vladimir Beloborodov)
+
+* Fix #3521 Make process.env more like a regular Object (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.9.0/node-v0.9.0.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.0/node-v0.9.0.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.0/node-v0.9.0-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.0/x64/node-v0.9.0-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.0/x64/
+
+Other release files: https://nodejs.org/dist/v0.9.0/
+
+Website: https://nodejs.org/docs/v0.9.0/
+
+Documentation: https://nodejs.org/docs/v0.9.0/api/
+
+Shasums:
+
+```
+4d6881934f5e41da651b478f914f71543d21d3cc  node-v0.9.0-x86.msi
+ec00cc6f0830f64cd9e8246a299abf9a2a6ed73e  node-v0.9.0.pkg
+912d0eb3139b8f6f99199dae5ec1ecb300ed9c9b  node-v0.9.0.tar.gz
+7e56dddbb1d3e243549db7182f1bf2dd4518eaae  node.exe
+31718ad3e0de9b0ea6c207966a13d4bafaf9ef64  node.exp
+0738b4d91de4c87cdee2547d83144668cb232c24  node.lib
+baca86ec3c12a5261abb940cd8107bdeb40713cc  node.pdb
+cf3892596a7d2a27a63672b537b06b8828125fe9  x64/node-v0.9.0-x64.msi
+cad4bf9b2be85476d1a897ea17b3f927ec49c96a  x64/node.exe
+29ea3654f7728efef6fa046943ded57af42b91f3  x64/node.exp
+1dfa57b111d5942b4fe701b625176eae73c82d82  x64/node.lib
+9093b2120f8adf0236f965982e4a32697af2af5d  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.1.md b/locale/uk/blog/release/v0.9.1.md
new file mode 100755
index 0000000000000..928d63729df0d
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.1.md
@@ -0,0 +1,119 @@
+---
+version: 0.9.1
+title: Version 0.9.1 (Unstable)
+category: release
+slug: node-v0-9-1-unstable
+date: 2012-08-28T22:33:45.659Z
+layout: blog-post.hbs
+---
+
+2012.08.28, Version 0.9.1 (Unstable)
+
+* buffer: Add Buffer.isEncoding(enc) to test for valid encoding values (isaacs)
+
+* Raise UV_ECANCELED on premature close. (Ben Noordhuis)
+
+* Remove c-ares from libuv, move to a top-level node dependency (Bert Belder)
+
+* ref/unref for all HandleWraps, timers, servers, and sockets (Timothy J Fontaine)
+
+* addon: remove node-waf, superseded by node-gyp (Ben Noordhuis)
+
+* child_process: emit error on exec failure (Ben Noordhuis)
+
+* cluster: do not use internal server API (Andreas Madsen)
+
+* constants: add O_DIRECT (Ian Babrou)
+
+* crypto: add sync interface to crypto.pbkdf2() (Ben Noordhuis)
+
+* darwin: emulate fdatasync() (Fedor Indutny)
+
+* dgram: make .bind() always asynchronous (Ben Noordhuis)
+
+* events: Make emitter.listeners() side-effect free (isaacs, Joe Andaverde)
+
+* fs: Throw early on invalid encoding args (isaacs)
+
+* fs: fix naming of truncate/ftruncate functions (isaacs)
+
+* http: bubble up parser errors to ClientRequest (Brian White)
+
+* linux: improve cpuinfo parser on ARM and MIPS (Ben Noordhuis)
+
+* net: add support for IPv6 addresses ending in :: (Josh Erickson)
+
+* net: support Server.listen(Pipe) (Andreas Madsen)
+
+* node: don't scan add-on for "init" symbol (Ben Noordhuis)
+
+* remove process.uvCounters() (Ben Noordhuis)
+
+* repl: console writes to repl rather than process stdio (Nathan Rajlich)
+
+* timers: implement setImmediate (Timothy J Fontaine)
+
+* tls: fix segfault in pummel/test-tls-ci-reneg-attack (Ben Noordhuis)
+
+* tools: Move gyp addon tools to node-gyp (Nathan Rajlich)
+
+* unix: preliminary signal handler support (Ben Noordhuis)
+
+* unix: remove dependency on ev_child (Ben Noordhuis)
+
+* unix: work around darwin bug, don't poll() on pipe (Fedor Indutny)
+
+* util: Formally deprecate util.pump() (Ben Noordhuis)
+
+* windows: make active and closing handle state independent (Bert Belder)
+
+* windows: report spawn errors to the exit callback (Bert Belder)
+
+* windows: signal handling support with uv_signal_t (Bert Belder)
+
+
+Source Code: https://nodejs.org/dist/v0.9.1/node-v0.9.1.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.1/node-v0.9.1.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.1/node-v0.9.1-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.1/x64/node-v0.9.1-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.1/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.1/node-v0.9.1-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.1/node-v0.9.1-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.1/node-v0.9.1-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.1/node-v0.9.1-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.1/
+
+Website: https://nodejs.org/docs/v0.9.1/
+
+Documentation: https://nodejs.org/docs/v0.9.1/api/
+
+Shasums:
+
+```
+b86a5b0b2c9a89d08baaeb3d5270a8f247b4ba43  node-v0.9.1-darwin-x64.tar.gz
+800af9d15a4b65e624351bb94dedc3b7eb322b86  node-v0.9.1-darwin-x86.tar.gz
+a7ea43b0db472ca84dc9838960dae57ff0abaa72  node-v0.9.1-linux-x64.tar.gz
+89c4be492a946eefa45aa87d16787875aa0f2dff  node-v0.9.1-linux-x86.tar.gz
+6495d2814541e945dba5941b8d3facf2a61dc55d  node-v0.9.1-sunos-x64.tar.gz
+05ea83ba4d648f5b949833bb28d69e6eeebabb78  node-v0.9.1-sunos-x86.tar.gz
+3ccf1ac2fea7f2d05bcaed590bc54ee61c982fbb  node-v0.9.1-x86.msi
+bd0ede40e4681b16088284fe6a18ae3a5c5a3795  node-v0.9.1.tar.gz
+159470a999ef23fa940ad3c54265053c3d2a4332  node.exe
+02472e388a44b91e2644178a0fe011354fcd361e  node.exp
+c6d6ce22be4b47ad022d82dd91ebd4c040742fee  node.lib
+7b4cec8b4106d90a077388fe483fdbb13119dcb1  node.pdb
+a5fbf5e22c7623a9206abc6608d084ff53c7c4c9  x64/node-v0.9.1-x64.msi
+9755685a9d7bea6dc63d3260829c26c5b0430a7a  x64/node.exe
+621f177733647848f7f667926fe4f498a1f50c97  x64/node.exp
+5877dffbf012c458dab88f3392af59cb33720d2f  x64/node.lib
+dc513ce5c16771dcfab9c1777d5949252290b412  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.10.md b/locale/uk/blog/release/v0.9.10.md
new file mode 100755
index 0000000000000..faf6f6d7349ac
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.10.md
@@ -0,0 +1,87 @@
+---
+category: release
+date: 2013-02-19T22:00:08.000Z
+slug: node-v0-9-10-unstable
+title: Node v0.9.10 (Unstable)
+version: 0.9.10
+layout: blog-post.hbs
+---
+
+2013.02.19, Version 0.9.10 (Unstable)
+
+* V8: Upgrade to 3.15.11.15
+
+* npm: Upgrade to 1.2.12
+
+* fs: Change default WriteStream config, increase perf (isaacs)
+
+* process: streamlining tick callback logic (Trevor Norris)
+
+* stream_wrap, udp_wrap: add read-only fd property (Ben Noordhuis)
+
+* buffer: accept negative indices in Buffer#slice() (Ben Noordhuis)
+
+* tls: Cycle data when underlying socket drains (isaacs)
+
+* stream: read(0) should not always trigger _read(n,cb) (isaacs)
+
+* stream: Empty strings/buffers do not signal EOF any longer (isaacs)
+
+* crypto: improve cipher/decipher error messages (Ben Noordhuis)
+
+* net: Respect the 'readable' flag on sockets (isaacs)
+
+* net: don't suppress ECONNRESET (Ben Noordhuis)
+
+* typed arrays: copy Buffer in typed array constructor (Ben Noordhuis)
+
+* typed arrays: make DataView throw on non-ArrayBuffer (Ben Noordhuis)
+
+* windows: MSI installer enhancements (Scott Blomquist, Jim Schubert)
+
+
+Source Code: https://nodejs.org/dist/v0.9.10/node-v0.9.10.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.10/node-v0.9.10.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.10/node-v0.9.10-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.10/x64/node-v0.9.10-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.10/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.10/node-v0.9.10-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.10/node-v0.9.10-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.10/node-v0.9.10-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.10/node-v0.9.10-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.10/
+
+Website: https://nodejs.org/docs/v0.9.10/
+
+Documentation: https://nodejs.org/docs/v0.9.10/api/
+
+Shasums:
+```
+813d5f42b156b7d64f00b86e13d26ada3ef352e5  node-v0.9.10-darwin-x64.tar.gz
+99dbe66fd0fc176fb3459ffcf62212dcb27bef10  node-v0.9.10-darwin-x86.tar.gz
+3a5a465238cbdbdac9786c204fd27be61ce7159a  node-v0.9.10-linux-x64.tar.gz
+3340ac206ec1a1f827c954efdfa1351dcfe9f419  node-v0.9.10-linux-x86.tar.gz
+b920b2e57c6df1e080966fdeccbfd1b384b156d4  node-v0.9.10-sunos-x64.tar.gz
+9c1744352bb1bc71f48f8aea1aff6aeefe35a394  node-v0.9.10-sunos-x86.tar.gz
+f1daaafc330cc9993a3a6f7ca8b9cc870b49e75c  node-v0.9.10-x86.msi
+2b6c70f57c1513e8f5151785b1ac263565983918  node-v0.9.10.pkg
+265542c15cf939b7c71a545758d835ed44d791d3  node-v0.9.10.tar.gz
+653f24d53f411217d57ed18d73921ff4721f00dd  node.exe
+7d62da67a7b33628d7d90c9d5037cf564dfc5ce4  node.exp
+cfebbcd81db602b2f051328a9924e19ca2cb6235  node.lib
+a31694cb9e03d13a616f3cc634852d8dc98e69b8  node.pdb
+5f94c1cc9301a8b85082fee7549aa376aedd8ec5  x64/node-v0.9.10-x64.msi
+7716c01ce60f7c65100cc405726badf8476afebd  x64/node.exe
+121d4a721968ba4631d29de07e5d6c326d259b4b  x64/node.exp
+17f651000f6b0c840efe539ae5257cb894481c49  x64/node.lib
+d04242a5ec3a3104931ec8de6a846a8f7746b1fd  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.11.md b/locale/uk/blog/release/v0.9.11.md
new file mode 100755
index 0000000000000..43e12fa538e5f
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.11.md
@@ -0,0 +1,91 @@
+---
+date: 2013-03-01T19:17:40.000Z
+version: 0.9.11
+category: release
+title: Node v0.9.11 (Unstable)
+slug: node-v0-9-11-unstable
+layout: blog-post.hbs
+---
+
+2013.03.01, Version 0.9.11 (Unstable)
+
+* V8: downgrade 3.14.5
+
+* openssl: update to 1.0.1e
+
+* darwin: Make process.title work properly (Ben Noordhuis)
+
+* fs: Support mode/flag options to read/append/writeFile (isaacs)
+
+* stream: _read() no longer takes a callback (isaacs)
+
+* stream: Add stream.unshift(chunk) (isaacs)
+
+* stream: remove lowWaterMark feature (isaacs)
+
+* net: omit superfluous 'connect' event (Ben Noordhuis)
+
+* build, windows: disable SEH (Ben Noordhuis)
+
+* core: remove errno global (Ben Noordhuis)
+
+* core: Remove the nextTick for running the main file (isaacs)
+
+* core: Mark exit() calls with status codes (isaacs)
+
+* core: Fix debug signal handler race condition lock (isaacs)
+
+* crypto: clear error stack (Ben Noordhuis)
+
+* test: optionally set common.PORT via env variable (Timothy J Fontaine)
+
+* path: Throw TypeError on non-string args to path.resolve/join (isaacs, Arianit Uka)
+
+* crypto: fix uninitialized memory access in openssl (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.9.11/node-v0.9.11.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.11/node-v0.9.11.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.11/node-v0.9.11-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.11/x64/node-v0.9.11-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.11/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.11/node-v0.9.11-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.11/node-v0.9.11-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.11/node-v0.9.11-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.11/node-v0.9.11-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.11/
+
+Website: https://nodejs.org/docs/v0.9.11/
+
+Documentation: https://nodejs.org/docs/v0.9.11/api/
+
+Shasums:
+```
+2e11c53449523642f1b3f2cad9726d032ebf0a1b  node-v0.9.11-darwin-x64.tar.gz
+6a8c18185d67ff50979a143b9e100d56b35aedde  node-v0.9.11-darwin-x86.tar.gz
+16a95dfc6974ba3562801d9f7bb9e2fa0c001d32  node-v0.9.11-linux-x64.tar.gz
+4711aae106edf9a2bf9f644b08db1b608e9829c1  node-v0.9.11-linux-x86.tar.gz
+897c21d0fc59faebbdf515e0dfee27551386c4af  node-v0.9.11-sunos-x64.tar.gz
+09c2b469ef984237bbd606d78f523d1c8b92e680  node-v0.9.11-sunos-x86.tar.gz
+81627efd5c591f636147100e2e95bbbb17fd0290  node-v0.9.11-x86.msi
+a0e91028c7fd091db1667ccf9dba6216ee321e98  node-v0.9.11.pkg
+66370601eb824305b12c7f3e5b2a5e8ca94f1209  node-v0.9.11.tar.gz
+db08f56a8258dd8a6a525595a023ad9eb72603e6  node.exe
+759fe57cbceeee5820c7de176b6ef8c2a5af7fab  node.exp
+299f0f8aebbc755b37fc6b40e463cb455a5bb1c6  node.lib
+f12b3dc557ae16834ae3a793d768e251d1ba5db3  node.pdb
+807520a39d6f7518e53da796fa1ca62316219146  x64/node-v0.9.11-x64.msi
+e27a6adc077629ae9a367b4a5cb7fb31853863d3  x64/node.exe
+fdcf8ccea3b2c5e3f4f99fa606715e1e27a96acc  x64/node.exp
+fa0db53aac8d97bab3566c7d80fceb8e148c6d0d  x64/node.lib
+e24cf62376b8439ae40b84d37c55ab23fbad4e47  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.12.md b/locale/uk/blog/release/v0.9.12.md
new file mode 100755
index 0000000000000..30453b98313fb
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.12.md
@@ -0,0 +1,110 @@
+---
+date: 2013-03-06T21:51:00.000Z
+version: 0.9.12
+category: release
+title: Node v0.9.12 (Unstable)
+slug: node-v0-9-12-unstable
+layout: blog-post.hbs
+---
+
+As of this release, Node v0.9 is finally performing faster than v0.8
+on HTTP, file system, and TLS benchmarks.
+
+Unless there are serious problems found, v0.10.0 will be released on
+Monday, 2013.03.11, along with more details about the benchmark
+results and the plans for what comes next.
+
+Please consider this a v0.10 Release Candidate.  Use it in your
+programs.  It is as stable as 0.9 is going to get.
+
+----
+
+2013.03.06, Version 0.9.12 (Unstable)
+
+* stream: Allow strings in Readable.push/unshift (isaacs)
+
+* stream: Remove bufferSize option (isaacs)
+
+* stream: Increase highWaterMark on large reads (isaacs)
+
+* stream: _write: takes an encoding argument (isaacs)
+
+* stream: _transform: remove output() method, provide encoding (isaacs)
+
+* stream: Don't require read(0) to emit 'readable' event (isaacs)
+
+* node: Add --throw-deprecation (isaacs)
+
+* http: fix multiple timeout events (Eugene Girshov)
+
+* http: More useful setTimeout API on server (isaacs)
+
+* net: use close callback, not process.nextTick (Ben Noordhuis)
+
+* net: Provide better error when writing after FIN (isaacs)
+
+* dns: Support NAPTR queries (Pavel Lang)
+
+* dns: fix ReferenceError in resolve() error path (Xidorn Quan)
+
+* child_process: handle ENOENT correctly on Windows (Scott Blomquist)
+
+* cluster: Rename destroy() to kill(signal=SIGTERM) (isaacs)
+
+* build: define nightly tag external to build system (Timothy J Fontaine)
+
+* build: make msi build work when spaces are present in the path (Bert Belder)
+
+* build: fix msi build issue with WiX 3.7/3.8 (Raymond Feng)
+
+* repl: make compatible with domains (Dave Olszewski)
+
+* events: Code cleanup and performance improvements (Trevor Norris)
+
+
+Source Code: https://nodejs.org/dist/v0.9.12/node-v0.9.12.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.12/node-v0.9.12.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.12/node-v0.9.12-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.12/x64/node-v0.9.12-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.12/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.12/node-v0.9.12-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.12/node-v0.9.12-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.12/node-v0.9.12-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.12/node-v0.9.12-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.12/
+
+Website: https://nodejs.org/docs/v0.9.12/
+
+Documentation: https://nodejs.org/docs/v0.9.12/api/
+
+Shasums:
+
+```
+caa171a35f7eb36fd585f4e16dbf1c60f9d056af  node-v0.9.12-darwin-x64.tar.gz
+ffd98e60cdb630c4239c3d94e89b5ba84fb8d234  node-v0.9.12-darwin-x86.tar.gz
+85c008721b33872085c3af6253b6e92a6587a467  node-v0.9.12-linux-x64.tar.gz
+cc3d50b8ba0474f1907959aae5dfa5e64801bc6b  node-v0.9.12-linux-x86.tar.gz
+bcedc7c18f9984ea8873752672a09622e56008e1  node-v0.9.12-sunos-x64.tar.gz
+4a7e2baf41fc994044c204a9c90eb894b60ee4c3  node-v0.9.12-sunos-x86.tar.gz
+0f7c4f600768736c0e7107e7da33a748a4e2d61e  node-v0.9.12-x86.msi
+a9e610225a6cad24923a7242eba97ab1577f3886  node-v0.9.12.pkg
+2353d3e5c6518f75202b74236fa9d8eeecd26ca3  node-v0.9.12.tar.gz
+9be76f46fbfc66a84fbd02210b6422f14d5dd7eb  node.exe
+1f528fdf910036bb791fc6031e2dc9aff300f7eb  node.exp
+6aec59165f64fea2e89b6ec4ddbf55ab630b318f  node.lib
+fd575f13dc714fdeb64f814e67db9ef5d142e7f8  node.pdb
+442dae32457159a579eb44da12c7c5f182c1ae4c  x64/node-v0.9.12-x64.msi
+8dc7f6fec9172a5e606ca1b6b3520178313caa29  x64/node.exe
+f441fb3807930ee658a105db97ec61a2b5e331d4  x64/node.exp
+f8b3880e5fa00151343bf0000f324ea9e96155a7  x64/node.lib
+7adb54566301d39866e93506ffc9391870f9c644  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.2.md b/locale/uk/blog/release/v0.9.2.md
new file mode 100755
index 0000000000000..32d9d7f35e8a0
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.2.md
@@ -0,0 +1,98 @@
+---
+title: Version 0.9.2 (Unstable)
+category: release
+version: 0.9.2
+date: 2012-09-18T01:25:53.000Z
+slug: node-v0-9-2-unstable
+layout: blog-post.hbs
+---
+
+2012.09.17, Version 0.9.2 (Unstable)
+
+* http_parser: upgrade to ad3b631
+
+* openssl: upgrade 1.0.1c
+
+* darwin: use FSEvents to watch directory changes (Fedor Indutny)
+
+* unix: support missing API on NetBSD (Shigeki Ohtsu)
+
+* unix: fix EMFILE busy loop (Ben Noordhuis)
+
+* windows: un-break writable tty handles (Bert Belder)
+
+* windows: map WSAESHUTDOWN to UV_EPIPE (Bert Belder)
+
+* windows: make spawn with custom environment work again (Bert Belder)
+
+* windows: map ERROR_DIRECTORY to UV_ENOENT (Bert Belder)
+
+* tls, https: validate server certificate by default (Ben Noordhuis)
+
+* tls, https: throw exception on missing key/cert (Ben Noordhuis)
+
+* tls: async session storage (Fedor Indutny)
+
+* installer: don't install header files (Ben Noordhuis)
+
+* buffer: implement Buffer.prototype.toJSON() (Nathan Rajlich)
+
+* buffer: added support for writing NaN and Infinity (koichik)
+
+* http: make http.ServerResponse emit 'end' (Ben Noordhuis)
+
+* build: ./configure --ninja (Ben Noordhuis, Timothy J Fontaine)
+
+* installer: fix --without-npm (Ben Noordhuis)
+
+* cli: make -p equivalent to -pe (Ben Noordhuis)
+
+* url: Go much faster by using Url class (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.9.2/node-v0.9.2.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.2/node-v0.9.2.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.2/node-v0.9.2-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.2/x64/node-v0.9.2-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.2/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.2/node-v0.9.2-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.2/node-v0.9.2-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.2/node-v0.9.2-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.2/node-v0.9.2-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.2/
+
+Website: https://nodejs.org/docs/v0.9.2/
+
+Documentation: https://nodejs.org/docs/v0.9.2/api/
+
+Shasums:
+
+```
+3d1bb82013cbefd199abedaf0fe91d18579939b5  node-v0.9.2-darwin-x64.tar.gz
+0a8e43e13ae6ce13ee3c8bb281d9a26aacc3ba3c  node-v0.9.2-darwin-x86.tar.gz
+c5c2708d796d0e37c5a401af39bfa17c9c3b67c0  node-v0.9.2-linux-x64.tar.gz
+0d0a09b34b74f2c9f310f044cd142d0b80885c22  node-v0.9.2-linux-x86.tar.gz
+0bcc9a23e601cd8bef42a2e250d918ccb03b3f5b  node-v0.9.2-sunos-x64.tar.gz
+7827998ec5ca442f26f824f46b51f33d0c9bbbb7  node-v0.9.2-sunos-x86.tar.gz
+ed1c7d8a966c786969e3b4f68081cc5b3c753a03  node-v0.9.2-x86.msi
+e1a1270d3f2a398738a363c68e8f30fd47dd5eb6  node-v0.9.2.pkg
+09dd5e2135ab67ee9544f2b6ce0c5ab0e95b02b8  node-v0.9.2.tar.gz
+8bfd33550b0115f71aed15a0c114a13cd573e10b  node.exe
+3484b1c61442bd2ca7e00d06c61ad7fa6f61acad  node.exp
+37dcaa77234b63a3ce3cecdea27041b7565698cc  node.lib
+52abfb1b09f6facb0cda7c2e27b1bb48f8e75404  node.pdb
+c4c3f87c5dd7a0d36d682fb449cc6a8a245a4789  x64/node-v0.9.2-x64.msi
+d60fb389deada9eb753948bedb84b2f797424a93  x64/node.exe
+04190c31210b2bc7ee80679167920567c166db75  x64/node.exp
+dfb5a231905da844279bf86984813440e152becf  x64/node.lib
+d5c5e26395e5c714efd4855505dcf0a31c57e22e  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.3.md b/locale/uk/blog/release/v0.9.3.md
new file mode 100755
index 0000000000000..a4774f785842a
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.3.md
@@ -0,0 +1,90 @@
+---
+category: release
+version: v0.9.3
+date: 2012-10-24T17:04:08.000Z
+slug: node-v0.9.3
+title: Node v0.9.3 (Unstable)
+layout: blog-post.hbs
+---
+
+2012.10.24, Version 0.9.3 (Unstable)
+
+* V8: Upgrade to 3.13.7.4
+
+* crypto: Default to buffers instead of binary strings (isaacs, Fedor Indutny)
+
+* crypto: add getHashes() and getCiphers() (Ben Noordhuis)
+
+* unix: add custom thread pool, remove libeio (Ben Noordhuis)
+
+* util: make `inspect()` accept an "options" argument (Nathan Rajlich)
+
+* https: fix renegotation attack protection (Ben Noordhuis)
+
+* cluster: make 'listening' handler see actual port (Aaditya Bhatia)
+
+* windows: use USERPROFILE to get the user's home dir (Bert Belder)
+
+* path: add platform specific path delimiter (Paul Serby)
+
+* http: add response.headersSent property (Pavel Lang)
+
+* child_process: make .fork()'d child auto-exit (Ben Noordhuis)
+
+* events: add 'removeListener' event (Ben Noordhuis)
+
+* string_decoder: Add 'end' method, do base64 properly (isaacs)
+
+* buffer: include encoding value in exception when invalid (Ricky Ng-Adam)
+
+* http: make http.ServerResponse no longer emit 'end' (isaacs)
+
+* streams: fix pipe is destructed by 'end' from destination (koichik)
+
+
+Source Code: https://nodejs.org/dist/v0.9.3/node-v0.9.3.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.3/node-v0.9.3.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.3/node-v0.9.3-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.3/x64/node-v0.9.3-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.3/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.3/node-v0.9.3-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.3/node-v0.9.3-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.3/node-v0.9.3-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.3/node-v0.9.3-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.3/
+
+Website: https://nodejs.org/docs/v0.9.3/
+
+Documentation: https://nodejs.org/docs/v0.9.3/api/
+
+Shasums:
+
+```
+188b3ffacdc4342dc3c34e7ea8374acc3e186df0  node-v0.9.3-darwin-x64.tar.gz
+94ae90f06a5bf72bb6efa8053c0beefde21f8bd7  node-v0.9.3-darwin-x86.tar.gz
+ccb065fe242f15ffe35ecd7b22db33d11d6a5951  node-v0.9.3-linux-x64.tar.gz
+0febfb1c37a3560b0140f7f952042aa4b4712974  node-v0.9.3-linux-x86.tar.gz
+4362fdfefa0ed2985045883cea51ab802555c24c  node-v0.9.3-sunos-x64.tar.gz
+f43b6ce2a5da3bb384f6c115826cd2fea5f4bc2c  node-v0.9.3-sunos-x86.tar.gz
+ff6a7f8ff1a6d1af299a2702e09eec2cdfef474a  node-v0.9.3-x86.msi
+d47f953ee97047e1202350db2b11fb880ce2809b  node-v0.9.3.pkg
+34b7406e1da49bf0f0967e5a084157fdf8735078  node-v0.9.3.tar.gz
+d0829f57b8460807cf58b2154b16176ef68189b1  node.exe
+76007380d1f5cefd772b5890cd64f409ba85893e  node.exp
+fbe95014f9f4e2c5a38bc67b75511683f4a17fa9  node.lib
+8c405af98ce922bf9bd82d29723aa343f3ca5488  node.pdb
+04c1dce1188f4c52adfda0bc8219c478ed6553a8  x64/node-v0.9.3-x64.msi
+fe6af3bd1405ecdef826a31a7c1333819aab4f3b  x64/node.exe
+abc9afb5ac40276346072f85601bd1a9e5135856  x64/node.exp
+41622dce275f0f0f740485cca8d86ba3e63c884e  x64/node.lib
+8c34040ba4aa916d13c8313514cf93f99f5e3e34  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.4.md b/locale/uk/blog/release/v0.9.4.md
new file mode 100755
index 0000000000000..2b8f961f3acf4
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.4.md
@@ -0,0 +1,100 @@
+---
+date: 2012-12-21T20:30:15.000Z
+version: 0.9.4
+category: release
+slug: node-v0-9-4-unstable
+title: Node v0.9.4 (Unstable)
+layout: blog-post.hbs
+---
+
+2012.12.21, Version 0.9.4 (Unstable)
+
+* streams: Update all streaming interfaces to use new classes (isaacs)
+
+* node: remove idle gc (Ben Noordhuis)
+
+* http: protect against response splitting attacks (Bert Belder)
+
+* fs: Raise error when null bytes detected in paths (isaacs)
+
+* fs: fix 'object is not a function' callback errors (Ben Noordhuis)
+
+* fs: add autoClose=true option to fs.createReadStream (Farid Neshat)
+
+* process: add getgroups(), setgroups(), initgroups() (Ben Noordhuis)
+
+* openssl: optimized asm code on x86 and x64 (Bert Belder)
+
+* crypto: fix leak in GetPeerCertificate (Fedor Indutny)
+
+* add systemtap support (Jan Wynholds)
+
+* windows: add ETW and PerfCounters support (Scott Blomquist)
+
+* windows: fix normalization of UNC paths (Bert Belder)
+
+* crypto: fix ssl error handling (Sergey Kholodilov)
+
+* node: remove eio-emul.h (Ben Noordhuis)
+
+* os: add os.endianness() function (Nathan Rajlich)
+
+* readline: don't emit "line" events with a trailing 'n' char (Nathan Rajlich)
+
+* build: add configure option to generate xcode build files (Timothy J Fontaine)
+
+* build: allow linking against system libuv, cares, http_parser (Stephen Gallagher)
+
+* typed arrays: add slice() support to ArrayBuffer (Anthony Pesch)
+
+* debugger: exit and kill child on SIGTERM or SIGHUP (Fedor Indutny)
+
+* url: url.format escapes delimiters in path and query (J. Lee Coltrane)
+
+
+Source Code: https://nodejs.org/dist/v0.9.4/node-v0.9.4.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.4/node-v0.9.4.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.4/node-v0.9.4-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.4/x64/node-v0.9.4-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.4/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.4/node-v0.9.4-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.4/node-v0.9.4-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.4/node-v0.9.4-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.4/node-v0.9.4-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.4/
+
+Website: https://nodejs.org/docs/v0.9.4/
+
+Documentation: https://nodejs.org/docs/v0.9.4/api/
+
+Shasums:
+
+```
+7919d5fa63583c9a38a8ade1e977809b53476f7f  node-v0.9.4-darwin-x64.tar.gz
+82eb2f39c61b14be8a9d2c1b6ba624030ab3ddbe  node-v0.9.4-darwin-x86.tar.gz
+34cd2f6bed15d4d7d28944575b7098f4500651e2  node-v0.9.4-linux-x64.tar.gz
+bf5da5432a5d80343e1d53c57b242283be11c97f  node-v0.9.4-linux-x86.tar.gz
+6eebcf27a545d598c0ffa8056d7d5c83add5746c  node-v0.9.4-sunos-x64.tar.gz
+1c2e28389b34a0e51f5ad2a1c09677f2941765b1  node-v0.9.4-sunos-x86.tar.gz
+4d7b4dfd150f17dac787400e74fc469b3432f3a2  node-v0.9.4-x86.msi
+20ceaafeb6d4ecf5d2f37d3d825d47cc81927dd6  node-v0.9.4.pkg
+30b3f8dee0b2ace3d83c200eeffc6f450d3b4366  node-v0.9.4.tar.gz
+a5b4304f4a50ac3385577f7833890ca6f44301c0  node.exe
+5b960053a6bddfd10cf6408ea1581b7237512248  node.exp
+f1aaac71a21e7a0c884211957e5d79bed1deb1d3  node.lib
+73016ab15ee7ee6f6363391d3e41a698ed764e65  node.pdb
+5a624fc9a5dac85a6f00945ccc2d31d9b8a51499  x64/node-v0.9.4-x64.msi
+fe738e969f9b050b7b1675ecf3cda567021e121b  x64/node.exe
+d32c7ea441ad0d24cd2fd2b4932d2924a95f25ec  x64/node.exp
+753f7fadc501a1b86d94af23710137f6e93c5cff  x64/node.lib
+a707ef46e6483f40a30c85c037eeadbf9e5923b8  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.5.md b/locale/uk/blog/release/v0.9.5.md
new file mode 100755
index 0000000000000..861bdd8bed6bf
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.5.md
@@ -0,0 +1,85 @@
+---
+category: release
+version: 0.9.5
+date: 2012-12-30T01:19:51.000Z
+slug: node-v0-9-5-unstable
+title: Node v0.9.5 (Unstable)
+layout: blog-post.hbs
+---
+
+2012.12.30, Version 0.9.5 (Unstable)
+
+* assert: improve support for new execution contexts (lukebayes)
+
+* domain: use camelCase instead of snake_case (isaacs)
+
+* domain: Do not use uncaughtException handler (isaacs)
+
+* fs: make 'end' work with ReadStream without 'start' (Ben Noordhuis)
+
+* https: optimize createConnection() (Ryunosuke SATO)
+
+* buffer: speed up base64 encoding by 20% (Ben Noordhuis)
+
+* doc: Colorize API stabilitity index headers in docs (Luke Arduini)
+
+* net: socket.readyState corrections (bentaber)
+
+* http: Performance enhancements for http under streams2 (isaacs)
+
+* stream: fix to emit end event on http.ClientResponse (Shigeki Ohtsu)
+
+* stream: fix event handler leak in readstream pipe and unpipe (Andreas Madsen)
+
+* build: Support ./configure --tag switch (Maciej Małecki)
+
+* repl: don't touch `require.cache` (Nathan Rajlich)
+
+* node: Emit 'exit' event when exiting for an uncaught exception (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.9.5/node-v0.9.5.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.5/node-v0.9.5.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.5/node-v0.9.5-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.5/x64/node-v0.9.5-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.5/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.5/node-v0.9.5-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.5/node-v0.9.5-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.5/node-v0.9.5-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.5/node-v0.9.5-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.5/
+
+Website: https://nodejs.org/docs/v0.9.5/
+
+Documentation: https://nodejs.org/docs/v0.9.5/api/
+
+Shasums:
+
+```
+d44535e086c3f0fe47152b9323189c18a488d995  node-v0.9.5-darwin-x64.tar.gz
+b588332e38e3ddd0424b18d14a3c6c65c5cad6f6  node-v0.9.5-darwin-x86.tar.gz
+17b07641b59bc56582e68db6bd52c1b41bb06a5e  node-v0.9.5-linux-x64.tar.gz
+89656e3dc094a6fa4244a03ac85e9b08b7443a50  node-v0.9.5-linux-x86.tar.gz
+bf84b80ea80b4cb20767d4b3f276979f0f3d8866  node-v0.9.5-sunos-x64.tar.gz
+4f98560e55db63f323b6f75b22538d96b199892c  node-v0.9.5-sunos-x86.tar.gz
+7ed38be34e5377f45e8906c4d887de262c1925e2  node-v0.9.5-x86.msi
+a1f1322fcaa5535ae830f3242bcdd213388357cc  node-v0.9.5.tar.gz
+94c22b744945e9bc8b3f9fd31991cb6b87f727ce  node.exe
+e809779c8071abf05650fbb47e207140829dc62c  node.exp
+cec09944297546185070c809a78931839e3c2695  node.lib
+5a3a4f3de4b8bf4209ecc2e6d40418d6a7e8fcac  node.pdb
+55c986c14a72081757002f8df43272b20f024c57  x64/node-v0.9.5-x64.msi
+55514dd925a9b24cb3925f89facbec5efb2a99aa  x64/node.exe
+920e2d3319eac8a3356023a1cb8c61f139f80398  x64/node.exp
+e072006328dacce920e4951596e457e58e6310d0  x64/node.lib
+633816d865155148129ca21399e411f1240b2cce  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.6.md b/locale/uk/blog/release/v0.9.6.md
new file mode 100755
index 0000000000000..5cff3a8750e97
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.6.md
@@ -0,0 +1,90 @@
+---
+title: Node v0.9.6 (Unstable)
+slug: node-v0-9-6-unstable
+version: 0.9.6
+category: release
+date: 2013-01-11T19:23:56.000Z
+layout: blog-post.hbs
+---
+
+2013.01.11, Version 0.9.6 (Unstable)
+
+* V8: update to 3.15.11.5
+
+* node: remove ev-emul.h (Ben Noordhuis)
+
+* path: make basename and extname ignore trailing slashes (Bert Belder)
+
+* typed arrays: fix sunos signed/unsigned char issue (Ben Noordhuis)
+
+* child_process: Fix {stdio:'inherit'} regression (Ben Noordhuis)
+
+* child_process: Fix pipe() from child stdio streams  (Maciej Małecki)
+
+* child_process: make fork() execPath configurable (Bradley Meck)
+
+* stream: Add readable.push(chunk) method (isaacs)
+
+* dtrace: x64 ustack helper (Fedor Indutny)
+
+* repl: fix floating point number parsing (Nirk Niggler)
+
+* repl: allow overriding builtins (Ben Noordhuis)
+
+* net: add localAddress and localPort to Socket (James Hight)
+
+* fs: make pool size coincide with ReadStream bufferSize (Shigeki Ohtsu)
+
+* typed arrays: implement load and store swizzling (Dean McNamee)
+
+* windows: fix perfctr crash on XP and 2003 (Scott Blomquist)
+
+* dgram: fix double implicit bind error (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.9.6/node-v0.9.6.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.6/node-v0.9.6.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.6/node-v0.9.6-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.6/x64/node-v0.9.6-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.6/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.6/node-v0.9.6-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.6/node-v0.9.6-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.6/node-v0.9.6-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.6/node-v0.9.6-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.6/
+
+Website: https://nodejs.org/docs/v0.9.6/
+
+Documentation: https://nodejs.org/docs/v0.9.6/api/
+
+Shasums:
+
+```
+31ef1e0d875232c85ecde0bc84ddf19cf6cd63f7  node-v0.9.6-darwin-x64.tar.gz
+62d5f6f2b39e87eb1f86da0423b6ec45180cd986  node-v0.9.6-darwin-x86.tar.gz
+e3cb0989c8262349659424ea2f534c8afe12f93c  node-v0.9.6-linux-x64.tar.gz
+ff4b68f274a52038fbd04a4ef143e1076ae71db9  node-v0.9.6-linux-x86.tar.gz
+59ebb5e5c02c9e40a7a3cc2d8f554f2d722048eb  node-v0.9.6-sunos-x64.tar.gz
+714b88c5f34bb0adad2d73b6d76fa423d14c29b8  node-v0.9.6-sunos-x86.tar.gz
+3ecc617efcae5274c3a1e3452e8fb0646a3e6afc  node-v0.9.6-x86.msi
+d865d044cc1e9379998aa6c3d34dbe2824e41b5e  node-v0.9.6.pkg
+650d7c50e29ce7ab428de0617ad315063a53ea1a  node-v0.9.6.tar.gz
+94b10c6945ec78af6d9b90fc083f97adfa44473f  node.exe
+0b0eceee083ca9cfdc8c24fbdfe92f7ee25938c2  node.exp
+9af3ceee0be869e866b2f516dc2b17690e442739  node.lib
+7dfbdf0ac378e67cfa5aff550f057c31f8f92d38  node.pdb
+02f27f503a16850a66f7e6fe8732bfa5fcbe311f  x64/node-v0.9.6-x64.msi
+3f5990602e7268413602dd54a4d019b3330630ae  x64/node.exe
+836a7be49bd7ed5f1794775d0c20e75f327b067d  x64/node.exp
+e5e3abed1da31d94525f8731e2d67f0e19b20304  x64/node.lib
+b61c1a7a5786a38864943bb3d4c78859d0430d7a  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.7.md b/locale/uk/blog/release/v0.9.7.md
new file mode 100755
index 0000000000000..6b6e6c05d3d58
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.7.md
@@ -0,0 +1,84 @@
+---
+category: release
+version: 0.9.7
+date: 2013-01-18T19:38:32.000Z
+title: Node v0.9.7 (Unstable)
+slug: node-v0-9-7-unstable
+layout: blog-post.hbs
+---
+
+2013.01.18, Version 0.9.7 (Unstable)
+
+* V8: Upgrade to 3.15.11.7
+
+* npm: Upgrade to 1.2.2
+
+* punycode: Upgrade to 1.2.0 (Mathias Bynens)
+
+* repl: make built-in modules available by default (Felix Böhm)
+
+* windows: add support for '_Total' perf counters (Scott Blomquist)
+
+* cluster: make --prof work for workers (Ben Noordhuis)
+
+* child_process: do not keep list of sent sockets (Fedor Indutny)
+
+* tls: Follow RFC6125 more strictly (Fedor Indutny)
+
+* buffer: floating point read/write improvements (Trevor Norris)
+
+* TypedArrays: Improve dataview perf without endian param (Dean McNamee)
+
+* module: assert require() called with a non-empty string (Felix Böhm, James Campos)
+
+* stdio: Set readable/writable flags properly (isaacs)
+
+* stream: Properly handle large reads from push-streams (isaacs)
+
+
+Source Code: https://nodejs.org/dist/v0.9.7/node-v0.9.7.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.7/node-v0.9.7.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.7/node-v0.9.7-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.7/x64/node-v0.9.7-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.7/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.7/node-v0.9.7-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.7/node-v0.9.7-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.7/node-v0.9.7-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.7/node-v0.9.7-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.7/
+
+Website: https://nodejs.org/docs/v0.9.7/
+
+Documentation: https://nodejs.org/docs/v0.9.7/api/
+
+Shasums:
+
+```
+fa5771999205beae787e56bbffa3be3c496dbb3e  node-v0.9.7-darwin-x64.tar.gz
+3790a0323e82598d9286470a3ca8b079b25d815c  node-v0.9.7-darwin-x86.tar.gz
+70da0da05a2d76dfba389b413112aa1c31289114  node-v0.9.7-linux-x64.tar.gz
+b7448f020820302a6c648744a9ba4b6e1979fbf8  node-v0.9.7-linux-x86.tar.gz
+a0148c804c37ecbcfd4039213e469ba2757b6125  node-v0.9.7-sunos-x64.tar.gz
+121cd6fe2fbab0ca20644256914433bfa02ca6c4  node-v0.9.7-sunos-x86.tar.gz
+8938d57fc9cff896bb13901a43b5cff989785a23  node-v0.9.7-x86.msi
+23b86861de7c6111311f869c722431cf84d93761  node-v0.9.7.pkg
+527a86ee094f7ed77967eda3dff4b2aff3f29384  node-v0.9.7.tar.gz
+5231f327979f900d4ba927f2e63e67635001268c  node.exe
+6a78465d3f6e34aab82a529839c522abbab715ac  node.exp
+d814bd0733ba22a3cd9c086d34c68706d6c77663  node.lib
+5c9df4dcf16c9baafce9b6982907ada586e878a2  node.pdb
+f49f1e0706ef38facba45af75cfdf44678b21f5a  x64/node-v0.9.7-x64.msi
+13f9ee5c81b89bf77c5bfe46993905de4e3384d7  x64/node.exe
+3f9c67381a7f2b3fc2f6c14b66036dde02de2820  x64/node.exp
+cac98eebe21aeb05741a2fec6e2c7eaf5bb111a6  x64/node.lib
+563932b95c08ebdb923358cd8b68ee17ac7ad781  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v0.9.8.md b/locale/uk/blog/release/v0.9.8.md
new file mode 100755
index 0000000000000..bd96bac2a9cdf
--- /dev/null
+++ b/locale/uk/blog/release/v0.9.8.md
@@ -0,0 +1,79 @@
+---
+category: release
+date: 2013-01-24T18:28:53.000Z
+version: 0.9.8
+title: Node v0.9.8 (Unstable)
+slug: node-v0-9-8-unstable
+layout: blog-post.hbs
+---
+
+2013.01.24, Version 0.9.8 (Unstable)
+
+* npm: Upgrade to v1.2.3
+
+* V8: Upgrade to 3.15.11.10
+
+* streams: Support objects other than Buffers (Jake Verbaten)
+
+* buffer: remove float write range checks (Trevor Norris)
+
+* http: close connection on 304/204 responses with chunked encoding (Ben Noordhuis)
+
+* build: fix build with dtrace support on FreeBSD (Fedor Indutny)
+
+* console: Support formatting options in trace() (isaacs)
+
+* domain: empty stack on all exceptions (Dave Olszewski)
+
+* unix, windows: make uv_*_bind() error codes consistent (Andrius Bentkus)
+
+* linux: add futimes() fallback (Ben Noordhuis)
+
+
+Source Code: https://nodejs.org/dist/v0.9.8/node-v0.9.8.tar.gz
+
+Macintosh Installer (Universal): https://nodejs.org/dist/v0.9.8/node-v0.9.8.pkg
+
+Windows Installer: https://nodejs.org/dist/v0.9.8/node-v0.9.8-x86.msi
+
+Windows x64 Installer: https://nodejs.org/dist/v0.9.8/x64/node-v0.9.8-x64.msi
+
+Windows x64 Files: https://nodejs.org/dist/v0.9.8/x64/
+
+Linux 32-bit Binary: https://nodejs.org/dist/v0.9.8/node-v0.9.8-linux-x86.tar.gz
+
+Linux 64-bit Binary: https://nodejs.org/dist/v0.9.8/node-v0.9.8-linux-x64.tar.gz
+
+Solaris 32-bit Binary: https://nodejs.org/dist/v0.9.8/node-v0.9.8-sunos-x86.tar.gz
+
+Solaris 64-bit Binary: https://nodejs.org/dist/v0.9.8/node-v0.9.8-sunos-x64.tar.gz
+
+Other release files: https://nodejs.org/dist/v0.9.8/
+
+Website: https://nodejs.org/docs/v0.9.8/
+
+Documentation: https://nodejs.org/docs/v0.9.8/api/
+
+Shasums:
+
+```
+30bbd1df69be189afca34d808932f5417986d966  node-v0.9.8-darwin-x64.tar.gz
+e9e2e9477836e22a2e8242ddbc73400a2a5fac43  node-v0.9.8-darwin-x86.tar.gz
+fddaef3c084121f21d466a29f1117a844761a4a6  node-v0.9.8-linux-arm-pi.tar.gz
+0ec573b26722c45abf8db1c865f8169d49244877  node-v0.9.8-linux-x64.tar.gz
+b5227fb14eaad8f0c3c4fbc97b30292dcc34046b  node-v0.9.8-linux-x86.tar.gz
+1d846eba7dc3c02c19d82915bfccba4efb77d54c  node-v0.9.8-sunos-x64.tar.gz
+e06c6b965d44084ef355d80b10d99f23005bdac7  node-v0.9.8-sunos-x86.tar.gz
+4ba7fcefbd0d9cc83427500f4d71fa5ed0e82bb8  node-v0.9.8-x86.msi
+c92303e41c45aef6959b6a70285cdd6be30ef0b4  node-v0.9.8.pkg
+ce337f1f7baca56954412fbeaa25b4f9ea4c8528  node-v0.9.8.tar.gz
+474b4afd7b8696edaf240f1710084c3c7e48a00c  node.exe
+22044cb9cf46570d9a41cc830eda962e57331da7  node.exp
+3b612ca0692f8764dd722092d0ae6e5e2c6ae5fd  node.lib
+7b6e50f83202781bf827b554957d097f4ae66c46  node.pdb
+c67b8047392e591434169c5d367ff2356ae640fd  x64/node-v0.9.8-x64.msi
+474b4afd7b8696edaf240f1710084c3c7e48a00c  x64/node.exe
+22044cb9cf46570d9a41cc830eda962e57331da7  x64/node.exp
+3b612ca0692f8764dd722092d0ae6e5e2c6ae5fd  x64/node.lib
+7b6e50f83202781bf827b554957d097f4ae66c46  x64/node.pdb
+```
diff --git a/locale/uk/blog/release/v4.0.0.md b/locale/uk/blog/release/v4.0.0.md
new file mode 100755
index 0000000000000..9254440e6441a
--- /dev/null
+++ b/locale/uk/blog/release/v4.0.0.md
@@ -0,0 +1,177 @@
+---
+date: 2015-09-08T12:10:06.000Z
+version: 4.0.0
+category: release
+title: Node v4.0.0 (Current)
+slug: node-v4-0-0-stable
+layout: blog-post.hbs
+---
+
+The collaborators of the Node.js project and the members of the Node.js Foundation are proud to offer v4.0.0 for general release. This release represents countless hours of hard work encapsulated in both the Node.js project and the io.js project that are now combined in a single codebase. The Node.js project is now operated by a team of 44 collaborators, 15 of which form its Technical Steering Committee (TSC). Further, over 100 new individuals have been added to the list of people contributing code to core since v0.12.7.
+
+Node.js v4.0.0 contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](https://nodejs.org/en/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays (Node's `Buffer` is now backed by `Uint8Array`), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and, new to V8 v4.5, arrow functions.
+
+Over the past year thanks to donations from companies such as Rackspace, DigitalOcean, Scaleway, miniNodes, Voxer, Joyent, CloudFlare, ARM Holdings, and individuals from the community, we've built an amazing test cluster that includes an impressive line-up of Linux variants, OS X, Windows, FreeBSD and SmartOS. New to Node.js, we also have first-class support for ARM processors. Our test suite must be continually passing on ARMv6, ARMv7 and the new 64-bit ARMv8 processors. So Node.js is officially ready for use by hobbyists and ARM server users alike.
+
+Node.js v4 also brings a plan for [long-term support (LTS)](https://github.com/nodejs/LTS/) and a regular release cycle. Release versioning now follows [SemVer](http://semver.org/), so expect increments of both minor and patch version over the coming weeks as we fix bugs and add features. What we won't be doing within the v4.x branch is adding breaking changes.
+
+However, we have mapped a quick initial path to our first LTS version which will come in October. At the same time, a new v5.x branch will be cut and we will begin making a new series of Stable releases available, starting with v5.0.0. These will likely contain a new version of V8 and any breaking changes that may be necessary. The v4.x line of releases will continue for an additional 18 months in LTS, with a focus on stability and security and no unnecessary additions in functionality. Beyond that, v4.x will move in to Maintenance for an additional 12 months where it will continue to receive attention for critical bugs and security fixes.
+
+In parallel, we will be branching a new Stable line of releases every 6 months, one in October and one in April each year. Stable lines will be made up of regular releases as development continues, expect minor and patch version bumps every week or two from these. Every second Stable release line will continue life in LTS form by the time October comes around. This means that there will be overlapping LTS branches being maintained throughout the year, each receiving attention for a total of 30 months (LTS plus Maintenance). We believe that the Stable and LTS cycles provide the room for the project to continue its **innovation** and stay with the cutting-edge of JavaScript while also serving the need for **predictable long-term stability and security** demanded by the growing line-up of enterprise users proudly adopting Node.js as a key technology; some of who already count themselves as [members of the Node.js Foundation](https://nodejs.org/en/foundation/members/).
+
+As always with a major release, we don't expect the adoption of Node.js v4 to be painless. It will take time to adapt, particularly as compiled add-ons catch up with the new version of V8 (hint: see [NAN](https://github.com/nodejs/nan) for our official solution to the compatibility problem). Thankfully, the io.js v3.x series of releases have given many add-on authors a chance to prepare their code for Node.js v4, so much of the npm ecosystem is ready today.
+
+An initial list of breaking changes between v0.12 and v4 can be found on the [LTS wiki](https://github.com/nodejs/LTS/wiki/Breaking-changes-between-v0.12-and-next-LTS-release), in the coming days we will continue to populate both this wiki and the [core wiki](https://github.com/nodejs/node/wiki) with documentation regarding the changes you should be aware of.
+
+Please file any bugs at our new home on GitHub, <https://github.com/nodejs/node>, and consider joining the growing crew of collaborators by contributing to core!
+
+### Notable changes
+
+This list of changes is relative to the last io.js v3.x branch release, v3.3.0. Please see the list of notable changes in the v3.x, v2.x and v1.x releases compiled in unified [CHANGELOG](https://github.com/nodejs/node/blob/master/CHANGELOG.md) for a more complete list of changes from 0.12.x. Note, that some changes in the v3.x series as well as major breaking changes in this release constitute changes required for full convergence of the Node.js and io.js projects.
+
+* **child_process**: `ChildProcess.prototype.send()` and `process.send()` operate asynchronously across all platforms so an optional callback parameter has been introduced that will be invoked once the message has been sent, i.e. `.send(message[, sendHandle][, callback])` (Ben Noordhuis) [#2620](https://github.com/nodejs/node/pull/2620).
+* **node**: Rename "io.js" code to "Node.js" (cjihrig) [#2367](https://github.com/nodejs/node/pull/2367).
+* **node-gyp**: This release bundles an updated version of node-gyp that works with all versions of Node.js and io.js including nightly and release candidate builds. From io.js v3 and Node.js v4 onward, it will only download a headers tarball when building addons rather than the entire source. (Rod Vagg) [#2700](https://github.com/nodejs/node/pull/2700)
+* **npm**: Upgrade to version 2.14.2 from 2.13.3, includes a security update, see https://github.com/npm/npm/releases/tag/v2.14.2 for more details, (Kat Marchán) [#2696](https://github.com/nodejs/node/pull/2696).
+* **timers**: Improved timer performance from porting the 0.12 implementation, plus minor fixes (Jeremiah Senkpiel) [#2540](https://github.com/nodejs/node/pull/2540), (Julien Gilli) [nodejs/node-v0.x-archive#8751](https://github.com/nodejs/node-v0.x-archive/pull/8751) [nodejs/node-v0.x-archive#8905](https://github.com/nodejs/node-v0.x-archive/pull/8905)
+* **util**: The `util.is*()` functions have been deprecated, beginning with deprecation warnings in the documentation for this release, users are encouraged to seek more robust alternatives in the npm registry, (Sakthipriyan Vairamani) [#2447](https://github.com/nodejs/node/pull/2447).
+* **v8**: Upgrade to version 4.5.103.30 from 4.4.63.30 (Ali Ijaz Sheikh) [#2632](https://github.com/nodejs/node/pull/2632).
+ - Implement new `TypedArray` prototype methods: `copyWithin()`, `every()`, `fill()`, `filter()`, `find()`, `findIndex()`, `forEach()`, `indexOf()`, `join()`, `lastIndexOf()`, `map()`, `reduce()`, `reduceRight()`, `reverse()`, `slice()`, `some()`, `sort()`. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information.
+ - Implement new `TypedArray.from()` and `TypedArray.of()` functions. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information.
+ - Implement arrow functions, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions for further information.
+ - Full ChangeLog available at https://github.com/v8/v8-git-mirror/blob/4.5.103/ChangeLog
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some uses of computed object shorthand properties are not handled correctly by the current version of V8. e.g. `[{ [prop]: val }]` evaluates to `[{}]`. [#2507](https://github.com/nodejs/node/issues/2507)
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`4f50d3fb90`](https://github.com/nodejs/node/commit/4f50d3fb90)] - **(SEMVER-MAJOR)** This commit sets the value of process.release.name to "node". (cjihrig) [#2367](https://github.com/nodejs/node/pull/2367)
+* [[`d3178d8b1b`](https://github.com/nodejs/node/commit/d3178d8b1b)] - **buffer**: SlowBuffer only accept valid numeric values (Michaël Zasso) [#2635](https://github.com/nodejs/node/pull/2635)
+* [[`0cb0f4a6e4`](https://github.com/nodejs/node/commit/0cb0f4a6e4)] - **build**: fix v8_enable_handle_zapping override (Karl Skomski) [#2731](https://github.com/nodejs/node/pull/2731)
+* [[`a7596d7efc`](https://github.com/nodejs/node/commit/a7596d7efc)] - **build**: remote commands on staging in single session (Rod Vagg) [#2717](https://github.com/nodejs/node/pull/2717)
+* [[`be427e9efa`](https://github.com/nodejs/node/commit/be427e9efa)] - **build**: make .msi install to "nodejs", not "node" (Rod Vagg) [#2701](https://github.com/nodejs/node/pull/2701)
+* [[`5652ce0dbc`](https://github.com/nodejs/node/commit/5652ce0dbc)] - **build**: fix .pkg creation tooling (Rod Vagg) [#2687](https://github.com/nodejs/node/pull/2687)
+* [[`101db80111`](https://github.com/nodejs/node/commit/101db80111)] - **build**: add --enable-asan with builtin leakcheck (Karl Skomski) [#2376](https://github.com/nodejs/node/pull/2376)
+* [[`2c3939c9c0`](https://github.com/nodejs/node/commit/2c3939c9c0)] - **child_process**: use stdio.fd even if it is 0 (Evan Lucas) [#2727](https://github.com/nodejs/node/pull/2727)
+* [[`609db5a1dd`](https://github.com/nodejs/node/commit/609db5a1dd)] - **child_process**: check execFile and fork args (James M Snell) [#2667](https://github.com/nodejs/node/pull/2667)
+* [[`d010568c23`](https://github.com/nodejs/node/commit/d010568c23)] - **(SEMVER-MAJOR)** **child_process**: add callback parameter to .send() (Ben Noordhuis) [#2620](https://github.com/nodejs/node/pull/2620)
+* [[`c60857a81a`](https://github.com/nodejs/node/commit/c60857a81a)] - **cluster**: allow shared reused dgram sockets (Fedor Indutny) [#2548](https://github.com/nodejs/node/pull/2548)
+* [[`b2ecbb6191`](https://github.com/nodejs/node/commit/b2ecbb6191)] - **contextify**: ignore getters during initialization (Fedor Indutny) [#2091](https://github.com/nodejs/node/pull/2091)
+* [[`3711934095`](https://github.com/nodejs/node/commit/3711934095)] - **cpplint**: make it possible to run outside git repo (Ben Noordhuis) [#2710](https://github.com/nodejs/node/pull/2710)
+* [[`03f900ab25`](https://github.com/nodejs/node/commit/03f900ab25)] - **crypto**: replace rwlocks with simple mutexes (Ben Noordhuis) [#2723](https://github.com/nodejs/node/pull/2723)
+* [[`847459c29b`](https://github.com/nodejs/node/commit/847459c29b)] - **(SEMVER-MAJOR)** **crypto**: show exponent in decimal and hex (Chad Johnston) [#2320](https://github.com/nodejs/node/pull/2320)
+* [[`e1c976184d`](https://github.com/nodejs/node/commit/e1c976184d)] - **deps**: improve ArrayBuffer performance in v8 (Fedor Indutny) [#2732](https://github.com/nodejs/node/pull/2732)
+* [[`cc0ab17a23`](https://github.com/nodejs/node/commit/cc0ab17a23)] - **deps**: float node-gyp v3.0.0 (Rod Vagg) [#2700](https://github.com/nodejs/node/pull/2700)
+* [[`b2c3c6d727`](https://github.com/nodejs/node/commit/b2c3c6d727)] - **deps**: create .npmrc during npm tests (Kat Marchán) [#2696](https://github.com/nodejs/node/pull/2696)
+* [[`babdbfdbd5`](https://github.com/nodejs/node/commit/babdbfdbd5)] - **deps**: upgrade to npm 2.14.2 (Kat Marchán) [#2696](https://github.com/nodejs/node/pull/2696)
+* [[`155783d876`](https://github.com/nodejs/node/commit/155783d876)] - **deps**: backport 75e43a6 from v8 upstream (again) (saper) [#2692](https://github.com/nodejs/node/pull/2692)
+* [[`5424d6fcf0`](https://github.com/nodejs/node/commit/5424d6fcf0)] - **deps**: upgrade V8 to 4.5.103.30 (Ali Ijaz Sheikh) [#2632](https://github.com/nodejs/node/pull/2632)
+* [[`c43172578e`](https://github.com/nodejs/node/commit/c43172578e)] - **(SEMVER-MAJOR)** **deps**: upgrade V8 to 4.5.103.24 (Ali Ijaz Sheikh) [#2509](https://github.com/nodejs/node/pull/2509)
+* [[`714e96e8b9`](https://github.com/nodejs/node/commit/714e96e8b9)] - **deps**: backport 75e43a6 from v8 upstream (saper) [#2636](https://github.com/nodejs/node/pull/2636)
+* [[`8637755cbf`](https://github.com/nodejs/node/commit/8637755cbf)] - **doc**: add TSC meeting minutes 2015-09-02 (Rod Vagg) [#2674](https://github.com/nodejs/node/pull/2674)
+* [[`d3d5b93214`](https://github.com/nodejs/node/commit/d3d5b93214)] - **doc**: update environment vars in manpage and --help (Roman Reiss) [#2690](https://github.com/nodejs/node/pull/2690)
+* [[`29f586ac0a`](https://github.com/nodejs/node/commit/29f586ac0a)] - **doc**: update url doc to account for escaping (Jeremiah Senkpiel) [#2605](https://github.com/nodejs/node/pull/2605)
+* [[`ba50cfebef`](https://github.com/nodejs/node/commit/ba50cfebef)] - **doc**: reorder collaborators by their usernames (Johan Bergström) [#2322](https://github.com/nodejs/node/pull/2322)
+* [[`8a9a3bf798`](https://github.com/nodejs/node/commit/8a9a3bf798)] - **doc**: update changelog for io.js v3.3.0 (Rod Vagg) [#2653](https://github.com/nodejs/node/pull/2653)
+* [[`6cd0e2664b`](https://github.com/nodejs/node/commit/6cd0e2664b)] - **doc**: update io.js reference (Ben Noordhuis) [#2580](https://github.com/nodejs/node/pull/2580)
+* [[`f9539c19e8`](https://github.com/nodejs/node/commit/f9539c19e8)] - **doc**: update changelog for io.js v3.2.0 (Rod Vagg) [#2512](https://github.com/nodejs/node/pull/2512)
+* [[`cded6e7993`](https://github.com/nodejs/node/commit/cded6e7993)] - **doc**: fix CHANGELOG.md on master (Roman Reiss) [#2513](https://github.com/nodejs/node/pull/2513)
+* [[`93e2830686`](https://github.com/nodejs/node/commit/93e2830686)] - **(SEMVER-MINOR)** **doc**: document deprecation of util.is* functions (Sakthipriyan Vairamani) [#2447](https://github.com/nodejs/node/pull/2447)
+* [[`7038388558`](https://github.com/nodejs/node/commit/7038388558)] - **doc,test**: enable recursive file watching in Windows (Sakthipriyan Vairamani) [#2649](https://github.com/nodejs/node/pull/2649)
+* [[`f3696f64a1`](https://github.com/nodejs/node/commit/f3696f64a1)] - **events,lib**: don't require EE#listenerCount() (Jeremiah Senkpiel) [#2661](https://github.com/nodejs/node/pull/2661)
+* [[`45a2046f5d`](https://github.com/nodejs/node/commit/45a2046f5d)] - **(SEMVER-MAJOR)** **installer**: fix installers for node.js rename (Frederic Hemberger) [#2367](https://github.com/nodejs/node/pull/2367)
+* [[`7a999a1376`](https://github.com/nodejs/node/commit/7a999a1376)] - **(SEMVER-MAJOR)** **lib**: add net.Socket#localFamily property (Ben Noordhuis) [#956](https://github.com/nodejs/node/pull/956)
+* [[`de88255b0f`](https://github.com/nodejs/node/commit/de88255b0f)] - ***Revert*** "**lib,src**: add unix socket getsockname/getpeername" (Ben Noordhuis) [#2584](https://github.com/nodejs/node/pull/2584)
+* [[`f337595441`](https://github.com/nodejs/node/commit/f337595441)] - **(SEMVER-MAJOR)** **lib,src**: add unix socket getsockname/getpeername (Ben Noordhuis) [#956](https://github.com/nodejs/node/pull/956)
+* [[`3b602527d1`](https://github.com/nodejs/node/commit/3b602527d1)] - **(SEMVER-MAJOR)** **node**: additional cleanup for node rename (cjihrig) [#2367](https://github.com/nodejs/node/pull/2367)
+* [[`a69ab27ab4`](https://github.com/nodejs/node/commit/a69ab27ab4)] - **(SEMVER-MAJOR)** **node**: rename from io.js to node (cjihrig) [#2367](https://github.com/nodejs/node/pull/2367)
+* [[`9358eee9dd`](https://github.com/nodejs/node/commit/9358eee9dd)] - **node-gyp**: float 3.0.1, minor fix for download url (Rod Vagg) [#2737](https://github.com/nodejs/node/pull/2737)
+* [[`d2d981252b`](https://github.com/nodejs/node/commit/d2d981252b)] - **src**: s/ia32/x86 for process.release.libUrl for win (Rod Vagg) [#2699](https://github.com/nodejs/node/pull/2699)
+* [[`eba3d3dccd`](https://github.com/nodejs/node/commit/eba3d3dccd)] - **src**: use standard conform snprintf on windows (Karl Skomski) [#2404](https://github.com/nodejs/node/pull/2404)
+* [[`cddbec231f`](https://github.com/nodejs/node/commit/cddbec231f)] - **src**: fix buffer overflow for long exception lines (Karl Skomski) [#2404](https://github.com/nodejs/node/pull/2404)
+* [[`dd3f3417c7`](https://github.com/nodejs/node/commit/dd3f3417c7)] - **src**: re-enable fast math on arm (Michaël Zasso) [#2592](https://github.com/nodejs/node/pull/2592)
+* [[`e137c1177c`](https://github.com/nodejs/node/commit/e137c1177c)] - **(SEMVER-MAJOR)** **src**: enable vector ics on arm again (Ali Ijaz Sheikh) [#2509](https://github.com/nodejs/node/pull/2509)
+* [[`7ce749d722`](https://github.com/nodejs/node/commit/7ce749d722)] - **src**: replace usage of v8::Handle with v8::Local (Michaël Zasso) [#2202](https://github.com/nodejs/node/pull/2202)
+* [[`b1a2d9509f`](https://github.com/nodejs/node/commit/b1a2d9509f)] - **src**: enable v8 deprecation warnings and fix them (Ben Noordhuis) [#2091](https://github.com/nodejs/node/pull/2091)
+* [[`808de0da03`](https://github.com/nodejs/node/commit/808de0da03)] - **(SEMVER-MAJOR)** **src**: apply debug force load fixups from 41e63fb (Ali Ijaz Sheikh) [#2509](https://github.com/nodejs/node/pull/2509)
+* [[`5201cb0ff1`](https://github.com/nodejs/node/commit/5201cb0ff1)] - **src**: fix memory leak in ExternString (Karl Skomski) [#2402](https://github.com/nodejs/node/pull/2402)
+* [[`2308a27c0a`](https://github.com/nodejs/node/commit/2308a27c0a)] - **src**: only set v8 flags if argc > 1 (Evan Lucas) [#2646](https://github.com/nodejs/node/pull/2646)
+* [[`384effed20`](https://github.com/nodejs/node/commit/384effed20)] - **test**: fix use of `common` before required (Rod Vagg) [#2685](https://github.com/nodejs/node/pull/2685)
+* [[`f146f686b7`](https://github.com/nodejs/node/commit/f146f686b7)] - **(SEMVER-MAJOR)** **test**: fix test-repl-tab-complete.js for V8 4.5 (Ali Ijaz Sheikh) [#2509](https://github.com/nodejs/node/pull/2509)
+* [[`fe4b309fd3`](https://github.com/nodejs/node/commit/fe4b309fd3)] - **test**: refactor to eliminate flaky test (Rich Trott) [#2609](https://github.com/nodejs/node/pull/2609)
+* [[`619721e6b8`](https://github.com/nodejs/node/commit/619721e6b8)] - **test**: mark eval_messages as flaky (Alexis Campailla) [#2648](https://github.com/nodejs/node/pull/2648)
+* [[`93ba585b66`](https://github.com/nodejs/node/commit/93ba585b66)] - **test**: mark test-vm-syntax-error-stderr as flaky (João Reis) [#2662](https://github.com/nodejs/node/pull/2662)
+* [[`367140bca0`](https://github.com/nodejs/node/commit/367140bca0)] - **test**: mark test-repl-persistent-history as flaky (João Reis) [#2659](https://github.com/nodejs/node/pull/2659)
+* [[`f6b093343d`](https://github.com/nodejs/node/commit/f6b093343d)] - **timers**: minor `_unrefActive` fixes and improvements (Jeremiah Senkpiel) [#2540](https://github.com/nodejs/node/pull/2540)
+* [[`403d7ee7d1`](https://github.com/nodejs/node/commit/403d7ee7d1)] - **timers**: don't mutate unref list while iterating it (Julien Gilli) [#2540](https://github.com/nodejs/node/pull/2540)
+* [[`7a8c3e08c3`](https://github.com/nodejs/node/commit/7a8c3e08c3)] - **timers**: Avoid linear scan in `_unrefActive`. (Julien Gilli) [#2540](https://github.com/nodejs/node/pull/2540)
+* [[`b630ebaf43`](https://github.com/nodejs/node/commit/b630ebaf43)] - **win,msi**: Upgrade from old upgrade code (João Reis) [#2439](https://github.com/nodejs/node/pull/2439)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.0.0/node-v4.0.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.0.0/node-v4.0.0-x64.msi<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.0.0/node-v4.0.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.0.0/node-v4.0.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.0.0/<br>
+Documentation: https://nodejs.org/docs/v4.0.0/api/
+
+Shasums (GPG signing hash: SHA1, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+4893cadaa55fe88b214371b23257d7fae4b30661ef01d352e3f930ba9d402ee0  node-v4.0.0-darwin-x64.tar.gz
+1f2b278d4708d7d956f2a17be139af26955114b92cb4340735a10bb5f0585c0a  node-v4.0.0-darwin-x64.tar.xz
+8812b88e81ee258f7f9446b548f6b364edcdd455f73f06589f14dd71dca415d0  node-v4.0.0-headers.tar.gz
+776962bd95bf295e336fbf04f0d8764bb9f6236e0c699358b17e4e2a95ee3d6f  node-v4.0.0-headers.tar.xz
+0436f107e1d82c61c3ee4f916781466a49bece74bf4d4fb4bf4d53a57b81df85  node-v4.0.0-linux-arm64.tar.gz
+7fdb978ddda803b188958b368db13b97dcaacfbf96d40c99d13ed385499d3fdd  node-v4.0.0-linux-arm64.tar.xz
+6f88e532bbf55cff36d4940898b80359761de3a274cc214fbb58cc176ec49ba2  node-v4.0.0-linux-armv6l.tar.gz
+d7c1e9fefb360bde70c543d8981d2cce9a1c8444e847d19a89604756570d3075  node-v4.0.0-linux-armv6l.tar.xz
+a788ed1b04de00344f4bbb8a278b317c69f9672f5fd03adb24f53d7c3d6fc8f6  node-v4.0.0-linux-armv7l.tar.gz
+1ed96526e87c29b4d3b5618b5d2e3e65e1aef6a5e40f90ec3a3afd21047517cf  node-v4.0.0-linux-armv7l.tar.xz
+df8ada31840e3dc48c7fe7291c7eba70b2ce5a6b6d959ac01157b04731c8a88f  node-v4.0.0-linux-x64.tar.gz
+cc4eae3e4c2dd8b068d69e6d1d9849a863c51e3ec3d7f85cfb1e91e63912b66a  node-v4.0.0-linux-x64.tar.xz
+444b0c2e38602699103e4adb76c9f15b76c405f58b1308751cdc194041a39b93  node-v4.0.0-linux-x86.tar.gz
+6fe4ab43eae74c1cb376169f4f161bddef04ff8a693a772875de651fafa4252b  node-v4.0.0-linux-x86.tar.xz
+387dd01caf168267749b0ddc7702b2fef7c95fbe1b2dab9a41ded02c11f16889  node-v4.0.0.pkg
+f17ea8b1ffa6d63ba4eaa37708a365e5aefdb7de136f8b1a5751f2f258507026  node-v4.0.0-sunos-x64.tar.gz
+69188f3568bbc9c071c70cf92551dd15e6fb79c9bd5d8b3da136ed65af4adea1  node-v4.0.0-sunos-x64.tar.xz
+4537640f912b1db217351271e15d092d4654ecbe7cdb0169313988de5e453cd3  node-v4.0.0-sunos-x86.tar.gz
+99ce4830b6b4f10dfca050296c001beb60e47d3eda455bc5b287b4ecc0773c04  node-v4.0.0-sunos-x86.tar.xz
+e110e5a066f3a6fe565ede7dd66f3727384b9b5c5fbf46f8db723d726e2f5900  node-v4.0.0.tar.gz
+2e3c5069933bead1022848009a68426a10689e67c4204707798fa319a6847bb5  node-v4.0.0.tar.xz
+28dfb26fddb3ff56456bfc0ec186db27e6b84d9ce98752f34d48758f4af05fbe  node-v4.0.0-x64.msi
+ba67b46504afeedfd43d0ebb51844e2b427d64b631fe05d6fc35f7fc59d05307  node-v4.0.0-x86.msi
+4c468e9a5e664f700f664fde42576260a7dd2bd5625ab824a713845e231f8275  win-x64/node.exe
+c8189c310c774ce3cbe960bd9920e49f47db97a19f1256b9b5bfa1f9d83d4dca  win-x64/node.lib
+02814e5fdddbf77840e14042e98de3b50e0c0167aa1a8cccdf3222e643dd016f  win-x86/node.exe
+1bbe7009ea25e3ffe72cc7da92725146536be698cefd960e0e22269d02368c25  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJV71yWAAoJEMJzeS99g1RdcXkH/3sBJ89TZdqvzGEB/FZ5x+5C
+A4iAWfEa+RjSvJbtmo3noOUA7+OZPWVue6yEv3ZX4EEdk5ZIUEcf/4tYoW/D5cCm
+SBlnCB5TXMp8ZafCni3OvR52gBPIB4EFPlqPDLLA6wloUYm7xhyJ5V+Z9DeTzvGl
+CC6JDs0RkcqMT3799KBgrS/ud0G5BXCC1imnHxGUCgYc1BAcExHThbLs1zFyMuXg
+SSQJVJGoxR7LWfvnGFPnEbliSCuUfjGIT3DHAgovJgjQirj/vLssLBYyxMhCVBEa
+eR2+UlptmdbsIAsPvyNp2Tr466KlIawD99haYOfgmVnA1l1PWbAjJMdQZJPk+Mg=
+=tBAw
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v4.1.0.md b/locale/uk/blog/release/v4.1.0.md
new file mode 100755
index 0000000000000..714039679b163
--- /dev/null
+++ b/locale/uk/blog/release/v4.1.0.md
@@ -0,0 +1,161 @@
+---
+date: 2015-09-17T05:30:00.969Z
+version: 4.1.0
+category: release
+title: Node v4.1.0 (Current)
+slug: node-v4-1-0-stable
+layout: blog-post.hbs
+---
+
+## 2015-09-17, Version 4.1.0 (Current), @Fishrock123
+
+### Notable changes
+
+* **buffer**:
+  - Buffers are now created in JavaScript, rather than C++. This increases the speed of buffer creation (Trevor Norris) [#2866](https://github.com/nodejs/node/pull/2866).
+  - `Buffer#slice()` now uses `Uint8Array#subarray()` internally, increasing `slice()` performance (Karl Skomski) [#2777](https://github.com/nodejs/node/pull/2777).
+* **fs**:
+  - `fs.utimes()` now properly converts numeric strings, `NaN`, and `Infinity` (Yazhong Liu) [#2387](https://github.com/nodejs/node/pull/2387).
+  - `fs.WriteStream` now implements `_writev`, allowing for super-fast bulk writes (Ron Korving) [#2167](https://github.com/nodejs/node/pull/2167).
+* **http**: Fixed an issue with certain `write()` sizes causing errors when using `http.request()` (Fedor Indutny) [#2824](https://github.com/nodejs/node/pull/2824).
+* **npm**: Upgrade to version 2.14.3, see https://github.com/npm/npm/releases/tag/v2.14.3 for more details (Kat Marchán) [#2822](https://github.com/nodejs/node/pull/2822).
+* **src**: V8 cpu profiling no longer erroneously shows idle time (Oleksandr Chekhovskyi) [#2324](https://github.com/nodejs/node/pull/2324).
+* **timers**: `#ref()` and `#unref()` now return the timer they belong to (Sam Roberts) [#2905](https://github.com/nodejs/node/pull/2905).
+* **v8**: Lateral upgrade to 4.5.103.33 from 4.5.103.30, contains minor fixes (Ali Ijaz Sheikh) [#2870](https://github.com/nodejs/node/pull/2870).
+  - This fixes a previously known bug where some computed object shorthand properties did not work correctly ([#2507](https://github.com/nodejs/node/issues/2507)).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`b1abe812cd`](https://github.com/nodejs/node/commit/b1abe812cd)] - Working on 4.0.1 (Rod Vagg)
+* [[`f9f8378853`](https://github.com/nodejs/node/commit/f9f8378853)] - 2015-09-08, Version 4.0.0 (Current) Release (Rod Vagg)
+* [[`9683e5df51`](https://github.com/nodejs/node/commit/9683e5df51)] - **bindings**: close after reading module struct (Fedor Indutny) [#2792](https://github.com/nodejs/node/pull/2792)
+* [[`4b4cfa2d44`](https://github.com/nodejs/node/commit/4b4cfa2d44)] - **buffer**: always allocate typed arrays outside heap (Trevor Norris) [#2893](https://github.com/nodejs/node/pull/2893)
+* [[`7df018a29b`](https://github.com/nodejs/node/commit/7df018a29b)] - **buffer**: construct Uint8Array in JS (Trevor Norris) [#2866](https://github.com/nodejs/node/pull/2866)
+* [[`43397b204e`](https://github.com/nodejs/node/commit/43397b204e)] - **(SEMVER-MINOR)** **build**: Updates to enable AIX support (Michael Dawson) [#2364](https://github.com/nodejs/node/pull/2364)
+* [[`e35b1fd610`](https://github.com/nodejs/node/commit/e35b1fd610)] - **build**: clean up the generated tap file (Sakthipriyan Vairamani) [#2837](https://github.com/nodejs/node/pull/2837)
+* [[`96670ebe37`](https://github.com/nodejs/node/commit/96670ebe37)] - **deps**: backport 6d32be2 from v8's upstream (Michaël Zasso) [#2916](https://github.com/nodejs/node/pull/2916)
+* [[`94972d5b13`](https://github.com/nodejs/node/commit/94972d5b13)] - **deps**: backport 0d01728 from v8's upstream (Fedor Indutny) [#2912](https://github.com/nodejs/node/pull/2912)
+* [[`7ebd881c29`](https://github.com/nodejs/node/commit/7ebd881c29)] - **deps**: upgrade V8 to 4.5.103.33 (Ali Ijaz Sheikh) [#2870](https://github.com/nodejs/node/pull/2870)
+* [[`ed47ab6e44`](https://github.com/nodejs/node/commit/ed47ab6e44)] - **deps**: upgraded to node-gyp@3.0.3 in npm (Kat Marchán) [#2822](https://github.com/nodejs/node/pull/2822)
+* [[`f4641ae875`](https://github.com/nodejs/node/commit/f4641ae875)] - **deps**: upgrade to npm 2.14.3 (Kat Marchán) [#2822](https://github.com/nodejs/node/pull/2822)
+* [[`8119693a3d`](https://github.com/nodejs/node/commit/8119693a3d)] - **deps**: update libuv to version 1.7.4 (Saúl Ibarra Corretgé) [#2817](https://github.com/nodejs/node/pull/2817)
+* [[`6098504685`](https://github.com/nodejs/node/commit/6098504685)] - **deps**: cherry-pick 6da51b4 from v8's upstream (Fedor Indutny) [#2801](https://github.com/nodejs/node/pull/2801)
+* [[`bf42cc8dba`](https://github.com/nodejs/node/commit/bf42cc8dba)] - **doc**: process exit event is not guaranteed to fire (Rich Trott) [#2861](https://github.com/nodejs/node/pull/2861)
+* [[`bb0f869f67`](https://github.com/nodejs/node/commit/bb0f869f67)] - **doc**: remove incorrect reference to TCP in net docs (Sam Roberts) [#2903](https://github.com/nodejs/node/pull/2903)
+* [[`302d59dce8`](https://github.com/nodejs/node/commit/302d59dce8)] - **doc**: correct buffer.slice arg syntax (Sam Roberts) [#2903](https://github.com/nodejs/node/pull/2903)
+* [[`74db9637b7`](https://github.com/nodejs/node/commit/74db9637b7)] - **doc**: describe spawn option.detached (Sam Roberts) [#2903](https://github.com/nodejs/node/pull/2903)
+* [[`a7bd897273`](https://github.com/nodejs/node/commit/a7bd897273)] - **doc**: rename from iojs(1) to node(1) in benchmarks (Dmitry Vasilyev) [#2884](https://github.com/nodejs/node/pull/2884)
+* [[`cd643d7c37`](https://github.com/nodejs/node/commit/cd643d7c37)] - **doc**: add missing backtick in buffer.markdown (Sven Slootweg) [#2881](https://github.com/nodejs/node/pull/2881)
+* [[`e8a206e802`](https://github.com/nodejs/node/commit/e8a206e802)] - **doc**: fix broken link in repl.markdown (Danny Nemer) [#2827](https://github.com/nodejs/node/pull/2827)
+* [[`7ee36d61f7`](https://github.com/nodejs/node/commit/7ee36d61f7)] - **doc**: fix typos in README (Ionică Bizău) [#2852](https://github.com/nodejs/node/pull/2852)
+* [[`4d1ae26196`](https://github.com/nodejs/node/commit/4d1ae26196)] - **doc**: add tunniclm as a collaborator (Mike Tunnicliffe) [#2826](https://github.com/nodejs/node/pull/2826)
+* [[`2d77d03643`](https://github.com/nodejs/node/commit/2d77d03643)] - **doc**: fix two doc errors in stream and process (Jeremiah Senkpiel) [#2549](https://github.com/nodejs/node/pull/2549)
+* [[`55ac24f721`](https://github.com/nodejs/node/commit/55ac24f721)] - **doc**: fixed io.js references in process.markdown (Tristian Flanagan) [#2846](https://github.com/nodejs/node/pull/2846)
+* [[`cd1297fb57`](https://github.com/nodejs/node/commit/cd1297fb57)] - **doc**: use "Calls" over "Executes" for consistency (Minwoo Jung) [#2800](https://github.com/nodejs/node/pull/2800)
+* [[`d664b95581`](https://github.com/nodejs/node/commit/d664b95581)] - **doc**: use US English for consistency (Anne-Gaelle Colom) [#2784](https://github.com/nodejs/node/pull/2784)
+* [[`82ba1839fb`](https://github.com/nodejs/node/commit/82ba1839fb)] - **doc**: use 3rd person singular for consistency (Anne-Gaelle Colom) [#2765](https://github.com/nodejs/node/pull/2765)
+* [[`432cce6e95`](https://github.com/nodejs/node/commit/432cce6e95)] - **doc**: describe process API for IPC (Sam Roberts) [#1978](https://github.com/nodejs/node/pull/1978)
+* [[`1d75012b9d`](https://github.com/nodejs/node/commit/1d75012b9d)] - **doc**: fix comma splice in Assertion Testing doc (Rich Trott) [#2728](https://github.com/nodejs/node/pull/2728)
+* [[`6108ea9bb4`](https://github.com/nodejs/node/commit/6108ea9bb4)] - **fs**: consider NaN/Infinity in toUnixTimestamp (Yazhong Liu) [#2387](https://github.com/nodejs/node/pull/2387)
+* [[`2b6aa9415f`](https://github.com/nodejs/node/commit/2b6aa9415f)] - **(SEMVER-MINOR)** **fs**: implemented WriteStream#writev (Ron Korving) [#2167](https://github.com/nodejs/node/pull/2167)
+* [[`431bf74c55`](https://github.com/nodejs/node/commit/431bf74c55)] - **http**: default Agent.getName to 'localhost' (Malcolm Ahoy) [#2825](https://github.com/nodejs/node/pull/2825)
+* [[`ea15d71c16`](https://github.com/nodejs/node/commit/ea15d71c16)] - **http_server**: fix resume after socket close (Fedor Indutny) [#2824](https://github.com/nodejs/node/pull/2824)
+* [[`8e5843405b`](https://github.com/nodejs/node/commit/8e5843405b)] - **src**: null env_ field from constructor (Trevor Norris) [#2913](https://github.com/nodejs/node/pull/2913)
+* [[`0a5f80a11f`](https://github.com/nodejs/node/commit/0a5f80a11f)] - **src**: use subarray() in Buffer#slice() for speedup (Karl Skomski) [#2777](https://github.com/nodejs/node/pull/2777)
+* [[`57707e2490`](https://github.com/nodejs/node/commit/57707e2490)] - **src**: use ZCtxt as a source for v8::Isolates (Roman Klauke) [#2547](https://github.com/nodejs/node/pull/2547)
+* [[`b0df2273ab`](https://github.com/nodejs/node/commit/b0df2273ab)] - **src**: fix v8::CpuProfiler idle sampling (Oleksandr Chekhovskyi) [#2324](https://github.com/nodejs/node/pull/2324)
+* [[`eaa8e60b91`](https://github.com/nodejs/node/commit/eaa8e60b91)] - **streams**: refactor LazyTransform to internal/ (Brendan Ashworth) [#2566](https://github.com/nodejs/node/pull/2566)
+* [[`648c003e14`](https://github.com/nodejs/node/commit/648c003e14)] - **test**: use tmp directory in chdir test (Sakthipriyan Vairamani) [#2589](https://github.com/nodejs/node/pull/2589)
+* [[`079a2173d4`](https://github.com/nodejs/node/commit/079a2173d4)] - **test**: fix Buffer OOM error message (Trevor Norris) [#2915](https://github.com/nodejs/node/pull/2915)
+* [[`52019a1b21`](https://github.com/nodejs/node/commit/52019a1b21)] - **test**: fix default value for additional param (Sakthipriyan Vairamani) [#2553](https://github.com/nodejs/node/pull/2553)
+* [[`5df5d0423a`](https://github.com/nodejs/node/commit/5df5d0423a)] - **test**: remove disabled test (Rich Trott) [#2841](https://github.com/nodejs/node/pull/2841)
+* [[`9e5f0995bd`](https://github.com/nodejs/node/commit/9e5f0995bd)] - **test**: split up internet dns tests (Rich Trott) [#2802](https://github.com/nodejs/node/pull/2802)
+* [[`41f2dde51a`](https://github.com/nodejs/node/commit/41f2dde51a)] - **test**: increase dgram timeout for armv6 (Rich Trott) [#2808](https://github.com/nodejs/node/pull/2808)
+* [[`6e2fe1c21a`](https://github.com/nodejs/node/commit/6e2fe1c21a)] - **test**: remove valid hostname check in test-dns.js (Rich Trott) [#2785](https://github.com/nodejs/node/pull/2785)
+* [[`779e14f1a7`](https://github.com/nodejs/node/commit/779e14f1a7)] - **test**: expect error for test_lookup_ipv6_hint on FreeBSD (Rich Trott) [#2724](https://github.com/nodejs/node/pull/2724)
+* [[`f931b9dd95`](https://github.com/nodejs/node/commit/f931b9dd95)] - **(SEMVER-MINOR)** **timer**: ref/unref return self (Sam Roberts) [#2905](https://github.com/nodejs/node/pull/2905)
+* [[`59d03738cc`](https://github.com/nodejs/node/commit/59d03738cc)] - **tools**: enable arrow functions in .eslintrc (Sakthipriyan Vairamani) [#2840](https://github.com/nodejs/node/pull/2840)
+* [[`69e7b875a2`](https://github.com/nodejs/node/commit/69e7b875a2)] - **tools**: open `test.tap` file in write-binary mode (Sakthipriyan Vairamani) [#2837](https://github.com/nodejs/node/pull/2837)
+* [[`ff6d30d784`](https://github.com/nodejs/node/commit/ff6d30d784)] - **tools**: add missing tick processor polyfill (Matt Loring) [#2694](https://github.com/nodejs/node/pull/2694)
+* [[`519caba021`](https://github.com/nodejs/node/commit/519caba021)] - **tools**: fix flakiness in test-tick-processor (Matt Loring) [#2694](https://github.com/nodejs/node/pull/2694)
+* [[`ac004b8555`](https://github.com/nodejs/node/commit/ac004b8555)] - **tools**: remove hyphen in TAP result (Sakthipriyan Vairamani) [#2718](https://github.com/nodejs/node/pull/2718)
+* [[`ba47511976`](https://github.com/nodejs/node/commit/ba47511976)] - **tsc**: adjust TSC membership for IBM+StrongLoop (James M Snell) [#2858](https://github.com/nodejs/node/pull/2858)
+* [[`e035266805`](https://github.com/nodejs/node/commit/e035266805)] - **win,msi**: fix documentation shortcut url (Brian White) [#2781](https://github.com/nodejs/node/pull/2781)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.1.0/node-v4.1.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.1.0/node-v4.1.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.1.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.1.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.1.0/node-v4.1.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-linux-armv7.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.1.0/node-v4.1.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.1.0/node-v4.1.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.1.0/<br>
+Documentation: https://nodejs.org/docs/v4.1.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+ff1c4b13a10c0789709cd73980a496b27e434207802989377ec4cb56302a1ebc  node-v4.1.0-darwin-x64.tar.gz
+11d8d7367a7a7c91eb0ea7d8bdca7d24a9b944bf7a9c84389fbc3d3d35cb31a2  node-v4.1.0-darwin-x64.tar.xz
+1ba579ead4cc6a70b1d74bbc3591ca9c9c46e4254ff6cebc9dedfaf98e1657aa  node-v4.1.0-headers.tar.gz
+550a3023531f8387dcd7b632ceda6b613e0464a78aba0c4ee30dcb69026829dd  node-v4.1.0-headers.tar.xz
+d27001f51d75c43cc1f444eab8aef0ced4ac4d162598be7eccf58790127e5368  node-v4.1.0-linux-arm64.tar.gz
+8c0abe5f89ae9530751188cfef9640fa774c9812c15f7e168207d0adf51d8fff  node-v4.1.0-linux-arm64.tar.xz
+3b728cdb93d155cf532a8a7f57f5a86f6f67a73e57a7abe657ff88166995e99e  node-v4.1.0-linux-armv7.tar.gz
+3e1618a9c276fdcef45993ede68221667ef39c39356e8bc6f91c9ebf7310e8db  node-v4.1.0-linux-armv7.tar.xz
+7c6055e08127143d9a8f779aa56f3fe42035fff8843c2652b0b2726204556382  node-v4.1.0-linux-x64.tar.gz
+0f062984d1f7ce40cd902120b40b916b50df8041adb851373dce178f5ea959a3  node-v4.1.0-linux-x64.tar.xz
+2ceaf5e66993da50e4514ddc5c270dc15ee712d00c29a2108655d9d259b3b9bb  node-v4.1.0-linux-x86.tar.gz
+ac21e4c3628acfcd7df14cb4127691a4c55b9c7dbd5b1cba73c592f848e61cac  node-v4.1.0-linux-x86.tar.xz
+9df8830c12bd28a5c1a0e1355cad9f50546e40ce681061d62f7a16e351272764  node-v4.1.0.pkg
+b9b176f4e54422ab73458dcc36eec34149ffb298a9f5a5aa042c4b7e59860113  node-v4.1.0-sunos-x64.tar.gz
+dfdead90e1c0e9760aeef0acf198fd1450b9c2b7dd32b42bae6f9ee6e0046566  node-v4.1.0-sunos-x64.tar.xz
+ed6c5163b3cb2e452e8e9bf4e3857af9e65eccd7fce0959fb97dcf03547c726a  node-v4.1.0-sunos-x86.tar.gz
+856e7478a237495ec1586054722b853a1b1f21dd29442fade9f8d2259967c214  node-v4.1.0-sunos-x86.tar.xz
+453005f64ee529f7dcf1237eb27ee2fa2415c49f5c9e7463e8b71fba61c5b408  node-v4.1.0.tar.gz
+2e153aaa72d73578e2ef68bd943e629904f00897769c2a2992ff4561d742772d  node-v4.1.0.tar.xz
+ebf934575177def034130e2adea292567956be7ef4ed6c11fe645bc59a6ace06  node-v4.1.0-x64.msi
+4c6fae187c23b15ec1689d25ac0000d2902d8d5f6c64710ed4ad9e2166f6580f  node-v4.1.0-x86.msi
+95199ec14462edc982e01538d81ecd9af35ae3f9ef18c33be53102a5f93053e0  win-x64/node.exe
+a00d40f053c7926f0999279c987cbd293a630853bb5565b0a07e61bece80fe34  win-x64/node.lib
+62dca0c50648c3b87d9af1e469f290e82ab009f60892b164e1d1f6655c7310e3  win-x86/node.exe
+6f84367eb539f230eef02714703d8a817b1c956ad302def07034f3cd310461df  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJV+k2+AAoJEEX17r2BPa6OJjQP/1IAMo0X/9rSMwy8grbaj5Iy
+E5sZTrTVZ7Xddzqu3c6zn/M9poK28aQUEPAkgXrICTXrmD6zM8In2wrmRMmcQkOn
+iuS9rl7wsSLzfha2QnBbnl9XxEvSlf7csXsWuHKOk/MSPTqdowGbcWZhs2wsHpgX
+Wv7yhaygvWZtboeZ3KTJsh48AcEru+Azm2jjU6/toBRCTTLWwXIYU8v1QdYhVVbM
+A5nufi2tlpY4cBMZBOeEN/rFfCxoXvk8t0kR82qIGz28292p9anYt1I0MDMbK6Dq
+N+ex02SQNcA+4+PMMBP5IyQXXIvi+jBzbDIxAHI/B3b+k5ZQXtV44sB+kiPS1H9Z
+KHaC7ccom9Oo9lvU9KElTRJGD9JWdLvAENvsJO9CUFbR+NCcfk+amCcqK/UZxQeq
+4s7cqnyM99oacX1fqqj+dMh8YxWB10lqz4ttdgkGX4yZtJQdp1OZ6F1NQuu839e7
+TNUMa4MI0eZ/BjnocqlKnlCyMWQmWBPRIzfFXnRu+Q3Mq+3tpi6qKhE1Zda/E4Ow
++zUgRBDd94rE84rQNp9QLuEY0yhWWI2QQOOnBIRlfZPfDLcr12eSVm41yOYbL9pZ
+wbF5+3DHMvjCC0IjcnFAja16joTps27eBsn2dNI72wyQod06W2qLZFS+Xt+AO6Tb
+cFwYASzhWAmlr+3T6kFK
+=VJ63
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.1.1.md b/locale/uk/blog/release/v4.1.1.md
new file mode 100755
index 0000000000000..63f07de94227f
--- /dev/null
+++ b/locale/uk/blog/release/v4.1.1.md
@@ -0,0 +1,126 @@
+---
+date: 2015-09-23T02:01:38.545Z
+version: 4.1.1
+category: release
+title: Node v4.1.1 (Current)
+slug: node-v4-1-1-stable
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+This release contains some minor security-related updates. You are advised to upgrade to 4.1.1 if you are currently running v4.1.0.
+
+### Notable changes
+
+* **buffer**: Fixed a bug introduced in v4.1.0 where allocating a new zero-length buffer can result in the _next_ allocation of a TypedArray in JavaScript not being zero-filled. In certain circumstances this could result in data leakage via reuse of memory space in TypedArrays, breaking the normally safe assumption that TypedArrays should be always zero-filled. (Trevor Norris) [#2931](https://github.com/nodejs/node/pull/2931).
+* **http**: Guard against response-splitting of HTTP trailing headers added via [`response.addTrailers()`](https://nodejs.org/api/http.html#http_response_addtrailers_headers) by removing new-line (`[\r\n]`) characters from values. Note that standard header values are already stripped of new-line characters. The expected security impact is low because trailing headers are rarely used. (Ben Noordhuis) [#2945](https://github.com/nodejs/node/pull/2945).
+* **npm**: Upgrade to npm 2.14.4 from 2.14.3, see [release notes](https://github.com/npm/npm/releases/tag/v2.14.4) for full details (Kat Marchán) [#2958](https://github.com/nodejs/node/pull/2958)
+  - Upgrades `graceful-fs` on multiple dependencies to no longer rely on monkey-patching `fs`
+  - Fix `npm link` for pre-release / RC builds of Node
+* **v8**: Update post-mortem metadata to allow post-mortem debugging tools to find and inspect:
+  - JavaScript objects that use dictionary properties (Julien Gilli) [#2959](https://github.com/nodejs/node/pull/2959)
+  - ScopeInfo and thus closures (Julien Gilli) [#2974](https://github.com/nodejs/node/pull/2974)
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`d63e02e08d`](https://github.com/nodejs/node/commit/d63e02e08d)] - **buffer**: don't set zero fill for zero-length buffer (Trevor Norris) [#2931](https://github.com/nodejs/node/pull/2931)
+* [[`5905b14bff`](https://github.com/nodejs/node/commit/5905b14bff)] - **build**: fix icutrim when building small-icu on BE (Stewart Addison) [#2602](https://github.com/nodejs/node/pull/2602)
+* [[`f010cb5d96`](https://github.com/nodejs/node/commit/f010cb5d96)] - **configure**: detect mipsel host (Jérémy Lal) [#2971](https://github.com/nodejs/node/pull/2971)
+* [[`b93ad5abbd`](https://github.com/nodejs/node/commit/b93ad5abbd)] - **deps**: backport 357e6b9 from V8's upstream (Julien Gilli) [#2974](https://github.com/nodejs/node/pull/2974)
+* [[`8da3da4d41`](https://github.com/nodejs/node/commit/8da3da4d41)] - **deps**: backport ff7d70b from V8's upstream (Julien Gilli) [#2959](https://github.com/nodejs/node/pull/2959)
+* [[`2600fb8ae6`](https://github.com/nodejs/node/commit/2600fb8ae6)] - **deps**: upgraded to node-gyp@3.0.3 in npm (Kat Marchán) [#2958](https://github.com/nodejs/node/pull/2958)
+* [[`793aad2d7a`](https://github.com/nodejs/node/commit/793aad2d7a)] - **deps**: upgrade to npm 2.14.4 (Kat Marchán) [#2958](https://github.com/nodejs/node/pull/2958)
+* [[`43e2b7f836`](https://github.com/nodejs/node/commit/43e2b7f836)] - **doc**: remove usage of events.EventEmitter (Sakthipriyan Vairamani) [#2921](https://github.com/nodejs/node/pull/2921)
+* [[`9c59d2f16a`](https://github.com/nodejs/node/commit/9c59d2f16a)] - **doc**: remove extra using v8::HandleScope statement (Christopher J. Brody) [#2983](https://github.com/nodejs/node/pull/2983)
+* [[`f7edbab367`](https://github.com/nodejs/node/commit/f7edbab367)] - **doc**: clarify description of assert.ifError() (Rich Trott) [#2941](https://github.com/nodejs/node/pull/2941)
+* [[`b2ddf0f9a2`](https://github.com/nodejs/node/commit/b2ddf0f9a2)] - **doc**: refine process.kill() and exit explanations (Rich Trott) [#2918](https://github.com/nodejs/node/pull/2918)
+* [[`f68fed2e6f`](https://github.com/nodejs/node/commit/f68fed2e6f)] - **http**: remove redundant code in _deferToConnect (Malcolm Ahoy) [#2769](https://github.com/nodejs/node/pull/2769)
+* [[`f542e74c93`](https://github.com/nodejs/node/commit/f542e74c93)] - **http**: guard against response splitting in trailers (Ben Noordhuis) [#2945](https://github.com/nodejs/node/pull/2945)
+* [[`bc9f629387`](https://github.com/nodejs/node/commit/bc9f629387)] - **http_parser**: do not dealloc during kOnExecute (Fedor Indutny) [#2956](https://github.com/nodejs/node/pull/2956)
+* [[`1860e0cebd`](https://github.com/nodejs/node/commit/1860e0cebd)] - **lib,src**: remove usage of events.EventEmitter (Sakthipriyan Vairamani) [#2921](https://github.com/nodejs/node/pull/2921)
+* [[`d4cd5ac407`](https://github.com/nodejs/node/commit/d4cd5ac407)] - **readline**: fix tab completion bug (Matt Harrison) [#2816](https://github.com/nodejs/node/pull/2816)
+* [[`9760e04839`](https://github.com/nodejs/node/commit/9760e04839)] - **repl**: don't use tty control codes when $TERM is set to "dumb" (Salman Aljammaz) [#2712](https://github.com/nodejs/node/pull/2712)
+* [[`cb971cc97d`](https://github.com/nodejs/node/commit/cb971cc97d)] - **repl**: backslash bug fix (Sakthipriyan Vairamani) [#2968](https://github.com/nodejs/node/pull/2968)
+* [[`2034f68668`](https://github.com/nodejs/node/commit/2034f68668)] - **src**: honor --abort_on_uncaught_exception flag (Evan Lucas) [#2776](https://github.com/nodejs/node/pull/2776)
+* [[`0b1ca4a9ef`](https://github.com/nodejs/node/commit/0b1ca4a9ef)] - **src**: Add ABORT macro (Evan Lucas) [#2776](https://github.com/nodejs/node/pull/2776)
+* [[`4519dd00f9`](https://github.com/nodejs/node/commit/4519dd00f9)] - **test**: test sync version of mkdir & rmdir (Sakthipriyan Vairamani) [#2588](https://github.com/nodejs/node/pull/2588)
+* [[`816f609c8b`](https://github.com/nodejs/node/commit/816f609c8b)] - **test**: use tmpDir instead of fixtures in readdir (Sakthipriyan Vairamani) [#2587](https://github.com/nodejs/node/pull/2587)
+* [[`2084f52585`](https://github.com/nodejs/node/commit/2084f52585)] - **test**: test more http response splitting scenarios (Ben Noordhuis) [#2945](https://github.com/nodejs/node/pull/2945)
+* [[`fa08d1d8a1`](https://github.com/nodejs/node/commit/fa08d1d8a1)] - **test**: add test-spawn-cmd-named-pipe (Alexis Campailla) [#2770](https://github.com/nodejs/node/pull/2770)
+* [[`71b5d80682`](https://github.com/nodejs/node/commit/71b5d80682)] - **test**: make cluster tests more time tolerant (Michael Dawson) [#2891](https://github.com/nodejs/node/pull/2891)
+* [[`3e09dcfc32`](https://github.com/nodejs/node/commit/3e09dcfc32)] - **test**: update cwd-enoent tests for AIX (Imran Iqbal) [#2909](https://github.com/nodejs/node/pull/2909)
+* [[`6ea8ec1c59`](https://github.com/nodejs/node/commit/6ea8ec1c59)] - **tools**: single, cross-platform tick processor (Matt Loring) [#2868](https://github.com/nodejs/node/pull/2868)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.1.1/node-v4.1.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.1.1/node-v4.1.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.1.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.1.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.1.1/node-v4.1.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.1.1/node-v4.1.1-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.1.1/node-v4.1.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.1.1/<br>
+Documentation: https://nodejs.org/docs/v4.1.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+b7e72bf8364c35992a8bebc57bf68c596d622c33d409c0943bf7d24ca7205c76  node-v4.1.1-darwin-x64.tar.gz
+ce887b8c4d38fc269d22c072224a13c686445ea4c84ee506d4edd27de169c34c  node-v4.1.1-darwin-x64.tar.xz
+d134614e78cfc406611e366c9618704a47c2ee1bf60f0a11909ba84d8b2a9e28  node-v4.1.1-headers.tar.gz
+9edcf9fd5c79a3696faef185bc2e9ee51c709dda2381b1bc6deb49f240897e5d  node-v4.1.1-headers.tar.xz
+b2e1915a0c65dd9faee7f05a56792371958980e02d1f7cde447c8260bb805052  node-v4.1.1-linux-arm64.tar.gz
+63b4705f3ae5ee9f97b319dbc68463c12478fbcfc1bdf654f760a2e5bea565e8  node-v4.1.1-linux-arm64.tar.xz
+ca38cef96180916891a262bbb39f335eaa8de6c0c06933609f4f3d7bebdc94b5  node-v4.1.1-linux-armv6l.tar.gz
+06eff36b1f65b917ddedd2d6143d56ccc509518ac7cace6375011e2c5a40c226  node-v4.1.1-linux-armv6l.tar.xz
+2896f0ab7c53bb7b489a09f7344e059f898ae929c2a9bfb7dfce85a5846ab9d2  node-v4.1.1-linux-armv7l.tar.gz
+a88e19a3f6be90c7f93b890b3ef2e91f9563ab0b270f619b0fb78c773771c0af  node-v4.1.1-linux-armv7l.tar.xz
+f5f7e11a503c997486d50d8683741a554bdda1d1181125a05ac5844cb29d1572  node-v4.1.1-linux-x64.tar.gz
+ffd058c4742c0525cc9d59069f29768096caac6d8d7eac2300d486a7f2d8122e  node-v4.1.1-linux-x64.tar.xz
+3f9836b8a7e6e3d6591af6ef59e6055255439420518c3f77e0e65832a8486be1  node-v4.1.1-linux-x86.tar.gz
+dc2813fcf233d5fd8a375839757a0225748cf65f3d1027cab6188cd9e99897cf  node-v4.1.1-linux-x86.tar.xz
+1d7ee48a3d66d895692ca8085470358306eb11f398564834c3030cf3fe9f77e0  node-v4.1.1.pkg
+e1e991519f4147ccef0c1816d26905ccf0a0be094af08d302a63e1025a7369df  node-v4.1.1-sunos-x64.tar.gz
+6b0d3278bba8313c7894cf55b755556c549651d0027a3a735114fb99b3afa148  node-v4.1.1-sunos-x64.tar.xz
+915ec11b4a64becd817a810b7d8ecb426da3c52465d3ac3dfae50b53ad1ea28c  node-v4.1.1-sunos-x86.tar.gz
+ef71fbfa086a5d6929f8a7cac0addb99d9c4f5a1f9caa889aecb1e5a980b4449  node-v4.1.1-sunos-x86.tar.xz
+6a610935ff52de713cf2af6a26002322e24fd7933a444436f0817a2b84e15a58  node-v4.1.1.tar.gz
+f7ca9ceb0b7cc49b12f28a652c908a1f0ffbf34cec73ad0805fe717b14996bb9  node-v4.1.1.tar.xz
+04b65daa09c1daff6d0a4101a3256d18eb9d5b50ba3ba49184b5b032dd9a4c06  node-v4.1.1-x64.msi
+e73db653f543e3f6bcd28451d82e491064405b70546849579b31587f74b1a504  node-v4.1.1-x86.msi
+9e985444df6374fb9efaa8c43630a26ca4fc77dcdcb5564abf7c30a62033dd53  win-x64/node.exe
+e416599fb719d32d88e5e1abb27d1225c65bea452d8f11d1608e6a2c91c7695c  win-x64/node.lib
+8fe8b23e11e6356b6ab50f18060939c3e7a9f56d8ca2189fc556c8185f1a5083  win-x86/node.exe
+e2a6a441e26cd60043f7537552fd10a3f678bc9265af539256410c6da2a0e9b4  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWA1eGAAoJEMJzeS99g1Rd/uMH+wT/zvf2BLZjyd95XvmgZ3yx
+nCwZjGRLUfsMPd9Hk5x0D6Wpjq7hpIcN06W3ea6t7zgiZ/yCHBRfZ8KZHUkHP+Tm
+/yNQwpZajEIL1RGssx/Wm1VMB3sysAl3RZ665OtvpuBgQ0w6PKNqB+WJG8G/1GSd
+lB1sVYCq+CagjknPUMM+tYnxGDzSnJRcKdGI3DVvAu57AHdsYmuEfVxic2jRF1m+
+yB2ncABRXYqcELt6U293B82Lr3zBYUd8gcBd2VzgOUSmMZh0YlqgPKt2Ll5/fEnY
+fe3ditIQsQTiWtKzXr++Hd9iD2B+ppL3XBbiDByKFznIHg4BR61l8OuotHoL334=
+=Oh4x
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.1.2.md b/locale/uk/blog/release/v4.1.2.md
new file mode 100755
index 0000000000000..19cdb489999b8
--- /dev/null
+++ b/locale/uk/blog/release/v4.1.2.md
@@ -0,0 +1,143 @@
+---
+date: 2015-10-05T20:05:01.925Z
+version: 4.1.2
+category: release
+title: Node v4.1.2 (Current)
+slug: node-v4-1-2-stable
+layout: blog-post.hbs
+---
+
+## 2015-10-05, Version 4.1.2 (Current), @rvagg
+
+This release includes a fix for [CVE-2015-7384](https://github.com/nodejs/node/issues/3138), a Denial of Service (DoS) bug. Details of the bug can be found on the [nodejs-sec](https://groups.google.com/forum/#!topic/nodejs-sec/fSNEQiuof6I) group. Please subscribe to [nodejs-sec](https://groups.google.com/forum/#!forum/nodejs-sec) to receive future notifications of security releases.
+
+All users of Node.js v4.x should upgrade to v4.1.2, this is a critical update.
+
+### Notable changes
+
+* **http**:
+  - Fix out-of-order 'finish' event bug in pipelining that can abort execution, fixes DoS vulnerability [CVE-2015-7384](https://github.com/nodejs/node/issues/3138) (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+  - Account for pending response data instead of just the data on the current request to decide whether pause the socket or not (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+* **libuv**: Upgraded from v1.7.4 to v1.7.5, see [release notes](https://github.com/libuv/libuv/releases/tag/v1.7.5) for details (Saúl Ibarra Corretgé) [#3010](https://github.com/nodejs/node/pull/3010)
+  - A better rwlock implementation for all Windows versions
+  - Improved AIX support
+* **v8**:
+  - Upgraded from v4.5.103.33 to v4.5.103.35 (Ali Ijaz Sheikh) [#3117](https://github.com/nodejs/node/pull/3117)
+  - Backported [f782159](https://codereview.chromium.org/1367123003) from v8's upstream to help speed up Promise introspection (Ben Noordhuis) [#3130](https://github.com/nodejs/node/pull/3130)
+  - Backported [c281c15](https://codereview.chromium.org/1363683002) from v8's upstream to add JSTypedArray length in post-mortem metadata (Julien Gilli) [#3031](https://github.com/nodejs/node/pull/3031)
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`39b8730e8b`](https://github.com/nodejs/node/commit/39b8730e8b)] - **async_wrap**: ensure all objects have internal field (Trevor Norris) [#3139](https://github.com/nodejs/node/pull/3139)
+* [[`99e66074d7`](https://github.com/nodejs/node/commit/99e66074d7)] - **async_wrap**: update providers and add test (Trevor Norris) [#3139](https://github.com/nodejs/node/pull/3139)
+* [[`7a58157d4e`](https://github.com/nodejs/node/commit/7a58157d4e)] - **benchmark**: update comment in common.js (Minwoo Jung) [#2399](https://github.com/nodejs/node/pull/2399)
+* [[`9e9bfa4dc0`](https://github.com/nodejs/node/commit/9e9bfa4dc0)] - **build**: iojs -> nodejs of release-urlbase (P.S.V.R) [#3015](https://github.com/nodejs/node/pull/3015)
+* [[`8335ec7191`](https://github.com/nodejs/node/commit/8335ec7191)] - **build**: fix some typos inside the configure script (P.S.V.R) [#3016](https://github.com/nodejs/node/pull/3016)
+* [[`d6ac547d5d`](https://github.com/nodejs/node/commit/d6ac547d5d)] - **build,win**: fix node.exe resource version (João Reis) [#3053](https://github.com/nodejs/node/pull/3053)
+* [[`798dad24f4`](https://github.com/nodejs/node/commit/798dad24f4)] - **child_process**: `null` channel handle on close (Fedor Indutny) [#3041](https://github.com/nodejs/node/pull/3041)
+* [[`e5615854ea`](https://github.com/nodejs/node/commit/e5615854ea)] - **contextify**: use CHECK instead of `if` (Oguz Bastemur) [#3125](https://github.com/nodejs/node/pull/3125)
+* [[`f055a66a38`](https://github.com/nodejs/node/commit/f055a66a38)] - **crypto**: enable FIPS only when configured with it (Fedor Indutny) [#3153](https://github.com/nodejs/node/pull/3153)
+* [[`4c8d96bc30`](https://github.com/nodejs/node/commit/4c8d96bc30)] - **crypto**: add more keylen sanity checks in pbkdf2 (Johann) [#3029](https://github.com/nodejs/node/pull/3029)
+* [[`4c5940776c`](https://github.com/nodejs/node/commit/4c5940776c)] - **deps**: upgrade libuv to 1.7.5 (Saúl Ibarra Corretgé) [#3010](https://github.com/nodejs/node/pull/3010)
+* [[`5a9e795577`](https://github.com/nodejs/node/commit/5a9e795577)] - **deps**: upgrade V8 to 4.5.103.35 (Ali Ijaz Sheikh) [#3117](https://github.com/nodejs/node/pull/3117)
+* [[`925b29f959`](https://github.com/nodejs/node/commit/925b29f959)] - **deps**: backport f782159 from v8's upstream (Ben Noordhuis) [#3130](https://github.com/nodejs/node/pull/3130)
+* [[`039f73fa83`](https://github.com/nodejs/node/commit/039f73fa83)] - **deps**: remove and gitignore .bin directory (Ben Noordhuis) [#3004](https://github.com/nodejs/node/pull/3004)
+* [[`5fbb24812d`](https://github.com/nodejs/node/commit/5fbb24812d)] - **deps**: backport c281c15 from V8's upstream (Julien Gilli) [#3031](https://github.com/nodejs/node/pull/3031)
+* [[`6ee5d0f69f`](https://github.com/nodejs/node/commit/6ee5d0f69f)] - **dns**: add missing exports.BADNAME (Roman Reiss) [#3051](https://github.com/nodejs/node/pull/3051)
+* [[`f92aee7170`](https://github.com/nodejs/node/commit/f92aee7170)] - **doc**: fix outdated 'try/catch' statement in sync (Minwoo Jung) [#3087](https://github.com/nodejs/node/pull/3087)
+* [[`c7161f39e8`](https://github.com/nodejs/node/commit/c7161f39e8)] - **doc**: add TSC meeting minutes 2015-09-16 (Rod Vagg) [#3023](https://github.com/nodejs/node/pull/3023)
+* [[`928166c4a8`](https://github.com/nodejs/node/commit/928166c4a8)] - **doc**: copyedit fs.watch() information (Rich Trott) [#3097](https://github.com/nodejs/node/pull/3097)
+* [[`75d5dcea76`](https://github.com/nodejs/node/commit/75d5dcea76)] - **doc**: jenkins-iojs.nodesource.com -> ci.nodejs.org (Michał Gołębiowski) [#2886](https://github.com/nodejs/node/pull/2886)
+* [[`5c3f50b21d`](https://github.com/nodejs/node/commit/5c3f50b21d)] - **doc**: rearrange execSync and execFileSync (Laurent Fortin) [#2940](https://github.com/nodejs/node/pull/2940)
+* [[`4fc33ac11a`](https://github.com/nodejs/node/commit/4fc33ac11a)] - **doc**: make execFileSync in line with execFile (Laurent Fortin) [#2940](https://github.com/nodejs/node/pull/2940)
+* [[`a366e84b17`](https://github.com/nodejs/node/commit/a366e84b17)] - **doc**: fix typos in cluster & errors (reggi) [#3011](https://github.com/nodejs/node/pull/3011)
+* [[`52031e1bf1`](https://github.com/nodejs/node/commit/52031e1bf1)] - **doc**: switch LICENSE from closure-linter to eslint (P.S.V.R) [#3018](https://github.com/nodejs/node/pull/3018)
+* [[`b28f6a53bc`](https://github.com/nodejs/node/commit/b28f6a53bc)] - **docs**: Clarify assert.doesNotThrow behavior (Fabio Oliveira) [#2807](https://github.com/nodejs/node/pull/2807)
+* [[`99943e189d`](https://github.com/nodejs/node/commit/99943e189d)] - **http**: fix out-of-order 'finish' bug in pipelining (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+* [[`fb7a491d1c`](https://github.com/nodejs/node/commit/fb7a491d1c)] - **http_server**: pause socket properly (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+* [[`a0b35bfcf3`](https://github.com/nodejs/node/commit/a0b35bfcf3)] - **i18n**: add caller to removal list for bidi in ICU55 (Michael Dawson) [#3115](https://github.com/nodejs/node/pull/3115)
+* [[`ac2bce0b0c`](https://github.com/nodejs/node/commit/ac2bce0b0c)] - **path**: improve posixSplitPath performance (Evan Lucas) [#3034](https://github.com/nodejs/node/pull/3034)
+* [[`37cdeafa2f`](https://github.com/nodejs/node/commit/37cdeafa2f)] - **smalloc**: remove module (Brendan Ashworth) [#3099](https://github.com/nodejs/node/pull/3099)
+* [[`5ec5d0aa8b`](https://github.com/nodejs/node/commit/5ec5d0aa8b)] - **src**: internalize binding function property names (Ben Noordhuis) [#3060](https://github.com/nodejs/node/pull/3060)
+* [[`c8175fc2af`](https://github.com/nodejs/node/commit/c8175fc2af)] - **src**: internalize per-isolate string properties (Ben Noordhuis) [#3060](https://github.com/nodejs/node/pull/3060)
+* [[`9a593abc47`](https://github.com/nodejs/node/commit/9a593abc47)] - **src**: include signal.h in util.h (Cheng Zhao) [#3058](https://github.com/nodejs/node/pull/3058)
+* [[`fde0c6f321`](https://github.com/nodejs/node/commit/fde0c6f321)] - **src**: fix function and variable names in comments (Sakthipriyan Vairamani) [#3039](https://github.com/nodejs/node/pull/3039)
+* [[`1cc7b41ba4`](https://github.com/nodejs/node/commit/1cc7b41ba4)] - **stream_wrap**: support empty `TryWrite`s (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+* [[`9faf4c6fcf`](https://github.com/nodejs/node/commit/9faf4c6fcf)] - **test**: load common.js to test for global leaks (Rich Trott) [#3095](https://github.com/nodejs/node/pull/3095)
+* [[`0858c86374`](https://github.com/nodejs/node/commit/0858c86374)] - **test**: fix invalid variable name (Sakthipriyan Vairamani) [#3150](https://github.com/nodejs/node/pull/3150)
+* [[`1167171004`](https://github.com/nodejs/node/commit/1167171004)] - **test**: change calls to deprecated util.print() (Rich Trott) [#3083](https://github.com/nodejs/node/pull/3083)
+* [[`5ada45bf28`](https://github.com/nodejs/node/commit/5ada45bf28)] - **test**: replace deprecated util.debug() calls (Rich Trott) [#3082](https://github.com/nodejs/node/pull/3082)
+* [[`d8ab4e185d`](https://github.com/nodejs/node/commit/d8ab4e185d)] - **util**: optimize promise introspection (Ben Noordhuis) [#3130](https://github.com/nodejs/node/pull/3130)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.1.2/node-v4.1.2-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.1.2/node-v4.1.2-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.1.2/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.1.2/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.1.2/node-v4.1.2.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.1.2/node-v4.1.2.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.1.2/<br>
+Documentation: https://nodejs.org/docs/v4.1.2/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+058a5b07c9bda34074f4acad75ce03319402592a0482221f574e2fc4aed60131  node-v4.1.2-darwin-x64.tar.gz
+ea5495dab4139c291ecec2cfd618adea14e7df6794ce60873db3783d5897f7fd  node-v4.1.2-darwin-x64.tar.xz
+e8e17c8dc5afbf42d9533b37d32d7b44f105c425f13be4840c9e20cfcd251e78  node-v4.1.2-headers.tar.gz
+33651643226584cc83753633a61ad83e02ba399537e428468b793e06f1f3a188  node-v4.1.2-headers.tar.xz
+ae74c245b9592d52f8632a249a0bdd2eb664dcf7aaf5089d061f9c5b051f101a  node-v4.1.2-linux-arm64.tar.gz
+5a805fb6e3f3650c2048ac4eafb7654df12b34f1bcc94bd58ad93fc015ded9da  node-v4.1.2-linux-arm64.tar.xz
+834b36fa7e397f27f63f8fd56b77c15de4d9297c23f70679d0ceabd83662d950  node-v4.1.2-linux-armv6l.tar.gz
+32f0958afef2ebeb390a10e9e5e12a99ddba41a8cd17ad26038a8b27fd2e26d1  node-v4.1.2-linux-armv6l.tar.xz
+a8e38b1fae35c9b13f0c8cc57991d20a0267603c820028290236508930a522b0  node-v4.1.2-linux-armv7l.tar.gz
+d1fccdbedd27ab77aed20861f2dc0dcefb91512f198957ef9574bfe8d9329a0e  node-v4.1.2-linux-armv7l.tar.xz
+c39aefac81a2a4b0ae12df495e7dcdf6a8b75cbfe3a6efb649c8a4daa3aebdb6  node-v4.1.2-linux-x64.tar.gz
+b2d072cf2c87e368ae41931e8ef855d825d66a39f3092cd61e7e60123ad1b471  node-v4.1.2-linux-x64.tar.xz
+843599c40d3aabb1f60e33144647e6ead92bcfcefa7efca8396651ab92b5f3b9  node-v4.1.2-linux-x86.tar.gz
+4429573a7d26b4103c92f06a4a1384a0ad9476baffdfb081434f95248e1cfe41  node-v4.1.2-linux-x86.tar.xz
+d1e6e59bea645b4de42ca0b45f302eea32b0af55bccd7fee8da112eaebf6f221  node-v4.1.2.pkg
+5a783eb6b4feaee29f447fe6ea4bfd1b745bee2f00b48d5bbb78f6a2a6488e59  node-v4.1.2-sunos-x64.tar.gz
+9c6a3361deddf0712a87a751f679425451692453c407dba75618cf3c789ef637  node-v4.1.2-sunos-x64.tar.xz
+33719d820fca0a0b44f55ecb9d9de0ce8359211a98d802a3191dfb4e0e5f2c5c  node-v4.1.2-sunos-x86.tar.gz
+a09199e3383d855b84033c7441b19dae93172dbd1dd49505df8464f8aefa0005  node-v4.1.2-sunos-x86.tar.xz
+febec3703a3fea9b64c46100a7b6a4408250027aa8259a2a815fd2275d502c49  node-v4.1.2.tar.gz
+443c8251e812b1f2c4b3e9152a47df23c55567ade739e017e2c0ca0869b71e74  node-v4.1.2.tar.xz
+9dce96b418ee81f4552601e936312a503d8f17a6ef34936fb562f6653a933071  node-v4.1.2-x64.msi
+18f003ffb82b832c39eb94d5e167c4b0e965e4a28fefda909871375b43a6d94b  node-v4.1.2-x86.msi
+f80b66e561125ec54f3ac3ad4098847581493ae1be850eceadc3255b5f5ed843  win-x64/node.exe
+64f2738aef37a64356c290dd23b72a4171eafb9bec2c2f57208fa7638a06120b  win-x64/node.lib
+e1fddb067d39edcbe187b3dfd276bb89cb5282d21f2eda7331b46005561ffa0f  win-x86/node.exe
+80ba09d65813acebf005102ed5cd52a020ec0fbdef09928f3a3667c25cdfab47  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWEu1KAAoJEMJzeS99g1RdSpsIALZ4L9a6jqUmpfig5tNGd8++
+IlzCDYIqKkrN570V12rMpmFLSRKnE8kl08t0fcy4XbLCBpBYVoIlF5aztUHEjgSz
+O2NijWuvygN2rpQWNMKoa0/a3enN5WeduRTm7/0pJvThy1k79tYNA2ti/7aMt554
+zlnXxTWYoimz/trfl9ZSBOGKY3Qv8EecKhMw4D2PuTXrUYsOR1GdJikj4nwVgGpo
+X+T+h2/yoCcxgCVcruckcmJOYMqKRuu+p5EvtRxycgC5ja7/2XrM/ywgJ33VcJXL
+ETnnmI3fSDhXKo9JdAA4mtHMLeIBHUjMu253Dyq1NmbUrEcONF6TBMhuPTM4PwI=
+=SCKn
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v4.2.0.md b/locale/uk/blog/release/v4.2.0.md
new file mode 100755
index 0000000000000..dd25cf7a84253
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.0.md
@@ -0,0 +1,170 @@
+---
+date: 2015-10-12T18:20:40.988Z
+version: 4.2.0
+category: release
+title: Node v4.2.0 (LTS)
+slug: node-v4-2-0-stable
+layout: blog-post.hbs
+---
+We are proud to announce the release of Node.js v4.2.0 "Argon", the first  release covered under the new [Long Term Support](https://github.com/nodejs/LTS) plan!
+
+As an LTS release, support for v4.x will continue for a period of 30 months from today. This means that individuals and businesses building on Node.js will have a stable and supported platform on which to grow. For more details on what LTS means for Node.js, see Rod Vagg's [blog post](https://nodesource.com/blog/essential-steps-long-term-support-for-nodejs).
+
+### Argon?
+
+To better differentiate LTS releases from regular Node.js releases, we have introduced a naming convention based on the Periodic Table of Elements that applies only to LTS releases. The name selected for v4.2.0 is "Argon", so as to be in alphabetical order by the first letter.
+
+Developers can easily determine if they are working with an LTS version of Node.js by checking the `process.release.lts` property within node. This property will be undefined in regular releases.
+
+```bash
+$ node -v
+v4.2.0
+$ node -pe process.release.lts
+Argon
+```
+
+### Notable changes
+
+The first Node.js LTS release! See https://github.com/nodejs/LTS/ for details of the LTS process.
+
+* **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) [#3281](https://github.com/nodejs/node/pull/3281)
+* **node**:
+  - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) [#2411](https://github.com/nodejs/node/pull/2411)
+  - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) [#3102](https://github.com/nodejs/node/pull/3102)
+  - Added `process.release.lts` to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg) [#3212](https://github.com/nodejs/node/pull/3212)
+* **npm**: Upgraded to npm 2.14.7 from 2.14.4, see [release notes](https://github.com/npm/npm/releases/tag/v2.14.7) for full details (Kat Marchán) [#3299](https://github.com/nodejs/node/pull/3299)
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+
+* [[`8383c4fe00`](https://github.com/nodejs/node/commit/8383c4fe00)] - **assert**: support arrow functions in .throws() (Ben Noordhuis) [#3276](https://github.com/nodejs/node/pull/3276)
+* [[`3eaa593a32`](https://github.com/nodejs/node/commit/3eaa593a32)] - **async_wrap**: correctly pass parent to init callback (Trevor Norris) [#3216](https://github.com/nodejs/node/pull/3216)
+* [[`54795620f6`](https://github.com/nodejs/node/commit/54795620f6)] - **buffer**: don't abort on prototype getters (Trevor Norris) [#3302](https://github.com/nodejs/node/pull/3302)
+* [[`660f7591c8`](https://github.com/nodejs/node/commit/660f7591c8)] - **buffer**: FreeCallback should be tied to ArrayBuffer (Fedor Indutny) [#3198](https://github.com/nodejs/node/pull/3198)
+* [[`651a5b51eb`](https://github.com/nodejs/node/commit/651a5b51eb)] - **buffer**: only check if instance is Uint8Array (Trevor Norris) [#3080](https://github.com/nodejs/node/pull/3080)
+* [[`d5a1b1ad7c`](https://github.com/nodejs/node/commit/d5a1b1ad7c)] - **buffer**: clean up usage of __proto__ (Trevor Norris) [#3080](https://github.com/nodejs/node/pull/3080)
+* [[`af24376e18`](https://github.com/nodejs/node/commit/af24376e18)] - **build**: Intl: deps: bump ICU to 56.1 (GA) (Steven R. Loomis) [#3281](https://github.com/nodejs/node/pull/3281)
+* [[`9136359d57`](https://github.com/nodejs/node/commit/9136359d57)] - **build**: make icu download path customizable (Johan Bergström) [#3200](https://github.com/nodejs/node/pull/3200)
+* [[`b3c5ad10a8`](https://github.com/nodejs/node/commit/b3c5ad10a8)] - **build**: add --with-arm-fpu option (Jérémy Lal) [#3228](https://github.com/nodejs/node/pull/3228)
+* [[`f00f3268e4`](https://github.com/nodejs/node/commit/f00f3268e4)] - **build**: intl: avoid 'duplicate main()' on ICU 56 (Steven R. Loomis) [#3066](https://github.com/nodejs/node/pull/3066)
+* [[`071c72a6a3`](https://github.com/nodejs/node/commit/071c72a6a3)] - **deps**: upgrade to npm 2.14.7 (Kat Marchán) [#3299](https://github.com/nodejs/node/pull/3299)
+* [[`8b50e95f06`](https://github.com/nodejs/node/commit/8b50e95f06)] - **(SEMVER-MINOR)** **deps**: backport 1ee712a from V8 upstream (Julien Gilli) [#3036](https://github.com/nodejs/node/pull/3036)
+* [[`747271372f`](https://github.com/nodejs/node/commit/747271372f)] - **doc**: update the assert module summary (David Boivin) [#2799](https://github.com/nodejs/node/pull/2799)
+* [[`0d506556b0`](https://github.com/nodejs/node/commit/0d506556b0)] - **doc**: replace node-gyp link with nodejs/node-gyp (Roman Klauke) [#3320](https://github.com/nodejs/node/pull/3320)
+* [[`40a159e4f4`](https://github.com/nodejs/node/commit/40a159e4f4)] - **doc**: Amend capitalization of word JavaScript (Dave Hodder) [#3285](https://github.com/nodejs/node/pull/3285)
+* [[`6dd34761fd`](https://github.com/nodejs/node/commit/6dd34761fd)] - **doc**: add method links in dns.markdown (Alejandro Oviedo) [#3196](https://github.com/nodejs/node/pull/3196)
+* [[`333e8336be`](https://github.com/nodejs/node/commit/333e8336be)] - **doc**: add method links in child_process.markdown (Alejandro Oviedo) [#3186](https://github.com/nodejs/node/pull/3186)
+* [[`0cfc6d39ca`](https://github.com/nodejs/node/commit/0cfc6d39ca)] - **doc**: recommend Infinity on emitter.setMaxListeners (Jason Karns) [#2559](https://github.com/nodejs/node/pull/2559)
+* [[`d4fc6d93ef`](https://github.com/nodejs/node/commit/d4fc6d93ef)] - **doc**: add help repo link to CONTRIBUTING.md (Doug Shamoo) [#3233](https://github.com/nodejs/node/pull/3233)
+* [[`28aac7f19d`](https://github.com/nodejs/node/commit/28aac7f19d)] - **doc**: add TLS session resumption example (Roman Reiss) [#3147](https://github.com/nodejs/node/pull/3147)
+* [[`365cf22cce`](https://github.com/nodejs/node/commit/365cf22cce)] - **doc**: update AUTHORS list (Rod Vagg) [#3211](https://github.com/nodejs/node/pull/3211)
+* [[`d4399613b7`](https://github.com/nodejs/node/commit/d4399613b7)] - **doc**: standardize references to userland (Martial) [#3192](https://github.com/nodejs/node/pull/3192)
+* [[`75de258376`](https://github.com/nodejs/node/commit/75de258376)] - **doc**: fix spelling in Buffer documentation (Rod Machen) [#3226](https://github.com/nodejs/node/pull/3226)
+* [[`725c7276dd`](https://github.com/nodejs/node/commit/725c7276dd)] - **doc**: fix README.md link to joyent/node intl wiki (Steven R. Loomis) [#3067](https://github.com/nodejs/node/pull/3067)
+* [[`4a35ba4966`](https://github.com/nodejs/node/commit/4a35ba4966)] - **(SEMVER-MINOR)** **fs**: include filename in watch errors (charlierudolph) [#2748](https://github.com/nodejs/node/pull/2748)
+* [[`2ddbbfd164`](https://github.com/nodejs/node/commit/2ddbbfd164)] - **http**: cork/uncork before flushing pipelined res (Fedor Indutny) [#3172](https://github.com/nodejs/node/pull/3172)
+* [[`f638402e2f`](https://github.com/nodejs/node/commit/f638402e2f)] - **http**: add comment about `outputSize` in res/server (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+* [[`1850879b0e`](https://github.com/nodejs/node/commit/1850879b0e)] - **js_stream**: prevent abort if isalive doesn't exist (Trevor Norris) [#3282](https://github.com/nodejs/node/pull/3282)
+* [[`63644dd1cd`](https://github.com/nodejs/node/commit/63644dd1cd)] - **lib**: remove redundant code, add tests in timers.js (Rich Trott) [#3143](https://github.com/nodejs/node/pull/3143)
+* [[`74f443583c`](https://github.com/nodejs/node/commit/74f443583c)] - **module**: use UNC paths when loading native addons (Justin Chase) [#2965](https://github.com/nodejs/node/pull/2965)
+* [[`01cb3fc36b`](https://github.com/nodejs/node/commit/01cb3fc36b)] - **net**: don't throw on bytesWritten access (Trevor Norris) [#3305](https://github.com/nodejs/node/pull/3305)
+* [[`9d65528b01`](https://github.com/nodejs/node/commit/9d65528b01)] - **(SEMVER-MINOR)** **node**: add -c|--check CLI arg to syntax check script (Dave Eddy) [#2411](https://github.com/nodejs/node/pull/2411)
+* [[`42b936e78d`](https://github.com/nodejs/node/commit/42b936e78d)] - **(SEMVER-MINOR)** **src**: add process.release.lts property (Rod Vagg) [#3212](https://github.com/nodejs/node/pull/3212)
+* [[`589287b2e3`](https://github.com/nodejs/node/commit/589287b2e3)] - **src**: convert BE-utf16-string to LE before search (Karl Skomski) [#3295](https://github.com/nodejs/node/pull/3295)
+* [[`2314378f06`](https://github.com/nodejs/node/commit/2314378f06)] - **src**: fix u-a-free if uv returns err in ASYNC_CALL (Karl Skomski) [#3049](https://github.com/nodejs/node/pull/3049)
+* [[`d99336a391`](https://github.com/nodejs/node/commit/d99336a391)] - **(SEMVER-MINOR)** **src**: replace naive search in Buffer::IndexOf (Karl Skomski) [#2539](https://github.com/nodejs/node/pull/2539)
+* [[`546e8333ba`](https://github.com/nodejs/node/commit/546e8333ba)] - **(SEMVER-MINOR)** **src**: fix --abort-on-uncaught-exception (Jeremy Whitlock) [#3036](https://github.com/nodejs/node/pull/3036)
+* [[`7271cb047c`](https://github.com/nodejs/node/commit/7271cb047c)] - **(SEMVER-MINOR)** **src**: add process.versions.icu (Evan Lucas) [#3102](https://github.com/nodejs/node/pull/3102)
+* [[`7b9f78acb2`](https://github.com/nodejs/node/commit/7b9f78acb2)] - **stream**: avoid pause with unpipe in buffered write (Brian White) [#2325](https://github.com/nodejs/node/pull/2325)
+* [[`f0f8afd879`](https://github.com/nodejs/node/commit/f0f8afd879)] - **test**: remove common.inspect() (Rich Trott) [#3257](https://github.com/nodejs/node/pull/3257)
+* [[`5ca4f6f8bd`](https://github.com/nodejs/node/commit/5ca4f6f8bd)] - **test**: test `util` rather than `common` (Rich Trott) [#3256](https://github.com/nodejs/node/pull/3256)
+* [[`7a5ae34345`](https://github.com/nodejs/node/commit/7a5ae34345)] - **test**: refresh temp directory when using pipe (Rich Trott) [#3231](https://github.com/nodejs/node/pull/3231)
+* [[`7c85557ef0`](https://github.com/nodejs/node/commit/7c85557ef0)] - **test**: Fix test-fs-read-stream-fd-leak race cond (Junliang Yan) [#3218](https://github.com/nodejs/node/pull/3218)
+* [[`26a7ec6960`](https://github.com/nodejs/node/commit/26a7ec6960)] - **test**: fix losing original env vars issue (Junliang Yan) [#3190](https://github.com/nodejs/node/pull/3190)
+* [[`e922716192`](https://github.com/nodejs/node/commit/e922716192)] - **test**: remove deprecated error logging (Rich Trott) [#3079](https://github.com/nodejs/node/pull/3079)
+* [[`8f29d95a8c`](https://github.com/nodejs/node/commit/8f29d95a8c)] - **test**: report timeout in TapReporter (Karl Skomski) [#2647](https://github.com/nodejs/node/pull/2647)
+* [[`2d0fe4c657`](https://github.com/nodejs/node/commit/2d0fe4c657)] - **test**: linting for buffer-free-callback test (Rich Trott) [#3230](https://github.com/nodejs/node/pull/3230)
+* [[`70c9e4337e`](https://github.com/nodejs/node/commit/70c9e4337e)] - **test**: make common.js mandatory via linting rule (Rich Trott) [#3157](https://github.com/nodejs/node/pull/3157)
+* [[`b7179562aa`](https://github.com/nodejs/node/commit/b7179562aa)] - **test**: load common.js in all tests (Rich Trott) [#3157](https://github.com/nodejs/node/pull/3157)
+* [[`bab555a1c1`](https://github.com/nodejs/node/commit/bab555a1c1)] - **test**: speed up stringbytes-external test (Evan Lucas) [#3005](https://github.com/nodejs/node/pull/3005)
+* [[`ddf258376d`](https://github.com/nodejs/node/commit/ddf258376d)] - **test**: use normalize() for unicode paths (Roman Reiss) [#3007](https://github.com/nodejs/node/pull/3007)
+* [[`46876d519c`](https://github.com/nodejs/node/commit/46876d519c)] - **test**: remove arguments.callee usage (Roman Reiss) [#3167](https://github.com/nodejs/node/pull/3167)
+* [[`af10df6108`](https://github.com/nodejs/node/commit/af10df6108)] - **tls**: use parent handle's close callback (Fedor Indutny) [#2991](https://github.com/nodejs/node/pull/2991)
+* [[`9c2748bad1`](https://github.com/nodejs/node/commit/9c2748bad1)] - **tools**: remove leftover license boilerplate (Nathan Rajlich) [#3225](https://github.com/nodejs/node/pull/3225)
+* [[`5d9f83ff2a`](https://github.com/nodejs/node/commit/5d9f83ff2a)] - **tools**: apply linting to custom rules code (Rich Trott) [#3195](https://github.com/nodejs/node/pull/3195)
+* [[`18a8b2ec73`](https://github.com/nodejs/node/commit/18a8b2ec73)] - **tools**: remove unused gflags module (Ben Noordhuis) [#3220](https://github.com/nodejs/node/pull/3220)
+* [[`e0fffca836`](https://github.com/nodejs/node/commit/e0fffca836)] - **util**: fix for inspecting promises (Evan Lucas) [#3221](https://github.com/nodejs/node/pull/3221)
+* [[`8dfdee3733`](https://github.com/nodejs/node/commit/8dfdee3733)] - **util**: correctly inspect Map/Set Iterators (Evan Lucas) [#3119](https://github.com/nodejs/node/pull/3119)
+* [[`b5c51fdba0`](https://github.com/nodejs/node/commit/b5c51fdba0)] - **util**: fix check for Array constructor (Evan Lucas) [#3119](https://github.com/nodejs/node/pull/3119)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.0/node-v4.2.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.0/node-v4.2.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.0/node-v4.2.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: *Coming soon*<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.0/node-v4.2.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.0/node-v4.2.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.0/<br>
+Documentation: https://nodejs.org/docs/v4.2.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+078c9a2c2fbfb603700d94b618df3b8b211e10f361bced5e4439142715aebde5  node-v4.2.0-darwin-x64.tar.gz
+5ca8495fd39f5fccaaaad4a4c10602723b4146efd8cb2c933f1733cf0f2bd2b3  node-v4.2.0-darwin-x64.tar.xz
+b82bd1c46b49599e5ee6565b0b4ecb5ef6f3af573f897f9df2470eafe255feed  node-v4.2.0-headers.tar.gz
+2cb4beaaacd2c097cd2ea5cc6de47427ee9e495cc7283a1e0476ae3a727e7cab  node-v4.2.0-headers.tar.xz
+ae67d6ddcb72505937982d6a0bcb031b3522f7abc11d9e2d449ea021a5f75faf  node-v4.2.0-linux-arm64.tar.gz
+6b96bc7de2e085ba04213aeb353396dd6ae5fcf6076c62598a83d7c009b4da3a  node-v4.2.0-linux-arm64.tar.xz
+c1844dd131020b2b2982de974d73b051159776fe3ebf6fa91f08a2f5e8c46555  node-v4.2.0-linux-armv7l.tar.gz
+c28312e164ea13dc6f2027926d55a7460ca7051c6f7e8828203fc686027d27e0  node-v4.2.0-linux-armv7l.tar.xz
+98b60c86d541f44c5d07111f9ffc9a81848f976cfbe84f71cb9c7d6bfd34e1a4  node-v4.2.0-linux-x64.tar.gz
+fd4830966fa1afd4ddbbde6b1e7fb581ce99917ad5dd41da9cb9b27d191c16a1  node-v4.2.0-linux-x64.tar.xz
+bc5e0791c23d897ea6c83976dd14eec8ac33f74188806012992aca335c4e9214  node-v4.2.0-linux-x86.tar.gz
+aff372b9e6f7ccfef16c55cda5c9666847322e24c8bc574e6081f8b20ef1fe0a  node-v4.2.0-linux-x86.tar.xz
+83005cd68ebf94c528b1da28cc3915df56426224ce6f6337ad2b067be87a00b0  node-v4.2.0.pkg
+d074ae0ab26f2f680adf7b94cfae0a8eac5ae4dcf083594a361b837fea6fdc72  node-v4.2.0-sunos-x64.tar.gz
+c24dd20cc4eb296418fd13913c60910929698488be4079441aeb34e5a4a23295  node-v4.2.0-sunos-x64.tar.xz
+fc753685f937d338f1367614ca49158d446e29b35694fac6b8e6be262db5ec38  node-v4.2.0-sunos-x86.tar.gz
+77cf3a17555dc83871c61bfbfc7fea9373c4664fb174e4b90281a5541be9aa42  node-v4.2.0-sunos-x86.tar.xz
+94ea40efeb598fed6e1a78990b698da73275c49876ec551dc36e11513c99fb6b  node-v4.2.0.tar.gz
+611e899c10fc26e077f26d70802728e87e743f9bd0c9ad9b4a9b1aeb6a45b511  node-v4.2.0.tar.xz
+9be6a2f95fb17c70aada09e0c5e2dadd2ce2bb2c5ac83bcce47d0f6c290ba15c  node-v4.2.0-x64.msi
+6f1c92772369ffb82d9eed586d74d343ea0d61bb9770746aae7589779d39a9af  node-v4.2.0-x86.msi
+701498dd467ccfcc2dd083c53212654d9bc04e5289e1021a6e411e758c411eeb  win-x64/node.exe
+2ce13cf0c50a0df6d6591ea84201a318877b5eb39eeac3dc189130da19c34685  win-x64/node.lib
+cf75e01de1c397342a01fa4d682851ae0694554c921604a27415c7681c02f7be  win-x86/node.exe
+4eca7dbfa577f015bb546d74ca330ce12ee5605924e463b7451b72f041a9b772  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWG/msAAoJEHNBsVwHCHesiwQH/2MWeonw7cb2fOmmTA2nItB7
+hpVUwnMwN1eziOZhZmG2V+iEd0h7QKWUWpVUrPyr6LMUndesa6g1oD9r93u02Wje
+tSbxFgg28lUyTWyGhL18ZNapZGi4HYpxaJBgZ/szjk1nDmVJ80XMnDh7qKQx19/X
+Ccwkqq3epkuix5utvUrj6+KAtxqeIYEoW5p+7OaRf+KzZNle6oD3JzjwZ7w8FjHB
+3AVR/P95e2VGoIotlxG1SgF8Qe+rPqAj9xiKTKgHuPwBWqH09ulQcRiiMw/5xXal
+dSkkiIu/sks+/MKTU+ltR2emQq5Ck75bY1Gvn1ki+jNP1KZcmYkgRoHjH0RkSYE=
+=gqB4
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.2.1.md b/locale/uk/blog/release/v4.2.1.md
new file mode 100755
index 0000000000000..411cefb75ce68
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.1.md
@@ -0,0 +1,93 @@
+---
+date: 2015-10-13T17:42:03.184Z
+version: 4.2.1
+category: release
+title: Node v4.2.1 (LTS)
+slug: node-v4-2-1-lts
+layout: blog-post.hbs
+---
+
+### Notable changes
+
+* Includes fixes for two regressions
+  - Assertion error in WeakCallback - see [#3329](https://github.com/nodejs/node/pull/3329)
+  - Undefined timeout regression - see [#3331](https://github.com/nodejs/node/pull/3331)
+
+### Known issues
+
+* When a server queues a large amount of data to send to a client over a pipelined HTTP connection, the underlying socket may be destroyed. See [#3332](https://github.com/nodejs/node/issues/3332) and [#3342](https://github.com/nodejs/node/pull/3342).
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`b3cbd13340`](https://github.com/nodejs/node/commit/b3cbd13340)] - **buffer**: fix assertion error in WeakCallback (Fedor Indutny) [#3329](https://github.com/nodejs/node/pull/3329)
+* [[`102cb7288c`](https://github.com/nodejs/node/commit/102cb7288c)] - **doc**: label v4.2.0 as LTS in changelog heading (Rod Vagg) [#3343](https://github.com/nodejs/node/pull/3343)
+* [[`c245a199a7`](https://github.com/nodejs/node/commit/c245a199a7)] - **lib**: fix undefined timeout regression (Ryan Graham) [#3331](https://github.com/nodejs/node/pull/3331
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.1/node-v4.2.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.1/node-v4.2.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.1/node-v4.2.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.1/node-v4.2.1-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.1/node-v4.2.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.1/<br>
+Documentation: https://nodejs.org/docs/v4.2.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+658686795fac9669d411ac5c5be2da8159058e386767322d8d8151dcdb4810b9  node-v4.2.1-darwin-x64.tar.gz
+d2c1ffb5c9f1d24f1f49652600bb2056b13afe068ba7d80bfd1009423ead8941  node-v4.2.1-darwin-x64.tar.xz
+b242fd0fa83748d95cc3e68d14579b629960b0436d65da9d86907eef27b96fc1  node-v4.2.1-headers.tar.gz
+b1416eca3f1c56e049d924d31b343d57a735d4e422c4288bf4c2ca453cb6bcf2  node-v4.2.1-headers.tar.xz
+05df4aeb8a53798f8b10074600518040fc317f2919f9755aeab57b0aaf7227b0  node-v4.2.1-linux-arm64.tar.gz
+ba5c0705f0d69306d978faac14ed37725b71b4e2c41192019e8e4aae239b2683  node-v4.2.1-linux-arm64.tar.xz
+6f29286464efda4a362d9464d82733398b98882051c20c0f190004480b6e506a  node-v4.2.1-linux-armv6l.tar.gz
+5a99151840df5dc2f9ec4562f6174ad06d0d52949256610e89ee8272e643cf95  node-v4.2.1-linux-armv6l.tar.xz
+fb4fbef9306962e800804ab5ba615c06bba28deb4e7a3e945a291dba986ef816  node-v4.2.1-linux-armv7l.tar.gz
+7699ee39c9bc92208ef38ab6d61ddee46cad2978b06095b2ca54a7a116c47d9a  node-v4.2.1-linux-armv7l.tar.xz
+e766e387934e17daaad92d0460ed76f756655da62b627a5c9cc07faea4a0b824  node-v4.2.1-linux-x64.tar.gz
+346f6c1b96bd5fc0a2a100e78deceff9e1045f5ccf0ba66401cd8d37d78d1b23  node-v4.2.1-linux-x64.tar.xz
+97b5ccea7044073c87a21bcc4b0762f4a6bd77db9cc958206f684ecdfeb89b1f  node-v4.2.1-linux-x86.tar.gz
+2a7a16e6066ddd724400634ba80266d6994036d0772545bcedc81c80d2e84e2b  node-v4.2.1-linux-x86.tar.xz
+688df0a12461f378b296f69e8ae2c1cbb974b0216278624815bce7dcfea080c2  node-v4.2.1.pkg
+acec44790ff0069620c0fd03945d14b9f97c7ccb0a0450f766a5cbe4a906510b  node-v4.2.1-sunos-x64.tar.gz
+72d1cb21347af731f594f85fa177140b2c3e015b8c1cb65a63a082999cd390e8  node-v4.2.1-sunos-x64.tar.xz
+d7bf8dcf353115b5e55bf64d25c2c34fa2d237e201e46dab97ae3d8e3f051583  node-v4.2.1-sunos-x86.tar.gz
+fb047d9b3db08fba2c3021d574a3ffd6f0f3e0208735035ed245926f0977ab8a  node-v4.2.1-sunos-x86.tar.xz
+8861b9f4c3b4db380fcda19a710c0430c3d62d03ee176c64db63eef95a672663  node-v4.2.1.tar.gz
+0528c60cf75371314ad0e7b19f9fd586d98a220d307d03e163b323b67458b7be  node-v4.2.1.tar.xz
+e460a71ea9aa4d743387a20319042de203de837cb613be0737b6ca368480302d  node-v4.2.1-x64.msi
+df70335dc34d48cf03c9074d84ff330f4d1fa0eb12b5225da91ad4f7c1835318  node-v4.2.1-x86.msi
+92744bfa525cd51ea3bf5ac810a9e3e9306f6fe4ac44847a8aefdd674701e8e6  win-x64/node.exe
+d5369e749dc6181226f8a91c6c7d590596175943301fd92455dbea5de7c6b6f6  win-x64/node.lib
+c22fcbf2f1db7ff3cd71b4c771f277fe8d75caff8689a3be50aeee1a7682820e  win-x86/node.exe
+98f0b03cae561cb59fd602c51a35b326e561fe9bc8ad6cc9d5ec32aa2fe2acbd  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWHmkUAAoJEHNBsVwHCHesq4oH/1ghNOtL/4uVfHPeQtmAR/lW
++IHOHno346EpZDR0afOCTDwB+GyY5gbDdmb1CEwmFN5IstRPM4Jow6W2JwDNwOYD
+QAIzzx/+sABFJZk3iuppIUbSA6ziP/L0B8dGxel96Iq02Zf9pv3NY5sxI744SMMF
+Mr5l7/FIyb4dd9H3QiX3mxvbVj8q7Oj5e2ROlqn5mKm5HszFVhDwu1PjR5/mjazC
+EB2rRJuIwzUO3VEe6ApmQCO26yLZA/CPwl41z9oQvF+j4lHHb6DkDDX7MQu3EWd7
+hqsK2xQ6oOAzcVOP5edwYgGVH4N8hlHaHTVfFezgcri83ruMxqmRA4cYdLb3yOk=
+=dRAV
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.2.2.md b/locale/uk/blog/release/v4.2.2.md
new file mode 100755
index 0000000000000..ef3f2dc77487c
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.2.md
@@ -0,0 +1,165 @@
+---
+date: 2015-11-03T20:18:34.527Z
+version: 4.2.2
+category: release
+title: Node v4.2.2 (LTS)
+slug: node-v4-2-2-lts
+layout: blog-post.hbs
+author: James M Snell
+---
+
+### Notable changes
+
+This is an LTS maintenance release that addresses a number of issues:
+
+* [[`1d0f2cbf87`](https://github.com/nodejs/node/commit/1d0f2cbf87)] - **buffer**: fix value check for writeUInt{B,L}E (Trevor Norris) [#3500](https://github.com/nodejs/node/pull/3500)
+* [[`2a45b72b4a`](https://github.com/nodejs/node/commit/2a45b72b4a)] - **buffer**: don't CHECK on zero-sized realloc (Ben Noordhuis) [#3499](https://github.com/nodejs/node/pull/3499)
+* [[`a6469e901a`](https://github.com/nodejs/node/commit/a6469e901a)] - **deps**: backport 010897c from V8 upstream (Ali Ijaz Sheikh) [#3520](https://github.com/nodejs/node/pull/3520)
+* [[`cadee67c25`](https://github.com/nodejs/node/commit/cadee67c25)] - **deps**: backport 8d6a228 from the v8's upstream (Fedor Indutny) [#3549](https://github.com/nodejs/node/pull/3549)
+* [[`46c8c94055`](https://github.com/nodejs/node/commit/46c8c94055)] - **fs**: reduced duplicate code in fs.write() (ronkorving) [#2947](https://github.com/nodejs/node/pull/2947)
+* [[`0427cdf094`](https://github.com/nodejs/node/commit/0427cdf094)] - **http**: fix stalled pipeline bug (Fedor Indutny) [#3342](https://github.com/nodejs/node/pull/3342)
+* [[`2109708186`](https://github.com/nodejs/node/commit/2109708186)] - **lib**: fix cluster handle leak (Rich Trott) [#3510](https://github.com/nodejs/node/pull/3510)
+* [[`f49c7c6955`](https://github.com/nodejs/node/commit/f49c7c6955)] - **lib**: avoid REPL exit on completion error (Rich Trott) [#3358](https://github.com/nodejs/node/pull/3358)
+* [[`8a2c4aeeaa`](https://github.com/nodejs/node/commit/8a2c4aeeaa)] - **repl**: handle comments properly (Sakthipriyan Vairamani) [#3515](https://github.com/nodejs/node/pull/3515)
+* [[`a04408acce`](https://github.com/nodejs/node/commit/a04408acce)] - **repl**: limit persistent history correctly on load (Jeremiah Senkpiel) [#2356](https://github.com/nodejs/node/pull/2356)
+* [[`3bafe1a59b`](https://github.com/nodejs/node/commit/3bafe1a59b)] - **src**: fix race condition in debug signal on exit (Ben Noordhuis) [#3528](https://github.com/nodejs/node/pull/3528)
+* [[`fe01d0df7a`](https://github.com/nodejs/node/commit/fe01d0df7a)] - **src**: fix exception message encoding on Windows (Brian White) [#3288](https://github.com/nodejs/node/pull/3288)
+* [[`4bac5d9ddf`](https://github.com/nodejs/node/commit/4bac5d9ddf)] - **stream**: avoid unnecessary concat of a single buffer. (Calvin Metcalf) [#3300](https://github.com/nodejs/node/pull/3300)
+* [[`8d78d687d5`](https://github.com/nodejs/node/commit/8d78d687d5)] - **timers**: reuse timer in `setTimeout().unref()` (Fedor Indutny) [#3407](https://github.com/nodejs/node/pull/3407)
+* [[`e69c869399`](https://github.com/nodejs/node/commit/e69c869399)] - **tls**: TLSSocket options default isServer false (Yuval Brik) [#2614](https://github.com/nodejs/node/pull/2614)
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`1d0f2cbf87`](https://github.com/nodejs/node/commit/1d0f2cbf87)] - **buffer**: fix value check for writeUInt{B,L}E (Trevor Norris) [#3500](https://github.com/nodejs/node/pull/3500)
+* [[`2a45b72b4a`](https://github.com/nodejs/node/commit/2a45b72b4a)] - **buffer**: don't CHECK on zero-sized realloc (Ben Noordhuis) [#3499](https://github.com/nodejs/node/pull/3499)
+* [[`dc655e1dd2`](https://github.com/nodejs/node/commit/dc655e1dd2)] - **build**: rectify --link-module help text (P.S.V.R) [#3379](https://github.com/nodejs/node/pull/3379)
+* [[`a6469e901a`](https://github.com/nodejs/node/commit/a6469e901a)] - **deps**: backport 010897c from V8 upstream (Ali Ijaz Sheikh) [#3520](https://github.com/nodejs/node/pull/3520)
+* [[`cadee67c25`](https://github.com/nodejs/node/commit/cadee67c25)] - **deps**: backport 8d6a228 from the v8's upstream (Fedor Indutny) [#3549](https://github.com/nodejs/node/pull/3549)
+* [[`1ebd35550b`](https://github.com/nodejs/node/commit/1ebd35550b)] - **doc**: fix typos in changelog (reggi) [#3291](https://github.com/nodejs/node/pull/3291)
+* [[`fbd93d4c1c`](https://github.com/nodejs/node/commit/fbd93d4c1c)] - **doc**: more use-cases for promise events (Domenic Denicola) [#3438](https://github.com/nodejs/node/pull/3438)
+* [[`6ceb9af407`](https://github.com/nodejs/node/commit/6ceb9af407)] - **doc**: remove old note, 'cluster' is marked stable (Balázs Galambosi) [#3314](https://github.com/nodejs/node/pull/3314)
+* [[`a5f0d64ddc`](https://github.com/nodejs/node/commit/a5f0d64ddc)] - **doc**: createServer's key option can be an array (Sakthipriyan Vairamani) [#3123](https://github.com/nodejs/node/pull/3123)
+* [[`317e0ec6b3`](https://github.com/nodejs/node/commit/317e0ec6b3)] - **doc**: binary encoding is not deprecated (Trevor Norris) [#3441](https://github.com/nodejs/node/pull/3441)
+* [[`b422f6ee1a`](https://github.com/nodejs/node/commit/b422f6ee1a)] - **doc**: mention the behaviour if URL is invalid (Sakthipriyan Vairamani) [#2966](https://github.com/nodejs/node/pull/2966)
+* [[`bc29aad22b`](https://github.com/nodejs/node/commit/bc29aad22b)] - **doc**: fix indent in tls resumption example (Roman Reiss) [#3372](https://github.com/nodejs/node/pull/3372)
+* [[`313877bd8f`](https://github.com/nodejs/node/commit/313877bd8f)] - **doc**: fix typo in changelog (Timothy Gu) [#3353](https://github.com/nodejs/node/pull/3353)
+* [[`4be432862a`](https://github.com/nodejs/node/commit/4be432862a)] - **doc**: show keylen in pbkdf2 as a byte length (calebboyd) [#3334](https://github.com/nodejs/node/pull/3334)
+* [[`23a1140ddb`](https://github.com/nodejs/node/commit/23a1140ddb)] - **doc**: add information about Assert behavior and maintenance (Rich Trott) [#3330](https://github.com/nodejs/node/pull/3330)
+* [[`e04cb1e1fc`](https://github.com/nodejs/node/commit/e04cb1e1fc)] - **doc**: clarify API buffer.concat (Martii) [#3255](https://github.com/nodejs/node/pull/3255)
+* [[`eae714c370`](https://github.com/nodejs/node/commit/eae714c370)] - **doc**: clarify the use of `option.detached` (Kyle Smith) [#3250](https://github.com/nodejs/node/pull/3250)
+* [[`b884899e67`](https://github.com/nodejs/node/commit/b884899e67)] - **doc**: label v4.2.1 as LTS in changelog heading (Phillip Johnsen) [#3360](https://github.com/nodejs/node/pull/3360)
+* [[`9120a04981`](https://github.com/nodejs/node/commit/9120a04981)] - **docs**: add missing shell option to execSync (fansworld-claudio) [#3440](https://github.com/nodejs/node/pull/3440)
+* [[`46c8c94055`](https://github.com/nodejs/node/commit/46c8c94055)] - **fs**: reduced duplicate code in fs.write() (ronkorving) [#2947](https://github.com/nodejs/node/pull/2947)
+* [[`0427cdf094`](https://github.com/nodejs/node/commit/0427cdf094)] - **http**: fix stalled pipeline bug (Fedor Indutny) [#3342](https://github.com/nodejs/node/pull/3342)
+* [[`2109708186`](https://github.com/nodejs/node/commit/2109708186)] - **lib**: fix cluster handle leak (Rich Trott) [#3510](https://github.com/nodejs/node/pull/3510)
+* [[`f49c7c6955`](https://github.com/nodejs/node/commit/f49c7c6955)] - **lib**: avoid REPL exit on completion error (Rich Trott) [#3358](https://github.com/nodejs/node/pull/3358)
+* [[`8a2c4aeeaa`](https://github.com/nodejs/node/commit/8a2c4aeeaa)] - **repl**: handle comments properly (Sakthipriyan Vairamani) [#3515](https://github.com/nodejs/node/pull/3515)
+* [[`a04408acce`](https://github.com/nodejs/node/commit/a04408acce)] - **repl**: limit persistent history correctly on load (Jeremiah Senkpiel) [#2356](https://github.com/nodejs/node/pull/2356)
+* [[`5d1f1c5fa8`](https://github.com/nodejs/node/commit/5d1f1c5fa8)] - **src**: wrap source before doing syntax check (Evan Lucas) [#3587](https://github.com/nodejs/node/pull/3587)
+* [[`3bafe1a59b`](https://github.com/nodejs/node/commit/3bafe1a59b)] - **src**: fix race condition in debug signal on exit (Ben Noordhuis) [#3528](https://github.com/nodejs/node/pull/3528)
+* [[`fe01d0df7a`](https://github.com/nodejs/node/commit/fe01d0df7a)] - **src**: fix exception message encoding on Windows (Brian White) [#3288](https://github.com/nodejs/node/pull/3288)
+* [[`4bac5d9ddf`](https://github.com/nodejs/node/commit/4bac5d9ddf)] - **stream**: avoid unnecessary concat of a single buffer. (Calvin Metcalf) [#3300](https://github.com/nodejs/node/pull/3300)
+* [[`117fb47a16`](https://github.com/nodejs/node/commit/117fb47a16)] - **stream**: fix signature of _write() in a comment (Fábio Santos) [#3248](https://github.com/nodejs/node/pull/3248)
+* [[`c563a34427`](https://github.com/nodejs/node/commit/c563a34427)] - **test**: split independent tests into separate files (Rich Trott) [#3548](https://github.com/nodejs/node/pull/3548)
+* [[`3f62952d42`](https://github.com/nodejs/node/commit/3f62952d42)] - **test**: add node::MakeCallback() test coverage (Ben Noordhuis) [#3478](https://github.com/nodejs/node/pull/3478)
+* [[`6b75f10d8a`](https://github.com/nodejs/node/commit/6b75f10d8a)] - **test**: use port number from env in tls socket test (Stefan Budeanu) [#3557](https://github.com/nodejs/node/pull/3557)
+* [[`39ff44e94f`](https://github.com/nodejs/node/commit/39ff44e94f)] - **test**: fix heap-profiler link error LNK1194 on win (Junliang Yan) [#3572](https://github.com/nodejs/node/pull/3572)
+* [[`a2786dd408`](https://github.com/nodejs/node/commit/a2786dd408)] - **test**: fix missing unistd.h on windows (Junliang Yan) [#3532](https://github.com/nodejs/node/pull/3532)
+* [[`5e6f7c9a23`](https://github.com/nodejs/node/commit/5e6f7c9a23)] - **test**: add regression test for --debug-brk -e 0 (Ben Noordhuis) [#3585](https://github.com/nodejs/node/pull/3585)
+* [[`7cad182cb6`](https://github.com/nodejs/node/commit/7cad182cb6)] - **test**: port domains regression test from v0.10 (Jonas Dohse) [#3356](https://github.com/nodejs/node/pull/3356)
+* [[`78d854c6ce`](https://github.com/nodejs/node/commit/78d854c6ce)] - **test**: remove util from common (Rich Trott) [#3324](https://github.com/nodejs/node/pull/3324)
+* [[`c566c8b8c0`](https://github.com/nodejs/node/commit/c566c8b8c0)] - **test**: remove util properties from common (Rich Trott) [#3304](https://github.com/nodejs/node/pull/3304)
+* [[`eb7c3fb2f4`](https://github.com/nodejs/node/commit/eb7c3fb2f4)] - **test**: split up buffer tests for reliability (Rich Trott) [#3323](https://github.com/nodejs/node/pull/3323)
+* [[`b398a85e19`](https://github.com/nodejs/node/commit/b398a85e19)] - **test**: parallelize long-running test (Rich Trott) [#3287](https://github.com/nodejs/node/pull/3287)
+* [[`b5f3b4956b`](https://github.com/nodejs/node/commit/b5f3b4956b)] - **test**: change call to deprecated util.isError() (Rich Trott) [#3084](https://github.com/nodejs/node/pull/3084)
+* [[`32149cacb5`](https://github.com/nodejs/node/commit/32149cacb5)] - **test**: improve tests for util.inherits (Michaël Zasso) [#3507](https://github.com/nodejs/node/pull/3507)
+* [[`5be686fab8`](https://github.com/nodejs/node/commit/5be686fab8)] - **test**: print helpful err msg on test-dns-ipv6.js (Junliang Yan) [#3501](https://github.com/nodejs/node/pull/3501)
+* [[`0429131e32`](https://github.com/nodejs/node/commit/0429131e32)] - **test**: fix domain with abort-on-uncaught on PPC (Julien Gilli) [#3354](https://github.com/nodejs/node/pull/3354)
+* [[`788106eee9`](https://github.com/nodejs/node/commit/788106eee9)] - **test**: cleanup, improve repl-persistent-history (Jeremiah Senkpiel) [#2356](https://github.com/nodejs/node/pull/2356)
+* [[`ea58fa0bac`](https://github.com/nodejs/node/commit/ea58fa0bac)] - **test**: add Symbol test for assert.deepEqual() (Rich Trott) [#3327](https://github.com/nodejs/node/pull/3327)
+* [[`d409ac473b`](https://github.com/nodejs/node/commit/d409ac473b)] - **test**: disable test-tick-processor - aix and be ppc (Michael Dawson) [#3491](https://github.com/nodejs/node/pull/3491)
+* [[`c1623039dd`](https://github.com/nodejs/node/commit/c1623039dd)] - **test**: harden test-child-process-fork-regr-gh-2847 (Michael Dawson) [#3459](https://github.com/nodejs/node/pull/3459)
+* [[`3bb4437abb`](https://github.com/nodejs/node/commit/3bb4437abb)] - **test**: fix test-net-keepalive for AIX (Imran Iqbal) [#3458](https://github.com/nodejs/node/pull/3458)
+* [[`af55641a69`](https://github.com/nodejs/node/commit/af55641a69)] - **test**: wrap assert.fail when passed to callback (Myles Borins) [#3453](https://github.com/nodejs/node/pull/3453)
+* [[`7c7ef01e65`](https://github.com/nodejs/node/commit/7c7ef01e65)] - **test**: skip test-dns-ipv6.js if ipv6 is unavailable (Junliang Yan) [#3444](https://github.com/nodejs/node/pull/3444)
+* [[`a4d1510ba4`](https://github.com/nodejs/node/commit/a4d1510ba4)] - **test**: repl-persistent-history is no longer flaky (Jeremiah Senkpiel) [#3437](https://github.com/nodejs/node/pull/3437)
+* [[`a5d968b8a2`](https://github.com/nodejs/node/commit/a5d968b8a2)] - **test**: fix flaky test-child-process-emfile (Rich Trott) [#3430](https://github.com/nodejs/node/pull/3430)
+* [[`eac2acca76`](https://github.com/nodejs/node/commit/eac2acca76)] - **test**: remove flaky status from eval_messages test (Rich Trott) [#3420](https://github.com/nodejs/node/pull/3420)
+* [[`155c778584`](https://github.com/nodejs/node/commit/155c778584)] - **test**: fix flaky test for symlinks (Rich Trott) [#3418](https://github.com/nodejs/node/pull/3418)
+* [[`74eb632483`](https://github.com/nodejs/node/commit/74eb632483)] - **test**: apply correct assert.fail() arguments (Rich Trott) [#3378](https://github.com/nodejs/node/pull/3378)
+* [[`0a4323dd82`](https://github.com/nodejs/node/commit/0a4323dd82)] - **test**: replace util with backtick strings (Myles Borins) [#3359](https://github.com/nodejs/node/pull/3359)
+* [[`93847694ec`](https://github.com/nodejs/node/commit/93847694ec)] - **test**: add test-child-process-emfile fail message (Rich Trott) [#3335](https://github.com/nodejs/node/pull/3335)
+* [[`8d78d687d5`](https://github.com/nodejs/node/commit/8d78d687d5)] - **timers**: reuse timer in `setTimeout().unref()` (Fedor Indutny) [#3407](https://github.com/nodejs/node/pull/3407)
+* [[`e69c869399`](https://github.com/nodejs/node/commit/e69c869399)] - **tls**: TLSSocket options default isServer false (Yuval Brik) [#2614](https://github.com/nodejs/node/pull/2614)
+* [[`0b32bbbf69`](https://github.com/nodejs/node/commit/0b32bbbf69)] - **v8**: pull fix for builtin code size on PPC (Michael Dawson) [#3474](https://github.com/nodejs/node/pull/3474)
+
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.2/node-v4.2.2-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.2/node-v4.2.2-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.2/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.2/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.2/node-v4.2.2.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/download/release/latest-v4.x/node-v4.2.2-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.2/node-v4.2.2-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.2/node-v4.2.2.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.2/<br>
+Documentation: https://nodejs.org/docs/v4.2.2/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+17e60f59cfd40bd0a74f62106dfe2d6cf14aea53490c5e872fa7530138d0dfef  node-v4.2.2-darwin-x64.tar.gz
+949fe7a06e097e1f1b15196020e4c0ef5f132b146b000811e59513de9d22a9ef  node-v4.2.2-darwin-x64.tar.xz
+787a89963b9b0ea41f7d4964705ed3561d16d023e1b5aae80700f973ba7ec4e7  node-v4.2.2-headers.tar.gz
+663c5a6fdc2c6abab7e8e528299f414a75b544d775c43aef2303272c8a3560bf  node-v4.2.2-headers.tar.xz
+125b2236da6c0c7fed39b6652b3867646200c3fe7c9284df3f8ac07a84d39010  node-v4.2.2-linux-arm64.tar.gz
+d51b08a018f91440658b077c7ea92296516208f008df66cebfc882086be9e2b0  node-v4.2.2-linux-arm64.tar.xz
+dfe30ab4dbfb66c31259c0b176609f2dbace29f03d3cf12c5d8bee3dd25db035  node-v4.2.2-linux-armv6l.tar.gz
+35015424950ec585f4c4f882f0433bd2b64111020c59075d4de19b34d1990a97  node-v4.2.2-linux-armv6l.tar.xz
+2170dea2d74b6a1c5c82be6b93a9b84ad5a78cafa47415661095be2b358d964a  node-v4.2.2-linux-armv7l.tar.gz
+7ce4aa955d98a1023b13c11175a8381db78fac0ea91d69ad9ec48f7f16993eec  node-v4.2.2-linux-armv7l.tar.xz
+5c39fac55c945be3b8ac381a12bdbe3a64a9bdc5376d27e2ce0c72160eff5942  node-v4.2.2-linux-x64.tar.gz
+8e08eb5da9d2ea14c5dcf268a09725f0e44ba3f03b2c549949a827f97f893611  node-v4.2.2-linux-x64.tar.xz
+7fe7d716cf52db39fa0590885e2f39a0bdee9ecbba230621f042c8154e8100fe  node-v4.2.2-linux-x86.tar.gz
+5b8e8a25faad1d4600c695df9887b6925eff8a9bb9151576f845fb3ab7e01fd2  node-v4.2.2-linux-x86.tar.xz
+0b2ca2deecfeb37d23745c374c2332a11b291b58df8b39803c27b089c16bb1d2  node-v4.2.2.pkg
+23d47dee4057a4105c53158b07c2362ad0e962332e9a939c841de9867e541da3  node-v4.2.2-sunos-x64.tar.gz
+5dff7b74011335176af73e845e0f0aff2b21fb72e472bfa961c0269e0b7554c9  node-v4.2.2-sunos-x64.tar.xz
+ed69c2a73a55100c044ae16f244119e889d502722ada7df8640793c1fb1a5195  node-v4.2.2-sunos-x86.tar.gz
+9c433f01cb09f3bcd8a10646195bbe5b408bf329ca5e87b68477bcb590002968  node-v4.2.2-sunos-x86.tar.xz
+00e709353435b436b5bbf5e62272ebb15fe801065422c4c2afe2b93456210cb1  node-v4.2.2.tar.gz
+b016c3d2f434f86d8d3da9ad90ffb2fd35b32223e9081e3d4f67b8de0370ce69  node-v4.2.2.tar.xz
+aee3b5506adcef036b5db4d2cbc978fe4de5786cdd4803fc65305482904c26fe  node-v4.2.2-x64.msi
+84dcb146c2eef134643d47f9f772a6a3a84c5bb8d254cef223cb4df43698b7c9  node-v4.2.2-x86.msi
+56b7acccf89d073b7e71ef73b19fcb02bc7ac23f3222528f1d36c0c83c114c9a  win-x64/node.exe
+e73cbd09bac9338df5f5aea804358e36ae33af1a1664f1d9c6d6161801e3147c  win-x64/node.lib
+ca722e26b0edc14043085e1a7794b1281b4cfacd11ae00a96d9009e97d8ecb0b  win-x86/node.exe
+238388ba03873b40988e37a5f83867f9fb6dbe51a1c9f85e5fc371f555a3f648  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWORyQAAoJEHNBsVwHCHesJfMH/19SGfkAjguPYgfprKyG32jZ
+rE9slmg0pz+VGEJCv+yepgvRBHfu0w9sxZ/TjBHg2ioh4ZgWNoLrZcTNmYvaqY/K
+ifyLeoDcOSoXbYmqw8vZvKbGTpS7p10Bi9cNfr49YiE814RbdRulIDqKlcymxYIt
+vecnX+X/ZiFBipIDmak1n582dikmFe5gPvwx5vCydKCo89l7Ja7XCLy484cEkQo/
+aRHI0dnjwcC7+/EBXBhpGAM42ls4AcN5FtuUKgpUT609rcH0Z4SwKW3CShU3nDO1
+IecVUMtE1G8uy4dmCFozpA2IXzGSoNSGIEWYAWNDbc8JtPMRyBhcBOUDox2utjY=
+=0leN
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v4.2.3.md b/locale/uk/blog/release/v4.2.3.md
new file mode 100755
index 0000000000000..87ee319b4db46
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.3.md
@@ -0,0 +1,99 @@
+---
+date: 2015-12-04T03:03:00.000Z
+version: 4.2.3
+category: release
+title: Node v4.2.3 "Argon" (LTS)
+slug: node-v4-2-3
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+**This is an important security release**. All Node.js users should consult our [December Security Release Summary](/en/blog/vulnerability/december-2015-security-releases/) for details on patched vulnerabilities.
+
+### Notable changes
+
+* **http**: Fix a bug where an HTTP socket may no longer have an associated parser but a pipelined request triggers a pause or resume, a potential denial-of-service vector. (Fedor Indutny)
+* **openssl**: Upgrade to 1.0.2e, containing fixes for:
+  - CVE-2015-3193 "BN_mod_exp may produce incorrect results on x86_64", an attack may be feasible against a Node.js TLS server using DHE key exchange. Details are available at <http://openssl.org/news/secadv/20151203.txt>.
+  - CVE-2015-3194 "Certificate verify crash with missing PSS parameter", a potential denial-of-service vector for Node.js TLS servers using client authentication; TLS clients are also impacted. Details are available at <http://openssl.org/news/secadv/20151203.txt>.
+  (Shigeki Ohtsu) [#4134](https://github.com/nodejs/node/pull/4134)
+* **v8**: Backport fixes for a bug in `JSON.stringify()` that can result in out-of-bounds reads for arrays. (Ben Noordhuis)
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`49bbd563be`](https://github.com/nodejs/node/commit/49bbd563be)] - **deps**: upgrade openssl sources to 1.0.2e (Shigeki Ohtsu) [#4134](https://github.com/nodejs/node/pull/4134)
+* [[`9a063fd492`](https://github.com/nodejs/node/commit/9a063fd492)] - **deps**: backport a7e50a5 from upstream v8 (Ben Noordhuis)
+* [[`07233206e9`](https://github.com/nodejs/node/commit/07233206e9)] - **deps**: backport 6df9a1d from upstream v8 (Ben Noordhuis)
+* [[`1c8e6de78e`](https://github.com/nodejs/node/commit/1c8e6de78e)] - **http**: fix pipeline regression (Fedor Indutny)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.3/node-v4.2.3-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.3/node-v4.2.3-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.3/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.3/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.3/node-v4.2.3.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.3/node-v4.2.3-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.3/node-v4.2.3.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.3/<br>
+Documentation: https://nodejs.org/docs/v4.2.3/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+078b033d98367da2248b443ed74f0b8a5808783d07cf0c24884457fd66b68fc1  node-v4.2.3-darwin-x64.tar.gz
+9890cba5c90e6bd0465140dda2471e3545a7fd19a8f927af8f6c6ce145cb33d1  node-v4.2.3-darwin-x64.tar.xz
+e8fab75b9183a4f35c358813e3c5d451daf2fef737a21494f7aa64bdd538c87c  node-v4.2.3-headers.tar.gz
+27d79e6b6f1613f9a9cb97f6cfecd0cb710bc6719f24cae2e284b8693eb40d1e  node-v4.2.3-headers.tar.xz
+9ec1becd52959920a0f06c92f01b3c3e8c09dd35b4b4f591d975f1975a5f1689  node-v4.2.3-linux-arm64.tar.gz
+d6b7233fe980b647bb4349ec577387baf38177cf5952596358b1c3ee7dd11fc6  node-v4.2.3-linux-arm64.tar.xz
+50b158bc4c324e78bc5ceb08e2d5e6aefb34f2570798e7ac4fd12bacd6733478  node-v4.2.3-linux-armv6l.tar.gz
+095fe43b1a224ec1afae2ee9c19586fddfe4135fea6c1f3cec9907128a436203  node-v4.2.3-linux-armv6l.tar.xz
+bebe529dd9ef576193cd7ef40f3f8a16f51317251b624f5e6a9998861b1778f3  node-v4.2.3-linux-armv7l.tar.gz
+f5faa99318d7c89de6706b5d7e3602fd613eb7fd002222f7674d28136311cc13  node-v4.2.3-linux-armv7l.tar.xz
+644d4c0b206ebcb75383fbe42f6025e7253a61992816289359d0f4dcdb6087d7  node-v4.2.3-linux-x64.tar.gz
+feac5b14a28fa32513bcbbbee1712e24996597510d9d1718ce8b0e22e019f8a2  node-v4.2.3-linux-x64.tar.xz
+fd30b15327348520dc840bb95a1441d0495e7a843d5a7ec102f012aedc1b3a75  node-v4.2.3-linux-x86.tar.gz
+6706cb10ea2252ddd167bcedb77e9884eee3ce2a683a9e21ec417e9084a9187a  node-v4.2.3-linux-x86.tar.xz
+0d72b52f99291bef3961ca78b9add920524eae84b4879c0e003546bd28f7a604  node-v4.2.3.pkg
+28096b317320bec8d40263975bdc3fdd1b77c941304abcb3fd6c106970b3a936  node-v4.2.3-sunos-x64.tar.gz
+d647fe76ffe5bb8d3359d0d9196e972b3f7ca895246c5e7379b3e1c0e1539697  node-v4.2.3-sunos-x64.tar.xz
+b37e7652c5d0e08c6c2087e03c0fa860ab55b9c005db33c50373de891eb48dba  node-v4.2.3-sunos-x86.tar.gz
+e5ef81350f32320fca5067573b391a1a4ebcc5b9b73e27d60317f6f6b7ff3881  node-v4.2.3-sunos-x86.tar.xz
+5008ade5feb4b089f59163f66bffddc113f27de5d78edf203e39435c2c5d554f  node-v4.2.3.tar.gz
+9e8aef1e47b317575c421c8d10a80e6c319b26969b566d3b84e49e65a92837f4  node-v4.2.3.tar.xz
+3dc276d247684cf45ace30fb99bc44e1af1467108075016a4cd17f980aae086a  node-v4.2.3-x64.msi
+a425efc379bca298f3bb1395aafbf851b1d8c6c27fdacf5155bbf4b0b0749332  node-v4.2.3-x86.msi
+b987313753634a22e79876fa42b8e85ef33d735164d291416d60bbd7b1ff2603  win-x64/node.exe
+109e4dc21a761e5a0707798f6c7575faac5c5f83fda8f6903aea05a89e5e9a14  win-x64/node.lib
+ecc0e06bce6e95d849ba2224a3e0666537da08b0e99e132b39633a53d670c05f  win-x86/node.exe
+dc35cce7b4928c7635d1ab0b76b6cea35b5029ca4241191dc126a0fc16bd0382  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWYPvzAAoJEMJzeS99g1RdUDAH/0vQha25eANiUxKhIMOWFAF6
+CdsqGDVjfHq6NsUfx3Ehlwu0gVGpDNDU4Pi7M5unXd17UzOlvFBnqGdY5Hcz/4w+
+bA2UMJQwr8O28FJ0rShGrYThlM0YMMHnJKtECRzsv54FuCUaUiKkB2omqPY/0aIZ
+nHeqAyfvR1y4k/Elx9y2Ni3tMaikQBAeMif7exIYvTrB8H5P4lZoEECRBt1/If87
+ui9CRj28Q0fv9HS24iQuXCf4sNhMLq2JEgzH7hzG35GZijj9fby9k/loq8NXs7li
+5p4YId7nQhciSaAY3zS1JaUnofBdg35zIIorz4fJZ5dLreeZN7XCjC7eqFpsjMg=
+=GNHn
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.2.4.md b/locale/uk/blog/release/v4.2.4.md
new file mode 100755
index 0000000000000..7a2d80f56c725
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.4.md
@@ -0,0 +1,247 @@
+---
+date: 2015-12-23T17:26:48.289Z
+version: 4.2.4
+category: release
+title: Node v4.2.4 (LTS)
+slug: node-v4-2-4-lts
+layout: blog-post.hbs
+author: James M Snell
+---
+
+### Notable changes
+
+Node.js v4.2.4 is a Long Term Support Maintenance Update. There are a number
+of fixes and documentation updates.
+
+* Roughly 78% of the commits are documentation and test improvements
+* **domains**:
+** Fix handling of uncaught exceptions (Julien Gilli) [#3884](https://github.com/nodejs/node/pull/3884)
+* **deps**:
+** Upgrade to npm 2.14.12 (Kat Marchán) [#4110](https://github.com/nodejs/node/pull/4110)
+** Backport 819b40a from V8 upstream (Michaël Zasso) [#3938](https://github.com/nodejs/node/pull/3938)
+** Updated node LICENSE file with new npm license (Kat Marchán) [#4110](https://github.com/nodejs/node/pull/4110)
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`907a13a07f`](https://github.com/nodejs/node/commit/907a13a07f)] - Add missing va_end before return (Ömer Fadıl Usta) [#3565](https://github.com/nodejs/node/pull/3565)
+* [[`7ffc01756f`](https://github.com/nodejs/node/commit/7ffc01756f)] - **buffer**: fix writeInt{B,L}E for some neg values (Peter A. Bigot) [#3994](https://github.com/nodejs/node/pull/3994)
+* [[`db0186e435`](https://github.com/nodejs/node/commit/db0186e435)] - **buffer**: let WriteFloatGeneric silently drop values (P.S.V.R)
+* [[`5c6740865a`](https://github.com/nodejs/node/commit/5c6740865a)] - **build**: update signtool description, add url (Rod Vagg) [#4011](https://github.com/nodejs/node/pull/4011)
+* [[`60dda70f89`](https://github.com/nodejs/node/commit/60dda70f89)] - **build**: fix --with-intl=system-icu for x-compile (Steven R. Loomis) [#3808](https://github.com/nodejs/node/pull/3808)
+* [[`22208b067c`](https://github.com/nodejs/node/commit/22208b067c)] - **build**: fix configuring with prebuilt libraries (Markus Tzoe) [#3135](https://github.com/nodejs/node/pull/3135)
+* [[`914caf9c69`](https://github.com/nodejs/node/commit/914caf9c69)] - **child_process**: add safety checks on stdio access (cjihrig) [#3799](https://github.com/nodejs/node/pull/3799)
+* [[`236ad90a84`](https://github.com/nodejs/node/commit/236ad90a84)] - **child_process**: don't fork bomb ourselves from -e (Ben Noordhuis) [#3575](https://github.com/nodejs/node/pull/3575)
+* [[`f28f69dac4`](https://github.com/nodejs/node/commit/f28f69dac4)] - **cluster**: remove handles when disconnecting worker (Ben Noordhuis) [#3677](https://github.com/nodejs/node/pull/3677)
+* [[`f5c5e8bf91`](https://github.com/nodejs/node/commit/f5c5e8bf91)] - **cluster**: send suicide message on disconnect (cjihrig) [#3720](https://github.com/nodejs/node/pull/3720)
+* [[`629d5d18d7`](https://github.com/nodejs/node/commit/629d5d18d7)] - **configure**: `v8_use_snapshot` should be `true` (Fedor Indutny) [#3962](https://github.com/nodejs/node/pull/3962)
+* [[`3094464871`](https://github.com/nodejs/node/commit/3094464871)] - **configure**: use __ARM_ARCH to determine arm version (João Reis) [#4123](https://github.com/nodejs/node/pull/4123)
+* [[`1e1173fc5c`](https://github.com/nodejs/node/commit/1e1173fc5c)] - **configure**: respect CC_host in host arch detection (João Reis) [#4117](https://github.com/nodejs/node/pull/4117)
+* [[`2e9b886fbf`](https://github.com/nodejs/node/commit/2e9b886fbf)] - **crypto**: DSA parameter validation in FIPS mode (Stefan Budeanu) [#3756](https://github.com/nodejs/node/pull/3756)
+* [[`00b77d9e84`](https://github.com/nodejs/node/commit/00b77d9e84)] - **crypto**: Improve error checking and reporting (Stefan Budeanu) [#3753](https://github.com/nodejs/node/pull/3753)
+* [[`3dd90ddc73`](https://github.com/nodejs/node/commit/3dd90ddc73)] - **deps**: upgrade to npm 2.14.12 (Kat Marchán) [#4110](https://github.com/nodejs/node/pull/4110)
+* [[`51ae8d10b3`](https://github.com/nodejs/node/commit/51ae8d10b3)] - **deps**: Updated node LICENSE file with new npm license (Kat Marchán) [#4110](https://github.com/nodejs/node/pull/4110)
+* [[`9e1edead22`](https://github.com/nodejs/node/commit/9e1edead22)] - **deps**: backport 819b40a from V8 upstream (Michaël Zasso) [#3938](https://github.com/nodejs/node/pull/3938)
+* [[`a2ce3843cc`](https://github.com/nodejs/node/commit/a2ce3843cc)] - **deps**: upgrade npm to 2.14.9 (Forrest L Norvell) [#3686](https://github.com/nodejs/node/pull/3686)
+* [[`b140cb29f4`](https://github.com/nodejs/node/commit/b140cb29f4)] - **dns**: prevent undefined values in results (Junliang Yan) [#3696](https://github.com/nodejs/node/pull/3696)
+* [[`8aafa2ecc0`](https://github.com/nodejs/node/commit/8aafa2ecc0)] - **doc**: standardize references to node.js in docs (Scott Buchanan) [#4136](https://github.com/nodejs/node/pull/4136)
+* [[`72f43a263a`](https://github.com/nodejs/node/commit/72f43a263a)] - **doc**: fix internal link to child.send() (Luigi Pinca) [#4089](https://github.com/nodejs/node/pull/4089)
+* [[`dcfdbac457`](https://github.com/nodejs/node/commit/dcfdbac457)] - **doc**: reword https.Agent example text (Jan Krems) [#4075](https://github.com/nodejs/node/pull/4075)
+* [[`f93d268dec`](https://github.com/nodejs/node/commit/f93d268dec)] - **doc**: add HTTP working group (James M Snell) [#3919](https://github.com/nodejs/node/pull/3919)
+* [[`beee0553ca`](https://github.com/nodejs/node/commit/beee0553ca)] - **doc**: update WORKING_GROUPS.md - add missing groups (Michael Dawson) [#3450](https://github.com/nodejs/node/pull/3450)
+* [[`3327415fc4`](https://github.com/nodejs/node/commit/3327415fc4)] - **doc**: fix the exception description (yorkie) [#3658](https://github.com/nodejs/node/pull/3658)
+* [[`da8d012c88`](https://github.com/nodejs/node/commit/da8d012c88)] - **doc**: clarify v4.2.3 notable items (Rod Vagg) [#4155](https://github.com/nodejs/node/pull/4155)
+* [[`44a2d8ca24`](https://github.com/nodejs/node/commit/44a2d8ca24)] - **doc**: fix color of linked code blocks (jpersson) [#4068](https://github.com/nodejs/node/pull/4068)
+* [[`bebde48ebc`](https://github.com/nodejs/node/commit/bebde48ebc)] - **doc**: fix typo in README (Rich Trott) [#4000](https://github.com/nodejs/node/pull/4000)
+* [[`b48d5ec301`](https://github.com/nodejs/node/commit/b48d5ec301)] - **doc**: message.header duplication correction (Bryan English) [#3997](https://github.com/nodejs/node/pull/3997)
+* [[`6ef3625456`](https://github.com/nodejs/node/commit/6ef3625456)] - **doc**: replace sane with reasonable (Lewis Cowper) [#3980](https://github.com/nodejs/node/pull/3980)
+* [[`c5be3c63f0`](https://github.com/nodejs/node/commit/c5be3c63f0)] - **doc**: fix rare case of misaligned columns (Roman Reiss) [#3948](https://github.com/nodejs/node/pull/3948)
+* [[`bd82fb06ff`](https://github.com/nodejs/node/commit/bd82fb06ff)] - **doc**: fix broken references (Alexander Gromnitsky) [#3944](https://github.com/nodejs/node/pull/3944)
+* [[`8eb28c3d50`](https://github.com/nodejs/node/commit/8eb28c3d50)] - **doc**: add reference for buffer.inspect() (cjihrig) [#3921](https://github.com/nodejs/node/pull/3921)
+* [[`4bc71e0078`](https://github.com/nodejs/node/commit/4bc71e0078)] - **doc**: clarify module loading behavior (cjihrig) [#3920](https://github.com/nodejs/node/pull/3920)
+* [[`4c382e7aaa`](https://github.com/nodejs/node/commit/4c382e7aaa)] - **doc**: numeric flags to fs.open (Carl Lei) [#3641](https://github.com/nodejs/node/pull/3641)
+* [[`5207099dc9`](https://github.com/nodejs/node/commit/5207099dc9)] - **doc**: clarify that fs streams expect blocking fd (Carl Lei) [#3641](https://github.com/nodejs/node/pull/3641)
+* [[`753c5071ea`](https://github.com/nodejs/node/commit/753c5071ea)] - **doc**: Adding best practises for crypto.pbkdf2 (Tom Gallacher) [#3290](https://github.com/nodejs/node/pull/3290)
+* [[`8f0291beba`](https://github.com/nodejs/node/commit/8f0291beba)] - **doc**: update WORKING_GROUPS.md to include Intl (Steven R. Loomis) [#3251](https://github.com/nodejs/node/pull/3251)
+* [[`c31d472487`](https://github.com/nodejs/node/commit/c31d472487)] - **doc**: sort repl alphabetically (Tristian Flanagan) [#3859](https://github.com/nodejs/node/pull/3859)
+* [[`6b172d9fe8`](https://github.com/nodejs/node/commit/6b172d9fe8)] - **doc**: consistent reference-style links (Bryan English) [#3845](https://github.com/nodejs/node/pull/3845)
+* [[`ffd3335e29`](https://github.com/nodejs/node/commit/ffd3335e29)] - **doc**: address use of profanity in code of conduct (James M Snell) [#3827](https://github.com/nodejs/node/pull/3827)
+* [[`a36a5b63cf`](https://github.com/nodejs/node/commit/a36a5b63cf)] - **doc**: reword message.headers to indicate they are not read-only (Tristian Flanagan) [#3814](https://github.com/nodejs/node/pull/3814)
+* [[`6de77cd320`](https://github.com/nodejs/node/commit/6de77cd320)] - **doc**: clarify duplicate header handling (Bryan English) [#3810](https://github.com/nodejs/node/pull/3810)
+* [[`b22973af81`](https://github.com/nodejs/node/commit/b22973af81)] - **doc**: replace head of readme with updated text (Rod Vagg) [#3482](https://github.com/nodejs/node/pull/3482)
+* [[`eab0d56ea9`](https://github.com/nodejs/node/commit/eab0d56ea9)] - **doc**: repl: add defineComand and displayPrompt (Bryan English) [#3765](https://github.com/nodejs/node/pull/3765)
+* [[`15fb02985f`](https://github.com/nodejs/node/commit/15fb02985f)] - **doc**: document release types in readme (Rod Vagg) [#3482](https://github.com/nodejs/node/pull/3482)
+* [[`29f26b882f`](https://github.com/nodejs/node/commit/29f26b882f)] - **doc**: add link to \[customizing util.inspect colors\]. (Jesse McCarthy) [#3749](https://github.com/nodejs/node/pull/3749)
+* [[`90fdb4f7b3`](https://github.com/nodejs/node/commit/90fdb4f7b3)] - **doc**: sort tls alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`39fa9fa85c`](https://github.com/nodejs/node/commit/39fa9fa85c)] - **doc**: sort stream alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`e98e8afb2b`](https://github.com/nodejs/node/commit/e98e8afb2b)] - **doc**: sort net alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`6de887483d`](https://github.com/nodejs/node/commit/6de887483d)] - **doc**: sort process alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`37033dcb71`](https://github.com/nodejs/node/commit/37033dcb71)] - **doc**: sort zlib alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`9878034567`](https://github.com/nodejs/node/commit/9878034567)] - **doc**: sort util alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`48fc765eb6`](https://github.com/nodejs/node/commit/48fc765eb6)] - **doc**: sort https alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`3546eb4f40`](https://github.com/nodejs/node/commit/3546eb4f40)] - **doc**: sort http alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`dedfb1156a`](https://github.com/nodejs/node/commit/dedfb1156a)] - **doc**: sort modules alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`71722fe1a1`](https://github.com/nodejs/node/commit/71722fe1a1)] - **doc**: sort readline alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`660062bf9e`](https://github.com/nodejs/node/commit/660062bf9e)] - **doc**: sort repl alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`34b8d28725`](https://github.com/nodejs/node/commit/34b8d28725)] - **doc**: sort string_decoder alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`3f3b9ed7d7`](https://github.com/nodejs/node/commit/3f3b9ed7d7)] - **doc**: sort timers alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`af876ddc64`](https://github.com/nodejs/node/commit/af876ddc64)] - **doc**: sort tty alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`3c2068704a`](https://github.com/nodejs/node/commit/3c2068704a)] - **doc**: sort url alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`363692fd0c`](https://github.com/nodejs/node/commit/363692fd0c)] - **doc**: sort vm alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`ca41b55166`](https://github.com/nodejs/node/commit/ca41b55166)] - **doc**: sort querystring alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`f37ff22b9f`](https://github.com/nodejs/node/commit/f37ff22b9f)] - **doc**: sort punycode alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`4d569607af`](https://github.com/nodejs/node/commit/4d569607af)] - **doc**: sort path alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`daa62447d1`](https://github.com/nodejs/node/commit/daa62447d1)] - **doc**: sort os alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`0906f9a8bb`](https://github.com/nodejs/node/commit/0906f9a8bb)] - **doc**: sort globals alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`6cd06c1319`](https://github.com/nodejs/node/commit/6cd06c1319)] - **doc**: sort fs alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`5b310f8d9e`](https://github.com/nodejs/node/commit/5b310f8d9e)] - **doc**: sort events alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`782cb7d15b`](https://github.com/nodejs/node/commit/782cb7d15b)] - **doc**: sort errors alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`c39eabbec4`](https://github.com/nodejs/node/commit/c39eabbec4)] - **doc**: sort dgram alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`261e0f3a21`](https://github.com/nodejs/node/commit/261e0f3a21)] - **doc**: sort crypto alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`0e6121d04d`](https://github.com/nodejs/node/commit/0e6121d04d)] - **doc**: sort dns alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`435ffb79f7`](https://github.com/nodejs/node/commit/435ffb79f7)] - **doc**: sort console alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`28935a10d6`](https://github.com/nodejs/node/commit/28935a10d6)] - **doc**: sort cluster alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`5e79dc4406`](https://github.com/nodejs/node/commit/5e79dc4406)] - **doc**: sort child_process alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`af0bf1a72c`](https://github.com/nodejs/node/commit/af0bf1a72c)] - **doc**: sort buffer alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`f43a0330aa`](https://github.com/nodejs/node/commit/f43a0330aa)] - **doc**: sort assert alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`1bbc3b3ff8`](https://github.com/nodejs/node/commit/1bbc3b3ff8)] - **doc**: add note on tls connection meta data methods (Tyler Henkel) [#3746](https://github.com/nodejs/node/pull/3746)
+* [[`3c415bbb12`](https://github.com/nodejs/node/commit/3c415bbb12)] - **doc**: add note to util.isBuffer (Evan Lucas) [#3790](https://github.com/nodejs/node/pull/3790)
+* [[`7b5e4574fd`](https://github.com/nodejs/node/commit/7b5e4574fd)] - **doc**: add romankl to collaborators (Roman Klauke) [#3725](https://github.com/nodejs/node/pull/3725)
+* [[`4f7c638a7a`](https://github.com/nodejs/node/commit/4f7c638a7a)] - **doc**: add saghul as a collaborator (Saúl Ibarra Corretgé)
+* [[`523251270a`](https://github.com/nodejs/node/commit/523251270a)] - **doc**: add thealphanerd to collaborators (Myles Borins) [#3723](https://github.com/nodejs/node/pull/3723)
+* [[`488e74f27d`](https://github.com/nodejs/node/commit/488e74f27d)] - **doc**: update lts description in the collaborator guide (James M Snell) [#3668](https://github.com/nodejs/node/pull/3668)
+* [[`fe3ae3cea4`](https://github.com/nodejs/node/commit/fe3ae3cea4)] - **doc**: add LTS info to COLLABORATOR_GUIDE.md (Myles Borins) [#3442](https://github.com/nodejs/node/pull/3442)
+* [[`daa10a345e`](https://github.com/nodejs/node/commit/daa10a345e)] - **doc**: typo fix in readme.md (Sam P Gallagher-Bishop) [#3649](https://github.com/nodejs/node/pull/3649)
+* [[`eca5720761`](https://github.com/nodejs/node/commit/eca5720761)] - **doc**: fix wrong date and known issue in changelog.md (James M Snell) [#3650](https://github.com/nodejs/node/pull/3650)
+* [[`83494f8f3e`](https://github.com/nodejs/node/commit/83494f8f3e)] - **doc**: rename iojs-* groups to nodejs-* (Steven R. Loomis) [#3634](https://github.com/nodejs/node/pull/3634)
+* [[`347fb65aee`](https://github.com/nodejs/node/commit/347fb65aee)] - **doc**: fix crypto spkac function descriptions (Jason Gerfen) [#3614](https://github.com/nodejs/node/pull/3614)
+* [[`11d2050d63`](https://github.com/nodejs/node/commit/11d2050d63)] - **doc**: Updated streams simplified constructor API (Tom Gallacher) [#3602](https://github.com/nodejs/node/pull/3602)
+* [[`6db4392bfb`](https://github.com/nodejs/node/commit/6db4392bfb)] - **doc**: made code spans more visible in the API docs (phijohns) [#3573](https://github.com/nodejs/node/pull/3573)
+* [[`8a7dd73af1`](https://github.com/nodejs/node/commit/8a7dd73af1)] - **doc**: added what buf.copy returns (Manuel B) [#3555](https://github.com/nodejs/node/pull/3555)
+* [[`cf4b65c2d6`](https://github.com/nodejs/node/commit/cf4b65c2d6)] - **doc**: fix function param order in assert doc (David Woods) [#3533](https://github.com/nodejs/node/pull/3533)
+* [[`a2efe4c72b`](https://github.com/nodejs/node/commit/a2efe4c72b)] - **doc**: add note about timeout delay > TIMEOUT_MAX (Guilherme Souza) [#3512](https://github.com/nodejs/node/pull/3512)
+* [[`d1b5833476`](https://github.com/nodejs/node/commit/d1b5833476)] - **doc**: add caveats of algs and key size in crypto (Shigeki Ohtsu) [#3479](https://github.com/nodejs/node/pull/3479)
+* [[`12cdf6fcf3`](https://github.com/nodejs/node/commit/12cdf6fcf3)] - **doc**: add method links in events.markdown (Alejandro Oviedo) [#3187](https://github.com/nodejs/node/pull/3187)
+* [[`f50f19e384`](https://github.com/nodejs/node/commit/f50f19e384)] - **doc**: stdout/stderr can block when directed to file (Ben Noordhuis) [#3170](https://github.com/nodejs/node/pull/3170)
+* [[`b2cc1302e0`](https://github.com/nodejs/node/commit/b2cc1302e0)] - **docs**: improve discoverability of Code of Conduct (Ashley Williams) [#3774](https://github.com/nodejs/node/pull/3774)
+* [[`fa1ab497f1`](https://github.com/nodejs/node/commit/fa1ab497f1)] - **docs**: fs - change links to buffer encoding to Buffer class anchor (fansworld-claudio) [#2796](https://github.com/nodejs/node/pull/2796)
+* [[`34e64e5390`](https://github.com/nodejs/node/commit/34e64e5390)] - **domains**: fix handling of uncaught exceptions (Julien Gilli) [#3884](https://github.com/nodejs/node/pull/3884)
+* [[`0311836e7a`](https://github.com/nodejs/node/commit/0311836e7a)] - **meta**: remove use of profanity in source (Myles Borins) [#4122](https://github.com/nodejs/node/pull/4122)
+* [[`971762ada9`](https://github.com/nodejs/node/commit/971762ada9)] - **module**: cache regular expressions (Evan Lucas) [#3869](https://github.com/nodejs/node/pull/3869)
+* [[`d80fa2c77c`](https://github.com/nodejs/node/commit/d80fa2c77c)] - **module**: remove unnecessary JSON.stringify (Andres Suarez) [#3578](https://github.com/nodejs/node/pull/3578)
+* [[`aa85d62f09`](https://github.com/nodejs/node/commit/aa85d62f09)] - **net**: add local address/port for better errors (Jan Schär) [#3946](https://github.com/nodejs/node/pull/3946)
+* [[`803a56de52`](https://github.com/nodejs/node/commit/803a56de52)] - **querystring**: Parse multiple separator characters (Yosuke Furukawa) [#3807](https://github.com/nodejs/node/pull/3807)
+* [[`ff02b295fc`](https://github.com/nodejs/node/commit/ff02b295fc)] - **repl**: don't crash if cannot open history file (Evan Lucas) [#3630](https://github.com/nodejs/node/pull/3630)
+* [[`329e88e545`](https://github.com/nodejs/node/commit/329e88e545)] - **repl**: To exit, press ^C again or type .exit. (Hemanth.HM) [#3368](https://github.com/nodejs/node/pull/3368)
+* [[`9b05905361`](https://github.com/nodejs/node/commit/9b05905361)] - **src**: Revert "nix stdin _readableState.reading" (Roman Reiss) [#3490](https://github.com/nodejs/node/pull/3490)
+* [[`957c1f2543`](https://github.com/nodejs/node/commit/957c1f2543)] - **stream_wrap**: error if stream has StringDecoder (Fedor Indutny) [#4031](https://github.com/nodejs/node/pull/4031)
+* [[`43e3b69dae`](https://github.com/nodejs/node/commit/43e3b69dae)] - **test**: refactor test-http-exit-delay (Rich Trott) [#4055](https://github.com/nodejs/node/pull/4055)
+* [[`541d0d21be`](https://github.com/nodejs/node/commit/541d0d21be)] - **test**: fix cluster-disconnect-handles flakiness (Santiago Gimeno) [#4009](https://github.com/nodejs/node/pull/4009)
+* [[`5f66d66e84`](https://github.com/nodejs/node/commit/5f66d66e84)] - **test**: don't check the # of chunks in test-http-1.0 (Santiago Gimeno) [#3961](https://github.com/nodejs/node/pull/3961)
+* [[`355edf585b`](https://github.com/nodejs/node/commit/355edf585b)] - **test**: fix cluster-worker-isdead (Santiago Gimeno) [#3954](https://github.com/nodejs/node/pull/3954)
+* [[`4e46e04002`](https://github.com/nodejs/node/commit/4e46e04002)] - **test**: add test for repl.defineCommand() (Bryan English) [#3908](https://github.com/nodejs/node/pull/3908)
+* [[`4ea1a69c53`](https://github.com/nodejs/node/commit/4ea1a69c53)] - **test**: mark test flaky on FreeBSD (Rich Trott) [#4016](https://github.com/nodejs/node/pull/4016)
+* [[`05b64c11f5`](https://github.com/nodejs/node/commit/05b64c11f5)] - **test**: mark cluster-net-send test flaky on windows (Rich Trott) [#4006](https://github.com/nodejs/node/pull/4006)
+* [[`695015579b`](https://github.com/nodejs/node/commit/695015579b)] - **test**: remove flaky designation from ls-no-sslv3 (Rich Trott) [#3620](https://github.com/nodejs/node/pull/3620)
+* [[`abbd87b273`](https://github.com/nodejs/node/commit/abbd87b273)] - **test**: mark fork regression test flaky on windows (Rich Trott) [#4005](https://github.com/nodejs/node/pull/4005)
+* [[`38ba152a7a`](https://github.com/nodejs/node/commit/38ba152a7a)] - **test**: skip test if in FreeBSD jail (Rich Trott) [#3995](https://github.com/nodejs/node/pull/3995)
+* [[`cc24f0ea58`](https://github.com/nodejs/node/commit/cc24f0ea58)] - **test**: fix test-domain-exit-dispose-again (Julien Gilli) [#3990](https://github.com/nodejs/node/pull/3990)
+* [[`b2f1014d26`](https://github.com/nodejs/node/commit/b2f1014d26)] - **test**: remove flaky status for cluster test (Rich Trott) [#3975](https://github.com/nodejs/node/pull/3975)
+* [[`e66794fd30`](https://github.com/nodejs/node/commit/e66794fd30)] - **test**: address flaky test-http-client-timeout-event (Rich Trott) [#3968](https://github.com/nodejs/node/pull/3968)
+* [[`5a2727421a`](https://github.com/nodejs/node/commit/5a2727421a)] - **test**: retry on smartos if ECONNREFUSED (Rich Trott) [#3941](https://github.com/nodejs/node/pull/3941)
+* [[`dbc85a275c`](https://github.com/nodejs/node/commit/dbc85a275c)] - **test**: avoid test timeouts on rpi (Stefan Budeanu) [#3902](https://github.com/nodejs/node/pull/3902)
+* [[`b9d7378d20`](https://github.com/nodejs/node/commit/b9d7378d20)] - **test**: fix flaky test-child-process-spawnsync-input (Rich Trott) [#3889](https://github.com/nodejs/node/pull/3889)
+* [[`cca216a034`](https://github.com/nodejs/node/commit/cca216a034)] - **test**: move test-specific function out of common (Rich Trott) [#3871](https://github.com/nodejs/node/pull/3871)
+* [[`fb8df8d6c2`](https://github.com/nodejs/node/commit/fb8df8d6c2)] - **test**: module loading error fix solaris #3798 (fansworld-claudio) [#3855](https://github.com/nodejs/node/pull/3855)
+* [[`9ea6bc1e0f`](https://github.com/nodejs/node/commit/9ea6bc1e0f)] - **test**: skip test if FreeBSD jail will break it (Rich Trott) [#3839](https://github.com/nodejs/node/pull/3839)
+* [[`150f126618`](https://github.com/nodejs/node/commit/150f126618)] - **test**: fix flaky SmartOS test (Rich Trott) [#3830](https://github.com/nodejs/node/pull/3830)
+* [[`603a6f5405`](https://github.com/nodejs/node/commit/603a6f5405)] - **test**: run pipeline flood test in parallel (Rich Trott) [#3811](https://github.com/nodejs/node/pull/3811)
+* [[`4a26f74ee3`](https://github.com/nodejs/node/commit/4a26f74ee3)] - **test**: skip/replace weak crypto tests in FIPS mode (Stefan Budeanu) [#3757](https://github.com/nodejs/node/pull/3757)
+* [[`3f9562b6bd`](https://github.com/nodejs/node/commit/3f9562b6bd)] - **test**: stronger crypto in test fixtures (Stefan Budeanu) [#3759](https://github.com/nodejs/node/pull/3759)
+* [[`1f83eebec5`](https://github.com/nodejs/node/commit/1f83eebec5)] - **test**: increase crypto strength for FIPS standard (Stefan Budeanu) [#3758](https://github.com/nodejs/node/pull/3758)
+* [[`7c5fbf7850`](https://github.com/nodejs/node/commit/7c5fbf7850)] - **test**: add hasFipsCrypto to test/common.js (Stefan Budeanu) [#3756](https://github.com/nodejs/node/pull/3756)
+* [[`f30214f135`](https://github.com/nodejs/node/commit/f30214f135)] - **test**: add test for invalid DSA key size (Stefan Budeanu) [#3756](https://github.com/nodejs/node/pull/3756)
+* [[`9a6c9faafb`](https://github.com/nodejs/node/commit/9a6c9faafb)] - **test**: numeric flags to fs.open (Carl Lei) [#3641](https://github.com/nodejs/node/pull/3641)
+* [[`93d1d3cfcd`](https://github.com/nodejs/node/commit/93d1d3cfcd)] - **test**: refactor test-http-pipeline-flood (Rich Trott) [#3636](https://github.com/nodejs/node/pull/3636)
+* [[`6c23f67504`](https://github.com/nodejs/node/commit/6c23f67504)] - **test**: fix flaky test test-http-pipeline-flood (Devin Nakamura) [#3636](https://github.com/nodejs/node/pull/3636)
+* [[`4e5cae4360`](https://github.com/nodejs/node/commit/4e5cae4360)] - **test**: use really invalid hostname (Sakthipriyan Vairamani) [#3711](https://github.com/nodejs/node/pull/3711)
+* [[`da189f793b`](https://github.com/nodejs/node/commit/da189f793b)] - **test**: Fix test-cluster-worker-exit.js for AIX (Imran Iqbal) [#3666](https://github.com/nodejs/node/pull/3666)
+* [[`7b4194a863`](https://github.com/nodejs/node/commit/7b4194a863)] - **test**: fix test-module-loading-error for musl (Hugues Malphettes) [#3657](https://github.com/nodejs/node/pull/3657)
+* [[`3dc52e99df`](https://github.com/nodejs/node/commit/3dc52e99df)] - **test**: fix test-net-persistent-keepalive for AIX (Imran Iqbal) [#3646](https://github.com/nodejs/node/pull/3646)
+* [[`0e8eb66a78`](https://github.com/nodejs/node/commit/0e8eb66a78)] - **test**: fix path to module for repl test on Windows (Michael Cornacchia) [#3608](https://github.com/nodejs/node/pull/3608)
+* [[`3aecbc86d2`](https://github.com/nodejs/node/commit/3aecbc86d2)] - **test**: add test-zlib-flush-drain (Myles Borins) [#3534](https://github.com/nodejs/node/pull/3534)
+* [[`542d05cbe1`](https://github.com/nodejs/node/commit/542d05cbe1)] - **test**: enhance fs-watch-recursive test (Sakthipriyan Vairamani) [#2599](https://github.com/nodejs/node/pull/2599)
+* [[`0eb0119d64`](https://github.com/nodejs/node/commit/0eb0119d64)] - **tls**: Use SHA1 for sessionIdContext in FIPS mode (Stefan Budeanu) [#3755](https://github.com/nodejs/node/pull/3755)
+* [[`c10c08604c`](https://github.com/nodejs/node/commit/c10c08604c)] - **tls**: remove util and calls to util.format (Myles Borins) [#3456](https://github.com/nodejs/node/pull/3456)
+* [[`a558a570c0`](https://github.com/nodejs/node/commit/a558a570c0)] - **util**: use regexp instead of str.replace().join() (qinjia) [#3689](https://github.com/nodejs/node/pull/3689)
+* [[`47bb94a0c3`](https://github.com/nodejs/node/commit/47bb94a0c3)] - **zlib**: only apply drain listener if given callback (Craig Cavalier) [#3534](https://github.com/nodejs/node/pull/3534)
+* [[`4733a60158`](https://github.com/nodejs/node/commit/4733a60158)] - **zlib**: pass kind to recursive calls to flush (Myles Borins) [#3534](https://github.com/nodejs/node/pull/3534)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.4/node-v4.2.4-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.4/node-v4.2.4-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.4/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.4/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.4/node-v4.2.4.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: *Coming soon*<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.4/node-v4.2.4-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.4/node-v4.2.4.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.4/<br>
+Documentation: https://nodejs.org/docs/v4.2.4/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+3260412c210099b82a42316d614dec3313f4684a8ec63fca8684423675c37b0b  node-v4.2.4-darwin-x64.tar.gz
+c0385cc23e931547b5f5c190eeaad18301c132ad6a81f70b82b1a41e6567e035  node-v4.2.4-darwin-x64.tar.xz
+b1375e5296d0df6919fb1c3485d7174ac43a55a9507432d0e182c43c1cb5e3a0  node-v4.2.4-headers.tar.gz
+33b9e7cf0ab9c93455e28b6df5aea852b1d99fc6e8a3af84eb5bc7cb093984e5  node-v4.2.4-headers.tar.xz
+96b5d86ca677ddfa351289ea78a338f3a66ef57ceb485cdddb4798ae33e52a08  node-v4.2.4-linux-arm64.tar.gz
+387981a1c8f8e6033c82f74f5552e15f021bbf94ab3d4d781651ae3ad0e62c7f  node-v4.2.4-linux-arm64.tar.xz
+7d3645a032b56aefe1e1a023a6592b4900d4966312d034beac352bb833a74b60  node-v4.2.4-linux-armv7l.tar.gz
+118be7c8c9894c37c86974a11cce2e659c64e4b265c69d5c6b046762300dc96f  node-v4.2.4-linux-armv7l.tar.xz
+dcae0c0faf9841ef38953075e67ca477ef9d2ea7c14ac2221de2429813f83a62  node-v4.2.4-linux-x64.tar.gz
+af71f7e5acd7a98fbc2d9a7a96a03d481d6d0bb77b9fe810c56a0fb3c68b088a  node-v4.2.4-linux-x64.tar.xz
+39c0d90eb65f38f24a4cd2939212b655ea0e8685b92b7de6f407d0df5d6c261c  node-v4.2.4-linux-x86.tar.gz
+f2d17bf370329293716ac5840b8839e2c161d23dd8343391489cefc82da79834  node-v4.2.4-linux-x86.tar.xz
+2dff0a6e14ff25d7aa34b47f1863a0de61cd26918d0954055b783186a3a7614e  node-v4.2.4.pkg
+0a90e813eb1e8bcbdbb55f9b3594f1a93e64bef710a7276bcf94dbf6de79e8f6  node-v4.2.4-sunos-x64.tar.gz
+38fe0e73c11562d6f37d5b47831501077decc9363e110244773016b62b88e312  node-v4.2.4-sunos-x64.tar.xz
+214178bc2dc35b96ff73c49f7908c509213aecf355859eb9a3f26a487959afaa  node-v4.2.4-sunos-x86.tar.gz
+c2da2cc30de4cfab7e323e67c0dafd005df910c03e312d2676bbe5848ea380a4  node-v4.2.4-sunos-x86.tar.xz
+4ee244ffede7328d9fa24c3024787e71225b7abaac49fe2b30e68b27460c10ec  node-v4.2.4.tar.gz
+75cf0bb4b6bab5f864adaf3031d7c9757486dd00eadda4b8c51c40881451fae0  node-v4.2.4.tar.xz
+1b645f3c2ebefeba0ec21de94435878f5f4d885a41725d3b349da4c8d78cf4b8  node-v4.2.4-x64.msi
+c7c9ab4a1917add9289230805cc070c9daf383eecfe77540ee7ae31218bdbec3  node-v4.2.4-x86.msi
+761c1f14f34231bf184fc2a7a65ab2fbed4a57940e040ea74173e5882abe7f64  win-x64/node.exe
+a6c638bdf4d46c74d230bd99858de9e6b1da59f1176bc49234727daec1d61a46  win-x64/node.lib
+0c32e6dfdf483d8dd72cb017978b643e02578e537a94c545a78415275b5dab17  win-x86/node.exe
+aa1af8ba2c4545518962100b700532f3ed7dbf373b1f1ec45285c3bc94295e36  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWetOlAAoJEHNBsVwHCHesch8IAJBeFs4XFV0fwbSri5emiAvb
+Z/2KjZ4wPHWYzp2ytSpq9aFnTlO3RAzFmwSANxbhTA26eZyEqMuI5j4KfTG8X67n
+0+dAWAmOIQGwdd/n4Z/IWlQuGWDrL/ZEJkRsaF/ZBR+KE/j9iqgRzxoXx4GsTqV3
+qXSH9XBZyrA66FMcRcG/Ce4gqNtJ17Ckm3QvfSuKq/PQt9ntPYmTpACdgE3WXn+i
+pWwILoUlnNKwEdLRIGL+uJXJz6EmQhoWu5LHXUtEtr++tN8/PgPwHNhLMZTk+VKi
+aq9TqTPQASxd3RWT+2PGF1/orqEw+qlGFC3bdnEDnZKJuX5TUvj+JeVohs7S8r0=
+=Lc6h
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.2.5.md b/locale/uk/blog/release/v4.2.5.md
new file mode 100755
index 0000000000000..c5a4310ac9122
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.5.md
@@ -0,0 +1,295 @@
+---
+date: 2016-01-20T21:51:29.735Z
+version: 4.2.5
+category: release
+title: Node v4.2.5 (LTS)
+slug: node-v4-2-5
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+* **assert**
+  * accommodate ES6 classes that extend Error (Rich Trott) [#4166](https://github.com/nodejs/node/pull/4166)
+* **build**
+  * add "--partly-static" build options (Super Zheng) [#4152](https://github.com/nodejs/node/pull/4152)
+* **deps**
+  * backport 066747e from upstream V8 (Ali Ijaz Sheikh) [#4655](https://github.com/nodejs/node/pull/4655)
+  * backport 200315c from V8 upstream (Vladimir Kurchatkin) [#4128](https://github.com/nodejs/node/pull/4128)
+  * upgrade libuv to 1.8.0 (Saúl Ibarra Corretgé)
+* **docs**
+  * various updates landed in 70 different commits!
+* **repl**
+  * attach location info to syntax errors (cjihrig) [#4013](https://github.com/nodejs/node/pull/4013)
+  * display error message when loading directory (Prince J Wesley) [#4170](https://github.com/nodejs/node/pull/4170)
+* **tests**
+  * various updates landed in over 50 commits
+* **tools**
+  * add tap output to cpplint (Johan Bergström) [#3448](https://github.com/nodejs/node/pull/3448)
+* **util**
+  * allow lookup of hidden values (cjihrig) [#3988](https://github.com/nodejs/node/pull/3988)
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+
+* [[`87181cd74c`](https://github.com/nodejs/node/commit/87181cd74c)] - **assert**: accommodate ES6 classes that extend Error (Rich Trott) [#4166](https://github.com/nodejs/node/pull/4166)
+* [[`901172a783`](https://github.com/nodejs/node/commit/901172a783)] - **assert**: typed array deepequal performance fix (Claudio Rodriguez) [#4330](https://github.com/nodejs/node/pull/4330)
+* [[`55336810ee`](https://github.com/nodejs/node/commit/55336810ee)] - **async_wrap**: call callback in destructor (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461)
+* [[`a8b45e9e96`](https://github.com/nodejs/node/commit/a8b45e9e96)] - **async_wrap**: new instances get uid (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461)
+* [[`49f16d77c4`](https://github.com/nodejs/node/commit/49f16d77c4)] - **async_wrap**: allow some hooks to be optional (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461)
+* [[`44ee33f945`](https://github.com/nodejs/node/commit/44ee33f945)] - **buffer**: refactor create buffer (Jackson Tian) [#4340](https://github.com/nodejs/node/pull/4340)
+* [[`138d004ac0`](https://github.com/nodejs/node/commit/138d004ac0)] - **buffer**: faster case for create Buffer from new Buffer(0) (Jackson Tian) [#4326](https://github.com/nodejs/node/pull/4326)
+* [[`c6dc2a1609`](https://github.com/nodejs/node/commit/c6dc2a1609)] - **buffer**: Prevent Buffer constructor deopt (Bryce Baril) [#4158](https://github.com/nodejs/node/pull/4158)
+* [[`a320045e68`](https://github.com/nodejs/node/commit/a320045e68)] - **buffer**: default to UTF8 in byteLength() (Tom Gallacher) [#4010](https://github.com/nodejs/node/pull/4010)
+* [[`c5f71ac771`](https://github.com/nodejs/node/commit/c5f71ac771)] - **build**: add "--partly-static" build options (Super Zheng) [#4152](https://github.com/nodejs/node/pull/4152)
+* [[`e6c25335ea`](https://github.com/nodejs/node/commit/e6c25335ea)] - **build**: omit -gline-tables-only for --enable-asan (Ben Noordhuis) [#3680](https://github.com/nodejs/node/pull/3680)
+* [[`80b4ba286c`](https://github.com/nodejs/node/commit/80b4ba286c)] - **build**: Updates for AIX npm support - part 1 (Michael Dawson) [#3114](https://github.com/nodejs/node/pull/3114)
+* [[`35e32985ca`](https://github.com/nodejs/node/commit/35e32985ca)] - **child_process**: guard against race condition (Rich Trott) [#4418](https://github.com/nodejs/node/pull/4418)
+* [[`48564204f0`](https://github.com/nodejs/node/commit/48564204f0)] - **child_process**: flush consuming streams (Dave) [#4071](https://github.com/nodejs/node/pull/4071)
+* [[`481d59a74c`](https://github.com/nodejs/node/commit/481d59a74c)] - **configure**: fix arm vfpv2 (Jörg Krause) [#4203](https://github.com/nodejs/node/pull/4203)
+* [[`d19da6638d`](https://github.com/nodejs/node/commit/d19da6638d)] - **crypto**: load PFX chain the same way as regular one (Fedor Indutny) [#4165](https://github.com/nodejs/node/pull/4165)
+* [[`b8e75de1f3`](https://github.com/nodejs/node/commit/b8e75de1f3)] - **crypto**: fix native module compilation with FIPS (Stefan Budeanu) [#4023](https://github.com/nodejs/node/pull/4023)
+* [[`b7c3fb7f75`](https://github.com/nodejs/node/commit/b7c3fb7f75)] - **crypto**: disable crypto.createCipher in FIPS mode (Stefan Budeanu) [#3754](https://github.com/nodejs/node/pull/3754)
+* [[`31b4091a1e`](https://github.com/nodejs/node/commit/31b4091a1e)] - **debugger**: also exit when the repl emits 'exit' (Felix Böhm) [#2369](https://github.com/nodejs/node/pull/2369)
+* [[`9baa5618f5`](https://github.com/nodejs/node/commit/9baa5618f5)] - **deps**: backport 066747e from upstream V8 (Ali Ijaz Sheikh) [#4655](https://github.com/nodejs/node/pull/4655)
+* [[`c3a9d8a62e`](https://github.com/nodejs/node/commit/c3a9d8a62e)] - **deps**: backport 200315c from V8 upstream (Vladimir Kurchatkin) [#4128](https://github.com/nodejs/node/pull/4128)
+* [[`1ebb0c0fdf`](https://github.com/nodejs/node/commit/1ebb0c0fdf)] - **deps**: upgrade libuv to 1.8.0 (Saúl Ibarra Corretgé) [#4276](https://github.com/nodejs/node/pull/4276)
+* [[`253fe3e7c8`](https://github.com/nodejs/node/commit/253fe3e7c8)] - **dns**: remove nonexistant exports.ADNAME (Roman Reiss) [#3051](https://github.com/nodejs/node/pull/3051)
+* [[`8c2b65ad82`](https://github.com/nodejs/node/commit/8c2b65ad82)] - **doc**: clarify protocol default in http.request() (cjihrig) [#4714](https://github.com/nodejs/node/pull/4714)
+* [[`33e72e135f`](https://github.com/nodejs/node/commit/33e72e135f)] - **doc**: update links to use https where possible (jpersson) [#4054](https://github.com/nodejs/node/pull/4054)
+* [[`5f4aa79410`](https://github.com/nodejs/node/commit/5f4aa79410)] - **doc**: clarify explanation of first stream section (Vitor Cortez) [#4234](https://github.com/nodejs/node/pull/4234)
+* [[`295ca5bfb2`](https://github.com/nodejs/node/commit/295ca5bfb2)] - **doc**: add branch-diff example to releases.md (Myles Borins) [#4636](https://github.com/nodejs/node/pull/4636)
+* [[`18f5cd8710`](https://github.com/nodejs/node/commit/18f5cd8710)] - **doc**: update stylesheet to match frontpage (Roman Reiss) [#4621](https://github.com/nodejs/node/pull/4621)
+* [[`2f40715f08`](https://github.com/nodejs/node/commit/2f40715f08)] - **doc**: adds usage of readline line-by-line parsing (Robert Jefe Lindstaedt) [#4609](https://github.com/nodejs/node/pull/4609)
+* [[`5b45a464ee`](https://github.com/nodejs/node/commit/5b45a464ee)] - **doc**: document http's server.listen return value (Sequoia McDowell) [#4590](https://github.com/nodejs/node/pull/4590)
+* [[`bd31740339`](https://github.com/nodejs/node/commit/bd31740339)] - **doc**: label http.IncomingMessage as a Class (Sequoia McDowell) [#4589](https://github.com/nodejs/node/pull/4589)
+* [[`bcd2cbbb93`](https://github.com/nodejs/node/commit/bcd2cbbb93)] - **doc**: fix description about the latest-codename (Minwoo Jung) [#4583](https://github.com/nodejs/node/pull/4583)
+* [[`0b12bcb35d`](https://github.com/nodejs/node/commit/0b12bcb35d)] - **doc**: add Evan Lucas to Release Team (Evan Lucas) [#4579](https://github.com/nodejs/node/pull/4579)
+* [[`e20b1f6f10`](https://github.com/nodejs/node/commit/e20b1f6f10)] - **doc**: add Myles Borins to Release Team (Myles Borins) [#4578](https://github.com/nodejs/node/pull/4578)
+* [[`54977e63eb`](https://github.com/nodejs/node/commit/54977e63eb)] - **doc**: add missing backtick for readline (Brian White) [#4549](https://github.com/nodejs/node/pull/4549)
+* [[`5d6bed895c`](https://github.com/nodejs/node/commit/5d6bed895c)] - **doc**: bring releases.md up to date (cjihrig) [#4540](https://github.com/nodejs/node/pull/4540)
+* [[`0cd2252e85`](https://github.com/nodejs/node/commit/0cd2252e85)] - **doc**: fix numbering in stream.markdown (Richard Sun) [#4538](https://github.com/nodejs/node/pull/4538)
+* [[`8574d91f27`](https://github.com/nodejs/node/commit/8574d91f27)] - **doc**: stronger suggestion for userland assert (Wyatt Preul) [#4535](https://github.com/nodejs/node/pull/4535)
+* [[`a7bcf8b84d`](https://github.com/nodejs/node/commit/a7bcf8b84d)] - **doc**: close backtick in process.title description (Dave) [#4534](https://github.com/nodejs/node/pull/4534)
+* [[`0ceb3148b0`](https://github.com/nodejs/node/commit/0ceb3148b0)] - **doc**: improvements to events.markdown copy (James M Snell) [#4468](https://github.com/nodejs/node/pull/4468)
+* [[`bf56d509b9`](https://github.com/nodejs/node/commit/bf56d509b9)] - **doc**: explain ClientRequest#setTimeout time unit (Ben Ripkens) [#4458](https://github.com/nodejs/node/pull/4458)
+* [[`d927c51be3`](https://github.com/nodejs/node/commit/d927c51be3)] - **doc**: improvements to errors.markdown copy (James M Snell) [#4454](https://github.com/nodejs/node/pull/4454)
+* [[`ceea6df581`](https://github.com/nodejs/node/commit/ceea6df581)] - **doc**: improvements to dns.markdown copy (James M Snell) [#4449](https://github.com/nodejs/node/pull/4449)
+* [[`506f2f8ed1`](https://github.com/nodejs/node/commit/506f2f8ed1)] - **doc**: add anchors for _transform _flush _writev in stream.markdown (iamchenxin) [#4448](https://github.com/nodejs/node/pull/4448)
+* [[`74bcad0b78`](https://github.com/nodejs/node/commit/74bcad0b78)] - **doc**: improvements to dgram.markdown copy (James M Snell) [#4437](https://github.com/nodejs/node/pull/4437)
+* [[`e244d560c9`](https://github.com/nodejs/node/commit/e244d560c9)] - **doc**: improvements to debugger.markdown copy (James M Snell) [#4436](https://github.com/nodejs/node/pull/4436)
+* [[`df7e1281a5`](https://github.com/nodejs/node/commit/df7e1281a5)] - **doc**: improvements to console.markdown copy (James M Snell) [#4428](https://github.com/nodejs/node/pull/4428)
+* [[`abb17cc6c1`](https://github.com/nodejs/node/commit/abb17cc6c1)] - **doc**: fix spelling error in lib/url.js comment (Nik Nyby) [#4390](https://github.com/nodejs/node/pull/4390)
+* [[`823269db2d`](https://github.com/nodejs/node/commit/823269db2d)] - **doc**: improve assert.markdown copy (James M Snell) [#4360](https://github.com/nodejs/node/pull/4360)
+* [[`2b1804f6cb`](https://github.com/nodejs/node/commit/2b1804f6cb)] - **doc**: copyedit releases.md (Rich Trott) [#4384](https://github.com/nodejs/node/pull/4384)
+* [[`2b142fd876`](https://github.com/nodejs/node/commit/2b142fd876)] - **doc**: catch the WORKING_GROUPS.md bootstrap docs up to date (James M Snell) [#4367](https://github.com/nodejs/node/pull/4367)
+* [[`ed87873de3`](https://github.com/nodejs/node/commit/ed87873de3)] - **doc**: fix link in addons.markdown (Nicholas Young) [#4331](https://github.com/nodejs/node/pull/4331)
+* [[`fe693b7a4f`](https://github.com/nodejs/node/commit/fe693b7a4f)] - **doc**: Typo in buffer.markdown referencing buf.write() (chrisjohn404) [#4324](https://github.com/nodejs/node/pull/4324)
+* [[`764df2166e`](https://github.com/nodejs/node/commit/764df2166e)] - **doc**: document the cache parameter for fs.realpathSync (Jackson Tian) [#4285](https://github.com/nodejs/node/pull/4285)
+* [[`61f91b2f29`](https://github.com/nodejs/node/commit/61f91b2f29)] - **doc**: fix, modernize examples in docs (James M Snell) [#4282](https://github.com/nodejs/node/pull/4282)
+* [[`d87ad302ce`](https://github.com/nodejs/node/commit/d87ad302ce)] - **doc**: clarify error events in HTTP module documentation (Lenny Markus) [#4275](https://github.com/nodejs/node/pull/4275)
+* [[`7983577e41`](https://github.com/nodejs/node/commit/7983577e41)] - **doc**: fix improper http.get sample code (Hideki Yamamura) [#4263](https://github.com/nodejs/node/pull/4263)
+* [[`6c30d087e5`](https://github.com/nodejs/node/commit/6c30d087e5)] - **doc**: Fixing broken links to the v8 wiki (Tom Gallacher) [#4241](https://github.com/nodejs/node/pull/4241)
+* [[`cf214e56e4`](https://github.com/nodejs/node/commit/cf214e56e4)] - **doc**: move description of 'equals' method to right place (janriemer) [#4227](https://github.com/nodejs/node/pull/4227)
+* [[`fb8e8dbb92`](https://github.com/nodejs/node/commit/fb8e8dbb92)] - **doc**: copyedit console doc (Rich Trott) [#4225](https://github.com/nodejs/node/pull/4225)
+* [[`4ccf04c229`](https://github.com/nodejs/node/commit/4ccf04c229)] - **doc**: add mcollina to collaborators (Matteo Collina) [#4220](https://github.com/nodejs/node/pull/4220)
+* [[`59654c21d4`](https://github.com/nodejs/node/commit/59654c21d4)] - **doc**: add rmg to collaborators (Ryan Graham) [#4219](https://github.com/nodejs/node/pull/4219)
+* [[`bfe1a6bd2b`](https://github.com/nodejs/node/commit/bfe1a6bd2b)] - **doc**: add calvinmetcalf to collaborators (Calvin Metcalf) [#4218](https://github.com/nodejs/node/pull/4218)
+* [[`5140c404ae`](https://github.com/nodejs/node/commit/5140c404ae)] - **doc**: harmonize description of `ca` argument (Ben Noordhuis) [#4213](https://github.com/nodejs/node/pull/4213)
+* [[`2e642051cf`](https://github.com/nodejs/node/commit/2e642051cf)] - **doc**: copyedit child_process doc (Rich Trott) [#4188](https://github.com/nodejs/node/pull/4188)
+* [[`7920f8dbde`](https://github.com/nodejs/node/commit/7920f8dbde)] - **doc**: copyedit buffer doc (Rich Trott) [#4187](https://github.com/nodejs/node/pull/4187)
+* [[`c35a409cbe`](https://github.com/nodejs/node/commit/c35a409cbe)] - **doc**: clarify assert.fail doc (Rich Trott) [#4186](https://github.com/nodejs/node/pull/4186)
+* [[`6235fdf72e`](https://github.com/nodejs/node/commit/6235fdf72e)] - **doc**: copyedit addons doc (Rich Trott) [#4185](https://github.com/nodejs/node/pull/4185)
+* [[`990e7ff93e`](https://github.com/nodejs/node/commit/990e7ff93e)] - **doc**: update AUTHORS list (Rod Vagg) [#4183](https://github.com/nodejs/node/pull/4183)
+* [[`8d676ef55e`](https://github.com/nodejs/node/commit/8d676ef55e)] - **doc**: change references from node to Node.js (Roman Klauke) [#4177](https://github.com/nodejs/node/pull/4177)
+* [[`1c34b139a2`](https://github.com/nodejs/node/commit/1c34b139a2)] - **doc**: add brief Node.js overview to README (wurde) [#4174](https://github.com/nodejs/node/pull/4174)
+* [[`27b9b72ab0`](https://github.com/nodejs/node/commit/27b9b72ab0)] - **doc**: add iarna to collaborators (Rebecca Turner) [#4144](https://github.com/nodejs/node/pull/4144)
+* [[`683d8dd564`](https://github.com/nodejs/node/commit/683d8dd564)] - **doc**: add JungMinu to collaborators (Minwoo Jung) [#4143](https://github.com/nodejs/node/pull/4143)
+* [[`17b06dfa94`](https://github.com/nodejs/node/commit/17b06dfa94)] - **doc**: add zkat to collaborators (Kat Marchán) [#4142](https://github.com/nodejs/node/pull/4142)
+* [[`39364c4c72`](https://github.com/nodejs/node/commit/39364c4c72)] - **doc**: improve child_process.markdown wording (yorkie) [#4138](https://github.com/nodejs/node/pull/4138)
+* [[`abe452835f`](https://github.com/nodejs/node/commit/abe452835f)] - **doc**: url.format - true slash postfix behaviour (fansworld-claudio) [#4119](https://github.com/nodejs/node/pull/4119)
+* [[`6dd375cfe2`](https://github.com/nodejs/node/commit/6dd375cfe2)] - **doc**: document backlog for server.listen() variants (Jan Schär) [#4025](https://github.com/nodejs/node/pull/4025)
+* [[`b71a3b363a`](https://github.com/nodejs/node/commit/b71a3b363a)] - **doc**: fixup socket.remoteAddress (Arthur Gautier) [#4198](https://github.com/nodejs/node/pull/4198)
+* [[`e2fe214857`](https://github.com/nodejs/node/commit/e2fe214857)] - **doc**: add links and backticks around names (jpersson) [#4054](https://github.com/nodejs/node/pull/4054)
+* [[`bb158f8aed`](https://github.com/nodejs/node/commit/bb158f8aed)] - **doc**: s/node.js/Node.js in readme (Rod Vagg) [#3998](https://github.com/nodejs/node/pull/3998)
+* [[`f55491ad47`](https://github.com/nodejs/node/commit/f55491ad47)] - **doc**: move fs.existsSync() deprecation message (Martin Forsberg) [#3942](https://github.com/nodejs/node/pull/3942)
+* [[`8c5b847f5b`](https://github.com/nodejs/node/commit/8c5b847f5b)] - **doc**: Describe FIPSDIR environment variable (Stefan Budeanu) [#3752](https://github.com/nodejs/node/pull/3752)
+* [[`70c95ea0e5`](https://github.com/nodejs/node/commit/70c95ea0e5)] - **doc**: add warning about Windows process groups (Roman Klauke) [#3681](https://github.com/nodejs/node/pull/3681)
+* [[`46c59b7256`](https://github.com/nodejs/node/commit/46c59b7256)] - **doc**: add CTC meeting minutes 2015-10-28 (Rod Vagg) [#3661](https://github.com/nodejs/node/pull/3661)
+* [[`7ffd299a1d`](https://github.com/nodejs/node/commit/7ffd299a1d)] - **doc**: add final full stop in CONTRIBUTING.md (Emily Aviva Kapor-Mater) [#3576](https://github.com/nodejs/node/pull/3576)
+* [[`1f78bff7ce`](https://github.com/nodejs/node/commit/1f78bff7ce)] - **doc**: add TSC meeting minutes 2015-10-21 (Rod Vagg) [#3480](https://github.com/nodejs/node/pull/3480)
+* [[`2e623ff024`](https://github.com/nodejs/node/commit/2e623ff024)] - **doc**: add TSC meeting minutes 2015-10-14 (Rod Vagg) [#3463](https://github.com/nodejs/node/pull/3463)
+* [[`b9c69964bb`](https://github.com/nodejs/node/commit/b9c69964bb)] - **doc**: add TSC meeting minutes 2015-10-07 (Rod Vagg) [#3364](https://github.com/nodejs/node/pull/3364)
+* [[`f31d23c724`](https://github.com/nodejs/node/commit/f31d23c724)] - **doc**: add TSC meeting minutes 2015-09-30 (Rod Vagg) [#3235](https://github.com/nodejs/node/pull/3235)
+* [[`ae8e3af178`](https://github.com/nodejs/node/commit/ae8e3af178)] - **doc**: update irc channels: #node.js and #node-dev (Nelson Pecora) [#2743](https://github.com/nodejs/node/pull/2743)
+* [[`830caeb1bd`](https://github.com/nodejs/node/commit/830caeb1bd)] - **doc, test**: symbols as event names (Bryan English) [#4151](https://github.com/nodejs/node/pull/4151)
+* [[`82cbfcdcbe`](https://github.com/nodejs/node/commit/82cbfcdcbe)] - **docs**: update gpg key for Myles Borins (Myles Borins) [#4657](https://github.com/nodejs/node/pull/4657)
+* [[`50b72aa5a3`](https://github.com/nodejs/node/commit/50b72aa5a3)] - **docs**: fix npm command in releases.md (Myles Borins) [#4656](https://github.com/nodejs/node/pull/4656)
+* [[`5bf56882e1`](https://github.com/nodejs/node/commit/5bf56882e1)] - **fs,doc**: use `target` instead of `destination` (yorkie) [#3912](https://github.com/nodejs/node/pull/3912)
+* [[`41fcda840c`](https://github.com/nodejs/node/commit/41fcda840c)] - **http**: use `self.keepAlive` instead of `self.options.keepAlive` (Damian Schenkelman) [#4407](https://github.com/nodejs/node/pull/4407)
+* [[`3ff237333d`](https://github.com/nodejs/node/commit/3ff237333d)] - **http**: Remove an unnecessary assignment (Bo Borgerson) [#4323](https://github.com/nodejs/node/pull/4323)
+* [[`39dc054572`](https://github.com/nodejs/node/commit/39dc054572)] - **http**: remove excess calls to removeSocket (Dave) [#4172](https://github.com/nodejs/node/pull/4172)
+* [[`751fbd84dd`](https://github.com/nodejs/node/commit/751fbd84dd)] - **https**: use `servername` in agent key (Fedor Indutny) [#4389](https://github.com/nodejs/node/pull/4389)
+* [[`7a1a0a0055`](https://github.com/nodejs/node/commit/7a1a0a0055)] - **lib**: remove unused modules (Rich Trott) [#4683](https://github.com/nodejs/node/pull/4683)
+* [[`3d81ea99bb`](https://github.com/nodejs/node/commit/3d81ea99bb)] - **lib,test**: update let to const where applicable (Sakthipriyan Vairamani) [#3152](https://github.com/nodejs/node/pull/3152)
+* [[`8a9869eeab`](https://github.com/nodejs/node/commit/8a9869eeab)] - **module**: fix column offsets in errors (Tristian Flanagan) [#2867](https://github.com/nodejs/node/pull/2867)
+* [[`0ae90ecd3d`](https://github.com/nodejs/node/commit/0ae90ecd3d)] - **module,repl**: remove repl require() hack (Ben Noordhuis) [#4026](https://github.com/nodejs/node/pull/4026)
+* [[`a7367fdc1e`](https://github.com/nodejs/node/commit/a7367fdc1e)] - **net**: small code cleanup (Jan Schär) [#3943](https://github.com/nodejs/node/pull/3943)
+* [[`03e9495cc2`](https://github.com/nodejs/node/commit/03e9495cc2)] - **node**: remove unused variables in AppendExceptionLine (Yazhong Liu) [#4264](https://github.com/nodejs/node/pull/4264)
+* [[`06113b8711`](https://github.com/nodejs/node/commit/06113b8711)] - **node**: s/doNTCallbackX/nextTickCallbackWithXArgs/ (Rod Vagg) [#4167](https://github.com/nodejs/node/pull/4167)
+* [[`8ce6843fe4`](https://github.com/nodejs/node/commit/8ce6843fe4)] - **os**: fix crash in GetInterfaceAddresses (Martin Bark) [#4272](https://github.com/nodejs/node/pull/4272)
+* [[`53dcbb6aa4`](https://github.com/nodejs/node/commit/53dcbb6aa4)] - **repl**: remove unused function (Rich Trott)
+* [[`db0e906fc1`](https://github.com/nodejs/node/commit/db0e906fc1)] - **repl**: Fixed node repl history edge case. (Mudit Ameta) [#4108](https://github.com/nodejs/node/pull/4108)
+* [[`9855fab05f`](https://github.com/nodejs/node/commit/9855fab05f)] - **repl**: use String#repeat instead of Array#join (Evan Lucas) [#3900](https://github.com/nodejs/node/pull/3900)
+* [[`41882e4077`](https://github.com/nodejs/node/commit/41882e4077)] - **repl**: fix require('3rdparty') regression (Ben Noordhuis) [#4215](https://github.com/nodejs/node/pull/4215)
+* [[`93afc39d4a`](https://github.com/nodejs/node/commit/93afc39d4a)] - **repl**: attach location info to syntax errors (cjihrig) [#4013](https://github.com/nodejs/node/pull/4013)
+* [[`d4806675a6`](https://github.com/nodejs/node/commit/d4806675a6)] - **repl**: display error message when loading directory (Prince J Wesley) [#4170](https://github.com/nodejs/node/pull/4170)
+* [[`3080bdc7d7`](https://github.com/nodejs/node/commit/3080bdc7d7)] - **src**: define Is* util functions with macros (cjihrig) [#4118](https://github.com/nodejs/node/pull/4118)
+* [[`2b8a32a13b`](https://github.com/nodejs/node/commit/2b8a32a13b)] - **src**: refactor vcbuild configure args creation (Rod Vagg) [#3399](https://github.com/nodejs/node/pull/3399)
+* [[`d47f6ba768`](https://github.com/nodejs/node/commit/d47f6ba768)] - **src**: fix deprecation message for ErrnoException (Martin von Gagern) [#4269](https://github.com/nodejs/node/pull/4269)
+* [[`5ba08fbf76`](https://github.com/nodejs/node/commit/5ba08fbf76)] - **src**: fix line numbers on core errors (cjihrig) [#4254](https://github.com/nodejs/node/pull/4254)
+* [[`70974e9362`](https://github.com/nodejs/node/commit/70974e9362)] - **src**: use GetCurrentProcessId() for process.pid (Ben Noordhuis) [#4163](https://github.com/nodejs/node/pull/4163)
+* [[`c96eca164f`](https://github.com/nodejs/node/commit/c96eca164f)] - **src**: don't print garbage errors (cjihrig) [#4112](https://github.com/nodejs/node/pull/4112)
+* [[`f61412c753`](https://github.com/nodejs/node/commit/f61412c753)] - **test**: mark test-debug-no-context is flaky (Rich Trott) [#4421](https://github.com/nodejs/node/pull/4421)
+* [[`46d8c93ed2`](https://github.com/nodejs/node/commit/46d8c93ed2)] - **test**: don't use cwd for relative path (Johan Bergström) [#4477](https://github.com/nodejs/node/pull/4477)
+* [[`b6124ea39c`](https://github.com/nodejs/node/commit/b6124ea39c)] - **test**: write to tmp dir rather than fixture dir (Rich Trott) [#4489](https://github.com/nodejs/node/pull/4489)
+* [[`350fa664bb`](https://github.com/nodejs/node/commit/350fa664bb)] - **test**: don't assume a certain folder structure (Johan Bergström) [#3325](https://github.com/nodejs/node/pull/3325)
+* [[`6b2ef0efac`](https://github.com/nodejs/node/commit/6b2ef0efac)] - **test**: make temp path customizable (Johan Bergström) [#3325](https://github.com/nodejs/node/pull/3325)
+* [[`f1837703a9`](https://github.com/nodejs/node/commit/f1837703a9)] - **test**: remove unused vars from parallel tests (Rich Trott) [#4511](https://github.com/nodejs/node/pull/4511)
+* [[`b4964b099a`](https://github.com/nodejs/node/commit/b4964b099a)] - **test**: remove unused variables form http tests (Rich Trott) [#4422](https://github.com/nodejs/node/pull/4422)
+* [[`0d5a508dfb`](https://github.com/nodejs/node/commit/0d5a508dfb)] - **test**: extend timeout in Debug mode (Rich Trott) [#4431](https://github.com/nodejs/node/pull/4431)
+* [[`6e4598d5da`](https://github.com/nodejs/node/commit/6e4598d5da)] - **test**: remove unused variables from TLS tests (Rich Trott) [#4424](https://github.com/nodejs/node/pull/4424)
+* [[`7b1aa045a0`](https://github.com/nodejs/node/commit/7b1aa045a0)] - **test**: remove unused variables from HTTPS tests (Rich Trott) [#4426](https://github.com/nodejs/node/pull/4426)
+* [[`da9e5c1b01`](https://github.com/nodejs/node/commit/da9e5c1b01)] - **test**: remove unused variables from net tests (Rich Trott) [#4430](https://github.com/nodejs/node/pull/4430)
+* [[`13241bd24b`](https://github.com/nodejs/node/commit/13241bd24b)] - **test**: remove unused vars in ChildProcess tests (Rich Trott) [#4425](https://github.com/nodejs/node/pull/4425)
+* [[`2f4538ddda`](https://github.com/nodejs/node/commit/2f4538ddda)] - **test**: remove unused vars (Rich Trott) [#4536](https://github.com/nodejs/node/pull/4536)
+* [[`dffe83ccd6`](https://github.com/nodejs/node/commit/dffe83ccd6)] - **test**: remove unused modules (Rich Trott) [#4684](https://github.com/nodejs/node/pull/4684)
+* [[`c4eeb88ba1`](https://github.com/nodejs/node/commit/c4eeb88ba1)] - **test**: fix flaky cluster-disconnect-race (Brian White) [#4457](https://github.com/nodejs/node/pull/4457)
+* [[`7caf87bf6c`](https://github.com/nodejs/node/commit/7caf87bf6c)] - **test**: fix flaky test-http-agent-keepalive (Rich Trott) [#4524](https://github.com/nodejs/node/pull/4524)
+* [[`25c41d084d`](https://github.com/nodejs/node/commit/25c41d084d)] - **test**: remove flaky designations for tests (Rich Trott) [#4519](https://github.com/nodejs/node/pull/4519)
+* [[`b8f097ece2`](https://github.com/nodejs/node/commit/b8f097ece2)] - **test**: fix flaky streams test (Rich Trott) [#4516](https://github.com/nodejs/node/pull/4516)
+* [[`c24fa1437c`](https://github.com/nodejs/node/commit/c24fa1437c)] - **test**: inherit JOBS from environment (Johan Bergström) [#4495](https://github.com/nodejs/node/pull/4495)
+* [[`7dc90e9e7f`](https://github.com/nodejs/node/commit/7dc90e9e7f)] - **test**: remove time check (Rich Trott) [#4494](https://github.com/nodejs/node/pull/4494)
+* [[`7ca3c6c388`](https://github.com/nodejs/node/commit/7ca3c6c388)] - **test**: refactor test-fs-empty-readStream (Rich Trott) [#4490](https://github.com/nodejs/node/pull/4490)
+* [[`610727dea7`](https://github.com/nodejs/node/commit/610727dea7)] - **test**: clarify role of domains in test (Rich Trott) [#4474](https://github.com/nodejs/node/pull/4474)
+* [[`1ae0e355b9`](https://github.com/nodejs/node/commit/1ae0e355b9)] - **test**: improve assert message (Rich Trott) [#4461](https://github.com/nodejs/node/pull/4461)
+* [[`e70c88df56`](https://github.com/nodejs/node/commit/e70c88df56)] - **test**: remove unused assert module imports (Rich Trott) [#4438](https://github.com/nodejs/node/pull/4438)
+* [[`c77fc71f9b`](https://github.com/nodejs/node/commit/c77fc71f9b)] - **test**: remove unused var from test-assert.js (Rich Trott) [#4405](https://github.com/nodejs/node/pull/4405)
+* [[`f613b3033f`](https://github.com/nodejs/node/commit/f613b3033f)] - **test**: add test-domain-exit-dispose-again back (Julien Gilli) [#4256](https://github.com/nodejs/node/pull/4256)
+* [[`f5bfacd858`](https://github.com/nodejs/node/commit/f5bfacd858)] - **test**: remove unused `util` imports (Rich Trott) [#4562](https://github.com/nodejs/node/pull/4562)
+* [[`d795301025`](https://github.com/nodejs/node/commit/d795301025)] - **test**: remove unnecessary assignments (Rich Trott) [#4563](https://github.com/nodejs/node/pull/4563)
+* [[`acc3d66934`](https://github.com/nodejs/node/commit/acc3d66934)] - **test**: move ArrayStream to common (cjihrig) [#4027](https://github.com/nodejs/node/pull/4027)
+* [[`6c0021361c`](https://github.com/nodejs/node/commit/6c0021361c)] - **test**: refactor test-net-connect-options-ipv6 (Rich Trott) [#4395](https://github.com/nodejs/node/pull/4395)
+* [[`29804e00ad`](https://github.com/nodejs/node/commit/29804e00ad)] - **test**: use platformTimeout() in more places (Brian White) [#4387](https://github.com/nodejs/node/pull/4387)
+* [[`761af37d0e`](https://github.com/nodejs/node/commit/761af37d0e)] - **test**: fix race condition in test-http-client-onerror (Devin Nakamura) [#4346](https://github.com/nodejs/node/pull/4346)
+* [[`980852165f`](https://github.com/nodejs/node/commit/980852165f)] - **test**: fix flaky test-net-error-twice (Brian White) [#4342](https://github.com/nodejs/node/pull/4342)
+* [[`1bc44e79d3`](https://github.com/nodejs/node/commit/1bc44e79d3)] - **test**: try other ipv6 localhost alternatives (Brian White) [#4325](https://github.com/nodejs/node/pull/4325)
+* [[`44dbe15640`](https://github.com/nodejs/node/commit/44dbe15640)] - **test**: fix debug-port-cluster flakiness (Ben Noordhuis) [#4310](https://github.com/nodejs/node/pull/4310)
+* [[`73e781172b`](https://github.com/nodejs/node/commit/73e781172b)] - **test**: add test for tls.parseCertString (Evan Lucas) [#4283](https://github.com/nodejs/node/pull/4283)
+* [[`15c295a21b`](https://github.com/nodejs/node/commit/15c295a21b)] - **test**: use regular timeout times for ARMv8 (Jeremiah Senkpiel) [#4248](https://github.com/nodejs/node/pull/4248)
+* [[`fd250b8fab`](https://github.com/nodejs/node/commit/fd250b8fab)] - **test**: parallelize test-repl-persistent-history (Jeremiah Senkpiel) [#4247](https://github.com/nodejs/node/pull/4247)
+* [[`9a0f156e5a`](https://github.com/nodejs/node/commit/9a0f156e5a)] - **test**: fix domain-top-level-error-handler-throw (Santiago Gimeno) [#4364](https://github.com/nodejs/node/pull/4364)
+* [[`6bc1b1c259`](https://github.com/nodejs/node/commit/6bc1b1c259)] - **test**: don't assume openssl s_client supports -ssl3 (Ben Noordhuis) [#4204](https://github.com/nodejs/node/pull/4204)
+* [[`d00b9fc66f`](https://github.com/nodejs/node/commit/d00b9fc66f)] - **test**: fix tls-inception flakiness (Santiago Gimeno) [#4195](https://github.com/nodejs/node/pull/4195)
+* [[`c41b280a2b`](https://github.com/nodejs/node/commit/c41b280a2b)] - **test**: fix tls-inception (Santiago Gimeno) [#4195](https://github.com/nodejs/node/pull/4195)
+* [[`6f4ab1d1ab`](https://github.com/nodejs/node/commit/6f4ab1d1ab)] - **test**: mark test-cluster-shared-leak flaky (Rich Trott) [#4162](https://github.com/nodejs/node/pull/4162)
+* [[`90498e2a68`](https://github.com/nodejs/node/commit/90498e2a68)] - **test**: skip long path tests on non-Windows (Rafał Pocztarski) [#4116](https://github.com/nodejs/node/pull/4116)
+* [[`c9100d78f3`](https://github.com/nodejs/node/commit/c9100d78f3)] - **test**: fix flaky test-net-socket-local-address (Rich Trott) [#4109](https://github.com/nodejs/node/pull/4109)
+* [[`ac939d51d9`](https://github.com/nodejs/node/commit/ac939d51d9)] - **test**: improve cluster-disconnect-handles test (Brian White) [#4084](https://github.com/nodejs/node/pull/4084)
+* [[`22ba1b4115`](https://github.com/nodejs/node/commit/22ba1b4115)] - **test**: eliminate multicast test FreeBSD flakiness (Rich Trott) [#4042](https://github.com/nodejs/node/pull/4042)
+* [[`2ee7853bb7`](https://github.com/nodejs/node/commit/2ee7853bb7)] - **test**: fix http-many-ended-pipelines flakiness (Santiago Gimeno) [#4041](https://github.com/nodejs/node/pull/4041)
+* [[`a77dcfec06`](https://github.com/nodejs/node/commit/a77dcfec06)] - **test**: use platform-based timeout for reliability (Rich Trott) [#4015](https://github.com/nodejs/node/pull/4015)
+* [[`3f0ff879cf`](https://github.com/nodejs/node/commit/3f0ff879cf)] - **test**: fix time resolution constraint (Gireesh Punathil) [#3981](https://github.com/nodejs/node/pull/3981)
+* [[`22b88e1c48`](https://github.com/nodejs/node/commit/22b88e1c48)] - **test**: add TAP diagnostic message for retried tests (Rich Trott) [#3960](https://github.com/nodejs/node/pull/3960)
+* [[`22d2887b1c`](https://github.com/nodejs/node/commit/22d2887b1c)] - **test**: add OS X to module loading error test (Evan Lucas) [#3901](https://github.com/nodejs/node/pull/3901)
+* [[`e2141cb75e`](https://github.com/nodejs/node/commit/e2141cb75e)] - **test**: skip instead of fail when mem constrained (Michael Cornacchia) [#3697](https://github.com/nodejs/node/pull/3697)
+* [[`166523d0ed`](https://github.com/nodejs/node/commit/166523d0ed)] - **test**: fix race condition in unrefd interval test (Michael Cornacchia) [#3550](https://github.com/nodejs/node/pull/3550)
+* [[`86b47e8dc0`](https://github.com/nodejs/node/commit/86b47e8dc0)] - **timers**: optimize callback call: bind -> arrow (Andrei Sedoi) [#4038](https://github.com/nodejs/node/pull/4038)
+* [[`4d37472ea7`](https://github.com/nodejs/node/commit/4d37472ea7)] - **tls_wrap**: clear errors on return (Fedor Indutny) [#4709](https://github.com/nodejs/node/pull/4709)
+* [[`5b695d0343`](https://github.com/nodejs/node/commit/5b695d0343)] - **tls_wrap**: inherit from the `AsyncWrap` first (Fedor Indutny) [#4268](https://github.com/nodejs/node/pull/4268)
+* [[`0efc35e6d8`](https://github.com/nodejs/node/commit/0efc35e6d8)] - **tls_wrap**: slice buffer properly in `ClearOut` (Fedor Indutny) [#4184](https://github.com/nodejs/node/pull/4184)
+* [[`628cb8657c`](https://github.com/nodejs/node/commit/628cb8657c)] - **tools**: add .editorconfig (ronkorving) [#2993](https://github.com/nodejs/node/pull/2993)
+* [[`69fef19624`](https://github.com/nodejs/node/commit/69fef19624)] - **tools**: implement no-unused-vars for eslint (Rich Trott) [#4536](https://github.com/nodejs/node/pull/4536)
+* [[`3ee16706f2`](https://github.com/nodejs/node/commit/3ee16706f2)] - **tools**: enforce `throw new Error()` with lint rule (Rich Trott) [#3714](https://github.com/nodejs/node/pull/3714)
+* [[`32801de4ef`](https://github.com/nodejs/node/commit/32801de4ef)] - **tools**: Use `throw new Error()` consistently (Rich Trott) [#3714](https://github.com/nodejs/node/pull/3714)
+* [[`f413fae0cd`](https://github.com/nodejs/node/commit/f413fae0cd)] - **tools**: add tap output to cpplint (Johan Bergström) [#3448](https://github.com/nodejs/node/pull/3448)
+* [[`efa30dd2f0`](https://github.com/nodejs/node/commit/efa30dd2f0)] - **tools**: enable prefer-const eslint rule (Sakthipriyan Vairamani) [#3152](https://github.com/nodejs/node/pull/3152)
+* [[`dd0c925896`](https://github.com/nodejs/node/commit/dd0c925896)] - **udp**: remove a needless instanceof Buffer check (ronkorving) [#4301](https://github.com/nodejs/node/pull/4301)
+* [[`f4414102ed`](https://github.com/nodejs/node/commit/f4414102ed)] - **util**: faster arrayToHash (Jackson Tian)
+* [[`b421119984`](https://github.com/nodejs/node/commit/b421119984)] - **util**: determine object types in C++ (cjihrig) [#4100](https://github.com/nodejs/node/pull/4100)
+* [[`6a7c9d9293`](https://github.com/nodejs/node/commit/6a7c9d9293)] - **util**: move .decorateErrorStack to internal/util (Ben Noordhuis) [#4026](https://github.com/nodejs/node/pull/4026)
+* [[`422a865d46`](https://github.com/nodejs/node/commit/422a865d46)] - **util**: add decorateErrorStack() (cjihrig) [#4013](https://github.com/nodejs/node/pull/4013)
+* [[`2d5380ea25`](https://github.com/nodejs/node/commit/2d5380ea25)] - **util**: fix constructor/instanceof checks (Brian White) [#3385](https://github.com/nodejs/node/pull/3385)
+* [[`1bf84b9d41`](https://github.com/nodejs/node/commit/1bf84b9d41)] - **util,src**: allow lookup of hidden values (cjihrig) [#3988](https://github.com/nodejs/node/pull/3988)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.5/node-v4.2.5-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.5/node-v4.2.5-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.5/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.5/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.5/node-v4.2.5.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.5/node-v4.2.5-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.5/node-v4.2.5.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.5/<br>
+Documentation: https://nodejs.org/docs/v4.2.5/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+c504aa1a0b7d7a51efe2403d72ef35a4742b5321fd23a2af52e06f9986a5ca70  node-v4.2.5-darwin-x64.tar.gz
+e06aa1fbbc35e46e1bc550f72ee01f89f1671b1341a73890eb75de995253d7f3  node-v4.2.5-darwin-x64.tar.xz
+01edb44794cfe365560b644b7c8f8431b3531f2c8ad0a47e91d7d0c8761b900f  node-v4.2.5-headers.tar.gz
+c287b624980bf86d6d050fa7f41b4a288929c37d4ff3ce03a256cc8df40d0481  node-v4.2.5-headers.tar.xz
+b09a144acb67a8de6f873bbf05ccdf2accc1fd005127a5ab385f78a830fd3ddc  node-v4.2.5-linux-arm64.tar.gz
+e2d68f48153548ec9c0a51c91c3b169d0a9e205ae357919acfd03cdc0fcea0a9  node-v4.2.5-linux-arm64.tar.xz
+bcc74b00760293b886624c844abf3d4502baab06c454a856b46b165bf5a48b78  node-v4.2.5-linux-armv6l.tar.gz
+72b9b7d5277747d84b061513991b671ee0aa4448e596721fe6cbb6dfb86d56f3  node-v4.2.5-linux-armv6l.tar.xz
+0146ba2fe72e81a4a682ac114cb58c802100717ed900172f3ec3664c8f3ee0f7  node-v4.2.5-linux-armv7l.tar.gz
+4e77203e648d8e090ccc3b49f90bd4a9f2c0edcadaf4b3978d35f02b394b0529  node-v4.2.5-linux-armv7l.tar.xz
+3ed12d7ee8d911b87aed7f19640ec3d97a038330709ca4e0d137e8882b0f9cc4  node-v4.2.5-linux-x64.tar.gz
+59e5296e241d98714c452630b62b8f6c71fe7fbbde883bfda191ba29d8bfb457  node-v4.2.5-linux-x64.tar.xz
+64e1564c0302503c98d70824b940c6679bfe38da74fa7bb387ee0f4665969031  node-v4.2.5-linux-x86.tar.gz
+90a4aa5279963939d8d445702659d6222e0c797db376ada123f12651e3891d50  node-v4.2.5-linux-x86.tar.xz
+178d9ccd9408d8d5b59f37768d98a78f71437b30e7a02e96885a4f0f5324e060  node-v4.2.5.pkg
+3ce9a69bed1b15f251b6ca714901e45cb429a8e9e0ff9250a7735e7e58e942c9  node-v4.2.5-sunos-x64.tar.gz
+abf7faeeb2aa460d383b6f7bc9b7bf57a43fe64de7b6e386e2fa6bd0f66dff49  node-v4.2.5-sunos-x64.tar.xz
+8acc5a595e3d9bdcdfdb0cfcd7524266fc091306d570fc84cb8cbad5490ca091  node-v4.2.5-sunos-x86.tar.gz
+f79f802b706ab275571109459051567b2a8ece7c8bc59c548a93064821aa712a  node-v4.2.5-sunos-x86.tar.xz
+00162c5a8fcc5c35b27df26c49a83c7f4d52b1c963339a8a20401b81743f7fad  node-v4.2.5.tar.gz
+8a3c73f41096069f84d77c2501d34a29b40ec3aac44a57b079707b58e59b2c66  node-v4.2.5.tar.xz
+4d3a54e85e1d4f5b761be17c9a605d2e66a3a6b0979ec9aee657ed5e50a0f475  node-v4.2.5-x64.msi
+7425c143ee231961de530db4d8728bc2fae029ed230d25eac55dbc9b00b82294  node-v4.2.5-x86.msi
+4278bf5c1254ab4032ce9de6f3fa6db6534743b0fff0952c9b31d2911c4b70c3  win-x64/node.exe
+aac282baed734bff1f1fcd2716a592929a8dddd926388f6f6cb5fdb41637e96e  win-x64/node.lib
+9acbcfdd5a56795892f282a3f51e07de28ad6fe803e5882e10466aaf361c5ab2  win-x86/node.exe
+59b8959365e95d71270b3031b879c7263f76a36e1643d28129fd38f71ef28ab3  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJWoAAFAAoJEJM7AfQLXKlGV0AH/jiA0DA6haJmXVBzwlRRFFxg
+9Yg90MdMZN6jPM4gUp+LE5Dy7MYKi6oO00GW8Socfn5GLzBide4U4Iwe93Bpxd6A
+6o35rcTtT9sKil4nvHgk54O0vxiUQY13FvWnRIzP+kATK3swzVkXR4zRqSjW6+Dn
+m+uLdGLoHwn3gOO4r6OhNBAC4luF5FupMYaLybwARvr6qFfFFieUqV3BPSSpUORx
+JoOIDXmf8fjGIG3o6tjrSMpFfqs2rwHHucb83fZ0MjQPP+DCsw11LTqhhxYzqPgg
+vUZhPiuXQTGAVOAg864DvzHlNlBGqNoF1VFak/cpzza9CX2AIHWNcA3k9j0P88Q=
+=68ul
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.2.6.md b/locale/uk/blog/release/v4.2.6.md
new file mode 100755
index 0000000000000..c3afeb00095fa
--- /dev/null
+++ b/locale/uk/blog/release/v4.2.6.md
@@ -0,0 +1,90 @@
+---
+date: 2016-01-21T22:26:03.743Z
+version: 4.2.6
+category: release
+title: Node v4.2.6 (LTS)
+slug: node-v4-2-6
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+* Fix regression in debugger and profiler functionality
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Commits
+
+* [[`1408f7abb1`](https://github.com/nodejs/node/commit/1408f7abb1)] - **module,src**: do not wrap modules with -1 lineOffset (cjihrig) [#4298](https://github.com/nodejs/node/pull/4298)
+* [[`1f8e1472cc`](https://github.com/nodejs/node/commit/1f8e1472cc)] - **test**: add test for debugging one line files (cjihrig) [#4298](https://github.com/nodejs/node/pull/4298)
+
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.2.6/node-v4.2.6-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.2.6/node-v4.2.6-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.2.6/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.2.6/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.2.6/node-v4.2.6.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.2.6/node-v4.2.6-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.2.6/node-v4.2.6.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.2.6/<br>
+Documentation: https://nodejs.org/docs/v4.2.6/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+259ea77784013c1124506e3d90ee6847b2b9d3c066b6626ed62ebb31ed8e6fe3  node-v4.2.6-darwin-x64.tar.gz
+2d7091eed56ede7c28ee5499697b84c289c37c06152c804f4eff7e0edd5fe7e1  node-v4.2.6-darwin-x64.tar.xz
+a83ba921b951809aec81259a64c6d071c7ed443e8460898c42a8269c598930f9  node-v4.2.6-headers.tar.gz
+9df143eaead3b60bf2dce35a25e9c2d3f48bd10b0200e7218e3d45d7a83a7d36  node-v4.2.6-headers.tar.xz
+f0aadf2941d91bfac449cdc8c904a926f6d384e45a8f6443a2f0153501753427  node-v4.2.6-linux-arm64.tar.gz
+29e9c0ff27a5ec560f1d4ec8749e99d36a3640d0c7ef26f7c9dfa46bffd6c88a  node-v4.2.6-linux-arm64.tar.xz
+61eb9963c188fb63565461032db1ccce1bae741f985b7f237043dea16ca85531  node-v4.2.6-linux-armv6l.tar.gz
+f57d818a2e65c301704e251bf18a12c81248b0322762f83a3d17a089c8aa19e9  node-v4.2.6-linux-armv6l.tar.xz
+104d75d428a77a23cc646757cc5624d22fd8705026cf712ef6b826368efeae6f  node-v4.2.6-linux-armv7l.tar.gz
+a27e40d7cb808345b0c773f93895b64660b882cbe292cef9cea0ac23cbb0c00c  node-v4.2.6-linux-armv7l.tar.xz
+656d8bff06cc5e108b83176f81de7e1eb16392ae0958ec4a7bca2a3a309333a1  node-v4.2.6-linux-x64.tar.gz
+919498f2eb855ef0468b428b97d9d3f604d0f83417502d65b98c136786eb94d5  node-v4.2.6-linux-x64.tar.xz
+a96ce235e67e994aa5adec8255e13d4fbccd9c5b09b5e9554347dac2b1c5c8a1  node-v4.2.6-linux-x86.tar.gz
+3530eced1fa40393ff9e9c412879924e98dee6a5a57347e6d4f764b0d110944a  node-v4.2.6-linux-x86.tar.xz
+417b613ccae913e8ecb7e9836c7c0b2163feb27736c2478127d8046875aeaa0f  node-v4.2.6.pkg
+96ccfeb7e15123111215d2093aa6c78abc7a43898c0a6c1838a56896e0b5493e  node-v4.2.6-sunos-x64.tar.gz
+cb7f3901da967c1d71c04603a6ddf5488be9f149e26c54d3d40ab66efe64b4cc  node-v4.2.6-sunos-x64.tar.xz
+83505ceb87e584ff15f47a2ab25ee77378791be56b06cfe94fe24155f229e772  node-v4.2.6-sunos-x86.tar.gz
+41bb9a20ec77f42632345557d42f9603eb3a7785f729ce7c2742caa0f1a720af  node-v4.2.6-sunos-x86.tar.xz
+ea5e357db8817052b17496d607c719d809ed1383e8fcf7c8ffc5214e705aefdd  node-v4.2.6.tar.gz
+dcb935647f9e32fc90db52d393f00c9868ba9d84c5ebe5ddd766e225deb52c40  node-v4.2.6.tar.xz
+31556639d865e20fabe104dfe36ce148b4d046d00b35122a7261ff03ed5ded3a  node-v4.2.6-x64.msi
+b631c71151f127311c2a81fc65a9b4fc403acf570810b5b2563300db49eb2d98  node-v4.2.6-x86.msi
+3b595ef2e9232b5bebabc69dbf52316d0e7a7c2b2a2e62abae89787e6f001e44  win-x64/node.exe
+6863f29249ce79ddccb2ffcf1966d630e4f6efea695c6b20695d4d6a64828799  win-x64/node.lib
+4e9ca71d4bd56df6b2afa51c2a0937ff94ae7c3f04c1306a4d3bd77ca232cea8  win-x86/node.exe
+fd653c44129836021be6ad5f2822807158fb50f92c4bc4c91eda3e19ce0e0c40  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJWoVpPAAoJEJM7AfQLXKlGE1UH/2AjSQrV3Gi46uImVEg2NiAO
+qRYxoUL0ET1qESFcmSoufRfedFrG3Y1ukPNv4qRlMKSRvEuxSWYG6lEX/z6nUyJv
+9l8xii1yY2/gFIuwqEkjJzowEhi/yCSMZRg5iXE+0uD9IBYjFIyaTI24G6IjfUTE
+xt4vGxomqZeJij3JNJw+t4RReO56UIFcYS8cKp9g1NDdpkLab7qcjQ8QwpUZA+Oi
+IuQ9H5rLLXtqOOjHbo+TAtEM66K38BU1g0tneWznMecsjuAWWzSDTNNbZPaRY9hJ
+f8g37cwLOSO8GVviKfBwIaT0egfjexPrc3fPLQ6WMLSEAghwOib1zB/x1f6MzLg=
+=ivFL
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.3.0.md b/locale/uk/blog/release/v4.3.0.md
new file mode 100755
index 0000000000000..0bfc5f3dc0f3b
--- /dev/null
+++ b/locale/uk/blog/release/v4.3.0.md
@@ -0,0 +1,94 @@
+---
+date: 2016-02-09T17:32:54.296Z
+version: 4.3.0
+category: release
+title: Node v4.3.0 (LTS)
+slug: node-v4-3-0
+layout: blog-post.hbs
+author: James M Snell
+---
+
+This is an important security release. For full details see https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ for details on patched vulnerabilities.
+
+### Notable changes
+
+* **http**: fix defects in HTTP header parsing for requests and responses that can allow request smuggling (CVE-2016-2086) or response splitting (CVE-2016-2216). HTTP header parsing now aligns more closely with the HTTP spec including restricting the acceptable characters.
+* **http-parser**: upgrade from 2.5.0 to 2.5.1
+* **openssl**: upgrade from 1.0.2e to 1.0.2f. To mitigate against the Logjam attack, TLS clients now reject Diffie-Hellman handshakes with parameters shorter than 1024-bits, up from the previous limit of 768-bits.
+* **src**:
+  - introduce new `--security-revert={cvenum}` command line flag for selective reversion of specific CVE fixes
+  - allow the fix for CVE-2016-2216 to be selectively reverted using `--security-revert=CVE-2016-2216`
+
+### Commits
+
+* [[`d94f864abd`](https://github.com/nodejs/node/commit/d94f864abd0933c125afeb84b6f72ec709c63b43)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [#1836](https://github.com/nodejs/node/pull/1836)
+* [[`136295e202`](https://github.com/nodejs/node/commit/136295e202)] - **deps**: upgrade openssl sources to 1.0.2f (Myles Borins) [#4961](https://github.com/nodejs/node/pull/4961)
+* [[`0eae95eae3`](https://github.com/nodejs/node/commit/0eae95eae3)] - **(SEMVER-MINOR)** **deps**: update http-parser to version 2.5.1 (James M Snell)
+* [[`cf2b714b02`](https://github.com/nodejs/node/commit/cf2b714b02)] - **(SEMVER-MINOR)** **http**: strictly forbid invalid characters from headers (James M Snell)
+* [[`49ae2e0334`](https://github.com/nodejs/node/commit/49ae2e0334)] - **src**: avoid compiler warning in node_revert.cc (James M Snell)
+* [[`da3750f981`](https://github.com/nodejs/node/commit/da3750f981)] - **(SEMVER-MAJOR)** **src**: add --security-revert command line flag (James M Snell)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.3.0/node-v4.3.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.3.0/node-v4.3.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.3.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.3.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.3.0/node-v4.3.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.3.0/node-v4.3.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.3.0/node-v4.3.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.3.0/<br>
+Documentation: https://nodejs.org/docs/v4.3.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+72858adf7bc84b632f5635dd4a8030226048af5ad5cb166c7ee169dfcb4645ef  node-v4.3.0-darwin-x64.tar.gz
+b36acbb638db5091becb2edc7e450aa02dc3a8062cd11014eb79434901236ee3  node-v4.3.0-darwin-x64.tar.xz
+113a7c5689fd7a1d60160398a9cb0b03b0b88632ba0a2df148ef6e4c96986ec9  node-v4.3.0-headers.tar.gz
+34a510fd4caa2830463f3df4765ab274bb5054be7437e7ca3f47f01827f8e1c6  node-v4.3.0-headers.tar.xz
+47a52191e264efdbc36f5ec6510abd71fd5d3337d75120c2ddc6a285873763b7  node-v4.3.0-linux-arm64.tar.gz
+2d7e28d80667212547d75f7b77f1bba5b015195cebde94d62be787725ee9715b  node-v4.3.0-linux-arm64.tar.xz
+2e035c649f72b5fbd712e6cf52e83e9f013b9a266dc907d3595b1c143c9906df  node-v4.3.0-linux-armv6l.tar.gz
+eec2411bb08341982c5e40537b7660f09a8001d68d6bd7ef36254c6b813de340  node-v4.3.0-linux-armv6l.tar.xz
+49dfc4c4e5d1d07c91503c2a601665b68b6f5fc95d94517628f9a0f43b178158  node-v4.3.0-linux-armv7l.tar.gz
+ed2cc35422161e59946c3d53040e7c421ba607876f312181afb0994188c406e5  node-v4.3.0-linux-armv7l.tar.xz
+90ce6e23ad9748813742e1cf09e86fa4c0f3d53972d5dbe920a38bcc842e2d09  node-v4.3.0-linux-x64.tar.gz
+9e46eedf6cf6de8472fcf939b2ba6c78d6caaa9348f95385146ebc9cddf6470e  node-v4.3.0-linux-x64.tar.xz
+6972ed77c36f026498a0fde6b237fbc554325fa3a7426ee17ce563bdc08caa69  node-v4.3.0-linux-x86.tar.gz
+2054242f13a6bdb43ff33238dff20aeb5ef06e73a22b9e55b0a01d94c6f8dd9f  node-v4.3.0-linux-x86.tar.xz
+cafa3e7dc44fdd1459fcd81e4a770629f8fed4c74f77c446f9acde30a444bb28  node-v4.3.0.pkg
+c97723abd27c2b48ec2cbc9cc9b7dd057c96bf05c1895d7740414f84955753db  node-v4.3.0-sunos-x64.tar.gz
+6c850504d23c138c8de00731a814e8aec4ca9b96781970e3f4caa21d2d91c94d  node-v4.3.0-sunos-x64.tar.xz
+8f645328daa96702bf110cfcf2021620dc76fcb16ce80423a5f72dd23893cf71  node-v4.3.0-sunos-x86.tar.gz
+e7dac63c559050a09f8a201fab92af14d1f19cf6a6c5ad9f0d2cc53a2ffc4355  node-v4.3.0-sunos-x86.tar.xz
+18504ac6d903cd061f60a29dafcda416a078112f3404d23a7901c41a8e9706b9  node-v4.3.0.tar.gz
+4b4cb93929c2368219eb36a707b0cb87b08df5757c5c1073c18c15b79c873566  node-v4.3.0.tar.xz
+48d2a640d8d7f390cbe7f5e6ddb5a0240f1a5e49e1d6f97f222bc54a69773238  node-v4.3.0-x64.msi
+eb22e601c152b0ebad11e4ddd24b777aff6e36c8e0de92f9a088959cad3d0f47  node-v4.3.0-x86.msi
+cd7f06223a59fa7057a0b528dd411896f995a541c1e82dd838ef1b3c72d5383d  win-x64/node.exe
+6e2363d5ad5438f15373571ce44ffdd4a2bc3f8873fe9d51bbb108b34a7b7307  win-x64/node.lib
+e5bf98250aa9972cf810c52793d684eeba17afe7e1241d93b39f7110a6825b53  win-x86/node.exe
+7025ae784e4f78bb4dcb5d6635d773b3ada138b99cfea0a285a6c55311de9213  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWuhwKAAoJEHNBsVwHCHesMUUIAJIQP0LRemTTPlCgthwFlFDP
+FRiImqbIUSPCVf+lEzfBqGAOlHmPLqGLKhiaYt5TxgglomRYNuLcUhc8g19HSkvV
+KT9PU2JjSUHZ0dc2FgzlrWKZzET9DpBeNQzKHE3i26Z5SGdvVdZSShuS1WgoBzao
+SwQqB1F38mThrL0FAg7PQ80nNH/Tl+mqdJF9Yrjrblfisv+qAnFqlhSC8L78jhLc
+geWnuW22qm4CuDQp5DcwJAlYHk0P6AtVtVsvi+XUwUIe4RKpMUmvkYUa2zPF5T/9
+RtKneJXAF/hqEXhPfDE4gF0gGIVE0avHQAYV7NyXvi7R+jwhlNnwd3m0kyEdeZ4=
+=70Ju
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.3.1.md b/locale/uk/blog/release/v4.3.1.md
new file mode 100755
index 0000000000000..10f828f2afe9b
--- /dev/null
+++ b/locale/uk/blog/release/v4.3.1.md
@@ -0,0 +1,156 @@
+---
+date: 2016-02-17T17:34:38.789Z
+version: 4.3.1
+category: release
+title: Node v4.3.1 (LTS)
+slug: node-v4-3-1
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+* **buffer**
+  * make byteLength work with Buffer correctly (Jackson Tian)
+    - [#4738](https://github.com/nodejs/node/pull/4738)
+* **debugger** 
+  * guard against call from non-node context (Ben Noordhuis)
+    - [#4328](https://github.com/nodejs/node/pull/4328)
+    - fixes segfaults in debugger
+  * do not incept debug context (Myles Borins)
+    - [#4819](https://github.com/nodejs/node/pull/4819)
+    - fixes crash in debugger when using util methods
+* **deps**
+  * update to http-parser 2.5.2 (James Snell)
+    - [#5238](https://github.com/nodejs/node/pull/5238)
+
+### Commits
+
+* [[`748d2b4de1`](https://github.com/nodejs/node/commit/748d2b4de1)] - **buffer**: make byteLength work with Buffer correctly (Jackson Tian) [#4738](https://github.com/nodejs/node/pull/4738)
+* [[`fb615bdaf4`](https://github.com/nodejs/node/commit/fb615bdaf4)] - **buffer**: remove unnecessary TODO comments (Peter Geiss) [#4719](https://github.com/nodejs/node/pull/4719)
+* [[`b8213ba7e1`](https://github.com/nodejs/node/commit/b8213ba7e1)] - **cluster**: ignore queryServer msgs on disconnection (Santiago Gimeno) [#4465](https://github.com/nodejs/node/pull/4465)
+* [[`f8a676ed59`](https://github.com/nodejs/node/commit/f8a676ed59)] - **cluster**: fix race condition setting suicide prop (Santiago Gimeno) [#4349](https://github.com/nodejs/node/pull/4349)
+* [[`9d4a226dad`](https://github.com/nodejs/node/commit/9d4a226dad)] - **crypto**: clear error stack in ECDH::Initialize (Fedor Indutny) [#4689](https://github.com/nodejs/node/pull/4689)
+* [[`583f3347d8`](https://github.com/nodejs/node/commit/583f3347d8)] - **debugger**: remove variable redeclarations (Rich Trott) [#4633](https://github.com/nodejs/node/pull/4633)
+* [[`667f7a7ab3`](https://github.com/nodejs/node/commit/667f7a7ab3)] - **debugger**: guard against call from non-node context (Ben Noordhuis) [#4328](https://github.com/nodejs/node/pull/4328)
+* [[`188cff3c31`](https://github.com/nodejs/node/commit/188cff3c31)] - **deps**: update to http-parser 2.5.2 (James Snell) [#5238](https://github.com/nodejs/node/pull/5238)
+* [[`6e829b44e3`](https://github.com/nodejs/node/commit/6e829b44e3)] - **dgram**: prevent disabled optimization of bind() (Brian White) [#4613](https://github.com/nodejs/node/pull/4613)
+* [[`c3956d05b1`](https://github.com/nodejs/node/commit/c3956d05b1)] - **doc**: update list of personal traits in CoC (Kat Marchán) [#4801](https://github.com/nodejs/node/pull/4801)
+* [[`39cb69ca21`](https://github.com/nodejs/node/commit/39cb69ca21)] - **doc**: style fixes for the TOC (Roman Reiss) [#4748](https://github.com/nodejs/node/pull/4748)
+* [[`cb5986da81`](https://github.com/nodejs/node/commit/cb5986da81)] - **doc**: add `servername` parameter docs (Alexander Makarenko) [#4729](https://github.com/nodejs/node/pull/4729)
+* [[`91066b5f34`](https://github.com/nodejs/node/commit/91066b5f34)] - **doc**: update branch-diff arguments in release doc (Rod Vagg) [#4691](https://github.com/nodejs/node/pull/4691)
+* [[`9ca24de41d`](https://github.com/nodejs/node/commit/9ca24de41d)] - **doc**: add docs for more stream options (zoubin) [#4639](https://github.com/nodejs/node/pull/4639)
+* [[`437d0e336d`](https://github.com/nodejs/node/commit/437d0e336d)] - **doc**: mention that http.Server inherits from net.Server (Ryan Sobol) [#4455](https://github.com/nodejs/node/pull/4455)
+* [[`393e569160`](https://github.com/nodejs/node/commit/393e569160)] - **doc**: copyedit setTimeout() documentation (Rich Trott) [#4434](https://github.com/nodejs/node/pull/4434)
+* [[`e2a682ecc3`](https://github.com/nodejs/node/commit/e2a682ecc3)] - **doc**: fix formatting in process.markdown (Rich Trott) [#4433](https://github.com/nodejs/node/pull/4433)
+* [[`75b0ea85bd`](https://github.com/nodejs/node/commit/75b0ea85bd)] - **doc**: add path property to Write/ReadStream in fs.markdown (Claudio Rodriguez) [#4368](https://github.com/nodejs/node/pull/4368)
+* [[`48c2783421`](https://github.com/nodejs/node/commit/48c2783421)] - **doc**: add docs working group (Bryan English) [#4244](https://github.com/nodejs/node/pull/4244)
+* [[`c0432e9f56`](https://github.com/nodejs/node/commit/c0432e9f56)] - **doc**: restore ICU third-party software licenses (Richard Lau) [#4762](https://github.com/nodejs/node/pull/4762)
+* [[`36a4159dab`](https://github.com/nodejs/node/commit/36a4159dab)] - **doc**: rebuild LICENSE using tools/license-builder.sh (Rod Vagg) [#4194](https://github.com/nodejs/node/pull/4194)
+* [[`a2998a1bce`](https://github.com/nodejs/node/commit/a2998a1bce)] - **gitignore**: never ignore debug module (Michaël Zasso) [#2286](https://github.com/nodejs/node/pull/2286)
+* [[`661b2557d9`](https://github.com/nodejs/node/commit/661b2557d9)] - **http**: remove variable redeclaration (Rich Trott) [#4612](https://github.com/nodejs/node/pull/4612)
+* [[`1bb2967d48`](https://github.com/nodejs/node/commit/1bb2967d48)] - **http**: fix non-string header value concatenation (Brian White) [#4460](https://github.com/nodejs/node/pull/4460)
+* [[`15ed64e34c`](https://github.com/nodejs/node/commit/15ed64e34c)] - **lib**: fix style issues after eslint update (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`2e92a1a6b4`](https://github.com/nodejs/node/commit/2e92a1a6b4)] - **module**: move unnecessary work for early return (Andres Suarez) [#3579](https://github.com/nodejs/node/pull/3579)
+* [[`40c8e6d75d`](https://github.com/nodejs/node/commit/40c8e6d75d)] - **net**: remove hot path comment from connect (Evan Lucas) [#4648](https://github.com/nodejs/node/pull/4648)
+* [[`8ed0c1c22c`](https://github.com/nodejs/node/commit/8ed0c1c22c)] - **net**: fix dns lookup for android (Josh Dague) [#4580](https://github.com/nodejs/node/pull/4580)
+* [[`15fa555204`](https://github.com/nodejs/node/commit/15fa555204)] - **net, doc**: fix line wrapping lint in net.js (James M Snell) [#4588](https://github.com/nodejs/node/pull/4588)
+* [[`1b070e48e0`](https://github.com/nodejs/node/commit/1b070e48e0)] - **node_contextify**: do not incept debug context (Myles Borins) [#4815](https://github.com/nodejs/node/issues/4815)
+* [[`4fbcb47fe9`](https://github.com/nodejs/node/commit/4fbcb47fe9)] - **readline**: Remove XXX and output debuglog (Kohei TAKATA) [#4690](https://github.com/nodejs/node/pull/4690)
+* [[`26f02405d0`](https://github.com/nodejs/node/commit/26f02405d0)] - **repl**: make sure historyPath is trimmed (Evan Lucas) [#4539](https://github.com/nodejs/node/pull/4539)
+* [[`5990ba2a0a`](https://github.com/nodejs/node/commit/5990ba2a0a)] - **src**: remove redeclarations of variables (Rich Trott) [#4605](https://github.com/nodejs/node/pull/4605)
+* [[`c41ed59dbc`](https://github.com/nodejs/node/commit/c41ed59dbc)] - **src**: don't check failure with ERR_peek_error() (Ben Noordhuis) [#4731](https://github.com/nodejs/node/pull/4731)
+* [[`d71f9992f9`](https://github.com/nodejs/node/commit/d71f9992f9)] - **stream**: remove useless if test in transform (zoubin) [#4617](https://github.com/nodejs/node/pull/4617)
+* [[`f205e9920e`](https://github.com/nodejs/node/commit/f205e9920e)] - **test**: fix tls-no-rsa-key flakiness (Santiago Gimeno) [#4043](https://github.com/nodejs/node/pull/4043)
+* [[`447347cd62`](https://github.com/nodejs/node/commit/447347cd62)] - **test**: fix issues for space-in-parens ESLint rule (Roman Reiss) [#4753](https://github.com/nodejs/node/pull/4753)
+* [[`be8274508c`](https://github.com/nodejs/node/commit/be8274508c)] - **test**: improve test-cluster-disconnect-suicide-race (Rich Trott) [#4739](https://github.com/nodejs/node/pull/4739)
+* [[`0178001163`](https://github.com/nodejs/node/commit/0178001163)] - **test**: make test-cluster-disconnect-leak reliable (Rich Trott) [#4736](https://github.com/nodejs/node/pull/4736)
+* [[`d615757da2`](https://github.com/nodejs/node/commit/d615757da2)] - **test**: fix flaky test-net-socket-local-address (cjihrig) [#4650](https://github.com/nodejs/node/pull/4650)
+* [[`baa0a3dff5`](https://github.com/nodejs/node/commit/baa0a3dff5)] - **test**: fix race in test-net-server-pause-on-connect (Rich Trott) [#4637](https://github.com/nodejs/node/pull/4637)
+* [[`909b5167cb`](https://github.com/nodejs/node/commit/909b5167cb)] - **test**: remove 1 second delay from test (Rich Trott) [#4616](https://github.com/nodejs/node/pull/4616)
+* [[`8ea76608ed`](https://github.com/nodejs/node/commit/8ea76608ed)] - **test**: move resource intensive tests to sequential (Rich Trott) [#4615](https://github.com/nodejs/node/pull/4615)
+* [[`7afcdd358e`](https://github.com/nodejs/node/commit/7afcdd358e)] - **test**: require common module only once (Rich Trott) [#4611](https://github.com/nodejs/node/pull/4611)
+* [[`0e02eb0bbe`](https://github.com/nodejs/node/commit/0e02eb0bbe)] - **test**: only include http module once (Rich Trott) [#4606](https://github.com/nodejs/node/pull/4606)
+* [[`34d9e48bb6`](https://github.com/nodejs/node/commit/34d9e48bb6)] - **test**: fix `http-upgrade-client` flakiness (Santiago Gimeno) [#4602](https://github.com/nodejs/node/pull/4602)
+* [[`556703d531`](https://github.com/nodejs/node/commit/556703d531)] - **test**: fix flaky unrefed timers test (Rich Trott) [#4599](https://github.com/nodejs/node/pull/4599)
+* [[`3d5bc69796`](https://github.com/nodejs/node/commit/3d5bc69796)] - **test**: fix `http-upgrade-agent` flakiness (Santiago Gimeno) [#4520](https://github.com/nodejs/node/pull/4520)
+* [[`ec24d3767b`](https://github.com/nodejs/node/commit/ec24d3767b)] - **test**: fix flaky test-cluster-shared-leak (Rich Trott) [#4510](https://github.com/nodejs/node/pull/4510)
+* [[`a256790327`](https://github.com/nodejs/node/commit/a256790327)] - **test**: fix flaky cluster-net-send (Brian White) [#4444](https://github.com/nodejs/node/pull/4444)
+* [[`6809c2be1a`](https://github.com/nodejs/node/commit/6809c2be1a)] - **test**: fix flaky child-process-fork-regr-gh-2847 (Brian White) [#4442](https://github.com/nodejs/node/pull/4442)
+* [[`e6448aa36b`](https://github.com/nodejs/node/commit/e6448aa36b)] - **test**: use addon.md block headings as test dir names (Rod Vagg) [#4412](https://github.com/nodejs/node/pull/4412)
+* [[`305d340fca`](https://github.com/nodejs/node/commit/305d340fca)] - **test**: test each block in addon.md contains js & cc (Rod Vagg) [#4411](https://github.com/nodejs/node/pull/4411)
+* [[`f213406575`](https://github.com/nodejs/node/commit/f213406575)] - **test**: fix tls-multi-key race condition (Santiago Gimeno) [#3966](https://github.com/nodejs/node/pull/3966)
+* [[`607f545568`](https://github.com/nodejs/node/commit/607f545568)] - **test**: fix style issues after eslint update (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`aefb20a94f`](https://github.com/nodejs/node/commit/aefb20a94f)] - **tls**: copy client CAs and cert store on CertCb (Fedor Indutny) [#3537](https://github.com/nodejs/node/pull/3537)
+* [[`7821b3e305`](https://github.com/nodejs/node/commit/7821b3e305)] - **tls_legacy**: do not read on OpenSSL's stack (Fedor Indutny) [#4624](https://github.com/nodejs/node/pull/4624)
+* [[`b66db49f94`](https://github.com/nodejs/node/commit/b66db49f94)] - **tools**: add support for subkeys in release tools (Myles Borins) [#4807](https://github.com/nodejs/node/pull/4807)
+* [[`837ebd1985`](https://github.com/nodejs/node/commit/837ebd1985)] - **tools**: enable space-in-parens ESLint rule (Roman Reiss) [#4753](https://github.com/nodejs/node/pull/4753)
+* [[`066d5e7da2`](https://github.com/nodejs/node/commit/066d5e7da2)] - **tools**: fix style issue after eslint update (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`b20ea69f46`](https://github.com/nodejs/node/commit/b20ea69f46)] - **tools**: update eslint config (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`2e0352d50c`](https://github.com/nodejs/node/commit/2e0352d50c)] - **tools**: update eslint to v1.10.3 (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`c96800a432`](https://github.com/nodejs/node/commit/c96800a432)] - **tools**: fix license-builder.sh for ICU (Richard Lau) [#4762](https://github.com/nodejs/node/pull/4762)
+* [[`720b03dca7`](https://github.com/nodejs/node/commit/720b03dca7)] - **tools**: add license-builder.sh to construct LICENSE (Rod Vagg) [#4194](https://github.com/nodejs/node/pull/4194)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.3.1/node-v4.3.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.3.1/node-v4.3.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.3.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.3.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.3.1/node-v4.3.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.3.1/node-v4.3.1-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v4.3.1/node-v4.3.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.3.1/<br>
+Documentation: https://nodejs.org/docs/v4.3.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+9c0751ee88a47c10269eb930d7ad7b103c2ba875c3a96204ca133dc52fc50826  node-v4.3.1-darwin-x64.tar.gz
+264314ea7c696807c47aaa8d9d89425a4f2e7ed47dd1ea282426af56cc8227b0  node-v4.3.1-darwin-x64.tar.xz
+8ba5c1e5eb5509e0f4f00d56e1916ac703fdd05cf353f119451f2b37c51987a5  node-v4.3.1-headers.tar.gz
+951648b678b8ed7e1dbd6ce0800ffc66547b30e24b553b6574880fe2df4ff443  node-v4.3.1-headers.tar.xz
+cd55ce4426f9dd9be878fb89d715cbaf589210162e4269ce2ccfd6b9674385e9  node-v4.3.1-linux-arm64.tar.gz
+54e0fcea69a3111458d82e982574a2e9bd02af44435065a697d0669fbac8a5f2  node-v4.3.1-linux-arm64.tar.xz
+c42383509b7ad8a400da5b5605e2f8663cbe7e214a7c2cfa94964c57b1842ad8  node-v4.3.1-linux-armv6l.tar.gz
+8e0e8e80dcf69b009ff2730e07a672399cabd1de948980df77a20bcb897f3731  node-v4.3.1-linux-armv6l.tar.xz
+8fcf8016b01137d6ccb6d048227af30240a7a01cc40126b0f88f9e99ee40a552  node-v4.3.1-linux-armv7l.tar.gz
+99b82b14f40cab03070a67b57790b9693fffaf7ba97b6c77b2225d767418e5d7  node-v4.3.1-linux-armv7l.tar.xz
+b3af1ed18a9150af42754e9a0385ecc4b4e9b493fcf32bf6ca0d7239d636254b  node-v4.3.1-linux-x64.tar.gz
+1952d92af83b1bd7ffdb4735999f93a91e0d34ba1315ea1210f16f2e411125e4  node-v4.3.1-linux-x64.tar.xz
+b0ac5a9ec4c03b8e119498addd70c3d3ab030abe8d9ca1f120627e6ee2673acc  node-v4.3.1-linux-x86.tar.gz
+ff7c223cc1119a9ba8c32cdc7ef7c1a00b666ecb1e82d35259706e320c8a99bc  node-v4.3.1-linux-x86.tar.xz
+75195a95819aeb8aad75c8ec3b9592eb42ca483d4d2a74d299c942eb25cdf61e  node-v4.3.1.pkg
+f5d51b0d4324e88db468b20ddd3a3790d9dcaf10fe977e328e5d39976028573c  node-v4.3.1-sunos-x64.tar.gz
+7975f71fb5eeb381572408d7eb39e50488d0005daba09c2c0e05cc0fcee52004  node-v4.3.1-sunos-x64.tar.xz
+32d2369d00a50661c0ace7dd4d99105bda36430b27c8be129731bb44ac3064b0  node-v4.3.1-sunos-x86.tar.gz
+298fd5c5a998312d9a4bb96b03fcbedcfe6e3a0fee76f8fa4c5d017f0b90c544  node-v4.3.1-sunos-x86.tar.xz
+61e2d58e861b6c9dbf0ac7624b718198cbd59b88a9de31a39a05de95a32eee73  node-v4.3.1.tar.gz
+9f2fb884655add686a0414800ec2a58279a973520d42f18362f492715625ffa8  node-v4.3.1.tar.xz
+0da4c8de80fc753dafb032003ea1f5835928a8744855a20a0ad6ec9b1e034863  node-v4.3.1-x64.msi
+af0fa21c6a6383a9eb619af7fe8f731ae32559dfefe7813c4a0ad515bfdb3149  node-v4.3.1-x86.msi
+6064b088b0945ead21040f224e12a777f4a7c16328fbc5ce1f1f07d443fbe613  win-x64/node.exe
+739b2a55f75b995b67b97030d389cecc3c439ea23a047b64e4e35db90adc4701  win-x64/node.lib
+31c3a28d556ffe643d755887a5f9aa5263d370352d03f9201882234d1334148f  win-x86/node.exe
+0b821b79a7f43f4897814dd70d853b5ab3e099a4b6833fc2b7ef04b7dc3e9cc2  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJWxK8BAAoJEJM7AfQLXKlGUQEH/j/M/dDYdq8SFo7QX+rMVtXt
+m3bXcl5sYB5jzXvvbJhWAaYmOUnIjwfb0tTH9pPqrMuZ6G/96RsYZJe522NVFGhV
+LMfguS5qmXNrggUnYSZev8Hpu6Ce+6xSFr7VXgP0g27aS/3S5rpBwVf7dzMC51u4
+CSAE7TZGqkEvv5tpSvjfxZuDC5mUnCOTl34e5dBjFsOopOb34VYD6jIMHOp1tlXl
+wBUBqTaEM5cy37Iuq24ToAQBtUDz8RDzFQPn3iRAghXEfKEJRomNM5GxXV9fTmyW
+t8Oy2PPaFCWqYeeJJvJECPOFNJtSTRNsoghgFFfsbupvOV5vAx4fca7+RjawlYk=
+=yrZD
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.3.2.md b/locale/uk/blog/release/v4.3.2.md
new file mode 100755
index 0000000000000..48e4b27cca2d1
--- /dev/null
+++ b/locale/uk/blog/release/v4.3.2.md
@@ -0,0 +1,88 @@
+---
+date: 2016-03-02T21:53:44.939Z
+version: 4.3.2
+category: release
+title: Node v4.3.2 (LTS)
+slug: node-v4-3-2
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+* **openssl**: Upgrade from 1.0.2f to 1.0.2g (Ben Noordhuis) [#5507](https://github.com/nodejs/node/pull/5507)
+  - Fix a double-free defect in parsing malformed DSA keys that may potentially be used for DoS or memory corruption attacks. It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users. More info is available at [CVE-2016-0705](https://www.openssl.org/news/vulnerabilities.html#2016-0705).
+  - Fix a defect that can cause memory corruption in certain very rare cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()` functions. It is believed that Node.js is not invoking the code paths that use these functions so practical attacks via Node.js using this defect are _unlikely_ to be possible. More info is available at [CVE-2016-0797](https://www.openssl.org/news/vulnerabilities.html#2016-0797).
+  - Fix a defect that makes the _[CacheBleed Attack](https://ssrg.nicta.com.au/projects/TS/cachebleed/)_ possible. This defect enables attackers to execute side-channel attacks leading to the potential recovery of entire RSA private keys. It only affects the Intel Sandy Bridge (and possibly older) microarchitecture when using hyper-threading. Newer microarchitectures, including Haswell, are unaffected. More info is available at [CVE-2016-0702](https://www.openssl.org/news/vulnerabilities.html#2016-0702).
+  
+## Commits
+
+* [[`c133797d09`](https://github.com/nodejs/node/commit/c133797d09)] - **deps**: upgrade openssl to 1.0.2g (Ben Noordhuis) [#5507](https://github.com/nodejs/node/pull/5507)
+
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.3.2/node-v4.3.2-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.3.2/node-v4.3.2-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.3.2/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.3.2/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.3.2/node-v4.3.2.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.3.2/node-v4.3.2-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.3.2/node-v4.3.2.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.3.2/<br>
+Documentation: https://nodejs.org/docs/v4.3.2/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+6380a36500de02a48758f204c1c5931af986d93609cfa06db1f91216bec9a5eb  node-v4.3.2-darwin-x64.tar.gz
+47109a00cac344d80296c195451bb5eee7c21727fcef1594384ddfe1f852957a  node-v4.3.2-darwin-x64.tar.xz
+f532e7cd3886ac9fdc774cc2add0db21483052c966a23aace7c84ec69b91981f  node-v4.3.2-headers.tar.gz
+1f7c9a25c224ff3ce2da0cc858d813ba4359c3b6114e125b5c0abfcc6388a130  node-v4.3.2-headers.tar.xz
+5d86c21d47cad54e3e5d7f36c1323b1e2416efc75e4615dafe35b202b59f26c8  node-v4.3.2-linux-arm64.tar.gz
+606e85821fc88f389a20d4ed4e8e483d1e7627e808dada59931b282768041fb7  node-v4.3.2-linux-arm64.tar.xz
+f8767c0bacc0ed516bfa22802dda573082b5bf463e5ea79a74087272ccb2d1e2  node-v4.3.2-linux-armv6l.tar.gz
+3ea0b359efdb58ba693fdd67382ff0c086ee03899cde78c8aa2f29630c4d79fd  node-v4.3.2-linux-armv6l.tar.xz
+f4d5b9ae277aaec50cdbb735480ec1a04e6e02bd820e2a1fcfa913c0c25f2e3d  node-v4.3.2-linux-armv7l.tar.gz
+4e8cae9f7ad94edcc4eb29c9cfcf9e1e1f4cdd5a40156573d77ab352465a74c7  node-v4.3.2-linux-armv7l.tar.xz
+568b13ae13588853cbf49b7a0772698bf50b6de1168f76cd7a7cd7d7d7ada7c7  node-v4.3.2-linux-ppc64le.tar.gz
+a648fab221101408e5a2a740674686816c5ef26c9d3884c1c444fc14c3040b65  node-v4.3.2-linux-ppc64le.tar.xz
+f307f173a96dff6652bc70d835af0c732864bb09875cf32a0b6ce7d70cebf77d  node-v4.3.2-linux-x64.tar.gz
+4350d0431b49697517c6cca5d66adf5f74eb9101c52f52ae959fa94225822d44  node-v4.3.2-linux-x64.tar.xz
+3c668a2128db3982987c596c028f9ec1d08c6abf63502e24826d40e552f80a8c  node-v4.3.2-linux-x86.tar.gz
+ea45ccb7cf334789727dc5a1d1dfb0fa325e88de0b4a06d211dad6cb57c36e33  node-v4.3.2-linux-x86.tar.xz
+f27eda062619f624d198012735cd996bbe7999715dbed1d6e47f3dbc4529b7a6  node-v4.3.2.pkg
+80fdaa0c54b187d43933336b334b70bcbb79953350510006b07dbaa019929188  node-v4.3.2-sunos-x64.tar.gz
+632d45df9172e54feeba5d5400220f946daf2023c282fb2527a3ff0b1e93be8f  node-v4.3.2-sunos-x64.tar.xz
+04705681dde835c383028bc5bab3cab9d14dd7977e062ac824c2cfaf999f7c43  node-v4.3.2-sunos-x86.tar.gz
+1ad766e22773f3ad9ac2274fbf2f277e24d1234957a358e64bea2ea3ce6fe66a  node-v4.3.2-sunos-x86.tar.xz
+1f92f6d31f7292ce56db57d6703efccf3e6c945948f5901610cefa69e78d3498  node-v4.3.2.tar.gz
+f0c5761a7e4f520ab8793cb2dcabbd7dfd7f5839ce4f2cf79d9d52d1c2da5bca  node-v4.3.2.tar.xz
+49abd7e2855b4d124ad87f48162f6c0f0b26048bef17e1ab8f4ec8144d6914f3  node-v4.3.2-x64.msi
+206ef690925231c9a527aeffc5b2c3d77d2497d91f581a21ba9689bfff9556a1  node-v4.3.2-x86.msi
+606c44c42d17866c017c50c0afadad411d9492ac4281d2431b937f881911614e  win-x64/node.exe
+451a40570099a95488d6438f175813629e0430f87f23c8659bc18dc42494820a  win-x64/node.lib
+e41d283a6e3999dcf90742e97dd5d858a6b9d2b767087a4ef0087c0ed82f9bd9  win-x86/node.exe
+1a6f27f9cee7dc117c51eb1a9c2b1ab336020fd46673b87c4bf2719ef4d2d00c  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJW11/yAAoJEJM7AfQLXKlGYDYH/11wCIjqnoJq/mrx++DkwTPH
+/xcS6GPg+M6okP/+12BDxzJ3veMBCXFEe21wKcX68B7vzc9QyfcWR/FDbuu3Jpwl
+nhY0GwA8KqKQwKKl8ecchORWvVCX+b6D6bSSuC1gnO3w0C88usV0MLvdje2WjKdM
+Rg4fy/lzwpNp63yxghwuEwqemxoAt/B/KlJhRqDktcHnsJC4RL8gRr5CXa5E0l81
+ph71mN4nLnES9kYSwb7+XoXsbTXGwRMiWHjjT8s2DP3Tn+WeE1JJzT7JLRRN89KF
+rUnjnEW/76Rb4mk+9W8S30wdBBNEUL0JXAqlEQGANcp5Kdpr1SwwkDoaWSZOprc=
+=hltr
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.0.md b/locale/uk/blog/release/v4.4.0.md
new file mode 100755
index 0000000000000..ea3eda1a2267c
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.0.md
@@ -0,0 +1,329 @@
+---
+date: 2016-03-09T17:04:31.684Z
+version: 4.4.0
+category: release
+title: Node v4.4.0 (LTS)
+slug: node-v4-4-0
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+The SEMVER-MINOR changes include:
+  * **deps**: 
+    - An update to v8 that introduces a new flag --perf_basic_prof_only_functions (Ali Ijaz Sheikh) [#3609](https://github.com/nodejs/node/pull/3609)
+  * **http**:
+    - A new feature in http(s) agent that catches errors on *keep alived* connections (José F. Romaniello) [#4482](https://github.com/nodejs/node/pull/4482)
+  * **src**:
+    - Better support for Big-Endian systems (Bryon Leung) [#3410](https://github.com/nodejs/node/pull/3410)
+  * **tls**:
+    - A new feature that allows you to pass common SSL options to `tls.createSecurePair` (Коренберг Марк) [#2441](https://github.com/nodejs/node/pull/2441)
+  * **tools**:
+    - a new flag `--prof-process` which will execute the tick processor on the provided isolate files (Matt Loring) [#4021](https://github.com/nodejs/node/pull/4021)
+
+Notable semver patch changes include:
+
+  * **build**:
+    - Support python path that includes spaces. This should be of particular interest to our Windows users who may have python living in `c:/Program Files` (Felix Becker) [#4841](https://github.com/nodejs/node/pull/4841)
+  * **https**:
+    - A potential fix for [#3692](https://github.com/nodejs/node/issues/3692) HTTP/HTTPS client requests throwing EPROTO (Fedor Indutny) [#4982](https://github.com/nodejs/node/pull/4982)
+  * **installer**:
+    - More readable profiling information from isolate tick logs (Matt Loring) [#3032](https://github.com/nodejs/node/pull/3032)
+  * **npm**:
+    - upgrade to npm 2.14.20 (Kat Marchán) [#5510](https://github.com/nodejs/node/pull/5510)
+  * **process**:
+    - Add support for symbols in event emitters. Symbols didn't exist when it was written ¯\_(ツ)_/¯ (cjihrig) [#4798](https://github.com/nodejs/node/pull/4798)
+  * **querystring**: 
+    - querystring.parse() is now 13-22% faster! (Brian White) [#4675](https://github.com/nodejs/node/pull/4675)
+  * **streams**:
+    - performance improvements for moving small buffers that shows a 5% throughput gain. IoT projects have been seen to be as much as 10% faster with this change! (Matteo Collina) [#4354](https://github.com/nodejs/node/pull/4354)
+  * **tools**:
+    - eslint has been updated to version 2.1.0 (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+
+### Commits
+
+* [[`360e04fd5a`](https://github.com/nodejs/node/commit/360e04fd5a)] - internal/child_process: call postSend on error (Fedor Indutny) [#4752](https://github.com/nodejs/node/pull/4752)
+* [[`a29f501aa2`](https://github.com/nodejs/node/commit/a29f501aa2)] - **benchmark**: add a constant declaration for `net` (Minwoo Jung) [#3950](https://github.com/nodejs/node/pull/3950)
+* [[`85e06a2e34`](https://github.com/nodejs/node/commit/85e06a2e34)] - **(SEMVER-MINOR)** **buffer**: allow encoding param to collapse (Trevor Norris) [#4803](https://github.com/nodejs/node/pull/4803)
+* [[`fe893a8ebc`](https://github.com/nodejs/node/commit/fe893a8ebc)] - **(SEMVER-MINOR)** **buffer**: properly retrieve binary length of needle (Trevor Norris) [#4803](https://github.com/nodejs/node/pull/4803)
+* [[`fae7c9db3f`](https://github.com/nodejs/node/commit/fae7c9db3f)] - **buffer**: refactor redeclared variables (Rich Trott) [#4886](https://github.com/nodejs/node/pull/4886)
+* [[`4a6e2b26f7`](https://github.com/nodejs/node/commit/4a6e2b26f7)] - **build**: treat aarch64 as arm64 (Johan Bergström) [#5191](https://github.com/nodejs/node/pull/5191)
+* [[`bc2536dfc6`](https://github.com/nodejs/node/commit/bc2536dfc6)] - **build**: add a help message and removed a TODO. (Ojas Shirekar) [#5080](https://github.com/nodejs/node/pull/5080)
+* [[`f6416be5d2`](https://github.com/nodejs/node/commit/f6416be5d2)] - **build**: remove redundant TODO in configure (Ojas Shirekar) [#5080](https://github.com/nodejs/node/pull/5080)
+* [[`6deb7a6eb8`](https://github.com/nodejs/node/commit/6deb7a6eb8)] - **build**: remove Makefile.build (Ojas Shirekar) [#5080](https://github.com/nodejs/node/pull/5080)
+* [[`66d1115555`](https://github.com/nodejs/node/commit/66d1115555)] - **build**: fix build when python path contains spaces (Felix Becker) [#4841](https://github.com/nodejs/node/pull/4841)
+* [[`29951cf36a`](https://github.com/nodejs/node/commit/29951cf36a)] - **child_process**: fix data loss with readable event (Brian White) [#5036](https://github.com/nodejs/node/pull/5036)
+* [[`81d4127279`](https://github.com/nodejs/node/commit/81d4127279)] - **cluster**: dont rely on `this` in `fork` (Igor Klopov) [#5216](https://github.com/nodejs/node/pull/5216)
+* [[`de4c07b29e`](https://github.com/nodejs/node/commit/de4c07b29e)] - **console**: apply null as `this` for util.format (Jackson Tian) [#5222](https://github.com/nodejs/node/pull/5222)
+* [[`4e0755cab3`](https://github.com/nodejs/node/commit/4e0755cab3)] - **crypto**: have fixed NodeBIOs return EOF (Adam Langley) [#5105](https://github.com/nodejs/node/pull/5105)
+* [[`a7955d5071`](https://github.com/nodejs/node/commit/a7955d5071)] - **crypto**: fix memory leak in LoadPKCS12 (Fedor Indutny) [#5109](https://github.com/nodejs/node/pull/5109)
+* [[`5d9c1cf001`](https://github.com/nodejs/node/commit/5d9c1cf001)] - **crypto**: add `pfx` certs as CA certs too (Fedor Indutny) [#5109](https://github.com/nodejs/node/pull/5109)
+* [[`ab5cb0539b`](https://github.com/nodejs/node/commit/ab5cb0539b)] - **crypto**: use SSL_CTX_clear_extra_chain_certs. (Adam Langley) [#4919](https://github.com/nodejs/node/pull/4919)
+* [[`198928eb9f`](https://github.com/nodejs/node/commit/198928eb9f)] - **crypto**: fix build when OCSP-stapling not provided (Adam Langley) [#4914](https://github.com/nodejs/node/pull/4914)
+* [[`b8e1089df0`](https://github.com/nodejs/node/commit/b8e1089df0)] - **crypto**: use a const SSL_CIPHER (Adam Langley) [#4913](https://github.com/nodejs/node/pull/4913)
+* [[`139d6d9284`](https://github.com/nodejs/node/commit/139d6d9284)] - **debugger**: assert test before accessing this.binding (Prince J Wesley) [#5145](https://github.com/nodejs/node/pull/5145)
+* [[`9c8f2ab546`](https://github.com/nodejs/node/commit/9c8f2ab546)] - **deps**: upgrade to npm 2.14.20 (Kat Marchán) [#5510](https://github.com/nodejs/node/pull/5510)
+* [[`e591a0927f`](https://github.com/nodejs/node/commit/e591a0927f)] - **deps**: upgrade to npm 2.14.19 (Kat Marchán) [#5335](https://github.com/nodejs/node/pull/5335)
+* [[`a5ce67a0aa`](https://github.com/nodejs/node/commit/a5ce67a0aa)] - **deps**: upgrade to npm 2.14.18 (Kat Marchán) [#5245](https://github.com/nodejs/node/pull/5245)
+* [[`469db021f7`](https://github.com/nodejs/node/commit/469db021f7)] - **(SEMVER-MINOR)** **deps**: backport 9da3ab6 from V8 upstream (Ali Ijaz Sheikh) [#3609](https://github.com/nodejs/node/pull/3609)
+* [[`3ca04a5de9`](https://github.com/nodejs/node/commit/3ca04a5de9)] - **deps**: backport 8d00c2c from v8 upstream (Gibson Fahnestock) [#5024](https://github.com/nodejs/node/pull/5024)
+* [[`60e0bd4be9`](https://github.com/nodejs/node/commit/60e0bd4be9)] - **deps**: upgrade to npm 2.14.17 (Kat Marchán) [#5110](https://github.com/nodejs/node/pull/5110)
+* [[`976b9a9ab3`](https://github.com/nodejs/node/commit/976b9a9ab3)] - **deps**: upgrade to npm 2.14.16 (Kat Marchán) [#4960](https://github.com/nodejs/node/pull/4960)
+* [[`38b370abea`](https://github.com/nodejs/node/commit/38b370abea)] - **deps**: upgrade to npm 2.14.15 (Kat Marchán) [#4872](https://github.com/nodejs/node/pull/4872)
+* [[`82f549ef81`](https://github.com/nodejs/node/commit/82f549ef81)] - **dgram**: scope redeclared variables (Rich Trott) [#4940](https://github.com/nodejs/node/pull/4940)
+* [[`063e14b568`](https://github.com/nodejs/node/commit/063e14b568)] - **dns**: throw a TypeError in lookupService with invalid port (Evan Lucas) [#4839](https://github.com/nodejs/node/pull/4839)
+* [[`a2613aefae`](https://github.com/nodejs/node/commit/a2613aefae)] - **doc**: remove out-of-date matter from internal docs (Rich Trott) [#5421](https://github.com/nodejs/node/pull/5421)
+* [[`394743f4b3`](https://github.com/nodejs/node/commit/394743f4b3)] - **doc**: explicit about VS 2015 support in readme (Phillip Johnsen) [#5406](https://github.com/nodejs/node/pull/5406)
+* [[`da6b26fbfb`](https://github.com/nodejs/node/commit/da6b26fbfb)] - **doc**: copyedit util doc (Rich Trott) [#5399](https://github.com/nodejs/node/pull/5399)
+* [[`7070ad0cc0`](https://github.com/nodejs/node/commit/7070ad0cc0)] - **doc**: mention prototype check in deepStrictEqual() (cjihrig) [#5367](https://github.com/nodejs/node/pull/5367)
+* [[`d4789fc5fd`](https://github.com/nodejs/node/commit/d4789fc5fd)] - **doc**: s/http/https in Myles Borins' GitHub link (Rod Vagg) [#5356](https://github.com/nodejs/node/pull/5356)
+* [[`b86540d1eb`](https://github.com/nodejs/node/commit/b86540d1eb)] - **doc**: clarify error handling in net.createServer (Dirceu Pereira Tiegs) [#5353](https://github.com/nodejs/node/pull/5353)
+* [[`3106297037`](https://github.com/nodejs/node/commit/3106297037)] - **doc**: `require` behavior on case-insensitive systems (Hugo Wood)
+* [[`e0b45e4315`](https://github.com/nodejs/node/commit/e0b45e4315)] - **doc**: update repo docs to use 'CTC' (Alexis Campailla) [#5304](https://github.com/nodejs/node/pull/5304)
+* [[`e355f13989`](https://github.com/nodejs/node/commit/e355f13989)] - **doc**: improvements to crypto.markdown copy (Alexander Makarenko) [#5230](https://github.com/nodejs/node/pull/5230)
+* [[`a9035b5e1d`](https://github.com/nodejs/node/commit/a9035b5e1d)] - **doc**: link to man pages (dcposch@dcpos.ch) [#5073](https://github.com/nodejs/node/pull/5073)
+* [[`2043e6a63c`](https://github.com/nodejs/node/commit/2043e6a63c)] - **doc**: clarify child_process.execFile{,Sync} file arg (Kevin Locke) [#5310](https://github.com/nodejs/node/pull/5310)
+* [[`8c732ad1e1`](https://github.com/nodejs/node/commit/8c732ad1e1)] - **doc**: fix buf.length slice example (Chinedu Francis Nwafili) [#5259](https://github.com/nodejs/node/pull/5259)
+* [[`6c27c78b8b`](https://github.com/nodejs/node/commit/6c27c78b8b)] - **doc**: fix buffer\[index\] example (Chinedu Francis Nwafili) [#5253](https://github.com/nodejs/node/pull/5253)
+* [[`7765f99683`](https://github.com/nodejs/node/commit/7765f99683)] - **doc**: fix template string (Rafael Cepeda) [#5240](https://github.com/nodejs/node/pull/5240)
+* [[`d15ef20162`](https://github.com/nodejs/node/commit/d15ef20162)] - **doc**: improvements to console.markdown copy (Alexander Makarenko) [#5225](https://github.com/nodejs/node/pull/5225)
+* [[`593206a752`](https://github.com/nodejs/node/commit/593206a752)] - **doc**: fix net.createConnection() example (Brian White) [#5219](https://github.com/nodejs/node/pull/5219)
+* [[`464636b5c5`](https://github.com/nodejs/node/commit/464636b5c5)] - **doc**: improve scrolling, various CSS tweaks (Roman Reiss) [#5198](https://github.com/nodejs/node/pull/5198)
+* [[`f615cd5b0b`](https://github.com/nodejs/node/commit/f615cd5b0b)] - **doc**: console is asynchronous unless it's a file (Ben Noordhuis) [#5133](https://github.com/nodejs/node/pull/5133)
+* [[`fbed0d11f1`](https://github.com/nodejs/node/commit/fbed0d11f1)] - **doc**: merging behavior of writeHead vs setHeader (Alejandro Oviedo) [#5081](https://github.com/nodejs/node/pull/5081)
+* [[`b0bb42bd7d`](https://github.com/nodejs/node/commit/b0bb42bd7d)] - **doc**: fix reference to API `hash.final` (Minwoo Jung) [#5050](https://github.com/nodejs/node/pull/5050)
+* [[`dee5045221`](https://github.com/nodejs/node/commit/dee5045221)] - **doc**: uppercase 'RSA-SHA256' in crypto.markdown (Rainer Oviir) [#5044](https://github.com/nodejs/node/pull/5044)
+* [[`498052a017`](https://github.com/nodejs/node/commit/498052a017)] - **doc**: consistent styling for functions in TLS docs (Alexander Makarenko) [#5000](https://github.com/nodejs/node/pull/5000)
+* [[`031277e6f8`](https://github.com/nodejs/node/commit/031277e6f8)] - **doc**: apply consistent styling for functions (Rich Trott) [#4974](https://github.com/nodejs/node/pull/4974)
+* [[`808fe0ea48`](https://github.com/nodejs/node/commit/808fe0ea48)] - **doc**: fix `notDeepEqual` API (Minwoo Jung) [#4971](https://github.com/nodejs/node/pull/4971)
+* [[`5b9025689f`](https://github.com/nodejs/node/commit/5b9025689f)] - **doc**: show links consistently in deprecations (Sakthipriyan Vairamani) [#4907](https://github.com/nodejs/node/pull/4907)
+* [[`3a1865db5e`](https://github.com/nodejs/node/commit/3a1865db5e)] - **doc**: don't use "interface" as a variable name (ChALkeR) [#4900](https://github.com/nodejs/node/pull/4900)
+* [[`90715c3d68`](https://github.com/nodejs/node/commit/90715c3d68)] - **doc**: keep the names in sorted order (Sakthipriyan Vairamani) [#4876](https://github.com/nodejs/node/pull/4876)
+* [[`d8b3b25c9c`](https://github.com/nodejs/node/commit/d8b3b25c9c)] - **doc**: fix JSON generation for aliased methods (Timothy Gu) [#4871](https://github.com/nodejs/node/pull/4871)
+* [[`7b763c8d25`](https://github.com/nodejs/node/commit/7b763c8d25)] - **doc**: fix code type of markdowns (Jackson Tian) [#4858](https://github.com/nodejs/node/pull/4858)
+* [[`37d4e7afc2`](https://github.com/nodejs/node/commit/37d4e7afc2)] - **doc**: check for errors in 'listen' event (Benjamin Gruenbaum) [#4834](https://github.com/nodejs/node/pull/4834)
+* [[`3f876b104c`](https://github.com/nodejs/node/commit/3f876b104c)] - **doc**: Examples work when data exceeds buffer size (Glen Arrowsmith) [#4811](https://github.com/nodejs/node/pull/4811)
+* [[`e3e20422a7`](https://github.com/nodejs/node/commit/e3e20422a7)] - **doc**: harmonize $ node command line notation (Robert Jefe Lindstaedt) [#4806](https://github.com/nodejs/node/pull/4806)
+* [[`73e0195cef`](https://github.com/nodejs/node/commit/73e0195cef)] - **doc**: fix type references for link gen, link css (Claudio Rodriguez) [#4741](https://github.com/nodejs/node/pull/4741)
+* [[`0bdac429e1`](https://github.com/nodejs/node/commit/0bdac429e1)] - **doc**: multiple improvements in Stream docs (Alexander Makarenko) [#5009](https://github.com/nodejs/node/pull/5009)
+* [[`693c16fb6b`](https://github.com/nodejs/node/commit/693c16fb6b)] - **doc**: fix anchor links from stream to http and events (piepmatz) [#5007](https://github.com/nodejs/node/pull/5007)
+* [[`5fb533522c`](https://github.com/nodejs/node/commit/5fb533522c)] - **doc**: replace function expressions with arrows (Benjamin Gruenbaum) [#4832](https://github.com/nodejs/node/pull/4832)
+* [[`e3572fb809`](https://github.com/nodejs/node/commit/e3572fb809)] - **doc**: fix links order in Buffer doc (Alexander Makarenko) [#5076](https://github.com/nodejs/node/pull/5076)
+* [[`5c936ab765`](https://github.com/nodejs/node/commit/5c936ab765)] - **doc**: clarify optional arguments of Buffer methods (Michaël Zasso) [#5008](https://github.com/nodejs/node/pull/5008)
+* [[`6df350c2b3`](https://github.com/nodejs/node/commit/6df350c2b3)] - **doc**: improve styling consistency in Buffer docs (Alexander Makarenko) [#5001](https://github.com/nodejs/node/pull/5001)
+* [[`047f4a157f`](https://github.com/nodejs/node/commit/047f4a157f)] - **doc**: make buffer methods styles consistent (Timothy Gu) [#4873](https://github.com/nodejs/node/pull/4873)
+* [[`4cfc017b90`](https://github.com/nodejs/node/commit/4cfc017b90)] - **doc**: fix nonsensical grammar in Buffer::write (Jimb Esser) [#4863](https://github.com/nodejs/node/pull/4863)
+* [[`9087f6daca`](https://github.com/nodejs/node/commit/9087f6daca)] - **doc**: fix named anchors in addons.markdown and http.markdown (Michael Theriot) [#4708](https://github.com/nodejs/node/pull/4708)
+* [[`4c8713ce58`](https://github.com/nodejs/node/commit/4c8713ce58)] - **doc**: add buf.indexOf encoding param with example (Karl Skomski) [#3373](https://github.com/nodejs/node/pull/3373)
+* [[`1819d74491`](https://github.com/nodejs/node/commit/1819d74491)] - **doc**: fenced all code blocks, typo fixes (Robert Jefe Lindstaedt) [#4733](https://github.com/nodejs/node/pull/4733)
+* [[`961735e645`](https://github.com/nodejs/node/commit/961735e645)] - **doc**: make references clickable (Roman Klauke) [#4654](https://github.com/nodejs/node/pull/4654)
+* [[`7e80442483`](https://github.com/nodejs/node/commit/7e80442483)] - **doc**: improve child_process.execFile() code example (Ryan Sobol) [#4504](https://github.com/nodejs/node/pull/4504)
+* [[`de9ad5b39d`](https://github.com/nodejs/node/commit/de9ad5b39d)] - **doc**: remove "above" and "below" references (Richard Sun) [#4499](https://github.com/nodejs/node/pull/4499)
+* [[`c549ca3b69`](https://github.com/nodejs/node/commit/c549ca3b69)] - **doc**: fix heading level error in Buffer doc (Shigeki Ohtsu) [#4537](https://github.com/nodejs/node/pull/4537)
+* [[`a613bae14c`](https://github.com/nodejs/node/commit/a613bae14c)] - **doc**: improvements to crypto.markdown copy (James M Snell) [#4435](https://github.com/nodejs/node/pull/4435)
+* [[`18f580d0c1`](https://github.com/nodejs/node/commit/18f580d0c1)] - **doc**: improve child_process.markdown copy (James M Snell) [#4383](https://github.com/nodejs/node/pull/4383)
+* [[`a929837311`](https://github.com/nodejs/node/commit/a929837311)] - **doc**: improvements to buffer.markdown copy (James M Snell) [#4370](https://github.com/nodejs/node/pull/4370)
+* [[`a22f688407`](https://github.com/nodejs/node/commit/a22f688407)] - **doc**: improve addons.markdown copy (James M Snell) [#4320](https://github.com/nodejs/node/pull/4320)
+* [[`94c2de47b1`](https://github.com/nodejs/node/commit/94c2de47b1)] - **doc**: update process.send() signature (cjihrig) [#5284](https://github.com/nodejs/node/pull/5284)
+* [[`4e1926cb08`](https://github.com/nodejs/node/commit/4e1926cb08)] - **doc**: replace node-forward link in CONTRIBUTING.md (Ben Noordhuis) [#5227](https://github.com/nodejs/node/pull/5227)
+* [[`e1713e81e5`](https://github.com/nodejs/node/commit/e1713e81e5)] - **doc**: fix minor inconsistencies in repl doc (Rich Trott) [#5193](https://github.com/nodejs/node/pull/5193)
+* [[`b2e72c0d92`](https://github.com/nodejs/node/commit/b2e72c0d92)] - **doc**: clarify exceptions during uncaughtException (Noah Rose) [#5180](https://github.com/nodejs/node/pull/5180)
+* [[`c3c549836a`](https://github.com/nodejs/node/commit/c3c549836a)] - **doc**: update DCO to v1.1 (Mikeal Rogers) [#5170](https://github.com/nodejs/node/pull/5170)
+* [[`9dd35ad594`](https://github.com/nodejs/node/commit/9dd35ad594)] - **doc**: fix dgram doc indentation (Rich Trott) [#5118](https://github.com/nodejs/node/pull/5118)
+* [[`eed830702c`](https://github.com/nodejs/node/commit/eed830702c)] - **doc**: fix typo in dgram doc (Rich Trott) [#5114](https://github.com/nodejs/node/pull/5114)
+* [[`abfb2f5864`](https://github.com/nodejs/node/commit/abfb2f5864)] - **doc**: fix link in cluster documentation (Timothy Gu) [#5068](https://github.com/nodejs/node/pull/5068)
+* [[`8b040b5bb2`](https://github.com/nodejs/node/commit/8b040b5bb2)] - **doc**: fix minor typo in process doc (Prayag Verma) [#5018](https://github.com/nodejs/node/pull/5018)
+* [[`47eebe1d80`](https://github.com/nodejs/node/commit/47eebe1d80)] - **doc**: fix typo in Readme.md (Prayag Verma) [#5017](https://github.com/nodejs/node/pull/5017)
+* [[`2b97ff89a6`](https://github.com/nodejs/node/commit/2b97ff89a6)] - **doc**: minor improvement in OS docs (Alexander Makarenko) [#5006](https://github.com/nodejs/node/pull/5006)
+* [[`9a5d58b89e`](https://github.com/nodejs/node/commit/9a5d58b89e)] - **doc**: improve styling consistency in VM docs (Alexander Makarenko) [#5005](https://github.com/nodejs/node/pull/5005)
+* [[`960e1bab98`](https://github.com/nodejs/node/commit/960e1bab98)] - **doc**: minor improvement to HTTPS doc (Alexander Makarenko) [#5002](https://github.com/nodejs/node/pull/5002)
+* [[`6048b011e8`](https://github.com/nodejs/node/commit/6048b011e8)] - **doc**: spell writable consistently (Peter Lyons) [#4954](https://github.com/nodejs/node/pull/4954)
+* [[`7b8f904167`](https://github.com/nodejs/node/commit/7b8f904167)] - **doc**: update eol handling in readline (Kári Tristan Helgason) [#4927](https://github.com/nodejs/node/pull/4927)
+* [[`83efd0d4d1`](https://github.com/nodejs/node/commit/83efd0d4d1)] - **doc**: add more details to process.env (Evan Lucas) [#4924](https://github.com/nodejs/node/pull/4924)
+* [[`b2d2c0b588`](https://github.com/nodejs/node/commit/b2d2c0b588)] - **doc**: undo move http.IncomingMessage.statusMessage (Jeff Harris) [#4822](https://github.com/nodejs/node/pull/4822)
+* [[`b091c41b53`](https://github.com/nodejs/node/commit/b091c41b53)] - **doc**: proper markdown escaping -> \_\_, \*, \_ (Robert Jefe Lindstaedt) [#4805](https://github.com/nodejs/node/pull/4805)
+* [[`0887208290`](https://github.com/nodejs/node/commit/0887208290)] - **doc**: remove unnecessary bind(this) (Dmitriy Lazarev) [#4797](https://github.com/nodejs/node/pull/4797)
+* [[`f3e3c70bca`](https://github.com/nodejs/node/commit/f3e3c70bca)] - **doc**: Update small error in LICENSE for npm (Kat Marchán) [#4872](https://github.com/nodejs/node/pull/4872)
+* [[`e703b180b3`](https://github.com/nodejs/node/commit/e703b180b3)] - **doc,tools,test**: lint doc-based addon tests (Rich Trott) [#5427](https://github.com/nodejs/node/pull/5427)
+* [[`0f3b8ca192`](https://github.com/nodejs/node/commit/0f3b8ca192)] - **fs**: refactor redeclared variables (Rich Trott) [#4959](https://github.com/nodejs/node/pull/4959)
+* [[`152c6b6b8d`](https://github.com/nodejs/node/commit/152c6b6b8d)] - **http**: remove reference to onParserExecute (Tom Atkinson) [#4773](https://github.com/nodejs/node/pull/4773)
+* [[`6a0571cd72`](https://github.com/nodejs/node/commit/6a0571cd72)] - **http**: do not emit `upgrade` on advertisement (Fedor Indutny) [#4337](https://github.com/nodejs/node/pull/4337)
+* [[`567ced9ef0`](https://github.com/nodejs/node/commit/567ced9ef0)] - **(SEMVER-MINOR)** **http**: handle errors on idle sockets (José F. Romaniello) [#4482](https://github.com/nodejs/node/pull/4482)
+* [[`de5177ccb8`](https://github.com/nodejs/node/commit/de5177ccb8)] - **https**: evict cached sessions on error (Fedor Indutny) [#4982](https://github.com/nodejs/node/pull/4982)
+* [[`77a6036264`](https://github.com/nodejs/node/commit/77a6036264)] - **installer**: install the tick processor (Matt Loring) [#3032](https://github.com/nodejs/node/pull/3032)
+* [[`ea16d8d7c5`](https://github.com/nodejs/node/commit/ea16d8d7c5)] - **lib**: remove string_decoder.js var redeclarations (Rich Trott) [#4978](https://github.com/nodejs/node/pull/4978)
+* [[`1389660ab3`](https://github.com/nodejs/node/commit/1389660ab3)] - **lib**: scope loop variables (Rich Trott) [#4965](https://github.com/nodejs/node/pull/4965)
+* [[`59255d7218`](https://github.com/nodejs/node/commit/59255d7218)] - **lib**: use arrow functions instead of bind (Minwoo Jung) [#3622](https://github.com/nodejs/node/pull/3622)
+* [[`fd26960aab`](https://github.com/nodejs/node/commit/fd26960aab)] - **lib,test**: remove extra semicolons (Michaël Zasso) [#2205](https://github.com/nodejs/node/pull/2205)
+* [[`9646d26ffd`](https://github.com/nodejs/node/commit/9646d26ffd)] - **module**: refactor redeclared variable (Rich Trott) [#4962](https://github.com/nodejs/node/pull/4962)
+* [[`09311128e8`](https://github.com/nodejs/node/commit/09311128e8)] - **net**: use `_server` for internal book-keeping (Fedor Indutny) [#5262](https://github.com/nodejs/node/pull/5262)
+* [[`824c402174`](https://github.com/nodejs/node/commit/824c402174)] - **net**: refactor redeclared variables (Rich Trott) [#4963](https://github.com/nodejs/node/pull/4963)
+* [[`96f306f3cf`](https://github.com/nodejs/node/commit/96f306f3cf)] - **net**: move isLegalPort to internal/net (Evan Lucas) [#4882](https://github.com/nodejs/node/pull/4882)
+* [[`78d64889bd`](https://github.com/nodejs/node/commit/78d64889bd)] - **node**: set process._eventsCount to 0 on startup (Evan Lucas) [#5208](https://github.com/nodejs/node/pull/5208)
+* [[`7a2e8f4356`](https://github.com/nodejs/node/commit/7a2e8f4356)] - **process**: support symbol events (cjihrig) [#4798](https://github.com/nodejs/node/pull/4798)
+* [[`c9e2dce247`](https://github.com/nodejs/node/commit/c9e2dce247)] - **querystring**: improve parse() performance (Brian White) [#4675](https://github.com/nodejs/node/pull/4675)
+* [[`18542c41fe`](https://github.com/nodejs/node/commit/18542c41fe)] - **repl**: remove variable redeclaration (Rich Trott) [#4977](https://github.com/nodejs/node/pull/4977)
+* [[`10be8dc360`](https://github.com/nodejs/node/commit/10be8dc360)] - **src**: force line buffering for stderr (Rich Trott) [#3701](https://github.com/nodejs/node/pull/3701)
+* [[`7958664e85`](https://github.com/nodejs/node/commit/7958664e85)] - **src**: clean up usage of __proto__ (Jackson Tian) [#5069](https://github.com/nodejs/node/pull/5069)
+* [[`4e0a0d51b3`](https://github.com/nodejs/node/commit/4e0a0d51b3)] - **src**: remove no longer relevant comments (Chris911) [#4843](https://github.com/nodejs/node/pull/4843)
+* [[`51c8bc8abc`](https://github.com/nodejs/node/commit/51c8bc8abc)] - **src**: remove __builtin_bswap16 call (Ben Noordhuis) [#4290](https://github.com/nodejs/node/pull/4290)
+* [[`5e1976e37c`](https://github.com/nodejs/node/commit/5e1976e37c)] - **src**: remove unused BITS_PER_LONG macro (Ben Noordhuis) [#4290](https://github.com/nodejs/node/pull/4290)
+* [[`c18ef54d88`](https://github.com/nodejs/node/commit/c18ef54d88)] - **(SEMVER-MINOR)** **src**: add BE support to StringBytes::Encode() (Bryon Leung) [#3410](https://github.com/nodejs/node/pull/3410)
+* [[`be9e7610b5`](https://github.com/nodejs/node/commit/be9e7610b5)] - **src,test,tools**: modify for more stringent linting (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`538c4756a7`](https://github.com/nodejs/node/commit/538c4756a7)] - **stream**: refactor redeclared variables (Rich Trott) [#4816](https://github.com/nodejs/node/pull/4816)
+* [[`4fa22e4126`](https://github.com/nodejs/node/commit/4fa22e4126)] - **streams**: 5% throughput gain when sending small chunks (Matteo Collina) [#4354](https://github.com/nodejs/node/pull/4354)
+* [[`b6bd87495f`](https://github.com/nodejs/node/commit/b6bd87495f)] - **test**: remove flaky mark for test-debug-no-context (Rich Trott) [#5317](https://github.com/nodejs/node/pull/5317)
+* [[`7705360e35`](https://github.com/nodejs/node/commit/7705360e35)] - **test**: add test for https server close event (Braydon Fuller) [#5106](https://github.com/nodejs/node/pull/5106)
+* [[`9d6623e1d1`](https://github.com/nodejs/node/commit/9d6623e1d1)] - **test**: use String.prototype.repeat() for clarity (Rich Trott) [#5311](https://github.com/nodejs/node/pull/5311)
+* [[`18e3987e2e`](https://github.com/nodejs/node/commit/18e3987e2e)] - **test**: mitigate flaky test-debug-no-context (Rich Trott) [#5269](https://github.com/nodejs/node/pull/5269)
+* [[`058db07ce8`](https://github.com/nodejs/node/commit/058db07ce8)] - **test**: refactor test-dgram-send-callback-recursive (Santiago Gimeno) [#5079](https://github.com/nodejs/node/pull/5079)
+* [[`1647113d7a`](https://github.com/nodejs/node/commit/1647113d7a)] - **test**: refactor test-http-destroyed-socket-write2 (Santiago Gimeno) [#4970](https://github.com/nodejs/node/pull/4970)
+* [[`07dc2b50e2`](https://github.com/nodejs/node/commit/07dc2b50e2)] - **test**: shorten path for bogus socket (Rich Trott) [#4478](https://github.com/nodejs/node/pull/4478)
+* [[`47e7c8c359`](https://github.com/nodejs/node/commit/47e7c8c359)] - **test**: mark test-http-regr-gh-2928 flaky (Rich Trott) [#5280](https://github.com/nodejs/node/pull/5280)
+* [[`9dbd66f7ef`](https://github.com/nodejs/node/commit/9dbd66f7ef)] - **test**: mark test-http-agent flaky (Rich Trott) [#5209](https://github.com/nodejs/node/pull/5209)
+* [[`98049876b5`](https://github.com/nodejs/node/commit/98049876b5)] - **test**: minimal repl eval option test (Rich Trott) [#5192](https://github.com/nodejs/node/pull/5192)
+* [[`ae3185b8ac`](https://github.com/nodejs/node/commit/ae3185b8ac)] - **test**: disable fs watch tests for AIX (Michael Dawson) [#5187](https://github.com/nodejs/node/pull/5187)
+* [[`b639c3345b`](https://github.com/nodejs/node/commit/b639c3345b)] - **test**: fix child-process-fork-regr-gh-2847 again (Santiago Gimeno) [#5179](https://github.com/nodejs/node/pull/5179)
+* [[`8be3afc474`](https://github.com/nodejs/node/commit/8be3afc474)] - **test**: fix flaky test-http-regr-gh-2928 (Rich Trott) [#5154](https://github.com/nodejs/node/pull/5154)
+* [[`46dc12bdcc`](https://github.com/nodejs/node/commit/46dc12bdcc)] - **test**: enable to work pkcs12 test in FIPS mode (Shigeki Ohtsu) [#5150](https://github.com/nodejs/node/pull/5150)
+* [[`e19b8ea692`](https://github.com/nodejs/node/commit/e19b8ea692)] - **test**: remove unneeded common.indirectInstanceOf() (Rich Trott) [#5149](https://github.com/nodejs/node/pull/5149)
+* [[`6072d2e15e`](https://github.com/nodejs/node/commit/6072d2e15e)] - **test**: disable gh-5100 test when in FIPS mode (Fedor Indutny) [#5144](https://github.com/nodejs/node/pull/5144)
+* [[`a8417a2787`](https://github.com/nodejs/node/commit/a8417a2787)] - **test**: fix flaky test-dgram-pingpong (Rich Trott) [#5125](https://github.com/nodejs/node/pull/5125)
+* [[`9db67a6a44`](https://github.com/nodejs/node/commit/9db67a6a44)] - **test**: fix child-process-fork-regr-gh-2847 (Santiago Gimeno) [#5121](https://github.com/nodejs/node/pull/5121)
+* [[`69150caedc`](https://github.com/nodejs/node/commit/69150caedc)] - **test**: don't run test-tick-processor.js on Aix (Michael Dawson) [#5093](https://github.com/nodejs/node/pull/5093)
+* [[`4a492b96b1`](https://github.com/nodejs/node/commit/4a492b96b1)] - **test**: mark flaky tests on Raspberry Pi (Rich Trott) [#5082](https://github.com/nodejs/node/pull/5082)
+* [[`4301f2cdc2`](https://github.com/nodejs/node/commit/4301f2cdc2)] - **test**: fix inconsistent styling in test-url (Brian White) [#5014](https://github.com/nodejs/node/pull/5014)
+* [[`865baaed60`](https://github.com/nodejs/node/commit/865baaed60)] - **test**: fix redeclared vars in sequential tests (Rich Trott) [#4999](https://github.com/nodejs/node/pull/4999)
+* [[`663e852c1b`](https://github.com/nodejs/node/commit/663e852c1b)] - **test**: pummel test fixes (Rich Trott) [#4998](https://github.com/nodejs/node/pull/4998)
+* [[`72d38a4a38`](https://github.com/nodejs/node/commit/72d38a4a38)] - **test**: fix redeclared vars in test-vm-* (Rich Trott) [#4997](https://github.com/nodejs/node/pull/4997)
+* [[`97ddfa2b6e`](https://github.com/nodejs/node/commit/97ddfa2b6e)] - **test**: fix redeclared vars in test-url (Rich Trott) [#4993](https://github.com/nodejs/node/pull/4993)
+* [[`43d4db4314`](https://github.com/nodejs/node/commit/43d4db4314)] - **test**: fix redeclared test-util-* vars (Rich Trott) [#4994](https://github.com/nodejs/node/pull/4994)
+* [[`88fae38d0c`](https://github.com/nodejs/node/commit/88fae38d0c)] - **test**: fix variable redeclarations (Rich Trott) [#4992](https://github.com/nodejs/node/pull/4992)
+* [[`58595f146a`](https://github.com/nodejs/node/commit/58595f146a)] - **test**: fix redeclared test-path vars (Rich Trott) [#4991](https://github.com/nodejs/node/pull/4991)
+* [[`2b711d51fa`](https://github.com/nodejs/node/commit/2b711d51fa)] - **test**: fix var redeclarations in test-os (Rich Trott) [#4990](https://github.com/nodejs/node/pull/4990)
+* [[`bd9e2c31d6`](https://github.com/nodejs/node/commit/bd9e2c31d6)] - **test**: fix test-net-* variable redeclarations (Rich Trott) [#4989](https://github.com/nodejs/node/pull/4989)
+* [[`d67ab81882`](https://github.com/nodejs/node/commit/d67ab81882)] - **test**: fix redeclared test-intl var (Rich Trott) [#4988](https://github.com/nodejs/node/pull/4988)
+* [[`d6dbb2fae7`](https://github.com/nodejs/node/commit/d6dbb2fae7)] - **test**: fix redeclared test-http-* vars (Rich Trott) [#4987](https://github.com/nodejs/node/pull/4987)
+* [[`ecaa89a8cb`](https://github.com/nodejs/node/commit/ecaa89a8cb)] - **test**: fix redeclared test-event-emitter-* vars (Rich Trott) [#4985](https://github.com/nodejs/node/pull/4985)
+* [[`299c729371`](https://github.com/nodejs/node/commit/299c729371)] - **test**: remove redeclared var in test-domain (Rich Trott) [#4984](https://github.com/nodejs/node/pull/4984)
+* [[`35a4a203bf`](https://github.com/nodejs/node/commit/35a4a203bf)] - **test**: remove var redeclarations in test-crypto-* (Rich Trott) [#4981](https://github.com/nodejs/node/pull/4981)
+* [[`1d56b74af0`](https://github.com/nodejs/node/commit/1d56b74af0)] - **test**: remove test-cluster-* var redeclarations (Rich Trott) [#4980](https://github.com/nodejs/node/pull/4980)
+* [[`0ce12cc1ec`](https://github.com/nodejs/node/commit/0ce12cc1ec)] - **test**: fix test-http-extra-response flakiness (Santiago Gimeno) [#4979](https://github.com/nodejs/node/pull/4979)
+* [[`c6b4bf138c`](https://github.com/nodejs/node/commit/c6b4bf138c)] - **test**: scope redeclared vars in test-child-process* (Rich Trott) [#4944](https://github.com/nodejs/node/pull/4944)
+* [[`7654c171c7`](https://github.com/nodejs/node/commit/7654c171c7)] - **test**: refactor switch (Rich Trott) [#4870](https://github.com/nodejs/node/pull/4870)
+* [[`226dfef690`](https://github.com/nodejs/node/commit/226dfef690)] - **test**: add common.platformTimeout() to dgram test (Rich Trott) [#4938](https://github.com/nodejs/node/pull/4938)
+* [[`fb14bac662`](https://github.com/nodejs/node/commit/fb14bac662)] - **test**: fix flaky cluster test on Windows 10 (Rich Trott) [#4934](https://github.com/nodejs/node/pull/4934)
+* [[`f5d29d7ac4`](https://github.com/nodejs/node/commit/f5d29d7ac4)] - **test**: Add assertion for TLS peer certificate fingerprint (Alan Cohen) [#4923](https://github.com/nodejs/node/pull/4923)
+* [[`618427cea6`](https://github.com/nodejs/node/commit/618427cea6)] - **test**: fix test-tls-zero-clear-in flakiness (Santiago Gimeno) [#4888](https://github.com/nodejs/node/pull/4888)
+* [[`8700c39c70`](https://github.com/nodejs/node/commit/8700c39c70)] - **test**: fix irregular whitespace issue (Roman Reiss) [#4864](https://github.com/nodejs/node/pull/4864)
+* [[`2b026c9d5a`](https://github.com/nodejs/node/commit/2b026c9d5a)] - **test**: fs.link() test runs on same device (Drew Folta) [#4861](https://github.com/nodejs/node/pull/4861)
+* [[`80a637ac4d`](https://github.com/nodejs/node/commit/80a637ac4d)] - **test**: scope redeclared variable (Rich Trott) [#4854](https://github.com/nodejs/node/pull/4854)
+* [[`8c4903d4ef`](https://github.com/nodejs/node/commit/8c4903d4ef)] - **test**: update arrow function style (cjihrig) [#4813](https://github.com/nodejs/node/pull/4813)
+* [[`0a44e6a447`](https://github.com/nodejs/node/commit/0a44e6a447)] - **test**: mark test-tick-processor flaky (Rich Trott) [#4809](https://github.com/nodejs/node/pull/4809)
+* [[`363460616c`](https://github.com/nodejs/node/commit/363460616c)] - **test**: refactor test-net-settimeout (Rich Trott) [#4799](https://github.com/nodejs/node/pull/4799)
+* [[`6841d82c22`](https://github.com/nodejs/node/commit/6841d82c22)] - **test**: remove race condition in http flood test (Rich Trott) [#4793](https://github.com/nodejs/node/pull/4793)
+* [[`b5bae32847`](https://github.com/nodejs/node/commit/b5bae32847)] - **test**: remove test-http-exit-delay (Rich Trott) [#4786](https://github.com/nodejs/node/pull/4786)
+* [[`60514f9521`](https://github.com/nodejs/node/commit/60514f9521)] - **test**: refactor test-fs-watch (Rich Trott) [#4776](https://github.com/nodejs/node/pull/4776)
+* [[`2a3a431119`](https://github.com/nodejs/node/commit/2a3a431119)] - **test**: fix `net-socket-timeout-unref` flakiness (Santiago Gimeno) [#4772](https://github.com/nodejs/node/pull/4772)
+* [[`9e6f3632a1`](https://github.com/nodejs/node/commit/9e6f3632a1)] - **test**: remove Object.observe from tests (Vladimir Kurchatkin) [#4769](https://github.com/nodejs/node/pull/4769)
+* [[`f78daa67b8`](https://github.com/nodejs/node/commit/f78daa67b8)] - **test**: make npm tests work on prerelease node versions (Kat Marchán) [#4960](https://github.com/nodejs/node/pull/4960)
+* [[`1c03191b6a`](https://github.com/nodejs/node/commit/1c03191b6a)] - **test**: make npm tests work on prerelease node versions (Kat Marchán) [#4872](https://github.com/nodejs/node/pull/4872)
+* [[`d9c22cc896`](https://github.com/nodejs/node/commit/d9c22cc896)] - **test,buffer**: refactor redeclarations (Rich Trott) [#4893](https://github.com/nodejs/node/pull/4893)
+* [[`5c4960468a`](https://github.com/nodejs/node/commit/5c4960468a)] - **tls**: nullify `.ssl` on handle close (Fedor Indutny) [#5168](https://github.com/nodejs/node/pull/5168)
+* [[`c0f5f01c9c`](https://github.com/nodejs/node/commit/c0f5f01c9c)] - **tls**: scope loop vars with let (Rich Trott) [#4853](https://github.com/nodejs/node/pull/4853)
+* [[`c86627e0d1`](https://github.com/nodejs/node/commit/c86627e0d1)] - **(SEMVER-MINOR)** **tls**: add `options` argument to createSecurePair (Коренберг Марк) [#2441](https://github.com/nodejs/node/pull/2441)
+* [[`c908ff36f4`](https://github.com/nodejs/node/commit/c908ff36f4)] - **tls_wrap**: reach error reporting for UV_EPROTO (Fedor Indutny) [#4885](https://github.com/nodejs/node/pull/4885)
+* [[`cebe3b95e3`](https://github.com/nodejs/node/commit/cebe3b95e3)] - **tools**: run tick processor without forking (Matt Loring) [#4224](https://github.com/nodejs/node/pull/4224)
+* [[`70d8827714`](https://github.com/nodejs/node/commit/70d8827714)] - **(SEMVER-MINOR)** **tools**: add --prof-process flag to node binary (Matt Loring) [#4021](https://github.com/nodejs/node/pull/4021)
+* [[`a43b9291c7`](https://github.com/nodejs/node/commit/a43b9291c7)] - **tools**: replace obsolete ESLint rules (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`a89c6f58f1`](https://github.com/nodejs/node/commit/a89c6f58f1)] - **tools**: update ESLint to version 2.1.0 (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`789f62196a`](https://github.com/nodejs/node/commit/789f62196a)] - **tools**: remove obsolete lint rules (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`154772cfa8`](https://github.com/nodejs/node/commit/154772cfa8)] - **tools**: parse types into links in doc html gen (Claudio Rodriguez) [#4741](https://github.com/nodejs/node/pull/4741)
+* [[`9237b6e38a`](https://github.com/nodejs/node/commit/9237b6e38a)] - **tools**: fix warning in doc parsing (Shigeki Ohtsu) [#4537](https://github.com/nodejs/node/pull/4537)
+* [[`c653cc0c03`](https://github.com/nodejs/node/commit/c653cc0c03)] - **tools**: add recommended ES6 lint rules (Rich Trott) [#5210](https://github.com/nodejs/node/pull/5210)
+* [[`993d9b7df0`](https://github.com/nodejs/node/commit/993d9b7df0)] - **tools**: add recommended linting rules (Rich Trott) [#5188](https://github.com/nodejs/node/pull/5188)
+* [[`8423125223`](https://github.com/nodejs/node/commit/8423125223)] - **tools**: remove excessive comments from .eslintrc (Rich Trott) [#5151](https://github.com/nodejs/node/pull/5151)
+* [[`4c687c98e4`](https://github.com/nodejs/node/commit/4c687c98e4)] - **tools**: enable no-proto rule for linter (Jackson Tian) [#5140](https://github.com/nodejs/node/pull/5140)
+* [[`28e4e6f312`](https://github.com/nodejs/node/commit/28e4e6f312)] - **tools**: disallow mixed spaces and tabs for indents (Rich Trott) [#5135](https://github.com/nodejs/node/pull/5135)
+* [[`50c6fe8604`](https://github.com/nodejs/node/commit/50c6fe8604)] - **tools**: alphabetize eslint stylistic issues section (Rich Trott)
+* [[`ee594f1ed7`](https://github.com/nodejs/node/commit/ee594f1ed7)] - **tools**: lint for empty character classes in regex (Rich Trott) [#5115](https://github.com/nodejs/node/pull/5115)
+* [[`bf0e239e99`](https://github.com/nodejs/node/commit/bf0e239e99)] - **tools**: lint for spacing around unary operators (Rich Trott) [#5063](https://github.com/nodejs/node/pull/5063)
+* [[`6345acb792`](https://github.com/nodejs/node/commit/6345acb792)] - **tools**: enable no-redeclare rule for linter (Rich Trott) [#5047](https://github.com/nodejs/node/pull/5047)
+* [[`1dae175b62`](https://github.com/nodejs/node/commit/1dae175b62)] - **tools**: fix redeclared vars in doc/json.js (Rich Trott) [#5047](https://github.com/nodejs/node/pull/5047)
+* [[`d1d220a1cf`](https://github.com/nodejs/node/commit/d1d220a1cf)] - **tools**: apply linting to doc tools (Rich Trott) [#4973](https://github.com/nodejs/node/pull/4973)
+* [[`eddde1f60c`](https://github.com/nodejs/node/commit/eddde1f60c)] - **tools**: fix detecting constructor for JSON doc (Timothy Gu) [#4966](https://github.com/nodejs/node/pull/4966)
+* [[`bcb327c8dd`](https://github.com/nodejs/node/commit/bcb327c8dd)] - **tools**: add property types in JSON documentation (Timothy Gu) [#4884](https://github.com/nodejs/node/pull/4884)
+* [[`9a06a4c116`](https://github.com/nodejs/node/commit/9a06a4c116)] - **tools**: enable assorted ESLint error rules (Roman Reiss) [#4864](https://github.com/nodejs/node/pull/4864)
+* [[`38474cfd49`](https://github.com/nodejs/node/commit/38474cfd49)] - **tools**: add arrow function rules to eslint (cjihrig) [#4813](https://github.com/nodejs/node/pull/4813)
+* [[`f898abaa4f`](https://github.com/nodejs/node/commit/f898abaa4f)] - **tools**: fix setting path containing an ampersand (Brian White) [#4804](https://github.com/nodejs/node/pull/4804)
+* [[`d10bee8e79`](https://github.com/nodejs/node/commit/d10bee8e79)] - **tools**: enable no-extra-semi rule in eslint (Michaël Zasso) [#2205](https://github.com/nodejs/node/pull/2205)
+* [[`01006392cf`](https://github.com/nodejs/node/commit/01006392cf)] - **tools,doc**: fix linting errors (Rich Trott) [#5161](https://github.com/nodejs/node/pull/5161)
+* [[`57a5f8731a`](https://github.com/nodejs/node/commit/57a5f8731a)] - **url**: change scoping of variables with let (Kári Tristan Helgason) [#4867](https://github.com/nodejs/node/pull/4867)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.0/node-v4.4.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.0/node-v4.4.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.0/node-v4.4.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.0/node-v4.4.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.0/node-v4.4.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.0/<br>
+Documentation: https://nodejs.org/docs/v4.4.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+650c2f1e186a4974304b652321fbb3c4bd22ee7bc7c2c406c6e244dd6a6d38be  node-v4.4.0-darwin-x64.tar.gz
+e2aecfc2caf2881b463c98918f8e813be6b96e28e616a73376b0bbf9ed4d65c8  node-v4.4.0-darwin-x64.tar.xz
+60aff0f9ea74bc64a8d0653828f63d6e8c5f39c3f7a16dee4a6ab48707071236  node-v4.4.0-headers.tar.gz
+fc92838cc68322407b5fbfd787dcdcc3c2d094f98755df9b7168b0198331da7a  node-v4.4.0-headers.tar.xz
+649590a9c16d262ba95b8e22a2a69105f7e881375b879e34e647748f18d2c830  node-v4.4.0-linux-arm64.tar.gz
+edded0f3638757c7d1250ed8d9e2cf2790467d2f4295830e455d705d7cabbbf2  node-v4.4.0-linux-arm64.tar.xz
+9ae5e1bb3ddeb4ec399922b0cadff47109b1711e79518be64566653454c19df2  node-v4.4.0-linux-armv6l.tar.gz
+a1b68ff29aec840ef16549db542adc5fca764e5bdfc2e01c953ee30ce76f2c78  node-v4.4.0-linux-armv6l.tar.xz
+c610f75a848b3334148c8d78ce125550b296356fc6baf4fdd8167142aad24806  node-v4.4.0-linux-armv7l.tar.gz
+010d45cda9ced750f50fcc8ba3cf130edf2568d8c1346cdc8099096dcbc832b3  node-v4.4.0-linux-armv7l.tar.xz
+1978d58ea0b640e0ce1766f6cc71b163baa7ad3cafbff69051f2b71c9edaf353  node-v4.4.0-linux-ppc64le.tar.gz
+7f09ce7f067ade6b18ba3c7bea46986fd7b91efbcedb0f24d8b0523d0444634b  node-v4.4.0-linux-ppc64le.tar.xz
+114a865effcff2783022ef0fcd30d1e51624d6c28140db0bdc662bcd0f850d8b  node-v4.4.0-linux-x64.tar.gz
+781f63ca7a2f43cde6ca6561485582fdf63f2c78b66217bee6a1a5749fe2f28e  node-v4.4.0-linux-x64.tar.xz
+53eb070a459838fb5bff9edc8260b6d0007409d36b8f2917bc1e523e92d6d99f  node-v4.4.0-linux-x86.tar.gz
+200cb6ba462e860039407bd3205e8d3a8ffae5fa7060dc0ef906d7c86e01b85c  node-v4.4.0-linux-x86.tar.xz
+13eb21a569218815b37893af9f6080eaa8156d0e66c38ed15e5bed4abac739e4  node-v4.4.0.pkg
+46338fcf165edb93528196f942dd38d241abf56ca6e940200696f22fb40d7fe4  node-v4.4.0-sunos-x64.tar.gz
+c98d794d6bdf25a5f4e686e5c0665ed107feee9191fef476abac648cc9f09662  node-v4.4.0-sunos-x64.tar.xz
+4131f8f4baeb527a534c3b6a951d98727013e412a8c455c25c77a06a7faa0dfc  node-v4.4.0-sunos-x86.tar.gz
+8a5d8b12660775d4b968a723d16b99e684ba31af1da36dc2fbaf44784ebf614f  node-v4.4.0-sunos-x86.tar.xz
+2cfc76292576d17a8f2434329221675972c96e5fd60cd694610f53134079f92e  node-v4.4.0.tar.gz
+6ae44ae9a9cd1f102ca7f3ea09ca6223afe88fab4911f1bf21c9da2a1e795f1d  node-v4.4.0.tar.xz
+c87245838da77c601b38752626da8344b8874bedc3fa7d8634924cb70a801fe7  node-v4.4.0-x64.msi
+b403b8142a44b4b5fc713b6f29d5bfd0d0cbdaf46ba86ef0b04ef1c3756f6398  node-v4.4.0-x86.msi
+57b68aa386d828afb6b36c10953c95108b5f8e257562a9d9650f2597006879ed  win-x64/node.exe
+c0490530037a43a94bec8abe5c7f5b98d20d406c9c5387a2372d148b2a37286d  win-x64/node.lib
+23f6e19089ed4dc97dcf981ba5a1c5e2e9d726bc8857f434158bf3ed2dc161d5  win-x86/node.exe
+a5b5353caabbb9fe4e244235e947d35b81968874cd0b863dba883e279627f316  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJW38g9AAoJEJM7AfQLXKlGSk4H/AzwPhn3WTWA6NDVz/P9ZJ46
+P09EFxE/krDqA5LNO1+5tQ+HTzdTSdruYsQBd2qfewjJ64Ho+Gma4ALKruWaxklX
+qcv+0p26W2IRbNh3qOsSJGyXgtLHJsppx/wtdq5j9wv355NAfabMPnD/yffdqI0M
+F0sloJBwjGnMq53wBjy7xiSnDHefINWE5tXcezxqtmS+H+mX4GNuChz5UUbyrhn3
+6BEI/3FmQLpJ+zSzV3s2GHgiUxss4OF/EB0eh7BqLUwoc6tPZ7Uec43x0OtBTIbr
+rkjqj1mruq0G2WwWmYiMZlwsG5AMAmDHQ4peE95jwI2kBU1/Gy+YB/mxeZjNXSo=
+=fDQ1
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.1.md b/locale/uk/blog/release/v4.4.1.md
new file mode 100755
index 0000000000000..4fededb84b36d
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.1.md
@@ -0,0 +1,205 @@
+---
+date: 2016-03-22T22:59:32.738Z
+version: 4.4.1
+category: release
+title: Node v4.4.1 (LTS)
+slug: node-v4-4-1
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable Changes
+* **build**:
+  - Updated Logos for the OSX + Windows installers
+    - (Rod Vagg) [#5401](https://github.com/nodejs/node/pull/5401)
+    - (Robert Jefe Lindstaedt) [#5531](https://github.com/nodejs/node/pull/5531)
+  - New option to select your VS Version in the Windows installer
+    - (julien.waechter) [#4645](https://github.com/nodejs/node/pull/4645)
+  - Support Visual C++ Build Tools 2015
+    - (João Reis) [#5627](https://github.com/nodejs/node/pull/5627)
+* **tools**:
+  - Gyp now works on OSX without XCode
+    - (Shigeki Ohtsu) [nodejs/node#1325](https://github.com/nodejs/node/pull/1325)
+
+### Commits
+
+* [[`df283f8a03`](https://github.com/nodejs/node/commit/df283f8a03)] - **benchmark**: fix linting issues (Rich Trott) [#5773](https://github.com/nodejs/node/pull/5773)
+* [[`c901741c60`](https://github.com/nodejs/node/commit/c901741c60)] - **benchmark**: use strict mode (Rich Trott) [#5773](https://github.com/nodejs/node/pull/5773)
+* [[`4be2065dbc`](https://github.com/nodejs/node/commit/4be2065dbc)] - **benchmark**: refactor to eliminate redeclared vars (Rich Trott) [#5773](https://github.com/nodejs/node/pull/5773)
+* [[`ddac368533`](https://github.com/nodejs/node/commit/ddac368533)] - **benchmark**: fix lint errors (Rich Trott) [#5773](https://github.com/nodejs/node/pull/5773)
+* [[`03b20a73b9`](https://github.com/nodejs/node/commit/03b20a73b9)] - **benchmark**: add benchmark for buf.compare() (Rich Trott) [#5441](https://github.com/nodejs/node/pull/5441)
+* [[`b816044845`](https://github.com/nodejs/node/commit/b816044845)] - **buffer**: remove duplicated code in fromObject (HUANG Wei) [#4948](https://github.com/nodejs/node/pull/4948)
+* [[`067ce9b905`](https://github.com/nodejs/node/commit/067ce9b905)] - **build**: don't install github templates (Johan Bergström) [#5612](https://github.com/nodejs/node/pull/5612)
+* [[`a1772dc515`](https://github.com/nodejs/node/commit/a1772dc515)] - **build**: update Node.js logo on OSX installer (Rod Vagg) [#5401](https://github.com/nodejs/node/pull/5401)
+* [[`9058fc0383`](https://github.com/nodejs/node/commit/9058fc0383)] - **build**: correctly detect clang version (Stefan Budeanu) [#5553](https://github.com/nodejs/node/pull/5553)
+* [[`1165ecc6f7`](https://github.com/nodejs/node/commit/1165ecc6f7)] - **build**: update Node.js logo on Win installer (Robert Jefe Lindstaedt) [#5531](https://github.com/nodejs/node/pull/5531)
+* [[`4990ddad72`](https://github.com/nodejs/node/commit/4990ddad72)] - **build**: remove --quiet from eslint invocation (firedfox) [#5519](https://github.com/nodejs/node/pull/5519)
+* [[`46a5d519dd`](https://github.com/nodejs/node/commit/46a5d519dd)] - **build**: skip msi build if WiX is not found (Tsarevich Dmitry) [#5220](https://github.com/nodejs/node/pull/5220)
+* [[`dac4e64491`](https://github.com/nodejs/node/commit/dac4e64491)] - **build**: add option to select VS version (julien.waechter) [#4645](https://github.com/nodejs/node/pull/4645)
+* [[`7a10fd3a56`](https://github.com/nodejs/node/commit/7a10fd3a56)] - **collaborator_guide**: clarify commit message rules (Wyatt Preul) [#5661](https://github.com/nodejs/node/pull/5661)
+* [[`97e95d04c2`](https://github.com/nodejs/node/commit/97e95d04c2)] - **crypto**: PBKDF2 works with `int` not `ssize_t` (Fedor Indutny) [#5397](https://github.com/nodejs/node/pull/5397)
+* [[`57b02e6a3e`](https://github.com/nodejs/node/commit/57b02e6a3e)] - **debugger**: remove unneeded callback check (Rich Trott) [#5319](https://github.com/nodejs/node/pull/5319)
+* [[`19ae308867`](https://github.com/nodejs/node/commit/19ae308867)] - **deps**: update openssl config (Shigeki Ohtsu) [#5630](https://github.com/nodejs/node/pull/5630)
+* [[`d7b81b5bc7`](https://github.com/nodejs/node/commit/d7b81b5bc7)] - **deps**: cherry-pick 2e4da65 from v8's 4.8 upstream (Michael Dawson) [#5293](https://github.com/nodejs/node/pull/5293)
+* [[`1e05f371d6`](https://github.com/nodejs/node/commit/1e05f371d6)] - **doc**: fix typo in synchronous randomBytes example (Andrea Giammarchi) [#5781](https://github.com/nodejs/node/pull/5781)
+* [[`5f54bd2088`](https://github.com/nodejs/node/commit/5f54bd2088)] - **doc**: topic blocking vs non-blocking (Jarrett Widman) [#5326](https://github.com/nodejs/node/pull/5326)
+* [[`0943001563`](https://github.com/nodejs/node/commit/0943001563)] - **doc**: fix invalid path doc comments (Rich Trott) [#5797](https://github.com/nodejs/node/pull/5797)
+* [[`bb423bb1e6`](https://github.com/nodejs/node/commit/bb423bb1e6)] - **doc**: update release tweet template (Jeremiah Senkpiel) [#5628](https://github.com/nodejs/node/pull/5628)
+* [[`1e877f10aa`](https://github.com/nodejs/node/commit/1e877f10aa)] - **doc**: fix typo in child_process docs (Benjamin Gruenbaum) [#5681](https://github.com/nodejs/node/pull/5681)
+* [[`d53dcc599b`](https://github.com/nodejs/node/commit/d53dcc599b)] - **doc**: update fansworld-claudio username on README (Claudio Rodriguez) [#5680](https://github.com/nodejs/node/pull/5680)
+* [[`4332f8011e`](https://github.com/nodejs/node/commit/4332f8011e)] - **doc**: fix return value of write methods (Felix Böhm) [#5736](https://github.com/nodejs/node/pull/5736)
+* [[`e572542de5`](https://github.com/nodejs/node/commit/e572542de5)] - **doc**: Add note about use of JSON.stringify() (Mithun Patel) [#5723](https://github.com/nodejs/node/pull/5723)
+* [[`daf3ef66ef`](https://github.com/nodejs/node/commit/daf3ef66ef)] - **doc**: explain path.format() algorithm (Rich Trott) [#5688](https://github.com/nodejs/node/pull/5688)
+* [[`f6d4982aa0`](https://github.com/nodejs/node/commit/f6d4982aa0)] - **doc**: clarify type of first argument in zlib (Kirill Fomichev) [#5685](https://github.com/nodejs/node/pull/5685)
+* [[`07e71b2d44`](https://github.com/nodejs/node/commit/07e71b2d44)] - **doc**: fix typo in api/addons (Daijiro Wachi) [#5678](https://github.com/nodejs/node/pull/5678)
+* [[`c6dc56175b`](https://github.com/nodejs/node/commit/c6dc56175b)] - **doc**: remove non-standard use of hyphens (Stefano Vozza)
+* [[`4c92316972`](https://github.com/nodejs/node/commit/4c92316972)] - **doc**: add fansworld-claudio to collaborators (Claudio Rodriguez) [#5668](https://github.com/nodejs/node/pull/5668)
+* [[`0a6e883f85`](https://github.com/nodejs/node/commit/0a6e883f85)] - **doc**: add thekemkid to collaborators (Glen Keane) [#5667](https://github.com/nodejs/node/pull/5667)
+* [[`39c7d8a972`](https://github.com/nodejs/node/commit/39c7d8a972)] - **doc**: add AndreasMadsen to collaborators (Andreas Madsen) [#5666](https://github.com/nodejs/node/pull/5666)
+* [[`eec3008970`](https://github.com/nodejs/node/commit/eec3008970)] - **doc**: add whitlockjc to collaborators (Jeremy Whitlock) [#5665](https://github.com/nodejs/node/pull/5665)
+* [[`e5f254d83c`](https://github.com/nodejs/node/commit/e5f254d83c)] - **doc**: add benjamingr to collaborator list (Benjamin Gruenbaum) [#5664](https://github.com/nodejs/node/pull/5664)
+* [[`3f718643c9`](https://github.com/nodejs/node/commit/3f718643c9)] - **doc**: add phillipj to collaborators (Phillip Johnsen) [#5663](https://github.com/nodejs/node/pull/5663)
+* [[`2d5527fe69`](https://github.com/nodejs/node/commit/2d5527fe69)] - **doc**: add mattloring to collaborators (Matt Loring) [#5662](https://github.com/nodejs/node/pull/5662)
+* [[`51763462bc`](https://github.com/nodejs/node/commit/51763462bc)] - **doc**: include typo in 'unhandledRejection' example (Robert C Jensen) [#5654](https://github.com/nodejs/node/pull/5654)
+* [[`cae5da2f0a`](https://github.com/nodejs/node/commit/cae5da2f0a)] - **doc**: fix markdown links (Steve Mao) [#5641](https://github.com/nodejs/node/pull/5641)
+* [[`b1b17efcb7`](https://github.com/nodejs/node/commit/b1b17efcb7)] - **doc**: move build instructions to a new document (Johan Bergström) [#5634](https://github.com/nodejs/node/pull/5634)
+* [[`13a8bde1fa`](https://github.com/nodejs/node/commit/13a8bde1fa)] - **doc**: fix dns.resolveCname description typo (axvm) [#5622](https://github.com/nodejs/node/pull/5622)
+* [[`1faea43c40`](https://github.com/nodejs/node/commit/1faea43c40)] - **doc**: fix typo in fs.symlink (Michaël Zasso) [#5560](https://github.com/nodejs/node/pull/5560)
+* [[`98a1bb6989`](https://github.com/nodejs/node/commit/98a1bb6989)] - **doc**: document directories in test directory (Michael Barrett) [#5557](https://github.com/nodejs/node/pull/5557)
+* [[`04d3f8a741`](https://github.com/nodejs/node/commit/04d3f8a741)] - **doc**: update link green to match homepage (silverwind) [#5548](https://github.com/nodejs/node/pull/5548)
+* [[`1afab6ac9c`](https://github.com/nodejs/node/commit/1afab6ac9c)] - **doc**: add clarification on birthtime in fs stat (Kári Tristan Helgason) [#5479](https://github.com/nodejs/node/pull/5479)
+* [[`d871ae2349`](https://github.com/nodejs/node/commit/d871ae2349)] - **doc**: fix typo in child_process documentation (Evan Lucas) [#5474](https://github.com/nodejs/node/pull/5474)
+* [[`97a18bdbad`](https://github.com/nodejs/node/commit/97a18bdbad)] - **doc**: update NAN urls in ROADMAP.md and doc/releases.md (ronkorving) [#5472](https://github.com/nodejs/node/pull/5472)
+* [[`d4a1fc7acd`](https://github.com/nodejs/node/commit/d4a1fc7acd)] - **doc**: add Testing WG (Rich Trott) [#5461](https://github.com/nodejs/node/pull/5461)
+* [[`1642078580`](https://github.com/nodejs/node/commit/1642078580)] - **doc**: fix crypto function indentation level (Brian White) [#5460](https://github.com/nodejs/node/pull/5460)
+* [[`2b0c7ad985`](https://github.com/nodejs/node/commit/2b0c7ad985)] - **doc**: fix links in tls, cluster docs (Alexander Makarenko) [#5364](https://github.com/nodejs/node/pull/5364)
+* [[`901dbabea6`](https://github.com/nodejs/node/commit/901dbabea6)] - **doc**: fix relative links in net docs (Evan Lucas) [#5358](https://github.com/nodejs/node/pull/5358)
+* [[`38d429172d`](https://github.com/nodejs/node/commit/38d429172d)] - **doc**: fix typo in pbkdf2Sync code sample (Marc Cuva) [#5306](https://github.com/nodejs/node/pull/5306)
+* [[`d4cfc6f97c`](https://github.com/nodejs/node/commit/d4cfc6f97c)] - **doc**: add missing property in cluster example (Rafael Cepeda) [#5305](https://github.com/nodejs/node/pull/5305)
+* [[`b66d6b1458`](https://github.com/nodejs/node/commit/b66d6b1458)] - **doc**: improve httpVersionMajor / httpVersionMajor (Jackson Tian) [#5296](https://github.com/nodejs/node/pull/5296)
+* [[`70c872c9c4`](https://github.com/nodejs/node/commit/70c872c9c4)] - **doc**: improve unhandledException doc copy (James M Snell) [#5287](https://github.com/nodejs/node/pull/5287)
+* [[`ba5e0b6110`](https://github.com/nodejs/node/commit/ba5e0b6110)] - **doc**: fix buf.readInt16LE output (Chinedu Francis Nwafili) [#5282](https://github.com/nodejs/node/pull/5282)
+* [[`1624d5b049`](https://github.com/nodejs/node/commit/1624d5b049)] - **doc**: document base64url encoding support (Tristan Slominski) [#5243](https://github.com/nodejs/node/pull/5243)
+* [[`b1d580c9d2`](https://github.com/nodejs/node/commit/b1d580c9d2)] - **doc**: update removeListener behaviour (Vaibhav) [#5201](https://github.com/nodejs/node/pull/5201)
+* [[`ca17f91ba8`](https://github.com/nodejs/node/commit/ca17f91ba8)] - **doc**: add note for binary safe string reading (Anton Andesen) [#5155](https://github.com/nodejs/node/pull/5155)
+* [[`0830bb4950`](https://github.com/nodejs/node/commit/0830bb4950)] - **doc**: clarify when writable.write callback is called (Kevin Locke) [#4810](https://github.com/nodejs/node/pull/4810)
+* [[`17a74305c8`](https://github.com/nodejs/node/commit/17a74305c8)] - **doc**: add info to docs on how to submit docs patch (Sequoia McDowell) [#4591](https://github.com/nodejs/node/pull/4591)
+* [[`470a9ca909`](https://github.com/nodejs/node/commit/470a9ca909)] - **doc**: add onboarding resources (Jeremiah Senkpiel) [#3726](https://github.com/nodejs/node/pull/3726)
+* [[`3168e6b486`](https://github.com/nodejs/node/commit/3168e6b486)] - **doc**: update V8 URL (Craig Akimoto) [#5530](https://github.com/nodejs/node/pull/5530)
+* [[`04d16eb7e8`](https://github.com/nodejs/node/commit/04d16eb7e8)] - **doc**: document fs.datasync(Sync) (Ron Korving) [#5402](https://github.com/nodejs/node/pull/5402)
+* [[`29646200f8`](https://github.com/nodejs/node/commit/29646200f8)] - **doc**: add Evan Lucas to the CTC (Rod Vagg)
+* [[`a2a32b7810`](https://github.com/nodejs/node/commit/a2a32b7810)] - **doc**: add Rich Trott to the CTC (Rod Vagg) [#5276](https://github.com/nodejs/node/pull/5276)
+* [[`4e469d5e47`](https://github.com/nodejs/node/commit/4e469d5e47)] - **doc**: add Ali Ijaz Sheikh to the CTC (Rod Vagg) [#5277](https://github.com/nodejs/node/pull/5277)
+* [[`d09b44f59b`](https://github.com/nodejs/node/commit/d09b44f59b)] - **doc**: add Сковорода Никита Андреевич to the CTC (Rod Vagg) [#5278](https://github.com/nodejs/node/pull/5278)
+* [[`ebbc64bc97`](https://github.com/nodejs/node/commit/ebbc64bc97)] - **doc**: add "building node with ninja" guide (Jeremiah Senkpiel) [#4767](https://github.com/nodejs/node/pull/4767)
+* [[`67245fa0e3`](https://github.com/nodejs/node/commit/67245fa0e3)] - **doc**: clarify code of conduct reporting (Julie Pagano) [#5107](https://github.com/nodejs/node/pull/5107)
+* [[`cd78ff9706`](https://github.com/nodejs/node/commit/cd78ff9706)] - **doc**: fix links in Addons docs (Alexander Makarenko) [#5072](https://github.com/nodejs/node/pull/5072)
+* [[`20539954ff`](https://github.com/nodejs/node/commit/20539954ff)] - **docs**: fix man pages link if tok type is code (Mithun Patel) [#5721](https://github.com/nodejs/node/pull/5721)
+* [[`38d7b0b6ea`](https://github.com/nodejs/node/commit/38d7b0b6ea)] - **docs**: update link to iojs+release ci job (Myles Borins) [#5632](https://github.com/nodejs/node/pull/5632)
+* [[`f982632f90`](https://github.com/nodejs/node/commit/f982632f90)] - **http**: remove old, confusing comment (Brian White) [#5233](https://github.com/nodejs/node/pull/5233)
+* [[`ca5d7a8bb6`](https://github.com/nodejs/node/commit/ca5d7a8bb6)] - **http**: remove unnecessary check (Brian White) [#5233](https://github.com/nodejs/node/pull/5233)
+* [[`2ce83bd8f9`](https://github.com/nodejs/node/commit/2ce83bd8f9)] - **http,util**: fix typos in comments (Alexander Makarenko) [#5279](https://github.com/nodejs/node/pull/5279)
+* [[`b690916e5a`](https://github.com/nodejs/node/commit/b690916e5a)] - **lib**: freelist: use .pop() for allocation (Anton Khlynovskiy) [#2174](https://github.com/nodejs/node/pull/2174)
+* [[`e7f45f0a17`](https://github.com/nodejs/node/commit/e7f45f0a17)] - **repl**: handle quotes within regexp literal (Prince J Wesley) [#5117](https://github.com/nodejs/node/pull/5117)
+* [[`7c3b844f78`](https://github.com/nodejs/node/commit/7c3b844f78)] - **src**: return UV_EAI_NODATA on empty lookup (cjihrig) [#4715](https://github.com/nodejs/node/pull/4715)
+* [[`242a65e930`](https://github.com/nodejs/node/commit/242a65e930)] - **stream**: prevent object map change in TransformState (Evan Lucas) [#5032](https://github.com/nodejs/node/pull/5032)
+* [[`fb5ba6b928`](https://github.com/nodejs/node/commit/fb5ba6b928)] - **stream**: prevent object map change in ReadableState (Evan Lucas) [#4761](https://github.com/nodejs/node/pull/4761)
+* [[`04db9efd78`](https://github.com/nodejs/node/commit/04db9efd78)] - **stream**: fix no data on partial decode (Brian White) [#5226](https://github.com/nodejs/node/pull/5226)
+* [[`cc0e36ff98`](https://github.com/nodejs/node/commit/cc0e36ff98)] - **string_decoder**: fix performance regression (Brian White) [#5134](https://github.com/nodejs/node/pull/5134)
+* [[`666d3690d8`](https://github.com/nodejs/node/commit/666d3690d8)] - **test**: eval a strict function (Kári Tristan Helgason) [#5250](https://github.com/nodejs/node/pull/5250)
+* [[`9952bcf203`](https://github.com/nodejs/node/commit/9952bcf203)] - **test**: bug repro for vm function redefinition (cjihrig) [#5528](https://github.com/nodejs/node/pull/5528)
+* [[`063f22f1f0`](https://github.com/nodejs/node/commit/063f22f1f0)] - **test**: check memoryUsage properties The properties on memoryUsage were not checked before, this commit checks them. (Wyatt Preul) [#5546](https://github.com/nodejs/node/pull/5546)
+* [[`7a0fcfc127`](https://github.com/nodejs/node/commit/7a0fcfc127)] - **test**: remove broken debugger scenarios (Rich Trott) [#5532](https://github.com/nodejs/node/pull/5532)
+* [[`ba9ad2662c`](https://github.com/nodejs/node/commit/ba9ad2662c)] - **test**: apply Linux workaround to Linux only (Rich Trott) [#5471](https://github.com/nodejs/node/pull/5471)
+* [[`4aa2c03d31`](https://github.com/nodejs/node/commit/4aa2c03d31)] - **test**: increase timeout for test-tls-fast-writing (Rich Trott) [#5466](https://github.com/nodejs/node/pull/5466)
+* [[`b4ef644ce4`](https://github.com/nodejs/node/commit/b4ef644ce4)] - **test**: retry on known SmartOS bug (Rich Trott) [#5454](https://github.com/nodejs/node/pull/5454)
+* [[`d681bf24b5`](https://github.com/nodejs/node/commit/d681bf24b5)] - **test**: fix flaky child-process-fork-regr-gh-2847 (Santiago Gimeno) [#5422](https://github.com/nodejs/node/pull/5422)
+* [[`b4fbe04514`](https://github.com/nodejs/node/commit/b4fbe04514)] - **test**: fix test-timers.reliability on OS X (Rich Trott) [#5379](https://github.com/nodejs/node/pull/5379)
+* [[`99269ffdbf`](https://github.com/nodejs/node/commit/99269ffdbf)] - **test**: increase timeouts on some unref timers tests (Jeremiah Senkpiel) [#5352](https://github.com/nodejs/node/pull/5352)
+* [[`85f927a774`](https://github.com/nodejs/node/commit/85f927a774)] - **test**: prevent flakey test on pi2 (Trevor Norris) [#5537](https://github.com/nodejs/node/pull/5537)
+* [[`c86902d800`](https://github.com/nodejs/node/commit/c86902d800)] - **test**: mitigate flaky test-http-agent (Rich Trott) [#5346](https://github.com/nodejs/node/pull/5346)
+* [[`f242e62817`](https://github.com/nodejs/node/commit/f242e62817)] - **test**: remove flaky designation from fixed tests (Rich Trott) [#5459](https://github.com/nodejs/node/pull/5459)
+* [[`a39aacf035`](https://github.com/nodejs/node/commit/a39aacf035)] - **test**: refactor test-dgram-udp4 (Santiago Gimeno) [#5339](https://github.com/nodejs/node/pull/5339)
+* [[`6386f62221`](https://github.com/nodejs/node/commit/6386f62221)] - **test**: remove unneeded bind() and related comments (Aayush Naik) [#5023](https://github.com/nodejs/node/pull/5023)
+* [[`068b0cbd12`](https://github.com/nodejs/node/commit/068b0cbd12)] - **test**: move cluster tests to parallel (Rich Trott) [#4774](https://github.com/nodejs/node/pull/4774)
+* [[`a673c9ae2d`](https://github.com/nodejs/node/commit/a673c9ae2d)] - **tls**: fix assert in context._external accessor (Ben Noordhuis) [#5521](https://github.com/nodejs/node/pull/5521)
+* [[`8ffef48fee`](https://github.com/nodejs/node/commit/8ffef48fee)] - **tools**: fix gyp to work on MacOSX without XCode (Shigeki Ohtsu) [nodejs/node#1325](https://github.com/nodejs/node/pull/1325)
+* [[`4b6a8f4321`](https://github.com/nodejs/node/commit/4b6a8f4321)] - **tools**: update gyp to b3cef02 (Imran Iqbal) [#3487](https://github.com/nodejs/node/pull/3487)
+* [[`7501ddc878`](https://github.com/nodejs/node/commit/7501ddc878)] - **tools**: support testing known issues (cjihrig) [#5528](https://github.com/nodejs/node/pull/5528)
+* [[`10ec1d2a6b`](https://github.com/nodejs/node/commit/10ec1d2a6b)] - **tools**: enable linting for benchmarks (Rich Trott) [#5773](https://github.com/nodejs/node/pull/5773)
+* [[`deec8bc5f5`](https://github.com/nodejs/node/commit/deec8bc5f5)] - **tools**: reduce verbosity of cpplint (Sakthipriyan Vairamani) [#5578](https://github.com/nodejs/node/pull/5578)
+* [[`64d5752711`](https://github.com/nodejs/node/commit/64d5752711)] - **tools**: enable no-self-assign ESLint rule (Rich Trott) [#5552](https://github.com/nodejs/node/pull/5552)
+* [[`131ed494e2`](https://github.com/nodejs/node/commit/131ed494e2)] - **tools**: enable no-extra-parens in ESLint (Rich Trott) [#5512](https://github.com/nodejs/node/pull/5512)
+* [[`d4b9f02fdc`](https://github.com/nodejs/node/commit/d4b9f02fdc)] - **tools**: apply custom buffer lint rule to /lib only (Rich Trott) [#5371](https://github.com/nodejs/node/pull/5371)
+* [[`6867bed4c4`](https://github.com/nodejs/node/commit/6867bed4c4)] - **tools**: enable additional lint rules (Rich Trott) [#5357](https://github.com/nodejs/node/pull/5357)
+* [[`5e6b7605ee`](https://github.com/nodejs/node/commit/5e6b7605ee)] - **tools**: add Node.js-specific ESLint rules (Rich Trott) [#5320](https://github.com/nodejs/node/pull/5320)
+* [[`6dc49ae203`](https://github.com/nodejs/node/commit/6dc49ae203)] - **tools,benchmark**: increase lint compliance (Rich Trott) [#5773](https://github.com/nodejs/node/pull/5773)
+* [[`dff7091fce`](https://github.com/nodejs/node/commit/dff7091fce)] - **url**: group slashed protocols by protocol name (nettofarah) [#5380](https://github.com/nodejs/node/pull/5380)
+* [[`0e97a3ea51`](https://github.com/nodejs/node/commit/0e97a3ea51)] - **win,build**: support Visual C++ Build Tools 2015 (João Reis) [#5627](https://github.com/nodejs/node/pull/5627)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.1/node-v4.4.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.1/node-v4.4.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.1/node-v4.4.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.1/node-v4.4.1-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.1/node-v4.4.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.1/<br>
+Documentation: https://nodejs.org/docs/v4.4.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+628195be45f7248a6defb6c23aaed7d0bca78979934f6e868387ddeb311dcc56  node-v4.4.1-darwin-x64.tar.gz
+1a6936301202d3e53daeddb442654cc28ec30dc4ad788872e4efd122ff236a3c  node-v4.4.1-darwin-x64.tar.xz
+e759ee28a27dc47a5c80e48b063c0bee015f3b6d2f8f593ad0eabfab0ebb3922  node-v4.4.1-headers.tar.gz
+21c1ac9f615452c13b6e4ec5a4d5bb655647d942decd3585b2eb4d75e1ec6d11  node-v4.4.1-headers.tar.xz
+8ff4cfc1452abaa95f4d40cf13f7ca3c4cf38da23a3ebde9247154dd51fbc42d  node-v4.4.1-linux-arm64.tar.gz
+b58b1729d3b084255c18c99b31a6db375311ce2effb4f1083cee1b480d03e97f  node-v4.4.1-linux-arm64.tar.xz
+f4996cce41a3d0d6b551e64466f591203ad2a637e4613159b515d6fff576df9a  node-v4.4.1-linux-armv6l.tar.gz
+58627371bc50452fcfbdae66fae043eacde6649ff27fd8b41e2ce42e84720b4e  node-v4.4.1-linux-armv6l.tar.xz
+d61f87dd5994a3a095950d2477a981e0f250052b96ca4d32b1629bfda93e8d64  node-v4.4.1-linux-armv7l.tar.gz
+e1eaf11800762f45a0b07847c1276ed2c8a13e207ed6ea9938ad992379204131  node-v4.4.1-linux-armv7l.tar.xz
+ee8e2611269eae2f84644c7a36416e9ffecf71f9294bd1e463152cb979a35940  node-v4.4.1-linux-ppc64le.tar.gz
+8ff8ed52e9fafdda91645e5c6e45bca15aa377fd771441d17aee79b7d61c4b36  node-v4.4.1-linux-ppc64le.tar.xz
+f0a53527f52dbcab3b98921a6cfe8613e5fe26fb796624988f6d615c30305a95  node-v4.4.1-linux-x64.tar.gz
+3b58583102afbd54214f1ce61d90c7b05e807471bd6ecb084e2fa7de540cdce2  node-v4.4.1-linux-x64.tar.xz
+200a3f800110ee5342dd80498a3365dbb704f5e214d26447dcd9dfcf2a08b6d2  node-v4.4.1-linux-x86.tar.gz
+1267b0602e7f7f0c1ab53c841dc71d56dd70c4883396c2e1dc6a1108ab47a622  node-v4.4.1-linux-x86.tar.xz
+02e77d4ccd6d2a97124f61fc264f0e51268fe395c5de7f7528897eb7d31873e3  node-v4.4.1.pkg
+5612216d93a5f9ed7d0c054349ec23f45e261eb3b30b6fd40e0ef3a7b339ee82  node-v4.4.1-sunos-x64.tar.gz
+d546f5979449f88d20e8389de67ff63f1375b3c4b7080725dca4824c4f4f887e  node-v4.4.1-sunos-x64.tar.xz
+41c2559c98cc739bae4dd477d9119a130580c489cfed1222b5b67eab05a63d6d  node-v4.4.1-sunos-x86.tar.gz
+55841958492bfcfb8419812a766dbdff908f5fef2c6ef9760a3027e7fe16aca5  node-v4.4.1-sunos-x86.tar.xz
+f3e604cc4d05a4810c37cd43a838a2dc4399d517bd1e8c53b7670dcffc4dc481  node-v4.4.1.tar.gz
+3a37c89a3ac965688f9e6557579993b73eee44195a5fd53fded03a667d3d6a0a  node-v4.4.1.tar.xz
+796aa50d240740ffbb39b38dfeec5d040061e0bf5adb60d3543b83402430cd11  node-v4.4.1-x64.msi
+6b253abd93f2b01ec1e48f642d0611d3132c926757b1fdb5623db1c875f3ab87  node-v4.4.1-x86.msi
+fc4b93fab650040070cd5df1fce2deb77ef129096f6c675eb2e3d3d1a6304c97  win-x64/node.exe
+961651a05f31c82d70dbe00d40f1cb5b83d32b2dd87261f03356c1a563abf3b1  win-x64/node.lib
+0f33c55b1c056e702953dd5a6cbe8d9fcecc04bd2d1f0f0fc0335c147fd1b034  win-x86/node.exe
+d4f3d5d2f15a48a0109a769bb78134205c6aa4416dfa0d43da485ad6f8a64014  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJW8c3/AAoJEJM7AfQLXKlGONAH/RQ9ZQ8h+qXNQKq1+f5i+Lgb
+iEWZq1VJc1G/f7+n07N7+IffUz7QelQYh+Lmyd81Stx2ayLc5GCNxPJeWMBqBU+F
+l9gmksyxeu1/VuIz/QEf87B4wUlw1d9pRdWGF/RdH6Nm1U5fFX4EeWIKq+dlCS9V
+RpTInalZ1WCi7sKdPVxfTZe90UMGJUuBVbDHOQWk3z4xZ15pLQtUyHH0XivZXIK8
+odGr6k2UrKycoMdGkKezp8+CMFj6kkDyFLoxZq4kUFT8AQcsrLeZHmw7J6cRBbn6
+ABk2eEYCLDusoUcH+apqOwsB7VMXindHvMDmfdpPAC5+No6LvzH+2PTdg4d055Q=
+=eRWh
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.2.md b/locale/uk/blog/release/v4.4.2.md
new file mode 100755
index 0000000000000..b12a740a22898
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.2.md
@@ -0,0 +1,134 @@
+---
+date: 2016-04-01T01:47:06.225Z
+version: 4.4.2
+category: release
+title: Node v4.4.2 (LTS)
+slug: node-v4-4-2
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+This release includes a security update for npm. For more details you can read [this post on our blog](https://nodejs.org/en/blog/vulnerability/npm-tokens-leak-march-2016/) written by [Forrest L Norvell](https://github.com/othiym23) from npm.
+
+*Update*: The version of npm included in this release did not have the correct version string. As such executing `npm -v` will report `2.15.0` rather than `2.15.1`, which is incorrect. The source code included in this release is in fact the source for `2.15.1`, including the security fix.
+
+### Notable Changes
+
+* **https**:
+  - Under certain conditions ssl sockets may have been causing a memory leak when keepalive is enabled. This is no longer the case. (Alexander Penev) [#5713](https://github.com/nodejs/node/pull/5713)
+* **lib**:
+  - The way that we were internally passing arguments was causing a potential leak. By copying the arguments into an array we can avoid this. (Nathan Woltman) [#4361](https://github.com/nodejs/node/pull/4361)
+* **npm**: 
+  - Upgrade to v2.15.1. Fixes a security flaw in the use of authentication tokens in HTTP requests that would allow an attacker to set up a server that could collect tokens from users of the command-line interface. Authentication tokens have previously been sent with every request made by the CLI for logged-in users, regardless of the destination of the request. This update fixes this by only including those tokens for requests made against the registry or registries used for the current install. (Forrest L Norvell)
+* **repl**:
+  - Previously if you were using the repl in strict mode the column number would be wrong in a stack trace. This is no longer an issue. (Prince J Wesley) [#5416](https://github.com/nodejs/node/pull/5416)
+
+### Commits
+
+* [[`96e163a79f`](https://github.com/nodejs/node/commit/96e163a79f)] - **buffer**: changing let in for loops back to var (Gareth Ellis) [#5819](https://github.com/nodejs/node/pull/5819)
+* [[`0c6f6742f2`](https://github.com/nodejs/node/commit/0c6f6742f2)] - **console**: check that stderr is writable (Rich Trott) [#5635](https://github.com/nodejs/node/pull/5635)
+* [[`55c3f804c4`](https://github.com/nodejs/node/commit/55c3f804c4)] - **deps**: upgrade npm in LTS to 2.15.1 (Forrest L Norvell)
+* [[`1d0e4a987d`](https://github.com/nodejs/node/commit/1d0e4a987d)] - **deps**: remove unused openssl files (Ben Noordhuis) [#5619](https://github.com/nodejs/node/pull/5619)
+* [[`d55599f4d8`](https://github.com/nodejs/node/commit/d55599f4d8)] - **dns**: use template literals (Benjamin Gruenbaum) [#5809](https://github.com/nodejs/node/pull/5809)
+* [[`42bbdc9dd1`](https://github.com/nodejs/node/commit/42bbdc9dd1)] - **doc** Add @mhdawson back to the CTC (James M Snell) [#5633](https://github.com/nodejs/node/pull/5633)
+* [[`8d86d232e7`](https://github.com/nodejs/node/commit/8d86d232e7)] - **doc**: typo: interal->internal. (Corey Kosak) [#5849](https://github.com/nodejs/node/pull/5849)
+* [[`60ddab841e`](https://github.com/nodejs/node/commit/60ddab841e)] - **doc**: add instructions to only sign a release (Jeremiah Senkpiel) [#5876](https://github.com/nodejs/node/pull/5876)
+* [[`040263e0f3`](https://github.com/nodejs/node/commit/040263e0f3)] - **doc**: grammar, clarity and links in timers doc (Bryan English) [#5792](https://github.com/nodejs/node/pull/5792)
+* [[`8c24bd25a6`](https://github.com/nodejs/node/commit/8c24bd25a6)] - **doc**: fix order of end tags of list after heading (firedfox) [#5874](https://github.com/nodejs/node/pull/5874)
+* [[`7c837028da`](https://github.com/nodejs/node/commit/7c837028da)] - **doc**: use consistent event name parameter (Benjamin Gruenbaum) [#5850](https://github.com/nodejs/node/pull/5850)
+* [[`20faf9097d`](https://github.com/nodejs/node/commit/20faf9097d)] - **doc**: explain error message on missing main file (Wolfgang Steiner) [#5812](https://github.com/nodejs/node/pull/5812)
+* [[`79d26ae196`](https://github.com/nodejs/node/commit/79d26ae196)] - **doc**: explain path.format expected properties (John Eversole) [#5801](https://github.com/nodejs/node/pull/5801)
+* [[`e43e8e3a31`](https://github.com/nodejs/node/commit/e43e8e3a31)] - **doc**: add a cli options doc page (Jeremiah Senkpiel) [#5787](https://github.com/nodejs/node/pull/5787)
+* [[`c0a24e4a1d`](https://github.com/nodejs/node/commit/c0a24e4a1d)] - **doc**: fix multiline return comments in querystring (Claudio Rodriguez) [#5705](https://github.com/nodejs/node/pull/5705)
+* [[`bf1fe4693c`](https://github.com/nodejs/node/commit/bf1fe4693c)] - **doc**: Add windows example for Path.format (Mithun Patel) [#5700](https://github.com/nodejs/node/pull/5700)
+* [[`3b8fc4fddc`](https://github.com/nodejs/node/commit/3b8fc4fddc)] - **doc**: update crypto docs to use good defaults (Bill Automata) [#5505](https://github.com/nodejs/node/pull/5505)
+* [[`a6ec8a6cb7`](https://github.com/nodejs/node/commit/a6ec8a6cb7)] - **doc**: fix crypto update() signatures (Brian White) [#5500](https://github.com/nodejs/node/pull/5500)
+* [[`eb0ed46665`](https://github.com/nodejs/node/commit/eb0ed46665)] - **doc**: reformat & improve node.1 manual page (Jeremiah Senkpiel) [#5497](https://github.com/nodejs/node/pull/5497)
+* [[`b70ca4a4b4`](https://github.com/nodejs/node/commit/b70ca4a4b4)] - **doc**: updated fs #5862 removed irrelevant data in fs.markdown (topal) [#5877](https://github.com/nodejs/node/pull/5877)
+* [[`81876612f7`](https://github.com/nodejs/node/commit/81876612f7)] - **https**: fix ssl socket leak when keepalive is used (Alexander Penev) [#5713](https://github.com/nodejs/node/pull/5713)
+* [[`6daebdbd9b`](https://github.com/nodejs/node/commit/6daebdbd9b)] - **lib**: simplify code with String.prototype.repeat() (Jackson Tian) [#5359](https://github.com/nodejs/node/pull/5359)
+* [[`108fc90dd7`](https://github.com/nodejs/node/commit/108fc90dd7)] - **lib**: reduce usage of `self = this` (Jackson Tian) [#5231](https://github.com/nodejs/node/pull/5231)
+* [[`3c8e59c396`](https://github.com/nodejs/node/commit/3c8e59c396)] - **lib**: copy arguments object instead of leaking it (Nathan Woltman) [#4361](https://github.com/nodejs/node/pull/4361)
+* [[`8648420586`](https://github.com/nodejs/node/commit/8648420586)] - **net**: make `isIPv4` and `isIPv6` more efficient (Vladimir Kurchatkin) [#5478](https://github.com/nodejs/node/pull/5478)
+* [[`07b7172d76`](https://github.com/nodejs/node/commit/07b7172d76)] - **net**: remove unused `var self = this` from old code (Benjamin Gruenbaum) [#5224](https://github.com/nodejs/node/pull/5224)
+* [[`acbce4b72b`](https://github.com/nodejs/node/commit/acbce4b72b)] - **repl**: fix stack trace column number in strict mode (Prince J Wesley) [#5416](https://github.com/nodejs/node/pull/5416)
+* [[`0a1eb168e0`](https://github.com/nodejs/node/commit/0a1eb168e0)] - **test**: fix `test-cluster-worker-kill` (Santiago Gimeno) [#5814](https://github.com/nodejs/node/pull/5814)
+* [[`86b876fe7b`](https://github.com/nodejs/node/commit/86b876fe7b)] - **test**: smaller chunk size for smaller person.jpg (Jérémy Lal) [#5813](https://github.com/nodejs/node/pull/5813)
+* [[`1135ee97e7`](https://github.com/nodejs/node/commit/1135ee97e7)] - **test**: strip non-free icc profile from person.jpg (Jérémy Lal) [#5813](https://github.com/nodejs/node/pull/5813)
+* [[`0836d7e2fb`](https://github.com/nodejs/node/commit/0836d7e2fb)] - **test**: fix flaky test-cluster-shared-leak (Claudio Rodriguez) [#5802](https://github.com/nodejs/node/pull/5802)
+* [[`e57355c2f4`](https://github.com/nodejs/node/commit/e57355c2f4)] - **test**: make test-net-connect-options-ipv6.js better (Michael Dawson) [#5791](https://github.com/nodejs/node/pull/5791)
+* [[`1b266fc15c`](https://github.com/nodejs/node/commit/1b266fc15c)] - **test**: remove the use of curl in the test suite (Santiago Gimeno) [#5750](https://github.com/nodejs/node/pull/5750)
+* [[`7e45d4f076`](https://github.com/nodejs/node/commit/7e45d4f076)] - **test**: minimize test-http-get-pipeline-problem (Rich Trott) [#5728](https://github.com/nodejs/node/pull/5728)
+* [[`78effc3484`](https://github.com/nodejs/node/commit/78effc3484)] - **test**: add batch of known issue tests (cjihrig) [#5653](https://github.com/nodejs/node/pull/5653)
+* [[`d506eea4b7`](https://github.com/nodejs/node/commit/d506eea4b7)] - **test**: improve test-npm-install (Santiago Gimeno) [#5613](https://github.com/nodejs/node/pull/5613)
+* [[`7520100e8b`](https://github.com/nodejs/node/commit/7520100e8b)] - **test**: add test-npm-install to parallel tests suite (Myles Borins) [#5166](https://github.com/nodejs/node/pull/5166)
+* [[`b258dddb8c`](https://github.com/nodejs/node/commit/b258dddb8c)] - **test**: repl tab completion test (Santiago Gimeno) [#5534](https://github.com/nodejs/node/pull/5534)
+* [[`f209effe8b`](https://github.com/nodejs/node/commit/f209effe8b)] - **test**: remove timer from test-http-1.0 (Santiago Gimeno) [#5129](https://github.com/nodejs/node/pull/5129)
+* [[`3a901b0e3e`](https://github.com/nodejs/node/commit/3a901b0e3e)] - **tools**: remove unused imports (Sakthipriyan Vairamani) [#5765](https://github.com/nodejs/node/pull/5765)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.2/node-v4.4.2-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.2/node-v4.4.2-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.2/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.2/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.2/node-v4.4.2.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.2/node-v4.4.2-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.2/node-v4.4.2.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.2/<br>
+Documentation: https://nodejs.org/docs/v4.4.2/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+a143d6c71c9f1d1827d4cde1086611fb41d4909247377b8539a7129e1bf8266b  node-v4.4.2-darwin-x64.tar.gz
+2407261b3829b83b06ad285af1aaa5198b9c69f6efb93ca493ffb42344f219fe  node-v4.4.2-darwin-x64.tar.xz
+6b2ec4064900a8c39357ca7bdd7863587d749dcad1e4735df0de402400142cbb  node-v4.4.2-headers.tar.gz
+8dc001e4b78073c567eb4c345a5d50bb3d9f9dfe6a4b5f99ba4ca9cadd0a7e52  node-v4.4.2-headers.tar.xz
+be881df65ff29ffbec47a14e082800c150d4a9238d1c137ff18cf7c28fafa987  node-v4.4.2-linux-arm64.tar.gz
+a15d77d084b954c96d0fbb12e97afc988bfd1f9c0e386ad52e0805f6422db783  node-v4.4.2-linux-arm64.tar.xz
+c574a381e5955c724bf39ff93814882e8f5218293b8c4210ccfafbda06fc4200  node-v4.4.2-linux-armv6l.tar.gz
+d139f9ba6c18a55a9549b75d5b384ee4a7e7b379bf36e8077d33e27d5ee6e7fd  node-v4.4.2-linux-armv6l.tar.xz
+f243f42bbab4757b3881a26e7ac3af4a1ec6d0f5edc1e4415e69768e94cd1389  node-v4.4.2-linux-armv7l.tar.gz
+03bcb820c7f1fea145675a9b632e35b58211cb3dae202f9347eae007386ca1e7  node-v4.4.2-linux-armv7l.tar.xz
+035d202d02ac965618d99ec5c8680aba1ea41f6114caf720a160fe23405809b5  node-v4.4.2-linux-ppc64le.tar.gz
+cd6e96898fcc1b8e98177d6de3e58904431db5c9ca75a68b08558d5c8f166ab9  node-v4.4.2-linux-ppc64le.tar.xz
+b4a44dbe528520397621aad76168bdfd50cdb96fb1f15e99358263f6400c33d2  node-v4.4.2-linux-x64.tar.gz
+003a8dcb3c267b9f268e9443ee2ae381bceaebee1cb438688cd52122591c9b56  node-v4.4.2-linux-x64.tar.xz
+0c2bdf6fed204c6b9bddd7f839f49010cf9b484986f820e20d4f7abb01d8ee9d  node-v4.4.2-linux-x86.tar.gz
+3787dc1a9dd6f65a32f9cc435c6c7d04bc3580ac03ce38246734bfdcdef94ea9  node-v4.4.2-linux-x86.tar.xz
+5d115f4d561f92c6b26f40e7d0217e99e4255e2051337bca15489c39597d05ba  node-v4.4.2.pkg
+006ef87af910bb5b0d78d65d2b979125a6b1049d56dc26088c9cb9deb6a16986  node-v4.4.2-sunos-x64.tar.gz
+c66c35ea9b3594475eac67b213bb87f3ac867a953b5202c70433bc318de1369d  node-v4.4.2-sunos-x64.tar.xz
+13da507b8ecd88598080c63a63c77efc83e04c8454f4070389c4472d512ced48  node-v4.4.2-sunos-x86.tar.gz
+6e9e382fca253b6032881cad42a7e7380f7efd7a169b4df56aba990613a6404f  node-v4.4.2-sunos-x86.tar.xz
+ae91cb0a31f87b5b13bb2665178845d99abf1037dc3636fa88f442b4a4c65297  node-v4.4.2.tar.gz
+49051fd930e36181509dc8fcf584fc01971083b6bf9e14f2bbec49cc9c4224e9  node-v4.4.2.tar.xz
+70bab3f8412f341d8ed2f2fd98904270aba650262f947084dbc5b1e7e6d98692  node-v4.4.2-x64.msi
+3f16ed3b83d893b8d594e252fbe2512806141d078afd66440afd63cd00f562f8  node-v4.4.2-x86.msi
+133e73a2b7a231e78cfa5802ae301de64e9b1bcfbe7e46e49a930b6b6f08c222  win-x64/node.exe
+c258cd572a3120e940671c4728041bc1e34fe1e2287e73c358dccb41f959191b  win-x64/node.lib
+79f633a85f6c06b923b2283d7f6b8a869d4cf0f66ef95464c19e67d575d204bc  win-x86/node.exe
+b2a4e0057b5bca1a5b089d1faa92f23718359442f1bd072dac2c9d7b0bd71199  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJW/dEwAAoJEJM7AfQLXKlGMW8H/Aj8PhN/66SYqG3LH2UCffmh
+rlsc9R265TU5m9WJA6AuXOa5cY5rIdWiucp9wzc5nX/y8imSmy7bCNui2Ar0McDN
+VKIlzcUhsa4TG0b1LihF5NUbNDwpFjandbMVHMPoo4KPYYd5IbxEIDjGj6ysktRl
+D7w/cUXihLTWm8Ucda1IKGBDt28e4zSSz1bYUBPcw0AKc9KJzTWth0ikqRWLNxXB
+aSJWflrDatBvghtTOtXNrGmnlcn2dLDOD44a9gqTkFBdQg1CfHchFCHpG7+TIAHZ
+kUMFGcEvH3tj27YFn7iyfUIlGUezwI+fuS52HN6BU3alO0JWCmQmGNr/Z6uL4Ew=
+=+gcT
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.3.md b/locale/uk/blog/release/v4.4.3.md
new file mode 100755
index 0000000000000..37ea980d10132
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.3.md
@@ -0,0 +1,140 @@
+---
+date: 2016-04-12T22:08:19.877Z
+version: 4.4.3
+category: release
+title: Node v4.4.3 (LTS)
+slug: node-v4-4-3
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable Changes
+
+* **deps**:
+  - Fix `--gdbjit` for embedders. Backported from v8 upstream. (Ben Noordhuis) [#5577](https://github.com/nodejs/node/pull/5577)
+* **etw**:
+  - Correctly display descriptors for ETW events 9 and 23 on the windows platform. (João Reis) [#5742](https://github.com/nodejs/node/pull/5742)
+* **querystring**:
+  - Restore throw when attempting to stringify bad surrogate pair. (Brian White) [#5858](https://github.com/nodejs/node/pull/5858)
+
+### Commits
+
+* [[`f949c273cd`](https://github.com/nodejs/node/commit/f949c273cd)] - **assert**: Check typed array view type in deepEqual (Anna Henningsen) [#5910](https://github.com/nodejs/node/pull/5910)
+* [[`132acea0d4`](https://github.com/nodejs/node/commit/132acea0d4)] - **build**: introduce ci targets for lint/benchmark (Johan Bergström) [#5921](https://github.com/nodejs/node/pull/5921)
+* [[`9a8f922dee`](https://github.com/nodejs/node/commit/9a8f922dee)] - **build**: add missing `openssl_fips%` to common.gypi (Fedor Indutny) [#5919](https://github.com/nodejs/node/pull/5919)
+* [[`d275cdf202`](https://github.com/nodejs/node/commit/d275cdf202)] - **child_process**: refactor self=this in socket_list (Benjamin Gruenbaum) [#5860](https://github.com/nodejs/node/pull/5860)
+* [[`aadf356aa2`](https://github.com/nodejs/node/commit/aadf356aa2)] - **deps**: backport 8d00c2c from v8 upstream (Ben Noordhuis) [#5577](https://github.com/nodejs/node/pull/5577)
+* [[`200f763c43`](https://github.com/nodejs/node/commit/200f763c43)] - **deps**: completely upgrade npm in LTS to 2.15.1 (Forrest L Norvell) [#5989](https://github.com/nodejs/node/pull/5989)
+* [[`86e3903626`](https://github.com/nodejs/node/commit/86e3903626)] - **dns**: Use object without protoype for map (Benjamin Gruenbaum) [#5843](https://github.com/nodejs/node/pull/5843)
+* [[`9a33f43f73`](https://github.com/nodejs/node/commit/9a33f43f73)] - **doc**: update openssl LICENSE using license-builder.sh (Steven R. Loomis) [#6065](https://github.com/nodejs/node/pull/6065)
+* [[`9679e2dc70`](https://github.com/nodejs/node/commit/9679e2dc70)] - **doc**: clarify that __dirname is module local (James M Snell) [#6018](https://github.com/nodejs/node/pull/6018)
+* [[`86d2af58d6`](https://github.com/nodejs/node/commit/86d2af58d6)] - **doc**: simple doc typo fix (Brendon Pierson) [#6041](https://github.com/nodejs/node/pull/6041)
+* [[`f16802f3ca`](https://github.com/nodejs/node/commit/f16802f3ca)] - **doc**: note about Android support (Rich Trott) [#6040](https://github.com/nodejs/node/pull/6040)
+* [[`8c2befe176`](https://github.com/nodejs/node/commit/8c2befe176)] - **doc**: note assert.throws() pitfall (Rich Trott) [#6029](https://github.com/nodejs/node/pull/6029)
+* [[`0870ac65f2`](https://github.com/nodejs/node/commit/0870ac65f2)] - **doc**: use HTTPS for links where possible (Rich Trott) [#6019](https://github.com/nodejs/node/pull/6019)
+* [[`56755de96e`](https://github.com/nodejs/node/commit/56755de96e)] - **doc**: clarify stdout/stderr arguments to callback (James M Snell) [#6015](https://github.com/nodejs/node/pull/6015)
+* [[`bb603b89a2`](https://github.com/nodejs/node/commit/bb603b89a2)] - **doc**: add 'Command Line Options' to 'View on single page' (firedfox) [#6011](https://github.com/nodejs/node/pull/6011)
+* [[`c91f3d897a`](https://github.com/nodejs/node/commit/c91f3d897a)] - **doc**: add copy about how to curl SHA256.txt (Myles Borins) [#6120](https://github.com/nodejs/node/pull/6120)
+* [[`f9cf232284`](https://github.com/nodejs/node/commit/f9cf232284)] - **doc**: add example using algorithms not directly exposed (Brad Hill) [#6108](https://github.com/nodejs/node/pull/6108)
+* [[`f60ce1078d`](https://github.com/nodejs/node/commit/f60ce1078d)] - **doc**: document unspecified behavior for buf.write* methods (James M Snell) [#5925](https://github.com/nodejs/node/pull/5925)
+* [[`02401a6cbd`](https://github.com/nodejs/node/commit/02401a6cbd)] - **doc**: fix scrolling on iOS devices (Luigi Pinca) [#5878](https://github.com/nodejs/node/pull/5878)
+* [[`aed22d0855`](https://github.com/nodejs/node/commit/aed22d0855)] - **doc**: path.format provide more examples (John Eversole) [#5838](https://github.com/nodejs/node/pull/5838)
+* [[`6e2bfbe1fd`](https://github.com/nodejs/node/commit/6e2bfbe1fd)] - **doc**: fix doc for Buffer.readInt32LE() (ghaiklor) [#5890](https://github.com/nodejs/node/pull/5890)
+* [[`940d204401`](https://github.com/nodejs/node/commit/940d204401)] - **doc**: consolidate timers docs in timers.markdown (Bryan English) [#5837](https://github.com/nodejs/node/pull/5837)
+* [[`505faf6360`](https://github.com/nodejs/node/commit/505faf6360)] - **doc**: refine child_process detach behaviour (Robert Jefe Lindstaedt) [#5330](https://github.com/nodejs/node/pull/5330)
+* [[`feedca7879`](https://github.com/nodejs/node/commit/feedca7879)] - **doc**: add topic - event loop, timers, `nextTick()` (Jeff Harris) [#4936](https://github.com/nodejs/node/pull/4936)
+* [[`6d3822c12b`](https://github.com/nodejs/node/commit/6d3822c12b)] - **etw**: fix descriptors of events 9 and 23 (João Reis) [#5742](https://github.com/nodejs/node/pull/5742)
+* [[`56dda6f336`](https://github.com/nodejs/node/commit/56dda6f336)] - **fs**: Remove unused branches (Benjamin Gruenbaum) [#5289](https://github.com/nodejs/node/pull/5289)
+* [[`dfe9e157c1`](https://github.com/nodejs/node/commit/dfe9e157c1)] - **governance**: remove target size for CTC (Rich Trott) [#5879](https://github.com/nodejs/node/pull/5879)
+* [[`c4103b154f`](https://github.com/nodejs/node/commit/c4103b154f)] - **lib**: refactor code with startsWith/endsWith (Jackson Tian) [#5753](https://github.com/nodejs/node/pull/5753)
+* [[`16216a81de`](https://github.com/nodejs/node/commit/16216a81de)] - **meta**: add "joining a wg" section to WORKING_GROUPS.md (Matteo Collina) [#5488](https://github.com/nodejs/node/pull/5488)
+* [[`65fc4e36ce`](https://github.com/nodejs/node/commit/65fc4e36ce)] - **querystring**: don't stringify bad surrogate pair (Brian White) [#5858](https://github.com/nodejs/node/pull/5858)
+* [[`4f683ab912`](https://github.com/nodejs/node/commit/4f683ab912)] - **src,tools**: use template literals (Rich Trott) [#5778](https://github.com/nodejs/node/pull/5778)
+* [[`ac40a4510d`](https://github.com/nodejs/node/commit/ac40a4510d)] - **test**: explicitly set global in test-repl (Rich Trott) [#6026](https://github.com/nodejs/node/pull/6026)
+* [[`a7b3a7533a`](https://github.com/nodejs/node/commit/a7b3a7533a)] - **test**: be explicit about polluting of `global` (Rich Trott) [#6017](https://github.com/nodejs/node/pull/6017)
+* [[`73e3b7b9a8`](https://github.com/nodejs/node/commit/73e3b7b9a8)] - **test**: make use of globals explicit (Rich Trott) [#6014](https://github.com/nodejs/node/pull/6014)
+* [[`e7877e61b6`](https://github.com/nodejs/node/commit/e7877e61b6)] - **test**: fix flaky test-net-socket-timeout-unref (Rich Trott) [#6003](https://github.com/nodejs/node/pull/6003)
+* [[`a39051f5b3`](https://github.com/nodejs/node/commit/a39051f5b3)] - **test**: make arch available in status files (Santiago Gimeno) [#5997](https://github.com/nodejs/node/pull/5997)
+* [[`ccf90b651a`](https://github.com/nodejs/node/commit/ccf90b651a)] - **test**: fix test-dns.js flakiness (Rich Trott) [#5996](https://github.com/nodejs/node/pull/5996)
+* [[`1994ac0912`](https://github.com/nodejs/node/commit/1994ac0912)] - **test**: add test for piping large input from stdin (Anna Henningsen) [#5949](https://github.com/nodejs/node/pull/5949)
+* [[`cc1aab9f6a`](https://github.com/nodejs/node/commit/cc1aab9f6a)] - **test**: mitigate flaky test-https-agent (Rich Trott) [#5939](https://github.com/nodejs/node/pull/5939)
+* [[`10fe79b809`](https://github.com/nodejs/node/commit/10fe79b809)] - **test**: fix offending max-len linter error (Sakthipriyan Vairamani) [#5980](https://github.com/nodejs/node/pull/5980)
+* [[`63d82960fd`](https://github.com/nodejs/node/commit/63d82960fd)] - **test**: stdin is not always a net.Socket (Jeremiah Senkpiel) [#5935](https://github.com/nodejs/node/pull/5935)
+* [[`fe0233b923`](https://github.com/nodejs/node/commit/fe0233b923)] - **test**: add known_issues test for GH-2148 (Rich Trott) [#5920](https://github.com/nodejs/node/pull/5920)
+* [[`d59be4d248`](https://github.com/nodejs/node/commit/d59be4d248)] - **test**: ensure _handle property existence (Rich Trott) [#5916](https://github.com/nodejs/node/pull/5916)
+* [[`9702153107`](https://github.com/nodejs/node/commit/9702153107)] - **test**: fix flaky test-repl (Brian White) [#5914](https://github.com/nodejs/node/pull/5914)
+* [[`a0a2e69097`](https://github.com/nodejs/node/commit/a0a2e69097)] - **test**: move dns test to test/internet (Ben Noordhuis) [#5905](https://github.com/nodejs/node/pull/5905)
+* [[`8462d8f465`](https://github.com/nodejs/node/commit/8462d8f465)] - **test**: fix flaky test-net-socket-timeout (Brian White) [#5902](https://github.com/nodejs/node/pull/5902)
+* [[`e0b283af73`](https://github.com/nodejs/node/commit/e0b283af73)] - **test**: fix flaky test-http-set-timeout (Rich Trott) [#5856](https://github.com/nodejs/node/pull/5856)
+* [[`5853fec36f`](https://github.com/nodejs/node/commit/5853fec36f)] - **test**: fix test-debugger-client.js (Rich Trott) [#5851](https://github.com/nodejs/node/pull/5851)
+* [[`ea83c382f9`](https://github.com/nodejs/node/commit/ea83c382f9)] - **test**: ensure win32.isAbsolute() is consistent (Brian White) [#6043](https://github.com/nodejs/node/pull/6043)
+* [[`c33a23fd1e`](https://github.com/nodejs/node/commit/c33a23fd1e)] - **tools**: fix json doc generation (firedfox) [#5943](https://github.com/nodejs/node/pull/5943)
+* [[`6f0bd64122`](https://github.com/nodejs/node/commit/6f0bd64122)] - **tools,doc**: fix incomplete json produced by doctool (firedfox) [#5966](https://github.com/nodejs/node/pull/5966)
+* [[`f7eb48302c`](https://github.com/nodejs/node/commit/f7eb48302c)] - **win,build**: build and test add-ons on test-ci (Bogdan Lobor) [#5886](https://github.com/nodejs/node/pull/5886)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.3/node-v4.4.3-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.3/node-v4.4.3-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.3/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.3/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.3/node-v4.4.3.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.3/node-v4.4.3.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.3/<br>
+Documentation: https://nodejs.org/docs/v4.4.3/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+7cbb9819926d90c9c9f31c3db4c83499a3d9518ad3c7d9915fa4c66d6d5875df  node-v4.4.3-darwin-x64.tar.gz
+9aabc5221d664ff6030abbbd8c94c74c1579cfd91cc39f82508a1da4cff2c42d  node-v4.4.3-darwin-x64.tar.xz
+e24fb3eb7c7fe4c5b1ac64a93b63cfc109d56b59bedf2e88a2001f7ce3b1673c  node-v4.4.3-headers.tar.gz
+286a884fe4ff5601afcd1352257b6133cf04304859e126cac533c9f1662af38c  node-v4.4.3-headers.tar.xz
+261646b9d606ab3cc42f870d4bcaab79a40f18f7b13740762127598ef29d4ffc  node-v4.4.3-linux-arm64.tar.gz
+fe65d3992219389cd965cee015571b222948ce46c676e5e0224450439fa26637  node-v4.4.3-linux-arm64.tar.xz
+04d8abedf4199d1ca9b963d18458eb9e99f80cc5663e6f61041735dc28c9eb5f  node-v4.4.3-linux-armv6l.tar.gz
+b570ba9a8dcb287fa833c0d0dd05f3ad008853a4a445805ef1e17e2ce7c01d03  node-v4.4.3-linux-armv6l.tar.xz
+b1cd7144bea5564ae8ca0f653f1e1daf45c63e2a0d0e5c391519aaf7167dbd9e  node-v4.4.3-linux-armv7l.tar.gz
+437716a5a9e751196eb25486fc486786a431fe3a632c61728949f4628ccbe83d  node-v4.4.3-linux-armv7l.tar.xz
+dd9d9f8a25b1ba67c73af4724ca1abe4e0661d3ffac3d48e57ef3480c8f3cb2a  node-v4.4.3-linux-ppc64le.tar.gz
+20af624f1ef5214f34ad5e7fab3cf11cb9bbadce4efeae727602eae03fb037bd  node-v4.4.3-linux-ppc64le.tar.xz
+28ff2b23a837526ecfea66b0db42d43ec84368949998f2cb26dd742e8988ec1f  node-v4.4.3-linux-x64.tar.gz
+7d8919fa7c6fa927c0fe295fcb16c7025c974b717350e97ddbd7a46d3b60fbef  node-v4.4.3-linux-x64.tar.xz
+ffdbb81573d77a2bf14415fc1c0d65b110cfc2ba5a20dcdf8b62015519acd079  node-v4.4.3-linux-x86.tar.gz
+93bcf48a9e5c6fdcd030ccfa0bde626466daaf0d8924a98f235e89f517addb76  node-v4.4.3-linux-x86.tar.xz
+2e7cfa53c916524add24d7407572ede6d199a0a7b539ba6da67fd5a97c7ebab2  node-v4.4.3.pkg
+72ceeafe74e911a418baa5c73cdb2888105c85d62f15245d55009f0e93da543a  node-v4.4.3-sunos-x64.tar.gz
+24ab0b4363718b3062b5a1aeb6ce5c41d6444eb5315a8e97be7982cb3ee8049f  node-v4.4.3-sunos-x64.tar.xz
+182963950c657aeecb18494c4d3765bcf51970aca938dd4848cf6942382fc730  node-v4.4.3-sunos-x86.tar.gz
+4ad7229ca766aa80c412d69d1968a41172090698547829e3f34bcd3e9bd86fa6  node-v4.4.3-sunos-x86.tar.xz
+8e67b95721aab7bd721179da2fe5dd97f9acc1306c15c9712ee103bcd6381638  node-v4.4.3.tar.gz
+57499bb0b1b86080459d4066e3c138579a278b2d0b1f5b2f19e66c69b4e8433c  node-v4.4.3.tar.xz
+388197c171805d97746d29b64d1e98c87dca378e70d5e947875327772bb2d560  node-v4.4.3-x64.msi
+1ea07653ae47f71201c9ea0691fdfe4384416666ea70f725030f3b0140d729ca  node-v4.4.3-x86.msi
+484b02a6559d6938ee90ac7f86e8b46b22025f3900c8677162af1f381c48c554  win-x64/node.exe
+050a3d2743ea783ee63846872e5922f2afeeef0aa576994deafcf25565090b26  win-x64/node.lib
+50ceedced779dd320da68e54ca403e9094c0f264cb3ba818cde1bf46ace415b3  win-x86/node.exe
+0393695ea383baf27dee1feabd288b2162ed9354ebf5fe6e89ef6bc3f8333d04  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJXDXGUAAoJEJM7AfQLXKlGIwUIALrSiVgRpJI8k93c3ZsAfiPq
+h8Q2JSKlk5vvCu/e2GttxaSlwUY6GBCpOyrsD1zEny+9ni37eOKph/T64MVr4rwt
+ZXNDOTuz+6/dAUUmPpnkVtJD9c0sWiDXM6PrLjAKnTuL2v8qqrtetKnUaVVtzMB8
+DE2bRpWGII/ULOKIAl7Er+G2J5Il5m1sMUnTHxMjrWyauj3kclehmStPSmXgTDjZ
+Lmm6BHIEQbm4qESJNsJJ+hhmdblcdMyfXH+vKxtT01XL9zTFzfXuDr8Awj+BHpfC
+A5B5lcCTgXo5meJyFisu7MA6zqt9Y7pajr0ecv1JqffwiFURWJUAva2suJ/xMH8=
+=OM4J
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.4.md b/locale/uk/blog/release/v4.4.4.md
new file mode 100755
index 0000000000000..764012e455552
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.4.md
@@ -0,0 +1,94 @@
+---
+date: 2016-05-06T14:50:41.800Z
+version: 4.4.4
+category: release
+title: Node v4.4.4 (LTS)
+slug: node-v4-4-4
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+* **deps**:
+  * update openssl to 1.0.2h. (Shigeki Ohtsu) [#6551](https://github.com/nodejs/node/pull/6551)
+    - Please see our [blog post](https://nodejs.org/en/blog/vulnerability/openssl-may-2016/) for more info on the security contents of this release.
+
+### Commits
+
+* [[`f46952e727`](https://github.com/nodejs/node/commit/f46952e727)] - **buffer**: safeguard against accidental kNoZeroFill (Сковорода Никита Андреевич) [nodejs/node-private#30](https://github.com/nodejs/node-private/pull/30)
+* [[`4f1c82f995`](https://github.com/nodejs/node/commit/4f1c82f995)] - **streams**: support unlimited synchronous cork/uncork cycles (Matteo Collina) [#6164](https://github.com/nodejs/node/pull/6164)
+* [[`1efd96c767`](https://github.com/nodejs/node/commit/1efd96c767)] - **deps**: update openssl asm and asm_obsolete files (Shigeki Ohtsu) [#6551](https://github.com/nodejs/node/pull/6551)
+* [[`c450f4a293`](https://github.com/nodejs/node/commit/c450f4a293)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [nodejs/io.js#1836](https://github.com/nodejs/io.js/pull/1836)
+* [[`baedfbae6a`](https://github.com/nodejs/node/commit/baedfbae6a)] - **openssl**: fix keypress requirement in apps on win32 (Shigeki Ohtsu) [iojs/io.js#1389](https://github.com/iojs/io.js/pull/1389)
+* [[`ff3045e40b`](https://github.com/nodejs/node/commit/ff3045e40b)] - **deps**: fix asm build error of openssl in x86_win32 (Shigeki Ohtsu) [iojs/io.js#1389](https://github.com/iojs/io.js/pull/1389)
+* [[`dc8dc97db3`](https://github.com/nodejs/node/commit/dc8dc97db3)] - **deps**: fix openssl assembly error on ia32 win32 (Fedor Indutny) [iojs/io.js#1389](https://github.com/iojs/io.js/pull/1389)
+* [[`2dfeb01213`](https://github.com/nodejs/node/commit/2dfeb01213)] - **deps**: copy all openssl header files to include dir (Shigeki Ohtsu) [#6551](https://github.com/nodejs/node/pull/6551)
+* [[`72f9952516`](https://github.com/nodejs/node/commit/72f9952516)] - **deps**: upgrade openssl sources to 1.0.2h (Shigeki Ohtsu) [#6551](https://github.com/nodejs/node/pull/6551)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.4/node-v4.4.4-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.4/node-v4.4.4-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.4/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.4/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.4/node-v4.4.4.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.4/node-v4.4.4-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.4/node-v4.4.4.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.4/<br>
+Documentation: https://nodejs.org/docs/v4.4.4/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+3d240db764391faca06df67db1eefd0b20989153edb0a99cbaf16e441e734a4d  node-v4.4.4-darwin-x64.tar.gz
+e6a521781d212a760ef63ca139a12a86b8a312f730abc8deb0d8fa8f18d9f357  node-v4.4.4-darwin-x64.tar.xz
+a5abc953d1ee4295cd3dcfdc116797e4b807e0b2d5c888aa31631fa1de9a9200  node-v4.4.4-headers.tar.gz
+7a3521608274a32b5e609bf76581d6cec838ec369f1b346f73aca58588515fb0  node-v4.4.4-headers.tar.xz
+4d7336411a61e92eb4815dc5b9042cae92ed49d3bc472da153aa13fd4e812b99  node-v4.4.4-linux-arm64.tar.gz
+e50d47bdd5fe26a249449059244222e06f98513209027bf557bf809e24e17400  node-v4.4.4-linux-arm64.tar.xz
+618efa1636db2d8acd7f28902200cbb42fd0f1d71ef482b6e99a027372584581  node-v4.4.4-linux-armv6l.tar.gz
+c1a67dc4c7080b4082d165861d44a1f3279adec18279edc927329d153ab5b657  node-v4.4.4-linux-armv6l.tar.xz
+64af655f048fc1ba70591076bbdeb61195347942ceef1ea18157467e5a01f253  node-v4.4.4-linux-armv7l.tar.gz
+9df9d2bb7335a3118ed20a8332df40659294bfe04896c49d7e4890d7f667c495  node-v4.4.4-linux-armv7l.tar.xz
+939cead87316367dd88430807ad335b9bdab4812fe0cd18adf62887c699dd4e7  node-v4.4.4-linux-ppc64le.tar.gz
+23cedc2304c1709450689e5a3afe01b749dcb7a5b4f817bf59e97a64b22b60b3  node-v4.4.4-linux-ppc64le.tar.xz
+0881eb010c8a4a0e746a1852fe48416d9c21b5f19a20d418cb02c7197fa55576  node-v4.4.4-linux-x64.tar.gz
+c8b4e3c6e07e51593dddbf1d2ec3cf0ec09d5c6b8c5258b37b3816cc6b7e9fe3  node-v4.4.4-linux-x64.tar.xz
+401fcef7908b3620bd28300bac06ad4fe774c95e10167c8617dde18befd78fcd  node-v4.4.4-linux-x86.tar.gz
+7c0771b0153dd1c6609197b7b56840085df5d0752862fe4e98569d8d7bcb8682  node-v4.4.4-linux-x86.tar.xz
+0e26458c8490af8f7d1aa4db8ca2792e2089fc0065517225cb30d4f22778b288  node-v4.4.4.pkg
+5748ececfb65a5dfa5c7eb87c31e890aff7a32aeea6ae440e382eca34ec16eba  node-v4.4.4-sunos-x64.tar.gz
+a2aea1b73dc559db924b4a00884f1ae26c5bea84956e506c7a1b7fbe04b36f5a  node-v4.4.4-sunos-x64.tar.xz
+1da8b38983ba9fd8878c2127225396991c8189934e578760f0860ed15302cdd6  node-v4.4.4-sunos-x86.tar.gz
+b542392497c7bd03d83cba378f0056b9d1e2c2feb71ba64196ab64a2a8ae67ba  node-v4.4.4-sunos-x86.tar.xz
+53c694c203ee18e7cd393612be08c61ed6ab8b2a165260984a99c014d1741414  node-v4.4.4.tar.gz
+2c9cedc401145a6648877ebd3fa9090c874dfced8bf7a6e7d9d8e9c21827b114  node-v4.4.4.tar.xz
+3bfa87c9feb0107800740fd0a7f950b9259ba73a353274ba60a91d7b4a5279c5  node-v4.4.4-x64.msi
+2198827fcc8ee3df77ec7551107409cf2eea02cdd98fed3388242e9f493d8467  node-v4.4.4-x86.msi
+7b9884e09881ab6e3ef942f641e766c74ec33dac20c08914aa8778508d4c116b  win-x64/node.exe
+a1736c89bf3510dab521fac288228ab3464eca1ee2d5449ff60de2ca6d17a38f  win-x64/node.lib
+02565551c3645760e6c466190a94badf8755f4ad789e61e8e40f40c3483590fc  win-x86/node.exe
+77bf8aa73cdf0d45b99a7844842e58ca6c4756531e759ea6581d92be8371c139  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJXLK8GAAoJEJM7AfQLXKlGVKUH/jYIvgLWqaQmpYJbgAupUmuo
+Av7DB+iKGWFK0Tn2vmeQsWAK7XzIaXHFimldQ8x6lwt5hjH5L4MjA8wQ6zblgT7S
+FK/VHWBHd+7T8eTE6D+42g7Umo4lL2D8PbB/ePKuDYYNtzFqllE0ThX+IkNnMRJs
+X8xqmzXa7EvEQMiOGzQF0B2gWqovW6m7d0Skm72szT0ldayUUBwQ9z1zE1RVGmlc
+lNMAMinZhOdbtCQChOTYRu6dhjdf/MOwHMMrG2AHiasjgKvrMjHBx9kbP/DOrtM4
+zIarizzJGPoTU0JEb63JE5OmeR5q1vhblnT/tTo0VB1oeaC7T72vZqxvvyYvekU=
+=RKEg
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.5.md b/locale/uk/blog/release/v4.4.5.md
new file mode 100755
index 0000000000000..4310b56df2ef9
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.5.md
@@ -0,0 +1,167 @@
+---
+date: 2016-05-24T18:44:10.363Z
+version: 4.4.5
+category: release
+title: Node v4.4.5 (LTS)
+slug: node-v4-4-5
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable Changes
+
+* **buffer**:
+  * Buffer no longer errors if you call lastIndexOf with a search term longer than the buffer (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* **contextify**:
+  * Context objects are now properly garbage collected, this solves a problem some individuals were experiencing with extreme memory growth (Ali Ijaz Sheikh) [#6871](https://github.com/nodejs/node/pull/6871)
+* **deps**:
+  * update npm to 2.15.5 (Rebecca Turner) [#6663](https://github.com/nodejs/node/pull/6663)
+* **http**:
+  * Invalid status codes can no longer be sent. Limited to 3 digit numbers between 100 - 999 (Brian White) [#6291](https://github.com/nodejs/node/pull/6291)
+
+### Commits
+
+* [[`59a977dd22`](https://github.com/nodejs/node/commit/59a977dd22)] - **assert**: respect assert.doesNotThrow message. (Ilya Shaisultanov) [#2407](https://github.com/nodejs/node/pull/2407)
+* [[`8b077faa82`](https://github.com/nodejs/node/commit/8b077faa82)] - **buffer**: fix UCS2 indexOf for odd buffer length (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`12a9699fcf`](https://github.com/nodejs/node/commit/12a9699fcf)] - **buffer**: fix needle length misestimation for UCS2 (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`292b1b733e`](https://github.com/nodejs/node/commit/292b1b733e)] - **build**: fix make tar-headers for Linux (Gibson Fahnestock) [#5978](https://github.com/nodejs/node/pull/5978)
+* [[`918d33ad4b`](https://github.com/nodejs/node/commit/918d33ad4b)] - **build**: add script to create Android .mk files (Robert Chiras) [#5544](https://github.com/nodejs/node/pull/5544)
+* [[`4ad71847bc`](https://github.com/nodejs/node/commit/4ad71847bc)] - **build**: add suport for x86 architecture (Robert Chiras) [#5544](https://github.com/nodejs/node/pull/5544)
+* [[`6ad85914b1`](https://github.com/nodejs/node/commit/6ad85914b1)] - **child_process**: add nullptr checks after allocs (Anna Henningsen) [#6256](https://github.com/nodejs/node/pull/6256)
+* [[`823f726f66`](https://github.com/nodejs/node/commit/823f726f66)] - **contextify**: tie lifetimes of context & sandbox (Ali Ijaz Sheikh) [#5800](https://github.com/nodejs/node/pull/5800)
+* [[`9ddb44ba61`](https://github.com/nodejs/node/commit/9ddb44ba61)] - **contextify**: cache sandbox and context in locals (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`8ebdcd65b0`](https://github.com/nodejs/node/commit/8ebdcd65b0)] - **contextify**: replace deprecated SetWeak usage (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`9e6d8170f7`](https://github.com/nodejs/node/commit/9e6d8170f7)] - **contextify**: cleanup weak ref for sandbox (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`b6fc15347d`](https://github.com/nodejs/node/commit/b6fc15347d)] - **contextify**: cleanup weak ref for global proxy (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`0dc875e2c7`](https://github.com/nodejs/node/commit/0dc875e2c7)] - **deps**: upgrade npm in LTS to 2.15.5 (Rebecca Turner)
+* [[`3c50350f41`](https://github.com/nodejs/node/commit/3c50350f41)] - **deps**: fix null pointer checks in v8 (Michaël Zasso) [#6669](https://github.com/nodejs/node/pull/6669)
+* [[`a40730b4b4`](https://github.com/nodejs/node/commit/a40730b4b4)] - **deps**: backport IsValid changes from 4e8736d in V8 (Michaël Zasso) [#6669](https://github.com/nodejs/node/pull/6669)
+* [[`855604c53a`](https://github.com/nodejs/node/commit/855604c53a)] - **deps**: upgrade npm in LTS to 2.15.4 (Rebecca Turner) [#6663](https://github.com/nodejs/node/pull/6663)
+* [[`433fb9a968`](https://github.com/nodejs/node/commit/433fb9a968)] - **deps**: cherry-pick 1383d00 from v8 upstream (Fedor Indutny) [#6179](https://github.com/nodejs/node/pull/6179)
+* [[`d1fca27ef8`](https://github.com/nodejs/node/commit/d1fca27ef8)] - **deps**: backport 125ac66 from v8 upstream (Myles Borins) [#6086](https://github.com/nodejs/node/pull/6086)
+* [[`df299019a0`](https://github.com/nodejs/node/commit/df299019a0)] - **deps**: upgrade npm in LTS to 2.15.2 (Kat Marchán)
+* [[`50f02bd8d6`](https://github.com/nodejs/node/commit/50f02bd8d6)] - **doc**: update vm.runInDebugContext() example (Ben Noordhuis) [#6757](https://github.com/nodejs/node/pull/6757)
+* [[`b872feade3`](https://github.com/nodejs/node/commit/b872feade3)] - **doc**: replace functions with arrow functions (abouthiroppy) [#6203](https://github.com/nodejs/node/pull/6203)
+* [[`7160229be4`](https://github.com/nodejs/node/commit/7160229be4)] - **doc**: note that zlib.flush acts after pending writes (Anna Henningsen) [#6172](https://github.com/nodejs/node/pull/6172)
+* [[`d069f2de8c`](https://github.com/nodejs/node/commit/d069f2de8c)] - **doc**: add full example for zlib.flush() (Anna Henningsen) [#6172](https://github.com/nodejs/node/pull/6172)
+* [[`59814acfef`](https://github.com/nodejs/node/commit/59814acfef)] - **doc**: describe child.kill() pitfalls on linux (Robert Jefe Lindstaedt) [#2098](https://github.com/nodejs/node/issues/2098)
+* [[`840c09492d`](https://github.com/nodejs/node/commit/840c09492d)] - **doc**: update openssl.org hash links (silverwind) [#6817](https://github.com/nodejs/node/pull/6817)
+* [[`126fdc3171`](https://github.com/nodejs/node/commit/126fdc3171)] - **doc**: fix issues related to page scrolling (Roman Reiss)
+* [[`29e25d8489`](https://github.com/nodejs/node/commit/29e25d8489)] - **doc**: add steps for running addons + npm tests (Myles Borins) [#6231](https://github.com/nodejs/node/pull/6231)
+* [[`fcc6a347f7`](https://github.com/nodejs/node/commit/fcc6a347f7)] - **doc**: get rid of sneaky hard tabs in CHANGELOG (Myles Borins) [#6608](https://github.com/nodejs/node/pull/6608)
+* [[`369569018e`](https://github.com/nodejs/node/commit/369569018e)] - **doc**: revert backported commits (Myles Borins) [#6530](https://github.com/nodejs/node/pull/6530)
+* [[`4ec9ae8a1c`](https://github.com/nodejs/node/commit/4ec9ae8a1c)] - **doc**: explain differences in console.assert between node and browsers (James M Snell) [#6169](https://github.com/nodejs/node/pull/6169)
+* [[`df5ce6fad4`](https://github.com/nodejs/node/commit/df5ce6fad4)] - **doc**: native module reloading is not supported (Bryan English) [#6168](https://github.com/nodejs/node/pull/6168)
+* [[`30f354f72b`](https://github.com/nodejs/node/commit/30f354f72b)] - **doc**: clarify fs.watch() and inodes on linux, os x (Joran Dirk Greef) [#6099](https://github.com/nodejs/node/pull/6099)
+* [[`29f821b73d`](https://github.com/nodejs/node/commit/29f821b73d)] - **doc**: clarifies http.serverResponse implementation (Allen Hernandez) [#6072](https://github.com/nodejs/node/pull/6072)
+* [[`6d560094f4`](https://github.com/nodejs/node/commit/6d560094f4)] - **doc**: minor argument formatting in stream.markdown (James M Snell) [#6016](https://github.com/nodejs/node/pull/6016)
+* [[`6a197ec617`](https://github.com/nodejs/node/commit/6a197ec617)] - **doc**: fix http response event, Agent#getName (Matthew Douglass) [#5993](https://github.com/nodejs/node/pull/5993)
+* [[`620a261240`](https://github.com/nodejs/node/commit/620a261240)] - **http**: disallow sending obviously invalid status codes (Brian White) [#6291](https://github.com/nodejs/node/pull/6291)
+* [[`9a8b53124d`](https://github.com/nodejs/node/commit/9a8b53124d)] - **http**: unref socket timer on parser execute (Fedor Indutny) [#6286](https://github.com/nodejs/node/pull/6286)
+* [[`b28e44deb2`](https://github.com/nodejs/node/commit/b28e44deb2)] - **http**: Corrects IPv6 address in Host header (Mihai Potra) [#5314](https://github.com/nodejs/node/pull/5314)
+* [[`2fac15ba94`](https://github.com/nodejs/node/commit/2fac15ba94)] - **src**: fix FindFirstCharacter argument alignment (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`2942cff069`](https://github.com/nodejs/node/commit/2942cff069)] - **src**: add missing 'inline' keywords (Ben Noordhuis) [#6056](https://github.com/nodejs/node/pull/6056)
+* [[`e0eebf412e`](https://github.com/nodejs/node/commit/e0eebf412e)] - **src,tools**: remove null sentinel from source array (Ben Noordhuis) [#5418](https://github.com/nodejs/node/pull/5418)
+* [[`8f18414cd5`](https://github.com/nodejs/node/commit/8f18414cd5)] - **src,tools**: drop nul byte from built-in source code (Ben Noordhuis) [#5418](https://github.com/nodejs/node/pull/5418)
+* [[`d7a3ea457b`](https://github.com/nodejs/node/commit/d7a3ea457b)] - **src,tools**: allow utf-8 in built-in js source code (Ben Noordhuis) [#5418](https://github.com/nodejs/node/pull/5418)
+* [[`51c0808b55`](https://github.com/nodejs/node/commit/51c0808b55)] - **stream**: Fix readableState.awaitDrain mechanism (Anna Henningsen) [#6023](https://github.com/nodejs/node/pull/6023)
+* [[`49a5941d30`](https://github.com/nodejs/node/commit/49a5941d30)] - **test**: fix test-debug-port-cluster flakiness (Rich Trott) [#6769](https://github.com/nodejs/node/pull/6769)
+* [[`f8144e4c4a`](https://github.com/nodejs/node/commit/f8144e4c4a)] - **test**: add logging for test-debug-port-cluster (Rich Trott) [#6769](https://github.com/nodejs/node/pull/6769)
+* [[`773ea20d0e`](https://github.com/nodejs/node/commit/773ea20d0e)] - **test**: include component in tap output (Ben Noordhuis) [#6653](https://github.com/nodejs/node/pull/6653)
+* [[`333369e1ff`](https://github.com/nodejs/node/commit/333369e1ff)] - **test**: increase the platform timeout for AIX (Michael Dawson) [#6342](https://github.com/nodejs/node/pull/6342)
+* [[`06e5fafe84`](https://github.com/nodejs/node/commit/06e5fafe84)] - **test**: add tests for console.assert (Evan Lucas) [#6302](https://github.com/nodejs/node/pull/6302)
+* [[`f60ba54811`](https://github.com/nodejs/node/commit/f60ba54811)] - **test**: add zlib close-after-error regression test (Anna Henningsen) [#6270](https://github.com/nodejs/node/pull/6270)
+* [[`24ac16f4be`](https://github.com/nodejs/node/commit/24ac16f4be)] - **test**: fix flaky test-http-set-timeout-server (Santiago Gimeno) [#6248](https://github.com/nodejs/node/pull/6248)
+* [[`5002a71357`](https://github.com/nodejs/node/commit/5002a71357)] - **test**: assert - fixed error messages to match the tests (surya panikkal) [#6241](https://github.com/nodejs/node/pull/6241)
+* [[`0f9405dd33`](https://github.com/nodejs/node/commit/0f9405dd33)] - **test**: move more tests from sequential to parallel (Santiago Gimeno) [#6187](https://github.com/nodejs/node/pull/6187)
+* [[`37cc249218`](https://github.com/nodejs/node/commit/37cc249218)] - **test**: fix test-net-settimeout flakiness (Santiago Gimeno) [#6166](https://github.com/nodejs/node/pull/6166)
+* [[`69dcbb642f`](https://github.com/nodejs/node/commit/69dcbb642f)] - **test**: fix flaky test-child-process-fork-net (Rich Trott) [#6138](https://github.com/nodejs/node/pull/6138)
+* [[`a97a6a9d69`](https://github.com/nodejs/node/commit/a97a6a9d69)] - **test**: fix issues for ESLint 2.7.0 (silverwind) [#6132](https://github.com/nodejs/node/pull/6132)
+* [[`a865975909`](https://github.com/nodejs/node/commit/a865975909)] - **test**: fix flaky test-http-client-abort (Rich Trott) [#6124](https://github.com/nodejs/node/pull/6124)
+* [[`25d4b5b1e9`](https://github.com/nodejs/node/commit/25d4b5b1e9)] - **test**: move some test from sequential to parallel (Santiago Gimeno) [#6087](https://github.com/nodejs/node/pull/6087)
+* [[`28040ccf49`](https://github.com/nodejs/node/commit/28040ccf49)] - **test**: refactor test-file-write-stream3 (Rich Trott) [#6050](https://github.com/nodejs/node/pull/6050)
+* [[`3a67a05ed4`](https://github.com/nodejs/node/commit/3a67a05ed4)] - **test**: enforce strict mode for test-domain-crypto (Rich Trott) [#6047](https://github.com/nodejs/node/pull/6047)
+* [[`0b376cb3f9`](https://github.com/nodejs/node/commit/0b376cb3f9)] - **test**: fix pummel test failures (Rich Trott) [#6012](https://github.com/nodejs/node/pull/6012)
+* [[`7b60b8f8e9`](https://github.com/nodejs/node/commit/7b60b8f8e9)] - **test**: fix flakiness of stringbytes-external (Ali Ijaz Sheikh) [#6705](https://github.com/nodejs/node/pull/6705)
+* [[`cc4c5187ed`](https://github.com/nodejs/node/commit/cc4c5187ed)] - **test**: ensure test-npm-install uses correct node (Myles Borins) [#6658](https://github.com/nodejs/node/pull/6658)
+* [[`3d4d5777bc`](https://github.com/nodejs/node/commit/3d4d5777bc)] - **test**: refactor http-end-throw-socket-handling (Santiago Gimeno) [#5676](https://github.com/nodejs/node/pull/5676)
+* [[`c76f214b90`](https://github.com/nodejs/node/commit/c76f214b90)] - **test,tools**: enable linting for undefined vars (Rich Trott) [#6255](https://github.com/nodejs/node/pull/6255)
+* [[`9222689215`](https://github.com/nodejs/node/commit/9222689215)] - **test,vm**: enable strict mode for vm tests (Rich Trott) [#6209](https://github.com/nodejs/node/pull/6209)
+* [[`b8c9d6b64e`](https://github.com/nodejs/node/commit/b8c9d6b64e)] - **tools**: enable linting for v8_prof_processor.js (Rich Trott) [#6262](https://github.com/nodejs/node/pull/6262)
+* [[`8fa202947d`](https://github.com/nodejs/node/commit/8fa202947d)] - **tools**: lint rule for assert.fail() (Rich Trott) [#6261](https://github.com/nodejs/node/pull/6261)
+* [[`1aa6c5b7a9`](https://github.com/nodejs/node/commit/1aa6c5b7a9)] - **tools**: update ESLint to 2.7.0 (silverwind) [#6132](https://github.com/nodejs/node/pull/6132)
+* [[`68c7de4372`](https://github.com/nodejs/node/commit/68c7de4372)] - **tools**: remove simplejson dependency (Sakthipriyan Vairamani) [#6101](https://github.com/nodejs/node/pull/6101)
+* [[`4fb4ba98a8`](https://github.com/nodejs/node/commit/4fb4ba98a8)] - **tools**: remove disabling of already-disabled rule (Rich Trott) [#6013](https://github.com/nodejs/node/pull/6013)
+* [[`4e6ea7f01a`](https://github.com/nodejs/node/commit/4e6ea7f01a)] - **tools**: remove obsolete npm test-legacy command (Kat Marchán)
+* [[`4c73ab4302`](https://github.com/nodejs/node/commit/4c73ab4302)] - **tools,doc**: fix json for grouped optional params (firedfox) [#5977](https://github.com/nodejs/node/pull/5977)
+* [[`c893cd33d1`](https://github.com/nodejs/node/commit/c893cd33d1)] - **tools,doc**: parse types in braces everywhere (Alexander Makarenko) [#5329](https://github.com/nodejs/node/pull/5329)
+* [[`48684af55f`](https://github.com/nodejs/node/commit/48684af55f)] - **zlib**: fix use after null when calling .close (James Lal) [#5982](https://github.com/nodejs/node/pull/5982)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.5/node-v4.4.5-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.5/node-v4.4.5-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.5/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.5/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.5/node-v4.4.5.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.5/node-v4.4.5-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.5/node-v4.4.5.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.5/<br>
+Documentation: https://nodejs.org/docs/v4.4.5/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+1e729f9836e7b543724ee0b2ac902b4dff4a6f7d91031d20314825b61e86127f  node-v4.4.5-darwin-x64.tar.gz
+ab00f874cf75d7504cc88bd99cf5f661aa0aa0d33eeecbfd5f8ef69ebc3a3e7f  node-v4.4.5-darwin-x64.tar.xz
+afd90e4b0ae408301facce1d4837c5f718a686d144bf624a53c55988a473601c  node-v4.4.5-headers.tar.gz
+d108e08fd83e5cf4d3a44cc799677ff6276450b5f601181733160358f230a060  node-v4.4.5-headers.tar.xz
+46c89b2cdb3d7f3e87ef1ed8e4d9ee07dcc603e42f3f86f831a6fd7c34be9404  node-v4.4.5-linux-arm64.tar.gz
+83c6a16989489908ea6be93f21a37316b4513d581875c3653ebeadd1c67d2e70  node-v4.4.5-linux-arm64.tar.xz
+8f6a09d7326c4a2570275519ae51bc2a9ba6b2809b5cc02658922368f0dc49b0  node-v4.4.5-linux-armv6l.tar.gz
+ae6a05b4dae19d31d2dd7de07c60ab4672d7aafacd0796974269432e451dd59b  node-v4.4.5-linux-armv6l.tar.xz
+2ce99cbfaef7a8a0e8119a3e1303015f5bed6e745c90a95b3dcd6658ad44035b  node-v4.4.5-linux-armv7l.tar.gz
+07f6610d91e4f03a28a97f1fd54a0b0547545fd5501657e30272a1a97604b709  node-v4.4.5-linux-armv7l.tar.xz
+a2f17bee90c650b30c90c3cd96118e7825eb1b1011c4c7584e60d1b36d9b6983  node-v4.4.5-linux-ppc64le.tar.gz
+d6d6331c1255307dd6cc9cfdba018afa6b35528cd8a293de2d89887b4d378119  node-v4.4.5-linux-ppc64le.tar.xz
+577688263d15b2d7f8004f99151c5d47e27b319510d501792cfd74f7c834caa4  node-v4.4.5-linux-ppc64.tar.gz
+0983e072d8101e7f274dc1403570636a5e12c0f56cfe3d891e379952dde0e619  node-v4.4.5-linux-ppc64.tar.xz
+15d57c4a3696df8d5ef1bba452d38e5d27fc3c963760eeb218533c48381e89d5  node-v4.4.5-linux-x64.tar.gz
+bd6505d8a350cd83907374ea98730b0ba99b97ec45cee418d453a0154384805a  node-v4.4.5-linux-x64.tar.xz
+447b17542981c20f6792a20c31eb946c786e2cbd3bd1459f85c2cd0eb400e009  node-v4.4.5-linux-x86.tar.gz
+354afb7fac8cb8dc3b926a4adb0901dd6ac42cb605f988f05f60f0bb8553a2c4  node-v4.4.5-linux-x86.tar.xz
+fc5688c7f649ea06ce21246c7aa795aa9100c9e90e4c3fe182bb8cc67435375a  node-v4.4.5.pkg
+75ebf346d29d441fbb32b177568f5727c357300406ea90b29c49a9e3bd89c506  node-v4.4.5-sunos-x64.tar.gz
+ebb5bc1fa1d165e5881dac470e260f1efb4303e122854c60633c9e097f2a977f  node-v4.4.5-sunos-x64.tar.xz
+181c092d49e2efc3ecd82806c9aa088ed1eda908671a5913cfa4704855ae288b  node-v4.4.5-sunos-x86.tar.gz
+f2ea7593bd245628a17477c61b30b6c145b2686d97f38052ac2d3cc18a87c0e5  node-v4.4.5-sunos-x86.tar.xz
+ea9c96ae4768feee4f18a26b819b9b4f6e49105ea0ee8c5c9d188dc8d49d4b77  node-v4.4.5.tar.gz
+eaec2cd3c26a1cc101b829d32fef392268285187d1d9eda3718db288e7be28c6  node-v4.4.5.tar.xz
+7b2409605c871a40d60c187bd24f6f6ddf10590df060b7d905ef46b3b3aa7f81  node-v4.4.5-x64.msi
+fa11aadbf769d2a307ba49fa8a7f6a52233e63cb44541207f31ceb30ecdd3bfa  node-v4.4.5-x86.msi
+0f9a6c4e340c45e0b32524b16f925099a79337281dd7fd982706e715634293da  win-x64/node.exe
+ec30b394f071612fa06781a0ffa757b6296287bfb4234054438c671af8fa99bf  win-x64/node.lib
+d423a134f376180939d55374aece4af1a66eb420e19f9fba2d882b000eeb01d8  win-x86/node.exe
+851793e06c47e87393fad249253d720f67111e8c34d9bf73e36fdbedecda9dc1  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJXRKDLAAoJEJM7AfQLXKlGBK8H/2Ohq5o2B6TBV4Z/tAn8N8Hs
+fbN/nGqLnKnnRPt5iXTeLQmcWx0bKNqwWq8PLo3EfaNiIC45GsS7/Jukdl6BhCvI
+BJ1DxYNnVrxyRm+IkddDwJAHMp25B8d8kSOgbO6iuYFc240ek+dWFhw60Kk68bs+
+elmOGCEFqempCCIg6rzliUSOBUOTu1c7axSy3Z6xzx0Ic9BRmsIwJzmL2RYZBEzn
+H1jbf4MoHpZvF+gdNStlsu9KE+6u4Bhy9DzJVkgcxoXU+Wikhe8x5n3I2blULSsl
+efqyCqM1GbKBZ2/wSj7KWEK1JhAJvPQnLuyERvUVYzc6nE6QGBpImen39tLjJxE=
+=DuAN
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v4.4.6.md b/locale/uk/blog/release/v4.4.6.md
new file mode 100755
index 0000000000000..3efbe6184d30c
--- /dev/null
+++ b/locale/uk/blog/release/v4.4.6.md
@@ -0,0 +1,87 @@
+---
+date: 2016-06-23T23:29:12.285Z
+version: 4.4.6
+category: release
+title: Node v4.4.6 (LTS)
+slug: node-v4-4-6
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable Changes
+
+This is an important security release. All Node.js users should consult the security release summary at nodejs.org for details on patched vulnerabilities.
+
+This release is specifically related to a Buffer overflow vulnerability discovered in v8, more details can be found [in the CVE](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1669)
+
+### Commits
+
+* [[`134c3b3977`](https://github.com/nodejs/node/commit/134c3b3977)] - **deps**: backport 3a9bfec from v8 upstream (Ben Noordhuis) [nodejs/node-private#38](https://github.com/nodejs/node-private/pull/38)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v4.4.6/node-v4.4.6-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v4.4.6/node-v4.4.6-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v4.4.6/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v4.4.6/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v4.4.6/node-v4.4.6.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v4.4.6/node-v4.4.6-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v4.4.6/node-v4.4.6.tar.gz<br>
+Other release files: https://nodejs.org/dist/v4.4.6/<br>
+Documentation: https://nodejs.org/docs/v4.4.6/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+2afbc5f48ce3b3bb9b9a46e64b8a23c08a448bf8bf89c10a5a053fd0ec024a07  node-v4.4.6-darwin-x64.tar.gz
+0b431bf1aa7fe9cd161a6d0b99da040ab67f98ed5e779c031f8c3420ad11b814  node-v4.4.6-darwin-x64.tar.xz
+75c114e9f4f3a10e5b8116a3ead9123b3982d951c392ed7a6c737638035dca21  node-v4.4.6-headers.tar.gz
+9389abec4b36775c4be959454dafb77e9872cbc57ccb5a10f7ef63c9936a503d  node-v4.4.6-headers.tar.xz
+de0c093ed38934f25cc5eaa1ecd84878fe123e0632db3bf4c3ffcd8af107a62d  node-v4.4.6-linux-arm64.tar.gz
+5a87874f63b534165d24d922b1be4d4d44da6a490832256b0a7a490915d8b719  node-v4.4.6-linux-arm64.tar.xz
+372087f61b2c53fbeb84b5cd0cdb508ef1c7d1fcecf9a56393d957d61ae4b2c2  node-v4.4.6-linux-armv6l.tar.gz
+0d4d5e1fbd97a1b349f7bb4d7f36529db75166f2ca0d28ec40aa78834d83acd6  node-v4.4.6-linux-armv6l.tar.xz
+736ca6a35cbae8870cf819362a699a9639c76eed27b6ae4f667713fbc9ec809f  node-v4.4.6-linux-armv7l.tar.gz
+6a9499375aafa23e46c72a86827ba5024727e2a66b2a5a4fcef458d1b59a76e1  node-v4.4.6-linux-armv7l.tar.xz
+ce02faf08867b01ba7bdb1431cd6750a13e8742ad30d6e9bdc2b36a417b578ad  node-v4.4.6-linux-ppc64le.tar.gz
+4ac5f5f4ed016c99f629a55c7c848f7feeedc616cfd2d788d5b57da832c39d8c  node-v4.4.6-linux-ppc64le.tar.xz
+228685937ffd2aad0999460616bfa25fa17538b52df6b328481142c1bbd565eb  node-v4.4.6-linux-ppc64.tar.gz
+1e5ddb72c71d972f62530a78110ffe82a6446665a595ca172057034dc95d747d  node-v4.4.6-linux-ppc64.tar.xz
+bef5cc1db30b56d3f40b123c6a40529b6f69c403fa969ec2654b62d4cac95e26  node-v4.4.6-linux-x64.tar.gz
+5a5633419069b2f049b8429165ab93712f8532a8b1a8fc1e733afc4d848c581c  node-v4.4.6-linux-x64.tar.xz
+86b7d4374b27ecb8d2f63b371147c0f7f7cf8b80f37ff740f42e2f074184329e  node-v4.4.6-linux-x86.tar.gz
+22d039fa55ecdb3644b49fd3ca5a9d9eb101ee07681f11afa63bbb60150bc791  node-v4.4.6-linux-x86.tar.xz
+0ff8facfc59cbe4bbbce559962d783293cbc540fe78230ab6dd8982dd9011bde  node-v4.4.6.pkg
+d1fa8b52c126a092f7c6d4ce95e12cf39d014e9593700d792aa38f529deb2f1e  node-v4.4.6-sunos-x64.tar.gz
+8de91bc3b07cf6325336156bf421e8258039fb465d095bdbaabf788b216c3b27  node-v4.4.6-sunos-x64.tar.xz
+cd0c3d55eb0d80787348cc6841ec9381746ef4992bae629d9b34671ef0270c29  node-v4.4.6-sunos-x86.tar.gz
+069f80346c74cf0db22ed362968ecef0e03f1750bed6a531bf9d200a6e0177c5  node-v4.4.6-sunos-x86.tar.xz
+45eab3d415616e5831ba5961b67cec5423e1f9c175ca7e331de7f560c2998d9f  node-v4.4.6.tar.gz
+0f6bbfbea525469c91932b1aac35e0810e6bcda96f1c720e42a433942ee66106  node-v4.4.6.tar.xz
+cff69594b5cf2ad1bf9d9c706ab43a8afd7531e187fa44cec626618b49164cce  node-v4.4.6-x64.msi
+78df65d9177034d805d0f687de179846b6467216bc915b7998305e26e9d59b06  node-v4.4.6-x86.msi
+6f12a13513d6c26aff1035bf1b6da4790370b0c54b1fd2e1c551a842c3a2558d  win-x64/node.exe
+3c81920c8f9ccdfa832de847b8fe75aca66844075880073cebb420245286e1cc  win-x64/node.lib
+d1350a5940dbea27f9d65c47dbe2d2ebf3790f2caad3d7eafa07c48c83946d57  win-x86/node.exe
+cb7b950cd0ab71c850680bfbcec783ade4ef27c77015c277670614f3ba56cdd4  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJXbGvwAAoJEJM7AfQLXKlGwroH/22IUdoCh8sl0ddlgZ0gNTM6
+/0dPRedM4U2nQrME7nugv3ZAdbGtU/UamKPGJn/yXGgHKbv7jL1oM3IpNTmwsTVs
+me9fXUi/w+rzcz+xrVlIucAhsAKkWWKmT6Ox1YyDSpe00pEFs3cBC5LCGpCpn0WG
+05Bj5udTurHQxrAUYAlro8uRXKMd/FHKu9eW587tQ6q3Q0stmPJ3FMnfNglk0eKk
+fWwORVZt8RNPJqKhaEGB9RusW0sVooHyUe6gT20biQNJ4H2pLH7DT/EYfV44SDkO
+piQ2ObJkJ4cIv58t4aKY8CaT+FnQ1jJNAdb5C6JK6FKaUvpE4dW5UPU5PMEVJXs=
+=cA0d
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.0.0.md b/locale/uk/blog/release/v5.0.0.md
new file mode 100755
index 0000000000000..a80f816cd0850
--- /dev/null
+++ b/locale/uk/blog/release/v5.0.0.md
@@ -0,0 +1,243 @@
+---
+date: 2015-10-29T12:33:38.068Z
+version: 5.0.0
+category: release
+title: Node v5.0.0 (Current)
+slug: node-v5-0-0
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+Say hello to Node.js v5! It's true that we only recently [released Node.js v4.0.0](https://nodejs.org/en/blog/release/v4.0.0/), however this new release doesn't mean that v4 is going away. In fact, v4 is going to live for a lot longer than v5.
+
+According to our new [LTS (Long-term Support) plan](https://github.com/nodejs/LTS/), Node.js v4 Argon will continue to be supported for 30 months, ending in April 2018. This new version of Node.js, however, will only be supported for 8 months, with a new major version, v6, being released in April 2016. Node.js v6 will eventually turn into a new LTS version that will have a similar support timeline to v4. In this way, we will have a new _Stable_ version of Node.js every 6 months with every second one of these turning into an LTS line. If our LTS plan is new to you, [read more](https://medium.com/@nodesource/essential-steps-long-term-support-for-node-js-8ecf7514dbd#.z6bzdfogi) about how it's going to work so you can make a properly informed decision regarding what version of Node.js to adopt.
+
+The general rule for deciding which version of Node.js to use is:
+
+* Stay on or upgrade to Node.js v4.2.x if you need **stability and have a complex production environment**, e.g. you are a medium or large enterprise.
+* Upgrade to Node.js v5.x if you have the ability to upgrade versions quickly and easily without distributing your environment and want to play with the latest features as they arrive.
+
+The release notes below are annotated with the main breaking changes that warrant the jump to v5. Note that because this new version of Node.js is shipping with a new version of V8, you will need to recompile any native add-ons you have already installed or you will receive a runtime error when trying to load them. Use `npm rebuild` or simply remove your *node_modules* directory and `npm install` from scratch.
+
+### Notable Changes
+
+* **buffer**: _(Breaking)_ Removed both `'raw'` and `'raws'` encoding types from `Buffer`, these have been deprecated for a long time (Sakthipriyan Vairamani) [#2859](https://github.com/nodejs/node/pull/2859).
+* **console**: _(Breaking)_ Values reported by `console.time()` now have 3 decimals of accuracy added (Michaël Zasso) [#3166](https://github.com/nodejs/node/pull/3166).
+* **fs**:
+  - `fs.readFile*()`, `fs.writeFile*()`, and `fs.appendFile*()` now also accept a file descriptor as their first argument (Johannes Wüller) [#3163](https://github.com/nodejs/node/pull/3163).
+  - _(Breaking)_ In `fs.readFile()`, if an encoding is specified and the internal `toString()` fails the error is no longer _thrown_ but is passed to the callback (Evan Lucas) [#3485](https://github.com/nodejs/node/pull/3485).
+  - _(Breaking)_ In `fs.read()` (using the `fs.read(fd, length, position, encoding, callback)` form), if the internal `toString()` fails the error is no longer _thrown_ but is passed to the callback (Evan Lucas) [#3503](https://github.com/nodejs/node/pull/3503).
+* **http**:
+  - Fixed a bug where pipelined http requests would stall (Fedor Indutny) [#3342](https://github.com/nodejs/node/pull/3342).
+  - _(Breaking)_ When parsing HTTP, don't add duplicates of the following headers: `Retry-After`, `ETag`, `Last-Modified`, `Server`, `Age`, `Expires`. This is in addition to the following headers which already block duplicates: `Content-Type`, `Content-Length`, `User-Agent`, `Referer`, `Host`, `Authorization`, `Proxy-Authorization`, `If-Modified-Since`, `If-Unmodified-Since`, `From`, `Location`, `Max-Forwards` (James M Snell) [#3090](https://github.com/nodejs/node/pull/3090).
+  - _(Breaking)_ The `callback` argument to `OutgoingMessage#setTimeout()` must be a function or a `TypeError` is thrown (James M Snell) [#3090](https://github.com/nodejs/node/pull/3090).
+  - _(Breaking)_ HTTP methods and header names must now conform to the RFC 2616 "token" rule, a list of allowed characters that excludes control characters and a number of _separator_ characters. Specifically, methods and header names must now match ```/^[a-zA-Z0-9_!#$%&'*+.^`|~-]+$/``` or a `TypeError` will be thrown (James M Snell) [#2526](https://github.com/nodejs/node/pull/2526).
+* **node**:
+  - _(Breaking)_ Deprecated the `_linklist` module (Rich Trott) [#3078](https://github.com/nodejs/node/pull/3078).
+  - _(Breaking)_ Removed `require.paths` and `require.registerExtension()`, both had been previously set to throw `Error` when accessed (Sakthipriyan Vairamani) [#2922](https://github.com/nodejs/node/pull/2922).
+* **npm**: Upgraded to version 3.3.6 from 2.14.7, see https://github.com/npm/npm/releases/tag/v3.3.6 for more details. This is a major version bump for npm and it has seen a significant amount of change. Please see the original [npm v3.0.0 release notes](https://github.com/npm/npm/blob/master/CHANGELOG.md#v300-2015-06-25) for a list of major changes (Rebecca Turner) [#3310](https://github.com/nodejs/node/pull/3310).
+* **src**: _(Breaking)_ Bumped `NODE_MODULE_VERSION` to `47` from `46`, this is necessary due to the V8 upgrade. Native add-ons will need to be recompiled (Rod Vagg) [#3400](https://github.com/nodejs/node/pull/3400).
+* **timers**: Attempt to reuse the timer handle for `setTimeout().unref()`. This fixes a long-standing known issue where unrefed timers would perviously hold `beforeExit` open (Fedor Indutny) [#3407](https://github.com/nodejs/node/pull/3407).
+* **tls**:
+  - Added ALPN Support (Shigeki Ohtsu) [#2564](https://github.com/nodejs/node/pull/2564).
+  - TLS options can now be passed in an object to `createSecurePair()` (Коренберг Марк) [#2441](https://github.com/nodejs/node/pull/2441).
+  - _(Breaking)_ The default minimum DH key size for `tls.connect()` is now 1024 bits and a warning is shown when DH key size is less than 2048 bits. This a security consideration to prevent "logjam" attacks. A new `minDHSize` TLS option can be used to override the default. (Shigeki Ohtsu) [#1831](https://github.com/nodejs/node/pull/1831).
+* **util**:
+  - _(Breaking)_ `util.p()` was deprecated for years, and has now been removed (Wyatt Preul) [#3432](https://github.com/nodejs/node/pull/3432).
+  - _(Breaking)_ `util.inherits()` can now work with ES6 classes. This is considered a breaking change because of potential subtle side-effects caused by a change from directly reassigning the prototype of the constructor using `ctor.prototype = Object.create(superCtor.prototype, { constructor: { ... } })` to using `Object.setPrototypeOf(ctor.prototype, superCtor.prototype)` (Michaël Zasso) [#3455](https://github.com/nodejs/node/pull/3455).
+* **v8**: _(Breaking)_ Upgraded to 4.6.85.25 from 4.5.103.35  (Ali Ijaz Sheikh) [#3351](https://github.com/nodejs/node/pull/3351).
+  - Implements the spread operator, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator for further information.
+  - Implements `new.target`, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/new.target for further information.
+* **zlib**: Decompression now throws on truncated input (e.g. unexpected end of file) (Yuval Brik) [#2595](https://github.com/nodejs/node/pull/2595).
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+
+### Commits
+
+* [[`6a04cc0a43`](https://github.com/nodejs/node/commit/6a04cc0a43)] - **buffer**: fix value check for writeUInt{B,L}E (Trevor Norris) [#3500](https://github.com/nodejs/node/pull/3500)
+* [[`1a41feb559`](https://github.com/nodejs/node/commit/1a41feb559)] - **buffer**: don't CHECK on zero-sized realloc (Ben Noordhuis) [#3499](https://github.com/nodejs/node/pull/3499)
+* [[`5f6579d366`](https://github.com/nodejs/node/commit/5f6579d366)] - **(SEMVER-MAJOR)** **buffer**: remove raw & raws encoding (Sakthipriyan Vairamani) [#2859](https://github.com/nodejs/node/pull/2859)
+* [[`70fca2a81e`](https://github.com/nodejs/node/commit/70fca2a81e)] - **build**: Updates for AIX npm support - part 1 (Michael Dawson) [#3114](https://github.com/nodejs/node/pull/3114)
+* [[`b36b4f385a`](https://github.com/nodejs/node/commit/b36b4f385a)] - **build**: rectify --link-module help text (P.S.V.R) [#3379](https://github.com/nodejs/node/pull/3379)
+* [[`a89eeca590`](https://github.com/nodejs/node/commit/a89eeca590)] - **console**: rename argument of time and timeEnd (Michaël Zasso) [#3166](https://github.com/nodejs/node/pull/3166)
+* [[`870108aaa8`](https://github.com/nodejs/node/commit/870108aaa8)] - **(SEMVER-MAJOR)** **console**: sub-millisecond accuracy for console.time (Michaël Zasso) [#3166](https://github.com/nodejs/node/pull/3166)
+* [[`0a43697ce8`](https://github.com/nodejs/node/commit/0a43697ce8)] - **deps**: backport 010897c from V8 upstream (Ali Ijaz Sheikh) [#3520](https://github.com/nodejs/node/pull/3520)
+* [[`8c0318ce8d`](https://github.com/nodejs/node/commit/8c0318ce8d)] - **deps**: backport 8d6a228 from the v8's upstream (Fedor Indutny) [#3549](https://github.com/nodejs/node/pull/3549)
+* [[`2974debc6e`](https://github.com/nodejs/node/commit/2974debc6e)] - **deps**: update V8 to 4.6.85.28 (Michaël Zasso) [#3484](https://github.com/nodejs/node/pull/3484)
+* [[`f76af49b13`](https://github.com/nodejs/node/commit/f76af49b13)] - **deps**: fix upgrade to npm 3.3.6 (Rebecca Turner) [#3494](https://github.com/nodejs/node/pull/3494)
+* [[`32b51c97ec`](https://github.com/nodejs/node/commit/32b51c97ec)] - **deps**: upgrade npm to 3.3.6 (Rebecca Turner) [#3310](https://github.com/nodejs/node/pull/3310)
+* [[`770cd229f9`](https://github.com/nodejs/node/commit/770cd229f9)] - **deps**: upgrade V8 to 4.6.85.25 (Ali Ijaz Sheikh) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`972a0c8515`](https://github.com/nodejs/node/commit/972a0c8515)] - **deps**: backport 0d01728 from v8's upstream (Fedor Indutny) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`1fdec65203`](https://github.com/nodejs/node/commit/1fdec65203)] - **deps**: improve ArrayBuffer performance in v8 (Fedor Indutny) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`5cd1fd836a`](https://github.com/nodejs/node/commit/5cd1fd836a)] - **deps**: backport 56a0a79 from V8 upstream (Julien Gilli) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`7fb128d8df`](https://github.com/nodejs/node/commit/7fb128d8df)] - **deps**: cherry-pick backports to V8 (Michaël Zasso) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`d8011d1683`](https://github.com/nodejs/node/commit/d8011d1683)] - **(SEMVER-MAJOR)** **deps**: upgrade V8 to 4.6.85.23 (Michaël Zasso) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`a334ddc467`](https://github.com/nodejs/node/commit/a334ddc467)] - ***Revert*** "**deps**: backport 03ef3cd from V8 upstream" (Ali Ijaz Sheikh) [#3237](https://github.com/nodejs/node/pull/3237)
+* [[`6fff47ffac`](https://github.com/nodejs/node/commit/6fff47ffac)] - **deps**: backport 03ef3cd from V8 upstream (Ali Ijaz Sheikh) [#3165](https://github.com/nodejs/node/pull/3165)
+* [[`680dda8023`](https://github.com/nodejs/node/commit/680dda8023)] - **dns**: remove nonexistant exports.ADNAME (Roman Reiss) [#3051](https://github.com/nodejs/node/pull/3051)
+* [[`239ad899a3`](https://github.com/nodejs/node/commit/239ad899a3)] - **doc**: add LTS info to COLLABORATOR_GUIDE.md (Myles Borins) [#3442](https://github.com/nodejs/node/pull/3442)
+* [[`5e76587fdf`](https://github.com/nodejs/node/commit/5e76587fdf)] - **doc**: createServer's key option can be an array (Sakthipriyan Vairamani) [#3123](https://github.com/nodejs/node/pull/3123)
+* [[`0317c880da`](https://github.com/nodejs/node/commit/0317c880da)] - **doc**: add TSC meeting minutes 2015-10-21 (Rod Vagg) [#3480](https://github.com/nodejs/node/pull/3480)
+* [[`cd245b12e0`](https://github.com/nodejs/node/commit/cd245b12e0)] - **doc**: clarify API buffer.concat (Martii) [#3255](https://github.com/nodejs/node/pull/3255)
+* [[`ff9ef893fd`](https://github.com/nodejs/node/commit/ff9ef893fd)] - **doc**: add TSC meeting minutes 2015-10-14 (Rod Vagg) [#3463](https://github.com/nodejs/node/pull/3463)
+* [[`605c5a7754`](https://github.com/nodejs/node/commit/605c5a7754)] - **doc**: clarify the use of `option.detached` (Kyle Smith) [#3250](https://github.com/nodejs/node/pull/3250)
+* [[`cf75a175e5`](https://github.com/nodejs/node/commit/cf75a175e5)] - **doc**: more use-cases for promise events (Domenic Denicola) [#3438](https://github.com/nodejs/node/pull/3438)
+* [[`1b75d4bda3`](https://github.com/nodejs/node/commit/1b75d4bda3)] - **doc**: update WORKING_GROUPS.md - add missing groups (Michael Dawson) [#3450](https://github.com/nodejs/node/pull/3450)
+* [[`c658de2f99`](https://github.com/nodejs/node/commit/c658de2f99)] - **doc**: add TSC meeting minutes 2015-09-30 (Rod Vagg) [#3235](https://github.com/nodejs/node/pull/3235)
+* [[`d0b8c5d3a4`](https://github.com/nodejs/node/commit/d0b8c5d3a4)] - **doc**: add TSC meeting minutes 2015-10-07 (Rod Vagg) [#3364](https://github.com/nodejs/node/pull/3364)
+* [[`b483afcb20`](https://github.com/nodejs/node/commit/b483afcb20)] - **doc**: binary encoding is not deprecated (Trevor Norris) [#3441](https://github.com/nodejs/node/pull/3441)
+* [[`b607366a1c`](https://github.com/nodejs/node/commit/b607366a1c)] - **doc**: add information about Assert behavior and maintenance (Rich Trott) [#3330](https://github.com/nodejs/node/pull/3330)
+* [[`086103b32e`](https://github.com/nodejs/node/commit/086103b32e)] - **doc**: show keylen in pbkdf2 as a byte length (calebboyd) [#3334](https://github.com/nodejs/node/pull/3334)
+* [[`f6ebc8277b`](https://github.com/nodejs/node/commit/f6ebc8277b)] - **doc**: reword description of console.time (Michaël Zasso) [#3166](https://github.com/nodejs/node/pull/3166)
+* [[`503f279527`](https://github.com/nodejs/node/commit/503f279527)] - **doc**: fix indent in tls resumption example (Roman Reiss) [#3372](https://github.com/nodejs/node/pull/3372)
+* [[`dae9fae0fe`](https://github.com/nodejs/node/commit/dae9fae0fe)] - **doc**: label v4.2.1 as LTS in changelog heading (Phillip Johnsen) [#3360](https://github.com/nodejs/node/pull/3360)
+* [[`4fc638804c`](https://github.com/nodejs/node/commit/4fc638804c)] - **doc**: update V8 options in man page (Michaël Zasso) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`a441aa6e1d`](https://github.com/nodejs/node/commit/a441aa6e1d)] - **doc**: update WORKING_GROUPS.md to include Intl (Steven R. Loomis) [#3251](https://github.com/nodejs/node/pull/3251)
+* [[`81503e597b`](https://github.com/nodejs/node/commit/81503e597b)] - **doc**: fix typo in changelog (Timothy Gu) [#3353](https://github.com/nodejs/node/pull/3353)
+* [[`3ef2e4acf3`](https://github.com/nodejs/node/commit/3ef2e4acf3)] - **doc**: fix typos in changelog (reggi) [#3291](https://github.com/nodejs/node/pull/3291)
+* [[`b9279aa193`](https://github.com/nodejs/node/commit/b9279aa193)] - **doc**: remove old note, 'cluster' is marked stable (Balázs Galambosi) [#3314](https://github.com/nodejs/node/pull/3314)
+* [[`cdfa271164`](https://github.com/nodejs/node/commit/cdfa271164)] - **doc**: update AUTHORS list (Rod Vagg)
+* [[`47b06f6bb1`](https://github.com/nodejs/node/commit/47b06f6bb1)] - **docs**: add missing shell option to execSync (fansworld-claudio) [#3440](https://github.com/nodejs/node/pull/3440)
+* [[`4c9abbd1bb`](https://github.com/nodejs/node/commit/4c9abbd1bb)] - **fs**: reduced duplicate code in fs.write() (ronkorving) [#2947](https://github.com/nodejs/node/pull/2947)
+* [[`2bb147535e`](https://github.com/nodejs/node/commit/2bb147535e)] - **(SEMVER-MAJOR)** **fs**: don't throw in read if buffer too big (Evan Lucas) [#3503](https://github.com/nodejs/node/pull/3503)
+* [[`7added3b39`](https://github.com/nodejs/node/commit/7added3b39)] - **(SEMVER-MAJOR)** **fs**: pass err to callback if buffer is too big (Evan Lucas) [#3485](https://github.com/nodejs/node/pull/3485)
+* [[`5e0759f6fd`](https://github.com/nodejs/node/commit/5e0759f6fd)] - **(SEMVER-MINOR)** **fs**: add file descriptor support to *File() funcs (Johannes Wüller) [#3163](https://github.com/nodejs/node/pull/3163)
+* [[`d1a2e5357e`](https://github.com/nodejs/node/commit/d1a2e5357e)] - **gitignore**: don't ignore debug source directory in V8 (Michaël Zasso) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`ab03635fb1`](https://github.com/nodejs/node/commit/ab03635fb1)] - **http**: fix stalled pipeline bug (Fedor Indutny) [#3342](https://github.com/nodejs/node/pull/3342)
+* [[`e655a437b3`](https://github.com/nodejs/node/commit/e655a437b3)] - **(SEMVER-MAJOR)** **http**: do not allow multiple instances of certain response headers (James M Snell) [#3090](https://github.com/nodejs/node/pull/3090)
+* [[`0094a8dad7`](https://github.com/nodejs/node/commit/0094a8dad7)] - **(SEMVER-MAJOR)** **http**: add callback is function check (James M Snell) [#3090](https://github.com/nodejs/node/pull/3090)
+* [[`6192c9892f`](https://github.com/nodejs/node/commit/6192c9892f)] - **(SEMVER-MAJOR)** **http**: add checkIsHttpToken check for header fields (James M Snell) [#2526](https://github.com/nodejs/node/pull/2526)
+* [[`c9786bb680`](https://github.com/nodejs/node/commit/c9786bb680)] - **(SEMVER-MAJOR)** http{s}: don't connect to localhost on invalid URL (Sakthipriyan Vairamani) [#2967](https://github.com/nodejs/node/pull/2967)
+* [[`1929d5be73`](https://github.com/nodejs/node/commit/1929d5be73)] - **lib**: fix cluster handle leak (Rich Trott) [#3510](https://github.com/nodejs/node/pull/3510)
+* [[`97d081709e`](https://github.com/nodejs/node/commit/97d081709e)] - **lib**: avoid REPL exit on completion error (Rich Trott) [#3358](https://github.com/nodejs/node/pull/3358)
+* [[`f236b3a904`](https://github.com/nodejs/node/commit/f236b3a904)] - **(SEMVER-MINOR)** **lib,doc**: return boolean from child.send() (Rich Trott) [#3516](https://github.com/nodejs/node/pull/3516)
+* [[`6e887cc630`](https://github.com/nodejs/node/commit/6e887cc630)] - **lib,test**: update let to const where applicable (Sakthipriyan Vairamani) [#3152](https://github.com/nodejs/node/pull/3152)
+* [[`47befffc53`](https://github.com/nodejs/node/commit/47befffc53)] - **(SEMVER-MAJOR)** **lib,test**: deprecate _linklist (Rich Trott) [#3078](https://github.com/nodejs/node/pull/3078)
+* [[`d5ce53458e`](https://github.com/nodejs/node/commit/d5ce53458e)] - **lttng**: update flags for gc tracing (Glen Keane) [#3388](https://github.com/nodejs/node/pull/3388)
+* [[`6ad458b752`](https://github.com/nodejs/node/commit/6ad458b752)] - **(SEMVER-MAJOR)** **module**: remove unnecessary property and method (Sakthipriyan Vairamani) [#2922](https://github.com/nodejs/node/pull/2922)
+* [[`ae196175f4`](https://github.com/nodejs/node/commit/ae196175f4)] - **node**: improve GetActiveRequests performance (Trevor Norris) [#3375](https://github.com/nodejs/node/pull/3375)
+* [[`bd4311bc9c`](https://github.com/nodejs/node/commit/bd4311bc9c)] - **repl**: handle comments properly (Sakthipriyan Vairamani) [#3515](https://github.com/nodejs/node/pull/3515)
+* [[`ce391ed849`](https://github.com/nodejs/node/commit/ce391ed849)] - **(SEMVER-MAJOR)** **repl**: event ordering: delay 'close' until 'flushHistory' (Jeremiah Senkpiel) [#3435](https://github.com/nodejs/node/pull/3435)
+* [[`4c80c02ac7`](https://github.com/nodejs/node/commit/4c80c02ac7)] - **repl**: limit persistent history correctly on load (Jeremiah Senkpiel) [#2356](https://github.com/nodejs/node/pull/2356)
+* [[`134a60c785`](https://github.com/nodejs/node/commit/134a60c785)] - **src**: fix race condition in debug signal on exit (Ben Noordhuis) [#3528](https://github.com/nodejs/node/pull/3528)
+* [[`bf7c3dabb4`](https://github.com/nodejs/node/commit/bf7c3dabb4)] - **(SEMVER-MAJOR)** **src**: bump NODE_MODULE_VERSION To 47 (Rod Vagg) [#3400](https://github.com/nodejs/node/pull/3400)
+* [[`2d3560767e`](https://github.com/nodejs/node/commit/2d3560767e)] - **src**: fix exception message encoding on Windows (Brian White) [#3288](https://github.com/nodejs/node/pull/3288)
+* [[`ff877e93e1`](https://github.com/nodejs/node/commit/ff877e93e1)] - **src**: fix stuck debugger process (Liang-Chi Hsieh) [#2778](https://github.com/nodejs/node/pull/2778)
+* [[`8854183fe5`](https://github.com/nodejs/node/commit/8854183fe5)] - **stream**: avoid unnecessary concat of a single buffer. (Calvin Metcalf) [#3300](https://github.com/nodejs/node/pull/3300)
+* [[`85b74de9de`](https://github.com/nodejs/node/commit/85b74de9de)] - **stream**: fix signature of _write() in a comment (Fábio Santos) [#3248](https://github.com/nodejs/node/pull/3248)
+* [[`b8cea49c88`](https://github.com/nodejs/node/commit/b8cea49c88)] - **test**: fix heap-profiler link error LNK1194 on win (Junliang Yan) [#3572](https://github.com/nodejs/node/pull/3572)
+* [[`4a5dbeab43`](https://github.com/nodejs/node/commit/4a5dbeab43)] - **test**: fix missing unistd.h on windows (Junliang Yan) [#3532](https://github.com/nodejs/node/pull/3532)
+* [[`74e2328b3a`](https://github.com/nodejs/node/commit/74e2328b3a)] - **test**: split independent tests into separate files (Rich Trott) [#3548](https://github.com/nodejs/node/pull/3548)
+* [[`8c6c0f915a`](https://github.com/nodejs/node/commit/8c6c0f915a)] - **test**: use port number from env in tls socket test (Stefan Budeanu) [#3557](https://github.com/nodejs/node/pull/3557)
+* [[`1a968e67a5`](https://github.com/nodejs/node/commit/1a968e67a5)] - **test**: improve tests for util.inherits (Michaël Zasso) [#3507](https://github.com/nodejs/node/pull/3507)
+* [[`9d8d752456`](https://github.com/nodejs/node/commit/9d8d752456)] - **test**: print helpful err msg on test-dns-ipv6.js (Junliang Yan) [#3501](https://github.com/nodejs/node/pull/3501)
+* [[`60de9f8d7b`](https://github.com/nodejs/node/commit/60de9f8d7b)] - **test**: wrap assert.fail when passed to callback (Myles Borins) [#3453](https://github.com/nodejs/node/pull/3453)
+* [[`cd83f7ed7f`](https://github.com/nodejs/node/commit/cd83f7ed7f)] - **test**: add node::MakeCallback() test coverage (Ben Noordhuis) [#3478](https://github.com/nodejs/node/pull/3478)
+* [[`08da5c2a06`](https://github.com/nodejs/node/commit/08da5c2a06)] - **test**: disable test-tick-processor - aix and be ppc (Michael Dawson) [#3491](https://github.com/nodejs/node/pull/3491)
+* [[`7c35fbcb14`](https://github.com/nodejs/node/commit/7c35fbcb14)] - **test**: harden test-child-process-fork-regr-gh-2847 (Michael Dawson) [#3459](https://github.com/nodejs/node/pull/3459)
+* [[`ad2b272417`](https://github.com/nodejs/node/commit/ad2b272417)] - **test**: fix test-net-keepalive for AIX (Imran Iqbal) [#3458](https://github.com/nodejs/node/pull/3458)
+* [[`04fb14cc35`](https://github.com/nodejs/node/commit/04fb14cc35)] - **test**: fix flaky test-child-process-emfile (Rich Trott) [#3430](https://github.com/nodejs/node/pull/3430)
+* [[`eef0f0cd63`](https://github.com/nodejs/node/commit/eef0f0cd63)] - **test**: remove flaky status from eval_messages test (Rich Trott) [#3420](https://github.com/nodejs/node/pull/3420)
+* [[`bbbd81eab2`](https://github.com/nodejs/node/commit/bbbd81eab2)] - **test**: skip test-dns-ipv6.js if ipv6 is unavailable (Junliang Yan) [#3444](https://github.com/nodejs/node/pull/3444)
+* [[`f78c8e7426`](https://github.com/nodejs/node/commit/f78c8e7426)] - **test**: fix flaky test for symlinks (Rich Trott) [#3418](https://github.com/nodejs/node/pull/3418)
+* [[`28e9a4f41b`](https://github.com/nodejs/node/commit/28e9a4f41b)] - **test**: repl-persistent-history is no longer flaky (Jeremiah Senkpiel) [#3437](https://github.com/nodejs/node/pull/3437)
+* [[`9e981556e5`](https://github.com/nodejs/node/commit/9e981556e5)] - **test**: cleanup, improve repl-persistent-history (Jeremiah Senkpiel) [#2356](https://github.com/nodejs/node/pull/2356)
+* [[`ee2e641e0a`](https://github.com/nodejs/node/commit/ee2e641e0a)] - **test**: add Symbol test for assert.deepEqual() (Rich Trott) [#3327](https://github.com/nodejs/node/pull/3327)
+* [[`e2b8393ee8`](https://github.com/nodejs/node/commit/e2b8393ee8)] - **test**: port domains regression test from v0.10 (Jonas Dohse) [#3356](https://github.com/nodejs/node/pull/3356)
+* [[`676e61872f`](https://github.com/nodejs/node/commit/676e61872f)] - **test**: apply correct assert.fail() arguments (Rich Trott) [#3378](https://github.com/nodejs/node/pull/3378)
+* [[`bbdbef9274`](https://github.com/nodejs/node/commit/bbdbef9274)] - **test**: fix tests after V8 upgrade (Michaël Zasso) [#3351](https://github.com/nodejs/node/pull/3351)
+* [[`6c032a8333`](https://github.com/nodejs/node/commit/6c032a8333)] - **test**: replace util with backtick strings (Myles Borins) [#3359](https://github.com/nodejs/node/pull/3359)
+* [[`f45c315763`](https://github.com/nodejs/node/commit/f45c315763)] - **test**: fix domain with abort-on-uncaught on PPC (Julien Gilli) [#3354](https://github.com/nodejs/node/pull/3354)
+* [[`e3d9d25083`](https://github.com/nodejs/node/commit/e3d9d25083)] - **test**: add test-child-process-emfile fail message (Rich Trott) [#3335](https://github.com/nodejs/node/pull/3335)
+* [[`6f14b3a7db`](https://github.com/nodejs/node/commit/6f14b3a7db)] - **test**: remove util from common (Rich Trott) [#3324](https://github.com/nodejs/node/pull/3324)
+* [[`7d94611ac9`](https://github.com/nodejs/node/commit/7d94611ac9)] - **test**: split up buffer tests for reliability (Rich Trott) [#3323](https://github.com/nodejs/node/pull/3323)
+* [[`3202456baa`](https://github.com/nodejs/node/commit/3202456baa)] - **test**: remove util properties from common (Rich Trott) [#3304](https://github.com/nodejs/node/pull/3304)
+* [[`31c971d641`](https://github.com/nodejs/node/commit/31c971d641)] - **test**: parallelize long-running test (Rich Trott) [#3287](https://github.com/nodejs/node/pull/3287)
+* [[`5bbc6df7de`](https://github.com/nodejs/node/commit/5bbc6df7de)] - **test**: change call to deprecated util.isError() (Rich Trott) [#3084](https://github.com/nodejs/node/pull/3084)
+* [[`522e3d3cd3`](https://github.com/nodejs/node/commit/522e3d3cd3)] - **timers**: reuse timer in `setTimeout().unref()` (Fedor Indutny) [#3407](https://github.com/nodejs/node/pull/3407)
+* [[`b64ce5960f`](https://github.com/nodejs/node/commit/b64ce5960f)] - **tls**: remove util and calls to util.format (Myles Borins) [#3456](https://github.com/nodejs/node/pull/3456)
+* [[`c64af7d99e`](https://github.com/nodejs/node/commit/c64af7d99e)] - **tls**: TLSSocket options default isServer false (Yuval Brik) [#2614](https://github.com/nodejs/node/pull/2614)
+* [[`2296a4fc0f`](https://github.com/nodejs/node/commit/2296a4fc0f)] - **(SEMVER-MINOR)** **tls**: add `options` argument to createSecurePair (Коренберг Марк) [#2441](https://github.com/nodejs/node/pull/2441)
+* [[`0140e1b5e3`](https://github.com/nodejs/node/commit/0140e1b5e3)] - **tls**: output warning of setDHParam to console.trace (Shigeki Ohtsu) [#1831](https://github.com/nodejs/node/pull/1831)
+* [[`f72e178a78`](https://github.com/nodejs/node/commit/f72e178a78)] - **(SEMVER-MAJOR)** **tls**: add minDHSize option to tls.connect() (Shigeki Ohtsu) [#1831](https://github.com/nodejs/node/pull/1831)
+* [[`6d92ebac11`](https://github.com/nodejs/node/commit/6d92ebac11)] - **tls**: add TLSSocket.getEphemeralKeyInfo() (Shigeki Ohtsu) [#1831](https://github.com/nodejs/node/pull/1831)
+* [[`62ad1d0113`](https://github.com/nodejs/node/commit/62ad1d0113)] - **(SEMVER-MINOR)** **tls, crypto**: add ALPN Support (Shigeki Ohtsu) [#2564](https://github.com/nodejs/node/pull/2564)
+* [[`5029f41b2f`](https://github.com/nodejs/node/commit/5029f41b2f)] - **(SEMVER-MINOR)** **tls,crypto**: move NPN protcol data to hidden value (Shigeki Ohtsu) [#2564](https://github.com/nodejs/node/pull/2564)
+* [[`701e38c25f`](https://github.com/nodejs/node/commit/701e38c25f)] - **tools**: enable prefer-const eslint rule (Sakthipriyan Vairamani) [#3152](https://github.com/nodejs/node/pull/3152)
+* [[`6e78382605`](https://github.com/nodejs/node/commit/6e78382605)] - **tools**: ensure npm always uses the local node (Jeremiah Senkpiel) [#3489](https://github.com/nodejs/node/pull/3489)
+* [[`3c3435d017`](https://github.com/nodejs/node/commit/3c3435d017)] - **tools**: update test-npm to work with npm 3 (Rebecca Turner) [#3489](https://github.com/nodejs/node/pull/3489)
+* [[`b4f4c24539`](https://github.com/nodejs/node/commit/b4f4c24539)] - **tools**: use absolute paths in test-npm (Rebecca Turner) [#3309](https://github.com/nodejs/node/pull/3309)
+* [[`80573153b8`](https://github.com/nodejs/node/commit/80573153b8)] - **(SEMVER-MAJOR)** **util**: make inherits work with classes (Michaël Zasso) [#3455](https://github.com/nodejs/node/pull/3455)
+* [[`412252ca04`](https://github.com/nodejs/node/commit/412252ca04)] - **(SEMVER-MAJOR)** **util**: Remove p, has been deprecated for years (Wyatt Preul) [#3432](https://github.com/nodejs/node/pull/3432)
+* [[`718c304a4f`](https://github.com/nodejs/node/commit/718c304a4f)] - **v8**: pull fix for builtin code size on PPC (Michael Dawson) [#3474](https://github.com/nodejs/node/pull/3474)
+* [[`6936468de2`](https://github.com/nodejs/node/commit/6936468de2)] - **vm**: remove Watchdog dependency on Environment (Ido Ben-Yair) [#3274](https://github.com/nodejs/node/pull/3274)
+* [[`80169b1f0a`](https://github.com/nodejs/node/commit/80169b1f0a)] - **(SEMVER-MAJOR)** **zlib**: decompression throw on truncated input (Yuval Brik) [#2595](https://github.com/nodejs/node/pull/2595)
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.0.0/node-v5.0.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.0.0/node-v5.0.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.0.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.0.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.0.0/node-v5.0.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.0.0/node-v5.0.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.0.0/node-v5.0.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.0.0/<br>
+Documentation: https://nodejs.org/docs/v5.0.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+26f3e42df814b9b42f0b0045901c84eb79233d8196d0dcdf77a6a3c975c6f25d  node-v5.0.0-darwin-x64.tar.gz
+060d4bdf5872047ef74f3b1f3daaa466c2506e34ad916128f4b9279d005bc205  node-v5.0.0-darwin-x64.tar.xz
+5133b6145df7083133e272e1b8c96b59c58a19d004d5aacdec80ea78e58c7e46  node-v5.0.0-headers.tar.gz
+47dc88a17c416285de6c517ea6107322b65920618e8f59e1c49a83c6dd423f31  node-v5.0.0-headers.tar.xz
+2c4517d3fdefc29b5c61aa6ea3386a0dafca831357d3bcd30fc14e97b49139d1  node-v5.0.0-linux-arm64.tar.gz
+5fd1939b15406d537bf17828a707898f2d710c3c9ddf243b6070353fd13f5880  node-v5.0.0-linux-arm64.tar.xz
+96629e271e34d14bdb7be93067a8770cb5326977b9168cf2344c80a721040784  node-v5.0.0-linux-armv6l.tar.gz
+82178863010dba66076fdda215e5ad505c1b83571df1d018dce2060d24f260d7  node-v5.0.0-linux-armv6l.tar.xz
+6bf5f19cac9f01cb31b7088685d9d6df6d24c9c2a4531ace839387763b8a28ec  node-v5.0.0-linux-armv7l.tar.gz
+97575c7ec3f042acf85f9b6de3ec6db027b0ef4a828eaa5e0f66504c72884bd9  node-v5.0.0-linux-armv7l.tar.xz
+ef73b59048a0ed11d01633f0061627b7a9879257deb9add2255e4d0808f8b671  node-v5.0.0-linux-x64.tar.gz
+1c3e8e7df3320e648f748d721115e6018e0701a206232a6a7332970d211e3706  node-v5.0.0-linux-x64.tar.xz
+6484c4cac1724f2818354e3f2a8ede66308617b648cd3db624596b8cd58b5f6b  node-v5.0.0-linux-x86.tar.gz
+46a56d8c00a791f46666dd9d2401b7c26ee7ac8455762fbb106c1497867c9c4b  node-v5.0.0-linux-x86.tar.xz
+f23ca05d3d7e642ab9b0c8090b0b88fb29dec987b07d67f307bf3aef81e95b14  node-v5.0.0.pkg
+7cfbed6e6658d8304f8593eae9dd28f8f83b57e7a6345b32f4d5e9830b80203f  node-v5.0.0-sunos-x64.tar.gz
+047bd9fbb25fc6a3349781bddf5210966943b06fa62c6e275d1221613c9f3423  node-v5.0.0-sunos-x64.tar.xz
+2e9d65dff65843ebfa5c9d623c5b930bd0af7252101cc9c69c55aa8c880fa9eb  node-v5.0.0-sunos-x86.tar.gz
+c7038764010eba883b5fa638123b7b94e82b86960a0792a7b10123451d978e9a  node-v5.0.0-sunos-x86.tar.xz
+698d9662067ae6a20a2586e5c09659735fc0050769a0d8f76f979189ceaccdf4  node-v5.0.0.tar.gz
+cf4f261618e19517c8cbf2fdde00d0b5160e271760abee00f387b11a0b3ca834  node-v5.0.0.tar.xz
+8a066f8cf38f4dd979366c223d90d6242076d2446f48856abb091b2becc939ef  node-v5.0.0-x64.msi
+07826a6b60702a0ce9a77240103bf20091a06ee740e646e9f7d6ca760c64e45a  node-v5.0.0-x86.msi
+27c819be0958fdb4b63be29fb032525965e997da8e0f6b4a6e9123350b7b22e0  win-x64/node.exe
+27992ac24ab67099d243e76fc52382b42caf4bf75b4b792d647359221dfa5d0f  win-x64/node.lib
+b2a5caab041d6e0a3fefc3a0b557df71ce9174c9ca344e5a690b9accb9f76d84  win-x86/node.exe
+f79d9545ad99221d090c30e415af74431eae15c729e820a96385b051be3837f2  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWMom1AAoJEMJzeS99g1RdsxAIAKcA3B14sgCa6qZ1LZfXN5Qj
+hogNS6r1L6Mb15E4Gvknjej2n2At2PpdSmxPKIex2uhwGJHcidyakn3NzPwzhdJQ
+VtgQKL7G7ZhsXYrKD78kS6GdGql1u4MroTbHSACthmZv+OdDhGEmL1UIN8+PU45V
+gBDwg+JPRPYeSGzXcqOwmUHkqgvCaFvyGZfu0j18GT8TjaXkj5M8J9emtmtRBX15
+Sp9jbOMRrt9gGHmIqcx/AzCIfqGyi4Lb/CwdyD5hXWfHFfeWspsOx+RFFh965JLy
+F6Z13Zr5Oph2fdobiuXYN1WSmrHX2kfy1B2WAt80vwwVzEiIQcSUhEU9qu8z9Qg=
+=v3xU
+-----END PGP SIGNATURE-----
+```
diff --git a/locale/uk/blog/release/v5.1.0.md b/locale/uk/blog/release/v5.1.0.md
new file mode 100755
index 0000000000000..2012f3b196b3a
--- /dev/null
+++ b/locale/uk/blog/release/v5.1.0.md
@@ -0,0 +1,239 @@
+---
+date: 2015-11-17T21:47:36.127Z
+version: 5.1.0
+category: release
+title: Node v5.1.0 (Current)
+slug: node-v5-1-0
+layout: blog-post.hbs
+author: Jeremiah Senkpiel
+---
+
+### Notable changes
+
+* **buffer**: The `noAssert` option for many buffer functions will now silently drop invalid write values rather than crashing (P.S.V.R) [#3767](https://github.com/nodejs/node/pull/3767).
+  - This makes the behavior match what the docs suggest.
+* **child_process**: `child.send()` now properly returns a boolean like the docs suggest (Rich Trott) [#3577](https://github.com/nodejs/node/pull/3577).
+* **doc**: All of the API docs have been re-ordered so as to read in alphabetical order (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662).
+* **http_parser**: update http-parser to 2.6.0 from 2.5.0 (James M Snell) [#3569](https://github.com/nodejs/node/pull/3569).
+  - Now supports the following HTTP methods: `LINK`, `UNLINK`, `BIND`, `REBIND`, `UNBIND`.
+  - Also added ACL and IPv6 Zone ID support.
+* **npm**: upgrade npm to 3.3.12 from v3.3.6 (Rebecca Turner) [#3685](https://github.com/nodejs/node/pull/3685).
+  - See the release notes for [v3.3.7](https://github.com/npm/npm/releases/tag/v3.3.7), [v3.3.8](https://github.com/npm/npm/releases/tag/v3.3.8), [v3.3.9](https://github.com/npm/npm/releases/tag/v3.3.9), [v3.3.10](https://github.com/npm/npm/releases/tag/v3.3.10), [v3.3.11](https://github.com/npm/npm/releases/tag/v3.3.11), and [v3.3.12](https://github.com/npm/npm/releases/tag/v3.3.12) for more details.
+* **repl**: The REPL no longer crashes if the [persistent history](https://nodejs.org/api/repl.html#repl_persistent_history) file cannot be opened (Evan Lucas) [#3630](https://github.com/nodejs/node/pull/3630).
+* **tls**: The default `sessionIdContext` now uses SHA1 in FIPS mode rather than MD5 (Stefan Budeanu) [#3755](https://github.com/nodejs/node/pull/3755).
+* **v8**: Added some more useful post-mortem data (Fedor Indutny) [#3779](https://github.com/nodejs/node/pull/3779).
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`b663d2bbb5`](https://github.com/nodejs/node/commit/b663d2bbb5)] - **async_wrap**: call callback in destructor (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461)
+* [[`eccbec99ea`](https://github.com/nodejs/node/commit/eccbec99ea)] - **async_wrap**: new instances get uid (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461)
+* [[`5d34c81a5c`](https://github.com/nodejs/node/commit/5d34c81a5c)] - **async_wrap**: allow some hooks to be optional (Trevor Norris) [#3461](https://github.com/nodejs/node/pull/3461)
+* [[`7bff0138e2`](https://github.com/nodejs/node/commit/7bff0138e2)] - **buffer**: let WriteFloatGeneric silently drop values (P.S.V.R) [#3767](https://github.com/nodejs/node/pull/3767)
+* [[`56673693cd`](https://github.com/nodejs/node/commit/56673693cd)] - **buffer**: neuter external `nullptr` buffers (Fedor Indutny) [#3624](https://github.com/nodejs/node/pull/3624)
+* [[`2d0ca0293a`](https://github.com/nodejs/node/commit/2d0ca0293a)] - **build**: fix configuring with prebuilt libraries (Markus Tzoe) [#3135](https://github.com/nodejs/node/pull/3135)
+* [[`2a69b6820f`](https://github.com/nodejs/node/commit/2a69b6820f)] - **build**: fix --with-intl=system-icu for x-compile (Steven R. Loomis) [#3808](https://github.com/nodejs/node/pull/3808)
+* [[`8f5a2550a7`](https://github.com/nodejs/node/commit/8f5a2550a7)] - **build**: omit -gline-tables-only for --enable-asan (Ben Noordhuis) [#3680](https://github.com/nodejs/node/pull/3680)
+* [[`84bb74547d`](https://github.com/nodejs/node/commit/84bb74547d)] - **child_process**: add safety checks on stdio access (cjihrig) [#3799](https://github.com/nodejs/node/pull/3799)
+* [[`e888471a11`](https://github.com/nodejs/node/commit/e888471a11)] - **child_process**: don't fork bomb ourselves from -e (Ben Noordhuis) [#3575](https://github.com/nodejs/node/pull/3575)
+* [[`47f3735e88`](https://github.com/nodejs/node/commit/47f3735e88)] - **cluster**: send suicide message on disconnect (cjihrig) [#3720](https://github.com/nodejs/node/pull/3720)
+* [[`d64a56cba5`](https://github.com/nodejs/node/commit/d64a56cba5)] - **cluster**: remove handles when disconnecting worker (Ben Noordhuis) [#3677](https://github.com/nodejs/node/pull/3677)
+* [[`5ed30da5a0`](https://github.com/nodejs/node/commit/5ed30da5a0)] - **console**: use 'label' argument for time and timeEnd (Roman Reiss) [#3590](https://github.com/nodejs/node/pull/3590)
+* [[`7a290abea6`](https://github.com/nodejs/node/commit/7a290abea6)] - **crypto**: DSA parameter validation in FIPS mode (Stefan Budeanu) [#3756](https://github.com/nodejs/node/pull/3756)
+* [[`2c9fb147be`](https://github.com/nodejs/node/commit/2c9fb147be)] - **crypto**: Improve error checking and reporting (Stefan Budeanu) [#3753](https://github.com/nodejs/node/pull/3753)
+* [[`66dccaf0cd`](https://github.com/nodejs/node/commit/66dccaf0cd)] - **debugger**: also exit when the repl emits 'exit' (Felix Böhm) [#2369](https://github.com/nodejs/node/pull/2369)
+* [[`fd0253be4d`](https://github.com/nodejs/node/commit/fd0253be4d)] - **deps**: backport bc2e393 from v8 upstream (evan.lucas) [#3792](https://github.com/nodejs/node/pull/3792)
+* [[`59077acc3d`](https://github.com/nodejs/node/commit/59077acc3d)] - **deps**: cherry-pick 68e89fb from v8's upstream (Fedor Indutny) [#3779](https://github.com/nodejs/node/pull/3779)
+* [[`9ef81ff5d3`](https://github.com/nodejs/node/commit/9ef81ff5d3)] - **deps**: update V8 to 4.6.85.31 (Michaël Zasso) [#3698](https://github.com/nodejs/node/pull/3698)
+* [[`b48dbf9fce`](https://github.com/nodejs/node/commit/b48dbf9fce)] - **deps**: upgrade npm to 3.3.12 (Rebecca Turner) [#3685](https://github.com/nodejs/node/pull/3685)
+* [[`7caeb14e11`](https://github.com/nodejs/node/commit/7caeb14e11)] - **(SEMVER-MINOR)** **deps**: update http-parser to 2.6.0 (James M Snell) [#3569](https://github.com/nodejs/node/pull/3569)
+* [[`08e0de59fa`](https://github.com/nodejs/node/commit/08e0de59fa)] - **deps**: upgrade npm to 3.3.10 (Rebecca Turner) [#3599](https://github.com/nodejs/node/pull/3599)
+* [[`ac9e4ffe8e`](https://github.com/nodejs/node/commit/ac9e4ffe8e)] - **dns**: prevent undefined values in results (Junliang Yan) [#3696](https://github.com/nodejs/node/pull/3696)
+* [[`ea67d870f4`](https://github.com/nodejs/node/commit/ea67d870f4)] - **doc**: document release types in readme (Rod Vagg) [#3482](https://github.com/nodejs/node/pull/3482)
+* [[`60d3daa65c`](https://github.com/nodejs/node/commit/60d3daa65c)] - **doc**: replace head of readme with updated text (Rod Vagg) [#3482](https://github.com/nodejs/node/pull/3482)
+* [[`df1fdba2ae`](https://github.com/nodejs/node/commit/df1fdba2ae)] - **doc**: sort repl alphabetically (Tristian Flanagan) [#3859](https://github.com/nodejs/node/pull/3859)
+* [[`7ecd5422c8`](https://github.com/nodejs/node/commit/7ecd5422c8)] - **doc**: address use of profanity in code of conduct (James M Snell) [#3827](https://github.com/nodejs/node/pull/3827)
+* [[`c2393d1f2a`](https://github.com/nodejs/node/commit/c2393d1f2a)] - **doc**: consistent reference-style links (Bryan English) [#3845](https://github.com/nodejs/node/pull/3845)
+* [[`96f53c6b02`](https://github.com/nodejs/node/commit/96f53c6b02)] - **doc**: add link to \[customizing util.inspect colors\]. (Jesse McCarthy) [#3749](https://github.com/nodejs/node/pull/3749)
+* [[`132297d3f6`](https://github.com/nodejs/node/commit/132297d3f6)] - **doc**: Updated streams simplified constructor API (Tom Gallacher) [#3602](https://github.com/nodejs/node/pull/3602)
+* [[`d137f0fd28`](https://github.com/nodejs/node/commit/d137f0fd28)] - **doc**: add warning about Windows process groups (Roman Klauke) [#3681](https://github.com/nodejs/node/pull/3681)
+* [[`45ff31cf94`](https://github.com/nodejs/node/commit/45ff31cf94)] - **doc**: added what buf.copy returns (Manuel B) [#3555](https://github.com/nodejs/node/pull/3555)
+* [[`5d1faa28cb`](https://github.com/nodejs/node/commit/5d1faa28cb)] - **doc**: reword message.headers to indicate they are not read-only (Tristian Flanagan) [#3814](https://github.com/nodejs/node/pull/3814)
+* [[`25c3807051`](https://github.com/nodejs/node/commit/25c3807051)] - **doc**: clarify duplicate header handling (Bryan English) [#3810](https://github.com/nodejs/node/pull/3810)
+* [[`ae2d1ee302`](https://github.com/nodejs/node/commit/ae2d1ee302)] - **doc**: repl: add defineComand and displayPrompt (Bryan English) [#3765](https://github.com/nodejs/node/pull/3765)
+* [[`09e524d013`](https://github.com/nodejs/node/commit/09e524d013)] - **doc**: sort tls alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`7e60b81c81`](https://github.com/nodejs/node/commit/7e60b81c81)] - **doc**: sort stream alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`cd931a8a13`](https://github.com/nodejs/node/commit/cd931a8a13)] - **doc**: sort net alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`cfa8198af8`](https://github.com/nodejs/node/commit/cfa8198af8)] - **doc**: sort process alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`e1a512607a`](https://github.com/nodejs/node/commit/e1a512607a)] - **doc**: sort zlib alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`0996b97240`](https://github.com/nodejs/node/commit/0996b97240)] - **doc**: sort util alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`df07072b66`](https://github.com/nodejs/node/commit/df07072b66)] - **doc**: sort https alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`6e9d01c7d8`](https://github.com/nodejs/node/commit/6e9d01c7d8)] - **doc**: sort http alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`18da02fa0f`](https://github.com/nodejs/node/commit/18da02fa0f)] - **doc**: sort modules alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`29054ffc0c`](https://github.com/nodejs/node/commit/29054ffc0c)] - **doc**: sort readline alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`389ead37ef`](https://github.com/nodejs/node/commit/389ead37ef)] - **doc**: sort repl alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`d383d624de`](https://github.com/nodejs/node/commit/d383d624de)] - **doc**: sort string_decoder alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`0d2262887c`](https://github.com/nodejs/node/commit/0d2262887c)] - **doc**: sort timers alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`14b5a95d03`](https://github.com/nodejs/node/commit/14b5a95d03)] - **doc**: sort tty alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`d4dda77e4a`](https://github.com/nodejs/node/commit/d4dda77e4a)] - **doc**: sort url alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`39b8259bd5`](https://github.com/nodejs/node/commit/39b8259bd5)] - **doc**: sort vm alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`d357b3090e`](https://github.com/nodejs/node/commit/d357b3090e)] - **doc**: sort querystring alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`1f56abaa98`](https://github.com/nodejs/node/commit/1f56abaa98)] - **doc**: sort punycode alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`bc63667456`](https://github.com/nodejs/node/commit/bc63667456)] - **doc**: sort path alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`22961e011c`](https://github.com/nodejs/node/commit/22961e011c)] - **doc**: sort os alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`4ba18489d3`](https://github.com/nodejs/node/commit/4ba18489d3)] - **doc**: sort globals alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`c3f5ea704f`](https://github.com/nodejs/node/commit/c3f5ea704f)] - **doc**: sort fs alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`ce3ac8dd1e`](https://github.com/nodejs/node/commit/ce3ac8dd1e)] - **doc**: sort events alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`63a78749b8`](https://github.com/nodejs/node/commit/63a78749b8)] - **doc**: sort errors alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`488326da8d`](https://github.com/nodejs/node/commit/488326da8d)] - **doc**: sort dgram alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`e1c357e881`](https://github.com/nodejs/node/commit/e1c357e881)] - **doc**: sort crypto alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`4118fd5794`](https://github.com/nodejs/node/commit/4118fd5794)] - **doc**: sort dns alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`3e046acc50`](https://github.com/nodejs/node/commit/3e046acc50)] - **doc**: sort console alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`05f1af7124`](https://github.com/nodejs/node/commit/05f1af7124)] - **doc**: sort cluster alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`5c30e5dada`](https://github.com/nodejs/node/commit/5c30e5dada)] - **doc**: sort child_process alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`fb6a09cd0e`](https://github.com/nodejs/node/commit/fb6a09cd0e)] - **doc**: sort buffer alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`c7c05d8f02`](https://github.com/nodejs/node/commit/c7c05d8f02)] - **doc**: sort assert alphabetically (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662)
+* [[`f2c2e53321`](https://github.com/nodejs/node/commit/f2c2e53321)] - **doc**: add note to util.isBuffer (Evan Lucas) [#3790](https://github.com/nodejs/node/pull/3790)
+* [[`35fb9f91eb`](https://github.com/nodejs/node/commit/35fb9f91eb)] - **doc**: Describe FIPSDIR environment variable (Stefan Budeanu) [#3752](https://github.com/nodejs/node/pull/3752)
+* [[`da911f158b`](https://github.com/nodejs/node/commit/da911f158b)] - **doc**: update lts description in the collaborator guide (James M Snell) [#3668](https://github.com/nodejs/node/pull/3668)
+* [[`597f8751d1`](https://github.com/nodejs/node/commit/597f8751d1)] - **doc**: add note on tls connection meta data methods (Tyler Henkel) [#3746](https://github.com/nodejs/node/pull/3746)
+* [[`a32d9e31dc`](https://github.com/nodejs/node/commit/a32d9e31dc)] - **doc**: add romankl to collaborators (Roman Klauke) [#3725](https://github.com/nodejs/node/pull/3725)
+* [[`e5b9109d12`](https://github.com/nodejs/node/commit/e5b9109d12)] - **doc**: add thealphanerd to collaborators (Myles Borins) [#3723](https://github.com/nodejs/node/pull/3723)
+* [[`a05a0b47e3`](https://github.com/nodejs/node/commit/a05a0b47e3)] - **doc**: add saghul as a collaborator (Saúl Ibarra Corretgé) [#3724](https://github.com/nodejs/node/pull/3724)
+* [[`b14d9c5f16`](https://github.com/nodejs/node/commit/b14d9c5f16)] - **doc**: add method links in events.markdown (Alejandro Oviedo) [#3187](https://github.com/nodejs/node/pull/3187)
+* [[`44f779b112`](https://github.com/nodejs/node/commit/44f779b112)] - **doc**: add caveats of algs and key size in crypto (Shigeki Ohtsu) [#3479](https://github.com/nodejs/node/pull/3479)
+* [[`a0db5fb355`](https://github.com/nodejs/node/commit/a0db5fb355)] - **doc**: stdout/stderr can block when directed to file (Ben Noordhuis) [#3170](https://github.com/nodejs/node/pull/3170)
+* [[`409f29972e`](https://github.com/nodejs/node/commit/409f29972e)] - **doc**: rename iojs-* groups to nodejs-* (Steven R. Loomis) [#3634](https://github.com/nodejs/node/pull/3634)
+* [[`801866280e`](https://github.com/nodejs/node/commit/801866280e)] - **doc**: fix wrong date and known issue in changelog.md (James M Snell) [#3650](https://github.com/nodejs/node/pull/3650)
+* [[`325c4c7af5`](https://github.com/nodejs/node/commit/325c4c7af5)] - **doc**: fix function param order in assert doc (David Woods) [#3533](https://github.com/nodejs/node/pull/3533)
+* [[`045e04e531`](https://github.com/nodejs/node/commit/045e04e531)] - **doc**: typo fix in readme.md (Sam P Gallagher-Bishop) [#3649](https://github.com/nodejs/node/pull/3649)
+* [[`7fd8f1371e`](https://github.com/nodejs/node/commit/7fd8f1371e)] - **doc**: add note about timeout delay > TIMEOUT_MAX (Guilherme Souza) [#3512](https://github.com/nodejs/node/pull/3512)
+* [[`7d0b589644`](https://github.com/nodejs/node/commit/7d0b589644)] - **doc**: fix crypto spkac function descriptions (Jason Gerfen) [#3614](https://github.com/nodejs/node/pull/3614)
+* [[`efa19bdcb5`](https://github.com/nodejs/node/commit/efa19bdcb5)] - **doc**: add final full stop in CONTRIBUTING.md (Emily Aviva Kapor-Mater) [#3576](https://github.com/nodejs/node/pull/3576)
+* [[`90723afe32`](https://github.com/nodejs/node/commit/90723afe32)] - **doc**: made code spans more visible in the API docs (phijohns) [#3573](https://github.com/nodejs/node/pull/3573)
+* [[`530bb9144f`](https://github.com/nodejs/node/commit/530bb9144f)] - **docs**: improve discoverability of Code of Conduct (Ashley Williams) [#3774](https://github.com/nodejs/node/pull/3774)
+* [[`73e40f0327`](https://github.com/nodejs/node/commit/73e40f0327)] - **docs**: fs - change links to buffer encoding to Buffer class anchor (fansworld-claudio) [#2796](https://github.com/nodejs/node/pull/2796)
+* [[`7a84fa6c60`](https://github.com/nodejs/node/commit/7a84fa6c60)] - **docs**: fs - remove encoding list and link to buffer (fansworld-claudio) [#2796](https://github.com/nodejs/node/pull/2796)
+* [[`2aa6a6d998`](https://github.com/nodejs/node/commit/2aa6a6d998)] - **fs**: return null error on readFile() success (Zheng Chaoping) [#3740](https://github.com/nodejs/node/pull/3740)
+* [[`c96400c572`](https://github.com/nodejs/node/commit/c96400c572)] - **gitignore**: don't ignore 'debug' in deps/npm (Rebecca Turner) [#3599](https://github.com/nodejs/node/pull/3599)
+* [[`a7f28a098e`](https://github.com/nodejs/node/commit/a7f28a098e)] - **http**: remove unneeded cb check from setTimeout() (Ashok Suthar) [#3631](https://github.com/nodejs/node/pull/3631)
+* [[`d2b5dcb2de`](https://github.com/nodejs/node/commit/d2b5dcb2de)] - **lib**: return boolean from child.send() (Rich Trott) [#3577](https://github.com/nodejs/node/pull/3577)
+* [[`5c54fa0095`](https://github.com/nodejs/node/commit/5c54fa0095)] - **module**: cache regular expressions (Evan Lucas) [#3869](https://github.com/nodejs/node/pull/3869)
+* [[`89285db128`](https://github.com/nodejs/node/commit/89285db128)] - **module**: remove unnecessary JSON.stringify (Andres Suarez) [#3578](https://github.com/nodejs/node/pull/3578)
+* [[`fd3f0d8e6e`](https://github.com/nodejs/node/commit/fd3f0d8e6e)] - **querystring**: Parse multiple separator characters (Yosuke Furukawa) [#3807](https://github.com/nodejs/node/pull/3807)
+* [[`75dbafc3f8`](https://github.com/nodejs/node/commit/75dbafc3f8)] - **repl**: To exit, press ^C again or type .exit. (Hemanth.HM) [#3368](https://github.com/nodejs/node/pull/3368)
+* [[`5073da0481`](https://github.com/nodejs/node/commit/5073da0481)] - **repl**: don't crash if cannot open history file (Evan Lucas) [#3630](https://github.com/nodejs/node/pull/3630)
+* [[`59cd28114d`](https://github.com/nodejs/node/commit/59cd28114d)] - **src**: Add missing va_end before return (Ömer Fadıl Usta) [#3565](https://github.com/nodejs/node/pull/3565)
+* [[`02e012e984`](https://github.com/nodejs/node/commit/02e012e984)] - **src**: force line buffering for stderr (Rich Trott) [#3701](https://github.com/nodejs/node/pull/3701)
+* [[`2498e29344`](https://github.com/nodejs/node/commit/2498e29344)] - **src**: Revert "nix stdin _readableState.reading" (Roman Reiss) [#3490](https://github.com/nodejs/node/pull/3490)
+* [[`65cd03cda6`](https://github.com/nodejs/node/commit/65cd03cda6)] - **src**: wrap source before doing syntax check (Evan Lucas) [#3587](https://github.com/nodejs/node/pull/3587)
+* [[`d72bb1e96a`](https://github.com/nodejs/node/commit/d72bb1e96a)] - ***Revert*** "**src**: fix stuck debugger process" (Ben Noordhuis) [#3585](https://github.com/nodejs/node/pull/3585)
+* [[`047abbd6eb`](https://github.com/nodejs/node/commit/047abbd6eb)] - **test**: move test-specific function out of common (Rich Trott) [#3871](https://github.com/nodejs/node/pull/3871)
+* [[`19a36ff355`](https://github.com/nodejs/node/commit/19a36ff355)] - **test**: fix flaky SmartOS test (Rich Trott) [#3830](https://github.com/nodejs/node/pull/3830)
+* [[`4bb27baf8d`](https://github.com/nodejs/node/commit/4bb27baf8d)] - **test**: skip test if FreeBSD jail will break it (Rich Trott) [#3839](https://github.com/nodejs/node/pull/3839)
+* [[`1c1e70864b`](https://github.com/nodejs/node/commit/1c1e70864b)] - **test**: fix path to module for repl test on Windows (Michael Cornacchia) [#3608](https://github.com/nodejs/node/pull/3608)
+* [[`413ca53107`](https://github.com/nodejs/node/commit/413ca53107)] - **test**: increase crypto strength for FIPS standard (Stefan Budeanu) [#3758](https://github.com/nodejs/node/pull/3758)
+* [[`2ec5e17d16`](https://github.com/nodejs/node/commit/2ec5e17d16)] - **test**: add test-zlib-flush-drain (Myles Borins) [#3534](https://github.com/nodejs/node/pull/3534)
+* [[`de707f0876`](https://github.com/nodejs/node/commit/de707f0876)] - **test**: add hasFipsCrypto to test/common.js (Stefan Budeanu) [#3756](https://github.com/nodejs/node/pull/3756)
+* [[`828b786e48`](https://github.com/nodejs/node/commit/828b786e48)] - **test**: add test for invalid DSA key size (Stefan Budeanu) [#3756](https://github.com/nodejs/node/pull/3756)
+* [[`252e810059`](https://github.com/nodejs/node/commit/252e810059)] - **test**: Fix test-cluster-worker-exit.js for AIX (Imran Iqbal) [#3666](https://github.com/nodejs/node/pull/3666)
+* [[`91248b1094`](https://github.com/nodejs/node/commit/91248b1094)] - **test**: run pipeline flood test in parallel (Rich Trott) [#3811](https://github.com/nodejs/node/pull/3811)
+* [[`583f58e5d6`](https://github.com/nodejs/node/commit/583f58e5d6)] - **test**: stronger crypto in test fixtures (Stefan Budeanu) [#3759](https://github.com/nodejs/node/pull/3759)
+* [[`2e67db3104`](https://github.com/nodejs/node/commit/2e67db3104)] - **test**: refactor test-http-pipeline-flood (Rich Trott) [#3636](https://github.com/nodejs/node/pull/3636)
+* [[`1ab59ab9b3`](https://github.com/nodejs/node/commit/1ab59ab9b3)] - **test**: fix flaky test test-http-pipeline-flood (Devin Nakamura) [#3636](https://github.com/nodejs/node/pull/3636)
+* [[`1c8a7c6351`](https://github.com/nodejs/node/commit/1c8a7c6351)] - **test**: enhance fs-watch-recursive test (Sakthipriyan Vairamani) [#2599](https://github.com/nodejs/node/pull/2599)
+* [[`81997840f2`](https://github.com/nodejs/node/commit/81997840f2)] - **test**: fix test-module-loading-error for musl (Hugues Malphettes) [#3657](https://github.com/nodejs/node/pull/3657)
+* [[`9cdceac782`](https://github.com/nodejs/node/commit/9cdceac782)] - **test**: use really invalid hostname (Sakthipriyan Vairamani) [#3711](https://github.com/nodejs/node/pull/3711)
+* [[`f3594e77b2`](https://github.com/nodejs/node/commit/f3594e77b2)] - **test**: fix test-net-persistent-keepalive for AIX (Imran Iqbal) [#3646](https://github.com/nodejs/node/pull/3646)
+* [[`81522480f1`](https://github.com/nodejs/node/commit/81522480f1)] - **test**: more regression tests for minDHSize option (Ben Noordhuis) [#3629](https://github.com/nodejs/node/pull/3629)
+* [[`935b97769e`](https://github.com/nodejs/node/commit/935b97769e)] - **test**: add regression test for 512 bits DH key (Ben Noordhuis) [#3629](https://github.com/nodejs/node/pull/3629)
+* [[`e302c33bb0`](https://github.com/nodejs/node/commit/e302c33bb0)] - **test**: mark http-pipeline-flood flaky (Rich Trott) [#3616](https://github.com/nodejs/node/pull/3616)
+* [[`5977963bce`](https://github.com/nodejs/node/commit/5977963bce)] - **test**: remove flaky designation from ls-no-sslv3 (Rich Trott) [#3620](https://github.com/nodejs/node/pull/3620)
+* [[`1e98d90db8`](https://github.com/nodejs/node/commit/1e98d90db8)] - **test**: add regression test for --debug-brk -e 0 (Ben Noordhuis) [#3585](https://github.com/nodejs/node/pull/3585)
+* [[`2f16be2b70`](https://github.com/nodejs/node/commit/2f16be2b70)] - **tls**: Use SHA1 for sessionIdContext in FIPS mode (Stefan Budeanu) [#3755](https://github.com/nodejs/node/pull/3755)
+* [[`05f0549b50`](https://github.com/nodejs/node/commit/05f0549b50)] - **tls**: copy client CAs and cert store on CertCb (Fedor Indutny) [#3537](https://github.com/nodejs/node/pull/3537)
+* [[`bea35424a2`](https://github.com/nodejs/node/commit/bea35424a2)] - **tools**: add tap output to cpplint (Johan Bergström) [#3448](https://github.com/nodejs/node/pull/3448)
+* [[`d036b35349`](https://github.com/nodejs/node/commit/d036b35349)] - **tools**: enforce `throw new Error()` with lint rule (Rich Trott) [#3714](https://github.com/nodejs/node/pull/3714)
+* [[`38bb0d864e`](https://github.com/nodejs/node/commit/38bb0d864e)] - **tools**: Use `throw new Error()` consistently (Rich Trott) [#3714](https://github.com/nodejs/node/pull/3714)
+* [[`e40d28283a`](https://github.com/nodejs/node/commit/e40d28283a)] - **tools**: update npm test tooling for 3.3.10+ (Rebecca Turner) [#3599](https://github.com/nodejs/node/pull/3599)
+* [[`cbd358ce33`](https://github.com/nodejs/node/commit/cbd358ce33)] - **tools**: fix gyp to work on MacOSX without XCode (Shigeki Ohtsu) [iojs/io.js#1325](https://github.com/iojs/io.js/pull/1325)
+* [[`3137e46cb8`](https://github.com/nodejs/node/commit/3137e46cb8)] - **tools**: update gyp to b3cef02 (Imran Iqbal) [#3487](https://github.com/nodejs/node/pull/3487)
+* [[`d61cb90ee3`](https://github.com/nodejs/node/commit/d61cb90ee3)] - **util**: use Object.create(null) for dictionary object (Minwoo Jung) [#3831](https://github.com/nodejs/node/pull/3831)
+* [[`9a45c21e6c`](https://github.com/nodejs/node/commit/9a45c21e6c)] - **util**: use regexp instead of str.replace().join() (qinjia) [#3689](https://github.com/nodejs/node/pull/3689)
+* [[`33ffc62670`](https://github.com/nodejs/node/commit/33ffc62670)] - **zlib**: only apply drain listener if given callback (Craig Cavalier) [#3534](https://github.com/nodejs/node/pull/3534)
+* [[`d70deabf90`](https://github.com/nodejs/node/commit/d70deabf90)] - **zlib**: pass kind to recursive calls to flush (Myles Borins) [#3534](https://github.com/nodejs/node/pull/3534)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.1.0/node-v5.1.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.1.0/node-v5.1.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.1.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.1.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.1.0/node-v5.1.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.1.0/node-v5.1.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.1.0/node-v5.1.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.1.0/<br>
+Documentation: https://nodejs.org/docs/v5.1.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+4752961731e579a26dd45d765f76e67f70683b0026c0035fc4c30d70c7baf4f0  node-v5.1.0-darwin-x64.tar.gz
+b5fe63b95720c4d76cfeba06fabbea2cc30ad346ce3c781476b55c1edae4512d  node-v5.1.0-darwin-x64.tar.xz
+2dd57f72e3dc7bcce841b2390edd6c8e6257ec41ed85aa4ad4d380a3685cb768  node-v5.1.0-headers.tar.gz
+f2c631510630f20b1ccd5f4abb3d63676bc6eec136423ebca87bc938578f10d9  node-v5.1.0-headers.tar.xz
+8e6eb18b4499c4c509b4132d3393121a7d344d4053400798614c843977696ff3  node-v5.1.0-linux-arm64.tar.gz
+9474ffa69fdd737570123558ed28933ab0c08e5b8ee9f8592a104db095daff33  node-v5.1.0-linux-arm64.tar.xz
+a6a64bf9d2e6b792505841b187eeb1c3ac971551840dab2a9a4a4719d1e7d150  node-v5.1.0-linux-armv6l.tar.gz
+0d1a715ae7b4bc4dc4c2dde448cbd2bbde235d30f0c52ee8ec820840493db2a3  node-v5.1.0-linux-armv6l.tar.xz
+c7bbb8c51bdaf9b46daffbebdc889ce561c8f7b6cdd3c804c5e8cb7314a4d40d  node-v5.1.0-linux-armv7l.tar.gz
+ba9f8443eaf46ca13454a568174da28591a01fd6e4bfeffdee2a77610d1a54b1  node-v5.1.0-linux-armv7l.tar.xz
+510e7a2e8639a3ea036f5f6a9f7a66037e3acf8d0c953aeac8d093dea7e41d4c  node-v5.1.0-linux-x64.tar.gz
+f08c2cadb965a4f85700e1b3a8645faf3192e8fefe5c740b4c581c0d6110ced1  node-v5.1.0-linux-x86.tar.gz
+a1088d6968a57a5e19c66628561c57825a7251045f3d20ab768b87c657bb87a0  node-v5.1.0.pkg
+eb4497a705e720e38ee71580c94c9d911922211dd5819eeb55d217f4f4839b69  node-v5.1.0-sunos-x64.tar.gz
+c59b474c8c43ceb0a368f07419f60f488f4b931ad43da1e4c8ac434c405b9ed6  node-v5.1.0-sunos-x64.tar.xz
+d51d05e57e77ca780f43e315a5477eee9fbb954822f473985ff6a8ce5d3b05ca  node-v5.1.0-sunos-x86.tar.gz
+7ebd42449b8998aae13b2741a7878b80b4e6b94fd693461800b4fe80adc4bb11  node-v5.1.0-sunos-x86.tar.xz
+25b2d3b7dd57fe47a483539fea240a3c6bbbdab4d89a45a812134cf1380ecb94  node-v5.1.0.tar.gz
+8f1235cfd61828084c0ebea3266faab231e0ec1a748f200a4bcfa02d5263eaea  node-v5.1.0.tar.xz
+d21c1bdff99c01983646af6f5a1448b81ec12527259a42d0ae5c30eaaf739ccc  node-v5.1.0-x64.msi
+31dff8ce817ebb7a30ad7a1588aeb7599c077398dad14b06aaaca61af611adae  node-v5.1.0-x86.msi
+237b38f781e5137b3f76658e1116f74557305d65e09e3211ad0842166a76795b  win-x64/node.exe
+f675ba445f63fa720fb3136de4375393972602dc1806b37470d907a309e414c7  win-x64/node.lib
+cedd73b96045b6c07007946c87725f2f6d98ca7cd92ba7eab9860befb873749a  win-x86/node.exe
+051086542859f57a829878977253a73b649279e8466f1d0f31ea75c73ff71d4e  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJWS6BnAAoJEEX17r2BPa6OciwQALg6PWKmWiyNDQdFRzexGk/P
+sN/MyZ3zdwm+1vz646xQ5CSMeO1Pdhz1StR6SdOe8LWvyyDgF3GgyzMO4tJv5QSW
+cNei+v4FpqrB70BkCnZL5vorFGe/Sz21bG2ghHvq5qEQ/TRZOlLhpRLsOkfCLh1E
+YZFq1hwXqnpaM9zCmSCnuJeJokLwYv/LAPKs4pSTfBVzt4vdZu3liL0swsnxNJmu
+tNXK5zSL2fWwa5CQS1Nq0+0i9ZuRcAkpUGN+bkURoo012144/CVK0INqT5+RBhqX
+AFDpNrZa78dC7wSIDTZgYebeQcAfS2uu4JiPmdV7GZgmMrA0HkxJk+1Kc34egmgF
+iw6Bs5G1hdDSGuKx4cZ/ObFkgbWMXmNEczbxVZOkIl2EI5yYFYt3qKGjXQJCKkOH
+mDjFMjJ8M9F6biZyKGfr2XcXs7g+SXB6JuqSAMohLJxjz2TWFwI12UfVP3fMgyTA
+GAuYzkFAmlTuUQe4kTrK8++XmQPjZtS19GBFwU1DN4v15uAa2mhW09ncU8q+rsI3
+zQczDfybsZd2umnhlssOCc3pIM+2brQ93ivvJMwX/ASicnDrGV98JfcYKSMnYLK0
+Dcs8jDyG0ctyoLAZ29Iga0t2EGTbXnJruxAJ4hWYN/Lc94RGxLbSjVqOsGN+sL00
+DxxpULMDf4Jmojgtg2+1
+=jm9B
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.1.1.md b/locale/uk/blog/release/v5.1.1.md
new file mode 100755
index 0000000000000..1d0ab366606f5
--- /dev/null
+++ b/locale/uk/blog/release/v5.1.1.md
@@ -0,0 +1,99 @@
+---
+date: 2015-12-04T03:04:00.000Z
+version: 5.1.1
+category: release
+title: Node v5.1.1 (Current)
+slug: node-v5-1-1
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+**This is an important security release**. All Node.js users should consult our [December Security Release Summary](/en/blog/vulnerability/december-2015-security-releases/) for details on patched vulnerabilities.
+
+### Notable changes
+
+* **http**: Fix a bug where an HTTP socket may no longer have an associated parser but a pipelined request triggers a pause or resume, a potential denial-of-service vector. (Fedor Indutny)
+* **openssl**: Upgrade to 1.0.2e, containing fixes for:
+  - CVE-2015-3193 "BN_mod_exp may produce incorrect results on x86_64", an attack may be feasible against a Node.js TLS server using DHE key exchange. Details are available at <http://openssl.org/news/secadv/20151203.txt>.
+  - CVE-2015-3194 "Certificate verify crash with missing PSS parameter", a potential denial-of-service vector for Node.js TLS servers using client authentication; TLS clients are also impacted. Details are available at <http://openssl.org/news/secadv/20151203.txt>.
+  (Shigeki Ohtsu) [#4134](https://github.com/nodejs/node/pull/4134)
+* **v8**: Backport fixes for a bug in `JSON.stringify()` that can result in out-of-bounds reads for arrays. (Ben Noordhuis)
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`678398f250`](https://github.com/nodejs/node/commit/678398f250)] - **deps**: backport a7e50a5 from upstream v8 (Ben Noordhuis)
+* [[`76a552c938`](https://github.com/nodejs/node/commit/76a552c938)] - **deps**: backport 6df9a1d from upstream v8 (Ben Noordhuis)
+* [[`533881f889`](https://github.com/nodejs/node/commit/533881f889)] - **deps**: upgrade openssl sources to 1.0.2e (Shigeki Ohtsu) [#4134](https://github.com/nodejs/node/pull/4134)
+* [[`12e70fafd3`](https://github.com/nodejs/node/commit/12e70fafd3)] - **http**: fix pipeline regression (Fedor Indutny)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.1.1/node-v5.1.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.1.1/node-v5.1.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.1.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.1.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.1.1/node-v5.1.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.1.1/node-v5.1.1-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.1.1/node-v5.1.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.1.1/<br>
+Documentation: https://nodejs.org/docs/v5.1.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+cb6c831e7c3a8432a14a0e4ddb2000295c0166abce06b2d50134cc2cccb2dc9c  node-v5.1.1-darwin-x64.tar.gz
+12566e3edfc24ad0efebcfa20ceed79ca87811bafe2c8b92432ff4614885c6ef  node-v5.1.1-darwin-x64.tar.xz
+cc320d0a3df073e9e92816d5698d69ade780ce854f26146539f0b29cb5be616a  node-v5.1.1-headers.tar.gz
+f0dba3ef1f953a8ebb4c610a1279a48ed1ba57fe24ab7783fd0fedadeaba3f9c  node-v5.1.1-headers.tar.xz
+1723abf50ee9b2b2209af06374523ae657c5562166bdc44b7b8d32801484c572  node-v5.1.1-linux-arm64.tar.gz
+5fefa92daf840076947a7ac2e97bcd2dcf35e1c632251b5ba73357318c8a7a1f  node-v5.1.1-linux-arm64.tar.xz
+e7b154a5f7574155df5e3b5df90af762ab0edde128e36eeac0bd8ba2a8f00697  node-v5.1.1-linux-armv6l.tar.gz
+30011d4caca9d07e076c11beed7e2c67c0e4e3b20ac29cb80d479db1131ab78f  node-v5.1.1-linux-armv6l.tar.xz
+fd96f77310708097cf9e783b9842122a4e2859674965734b7b22a615cb756165  node-v5.1.1-linux-armv7l.tar.gz
+ac0b4e73a180406883d8c5700623966093f0442988facf024d59129fa9017434  node-v5.1.1-linux-armv7l.tar.xz
+0c1a0788dfc07d1cfac08b9789f0e52950e80e61944e1684b27600463a5d2623  node-v5.1.1-linux-x64.tar.gz
+0de39988d293434eedb2c78e48dddfa5cb7c7f77cb4a1e6c2e4af4d44caf10aa  node-v5.1.1-linux-x64.tar.xz
+30099a0f305899aacdfd974873807b6bd8b6971c0a26209220a6e4cd88c08d70  node-v5.1.1-linux-x86.tar.gz
+e00bf38d9e24b4631ea0ff089ffeea39f37512900ca9e50628e716ecb0083184  node-v5.1.1-linux-x86.tar.xz
+7311f4848381ded99fd5415e818337efb9b9138656fbab80eb5fcf7f42d7bde8  node-v5.1.1.pkg
+14dfdf63f1ac8c9972199e7a62d8c732cf269e081aec6caa9e0e3f46d116d486  node-v5.1.1-sunos-x64.tar.gz
+1c45a06cd78ef236cfb331a43677ca514b1e5f9d52603c608fae998986f43cfb  node-v5.1.1-sunos-x64.tar.xz
+11ccaadb1e22b3c80548686caf19070c34017667866285fe8b6cb8b9e6afca30  node-v5.1.1-sunos-x86.tar.gz
+3971913cfce5182b626b761e7435811837542424da8d84d146383b37bba6ff95  node-v5.1.1-sunos-x86.tar.xz
+a779e024f800b5ec51f375fa1c14eda7254216daa36a1960cc1e4195b9fc22c3  node-v5.1.1.tar.gz
+b3aaa01051576425afce753d30b16be67f391222ff445b0c716ccf9e12d1b94b  node-v5.1.1.tar.xz
+d008ca8791145cf64db1a6ffc177fd70766619953d46570a1e39258c23001ed2  node-v5.1.1-x64.msi
+cea518f4bccc4818f77f09bb7c6e77a1b84d3cff91f2316d9d1596bf0af484bb  node-v5.1.1-x86.msi
+482cc88532d945e9e867c7f25f8182062dc8446b4457a6906a4bfdfafae9b947  win-x64/node.exe
+82feb5cf14a34da483795ba2c012e63d405f36125912f6ac7584072618bf46da  win-x64/node.lib
+0e86bac3fd75a07631b8048cd69dd515105a4e4c5bd300716bbf8678afce758e  win-x86/node.exe
+ed4c4367f53e14e5bd3feb35446aa3f1f533892455fc646cd5efa8b7cfce24dc  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWYPxuAAoJEMJzeS99g1RdDagIAKhiCiWHO3jRsTew/tHxROuQ
+AA88yXh2SHafXgkE5/iSxAb/oecOOZLQGjg3MrIZnwgZJweqjFmePLc6XiEZNDU5
+FiN/8SUTknW8no30SIr6yaE7S//Lw1xpeZLgYsjcqeKJ32P11hQ1TdfbXIigR0AM
+EhZs4m55X76mD4+wn6LnZeQxoxdXtsk+HHhNGesPOiNw0dpaVidkWqzISvSHy6lS
+zTD35CUdmjaHezu680il2WED3aublrRBwTmaXowUHnUGI0JQtUDkcA9ohMrfqO8F
+PwoGrXDYw8YIZWUux4Jc3kBbgA+PsyVWw31hdT1mJjYqP9SIaGIbsh1j1dCsC7g=
+=8elM
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.10.0.md b/locale/uk/blog/release/v5.10.0.md
new file mode 100755
index 0000000000000..18b879542a63a
--- /dev/null
+++ b/locale/uk/blog/release/v5.10.0.md
@@ -0,0 +1,164 @@
+---
+date: 2016-04-01T03:31:50.474Z
+version: 5.10.0
+category: release
+title: Node v5.10.0 (Current)
+slug: node-v5-10-0
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+This release includes a security update for npm. For more details you can read 
+[this post on our blog](https://nodejs.org/en/blog/vulnerability/npm-tokens-leak-march-2016/) 
+written by [Forrest L Norvell](https://github.com/othiym23) from npm.
+
+### Notable changes
+
+* **buffer**:
+  * make byteLength work with ArrayBuffer & DataView (Jackson Tian) [#5255](https://github.com/nodejs/node/pull/5255)
+  * backport --zero-fill-buffers command line option (James M Snell) [#5744](https://github.com/nodejs/node/pull/5744)
+  * backport new buffer constructor APIs (James M Snell) [#5763](https://github.com/nodejs/node/pull/5763)
+  * add swap16() and swap32() methods (James M Snell) [#5724](https://github.com/nodejs/node/pull/5724)
+* **fs**: add the fs.mkdtemp() function. (Florian MARGAINE) [#5333](https://github.com/nodejs/node/pull/5333)
+* **net**: emit host in lookup event (HUANG Wei) [#5598](https://github.com/nodejs/node/pull/5598)
+* **node**: --no-browser-globals configure flag (Fedor Indutny) [#5853](https://github.com/nodejs/node/pull/5853)
+* **npm**: Upgrade to v3.8.3. Fixes a security flaw in the use of authentication tokens in HTTP requests that 
+  would allow an attacker to set up a server that could collect tokens from users of the command-line interface. 
+  Authentication tokens have previously been sent with every request made by the CLI for logged-in users, 
+  regardless of the destination of the request. This update fixes this by only including those tokens for requests 
+  made against the registry or registries used for the current install. (Forrest L Norvell) [npm/node#6](https://github.com/npm/node/pull/6)
+* **repl**: support standalone blocks (Prince J Wesley) [#5581](https://github.com/nodejs/node/pull/5581)
+* **src**: override v8 thread defaults using cli options (Tom Gallacher) [#4344](https://github.com/nodejs/node/pull/4344)
+
+### Commits
+
+* [[`2cbbaafca9`](https://github.com/nodejs/node/commit/2cbbaafca9)] - **async_wrap**: don't abort on callback exception (Trevor Norris) [#5756](https://github.com/nodejs/node/pull/5756)
+* [[`6f16882733`](https://github.com/nodejs/node/commit/6f16882733)] - **async_wrap**: notify post if intercepted exception (Trevor Norris) [#5756](https://github.com/nodejs/node/pull/5756)
+* [[`a4856122d3`](https://github.com/nodejs/node/commit/a4856122d3)] - **async_wrap**: setupHooks now accepts object (Trevor Norris) [#5756](https://github.com/nodejs/node/pull/5756)
+* [[`ee83c956c5`](https://github.com/nodejs/node/commit/ee83c956c5)] - **(SEMVER-MINOR)** **buffer**: make byteLength work with ArrayBuffer & DataView (Jackson Tian) [#5255](https://github.com/nodejs/node/pull/5255)
+* [[`1f8e4b54ce`](https://github.com/nodejs/node/commit/1f8e4b54ce)] - **(SEMVER-MINOR)** **buffer**: add swap16() and swap32() methods (James M Snell) [#5724](https://github.com/nodejs/node/pull/5724)
+* [[`bdf933bece`](https://github.com/nodejs/node/commit/bdf933bece)] - **buffer**: changing let in for loops back to var (Gareth Ellis) [#5819](https://github.com/nodejs/node/pull/5819)
+* [[`c1534e7eaf`](https://github.com/nodejs/node/commit/c1534e7eaf)] - **(SEMVER-MINOR)** **buffer**: backport new buffer constructor APIs (James M Snell) [#5763](https://github.com/nodejs/node/pull/5763)
+* [[`3c02727055`](https://github.com/nodejs/node/commit/3c02727055)] - **(SEMVER-MINOR)** **buffer**: backport --zero-fill-buffers command line option (James M Snell) [#5744](https://github.com/nodejs/node/pull/5744)
+* [[`58b5c1e19f`](https://github.com/nodejs/node/commit/58b5c1e19f)] - **build**: add suport for x86 architecture (Robert Chiras) [#5544](https://github.com/nodejs/node/pull/5544)
+* [[`389f5a85e6`](https://github.com/nodejs/node/commit/389f5a85e6)] - **build**: add script to create Android .mk files (Robert Chiras) [#5544](https://github.com/nodejs/node/pull/5544)
+* [[`5ee5fa292f`](https://github.com/nodejs/node/commit/5ee5fa292f)] - **build**: add missing `openssl_fips%` to common.gypi (Fedor Indutny) [#5919](https://github.com/nodejs/node/pull/5919)
+* [[`5681ffecf7`](https://github.com/nodejs/node/commit/5681ffecf7)] - **build**: enable compilation for linuxOne (Michael Dawson) [#5941](https://github.com/nodejs/node/pull/5941)
+* [[`660ec9f889`](https://github.com/nodejs/node/commit/660ec9f889)] - **child_process**: refactor self=this in socket_list (Benjamin Gruenbaum) [#5860](https://github.com/nodejs/node/pull/5860)
+* [[`e1a012f277`](https://github.com/nodejs/node/commit/e1a012f277)] - **deps**: upgrade npm to 3.8.3 (Forrest L Norvell) 
+* [[`ec1813199d`](https://github.com/nodejs/node/commit/ec1813199d)] - **deps**: backport 8d00c2c from v8 upstream (Ben Noordhuis) [#5577](https://github.com/nodejs/node/pull/5577)
+* [[`2a5c6d7006`](https://github.com/nodejs/node/commit/2a5c6d7006)] - **dns**: Refactor forEach to map (Benjamin Gruenbaum) [#5803](https://github.com/nodejs/node/pull/5803)
+* [[`6a6112a2f3`](https://github.com/nodejs/node/commit/6a6112a2f3)] - **dns**: Use object without protoype for map (Benjamin Gruenbaum) [#5843](https://github.com/nodejs/node/pull/5843)
+* [[`8fa0b5c1da`](https://github.com/nodejs/node/commit/8fa0b5c1da)] - **doc**: Add @mhdawson back to the CTC (James M Snell) [#5633](https://github.com/nodejs/node/pull/5633)
+* [[`858a524325`](https://github.com/nodejs/node/commit/858a524325)] - **doc**: typo: interal->internal. (Corey Kosak) [#5849](https://github.com/nodejs/node/pull/5849)
+* [[`5676a35bd9`](https://github.com/nodejs/node/commit/5676a35bd9)] - **doc**: explain path.format expected properties (John Eversole) [#5801](https://github.com/nodejs/node/pull/5801)
+* [[`29778393a0`](https://github.com/nodejs/node/commit/29778393a0)] - **doc**: use consistent event name parameter (Benjamin Gruenbaum) [#5850](https://github.com/nodejs/node/pull/5850)
+* [[`949b17ff6d`](https://github.com/nodejs/node/commit/949b17ff6d)] - **doc**: fix order of end tags of list after heading (firedfox) [#5874](https://github.com/nodejs/node/pull/5874)
+* [[`8e790b7a0c`](https://github.com/nodejs/node/commit/8e790b7a0c)] - **doc**: add instructions to only sign a release (Jeremiah Senkpiel) [#5876](https://github.com/nodejs/node/pull/5876)
+* [[`f1f9aff855`](https://github.com/nodejs/node/commit/f1f9aff855)] - **doc**: fix doc for Buffer.readInt32LE() (ghaiklor) [#5890](https://github.com/nodejs/node/pull/5890)
+* [[`731f7b8055`](https://github.com/nodejs/node/commit/731f7b8055)] - **etw**: fix descriptors of events 9 and 23 (João Reis) [#5742](https://github.com/nodejs/node/pull/5742)
+* [[`aac9ead379`](https://github.com/nodejs/node/commit/aac9ead379)] - **etw,build**: always generate .rc and .h files (João Reis) [#5657](https://github.com/nodejs/node/pull/5657)
+* [[`80155d398c`](https://github.com/nodejs/node/commit/80155d398c)] - **(SEMVER-MINOR)** **fs**: add the fs.mkdtemp() function. (Florian MARGAINE) [#5333](https://github.com/nodejs/node/pull/5333)
+* [[`ae15d68ad1`](https://github.com/nodejs/node/commit/ae15d68ad1)] - **governance**: remove target size for CTC (Rich Trott) [#5879](https://github.com/nodejs/node/pull/5879)
+* [[`63c601bc15`](https://github.com/nodejs/node/commit/63c601bc15)] - **http**: speed up checkIsHttpToken (Jackson Tian) [#4790](https://github.com/nodejs/node/pull/4790)
+* [[`40847b0b8b`](https://github.com/nodejs/node/commit/40847b0b8b)] - **lib**: rename /node.js to /bootstrap_node.js (Jeremiah Senkpiel) [#5103](https://github.com/nodejs/node/pull/5103)
+* [[`e644eb3d69`](https://github.com/nodejs/node/commit/e644eb3d69)] - **lib**: refactor code with startsWith/endsWith (Jackson Tian) [#5753](https://github.com/nodejs/node/pull/5753)
+* [[`a757e0583c`](https://github.com/nodejs/node/commit/a757e0583c)] - **lib,src**: move src/node.js to lib/internal/node.js (Jeremiah Senkpiel) [#5103](https://github.com/nodejs/node/pull/5103)
+* [[`e3c7b46326`](https://github.com/nodejs/node/commit/e3c7b46326)] - **lib,src**: refactor src/node.js into internal files (Jeremiah Senkpiel) [#5103](https://github.com/nodejs/node/pull/5103)
+* [[`b07bc5d996`](https://github.com/nodejs/node/commit/b07bc5d996)] - **(SEMVER-MINOR)** **net**: emit host in lookup event (HUANG Wei) [#5598](https://github.com/nodejs/node/pull/5598)
+* [[`2fa959be15`](https://github.com/nodejs/node/commit/2fa959be15)] - **(SEMVER-MINOR)** **node**: --no-browser-globals configure flag (Fedor Indutny) [#5853](https://github.com/nodejs/node/pull/5853)
+* [[`a2ad21645f`](https://github.com/nodejs/node/commit/a2ad21645f)] - **querystring**: don't stringify bad surrogate pair (Brian White) [#5858](https://github.com/nodejs/node/pull/5858)
+* [[`427173204e`](https://github.com/nodejs/node/commit/427173204e)] - **(SEMVER-MINOR)** **repl**: support standalone blocks (Prince J Wesley) [#5581](https://github.com/nodejs/node/pull/5581)
+* [[`d044898495`](https://github.com/nodejs/node/commit/d044898495)] - **src**: Add missing `using v8::MaybeLocal` (Anna Henningsen) [#5974](https://github.com/nodejs/node/pull/5974)
+* [[`0d0c57ff5e`](https://github.com/nodejs/node/commit/0d0c57ff5e)] - **(SEMVER-MINOR)** **src**: override v8 thread defaults using cli options (Tom Gallacher) [#4344](https://github.com/nodejs/node/pull/4344)
+* [[`f9d0166291`](https://github.com/nodejs/node/commit/f9d0166291)] - **src**: reword command and add ternary (Trevor Norris) [#5756](https://github.com/nodejs/node/pull/5756)
+* [[`f1488bb24c`](https://github.com/nodejs/node/commit/f1488bb24c)] - **src,http_parser**: remove KickNextTick call (Trevor Norris) [#5756](https://github.com/nodejs/node/pull/5756)
+* [[`8e8768ecbb`](https://github.com/nodejs/node/commit/8e8768ecbb)] - **test**: add known_issues test for GH-2148 (Rich Trott) [#5920](https://github.com/nodejs/node/pull/5920)
+* [[`bf94b5a1b9`](https://github.com/nodejs/node/commit/bf94b5a1b9)] - **test**: mitigate flaky test-https-agent (Rich Trott) [#5939](https://github.com/nodejs/node/pull/5939)
+* [[`2192528326`](https://github.com/nodejs/node/commit/2192528326)] - **test**: fix flaky test-repl (Brian White) [#5914](https://github.com/nodejs/node/pull/5914)
+* [[`aebe6245b7`](https://github.com/nodejs/node/commit/aebe6245b7)] - **test**: add test for piping large input from stdin (Anna Henningsen) [#5949](https://github.com/nodejs/node/pull/5949)
+* [[`a19de97d2f`](https://github.com/nodejs/node/commit/a19de97d2f)] - **test**: remove the use of curl in the test suite (Santiago Gimeno) [#5750](https://github.com/nodejs/node/pull/5750)
+* [[`6928a17aa3`](https://github.com/nodejs/node/commit/6928a17aa3)] - **test**: exclude new fs watch test for AIX (Michael Dawson) [#5937](https://github.com/nodejs/node/pull/5937)
+* [[`3238bff3b3`](https://github.com/nodejs/node/commit/3238bff3b3)] - **test**: confirm globals not used internally (Rich Trott) [#5882](https://github.com/nodejs/node/pull/5882)
+* [[`a41fd93f68`](https://github.com/nodejs/node/commit/a41fd93f68)] - **test**: fix flaky test-net-socket-timeout (Brian White) [#5902](https://github.com/nodejs/node/pull/5902)
+* [[`82a50d3def`](https://github.com/nodejs/node/commit/82a50d3def)] - **test**: move dns test to test/internet (Ben Noordhuis) [#5905](https://github.com/nodejs/node/pull/5905)
+* [[`fb0c5bcac2`](https://github.com/nodejs/node/commit/fb0c5bcac2)] - **test**: fix flaky test-http-set-timeout (Rich Trott) [#5856](https://github.com/nodejs/node/pull/5856)
+* [[`8344a522a8`](https://github.com/nodejs/node/commit/8344a522a8)] - **test**: fix test-debugger-client.js (Rich Trott) [#5851](https://github.com/nodejs/node/pull/5851)
+* [[`7ec5397954`](https://github.com/nodejs/node/commit/7ec5397954)] - **timers**: fixing API refs to use safe internal refs (Kyle Simpson) [#5882](https://github.com/nodejs/node/pull/5882)
+* [[`cb676cf3e7`](https://github.com/nodejs/node/commit/cb676cf3e7)] - **tools**: fix json doc generation (firedfox) [#5943](https://github.com/nodejs/node/pull/5943)
+* [[`77bed269ad`](https://github.com/nodejs/node/commit/77bed269ad)] - **win,build**: build and test add-ons on test-ci (Bogdan Lobor) [#5886](https://github.com/nodejs/node/pull/5886)
+* [[`afcd276ecc`](https://github.com/nodejs/node/commit/afcd276ecc)] - **zlib**: Fix handling of gzip magic bytes mid-file (Anna Henningsen) [#5863](https://github.com/nodejs/node/pull/5863)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.10.0/node-v5.10.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.10.0/node-v5.10.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.10.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.10.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.10.0/node-v5.10.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.10.0/node-v5.10.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.10.0/node-v5.10.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.10.0/<br>
+Documentation: https://nodejs.org/docs/v5.10.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+00407892416649f7567cc20ae6f0c091650dee6186fe58eb33d2bd886f276799  node-v5.10.0-darwin-x64.tar.gz
+32bb55aa33da388e0ffb653678b1598511a12e9664ff42ff80e9072e75cbad3a  node-v5.10.0-darwin-x64.tar.xz
+726c61ca135198ef238078ab4f4f5a7ccd1980d049f08f2e1f2dd767c510f000  node-v5.10.0-headers.tar.gz
+ab520da8a88f00cdab394eb2064a293ab549f44d91f03cf3c20b671cfee48834  node-v5.10.0-headers.tar.xz
+df88803bda234b32240906b620315c8f6d6200332047a88cb0ec83009cf25dd5  node-v5.10.0-linux-arm64.tar.gz
+bee70770110caa640bc56d3da40a80de8a5c0f5c2bfc8b7363b9372c0a321faa  node-v5.10.0-linux-arm64.tar.xz
+019a257faa5eebf6304686dfeffdbcb4c22f0547aa366f6e563aad39ab1b1ab1  node-v5.10.0-linux-armv6l.tar.gz
+a9b085d19b8abac65ffa245d2959c2ff697b3a26b904be964a0b3c797c1e8d24  node-v5.10.0-linux-armv6l.tar.xz
+3f7524d3db60175c2323bb2a0a13ad1ca7d47d4ede6f42834b6b8425be70e0a2  node-v5.10.0-linux-armv7l.tar.gz
+e2988e55b603d08705137bb26690abe8c870144c5674f8c20a643df8c4833281  node-v5.10.0-linux-armv7l.tar.xz
+07058fb1c82e7cd3d21729ab6a5ed5523fdb9f664d975438974668710b7d8ec6  node-v5.10.0-linux-ppc64le.tar.gz
+05d9ecab3d2e9e82cd6ca046dcb7389b4e8d322a5ee6acc3948bbbeb0f475180  node-v5.10.0-linux-ppc64le.tar.xz
+a458ddab5f8d071c9b4f24ccfa685aedd57ccf7338c3ea0e2b99546cf35a3958  node-v5.10.0-linux-x64.tar.gz
+6e6442d1a44a0df0949ef7ade04caf43d994205e65ca57f97303b6462fa90377  node-v5.10.0-linux-x64.tar.xz
+e884f070542f49f577fd9785f09cf7734e6c2107d23b6c1b58453d43183c5ec0  node-v5.10.0-linux-x86.tar.gz
+fa3d63bfc2e6497b8ce5c5d7d6cde69e36669b246f2fe6ad0811ce76bf1d70d6  node-v5.10.0-linux-x86.tar.xz
+581fda48da967e8f5d3ba5ea5e1f6e12e689b91ee26393f398ab261dfe1fcfd2  node-v5.10.0.pkg
+78017489238f8ac86176079d1aa73cd8c40849f410d705080e00345512de8c93  node-v5.10.0-sunos-x64.tar.gz
+94f1963a760a2b874baafd856b610708dfcdf857bd6423b7f613c53384ee8ce7  node-v5.10.0-sunos-x64.tar.xz
+f9540debe8a396158f21a47f275d2fff564b42193f6621960d04c959e8ac5cc3  node-v5.10.0-sunos-x86.tar.gz
+202afe2bae1fa483ded7e6317af7a1445ab01f6cb390b32d8ba1473920bc231f  node-v5.10.0-sunos-x86.tar.xz
+8faeb9af5bde641b6e5dfae32bfa99253df2bccf59cf8a62162760026411762b  node-v5.10.0.tar.gz
+e3cc8e84b38b2d86ddf802f690eacabd97f5e32d37b9c70e19ecfdd2bef6e13a  node-v5.10.0.tar.xz
+d2c6cf6664e8fdb01d7078dd25191149ba44f6f2b4b5b2e441d2a25b1db12809  node-v5.10.0-x64.msi
+b807fb855048df7cae320aa55c4eca902a745dafc96571f720d9d3e1c129bd97  node-v5.10.0-x86.msi
+a37a8698d74a0204de958e53f1c44b158f0e46719664f2bdd195c3538b0ecacb  win-x64/node.exe
+7563f3c29e4b66a885dfaa9e3023eaec316dfb0e5cdbc98c1a8c09aa1049e759  win-x64/node.lib
+878b6c8a10622966a11dae7934f72dfb6abbe75896a21bd277acaa4076473187  win-x86/node.exe
+dc50c17be9a65d8e49939f497d73b7cb8b785c5aac5b20c28dc35dd286113064  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJW/en1AAoJELY7U1pMIGyp5F0QAKEASK8atK36nh0kVWIEftfo
+ttvy73f+6uAIPiTplGuGy8n3z0kh1i9FcEpstJaJnzNVcosZl4tNY1IZfASFHHjt
+xrybtRqpVmTR7ocLqEODDtqMNqKH/m+j7yhiGpewuDwSwIoXOM3nCj3axrVKFodV
+izYeInTBjIbr7KZmbTlDipLctMJfT7jGCZVR5bVYla5AEL7R9LHtecmDk7j5p3qu
+eEjohgAxcazam81LaG5YV6PNdL8wbZ5QmOAeQb47yZh6ZOal+kEtautQMb0N5eea
+F5CyFCPthhOuiU+Gg0KVeQI6S2bIq7N0RXPSFuwiXmosBXn57LtXN9Mw6GwXbRoJ
+YZQTOpaE20LJ/h3Vi1mx0cS6dRdsj5SaG/ks/q0t16S4Niybys7u7ZofteOThcjV
+6suuUM5WHCcfm5N8ABZtINZwth9za0bJkwSN8GhCugCDFWxk89zMnniQ9YIpSbWm
+WMN3JMWovyeRgicpje5sXRdBlfv26+FWN2VJ8C65RPQWGQHDm6WNb8ImTrjTqzI6
+mwcDfh98qYCVhWQ8laBfaVKweQLR4BhhLJSscFEjhOeu4TlA3ymKRgUvi9XnbX5b
+gwqGKpTfmwMzudgxRCqZHtPL1LMR3LGEztTk4mVXvPtr6lefYvIrnzZW2PffTEbS
+ZuQFj1HhTZwxX1mx0MpM
+=SX5M
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.10.1.md b/locale/uk/blog/release/v5.10.1.md
new file mode 100755
index 0000000000000..3cf7ec6eead04
--- /dev/null
+++ b/locale/uk/blog/release/v5.10.1.md
@@ -0,0 +1,117 @@
+---
+date: 2016-04-05T23:33:44.892Z
+version: 5.10.1
+category: release
+title: Node v5.10.1 (Current)
+slug: node-v5-10-1
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable changes
+
+**http**:
+  * Enclose IPv6 Host header in square brackets. This will enable proper seperation of the host adress from any port reference (Mihai Potra) [#5314](https://github.com/nodejs/node/pull/5314)
+
+**path**:
+  * Make win32.isAbsolute more consistent (Brian White) [#6028](https://github.com/nodejs/node/pull/6028)
+
+### Commits
+
+* [[`0f5a51ae4b`](https://github.com/nodejs/node/commit/0f5a51ae4b)] - **assert**: Check typed array view type in deepEqual (Anna Henningsen) [#5910](https://github.com/nodejs/node/pull/5910)
+* [[`e966d1f5db`](https://github.com/nodejs/node/commit/e966d1f5db)] - **buffer**: don't set `kNoZeroFill` flag in allocUnsafe (Vladimir Kurchatkin) [#6007](https://github.com/nodejs/node/pull/6007)
+* [[`3f75751c2e`](https://github.com/nodejs/node/commit/3f75751c2e)] - **build**: introduce ci targets for lint/benchmark (Johan Bergström) [#5921](https://github.com/nodejs/node/pull/5921)
+* [[`781290b61d`](https://github.com/nodejs/node/commit/781290b61d)] - **doc**: refine child_process detach behaviour (Robert Jefe Lindstaedt) [#5330](https://github.com/nodejs/node/pull/5330)
+* [[`aa9fb03202`](https://github.com/nodejs/node/commit/aa9fb03202)] - **doc**: use HTTPS for links where possible (Rich Trott) [#6019](https://github.com/nodejs/node/pull/6019)
+* [[`dd25984838`](https://github.com/nodejs/node/commit/dd25984838)] - **doc**: note assert.throws() pitfall (Rich Trott) [#6029](https://github.com/nodejs/node/pull/6029)
+* [[`f879f5e68a`](https://github.com/nodejs/node/commit/f879f5e68a)] - **doc**: document unspecified behavior for buf.write* methods (James M Snell) [#5925](https://github.com/nodejs/node/pull/5925)
+* [[`f12c3861e0`](https://github.com/nodejs/node/commit/f12c3861e0)] - **doc**: clarify stdout/stderr arguments to callback (James M Snell) [#6015](https://github.com/nodejs/node/pull/6015)
+* [[`ce173716be`](https://github.com/nodejs/node/commit/ce173716be)] - **doc**: add 'Command Line Options' to 'View on single page' (firedfox) [#6011](https://github.com/nodejs/node/pull/6011)
+* [[`7337ef6422`](https://github.com/nodejs/node/commit/7337ef6422)] - **doc**: minor argument formatting in stream.markdown (James M Snell) [#6016](https://github.com/nodejs/node/pull/6016)
+* [[`0ae5d027c6`](https://github.com/nodejs/node/commit/0ae5d027c6)] - **doc**: clarify that __dirname is module local (James M Snell) [#6018](https://github.com/nodejs/node/pull/6018)
+* [[`8bec8aa41f`](https://github.com/nodejs/node/commit/8bec8aa41f)] - **doc**: consolidate timers docs in timers.markdown (Bryan English) [#5837](https://github.com/nodejs/node/pull/5837)
+* [[`0a13099c42`](https://github.com/nodejs/node/commit/0a13099c42)] - **etw**: add event messages (João Reis) [#5936](https://github.com/nodejs/node/pull/5936)
+* [[`c6ac6f2ea1`](https://github.com/nodejs/node/commit/c6ac6f2ea1)] - **http**: Corrects IPv6 address in Host header (Mihai Potra) [#5314](https://github.com/nodejs/node/pull/5314)
+* [[`8317778925`](https://github.com/nodejs/node/commit/8317778925)] - **meta**: add "joining a wg" section to WORKING_GROUPS.md (Matteo Collina) [#5488](https://github.com/nodejs/node/pull/5488)
+* [[`f3f19ee5e2`](https://github.com/nodejs/node/commit/f3f19ee5e2)] - **net**: refactor self=this to arrow functions (Benjamin Gruenbaum) [#5857](https://github.com/nodejs/node/pull/5857)
+* [[`1c4007927d`](https://github.com/nodejs/node/commit/1c4007927d)] - **path**: fix win32.isAbsolute() inconsistency (Brian White) [#6028](https://github.com/nodejs/node/pull/6028)
+* [[`059b607a4f`](https://github.com/nodejs/node/commit/059b607a4f)] - **test**: make use of globals explicit (Rich Trott) [#6014](https://github.com/nodejs/node/pull/6014)
+* [[`cc8fcc5a07`](https://github.com/nodejs/node/commit/cc8fcc5a07)] - **test**: be explicit about polluting of `global` (Rich Trott) [#6017](https://github.com/nodejs/node/pull/6017)
+* [[`7db7a820b9`](https://github.com/nodejs/node/commit/7db7a820b9)] - **test**: make arch available in status files (Santiago Gimeno) [#5997](https://github.com/nodejs/node/pull/5997)
+* [[`02f2ebd9b4`](https://github.com/nodejs/node/commit/02f2ebd9b4)] - **test**: explicitly set global in test-repl (Rich Trott) [#6026](https://github.com/nodejs/node/pull/6026)
+* [[`2ab1237137`](https://github.com/nodejs/node/commit/2ab1237137)] - **test**: fix flaky test-net-socket-timeout-unref (Rich Trott) [#6003](https://github.com/nodejs/node/pull/6003)
+* [[`0127c2bd39`](https://github.com/nodejs/node/commit/0127c2bd39)] - **test**: fix test-dns.js flakiness (Rich Trott) [#5996](https://github.com/nodejs/node/pull/5996)
+* [[`6052ced37f`](https://github.com/nodejs/node/commit/6052ced37f)] - **test**: fix error message checks in test-module-loading (James M Snell) [#5986](https://github.com/nodejs/node/pull/5986)
+* [[`a40b0cb673`](https://github.com/nodejs/node/commit/a40b0cb673)] - **test**: refactor http-end-throw-socket-handling (Santiago Gimeno) [#5676](https://github.com/nodejs/node/pull/5676)
+* [[`96bb315262`](https://github.com/nodejs/node/commit/96bb315262)] - **test**: ensure _handle property existence (Rich Trott) [#5916](https://github.com/nodejs/node/pull/5916)
+* [[`4f1fa2adeb`](https://github.com/nodejs/node/commit/4f1fa2adeb)] - **test**: fix offending max-len linter error (Sakthipriyan Vairamani) [#5980](https://github.com/nodejs/node/pull/5980)
+* [[`f14d71ccea`](https://github.com/nodejs/node/commit/f14d71ccea)] - **test**: stdin is not always a net.Socket (Jeremiah Senkpiel) [#5935](https://github.com/nodejs/node/pull/5935)
+* [[`50a062e691`](https://github.com/nodejs/node/commit/50a062e691)] - **tools**: remove obsolete lint config file (Rich Trott) [#5959](https://github.com/nodejs/node/pull/5959)
+* [[`7491fdcfe9`](https://github.com/nodejs/node/commit/7491fdcfe9)] - **tools**: remove disabling of already-disabled rule (Rich Trott) [#6013](https://github.com/nodejs/node/pull/6013)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.10.1/node-v5.10.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.10.1/node-v5.10.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.10.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.10.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.10.1/node-v5.10.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.10.1/node-v5.10.1-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.10.1/node-v5.10.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.10.1/<br>
+Documentation: https://nodejs.org/docs/v5.10.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+00ffc5c662580e1a5062a8740a9b9a40dbf7dadb5c8aa16bdf0ed33c7c1dfbfb  node-v5.10.1-darwin-x64.tar.gz
+52d6103a14690c4541e6924d28687b23dbcf65cd171a50529db0998004e888c7  node-v5.10.1-darwin-x64.tar.xz
+77e1469d6c2c6f49e68cb3fb8052ee90284700e7da013a7d47ad1cefcd8afc63  node-v5.10.1-headers.tar.gz
+a3c5c8f545ca320305128731f546a24387719768ccf5fa8a5e3059ee26f43370  node-v5.10.1-headers.tar.xz
+98e4f003818968d5b9bcf17c921d33a5e3d6866be63d80510ae7ff8877e817db  node-v5.10.1-linux-arm64.tar.gz
+2c264c596a9bf1a962b37ea51afa3540f819a1428627a28b6a25abe284eb04ab  node-v5.10.1-linux-arm64.tar.xz
+5d6f652ce962a0fb59edf5e305af3a7e9147489ebb90a1244f3fa67d86fcf54b  node-v5.10.1-linux-armv6l.tar.gz
+bfa551df4739d3f975c4114f1e87b0060bb1998d27b4916a0238561bd4478e7c  node-v5.10.1-linux-armv6l.tar.xz
+f1ccddf5fc894a4a4becdf9b32e579b2aad6c6ace189890dbdcb934afbaab060  node-v5.10.1-linux-armv7l.tar.gz
+d35134ec4c6ac723da20898c3061c11b71823e09167cf830ab56983cb33affeb  node-v5.10.1-linux-armv7l.tar.xz
+b7137dc0bc9a6e3a91be67f05330d2722d58b4e50047d3455a7c035c455701b4  node-v5.10.1-linux-ppc64le.tar.gz
+2bc959b36318c0a64b86e0eedbc5179b59db9a8b4f1577039182d7c283b1ffc2  node-v5.10.1-linux-ppc64le.tar.xz
+897506e1e83cba9b780b030c9cc7299b0ae8872c0b8b0081a86996079025cea5  node-v5.10.1-linux-x64.tar.gz
+edc2afd401d5bbbc05aee186e94ea21078bd4d733da0fc1e95cb8dfbae04bcc8  node-v5.10.1-linux-x64.tar.xz
+a4c17570bd03424cd57affd10a4ef7d3b76167d3646656236bc78b86bc622a88  node-v5.10.1-linux-x86.tar.gz
+d2fd77706d6b122f978ac68eba540e3ad8efb93909b56a1fe944af81b74b552e  node-v5.10.1-linux-x86.tar.xz
+9bf1a7a92debe7613e6ff0d1852aa09e8ed95cf01f276e71848d44235059423a  node-v5.10.1.pkg
+0cb823dacc340aa79b70a08d7d81a72260c3414b6f07398ab80e755efcc93f85  node-v5.10.1-sunos-x64.tar.gz
+780c323919d1912989784e5577212a56856e3ceb7eab11a8d3d43bf6a7da3582  node-v5.10.1-sunos-x64.tar.xz
+1d2731f7ffb46d9f2153993f24ac36a5e98dd136ad28600e45d918205997403f  node-v5.10.1-sunos-x86.tar.gz
+75096b173bbbd920b2039b3ede985025f0c8dc91f999224626163d3cb9458cb5  node-v5.10.1-sunos-x86.tar.xz
+c6e278b612b53c240ddf85521403e55abfd8f0201d2f2c7e3d2c21383054aacd  node-v5.10.1.tar.gz
+9eecd853cdd06ebee24a1bb8d753cd20af5a19297c5d3a3b1680fe36b47d5cbe  node-v5.10.1.tar.xz
+a1207fa1e831c1347d338546e353ea195d5cb1acb7e290dad8836153aad11c35  node-v5.10.1-x64.msi
+87a902472fe0458ee444456ef5a9bdbd9247c7747b4deeb7a7ded43e56b43daa  node-v5.10.1-x86.msi
+4985991e02af90ca5628a6f3e5aa8d913c72b1c898fa0202db47cb757b576ac9  win-x64/node.exe
+8b2c8cfb473fa45bf24567302c0f5adf4d573afc13d27797e717dc0696336f01  win-x64/node.lib
+bbf7ca1d2bb2c590d97e785bbc7fe0f5478b4ee586d47a0e95ca6cff1b9f968b  win-x86/node.exe
+23be78c07830ad80f1b188dd9ef38dc9e267728d1f09acd435b42914875ae89d  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJXBEq/AAoJEJM7AfQLXKlGLc8H/1tjkCtDxKsrVWCTdTA+L4nD
+qkptH/E78gmGSq6BjQUV/usfhJVvH4kot9OGjIAs9rJezSco+y2jLkNfo6gm4SSt
+tI6pFxrZDnBC+qtXcdCcfjXiRhmPVInJVLHnU0H6BhkMEHcyjyPHim+UNIfbmOB4
+MD+Lduqf6xe8VTscipPujXFsS6B2XT2pMFCAyUJqz2xd23QubAGWSLWJ/eK3P0h5
+hhC7EHoVDkVhlByRhuSK74yKqm8jb4Rtv1tYJi2UM8Ip/XQhM+YcLFV3+k7e5huu
+X7sIluHGRzjaqts4BR79Fr0i80yBL06b7JCDl8McMn1wfZPDG+E/iSnU/zfS7g8=
+=aUEi
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.11.0.md b/locale/uk/blog/release/v5.11.0.md
new file mode 100755
index 0000000000000..820c664df5e37
--- /dev/null
+++ b/locale/uk/blog/release/v5.11.0.md
@@ -0,0 +1,198 @@
+---
+date: 2016-04-21T20:35:53.135Z
+version: 5.11.0
+category: release
+title: Node v5.11.0 (Stable)
+slug: node-v5-11-0
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable Changes
+
+* **Buffer**:
+  * `Buffer.prototype.compare` can now compare sub-ranges of two Buffers. (James M Snell) [#5880](https://github.com/nodejs/node/pull/5880)
+* **deps**:
+  * update to http-parser 2.7.0 (Fedor Indutny) [#6279](https://github.com/nodejs/node/pull/6279)
+  * update ESLint to 2.7.0 (silverwind) [#6132](https://github.com/nodejs/node/pull/6132)
+* **net**:
+  * adds support for passing DNS lookup hints to `createConnection()` (Colin Ihrig) [#6000](https://github.com/nodejs/node/pull/6000) 
+* **node**:
+  * Make the builtin libraries available for the `--eval` and `--print` CLI options (Anna Henningsen) [#6207](https://github.com/nodejs/node/pull/6207)
+* **npm**:
+  * upgrade npm to 3.8.6 (Kat Marchán) [#6153](https://github.com/nodejs/node/pull/6153)
+* **repl**:
+  * Pressing enter in the repl will repeat the last command by default if no input has been received. This behaviour was in node previously and was not removed intentionally. (Rich Trott) [#6090](https://github.com/nodejs/node/pull/6090)
+* **src**:
+  * add SIGINFO to supported signals (James Reggio) [#6093](https://github.com/nodejs/node/pull/6093)
+* **streams**:
+  * Fix a regression that caused by net streams requesting multiple chunks synchronously when combined with cork/uncork (Matteo Collina) [#6164](https://github.com/nodejs/node/pull/6164)
+* **zlib**:
+  * The flushing flag is now configurable allowing for decompression of partial data (Anna Henningsen) [#6069](https://github.com/nodejs/node/pull/6069)
+
+### Commits
+
+* [[`14fcb1dded`](https://github.com/nodejs/node/commit/14fcb1dded)] - **assert**: respect assert.doesNotThrow message. (Ilya Shaisultanov) [#2407](https://github.com/nodejs/node/pull/2407)
+* [[`332f7382bb`](https://github.com/nodejs/node/commit/332f7382bb)] - **benchmark**: add module loader benchmark parameter (Brian White) [#5172](https://github.com/nodejs/node/pull/5172)
+* [[`473f086a94`](https://github.com/nodejs/node/commit/473f086a94)] - **(SEMVER-MINOR)** **buffer**: add Buffer.prototype.compare by offset (James M Snell) [#5880](https://github.com/nodejs/node/pull/5880)
+* [[`d44540f5af`](https://github.com/nodejs/node/commit/d44540f5af)] - **buffer**: standardize array index check (Trevor Norris) [#6084](https://github.com/nodejs/node/pull/6084)
+* [[`bd12d72e0c`](https://github.com/nodejs/node/commit/bd12d72e0c)] - **build**: fix make tar-headers for Linux (Gibson Fahnestock) [#5978](https://github.com/nodejs/node/pull/5978)
+* [[`3c8d404a82`](https://github.com/nodejs/node/commit/3c8d404a82)] - **build**: allow test-ci to run tests in parallel (Johan Bergström) [#6208](https://github.com/nodejs/node/pull/6208)
+* [[`a5f8d0c6ef`](https://github.com/nodejs/node/commit/a5f8d0c6ef)] - **build**: remove -f{data,function}-sections flags (Ben Noordhuis) [#6077](https://github.com/nodejs/node/pull/6077)
+* [[`adfb1a4bb0`](https://github.com/nodejs/node/commit/adfb1a4bb0)] - **child_process**: add nullptr checks after allocs (Anna Henningsen) [#6256](https://github.com/nodejs/node/pull/6256)
+* [[`1fb40524ee`](https://github.com/nodejs/node/commit/1fb40524ee)] - **(SEMVER-MINOR)** **debugger**: run last command on presssing enter (Rich Trott) [#6090](https://github.com/nodejs/node/pull/6090)
+* [[`5305831184`](https://github.com/nodejs/node/commit/5305831184)] - **deps**: update to http-parser 2.7.0 (Fedor Indutny) [#6279](https://github.com/nodejs/node/pull/6279)
+* [[`8ae200c768`](https://github.com/nodejs/node/commit/8ae200c768)] - **deps**: floating fix for npm's test-node script (Kat Marchán) [#6153](https://github.com/nodejs/node/pull/6153)
+* [[`e3e544eb96`](https://github.com/nodejs/node/commit/e3e544eb96)] - **deps**: upgrade npm to 3.8.6 (Kat Marchán) [#6153](https://github.com/nodejs/node/pull/6153)
+* [[`a7104e4516`](https://github.com/nodejs/node/commit/a7104e4516)] - **deps**: cherry-pick 1383d00 from v8 upstream (Fedor Indutny) [#6179](https://github.com/nodejs/node/pull/6179)
+* [[`632e6b9617`](https://github.com/nodejs/node/commit/632e6b9617)] - **deps**: backport 125ac66 from v8 upstream (Myles Borins) [#6086](https://github.com/nodejs/node/pull/6086)
+* [[`4b8376986a`](https://github.com/nodejs/node/commit/4b8376986a)] - **doc**: git mv to .md (Robert Jefe Lindstaedt) [#4747](https://github.com/nodejs/node/pull/4747)
+* [[`e6f4a175d4`](https://github.com/nodejs/node/commit/e6f4a175d4)] - **doc**: add full example for zlib.flush() (Anna Henningsen) [#6172](https://github.com/nodejs/node/pull/6172)
+* [[`50f3f10ce6`](https://github.com/nodejs/node/commit/50f3f10ce6)] - **doc**: note that zlib.flush acts after pending writes (Anna Henningsen) [#6172](https://github.com/nodejs/node/pull/6172)
+* [[`985685d170`](https://github.com/nodejs/node/commit/985685d170)] - **doc**: fix broken references (Alexander Gromnitsky) [#6100](https://github.com/nodejs/node/pull/6100)
+* [[`d66d883a85`](https://github.com/nodejs/node/commit/d66d883a85)] - **doc**: path.format provide more examples (John Eversole) [#5838](https://github.com/nodejs/node/pull/5838)
+* [[`dc1552e321`](https://github.com/nodejs/node/commit/dc1552e321)] - **doc**: replace functions with arrow functions (abouthiroppy) [#6203](https://github.com/nodejs/node/pull/6203)
+* [[`fa04dfc307`](https://github.com/nodejs/node/commit/fa04dfc307)] - **doc**: DCO anchor that doesn't change (William Kapke) [#6257](https://github.com/nodejs/node/pull/6257)
+* [[`b49a5b33b5`](https://github.com/nodejs/node/commit/b49a5b33b5)] - **doc**: fix http response event, Agent#getName (Matthew Douglass) [#5993](https://github.com/nodejs/node/pull/5993)
+* [[`3b00d7a5b1`](https://github.com/nodejs/node/commit/3b00d7a5b1)] - **doc**: document intention and dangers of fs module Buffer API (Nikolai Vavilov) [#6020](https://github.com/nodejs/node/pull/6020)
+* [[`3bc31526bb`](https://github.com/nodejs/node/commit/3bc31526bb)] - **doc**: explain differences in console.assert between node and browsers (James M Snell) [#6169](https://github.com/nodejs/node/pull/6169)
+* [[`3f73502662`](https://github.com/nodejs/node/commit/3f73502662)] - **doc**: native module reloading is not supported (Bryan English) [#6168](https://github.com/nodejs/node/pull/6168)
+* [[`5f9c8297f1`](https://github.com/nodejs/node/commit/5f9c8297f1)] - **doc**: clarify fs.watch() and inodes on linux, os x (Joran Dirk Greef) [#6099](https://github.com/nodejs/node/pull/6099)
+* [[`f3c0b78ae4`](https://github.com/nodejs/node/commit/f3c0b78ae4)] - **doc**: add domain postmortem (Trevor Norris) [#6159](https://github.com/nodejs/node/pull/6159)
+* [[`a91834e743`](https://github.com/nodejs/node/commit/a91834e743)] - **doc**: add stefanmb to collaborators (Stefan Budeanu) [#6227](https://github.com/nodejs/node/pull/6227)
+* [[`117348d082`](https://github.com/nodejs/node/commit/117348d082)] - **doc**: add iWuzHere to collaborators (Imran Iqbal) [#6226](https://github.com/nodejs/node/pull/6226)
+* [[`a1c46b63e8`](https://github.com/nodejs/node/commit/a1c46b63e8)] - **doc**: add santigimeno to collaborators (Santiago Gimeno) [#6225](https://github.com/nodejs/node/pull/6225)
+* [[`976e4bb3da`](https://github.com/nodejs/node/commit/976e4bb3da)] - **doc**: add addaleax to collaborators (Anna Henningsen) [#6224](https://github.com/nodejs/node/pull/6224)
+* [[`4fa949ef75`](https://github.com/nodejs/node/commit/4fa949ef75)] - **doc**: fix incorrect references in buffer docs (Amery) [#6194](https://github.com/nodejs/node/pull/6194)
+* [[`b26fea1595`](https://github.com/nodejs/node/commit/b26fea1595)] - **doc**: add copy about how to curl SHA256.txt (Myles Borins) [#6120](https://github.com/nodejs/node/pull/6120)
+* [[`daaad47099`](https://github.com/nodejs/node/commit/daaad47099)] - **doc**: clarification for maxBuffer and Unicode output (James M Snell) [#6030](https://github.com/nodejs/node/pull/6030)
+* [[`5e6915f374`](https://github.com/nodejs/node/commit/5e6915f374)] - **doc**: describe child.kill() pitfalls on linux (Robert Jefe Lindstaedt) [#2098](https://github.com/nodejs/node/issues/2098)
+* [[`a40d0e8f9d`](https://github.com/nodejs/node/commit/a40d0e8f9d)] - **doc**: fix scrolling on iOS devices (Luigi Pinca) [#5878](https://github.com/nodejs/node/pull/5878)
+* [[`a81fca4f99`](https://github.com/nodejs/node/commit/a81fca4f99)] - **doc**: add topic - event loop, timers, `nextTick()` (Jeff Harris) [#4936](https://github.com/nodejs/node/pull/4936)
+* [[`440d1172fd`](https://github.com/nodejs/node/commit/440d1172fd)] - **doc**: add example using algorithms not directly exposed (Brad Hill) [#6108](https://github.com/nodejs/node/pull/6108)
+* [[`96ad5c5303`](https://github.com/nodejs/node/commit/96ad5c5303)] - **doc**: update openssl LICENSE using license-builder.sh (Steven R. Loomis) [#6065](https://github.com/nodejs/node/pull/6065)
+* [[`07829b0bc9`](https://github.com/nodejs/node/commit/07829b0bc9)] - **doc**: simple doc typo fix (Brendon Pierson) [#6041](https://github.com/nodejs/node/pull/6041)
+* [[`bc0ee06226`](https://github.com/nodejs/node/commit/bc0ee06226)] - **doc**: note about Android support (Rich Trott) [#6040](https://github.com/nodejs/node/pull/6040)
+* [[`60a73a2ed2`](https://github.com/nodejs/node/commit/60a73a2ed2)] - **doc**: fix a typo in 5.10.1's changelog (Vladimir Varankin) [#6076](https://github.com/nodejs/node/pull/6076)
+* [[`b57be92c1b`](https://github.com/nodejs/node/commit/b57be92c1b)] - **gitignore**: adding .vs/ directory to .gitignore (Mike Kaufman) [#6070](https://github.com/nodejs/node/pull/6070)
+* [[`6e891c7ad4`](https://github.com/nodejs/node/commit/6e891c7ad4)] - **gitignore**: ignore VS 2015 *.VC.opendb files (Mike Kaufman) [#6070](https://github.com/nodejs/node/pull/6070)
+* [[`abd101be1a`](https://github.com/nodejs/node/commit/abd101be1a)] - **http**: disallow sending obviously invalid status codes (Brian White) [#6291](https://github.com/nodejs/node/pull/6291)
+* [[`16b23b2c28`](https://github.com/nodejs/node/commit/16b23b2c28)] - **http**: skip body and next message of CONNECT res (Fedor Indutny) [#6279](https://github.com/nodejs/node/pull/6279)
+* [[`a259ee4018`](https://github.com/nodejs/node/commit/a259ee4018)] - **http**: unref socket timer on parser execute (Fedor Indutny) [#6286](https://github.com/nodejs/node/pull/6286)
+* [[`d4abca5b27`](https://github.com/nodejs/node/commit/d4abca5b27)] - **lib**: remove bootstrap global context indirection (Jeremiah Senkpiel) [#5881](https://github.com/nodejs/node/pull/5881)
+* [[`c8783aff21`](https://github.com/nodejs/node/commit/c8783aff21)] - **lib,test,tools**: alignment on variable assignments (Rich Trott) [#6242](https://github.com/nodejs/node/pull/6242)
+* [[`d5d4f194f1`](https://github.com/nodejs/node/commit/d5d4f194f1)] - **net**: replace __defineGetter__ with defineProperty (Fedor Indutny) [#6284](https://github.com/nodejs/node/pull/6284)
+* [[`6d9c0c9aa7`](https://github.com/nodejs/node/commit/6d9c0c9aa7)] - **(SEMVER-MINOR)** **net**: support DNS hints in createConnection() (Colin Ihrig) [#6000](https://github.com/nodejs/node/pull/6000)
+* [[`457f24f19c`](https://github.com/nodejs/node/commit/457f24f19c)] - **(SEMVER-MINOR)** **node**: make builtin libs available for `--eval` (Anna Henningsen) [#6207](https://github.com/nodejs/node/pull/6207)
+* [[`fc89d17656`](https://github.com/nodejs/node/commit/fc89d17656)] - **path**: fixing a test that breaks on some machines. (Mike Kaufman) [#6067](https://github.com/nodejs/node/pull/6067)
+* [[`1d408099b7`](https://github.com/nodejs/node/commit/1d408099b7)] - **process**: fix incorrect usage of assert.fail() (Rich Trott) [#6211](https://github.com/nodejs/node/pull/6211)
+* [[`07c9f981d6`](https://github.com/nodejs/node/commit/07c9f981d6)] - **(SEMVER-MINOR)** **repl**: keep the built-in modules non-enumerable (Anna Henningsen) [#6207](https://github.com/nodejs/node/pull/6207)
+* [[`5382deaa18`](https://github.com/nodejs/node/commit/5382deaa18)] - **repl**: don’t complete non-simple expressions (Anna Henningsen) [#6192](https://github.com/nodejs/node/pull/6192)
+* [[`2254f1a175`](https://github.com/nodejs/node/commit/2254f1a175)] - **repl**: refactor repl.js (Rich Trott) [#6071](https://github.com/nodejs/node/pull/6071)
+* [[`7d54d85269`](https://github.com/nodejs/node/commit/7d54d85269)] - **(SEMVER-MINOR)** **src**: add SIGINFO to supported signals (James Reggio) [#6093](https://github.com/nodejs/node/pull/6093)
+* [[`fbc99ba4f1`](https://github.com/nodejs/node/commit/fbc99ba4f1)] - **src**: add missing 'inline' keywords (Ben Noordhuis) [#6056](https://github.com/nodejs/node/pull/6056)
+* [[`20bb92f5c8`](https://github.com/nodejs/node/commit/20bb92f5c8)] - **src**: use size_t for http parser array size fields (Ben Noordhuis) [#5969](https://github.com/nodejs/node/pull/5969)
+* [[`2fd8be2dbe`](https://github.com/nodejs/node/commit/2fd8be2dbe)] - **src**: replace ARRAY_SIZE with typesafe arraysize (Ben Noordhuis) [#5969](https://github.com/nodejs/node/pull/5969)
+* [[`4392b4aee0`](https://github.com/nodejs/node/commit/4392b4aee0)] - **stream**: Fix readableState.awaitDrain mechanism (Anna Henningsen) [#6023](https://github.com/nodejs/node/pull/6023)
+* [[`20dcdd365b`](https://github.com/nodejs/node/commit/20dcdd365b)] - **stream_base**: expose `bytesRead` getter (Fedor Indutny) [#6284](https://github.com/nodejs/node/pull/6284)
+* [[`f69416c06e`](https://github.com/nodejs/node/commit/f69416c06e)] - **streams**: support unlimited synchronous cork/uncork cycles (Matteo Collina) [#6164](https://github.com/nodejs/node/pull/6164)
+* [[`4bfed26d1a`](https://github.com/nodejs/node/commit/4bfed26d1a)] - **test**: add zlib close-after-error regression test (Anna Henningsen) [#6270](https://github.com/nodejs/node/pull/6270)
+* [[`99d0a61441`](https://github.com/nodejs/node/commit/99d0a61441)] - **test**: move more tests from sequential to parallel (Santiago Gimeno) [#6187](https://github.com/nodejs/node/pull/6187)
+* [[`96be986a77`](https://github.com/nodejs/node/commit/96be986a77)] - **test**: assert - fixed error messages to match the tests (surya panikkal) [#6241](https://github.com/nodejs/node/pull/6241)
+* [[`4e4efb756e`](https://github.com/nodejs/node/commit/4e4efb756e)] - **test**: add test for responses to HTTP CONNECT req (Josh Leder) [#6279](https://github.com/nodejs/node/pull/6279)
+* [[`5b42ef5dfe`](https://github.com/nodejs/node/commit/5b42ef5dfe)] - **test**: move debugger tests to sequential (Rich Trott) [#6205](https://github.com/nodejs/node/pull/6205)
+* [[`9856b804e9`](https://github.com/nodejs/node/commit/9856b804e9)] - **test**: move some test from sequential to parallel (Santiago Gimeno) [#6087](https://github.com/nodejs/node/pull/6087)
+* [[`1d130d0203`](https://github.com/nodejs/node/commit/1d130d0203)] - **test**: move the debugger tests back to parallel (Santiago Gimeno) [#6246](https://github.com/nodejs/node/pull/6246)
+* [[`c0e9c94868`](https://github.com/nodejs/node/commit/c0e9c94868)] - **test**: fix issues for ESLint 2.7.0 (silverwind) [#6132](https://github.com/nodejs/node/pull/6132)
+* [[`056a258173`](https://github.com/nodejs/node/commit/056a258173)] - **test**: fix flaky test-http-set-timeout-server (Santiago Gimeno) [#6248](https://github.com/nodejs/node/pull/6248)
+* [[`be993fcf6c`](https://github.com/nodejs/node/commit/be993fcf6c)] - **test**: fix test-net-settimeout flakiness (Santiago Gimeno) [#6166](https://github.com/nodejs/node/pull/6166)
+* [[`a38b614ae9`](https://github.com/nodejs/node/commit/a38b614ae9)] - **test**: fix flaky test-child-process-fork-net (Rich Trott) [#6138](https://github.com/nodejs/node/pull/6138)
+* [[`476535cc0e`](https://github.com/nodejs/node/commit/476535cc0e)] - **test**: fix flaky test-http-client-abort (Rich Trott) [#6124](https://github.com/nodejs/node/pull/6124)
+* [[`6bb7999bd6`](https://github.com/nodejs/node/commit/6bb7999bd6)] - **test**: refactor test-file-write-stream3 (Rich Trott) [#6050](https://github.com/nodejs/node/pull/6050)
+* [[`a27e95231e`](https://github.com/nodejs/node/commit/a27e95231e)] - **test**: enforce strict mode for test-domain-crypto (Rich Trott) [#6047](https://github.com/nodejs/node/pull/6047)
+* [[`8da4bad1c9`](https://github.com/nodejs/node/commit/8da4bad1c9)] - **test**: fix pummel test failures (Rich Trott) [#6012](https://github.com/nodejs/node/pull/6012)
+* [[`edd8a15508`](https://github.com/nodejs/node/commit/edd8a15508)] - **test,repl**: use deepStrictEqual for false-y values (Jeremiah Senkpiel) [#6196](https://github.com/nodejs/node/pull/6196)
+* [[`48ecc0b6b5`](https://github.com/nodejs/node/commit/48ecc0b6b5)] - **test,tools**: enable linting for undefined vars (Rich Trott) [#6255](https://github.com/nodejs/node/pull/6255)
+* [[`d809c84bf8`](https://github.com/nodejs/node/commit/d809c84bf8)] - **test,vm**: enable strict mode for vm tests (Rich Trott) [#6209](https://github.com/nodejs/node/pull/6209)
+* [[`4a1dfdcc0f`](https://github.com/nodejs/node/commit/4a1dfdcc0f)] - **tools**: lint rule for assert.fail() (Rich Trott) [#6261](https://github.com/nodejs/node/pull/6261)
+* [[`fff6a84da5`](https://github.com/nodejs/node/commit/fff6a84da5)] - **tools**: enable linting for v8_prof_processor.js (Rich Trott) [#6262](https://github.com/nodejs/node/pull/6262)
+* [[`a2ca347803`](https://github.com/nodejs/node/commit/a2ca347803)] - **tools**: move message listener to worker objects (Brian White) [#6212](https://github.com/nodejs/node/pull/6212)
+* [[`f201b01bf7`](https://github.com/nodejs/node/commit/f201b01bf7)] - **tools**: improve js linter (Brian White) [#5638](https://github.com/nodejs/node/pull/5638)
+* [[`be070d775f`](https://github.com/nodejs/node/commit/be070d775f)] - **tools**: lint for alignment of variable assignments (Rich Trott) [#6242](https://github.com/nodejs/node/pull/6242)
+* [[`d9b8758f47`](https://github.com/nodejs/node/commit/d9b8758f47)] - **tools**: update ESLint to 2.7.0 (silverwind) [#6132](https://github.com/nodejs/node/pull/6132)
+* [[`a6056c453e`](https://github.com/nodejs/node/commit/a6056c453e)] - **tools**: fix license-builder.sh again for ICU (Steven R. Loomis) [#6068](https://github.com/nodejs/node/pull/6068)
+* [[`fabc33a075`](https://github.com/nodejs/node/commit/fabc33a075)] - **tools**: remove simplejson dependency (Sakthipriyan Vairamani) [#6101](https://github.com/nodejs/node/pull/6101)
+* [[`d516412cd5`](https://github.com/nodejs/node/commit/d516412cd5)] - **tools,doc**: parse types in braces everywhere (Alexander Makarenko) [#5329](https://github.com/nodejs/node/pull/5329)
+* [[`69eb4a6834`](https://github.com/nodejs/node/commit/69eb4a6834)] - **tools,doc**: fix json for grouped optional params (firedfox) [#5977](https://github.com/nodejs/node/pull/5977)
+* [[`a2dd848764`](https://github.com/nodejs/node/commit/a2dd848764)] - **tools,doc**: fix incomplete json produced by doctool (firedfox) [#5966](https://github.com/nodejs/node/pull/5966)
+* [[`bad006f2e1`](https://github.com/nodejs/node/commit/bad006f2e1)] - **zlib**: fix use after null when calling .close (James Lal) [#5982](https://github.com/nodejs/node/pull/5982)
+* [[`83bc0a2ac9`](https://github.com/nodejs/node/commit/83bc0a2ac9)] - **(SEMVER-MINOR)** **zlib**: Make the finish flush flag configurable (Anna Henningsen) [#6069](https://github.com/nodejs/node/pull/6069)
+* [[`2c23e14d5d`](https://github.com/nodejs/node/commit/2c23e14d5d)] - **(SEMVER-MINOR)** **zlib**: detect gzip files when using unzip* (Anna Henningsen) [#5884](https://github.com/nodejs/node/pull/5884)
+* [[`61167c3e23`](https://github.com/nodejs/node/commit/61167c3e23)] - **zlib**: fix gzip member head/buffer boundary issue (Anna Henningsen) [#5973](https://github.com/nodejs/node/pull/5973)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.11.0/node-v5.11.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.11.0/node-v5.11.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.11.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.11.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.11.0/node-v5.11.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.11.0/node-v5.11.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.11.0/node-v5.11.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.11.0/<br>
+Documentation: https://nodejs.org/docs/v5.11.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+4992e1ba18cdac51383a089b1494131dbca465a5328938dbd4835cbf780f7ecc  node-v5.11.0-darwin-x64.tar.gz
+b450fc3f380c23f98e800abb4feb79760b54ddbc1e504c23f69ac87fabc942be  node-v5.11.0-darwin-x64.tar.xz
+d6850717f78dd94238510ec3cb804181a6bd152397def7de4a90dedf08a0eae1  node-v5.11.0-headers.tar.gz
+ab0b262cf38de15aa8930d6f497173062832e09f47c95257e8fa433f31e7ab58  node-v5.11.0-headers.tar.xz
+b6cc0dd471f07b607367b76a3f2ec1f11d9bc05f2fccbcda7b85ce76d31a3e2a  node-v5.11.0-linux-arm64.tar.gz
+646fc0e65744fa8bb5af552ba4727fb588a327aab905bbae3b510a1498951f3f  node-v5.11.0-linux-arm64.tar.xz
+6bf29cbf6d78e95a895bfb77774fde49fc3a565d601320b91b7ed5849f01a08d  node-v5.11.0-linux-armv6l.tar.gz
+9873fb842c1e632c89a6aa18a1c2bb97abb6860e93d4128e0098cef2cb619753  node-v5.11.0-linux-armv6l.tar.xz
+c07487fab4434f667a4b456fab098deffa76d73853e6636ebe05045e7db875de  node-v5.11.0-linux-armv7l.tar.gz
+f5e6be7af2f06d63118d181e5d7000c41599cb1b118c79fc8c38de0a52a9620c  node-v5.11.0-linux-armv7l.tar.xz
+6d267c7e1294d15d99747437ee74104b941111e7861382da84466c86d7fca139  node-v5.11.0-linux-ppc64le.tar.gz
+c8882683c4f02e6eec1b7442ddc9b60e01bfb964524ec9bc9d24f43c4c8fa624  node-v5.11.0-linux-ppc64le.tar.xz
+92602b815ce1c64c63b94d6f72f9b96b427415d023d5f9466c7ffef334bf0386  node-v5.11.0-linux-x64.tar.gz
+8fffbfc5152e05434f2ff2a80f2ae9fd08952bebd54f57ca731d8e3ffee855ef  node-v5.11.0-linux-x64.tar.xz
+f167a644eb6bf94f9a289d28d8140a6a497b02190571b02c7919458e12431ce0  node-v5.11.0-linux-x86.tar.gz
+b462a02a0e80c4eb35736a0c2e15c882c443bcceec51fd937bc979aa86efbf6d  node-v5.11.0-linux-x86.tar.xz
+a5637b0eb69df94b74744a60603344e6fbba0de9145b944a136474920b8f3d4d  node-v5.11.0.pkg
+386fed5acd84eb0d9efe958c951db2e9af2dd469d82e745179285b52a087b553  node-v5.11.0-sunos-x64.tar.gz
+20782223853cdfd0c64c18aa7ad5e2789e0a330fadfc79bb341562d54849ec9d  node-v5.11.0-sunos-x64.tar.xz
+44dd2e9bae4513bbf586fde1fea11ea310219feece915c21b3a45d4715e14c5e  node-v5.11.0-sunos-x86.tar.gz
+9bfd684df327d32e58bb7802c9eba9799a3e5e111720949b7339d11dabee8a4e  node-v5.11.0-sunos-x86.tar.xz
+ef41b01a9e49de5a5d160071166f911d0bc9ff6a0bd0e88ea4863df572d95e91  node-v5.11.0.tar.gz
+083766aff72fc5c78f6999dd0d00bc0340a052ab270fd60d6928b719ca2b3fd1  node-v5.11.0.tar.xz
+5d4185ca686c32fad6d62fa2fcea13f437a04f1fbec2e4ec19998189941c472b  node-v5.11.0-x64.msi
+51d7c57d2246d92fbeb325f3bb8b878452829e36edb57110b67e402913cdc194  node-v5.11.0-x86.msi
+47d7c3d295be704c7423cfe556b5da99816404c9bb18d49f30947f28b70d358c  win-x64/node.exe
+f09c4aa7056f16f019b55b4e592c87fa72a72a94e680545cfdfdcf7ea2cc2f7b  win-x64/node.lib
+7167ebafaf12659f0b8adc1853af1fbffc974ecc6b2d74ca4adfbabf21856dfe  win-x86/node.exe
+3bb913a5edcb70bbd73eaff625852ebafa843aca081294981a17408e0d0edd40  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+
+iQEcBAEBAgAGBQJXGTmPAAoJEJM7AfQLXKlGl8sH+wWBJ7sh6SaNEuzAPFGJHDg7
+DfnT5ZtdOmKhcFU1TNYv1UkoddhOYGuiU6o64+RaoRQVNTbrS0CktmbZNebe+Ar5
+SVNf4ZPVYsqf78lzHkxBgBV8ysxXWL0G0GbOYCbc8PxE8oAmJz+TN5gsxSe3rNci
+ksRISXLL0Nt91ef/CEjpODo9Lpf8onmnvFemXz7lm5kLBKZBUGVVRA1XAyg/MgEE
+IWlpaGVJRCifLooy+nHBe+cXMomNMZUQZDFitgesHmNbMgNk7jlxorCjrYm/R69f
+h7Ojc19+84SaALBwFQ/gqTo8MV47pqNodLo4xP5A8SEwGpDzzTNkVeio4Go64hc=
+=imFa
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.11.1.md b/locale/uk/blog/release/v5.11.1.md
new file mode 100755
index 0000000000000..1f10e11a51455
--- /dev/null
+++ b/locale/uk/blog/release/v5.11.1.md
@@ -0,0 +1,103 @@
+---
+date: 2016-05-05T23:00:21.696Z
+version: 5.11.1
+category: release
+title: Node v5.11.1 (Stable)
+slug: node-v5-11-1
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+Please see our [blog post](https://nodejs.org/en/blog/vulnerability/openssl-may-2016) for more info on the security contents of this release.
+
+### Notable changes
+
+* **buffer**: safeguard against accidental kNoZeroFill (Сковорода Никита Андреевич) [nodejs/node-private#35](https://github.com/nodejs/node-private/pull/35)
+* **deps**: upgrade openssl sources to 1.0.2h (Shigeki Ohtsu) [#6552](https://github.com/nodejs/node/pull/6552)
+
+### Commits
+
+* [[`35f06df782`](https://github.com/nodejs/node/commit/35f06df782)] - **buffer**: safeguard against accidental kNoZeroFill (Сковорода Никита Андреевич) [nodejs/node-private#35](https://github.com/nodejs/node-private/pull/35)
+* [[`99920480ae`](https://github.com/nodejs/node/commit/99920480ae)] - **buffer**: fix a typo in Buffer example code (Mr C0B) [#6361](https://github.com/nodejs/node/pull/6361)
+* [[`d9f7b025d4`](https://github.com/nodejs/node/commit/d9f7b025d4)] - **deps**: update openssl asm and asm_obsolete files (Shigeki Ohtsu) [#6552](https://github.com/nodejs/node/pull/6552)
+* [[`f316fd20a0`](https://github.com/nodejs/node/commit/f316fd20a0)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [#1836](https://github.com/nodejs/node/pull/1836)
+* [[`263cc34657`](https://github.com/nodejs/node/commit/263cc34657)] - **deps**: fix asm build error of openssl in x86_win32 (Shigeki Ohtsu) [#1389](https://github.com/nodejs/node/pull/1389)
+* [[`889d1151de`](https://github.com/nodejs/node/commit/889d1151de)] - **deps**: fix openssl assembly error on ia32 win32 (Fedor Indutny) [#1389](https://github.com/nodejs/node/pull/1389)
+* [[`ba49b636b8`](https://github.com/nodejs/node/commit/ba49b636b8)] - **deps**: copy all openssl header files to include dir (Shigeki Ohtsu) [#6552](https://github.com/nodejs/node/pull/6552)
+* [[`cdad83a789`](https://github.com/nodejs/node/commit/cdad83a789)] - **deps**: upgrade openssl sources to 1.0.2h (Shigeki Ohtsu) [#6552](https://github.com/nodejs/node/pull/6552)
+* [[`c1ddefdd79`](https://github.com/nodejs/node/commit/c1ddefdd79)] - **openssl**: fix keypress requirement in apps on win32 (Shigeki Ohtsu) [#1389](https://github.com/nodejs/node/pull/1389)
+* [[`bec5d50f1e`](https://github.com/nodejs/node/commit/bec5d50f1e)] - **test**: fix alpn tests for openssl1.0.2h (Shigeki Ohtsu) [#6552](https://github.com/nodejs/node/pull/6552)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.11.1/node-v5.11.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.11.1/node-v5.11.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.11.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.11.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.11.1/node-v5.11.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.11.1/node-v5.11.1-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.11.1/node-v5.11.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.11.1/<br>
+Documentation: https://nodejs.org/docs/v5.11.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+7a992f61dc535c696ba2e236e3664ba669680f7e1a204e42166412cc3476503a  node-v5.11.1-darwin-x64.tar.gz
+0fe7b4f9ad94777e642ba5efff0bd899e15fa9fb6799cd22794ac4bd5006cc23  node-v5.11.1-darwin-x64.tar.xz
+85072d2f231a947862984ec79f44b990287a6ba1589342c0ac4fea54d9ec88e2  node-v5.11.1-headers.tar.gz
+b2a607a0cfb1252014bc01007b7c4d7790c78ba9fbe009accf89c16c06257397  node-v5.11.1-headers.tar.xz
+8df5fa56ea1f79efc6f8baa9a6784bb1b0596fb7ef1d631694e35a89b3840de6  node-v5.11.1-linux-arm64.tar.gz
+cb09abcd897d44959069c17d29ce6361ad20bd15e94cf72c1c5cd0976a08fa91  node-v5.11.1-linux-arm64.tar.xz
+d6ffd43fd0546a5830117bb76979f074a04f9f2323bfc786ca5bd25f254149bc  node-v5.11.1-linux-armv6l.tar.gz
+a9f2c90cd7be087dff8f4fb15cf603c1bba9e95f23bd66958c41cbedc72e13a7  node-v5.11.1-linux-armv6l.tar.xz
+d69ebad9bb86e2d54b6c8774e5bfd055b507dfd4da4b4a0a9ad8543358fd57de  node-v5.11.1-linux-armv7l.tar.gz
+17db8b2a9221ea7455c4471198965a9b6d6bc0c97187265e64925826a072dcaa  node-v5.11.1-linux-armv7l.tar.xz
+a349b77703902702ec2ec35de27150d19f73ca44045577c577312a5bde9e0b04  node-v5.11.1-linux-ppc64le.tar.gz
+d0653882535519ddc6637a04eeb797b02a4ee708f14dd6cc4d84f44fcb65d0a3  node-v5.11.1-linux-ppc64le.tar.xz
+d8e30e79a1e4ad56f55ef59facdf913c950e9664528f59f4388e85fdd899dfde  node-v5.11.1-linux-x64.tar.gz
+35ffd25963254decbec1069da318597ed2fb032d2782f7cbdfdd41dc6af99ee9  node-v5.11.1-linux-x64.tar.xz
+5c8269b21400327eaae94f52d220127a90eca40ab7574f9da07811c48d25570f  node-v5.11.1-linux-x86.tar.gz
+01bcebec40d2030ebfd87fec82249fe1e2919bedcbc4998ee0b1c0365a33e7b4  node-v5.11.1-linux-x86.tar.xz
+f06c2d54057c55913749991a6636e78c4180b989a6ee67bdc0017252bfc6c9c9  node-v5.11.1.pkg
+65e80b25ba648b62faae99f4f4df86eeea6ed448c592cb638349a63eefcb5d0f  node-v5.11.1-sunos-x64.tar.gz
+61507107d14720f1dd24a25bea2bd626ebda63da5d495e5d8f2cdb1a5c03a696  node-v5.11.1-sunos-x64.tar.xz
+24e9095e7fdb1765d2acf569209a194b16c048374a804a97fc5fec123b1b9217  node-v5.11.1-sunos-x86.tar.gz
+c211f830ccb2198571f0e843101b7c9917ef0feae165c7e28a795b61798968a5  node-v5.11.1-sunos-x86.tar.xz
+be1211ce415ecc48412ce3e9d5b48cf9ec8e99b34f25b4e1909a02679cc72fab  node-v5.11.1.tar.gz
+f11bc3727e7ea74cffa940be258beaf1f81bee90537d13caa9e748ae6105661f  node-v5.11.1.tar.xz
+53c1744bfc845deb4c3a727d9e581f845c34652eb994a81f651a804f67ae749f  node-v5.11.1-x64.msi
+b7c6f647a037f17d1dbdb602af8c35934dd06fa4fb8b35108bb311cbddbcb2ab  node-v5.11.1-x86.msi
+df52219a3fde636f0fb73e065c85b28904eefd81c16c34ec5e6576b7fd0d886b  win-x64/node.exe
+fe0654ca23f0f3c5b290d76efd8f18ba6a6d60445257eb4d59641dc647d33770  win-x64/node.lib
+11160ea9fd4ae6db9c0fcee529cfae3d9fb3eed15a0428febbf6033c00494646  win-x86/node.exe
+fa3fa032d8b04e65ff20cd34bb0e690f5f88ca023d9783aa5672215f568117b1  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJXK8+rAAoJELY7U1pMIGypxY8QANK8IsVkwb0u1ycZO65j+zIn
+ChB6k+0f5wTo8ueIrq8uGNKyvYJpGmqN0/a7C61OGizfDMQcEXts+S4uEDkYDKlC
+qR+TiwbKQBEE52T7+jcJOnXb2A1aJFNAItNEq/GVM6mjxgxNBA3gM/9PMEoBvfHI
+hp5jF8CgKmc4ZfrYWUuHuycfeyuCu0/99TV9nS8EDLyFpgovEBRngGOmWmn/xV0h
+Gv9bu0Ixih6oOEHBL3+dH9BJ6Fvf75gsazumKsQSXyoa7f/JfoLPbT8ecUvS9Mm/
+JX+sNiNw9iBbx0iFSHVh03b5CsH/ateFalSDjKhNqOMykniUNI+FELs5/1/wU+6B
+VzniJpbRR9tU2A0FdARvbnFMj1KJfUmsXGRlh399k2OmD6IoYkWtbsHcyFB6vGXE
+F8w8UihBHQ69GAzTltQnyn3QO7s/0kF9UqozAJ3ApvA8Sq9cSIXmE1s5+a5GD+Cc
+btrehhpUOgUZQ2ol4N2BOuKVc+svUWgiZ5QF1e2lNdOWnYCP+fSFqkf5PRRd4xW2
+oMwnFO3Ehc5VSGHzVwGKfltmot+vkGD9xbDJZH1vCzYuj9zf66TbduPdFk0Exf0f
+1gp5Na7EypJRgcLjLVSRriXVz6WYybgbVbA+7WcDw8jmKYwHdMUIRMRUFGMy/uts
+YkqY3iJ4b5wydOEg+0Jt
+=nE6V
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.12.0.md b/locale/uk/blog/release/v5.12.0.md
new file mode 100755
index 0000000000000..00879bdd3cbbf
--- /dev/null
+++ b/locale/uk/blog/release/v5.12.0.md
@@ -0,0 +1,102 @@
+---
+date: 2016-06-23T23:31:02.257Z
+version: 5.12.0
+category: release
+title: Node v5.12.0 (Stable)
+slug: node-v5-12-0
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+### Notable changes
+
+This is a security release. All Node.js users should consult the security release summary at https://nodejs.org/en/blog/vulnerability/june-2016-security-releases for details on patched vulnerabilities.
+
+* **buffer**
+  * backport allocUnsafeSlow (Сковорода Никита Андреевич) [#7169](https://github.com/nodejs/node/pull/7169)
+  * ignore negative allocation lengths (Anna Henningsen) [#7221](https://github.com/nodejs/node/pull/7221)
+* **deps**: backport 3a9bfec from v8 upstream (Ben Noordhuis) [nodejs/node-private#40](https://github.com/nodejs/node-private/pull/40)
+  * Fixes a Buffer overflow vulnerability discovered in v8. More details can be found in the CVE (CVE-2016-1699).
+
+### Commits
+
+* [[`0ca0827b71`](https://github.com/nodejs/node/commit/0ca0827b71)] - **(SEMVER-MINOR)** **buffer**: backport allocUnsafeSlow (Сковорода Никита Андреевич) [#7169](https://github.com/nodejs/node/pull/7169)
+* [[`27785aeb37`](https://github.com/nodejs/node/commit/27785aeb37)] - **buffer**: ignore negative allocation lengths (Anna Henningsen) [#7221](https://github.com/nodejs/node/pull/7221)
+* [[`34b96c1322`](https://github.com/nodejs/node/commit/34b96c1322)] - **deps**: backport 3a9bfec from v8 upstream (Ben Noordhuis) [nodejs/node-private#40](https://github.com/nodejs/node-private/pull/40)
+* [[`2ebeb82852`](https://github.com/nodejs/node/commit/2ebeb82852)] - **test**: fix test-net-* error code check for getaddrinfo(3) (Natanael Copa) [#5099](https://github.com/nodejs/node/pull/5099)
+* [[`03d36aea4f`](https://github.com/nodejs/node/commit/03d36aea4f)] - **(SEMVER-MINOR)** **test**: add buffer testcase for resetting kZeroFill (Сковорода Никита Андреевич) [#7169](https://github.com/nodejs/node/pull/7169)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.12.0/node-v5.12.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.12.0/node-v5.12.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.12.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.12.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.12.0/node-v5.12.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.12.0/node-v5.12.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.12.0/node-v5.12.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.12.0/<br>
+Documentation: https://nodejs.org/docs/v5.12.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+bcbfb16896d4b13e08184343420ab00822e9ef09a72f9dbc41ef0cfcc84b99c2  node-v5.12.0-darwin-x64.tar.gz
+2778a6344e5285af6412c66ef967cd3da2edb3262f19c06e484a062191f43019  node-v5.12.0-darwin-x64.tar.xz
+a36e815ac5a4d7d3f486deda97359ae8e01d42259bf4a2be4fbbf41efd585c70  node-v5.12.0-headers.tar.gz
+27deab94f424f38202a6ea8e945a542da71fe8f0808d69899ba4a855293bbb92  node-v5.12.0-headers.tar.xz
+db02351d2c205a3c60218f937a41a8b8d665f326e7dfa263954ab39f8a8a2bc3  node-v5.12.0-linux-arm64.tar.gz
+3eeaed6ce895c551903164966f950533c200ac24f68bdaebaab0e29e9923dc6d  node-v5.12.0-linux-arm64.tar.xz
+f58b9db77eb82830157f814704e8c3b3ba3420079a8ded3ad39302a33e3a30af  node-v5.12.0-linux-armv6l.tar.gz
+88a102d0d2614b088987759089b9d4351e9941a2e7095350f352a5eb4eafd0c6  node-v5.12.0-linux-armv6l.tar.xz
+da51a7025772766453f330b3274a12381995e07d68c99c55357767171af4c538  node-v5.12.0-linux-armv7l.tar.gz
+6ac1d3ec0cd5cb797cb641bfd170bfb19ffe96967fc90ed166c710e8a0841b5f  node-v5.12.0-linux-armv7l.tar.xz
+5cde9c115aade3d3eac494106ad29a2e0743a19516aa8a4ed531783292c7641f  node-v5.12.0-linux-ppc64le.tar.gz
+0413665e0d3fca6c58fec9301485bcbbc6f0336d64c0a591121538a7f969bab6  node-v5.12.0-linux-ppc64le.tar.xz
+a57642f7aa59f7a5248fd5368217f7c7218ae889664ab8974af468797bbfa7bb  node-v5.12.0-linux-ppc64.tar.gz
+f9b252f201b29b10c7d774db79eddeae782a5b8d1478e0ed5146036d4dbe5bb2  node-v5.12.0-linux-ppc64.tar.xz
+c0f459152aa87aba8a019a95899352170db0d8d52c860715c88356cb253fe2c4  node-v5.12.0-linux-x64.tar.gz
+619fc1d14ee0c92894cf01bf1a47f5bae321ac04dfeb4cea6a2b6ce65832df79  node-v5.12.0-linux-x64.tar.xz
+1ee1ef4e9f8bfb2976f35ca10658f3828cae10ef462d3fee7c3f159a3e21365b  node-v5.12.0-linux-x86.tar.gz
+6a83c52fa00c72cbc90a94dc392636fa4a5f1543311a4838c6ad87f703d67200  node-v5.12.0-linux-x86.tar.xz
+8835e19bff36fe2a0120e8b189aa33ea87e99eb8b08605212a5ddb8fb63bcaf2  node-v5.12.0.pkg
+e5738517163e9409457ff2fe434aa410b70064ba8639a38173decc430a87c546  node-v5.12.0-sunos-x64.tar.gz
+d3f72ebebb31c081b794c09941184e4744852552b1b32e4121cdc129c41d6a58  node-v5.12.0-sunos-x64.tar.xz
+b3831faef7112f4bd71dd4dff3f2296c8ee1f4f8e7b3adfdd205caa91adde198  node-v5.12.0-sunos-x86.tar.gz
+ddd41de09925860e383ed55d0251e5040ff5637c6504c9a6891eb167d3ff74db  node-v5.12.0-sunos-x86.tar.xz
+250c12a561d7319e71e142ee92ab682494c7823d81ce24703c80eb52bdf9ba42  node-v5.12.0.tar.gz
+4f926373f11f2a25156eee1804ec012eb912c42e5d34fc2909889da22efdadfe  node-v5.12.0.tar.xz
+afc6be86edc989c40a7019dfce370819448a2b43c1a641d12ee9efc6391a23a8  node-v5.12.0-x64.msi
+b3fc857e4925418ec43063606ce01134f91a20be8c7b6a0dbf0a9093636b40f9  node-v5.12.0-x86.msi
+cf27938a7fb5c983eb46cf9f27190016832d254ed96227d7720af299d2d75f1e  win-x64/node.exe
+2938e21edafdb5bfaabc7ea14b34c77b9d8af4a7a5d389178ca902c06f5a3d6b  win-x64/node.lib
+92c22479607ab269eae7c6040cb059757fd0a29ddc188d3a25e46ee485e6e221  win-x86/node.exe
+aebf98d723036e2a3c458baf21a93eb45f1a42da794fc29dc47d01b5c70dae3d  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJXbG57AAoJELY7U1pMIGypxHIQAKJnkwx/SDOJGquRw1Wl4V9W
+A6NzAzRDfCE2NYeglWMqinTjSFJkeYP98z4x63cE9uctxJns23z+PfPkRHZDbsSB
+Y/mHAm5ntbk8cndISgBiK55QiFaYzVFaw3A1XoIozTGR4irbPbaj28iUbY4T8q2+
+O3GfcDKD+SXS1AtTZ+P2GE6rxE0qkBYHMxM7b7lD5VXnzGr4Cyg4jSaD7w6PK2yG
+u986AW9EJjKigZtvy3nkO27+ZNx3jDNskWBpT6YjhAKSs18/qTGHgOL2Jtk6rdfv
+Vd/sumfIIlDUFXT/g01/leYbOHyIMmQYASm5XBA5UBoQuuapRvCVAe0SuRKe/9wV
+bD/DfDORzdJUuebvdxx9K+iMbFGD2ADKmFAomjxyTynZup0VrmeSUQtbpGucp0X/
+16Li8NDBD4WRXHYjcqXujJ4+cs/DZ6DUuqloCcB4cigs4sAyuqPVnZu5HTfBMzox
+T1HWbDh2hE6HqsXcYbCM1G7yXLH7VTGaJJifZNP1AL2C24Xa8zWbhOAcJ4JB1Z8J
+NQ2nW68AnXMh54PJhR/aBQLj3BC16i3RbWc8bhu85SpTVAO4y8W6i14FALJapXNz
+6tEa/LTc9aH5RiugUfZzWBBdl/FfdeKyRofaN7PbJwTqo7XCJxZ11wbYwYR35Edo
+4nsbRK+UN1gwWqSMvLXz
+=H+Rd
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.2.0.md b/locale/uk/blog/release/v5.2.0.md
new file mode 100755
index 0000000000000..8cc5d4204ed11
--- /dev/null
+++ b/locale/uk/blog/release/v5.2.0.md
@@ -0,0 +1,201 @@
+---
+date: 2015-12-09T05:24:54.976Z
+version: 5.2.0
+category: release
+title: Node v5.2.0 (Current)
+slug: node-v5-2-0
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes
+
+* **build**:
+  - Add support for Intel's VTune JIT profiling when compiled with `--enable-vtune-profiling`. For more information about VTune, see <https://software.intel.com/en-us/node/544211>. (Chunyang Dai) [#3785](https://github.com/nodejs/node/pull/3785).
+  - Properly enable V8 snapshots by default. Due to a configuration error, snapshots have been kept off by default when the intention is for the feature to be enabled. (Fedor Indutny) [#3962](https://github.com/nodejs/node/pull/3962).
+* **crypto**:
+  - Simplify use of ECDH (Elliptic Curve Diffie-Hellman) objects (created via `crypto.createECDH(curve_name)`) with private keys that are not dynamically generated via `generateKeys()`. The public key is now computed when explicitly setting a private key. Added validity checks to reduce the possibility of computing weak or invalid shared secrets. Also, deprecated the `setPublicKey()` method for ECDH objects as its usage is unnecessary and can lead to inconsistent state. (Michael Ruddy) [#3511](https://github.com/nodejs/node/pull/3511).
+  - Update root certificates from the current list stored maintained by Mozilla NSS. (Ben Noordhuis) [#3951](https://github.com/nodejs/node/pull/3951).
+  - Multiple CA certificates can now be passed with the `ca` option to TLS methods as an array of strings or in a single new-line separated string. (Ben Noordhuis) [#4099](https://github.com/nodejs/node/pull/4099)
+* **tools**: Include a tick processor in core, exposed via the `--prof-process` command-line argument which can be used to process V8 profiling output files generated when using the `--prof` command-line argument. (Matt Loring) [#4021](https://github.com/nodejs/node/pull/4021).
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`08a3f29fd4`](https://github.com/nodejs/node/commit/08a3f29fd4)] - **buffer**: fix range checking for slowToString (Matt Loring) [#4019](https://github.com/nodejs/node/pull/4019)
+* [[`e3a8e8bba4`](https://github.com/nodejs/node/commit/e3a8e8bba4)] - **buffer**: Prevent Buffer constructor deopt (Bryce Baril) [#4158](https://github.com/nodejs/node/pull/4158)
+* [[`0e18e68324`](https://github.com/nodejs/node/commit/0e18e68324)] - **buffer**: fix writeInt{B,L}E for some neg values (Peter A. Bigot) [#3994](https://github.com/nodejs/node/pull/3994)
+* [[`ab5b529dd2`](https://github.com/nodejs/node/commit/ab5b529dd2)] - **buffer**: default to UTF8 in byteLength() (Tom Gallacher) [#4010](https://github.com/nodejs/node/pull/4010)
+* [[`fcf0e8ebdf`](https://github.com/nodejs/node/commit/fcf0e8ebdf)] - **buffer**: move checkFloat from lib into src (Matt Loring) [#3763](https://github.com/nodejs/node/pull/3763)
+* [[`12649f4496`](https://github.com/nodejs/node/commit/12649f4496)] - **build**: add "--partly-static" build options (Super Zheng) [#4152](https://github.com/nodejs/node/pull/4152)
+* [[`a76d788119`](https://github.com/nodejs/node/commit/a76d788119)] - **build**: update signtool description, add url (Rod Vagg) [#4011](https://github.com/nodejs/node/pull/4011)
+* [[`ed255abdc1`](https://github.com/nodejs/node/commit/ed255abdc1)] - **(SEMVER-MINOR)** **build,src**: add Intel Vtune profiling support (Chunyang Dai) [#3785](https://github.com/nodejs/node/pull/3785)
+* [[`7793c364fc`](https://github.com/nodejs/node/commit/7793c364fc)] - **child_process**: flush consuming streams (Dave) [#4071](https://github.com/nodejs/node/pull/4071)
+* [[`f29c5d6e70`](https://github.com/nodejs/node/commit/f29c5d6e70)] - **configure**: `v8_use_snapshot` should be `true` (Fedor Indutny) [#3962](https://github.com/nodejs/node/pull/3962)
+* [[`da5ac55c83`](https://github.com/nodejs/node/commit/da5ac55c83)] - **(SEMVER-MINOR)** **crypto**: simplify using pre-existing keys with ECDH (Michael Ruddy) [#3511](https://github.com/nodejs/node/pull/3511)
+* [[`cfc97641ee`](https://github.com/nodejs/node/commit/cfc97641ee)] - **crypto**: fix native module compilation with FIPS (Stefan Budeanu) [#4023](https://github.com/nodejs/node/pull/4023)
+* [[`b81b45dabd`](https://github.com/nodejs/node/commit/b81b45dabd)] - **crypto**: update root certificates (Ben Noordhuis) [#3951](https://github.com/nodejs/node/pull/3951)
+* [[`def681a07e`](https://github.com/nodejs/node/commit/def681a07e)] - **crypto**: disable crypto.createCipher in FIPS mode (Stefan Budeanu) [#3754](https://github.com/nodejs/node/pull/3754)
+* [[`ce423f3624`](https://github.com/nodejs/node/commit/ce423f3624)] - **debugger**: introduce exec method for debugger (Jackson Tian)
+* [[`99fd1ec28d`](https://github.com/nodejs/node/commit/99fd1ec28d)] - **deps**: backport 819b40a from V8 upstream (Michaël Zasso) [#3937](https://github.com/nodejs/node/pull/3937)
+* [[`82252b2a17`](https://github.com/nodejs/node/commit/82252b2a17)] - **doc**: add brief Node.js overview to README (wurde) [#4174](https://github.com/nodejs/node/pull/4174)
+* [[`634c5f1f81`](https://github.com/nodejs/node/commit/634c5f1f81)] - **doc**: url.format - true slash postfix behaviour (fansworld-claudio) [#4119](https://github.com/nodejs/node/pull/4119)
+* [[`6f957a70d8`](https://github.com/nodejs/node/commit/6f957a70d8)] - **doc**: s/node.js/Node.js in readme (Rod Vagg) [#3998](https://github.com/nodejs/node/pull/3998)
+* [[`0cd4a52392`](https://github.com/nodejs/node/commit/0cd4a52392)] - **doc**: improve child_process.markdown wording (yorkie) [#4138](https://github.com/nodejs/node/pull/4138)
+* [[`fd5ed6888d`](https://github.com/nodejs/node/commit/fd5ed6888d)] - **doc**: add JungMinu to collaborators (Minwoo Jung) [#4143](https://github.com/nodejs/node/pull/4143)
+* [[`fa0cdf75d9`](https://github.com/nodejs/node/commit/fa0cdf75d9)] - **doc**: add iarna to collaborators (Rebecca Turner) [#4144](https://github.com/nodejs/node/pull/4144)
+* [[`424eb962b1`](https://github.com/nodejs/node/commit/424eb962b1)] - **doc**: add zkat to collaborators (Kat Marchán) [#4142](https://github.com/nodejs/node/pull/4142)
+* [[`85b601224b`](https://github.com/nodejs/node/commit/85b601224b)] - **doc**: add HTTP working group (James M Snell) [#3919](https://github.com/nodejs/node/pull/3919)
+* [[`f4164bd8df`](https://github.com/nodejs/node/commit/f4164bd8df)] - **doc**: update links to use https where possible (jpersson) [#4054](https://github.com/nodejs/node/pull/4054)
+* [[`3169eed1e3`](https://github.com/nodejs/node/commit/3169eed1e3)] - **doc**: add links and backticks around names (jpersson) [#4054](https://github.com/nodejs/node/pull/4054)
+* [[`f3417e2574`](https://github.com/nodejs/node/commit/f3417e2574)] - **doc**: standardize references to node.js in docs (Scott Buchanan) [#4136](https://github.com/nodejs/node/pull/4136)
+* [[`95dd60c657`](https://github.com/nodejs/node/commit/95dd60c657)] - **doc**: reword https.Agent example text (Jan Krems) [#4075](https://github.com/nodejs/node/pull/4075)
+* [[`c61237d3ea`](https://github.com/nodejs/node/commit/c61237d3ea)] - **doc**: fix internal link to child.send() (Luigi Pinca) [#4089](https://github.com/nodejs/node/pull/4089)
+* [[`aaeced915e`](https://github.com/nodejs/node/commit/aaeced915e)] - **doc**: fix the exception description (yorkie) [#3658](https://github.com/nodejs/node/pull/3658)
+* [[`a2b7596ac0`](https://github.com/nodejs/node/commit/a2b7596ac0)] - **doc**: fix color of linked code blocks (jpersson) [#4068](https://github.com/nodejs/node/pull/4068)
+* [[`f3c50f5fb5`](https://github.com/nodejs/node/commit/f3c50f5fb5)] - **doc**: fix rare case of misaligned columns (Roman Reiss) [#3948](https://github.com/nodejs/node/pull/3948)
+* [[`f0a2e2cdec`](https://github.com/nodejs/node/commit/f0a2e2cdec)] - **doc**: message.header duplication correction (Bryan English) [#3997](https://github.com/nodejs/node/pull/3997)
+* [[`b1dfa8bebb`](https://github.com/nodejs/node/commit/b1dfa8bebb)] - **doc**: fix typo in README (Rich Trott) [#4000](https://github.com/nodejs/node/pull/4000)
+* [[`4602e01221`](https://github.com/nodejs/node/commit/4602e01221)] - **doc**: replace sane with reasonable (Lewis Cowper) [#3980](https://github.com/nodejs/node/pull/3980)
+* [[`4849a54386`](https://github.com/nodejs/node/commit/4849a54386)] - **doc**: Adding best practises for crypto.pbkdf2 (Tom Gallacher) [#3290](https://github.com/nodejs/node/pull/3290)
+* [[`77251d99de`](https://github.com/nodejs/node/commit/77251d99de)] - **doc**: numeric flags to fs.open (Carl Lei) [#3641](https://github.com/nodejs/node/pull/3641)
+* [[`f4ca007b42`](https://github.com/nodejs/node/commit/f4ca007b42)] - **doc**: clarify that fs streams expect blocking fd (Carl Lei) [#3641](https://github.com/nodejs/node/pull/3641)
+* [[`26eeae8016`](https://github.com/nodejs/node/commit/26eeae8016)] - **doc**: fix broken references (Alexander Gromnitsky) [#3944](https://github.com/nodejs/node/pull/3944)
+* [[`f90227b0e8`](https://github.com/nodejs/node/commit/f90227b0e8)] - **doc**: move fs.existsSync() deprecation message (Martin Forsberg) [#3942](https://github.com/nodejs/node/pull/3942)
+* [[`bbcb2a2e65`](https://github.com/nodejs/node/commit/bbcb2a2e65)] - **doc**: clarify module loading behavior (cjihrig) [#3920](https://github.com/nodejs/node/pull/3920)
+* [[`0997178037`](https://github.com/nodejs/node/commit/0997178037)] - **doc**: add reference for buffer.inspect() (cjihrig) [#3921](https://github.com/nodejs/node/pull/3921)
+* [[`6c16c40283`](https://github.com/nodejs/node/commit/6c16c40283)] - **doc**: clarify v5.1.1 notable items (Rod Vagg) [#4156](https://github.com/nodejs/node/pull/4156)
+* [[`4c8800c2de`](https://github.com/nodejs/node/commit/4c8800c2de)] - **fs,doc**: use `target` instead of `destination` (yorkie) [#3912](https://github.com/nodejs/node/pull/3912)
+* [[`1f0e8dca8e`](https://github.com/nodejs/node/commit/1f0e8dca8e)] - **installer**: install the tick processor (Matt Loring) [#3032](https://github.com/nodejs/node/pull/3032)
+* [[`e8e4e0718b`](https://github.com/nodejs/node/commit/e8e4e0718b)] - **meta**: remove use of profanity in source (Myles Borins) [#4122](https://github.com/nodejs/node/pull/4122)
+* [[`13834caa28`](https://github.com/nodejs/node/commit/13834caa28)] - **module**: fix column offsets in errors (Tristian Flanagan) [#2867](https://github.com/nodejs/node/pull/2867)
+* [[`8988e1e117`](https://github.com/nodejs/node/commit/8988e1e117)] - **module,repl**: remove repl require() hack (Ben Noordhuis) [#4026](https://github.com/nodejs/node/pull/4026)
+* [[`baac81d95f`](https://github.com/nodejs/node/commit/baac81d95f)] - **net**: add local address/port for better errors (Jan Schär) [#3946](https://github.com/nodejs/node/pull/3946)
+* [[`12754c5dc3`](https://github.com/nodejs/node/commit/12754c5dc3)] - **net**: small code cleanup (Jan Schär) [#3943](https://github.com/nodejs/node/pull/3943)
+* [[`8a5e4345fd`](https://github.com/nodejs/node/commit/8a5e4345fd)] - **node**: s/doNTCallbackX/nextTickCallbackWithXArgs/ (Rod Vagg) [#4167](https://github.com/nodejs/node/pull/4167)
+* [[`0869ef3c55`](https://github.com/nodejs/node/commit/0869ef3c55)] - **(SEMVER-MINOR)** **repl**: allow leading period in multiline input (Zirak) [#3835](https://github.com/nodejs/node/pull/3835)
+* [[`aaab108dfe`](https://github.com/nodejs/node/commit/aaab108dfe)] - **repl**: attach location info to syntax errors (cjihrig) [#4013](https://github.com/nodejs/node/pull/4013)
+* [[`b08126dc9d`](https://github.com/nodejs/node/commit/b08126dc9d)] - **src**: refactor vcbuild configure args creation (Rod Vagg) [#3399](https://github.com/nodejs/node/pull/3399)
+* [[`da3137d0c5`](https://github.com/nodejs/node/commit/da3137d0c5)] - **src**: don't print garbage errors (cjihrig) [#4112](https://github.com/nodejs/node/pull/4112)
+* [[`9e9346fa32`](https://github.com/nodejs/node/commit/9e9346fa32)] - **src**: use GetCurrentProcessId() for process.pid (Ben Noordhuis) [#4163](https://github.com/nodejs/node/pull/4163)
+* [[`d969c0965c`](https://github.com/nodejs/node/commit/d969c0965c)] - **src**: define Is* util functions with macros (cjihrig) [#4118](https://github.com/nodejs/node/pull/4118)
+* [[`458facdf66`](https://github.com/nodejs/node/commit/458facdf66)] - **src**: define getpid() based on OS (cjihrig) [#4146](https://github.com/nodejs/node/pull/4146)
+* [[`7e18f2ec62`](https://github.com/nodejs/node/commit/7e18f2ec62)] - **(SEMVER-MINOR)** **src**: add BE support to StringBytes::Encode() (Bryon Leung) [#3410](https://github.com/nodejs/node/pull/3410)
+* [[`756ab9caad`](https://github.com/nodejs/node/commit/756ab9caad)] - **stream**: be less eager with readable flag (Brian White) [#4141](https://github.com/nodejs/node/pull/4141)
+* [[`8f845ba28a`](https://github.com/nodejs/node/commit/8f845ba28a)] - **stream_wrap**: error if stream has StringDecoder (Fedor Indutny) [#4031](https://github.com/nodejs/node/pull/4031)
+* [[`1c1af81ea0`](https://github.com/nodejs/node/commit/1c1af81ea0)] - **streams**: update .readable/.writable to false (Brian White) [#4083](https://github.com/nodejs/node/pull/4083)
+* [[`1d50819c85`](https://github.com/nodejs/node/commit/1d50819c85)] - **test**: check range fix for slowToString (Sakthipriyan Vairamani) [#4019](https://github.com/nodejs/node/pull/4019)
+* [[`0c2a0dc859`](https://github.com/nodejs/node/commit/0c2a0dc859)] - **test**: skip long path tests on non-Windows (Rafał Pocztarski) [#4116](https://github.com/nodejs/node/pull/4116)
+* [[`8a60aa1303`](https://github.com/nodejs/node/commit/8a60aa1303)] - **test**: don't check the # of chunks in test-http-1.0 (Santiago Gimeno) [#3961](https://github.com/nodejs/node/pull/3961)
+* [[`e84aeec883`](https://github.com/nodejs/node/commit/e84aeec883)] - **test**: mark test-cluster-shared-leak flaky (Rich Trott) [#4162](https://github.com/nodejs/node/pull/4162)
+* [[`b3f3b2e157`](https://github.com/nodejs/node/commit/b3f3b2e157)] - **test**: fix cluster-worker-isdead (Santiago Gimeno) [#3954](https://github.com/nodejs/node/pull/3954)
+* [[`da6be4d31a`](https://github.com/nodejs/node/commit/da6be4d31a)] - **test**: fix time resolution constraint (Gireesh Punathil) [#3981](https://github.com/nodejs/node/pull/3981)
+* [[`9d16729b20`](https://github.com/nodejs/node/commit/9d16729b20)] - **test**: skip instead of fail when mem constrained (Michael Cornacchia) [#3697](https://github.com/nodejs/node/pull/3697)
+* [[`be41eb751b`](https://github.com/nodejs/node/commit/be41eb751b)] - **test**: refactor test-http-exit-delay (Rich Trott) [#4055](https://github.com/nodejs/node/pull/4055)
+* [[`4b43bf0385`](https://github.com/nodejs/node/commit/4b43bf0385)] - **test**: fix flaky test-net-socket-local-address (Rich Trott) [#4109](https://github.com/nodejs/node/pull/4109)
+* [[`cb55c67a00`](https://github.com/nodejs/node/commit/cb55c67a00)] - **test**: improve cluster-disconnect-handles test (Brian White) [#4084](https://github.com/nodejs/node/pull/4084)
+* [[`2b5b127e14`](https://github.com/nodejs/node/commit/2b5b127e14)] - **test**: fix cluster-disconnect-handles flakiness (Santiago Gimeno) [#4009](https://github.com/nodejs/node/pull/4009)
+* [[`430264817b`](https://github.com/nodejs/node/commit/430264817b)] - **test**: add test for repl.defineCommand() (Bryan English) [#3908](https://github.com/nodejs/node/pull/3908)
+* [[`22b0971222`](https://github.com/nodejs/node/commit/22b0971222)] - **test**: eliminate multicast test FreeBSD flakiness (Rich Trott) [#4042](https://github.com/nodejs/node/pull/4042)
+* [[`c50003746b`](https://github.com/nodejs/node/commit/c50003746b)] - **test**: mark test flaky on FreeBSD (Rich Trott) [#4016](https://github.com/nodejs/node/pull/4016)
+* [[`69c95bbdb7`](https://github.com/nodejs/node/commit/69c95bbdb7)] - **test**: move ArrayStream to common (cjihrig) [#4027](https://github.com/nodejs/node/pull/4027)
+* [[`d94a70ec51`](https://github.com/nodejs/node/commit/d94a70ec51)] - **test**: fix test-domain-exit-dispose-again (Julien Gilli) [#3990](https://github.com/nodejs/node/pull/3990)
+* [[`00b839a2b8`](https://github.com/nodejs/node/commit/00b839a2b8)] - **test**: use platform-based timeout for reliability (Rich Trott) [#4015](https://github.com/nodejs/node/pull/4015)
+* [[`054a216b6f`](https://github.com/nodejs/node/commit/054a216b6f)] - **test**: mark cluster-net-send test flaky on windows (Rich Trott) [#4006](https://github.com/nodejs/node/pull/4006)
+* [[`d0621c5649`](https://github.com/nodejs/node/commit/d0621c5649)] - **test**: mark fork regression test flaky on windows (Rich Trott) [#4005](https://github.com/nodejs/node/pull/4005)
+* [[`19ed33df80`](https://github.com/nodejs/node/commit/19ed33df80)] - **test**: skip test if in FreeBSD jail (Rich Trott) [#3995](https://github.com/nodejs/node/pull/3995)
+* [[`a863e8d667`](https://github.com/nodejs/node/commit/a863e8d667)] - **test**: remove flaky status for cluster test (Rich Trott) [#3975](https://github.com/nodejs/node/pull/3975)
+* [[`dd0d15fc47`](https://github.com/nodejs/node/commit/dd0d15fc47)] - **test**: add TAP diagnostic message for retried tests (Rich Trott) [#3960](https://github.com/nodejs/node/pull/3960)
+* [[`1fe4d30efc`](https://github.com/nodejs/node/commit/1fe4d30efc)] - **test**: retry on smartos if ECONNREFUSED (Rich Trott) [#3941](https://github.com/nodejs/node/pull/3941)
+* [[`665a35d45e`](https://github.com/nodejs/node/commit/665a35d45e)] - **test**: address flaky test-http-client-timeout-event (Rich Trott) [#3968](https://github.com/nodejs/node/pull/3968)
+* [[`f9fe0aee53`](https://github.com/nodejs/node/commit/f9fe0aee53)] - **test**: numeric flags to fs.open (Carl Lei) [#3641](https://github.com/nodejs/node/pull/3641)
+* [[`54aafa17af`](https://github.com/nodejs/node/commit/54aafa17af)] - **test**: http complete list of non-concat headers (Bryan English) [#3930](https://github.com/nodejs/node/pull/3930)
+* [[`788541b40c`](https://github.com/nodejs/node/commit/788541b40c)] - **test**: fix race condition in unrefd interval test (Michael Cornacchia) [#3550](https://github.com/nodejs/node/pull/3550)
+* [[`e129d83996`](https://github.com/nodejs/node/commit/e129d83996)] - **test**: skip/replace weak crypto tests in FIPS mode (Stefan Budeanu) [#3757](https://github.com/nodejs/node/pull/3757)
+* [[`bc27379453`](https://github.com/nodejs/node/commit/bc27379453)] - **test**: avoid test timeouts on rpi (Stefan Budeanu) [#3902](https://github.com/nodejs/node/pull/3902)
+* [[`272732e76b`](https://github.com/nodejs/node/commit/272732e76b)] - **test**: fix flaky test-child-process-spawnsync-input (Rich Trott) [#3889](https://github.com/nodejs/node/pull/3889)
+* [[`781f8c0d1e`](https://github.com/nodejs/node/commit/781f8c0d1e)] - **test**: add OS X to module loading error test (Evan Lucas) [#3901](https://github.com/nodejs/node/pull/3901)
+* [[`f99c6363de`](https://github.com/nodejs/node/commit/f99c6363de)] - **test**: module loading error fix solaris #3798 (fansworld-claudio) [#3855](https://github.com/nodejs/node/pull/3855)
+* [[`1279adc756`](https://github.com/nodejs/node/commit/1279adc756)] - **timers**: optimize callback call: bind -> arrow (Andrei Sedoi) [#4038](https://github.com/nodejs/node/pull/4038)
+* [[`80f7f65464`](https://github.com/nodejs/node/commit/80f7f65464)] - **(SEMVER-MINOR)** **tls**: support reading multiple cas from one input (Ben Noordhuis) [#4099](https://github.com/nodejs/node/pull/4099)
+* [[`939f305d56`](https://github.com/nodejs/node/commit/939f305d56)] - **tls_wrap**: slice buffer properly in `ClearOut` (Fedor Indutny) [#4184](https://github.com/nodejs/node/pull/4184)
+* [[`6d4a03d3d2`](https://github.com/nodejs/node/commit/6d4a03d3d2)] - **(SEMVER-MINOR)** **tools**: list missing whitespace/if-one-line cpplint (Ben Noordhuis) [#4099](https://github.com/nodejs/node/pull/4099)
+* [[`1c1c1a0f2b`](https://github.com/nodejs/node/commit/1c1c1a0f2b)] - **(SEMVER-MINOR)** **tools**: add --prof-process flag to node binary (Matt Loring) [#4021](https://github.com/nodejs/node/pull/4021)
+* [[`d7a7d3e6f7`](https://github.com/nodejs/node/commit/d7a7d3e6f7)] - **tools**: update certdata.txt (Ben Noordhuis) [#3951](https://github.com/nodejs/node/pull/3951)
+* [[`1b434e0654`](https://github.com/nodejs/node/commit/1b434e0654)] - **util**: determine object types in C++ (cjihrig) [#4100](https://github.com/nodejs/node/pull/4100)
+* [[`c93e2678f0`](https://github.com/nodejs/node/commit/c93e2678f0)] - **util**: fix constructor/instanceof checks (Brian White) [#3385](https://github.com/nodejs/node/pull/3385)
+* [[`098a3113e1`](https://github.com/nodejs/node/commit/098a3113e1)] - **util**: move .decorateErrorStack to internal/util (Ben Noordhuis) [#4026](https://github.com/nodejs/node/pull/4026)
+* [[`e68ea16c32`](https://github.com/nodejs/node/commit/e68ea16c32)] - **util**: add decorateErrorStack() (cjihrig) [#4013](https://github.com/nodejs/node/pull/4013)
+* [[`c584c3e08f`](https://github.com/nodejs/node/commit/c584c3e08f)] - **util,src**: allow lookup of hidden values (cjihrig) [#3988](https://github.com/nodejs/node/pull/3988)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.2.0/node-v5.2.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.2.0/node-v5.2.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.2.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.2.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.2.0/node-v5.2.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.2.0/node-v5.2.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.2.0/node-v5.2.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.2.0/<br>
+Documentation: https://nodejs.org/docs/v5.2.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+e3d690b8a1f3aae3caaa57d931aac5ace7dbdea7237d3e9413041c30feecb4e0  node-v5.2.0-darwin-x64.tar.gz
+e93d2b2b594ee64f4bac42e4b659c033208340b21f597d3e86b41a58f8a32103  node-v5.2.0-darwin-x64.tar.xz
+72e3e0dfbbb37e85004c6a37a0233464eb10b910775baf9f69f3253de099319e  node-v5.2.0-headers.tar.gz
+f9f04bfbe6315c731b48e1f909808b0d0299f653b45b932d329895015c79b1ba  node-v5.2.0-headers.tar.xz
+3517d9ba80217985cac970272d387f4a905f17e5b87a7c7243efcc1173751531  node-v5.2.0-linux-arm64.tar.gz
+ffe8c113e0e377af8ede966a15b57ca7333fb4dc028a9335d1fcbd5a55e29f3c  node-v5.2.0-linux-arm64.tar.xz
+c3f2c2d3105e66d2d895711defb53becc5f8fddde177cd5cc2d981f6d9a5bd4b  node-v5.2.0-linux-armv6l.tar.gz
+3e60473ecc6e4a20559e4425c769b6bcf43095de3aaced634408e0a1dc4e7452  node-v5.2.0-linux-armv6l.tar.xz
+392cf0f1e1d3c64dbb940ddb750f436310b85f68261714639712816dd539365d  node-v5.2.0-linux-armv7l.tar.gz
+1a671cccb15c5ba31d5c3bc2ad3ca65eb940fbc2b1328708e98b5639b32ec653  node-v5.2.0-linux-armv7l.tar.xz
+7f31f5db97e1def61454d268d5206a6826385d157f444c21a36230a6c18f40d2  node-v5.2.0-linux-x64.tar.gz
+c4b09bdd3235504af67ad298da636333246d2c8c7aa1b71e04d860172beda430  node-v5.2.0-linux-x64.tar.xz
+963e3b4e23245db09581901ead2901bc2d516ddc69b7043fcb0cc76263d50152  node-v5.2.0-linux-x86.tar.gz
+0ae2106989f24e300625afca946639b54b1f1c801b48275ab1ec46cbf863ad9f  node-v5.2.0-linux-x86.tar.xz
+caefc6710a5a67bfc038738bb51b7de1ffcbd5743287ebc4309a938784bc2a7d  node-v5.2.0.pkg
+3f9eafb213c293ad09637056646ccc7a7746865d65508b01ad425005397fb25f  node-v5.2.0-sunos-x64.tar.gz
+dbdb5f10539e2abf0f88e064dc728c2cf844a998f32479bc6128498fa2ff164f  node-v5.2.0-sunos-x64.tar.xz
+4391329491781c0cb1a49360162198d8fe48190dfa9f1a8676b1e12b18a63afe  node-v5.2.0-sunos-x86.tar.gz
+07fc53c83355a954844d707484eee2336841855688e7bf79d85c30c2260c4f6d  node-v5.2.0-sunos-x86.tar.xz
+5df5682f9fdd8e747f652e0b09fed46478a1e3df159797852787a074b8787664  node-v5.2.0.tar.gz
+0cda6254aea3330a711f5b30425ad363568456ee1fd70336b21890b1c605f356  node-v5.2.0.tar.xz
+5c2a92d6f90ce19b19c8a87ffe7b0284b25174fead9665ebd04bc68369f2fee4  node-v5.2.0-x64.msi
+801b4a113615f6c81e1f9aaeb54bb7340d5bb4c7915c1264838d8dac91a24953  node-v5.2.0-x86.msi
+5eadf89f76550502414ad78f3ab920ff12aebcdbddf53c498959d604c672d153  win-x64/node.exe
+afeb574d979496b7bae4139051b520bd103e04efaf7452d0725069a5b9ef919f  win-x64/node.lib
+15e259ba6826931de2aaee0ee793970673643099a4663ba742023097bc037cb5  win-x86/node.exe
+a4790c00b2b03eadf09078bfc4bc373185a6acb057b35ae935ca21173d1ee55f  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWZ7rtAAoJEMJzeS99g1Rd8oQIAJJjWZ+oOZk47DKH0/FWyQOZ
+ukwiGWuFBLQyY72rATtE83SPDruf0+4ZGxiBk6k52/cXV8aLKj8LwUhvm6nYC35G
+sCiXUGQ0OxCvEMp3+62RA7W6hTTFtkXDMs0Ys1RYS+dNHIg7SZPZIj7v4U5AYktc
+vYR5WXM6Z35TMaNm64TB1yUsePhoPbchQ9YxNA+dFkT7zCM7h/xfCE0oTLEHm9Ya
+xgfpjMNC/fgyYq4lOH6TvHmyLccZdhfGtJQplW80V1Yz8kRvWO5KL3PG8yKk+fls
+dlYjECgZ55s1uU8Gg6nqCnvk3D0K+C6E6DQDaGzJqdzysMBGzuVaQHE7+OD/Yx8=
+=+GgE
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.3.0.md b/locale/uk/blog/release/v5.3.0.md
new file mode 100755
index 0000000000000..9cbadbf127f52
--- /dev/null
+++ b/locale/uk/blog/release/v5.3.0.md
@@ -0,0 +1,155 @@
+---
+date: 2015-12-16T20:23:07.363Z
+version: 5.3.0
+category: release
+title: Node v5.3.0 (Current)
+slug: node-v5-3-0
+layout: blog-post.hbs
+author: Colin Ihrig
+---
+
+### Notable changes
+
+* **buffer**:
+  - `Buffer.prototype.includes()` has been added to keep parity with TypedArrays. (Alexander Martin) [#3567](https://github.com/nodejs/node/pull/3567).
+* **domains**:
+  - Fix handling of uncaught exceptions. (Julien Gilli) [#3654](https://github.com/nodejs/node/pull/3654).
+* **https**:
+  - Added support for disabling session caching. (Fedor Indutny) [#4252](https://github.com/nodejs/node/pull/4252).
+* **repl**:
+  - Allow third party modules to be imported using `require()`. This corrects a regression from 5.2.0. (Ben Noordhuis) [#4215](https://github.com/nodejs/node/pull/4215).
+* **deps**:
+  - Upgrade libuv to 1.8.0. (Saúl Ibarra Corretgé) [#4276](https://github.com/nodejs/node/pull/4276).
+
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`6ca5ea3860`](https://github.com/nodejs/node/commit/6ca5ea3860)] - 2015-12-09, Version 5.2.0 (Current) (Rod Vagg) [#4181](https://github.com/nodejs/node/pull/4181)
+* [[`da5cdc2207`](https://github.com/nodejs/node/commit/da5cdc2207)] - **assert**: accommodate ES6 classes that extend Error (Rich Trott) [#4166](https://github.com/nodejs/node/pull/4166)
+* [[`67e181986a`](https://github.com/nodejs/node/commit/67e181986a)] - **(SEMVER-MINOR)** **buffer**: add includes() for parity with TypedArray (Alexander Martin) [#3567](https://github.com/nodejs/node/pull/3567)
+* [[`84dea1bd0c`](https://github.com/nodejs/node/commit/84dea1bd0c)] - **configure**: fix arm vfpv2 (Jörg Krause) [#4203](https://github.com/nodejs/node/pull/4203)
+* [[`a7f5dfd14c`](https://github.com/nodejs/node/commit/a7f5dfd14c)] - **configure**: use \_\_ARM\_ARCH to determine arm version (João Reis) [#4123](https://github.com/nodejs/node/pull/4123)
+* [[`0e3912be0b`](https://github.com/nodejs/node/commit/0e3912be0b)] - **configure**: respect CC\_host in host arch detection (João Reis) [#4117](https://github.com/nodejs/node/pull/4117)
+* [[`69b94ec55c`](https://github.com/nodejs/node/commit/69b94ec55c)] - **deps**: upgrade libuv to 1.8.0 (Saúl Ibarra Corretgé) [#4276](https://github.com/nodejs/node/pull/4276)
+* [[`a8854e5b59`](https://github.com/nodejs/node/commit/a8854e5b59)] - **doc**: document the cache parameter for fs.realpathSync (Jackson Tian) [#4285](https://github.com/nodejs/node/pull/4285)
+* [[`9e1b7aa874`](https://github.com/nodejs/node/commit/9e1b7aa874)] - **doc**: document backlog for server.listen() variants (Jan Schär) [#4025](https://github.com/nodejs/node/pull/4025)
+* [[`435d571f22`](https://github.com/nodejs/node/commit/435d571f22)] - **doc**: update AUTHORS list (Rod Vagg) [#4183](https://github.com/nodejs/node/pull/4183)
+* [[`3b3061365a`](https://github.com/nodejs/node/commit/3b3061365a)] - **doc**: update irc channels: #node.js and #node-dev (Nelson Pecora) [#2743](https://github.com/nodejs/node/pull/2743)
+* [[`9538fd02e5`](https://github.com/nodejs/node/commit/9538fd02e5)] - **doc**: clarify error events in HTTP module documentation (Lenny Markus) [#4275](https://github.com/nodejs/node/pull/4275)
+* [[`c6efd535e4`](https://github.com/nodejs/node/commit/c6efd535e4)] - **doc**: fix improper http.get sample code (Hideki Yamamura) [#4263](https://github.com/nodejs/node/pull/4263)
+* [[`498c9adb08`](https://github.com/nodejs/node/commit/498c9adb08)] - **doc**: add CTC meeting minutes 2015-10-28 (Rod Vagg) [#3661](https://github.com/nodejs/node/pull/3661)
+* [[`671347cf13`](https://github.com/nodejs/node/commit/671347cf13)] - **doc**: fixup socket.remoteAddress (Arthur Gautier) [#4198](https://github.com/nodejs/node/pull/4198)
+* [[`f050cab3d8`](https://github.com/nodejs/node/commit/f050cab3d8)] - **doc**: copyedit console doc (Rich Trott) [#4225](https://github.com/nodejs/node/pull/4225)
+* [[`1a21a5368b`](https://github.com/nodejs/node/commit/1a21a5368b)] - **doc**: move description of 'equals' method to right place (janriemer) [#4227](https://github.com/nodejs/node/pull/4227)
+* [[`9a9c5259bf`](https://github.com/nodejs/node/commit/9a9c5259bf)] - **doc**: Fixing broken links to the v8 wiki (Tom Gallacher) [#4241](https://github.com/nodejs/node/pull/4241)
+* [[`37ed05b8c1`](https://github.com/nodejs/node/commit/37ed05b8c1)] - **doc**: copyedit child_process doc (Rich Trott) [#4188](https://github.com/nodejs/node/pull/4188)
+* [[`e47ae5808b`](https://github.com/nodejs/node/commit/e47ae5808b)] - **doc**: copyedit buffer doc (Rich Trott) [#4187](https://github.com/nodejs/node/pull/4187)
+* [[`70fb06a90b`](https://github.com/nodejs/node/commit/70fb06a90b)] - **doc**: clarify assert.fail doc (Rich Trott) [#4186](https://github.com/nodejs/node/pull/4186)
+* [[`e3187cc81e`](https://github.com/nodejs/node/commit/e3187cc81e)] - **doc**: copyedit addons doc (Rich Trott) [#4185](https://github.com/nodejs/node/pull/4185)
+* [[`931ab967ff`](https://github.com/nodejs/node/commit/931ab967ff)] - **doc**: add calvinmetcalf to collaborators (Calvin Metcalf) [#4218](https://github.com/nodejs/node/pull/4218)
+* [[`01ce23148b`](https://github.com/nodejs/node/commit/01ce23148b)] - **doc**: add mcollina to collaborators (Matteo Collina) [#4220](https://github.com/nodejs/node/pull/4220)
+* [[`bd8753aabf`](https://github.com/nodejs/node/commit/bd8753aabf)] - **doc**: add rmg to collaborators (Ryan Graham) [#4219](https://github.com/nodejs/node/pull/4219)
+* [[`73a9a6fc92`](https://github.com/nodejs/node/commit/73a9a6fc92)] - **doc**: harmonize description of `ca` argument (Ben Noordhuis) [#4213](https://github.com/nodejs/node/pull/4213)
+* [[`dfc8bedbc5`](https://github.com/nodejs/node/commit/dfc8bedbc5)] - **doc**: change references from node to Node.js (Roman Klauke) [#4177](https://github.com/nodejs/node/pull/4177)
+* [[`7a518788e9`](https://github.com/nodejs/node/commit/7a518788e9)] - **doc, test**: symbols as event names (Bryan English) [#4151](https://github.com/nodejs/node/pull/4151)
+* [[`425a3545d2`](https://github.com/nodejs/node/commit/425a3545d2)] - **(SEMVER-MINOR)** **domains**: fix handling of uncaught exceptions (Julien Gilli) [#3654](https://github.com/nodejs/node/pull/3654)
+* [[`acef181fde`](https://github.com/nodejs/node/commit/acef181fde)] - **(SEMVER-MINOR)** **https**: support disabling session caching (Fedor Indutny) [#4252](https://github.com/nodejs/node/pull/4252)
+* [[`2a60e2ad71`](https://github.com/nodejs/node/commit/2a60e2ad71)] - **module,src**: do not wrap modules with -1 lineOffset (cjihrig) [#4298](https://github.com/nodejs/node/pull/4298)
+* [[`d3c498b1b7`](https://github.com/nodejs/node/commit/d3c498b1b7)] - **node**: remove unused variables in AppendExceptionLine (Yazhong Liu) [#4264](https://github.com/nodejs/node/pull/4264)
+* [[`aad6b9f0eb`](https://github.com/nodejs/node/commit/aad6b9f0eb)] - **repl**: display error message when loading directory (Prince J Wesley) [#4170](https://github.com/nodejs/node/pull/4170)
+* [[`213ede6cee`](https://github.com/nodejs/node/commit/213ede6cee)] - **repl**: fix require('3rdparty') regression (Ben Noordhuis) [#4215](https://github.com/nodejs/node/pull/4215)
+* [[`f176b31e74`](https://github.com/nodejs/node/commit/f176b31e74)] - **src**: remove \_\_builtin\_bswap16 call (Ben Noordhuis) [#4290](https://github.com/nodejs/node/pull/4290)
+* [[`ce2471673f`](https://github.com/nodejs/node/commit/ce2471673f)] - **src**: remove unused BITS_PER_LONG macro (Ben Noordhuis) [#4290](https://github.com/nodejs/node/pull/4290)
+* [[`b799a74709`](https://github.com/nodejs/node/commit/b799a74709)] - **src**: fix line numbers on core errors (cjihrig) [#4254](https://github.com/nodejs/node/pull/4254)
+* [[`c311b61430`](https://github.com/nodejs/node/commit/c311b61430)] - **src**: fix deprecation message for ErrnoException (Martin von Gagern) [#4269](https://github.com/nodejs/node/pull/4269)
+* [[`2859f9ef92`](https://github.com/nodejs/node/commit/2859f9ef92)] - **test**: fix debug-port-cluster flakiness (Ben Noordhuis) [#4310](https://github.com/nodejs/node/pull/4310)
+* [[`cb0b4a6bc0`](https://github.com/nodejs/node/commit/cb0b4a6bc0)] - **test**: add test for debugging one line files (cjihrig) [#4298](https://github.com/nodejs/node/pull/4298)
+* [[`0b9c3a30d6`](https://github.com/nodejs/node/commit/0b9c3a30d6)] - **test**: add test for tls.parseCertString (Evan Lucas) [#4283](https://github.com/nodejs/node/pull/4283)
+* [[`7598ed6cc0`](https://github.com/nodejs/node/commit/7598ed6cc0)] - **test**: parallelize test-repl-persistent-history (Jeremiah Senkpiel) [#4247](https://github.com/nodejs/node/pull/4247)
+* [[`668449ad14`](https://github.com/nodejs/node/commit/668449ad14)] - **test**: use regular timeout times for ARMv8 (Jeremiah Senkpiel) [#4248](https://github.com/nodejs/node/pull/4248)
+* [[`23e7703c85`](https://github.com/nodejs/node/commit/23e7703c85)] - **test**: fix http-many-ended-pipelines flakiness (Santiago Gimeno) [#4041](https://github.com/nodejs/node/pull/4041)
+* [[`3b94991bda`](https://github.com/nodejs/node/commit/3b94991bda)] - **test**: fix tls-inception flakiness (Santiago Gimeno) [#4195](https://github.com/nodejs/node/pull/4195)
+* [[`86a3bd09b0`](https://github.com/nodejs/node/commit/86a3bd09b0)] - **test**: fix tls-inception (Santiago Gimeno) [#4195](https://github.com/nodejs/node/pull/4195)
+* [[`1e89830a11`](https://github.com/nodejs/node/commit/1e89830a11)] - **test**: don't assume openssl s\_client supports -ssl3 (Ben Noordhuis) [#4204](https://github.com/nodejs/node/pull/4204)
+* [[`c5b4f6bc99`](https://github.com/nodejs/node/commit/c5b4f6bc99)] - **(SEMVER-MINOR)** **tls**: introduce `secureContext` for `tls.connect` (Fedor Indutny) [#4246](https://github.com/nodejs/node/pull/4246)
+* [[`e0bb118a1d`](https://github.com/nodejs/node/commit/e0bb118a1d)] - **tls_wrap**: inherit from the `AsyncWrap` first (Fedor Indutny) [#4268](https://github.com/nodejs/node/pull/4268)
+* [[`d63cceeb10`](https://github.com/nodejs/node/commit/d63cceeb10)] - **tools**: add .editorconfig (ronkorving) [#2993](https://github.com/nodejs/node/pull/2993)
+* [[`4b267df93e`](https://github.com/nodejs/node/commit/4b267df93e)] - **udp**: remove a needless instanceof Buffer check (ronkorving) [#4301](https://github.com/nodejs/node/pull/4301)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.3.0/node-v5.3.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.3.0/node-v5.3.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.3.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.3.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.3.0/node-v5.3.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.3.0/node-v5.3.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.3.0/node-v5.3.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.3.0/<br>
+Documentation: https://nodejs.org/docs/v5.3.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+bfb28ff6a02a6bcb3a77afcb66054dcf44b50e1ccdbeca807865c6220c380b6b  node-v5.3.0-darwin-x64.tar.gz
+c88af62d50f19803831a0ab0c1f208154d8bb0e022fe9e374e068183c05ed262  node-v5.3.0-darwin-x64.tar.xz
+40d7d7982865719af6723e4796d0d773f2d47a64e43133b7a7f89bbac1a52e97  node-v5.3.0-headers.tar.gz
+3e92e7cd02d2571455f7791d582ee76c5292c54ac97d57c229a05f85fd180287  node-v5.3.0-headers.tar.xz
+0a37c919cb2e2511ee7ff60e4fc80266afa3dad7cffa9204dc73da244c3a308a  node-v5.3.0-linux-arm64.tar.gz
+1e9f4f7650fdef2bbd030cec7de59e225030e05e0e1298f5f84b103fcd1900e8  node-v5.3.0-linux-arm64.tar.xz
+266bedf9f8777c98abd0f28b41b0bb2b0b3d5be888bcfb899bf46fd986188172  node-v5.3.0-linux-armv6l.tar.gz
+76dbb7960dfaab99c017e568e3f2b4b7c7bd4bdf2c341b38cf1053ad8d159eea  node-v5.3.0-linux-armv6l.tar.xz
+67205437fd74f7e63219cbe5932f83b064884204eea4503faa6d93f5db2719e1  node-v5.3.0-linux-armv7l.tar.gz
+2b84201ec54279b3d0e148c04111ac8aa004698bbb131753f6f86233f32b64aa  node-v5.3.0-linux-armv7l.tar.xz
+75b029b30d4a4147d67cf75bf6e034291fb5919c6935ec23f8365cee2d463f12  node-v5.3.0-linux-x64.tar.gz
+8c03fed1c6b11dc6604282a595cd695eab5b80cd9e025bd6ced4fa78c2ade396  node-v5.3.0-linux-x64.tar.xz
+5e1b2e0aa5277e6dded7bc3cba452035a9695b696e974b02eadcba76070ca7eb  node-v5.3.0-linux-x86.tar.gz
+6f46d13e0c6e94f1b31fece79eef880804de04b2316e04ba9fd6a4dcfd9ae666  node-v5.3.0-linux-x86.tar.xz
+755e0abee3b2d50f28a906d292fb201676661e38135916622f7ce5dbe6f39bea  node-v5.3.0.pkg
+96be7d379e284012c2da8e08df304896ba7b533fd84be4585b1405bcafbe8c96  node-v5.3.0-sunos-x64.tar.gz
+06fdb8871ccd4a86d893cecf06c8dbe367eeef95ee79cca5e737cb66f3a95340  node-v5.3.0-sunos-x64.tar.xz
+0c28263d118a1819e48d633d5dc62fbc88035cff007246588505eb836eb041af  node-v5.3.0-sunos-x86.tar.gz
+6530edeb7e09f5d1b6083579ed0438c2a15a7e2a8f931ebdd401b05eb5a27d77  node-v5.3.0-sunos-x86.tar.xz
+cc05ff06149c638345835788f448471d264a7e011bf083394f86d5be51975c7e  node-v5.3.0.tar.gz
+e5115ee78c31ac3af0f2b3553aa84fff2f49ae59bd6e01e11d78ce86c544569e  node-v5.3.0.tar.xz
+1c2a516cac40488f0d305c8aeed2fc61075dd882427830c12593f652d68f65e0  node-v5.3.0-x64.msi
+156065db0018e3058e2fb41753eb27d160e6ba3ec5fad8f394f1c6f2992661af  node-v5.3.0-x86.msi
+c665410c624b1a6833d7460e25ec8cfa21f4fb215b92f5c684ad26e64888554d  win-x64/node.exe
+796fab4b8bf369ba3d21cf932e8a3110b3b458c4d1c5cee87e8ab1d594d57ced  win-x64/node.lib
+2a1815c7f12ffa1ec62b827816657330a686180804c8482bff10c12433f1f49c  win-x86/node.exe
+4325dcfd627d6286907a9c2378bce93b7690152bd08da187d7c3e917b932f9b4  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJWccPxAAoJEHQ0OQvb6bnFCsEP/ROhGerba34tL4lzNRpRtMWP
+HwmvKX9VVFhZwYWpPrqkowl3F292Jo5oxNNxT8vkElWjBhLeRa55dDNJzv1f7xs1
+2/3U5vRmOv3bpcp32d/8+GIjDsSfy3KrzjgFJh9Nw4fW0QrIzsgLFIZKCnAI/Tx2
+1KTRVefFUbMlQxRP3cH4SaLmDACyD5KuDFJjWMLbtuUUql+x4UcfoEL9iM2kN/VX
+1vA+0SMBGcEftAnnM2xjeZNPXPUWOiCtONnngfcAU+TT5kPW54bvpPNb0E3qy7H4
+onliYYuDK5171BodmLnQTsXn5u9QhmngHll+nTVDjMJHY7RPCB2+6GOdyXRcZbNx
+t6/DEiBEs38qM+NOhEegzNCJsbMvHRd6KW+RVbX81u/X0ncXplOGwsfnjX4ndl4H
+piL3CnQts/EI5DHqm22YvBJj6NbxosLM8OOkJSrt9JZTwXyI4TWJ+zW9+OCrFZbw
+nDGeAokNSvA9nGXLgunSUVnIHHQdEUnIjYlnwFsJuE6qHuyNHerMuFdUPeAkWnr6
+21pwPOwSGbP1oll3vYB8CREu3rRskW7mk1m0amZc5dxsSs/w28XcwYacvz5Hpf4Q
+8Y2JkHAWZDKVyKyGY4j8uyRhHGJ6h5FFfa8LOPar/rwDM6IufcW4PKsqVvqM2glx
+5p6R3ZmeTxU1HDkQHWOk
+=IJpS
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.4.0.md b/locale/uk/blog/release/v5.4.0.md
new file mode 100755
index 0000000000000..3ab4ed9467880
--- /dev/null
+++ b/locale/uk/blog/release/v5.4.0.md
@@ -0,0 +1,201 @@
+---
+date: 2016-01-06T22:41:09.455Z
+version: 5.4.0
+category: release
+title: Node v5.4.0 (Current)
+slug: node-v5-4-0
+layout: blog-post.hbs
+author: Jeremiah Senkpiel
+---
+
+### Notable changes
+
+* **http**:
+  - A new status code was added: 451 - "Unavailable For Legal Reasons" (Max Barinov) [#4377](https://github.com/nodejs/node/pull/4377).
+  - Idle sockets that have been kept alive now handle errors (José F. Romaniello) [#4482](https://github.com/nodejs/node/pull/4482).
+* This release also includes several minor performance improvements:
+  - **assert**: deepEqual is now speedier when comparing TypedArrays (Claudio Rodriguez) [#4330](https://github.com/nodejs/node/pull/4330).
+  - **lib**: Use arrow functions instead of bind where possible (Minwoo Jung) [node#3622](https://github.com/nodejs/node/pull/3622).
+  - **node**: Improved accessor perf of `process.env` (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780).
+  - **node**: Improved performance of `process.hrtime()` (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780), (Evan Lucas) [#4484](https://github.com/nodejs/node/pull/4484).
+  - **node**: Improved GetActiveHandles performance (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780).
+  - **util**: Use faster iteration in `util.format()` (Jackson Tian) [#3964](https://github.com/nodejs/node/pull/3964).
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`d265fc821a`](https://github.com/nodejs/node/commit/d265fc821a)] - **assert**: typed array deepequal performance fix (Claudio Rodriguez) [#4330](https://github.com/nodejs/node/pull/4330)
+* [[`6d8053ab56`](https://github.com/nodejs/node/commit/6d8053ab56)] - **buffer**: faster case for create Buffer from new Buffer(0) (Jackson Tian) [#4326](https://github.com/nodejs/node/pull/4326)
+* [[`8781c59878`](https://github.com/nodejs/node/commit/8781c59878)] - **buffer**: refactor create buffer (Jackson Tian) [#4340](https://github.com/nodejs/node/pull/4340)
+* [[`252628294b`](https://github.com/nodejs/node/commit/252628294b)] - **child_process**: guard against race condition (Rich Trott) [#4418](https://github.com/nodejs/node/pull/4418)
+* [[`fcf632bc6a`](https://github.com/nodejs/node/commit/fcf632bc6a)] - **crypto**: load PFX chain the same way as regular one (Fedor Indutny) [#4165](https://github.com/nodejs/node/pull/4165)
+* [[`a5094a35a0`](https://github.com/nodejs/node/commit/a5094a35a0)] - **debugger**: guard against call from non-node context (Ben Noordhuis) [#4328](https://github.com/nodejs/node/pull/4328)
+* [[`b4c51c5b76`](https://github.com/nodejs/node/commit/b4c51c5b76)] - **deps**: backport 200315c from V8 upstream (Vladimir Kurchatkin) [#4128](https://github.com/nodejs/node/pull/4128)
+* [[`334e73942e`](https://github.com/nodejs/node/commit/334e73942e)] - **doc**: fix heading level error in Buffer doc (Shigeki Ohtsu) [#4537](https://github.com/nodejs/node/pull/4537)
+* [[`5be0259181`](https://github.com/nodejs/node/commit/5be0259181)] - **doc**: close backtick in process.title description (Dave) [#4534](https://github.com/nodejs/node/pull/4534)
+* [[`35aec4c14d`](https://github.com/nodejs/node/commit/35aec4c14d)] - **doc**: fix numbering in stream.markdown (Richard Sun) [#4538](https://github.com/nodejs/node/pull/4538)
+* [[`982f3227a5`](https://github.com/nodejs/node/commit/982f3227a5)] - **doc**: improvements to dgram.markdown copy (James M Snell) [#4437](https://github.com/nodejs/node/pull/4437)
+* [[`6cdfa38d23`](https://github.com/nodejs/node/commit/6cdfa38d23)] - **doc**: improvements to errors.markdown copy (James M Snell) [#4454](https://github.com/nodejs/node/pull/4454)
+* [[`6c7bcd5007`](https://github.com/nodejs/node/commit/6c7bcd5007)] - **doc**: fix website wg mislink (jona) [#4357](https://github.com/nodejs/node/pull/4357)
+* [[`eee50821dc`](https://github.com/nodejs/node/commit/eee50821dc)] - **doc**: mention that http.Server inherits from net.Server (Ryan Sobol) [#4455](https://github.com/nodejs/node/pull/4455)
+* [[`c745b4d5f8`](https://github.com/nodejs/node/commit/c745b4d5f8)] - **doc**: explain ClientRequest#setTimeout time unit (Ben Ripkens) [#4458](https://github.com/nodejs/node/pull/4458)
+* [[`40076bf7f8`](https://github.com/nodejs/node/commit/40076bf7f8)] - **doc**: fix spelling error in lib/url.js comment (Nik Nyby) [#4390](https://github.com/nodejs/node/pull/4390)
+* [[`5a223d64e3`](https://github.com/nodejs/node/commit/5a223d64e3)] - **doc**: add anchors for _transform _flush _writev in stream.markdown (iamchenxin) [#4448](https://github.com/nodejs/node/pull/4448)
+* [[`e8bbeecc4c`](https://github.com/nodejs/node/commit/e8bbeecc4c)] - **doc**: improvements to debugger.markdown copy (James M Snell) [#4436](https://github.com/nodejs/node/pull/4436)
+* [[`ccd75fe3fb`](https://github.com/nodejs/node/commit/ccd75fe3fb)] - **doc**: improvements to events.markdown copy (James M Snell) [#4468](https://github.com/nodejs/node/pull/4468)
+* [[`ed15962777`](https://github.com/nodejs/node/commit/ed15962777)] - **doc**: improvements to dns.markdown copy (James M Snell) [#4449](https://github.com/nodejs/node/pull/4449)
+* [[`e177cc9fdf`](https://github.com/nodejs/node/commit/e177cc9fdf)] - **doc**: improvements to console.markdown copy (James M Snell) [#4428](https://github.com/nodejs/node/pull/4428)
+* [[`c1bc9a1023`](https://github.com/nodejs/node/commit/c1bc9a1023)] - **doc**: improve child_process.markdown copy (James M Snell) [#4383](https://github.com/nodejs/node/pull/4383)
+* [[`150f62847c`](https://github.com/nodejs/node/commit/150f62847c)] - **doc**: copyedit setTimeout() documentation (Rich Trott) [#4434](https://github.com/nodejs/node/pull/4434)
+* [[`9e667354be`](https://github.com/nodejs/node/commit/9e667354be)] - **doc**: fix formatting in process.markdown (Rich Trott) [#4433](https://github.com/nodejs/node/pull/4433)
+* [[`bc1c0dc3fb`](https://github.com/nodejs/node/commit/bc1c0dc3fb)] - **doc**: catch the WORKING_GROUPS.md bootstrap docs up to date (James M Snell) [#4367](https://github.com/nodejs/node/pull/4367)
+* [[`c835ba3601`](https://github.com/nodejs/node/commit/c835ba3601)] - **doc**: improve assert.markdown copy (James M Snell) [#4360](https://github.com/nodejs/node/pull/4360)
+* [[`e79eda74c0`](https://github.com/nodejs/node/commit/e79eda74c0)] - **doc**: copyedit releases.md (Rich Trott) [#4384](https://github.com/nodejs/node/pull/4384)
+* [[`6450d8667f`](https://github.com/nodejs/node/commit/6450d8667f)] - **doc**: improve grammar in tls docs (Adri Van Houdt) [#4315](https://github.com/nodejs/node/pull/4315)
+* [[`474a0f081a`](https://github.com/nodejs/node/commit/474a0f081a)] - **doc**: improvements to buffer.markdown copy (James M Snell) [#4370](https://github.com/nodejs/node/pull/4370)
+* [[`57684d650e`](https://github.com/nodejs/node/commit/57684d650e)] - **doc**: improve addons.markdown copy (James M Snell) [#4320](https://github.com/nodejs/node/pull/4320)
+* [[`04dd861221`](https://github.com/nodejs/node/commit/04dd861221)] - **doc**: fix, modernize examples in docs (James M Snell) [#4282](https://github.com/nodejs/node/pull/4282)
+* [[`5ce6e99474`](https://github.com/nodejs/node/commit/5ce6e99474)] - **doc**: Typo in buffer.markdown referencing buf.write() (chrisjohn404) [#4324](https://github.com/nodejs/node/pull/4324)
+* [[`699bf2c464`](https://github.com/nodejs/node/commit/699bf2c464)] - **doc**: fix link in addons.markdown (Nicholas Young) [#4331](https://github.com/nodejs/node/pull/4331)
+* [[`e742422757`](https://github.com/nodejs/node/commit/e742422757)] - **fs**: use pushValueToArray for readdir(Sync) (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780)
+* [[`1dd2d015d2`](https://github.com/nodejs/node/commit/1dd2d015d2)] - **(SEMVER-MINOR)** **http**: handle errors on idle sockets (José F. Romaniello) [#4482](https://github.com/nodejs/node/pull/4482)
+* [[`083ae166bb`](https://github.com/nodejs/node/commit/083ae166bb)] - **http**: use `self.keepAlive` instead of `self.options.keepAlive` (Damian Schenkelman) [#4407](https://github.com/nodejs/node/pull/4407)
+* [[`ffb4a6e0e4`](https://github.com/nodejs/node/commit/ffb4a6e0e4)] - **http**: fix non-string header value concatenation (Brian White) [#4460](https://github.com/nodejs/node/pull/4460)
+* [[`c77fd6829a`](https://github.com/nodejs/node/commit/c77fd6829a)] - **(SEMVER-MINOR)** **http**: 451 status code "Unavailable For Legal Reasons" (Max Barinov) [#4377](https://github.com/nodejs/node/pull/4377)
+* [[`8f7af9a489`](https://github.com/nodejs/node/commit/8f7af9a489)] - **http**: remove excess calls to removeSocket (Dave) [#4172](https://github.com/nodejs/node/pull/4172)
+* [[`b841967103`](https://github.com/nodejs/node/commit/b841967103)] - **http**: Remove an unnecessary assignment (Bo Borgerson) [#4323](https://github.com/nodejs/node/pull/4323)
+* [[`b8366e76dd`](https://github.com/nodejs/node/commit/b8366e76dd)] - **http_parser**: use pushValueToArray for headers (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780)
+* [[`ca97e7276e`](https://github.com/nodejs/node/commit/ca97e7276e)] - **https**: use `servername` in agent key (Fedor Indutny) [#4389](https://github.com/nodejs/node/pull/4389)
+* [[`b5aaccc6af`](https://github.com/nodejs/node/commit/b5aaccc6af)] - **lib**: remove unused modules (Rich Trott) [#4396](https://github.com/nodejs/node/pull/4396)
+* [[`921fb540c1`](https://github.com/nodejs/node/commit/921fb540c1)] - **node**: improve performance of process.hrtime() (Evan Lucas) [#4484](https://github.com/nodejs/node/pull/4484)
+* [[`ecef817a28`](https://github.com/nodejs/node/commit/ecef817a28)] - **node**: improve accessor perf of process.env (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780)
+* [[`89f056bdf3`](https://github.com/nodejs/node/commit/89f056bdf3)] - **node**: improve performance of hrtime() (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780)
+* [[`c8fc217dc7`](https://github.com/nodejs/node/commit/c8fc217dc7)] - **node**: improve GetActiveHandles performance (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780)
+* [[`8464667071`](https://github.com/nodejs/node/commit/8464667071)] - **node**: fix erroneously named function call (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780)
+* [[`e57fd51a5e`](https://github.com/nodejs/node/commit/e57fd51a5e)] - **os**: fix crash in GetInterfaceAddresses (Martin Bark) [#4272](https://github.com/nodejs/node/pull/4272)
+* [[`65c40d753f`](https://github.com/nodejs/node/commit/65c40d753f)] - **repl**: remove unused function (Rich Trott)
+* [[`3d41a44dba`](https://github.com/nodejs/node/commit/3d41a44dba)] - **repl**: Fixed node repl history edge case. (Mudit Ameta) [#4108](https://github.com/nodejs/node/pull/4108)
+* [[`d11930d604`](https://github.com/nodejs/node/commit/d11930d604)] - **repl**: use String#repeat instead of Array#join (Evan Lucas) [#3900](https://github.com/nodejs/node/pull/3900)
+* [[`4220d25626`](https://github.com/nodejs/node/commit/4220d25626)] - **test**: fix linting for the v5.x branch (Jeremiah Senkpiel) [#4547](https://github.com/nodejs/node/pull/4547)
+* [[`4b14f1c983`](https://github.com/nodejs/node/commit/4b14f1c983)] - **test**: remove unused vars (Rich Trott) [#4536](https://github.com/nodejs/node/pull/4536)
+* [[`2a69ab32ec`](https://github.com/nodejs/node/commit/2a69ab32ec)] - **test**: add test-domain-exit-dispose-again back (Julien Gilli) [#4256](https://github.com/nodejs/node/pull/4256)
+* [[`ae0246641c`](https://github.com/nodejs/node/commit/ae0246641c)] - **test**: remove unused vars from parallel tests (Rich Trott) [#4511](https://github.com/nodejs/node/pull/4511)
+* [[`984db93e7c`](https://github.com/nodejs/node/commit/984db93e7c)] - **test**: fix flaky test-cluster-shared-leak (Rich Trott) [#4510](https://github.com/nodejs/node/pull/4510)
+* [[`30b0d7583a`](https://github.com/nodejs/node/commit/30b0d7583a)] - **test**: fix flaky streams test (Rich Trott) [#4516](https://github.com/nodejs/node/pull/4516)
+* [[`46fefbc1b5`](https://github.com/nodejs/node/commit/46fefbc1b5)] - **test**: fix flaky test-http-agent-keepalive (Rich Trott) [#4524](https://github.com/nodejs/node/pull/4524)
+* [[`e04a8401d9`](https://github.com/nodejs/node/commit/e04a8401d9)] - **test**: remove flaky designations for tests (Rich Trott) [#4519](https://github.com/nodejs/node/pull/4519)
+* [[`a703b1bf73`](https://github.com/nodejs/node/commit/a703b1bf73)] - **test**: remove time check (Rich Trott) [#4494](https://github.com/nodejs/node/pull/4494)
+* [[`02b3a5be52`](https://github.com/nodejs/node/commit/02b3a5be52)] - **test**: refactor test-fs-empty-readStream (Rich Trott) [#4490](https://github.com/nodejs/node/pull/4490)
+* [[`ab3e5c1417`](https://github.com/nodejs/node/commit/ab3e5c1417)] - **test**: write to tmp dir rather than fixture dir (Rich Trott) [#4489](https://github.com/nodejs/node/pull/4489)
+* [[`06043fdfa3`](https://github.com/nodejs/node/commit/06043fdfa3)] - **test**: remove unused modules (Rich Trott) [#4475](https://github.com/nodejs/node/pull/4475)
+* [[`f1a66bc249`](https://github.com/nodejs/node/commit/f1a66bc249)] - **test**: clarify role of domains in test (Rich Trott) [#4474](https://github.com/nodejs/node/pull/4474)
+* [[`08a3490dd6`](https://github.com/nodejs/node/commit/08a3490dd6)] - **test**: inherit JOBS from environment (Johan Bergström) [#4495](https://github.com/nodejs/node/pull/4495)
+* [[`3bfc18763a`](https://github.com/nodejs/node/commit/3bfc18763a)] - **test**: improve assert message (Rich Trott) [#4461](https://github.com/nodejs/node/pull/4461)
+* [[`d46d850461`](https://github.com/nodejs/node/commit/d46d850461)] - **test**: shorten path for bogus socket (Rich Trott) [#4478](https://github.com/nodejs/node/pull/4478)
+* [[`f68f86cd0a`](https://github.com/nodejs/node/commit/f68f86cd0a)] - **test**: fix race condition in test-http-client-onerror (Devin Nakamura) [#4346](https://github.com/nodejs/node/pull/4346)
+* [[`ec0b6362cf`](https://github.com/nodejs/node/commit/ec0b6362cf)] - **test**: remove unused assert module imports (Rich Trott) [#4438](https://github.com/nodejs/node/pull/4438)
+* [[`ba2445046c`](https://github.com/nodejs/node/commit/ba2445046c)] - **test**: don't use cwd for relative path (Johan Bergström) [#4477](https://github.com/nodejs/node/pull/4477)
+* [[`5110e4deed`](https://github.com/nodejs/node/commit/5110e4deed)] - **test**: don't assume a certain folder structure (Johan Bergström) [#3325](https://github.com/nodejs/node/pull/3325)
+* [[`55c6946400`](https://github.com/nodejs/node/commit/55c6946400)] - **test**: make temp path customizable (Johan Bergström) [#3325](https://github.com/nodejs/node/pull/3325)
+* [[`b19d19efaa`](https://github.com/nodejs/node/commit/b19d19efaa)] - **test**: extend timeout in Debug mode (Rich Trott) [#4431](https://github.com/nodejs/node/pull/4431)
+* [[`c6a99ddd37`](https://github.com/nodejs/node/commit/c6a99ddd37)] - **test**: remove unused variables from net tests (Rich Trott) [#4430](https://github.com/nodejs/node/pull/4430)
+* [[`54004f0e26`](https://github.com/nodejs/node/commit/54004f0e26)] - **test**: remove unused vars in ChildProcess tests (Rich Trott) [#4425](https://github.com/nodejs/node/pull/4425)
+* [[`e72112f90e`](https://github.com/nodejs/node/commit/e72112f90e)] - **test**: fix flaky cluster-disconnect-race (Brian White) [#4457](https://github.com/nodejs/node/pull/4457)
+* [[`715afc9bbd`](https://github.com/nodejs/node/commit/715afc9bbd)] - **test**: fix flaky cluster-net-send (Brian White) [#4444](https://github.com/nodejs/node/pull/4444)
+* [[`03c4bc704f`](https://github.com/nodejs/node/commit/03c4bc704f)] - **test**: fix flaky child-process-fork-regr-gh-2847 (Brian White) [#4442](https://github.com/nodejs/node/pull/4442)
+* [[`684eb32072`](https://github.com/nodejs/node/commit/684eb32072)] - **test**: remove unused variables from HTTPS tests (Rich Trott) [#4426](https://github.com/nodejs/node/pull/4426)
+* [[`585c01f674`](https://github.com/nodejs/node/commit/585c01f674)] - **test**: remove unused variables from TLS tests (Rich Trott) [#4424](https://github.com/nodejs/node/pull/4424)
+* [[`c36ca37e2a`](https://github.com/nodejs/node/commit/c36ca37e2a)] - **test**: remove unused variables form http tests (Rich Trott) [#4422](https://github.com/nodejs/node/pull/4422)
+* [[`c639d0f1fe`](https://github.com/nodejs/node/commit/c639d0f1fe)] - **test**: mark test-debug-no-context is flaky (Rich Trott) [#4421](https://github.com/nodejs/node/pull/4421)
+* [[`cd79ec268d`](https://github.com/nodejs/node/commit/cd79ec268d)] - **test**: remove unnecessary assignments (Rich Trott) [#4408](https://github.com/nodejs/node/pull/4408)
+* [[`0799a9abaf`](https://github.com/nodejs/node/commit/0799a9abaf)] - **test**: remove unused var from test-assert.js (Rich Trott) [#4405](https://github.com/nodejs/node/pull/4405)
+* [[`3710028a85`](https://github.com/nodejs/node/commit/3710028a85)] - **test**: remove unused `util` imports (Rich Trott) [#4397](https://github.com/nodejs/node/pull/4397)
+* [[`8c9d0c1f6f`](https://github.com/nodejs/node/commit/8c9d0c1f6f)] - **test**: refactor test-net-connect-options-ipv6 (Rich Trott) [#4395](https://github.com/nodejs/node/pull/4395)
+* [[`874209022f`](https://github.com/nodejs/node/commit/874209022f)] - **test**: fix http-response-multiheaders (Santiago Gimeno) [#3958](https://github.com/nodejs/node/pull/3958)
+* [[`71b79bcf54`](https://github.com/nodejs/node/commit/71b79bcf54)] - **test**: test each block in addon.md contains js & cc (Rod Vagg) [#4411](https://github.com/nodejs/node/pull/4411)
+* [[`00b37de243`](https://github.com/nodejs/node/commit/00b37de243)] - **test**: fix domain-top-level-error-handler-throw (Santiago Gimeno) [#4364](https://github.com/nodejs/node/pull/4364)
+* [[`6d14b6520f`](https://github.com/nodejs/node/commit/6d14b6520f)] - **test**: use platformTimeout() in more places (Brian White) [#4387](https://github.com/nodejs/node/pull/4387)
+* [[`82f74caa56`](https://github.com/nodejs/node/commit/82f74caa56)] - **test**: fix flaky test-net-error-twice (Brian White) [#4342](https://github.com/nodejs/node/pull/4342)
+* [[`96501e55be`](https://github.com/nodejs/node/commit/96501e55be)] - **test**: try other ipv6 localhost alternatives (Brian White) [#4325](https://github.com/nodejs/node/pull/4325)
+* [[`69343d6d2e`](https://github.com/nodejs/node/commit/69343d6d2e)] - **tls_wrap**: clear errors on return (Fedor Indutny) [#4515](https://github.com/nodejs/node/pull/4515)
+* [[`ca9812cf4d`](https://github.com/nodejs/node/commit/ca9812cf4d)] - **tools**: fix warning in doc parsing (Shigeki Ohtsu) [#4537](https://github.com/nodejs/node/pull/4537)
+* [[`386030b524`](https://github.com/nodejs/node/commit/386030b524)] - **tools**: implement no-unused-vars for eslint (Rich Trott) [#4536](https://github.com/nodejs/node/pull/4536)
+* [[`14a947fc70`](https://github.com/nodejs/node/commit/14a947fc70)] - **tools**: run tick processor without forking (Matt Loring) [#4224](https://github.com/nodejs/node/pull/4224)
+* [[`8039ca06eb`](https://github.com/nodejs/node/commit/8039ca06eb)] - **util**: faster arrayToHash (Jackson Tian)  [#3964](https://github.com/nodejs/node/pull/3964)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.4.0/node-v5.4.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.4.0/node-v5.4.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.4.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.4.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.4.0/node-v5.4.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.4.0/node-v5.4.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.4.0/node-v5.4.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.4.0/<br>
+Documentation: https://nodejs.org/docs/v5.4.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+efc7422f46ff2c9961ea984ced72b74f9c6c2e4e73f51ad83ff35c63835323f9  node-v5.4.0-darwin-x64.tar.gz
+d30efc022f6f893aa452c55a04832e44dda208c887230bb49d12a0bbeb3d0e95  node-v5.4.0-darwin-x64.tar.xz
+6f3de4df2ac30c1205ea228a1a9de6acd841255ee19229169bbb92318a75db0b  node-v5.4.0-headers.tar.gz
+19efc897e1a90e5aa66be9637dfc1e9b26950acb68f1521d52f9db62d8e5fa38  node-v5.4.0-headers.tar.xz
+0cb2c093e75090281423a2b3681629c663c83dac4587a12b77022afccd7aedc0  node-v5.4.0-linux-arm64.tar.gz
+c29e7d39457375b9bafd078019a7efa116d1aa2536a4d2af542e070fb49ef9f9  node-v5.4.0-linux-arm64.tar.xz
+108e6314f0b88ab6fdebe85885797a59dbfd7c4857f2976ce5b98c981162e01b  node-v5.4.0-linux-armv6l.tar.gz
+30c3c3d00e117cfe8afc3f19ae67ca00d129b14c085d6b6fd1c27175b350be53  node-v5.4.0-linux-armv6l.tar.xz
+e69b3f90b56f027dd0435b8b7a2f4ffa7ed3d8185e2162a08d6d2cf097370a97  node-v5.4.0-linux-armv7l.tar.gz
+1307e47e10d230cfbaf0eadb8bcfcf24bccca90108f2b3f91d2944d6739528e3  node-v5.4.0-linux-armv7l.tar.xz
+f037e2734f52b9de63e6d4a4e80756477b843e6f106e0be05591a16b71ec2bd0  node-v5.4.0-linux-x64.tar.gz
+ca1d6567716b47441c4f38ed344b00ba9fc48f83b333edfa5bc6b54d9253279f  node-v5.4.0-linux-x64.tar.xz
+8c3d8afb79d9ba5f381ed549521ca8183975dfad2d50290686657b8ce4304a4c  node-v5.4.0-linux-x86.tar.gz
+5e06288b4a816d0d32686d40734745cf04259d54392e41bd1853d5a84bffa324  node-v5.4.0-linux-x86.tar.xz
+4882333d6e4dad5e39599f918aa7e60f5125ce14f2c6f4ba32a58d08bb1781fe  node-v5.4.0.pkg
+97a90d9ee302949b5b8f0e1d64933cc1d64725b09d2eb034bb24deb4c336a511  node-v5.4.0-sunos-x64.tar.gz
+9748663f02aedcbebd0e0dcfbe34c37ac9dc9e4330b6ad73258deb8c104be074  node-v5.4.0-sunos-x64.tar.xz
+dcfe2748bcbc6bd6250be0d91b0f3a432b4e01a8d809fdd769a9b8e646e009a3  node-v5.4.0-sunos-x86.tar.gz
+a664e69f12222d28cd8476faa950a2859367a9c200fdad415b59caf479498b7f  node-v5.4.0-sunos-x86.tar.xz
+1dfe37a00cf0ed62beb73071f571ac56697f544a98cc2ff3318faec6363d72ab  node-v5.4.0.tar.gz
+744a31979b7c48a9c605fbfa7c159fcd60732ce27061671fe03847ffe448a5a3  node-v5.4.0.tar.xz
+198afe1118b310714f785e360f45928e25818cb03821bf941b1138b271676342  node-v5.4.0-x64.msi
+d1d2805d2ecb7695339d4092314635ca4fa602472af98ac0685aac5ff61ece91  node-v5.4.0-x86.msi
+f70cf7863ae4b69ab0cdbbc38a40cac40b13c52a4d2e91e5d4d6d2c1067553f5  win-x64/node.exe
+efd4ab0aa6888abc697319444772d182eda025c54b0bf730e7f38b71ba43ddf6  win-x64/node.lib
+3da18aeb3578bc5a683d2f1d853180c591d02fbbb2d6a43246dbf67003eb0307  win-x86/node.exe
+9f836eba3f5d231f981173ee0a3fc5fdafee97298e031669a3ff94e886279a1b  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJWjZeGAAoJEEX17r2BPa6Oi4oQAIe0+WIY0g+C5zIDfKxVz1jW
+5BZVT/eQKDbZG94p+ONIJElmeexRsNKm0389DD/lXmG7ilJLAUGQgeYLgyyRfpF9
+iQRKdUVJICuuHNzUQH2lkDdILbYESBM9MPCVQXUALO7ZP4/D0zZeHIwD3Au5QRJU
+hsxeMLeooP21PBuAR/t1Xxm3OrXMd7bRDinUCXmYcAHZ4SNLkxbI86oQPOTsyPLz
+dI8cOW/50REvyocGK0tqVRlsx46ZAYDBTZpUBOAdew1dmpDfsJfawZCBPke+FBY2
+PSJymxKK2GaZMu92s9wdyKtFk6wf17ySGm5w3DvoqLG3VjK7GgPdsEW1y5rm5xp3
+uR68sS/us63Om1VHYo/GtD7u1bnoXvugvILqazZA4b0iVstFzG0Wpde7OuB6v+MB
+wTKLrY8Y9MU5xf3uUk00KkaUvsAielpgDEJzkjYTEff+zNnwcV+CRwW8RKaGwQBu
+GBuO9SGLwTW1a/oLWvzMH7D21dnzNG327GSHUH4tzKVuefloHovWxcXUYk1SjFlv
+nXIFUx9uaiE2m4qMA+RBZqm7B6USwHi74219ABAZEyf4MTWpASNZPZZxJjtucfvC
+Z3drrsZ7gJerovpvBu0HdqQxAHOxBJFc7eJK6PjoFaMKveR5/LXZ08bo1Wgyqtv9
+BJeCTm2GksNuW04aimOZ
+=/3YZ
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.4.1.md b/locale/uk/blog/release/v5.4.1.md
new file mode 100755
index 0000000000000..1daab496db50a
--- /dev/null
+++ b/locale/uk/blog/release/v5.4.1.md
@@ -0,0 +1,124 @@
+---
+date: 2016-01-12T23:59:28.459Z
+version: 5.4.1
+category: release
+title: Node v5.4.1 (Current)
+slug: node-v5-4-1
+layout: blog-post.hbs
+author: Myles Borins
+---
+
+### Notable Changes
+
+* Minor performance improvements:
+  - **module**: move unnecessary work for early return (Andres Suarez) [#3579](https://github.com/nodejs/node/pull/3579)
+* Various bug fixes
+* Various doc fixes
+* Various test improvements
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`ff539c5bb5`](https://github.com/nodejs/node/commit/ff539c5bb5)] - **cluster**: ignore queryServer msgs on disconnection (Santiago Gimeno) [#4465](https://github.com/nodejs/node/pull/4465)
+* [[`00148b3de1`](https://github.com/nodejs/node/commit/00148b3de1)] - **deps**: backport 066747e from upstream V8 (Ali Ijaz Sheikh) [#4625](https://github.com/nodejs/node/pull/4625)
+* [[`3912b5cbda`](https://github.com/nodejs/node/commit/3912b5cbda)] - **doc**: adds usage of readline line-by-line parsing (Robert Jefe Lindstaedt) [#4609](https://github.com/nodejs/node/pull/4609)
+* [[`102fb7d3a1`](https://github.com/nodejs/node/commit/102fb7d3a1)] - **doc**: remove "above" and "below" references (Richard Sun) [#4499](https://github.com/nodejs/node/pull/4499)
+* [[`df87176ae0`](https://github.com/nodejs/node/commit/df87176ae0)] - **doc**: update stylesheet to match frontpage (Roman Reiss) [#4621](https://github.com/nodejs/node/pull/4621)
+* [[`ede98d1f98`](https://github.com/nodejs/node/commit/ede98d1f98)] - **doc**: stronger suggestion for userland assert (Wyatt Preul) [#4535](https://github.com/nodejs/node/pull/4535)
+* [[`fdfc72c977`](https://github.com/nodejs/node/commit/fdfc72c977)] - **doc**: label http.IncomingMessage as a Class (Sequoia McDowell) [#4589](https://github.com/nodejs/node/pull/4589)
+* [[`b181e26975`](https://github.com/nodejs/node/commit/b181e26975)] - **doc**: document http's server.listen return value (Sequoia McDowell) [#4590](https://github.com/nodejs/node/pull/4590)
+* [[`97aaeb8519`](https://github.com/nodejs/node/commit/97aaeb8519)] - **doc**: fix description about the latest-codename (Minwoo Jung) [#4583](https://github.com/nodejs/node/pull/4583)
+* [[`0126615d1e`](https://github.com/nodejs/node/commit/0126615d1e)] - **doc**: add Evan Lucas to Release Team (Evan Lucas) [#4579](https://github.com/nodejs/node/pull/4579)
+* [[`ec73c69412`](https://github.com/nodejs/node/commit/ec73c69412)] - **doc**: add Myles Borins to Release Team (Myles Borins) [#4578](https://github.com/nodejs/node/pull/4578)
+* [[`e703c9a4e2`](https://github.com/nodejs/node/commit/e703c9a4e2)] - **doc**: bring releases.md up to date (cjihrig) [#4540](https://github.com/nodejs/node/pull/4540)
+* [[`ac1108d5e7`](https://github.com/nodejs/node/commit/ac1108d5e7)] - **doc**: add missing backtick for readline (Brian White) [#4549](https://github.com/nodejs/node/pull/4549)
+* [[`09bc0c6a05`](https://github.com/nodejs/node/commit/09bc0c6a05)] - **doc**: improvements to crypto.markdown copy (James M Snell) [#4435](https://github.com/nodejs/node/pull/4435)
+* [[`787c5d96bd`](https://github.com/nodejs/node/commit/787c5d96bd)] - **http**: remove variable redeclaration (Rich Trott) [#4612](https://github.com/nodejs/node/pull/4612)
+* [[`145b66820f`](https://github.com/nodejs/node/commit/145b66820f)] - **module**: move unnecessary work for early return (Andres Suarez) [#3579](https://github.com/nodejs/node/pull/3579)
+* [[`ffb7deb443`](https://github.com/nodejs/node/commit/ffb7deb443)] - **net**: remove hot path comment from connect (Evan Lucas) [#4648](https://github.com/nodejs/node/pull/4648)
+* [[`799aa74d90`](https://github.com/nodejs/node/commit/799aa74d90)] - **net**: fix dns lookup for android (Josh Dague) [#4580](https://github.com/nodejs/node/pull/4580)
+* [[`9accebe087`](https://github.com/nodejs/node/commit/9accebe087)] - **net, doc**: fix line wrapping lint in net.js (James M Snell) [#4588](https://github.com/nodejs/node/pull/4588)
+* [[`37a546b490`](https://github.com/nodejs/node/commit/37a546b490)] - **src**: remove redeclarations of variables (Rich Trott) [#4605](https://github.com/nodejs/node/pull/4605)
+* [[`b515ccc2a1`](https://github.com/nodejs/node/commit/b515ccc2a1)] - **stream**: remove useless if test in transform (zoubin) [#4617](https://github.com/nodejs/node/pull/4617)
+* [[`ea6e26d904`](https://github.com/nodejs/node/commit/ea6e26d904)] - **test**: remove duplicate fork module import (Rich Trott) [#4634](https://github.com/nodejs/node/pull/4634)
+* [[`b14b2aec5e`](https://github.com/nodejs/node/commit/b14b2aec5e)] - **test**: require common module only once (Rich Trott) [#4611](https://github.com/nodejs/node/pull/4611)
+* [[`f28a640505`](https://github.com/nodejs/node/commit/f28a640505)] - **test**: only include http module once (Rich Trott) [#4606](https://github.com/nodejs/node/pull/4606)
+* [[`6f9a96f497`](https://github.com/nodejs/node/commit/6f9a96f497)] - **test**: fix flaky unrefed timers test (Rich Trott) [#4599](https://github.com/nodejs/node/pull/4599)
+* [[`b70eec8f7b`](https://github.com/nodejs/node/commit/b70eec8f7b)] - **tls_legacy**: do not read on OpenSSL's stack (Fedor Indutny) [#4624](https://github.com/nodejs/node/pull/4624)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.4.1/node-v5.4.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.4.1/node-v5.4.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.4.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.4.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.4.1/node-v5.4.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.4.1/node-v5.4.1-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.4.1/node-v5.4.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.4.1/<br>
+Documentation: https://nodejs.org/docs/v5.4.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+c523472a5972823e8b6baf2419f837885321c772612ec508a65614c758e25a46  node-v5.4.1-darwin-x64.tar.gz
+c4c721d7ef2fba4e5b21dfc8017bda10c8a4d8ff322f7545e74943ca9828ee89  node-v5.4.1-darwin-x64.tar.xz
+fd91d8fcbe72c76d1e58ddb3ba8bc08073c8c1e6d595bfe4b8b22e9b92855ed7  node-v5.4.1-headers.tar.gz
+17424fc015dc668480537fd32f67f4d85d6e78e37f87d5eef58ef12d40bcd335  node-v5.4.1-headers.tar.xz
+362ae4539b6be075b6757ba689f0ae522cfc9340c81061aca880f92fce9595c7  node-v5.4.1-linux-arm64.tar.gz
+40f8e6485759a5c5f166745f7d8f33285ef425d2fe569d085220fd954fb790b9  node-v5.4.1-linux-arm64.tar.xz
+21617e86758f1f95a3b9444be965aa87907410d786529cfd6aa2169ab7b5e15b  node-v5.4.1-linux-armv6l.tar.gz
+2698fdd1bcfb2234f65b786c0a46ac29bf2c301c992fd72045fd03553a57e298  node-v5.4.1-linux-armv6l.tar.xz
+af36dff32934dea9446673a5453efcda6e4621ce7fa73e0a401f1444c2f929af  node-v5.4.1-linux-armv7l.tar.gz
+09b346ee665e3510fe8679df95bc32e8dda5953e05807c21816a25b9f5969dd4  node-v5.4.1-linux-armv7l.tar.xz
+1880f3421da5579678803a523c314b345f5db00799b51b7fd9484a3248efc068  node-v5.4.1-linux-x64.tar.gz
+9d264641df98742246bfd868e84cf98f649077f31eeae58931a31b0b5eee05a0  node-v5.4.1-linux-x64.tar.xz
+184790d2ec8f95a75e7e746b3007e848aeba91be14ad7cec415b425df0df92e5  node-v5.4.1-linux-x86.tar.gz
+a18707f7ac559563220e3319f251a2a5479b8445538f757df3a6c2dead007f1b  node-v5.4.1-linux-x86.tar.xz
+059aae464e48cc11c5af1a12f47e6859da28b0fcf794f5c33d14ab7235fee1db  node-v5.4.1.pkg
+956b3b0790b5742765966c6851e43c6fca298ecfb8c7102fd87e5fb6294bebd4  node-v5.4.1-sunos-x64.tar.gz
+5644e5998d58bfac337a7c8672de68ec0a6dc55366a098b2364b9fbad6b345d8  node-v5.4.1-sunos-x64.tar.xz
+a3eb11d58760b4b9007ac882c02e7608549fe7f65124ca90a387ba71c524b3e2  node-v5.4.1-sunos-x86.tar.gz
+b8e78738f2714e34705eebd207400af422cee0842e7c599ab5077a4e51ed8453  node-v5.4.1-sunos-x86.tar.xz
+78455ef2e3dea06b7d13d393c36711009048a91e5de5892523ec4a9be5a55e0c  node-v5.4.1.tar.gz
+4e7d3fdfeac85c46ddaef0224695620f218e7a178e97d6e210d6d643483f1d53  node-v5.4.1.tar.xz
+a65a1eaeb1bd234516232803839ef5a2f6526730abfef98724c103f76a8b5440  node-v5.4.1-x64.msi
+d06e7a697d7519b83dbaf631ad45103f8768f6bfef13fa3ce8bddba9d9f436f2  node-v5.4.1-x86.msi
+85311ba0ce30a6f41c6d677c33f4c198e3a3f4a4e62754a84c6c3036a1fc6e4f  win-x64/node.exe
+e2715e5383d61c67d4f7d41f1fc760ef311c89b365b931720a452f1409ccabb4  win-x64/node.lib
+3edae51060629596c592e2bee4da15a4b3f7e36f0cb80c8a2fd6eedcefd0de13  win-x86/node.exe
+0dbb491180a380170bb89dc6976207c96c50aaf849021c7b049065c169fd09ef  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJWlZAFAAoJEEX17r2BPa6Oo3wQAKVEfZyDKAhbhg6r+x87tRqO
+zsyNpefHA3KPvnRJbZsVD2vvj2Arvv8uaYwHk9rE0IdErP55MzGzJpaf6s2CsKaZ
+qLZc+vcmvtdUFv5oiXrwCGZ2YSUtUrudHXyyve/qo4y1SuUagpDRT8ohjhn7Vlds
+qnJ2FohUU4oVclHXYKxpH5+5rd4WP4mtz8WIXrmzXn+OHmc9io1qzyzx7tVTK9J4
+BGZYZa1BAZ76ETCy8juipiN06T7CYnYYKJ/ti4dDCnG8cRZ5ohqPI5XtqLr4HVmv
+6Pfrjw3RRRvmTgqHxX0MZF2TZjDi9Rl6fzYmOWJL9emG3lVZmCI96V7t7JGZWbFi
+zVEIFoNE/UBw+Rqd4aUELJ4xALcj+vDWvvC2x+W5bEndorgbNWEBUyq6SwwQ1k/T
+9xlXddo92LVWVQjD+PJzV517MKgyHcch2xzAxaAXIRsNuVGMpkThSXeTX0n11HAV
+I+R0NHV5vuOdFt+KiENJmsD9RiszmRK3KWeRETwaelmHMR1jq25JcijOHokE0gB7
+oV64W9uuVkzrOEQUgBvRF/4Ov+PVM8IPAj9EqZM6xkIGEyq9fCSn9ddJMTF2xKDO
+9lD3o44MNAL/ml3wAnm10WltUkCLSHd3Cyi0/7ygeIp0KeUXuaix1sVrGJmZpgIn
+bNZ8ZbcRnuEiPnh8a/if
+=o+WC
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.5.0.md b/locale/uk/blog/release/v5.5.0.md
new file mode 100755
index 0000000000000..623ba7b94e6b6
--- /dev/null
+++ b/locale/uk/blog/release/v5.5.0.md
@@ -0,0 +1,162 @@
+---
+date: 2016-01-21T02:26:55.519Z
+version: 5.5.0
+category: release
+title: Node v5.5.0 (Current)
+slug: node-v5-5-0
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+### Notable Changes
+
+- **events**: make sure console functions exist (Dave) [#4479](https://github.com/nodejs/node/pull/4479)
+- **fs**: add autoClose option to fs.createWriteStream (Saquib) [#3679](https://github.com/nodejs/node/pull/3679)
+- **http**: improves expect header handling (Daniel Sellers) [#4501](https://github.com/nodejs/node/pull/4501)
+- **node**: allow preload modules with -i (Evan Lucas) [#4696](https://github.com/nodejs/node/pull/4696)
+- **v8,src**: expose statistics about heap spaces (`v8.getHeapSpaceStatistics()`) (Ben Ripkens) [#4463](https://github.com/nodejs/node/pull/4463)
+* Minor performance improvements:
+  - **lib**: Use arrow functions instead of bind where possible (Minwoo Jung) [#3622](https://github.com/nodejs/node/pull/3622).
+    - (Mistakenly missing from v5.4.0)
+  - **module**: cache stat() results more aggressively (Ben Noordhuis) [#4575](https://github.com/nodejs/node/pull/4575)
+  - **querystring**: improve parse() performance (Brian White) [#4675](https://github.com/nodejs/node/pull/4675)
+
+### Known issues
+
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* Unicode characters in filesystem paths are not handled consistently across platforms or Node.js APIs. See [#2088](https://github.com/nodejs/node/issues/2088), [#3401](https://github.com/nodejs/node/issues/3401) and [#3519](https://github.com/nodejs/node/issues/3519).
+
+### Commits
+
+* [[`8d0ca10752`](https://github.com/nodejs/node/commit/8d0ca10752)] - **buffer**: make byteLength work with Buffer correctly (Jackson Tian) [#4738](https://github.com/nodejs/node/pull/4738)
+* [[`83d2b7707e`](https://github.com/nodejs/node/commit/83d2b7707e)] - **buffer**: remove unnecessary TODO comments (Peter Geiss) [#4719](https://github.com/nodejs/node/pull/4719)
+* [[`8182ec094d`](https://github.com/nodejs/node/commit/8182ec094d)] - **build**: add option to select VS version (julien.waechter) [#4645](https://github.com/nodejs/node/pull/4645)
+* [[`4383acd9f4`](https://github.com/nodejs/node/commit/4383acd9f4)] - **build**: fix and refactor VTune config in vcbuild.bat (Rod Vagg) [#4192](https://github.com/nodejs/node/pull/4192)
+* [[`be0b0b8cb9`](https://github.com/nodejs/node/commit/be0b0b8cb9)] - **build**: minor corrections in VTune configure text (Rod Vagg) [#4192](https://github.com/nodejs/node/pull/4192)
+* [[`9571be12f6`](https://github.com/nodejs/node/commit/9571be12f6)] - **cluster**: fix race condition setting suicide prop (Santiago Gimeno) [#4349](https://github.com/nodejs/node/pull/4349)
+* [[`ebd9addcd1`](https://github.com/nodejs/node/commit/ebd9addcd1)] - **crypto**: clear error stack in ECDH::Initialize (Fedor Indutny) [#4689](https://github.com/nodejs/node/pull/4689)
+* [[`66b9c0d8bd`](https://github.com/nodejs/node/commit/66b9c0d8bd)] - **debugger**: remove variable redeclarations (Rich Trott) [#4633](https://github.com/nodejs/node/pull/4633)
+* [[`88b2889679`](https://github.com/nodejs/node/commit/88b2889679)] - **dgram**: prevent disabled optimization of bind() (Brian White) [#4613](https://github.com/nodejs/node/pull/4613)
+* [[`d56e3f8b67`](https://github.com/nodejs/node/commit/d56e3f8b67)] - **doc**: restore ICU third-party software licenses (Richard Lau) [#4762](https://github.com/nodejs/node/pull/4762)
+* [[`212a44df03`](https://github.com/nodejs/node/commit/212a44df03)] - **doc**: clarify protocol default in http.request() (cjihrig) [#4714](https://github.com/nodejs/node/pull/4714)
+* [[`3297036345`](https://github.com/nodejs/node/commit/3297036345)] - **doc**: update branch-diff arguments in release doc (Rod Vagg) [#4691](https://github.com/nodejs/node/pull/4691)
+* [[`666c089e68`](https://github.com/nodejs/node/commit/666c089e68)] - **doc**: fix named anchors in addons.markdown and http.markdown (Michael Theriot) [#4708](https://github.com/nodejs/node/pull/4708)
+* [[`310530b7ec`](https://github.com/nodejs/node/commit/310530b7ec)] - **doc**: add path property to Write/ReadStream in fs.markdown (Claudio Rodriguez) [#4368](https://github.com/nodejs/node/pull/4368)
+* [[`3470574cb6`](https://github.com/nodejs/node/commit/3470574cb6)] - **doc**: clarify explanation of first stream section (Vitor Cortez) [#4234](https://github.com/nodejs/node/pull/4234)
+* [[`d91646b9c7`](https://github.com/nodejs/node/commit/d91646b9c7)] - **doc**: rebuild LICENSE using tools/license-builder.sh (Rod Vagg) [#4194](https://github.com/nodejs/node/pull/4194)
+* [[`265e2f557b`](https://github.com/nodejs/node/commit/265e2f557b)] - **doc**: fix typo in doc/node.1 (Jérémy Lal) [#4680](https://github.com/nodejs/node/pull/4680)
+* [[`4c132fe61e`](https://github.com/nodejs/node/commit/4c132fe61e)] - **doc**: make references clickable (Roman Klauke) [#4654](https://github.com/nodejs/node/pull/4654)
+* [[`d139704ff7`](https://github.com/nodejs/node/commit/d139704ff7)] - **doc**: improve child_process.execFile() code example (Ryan Sobol) [#4504](https://github.com/nodejs/node/pull/4504)
+* [[`eeb6fdcd0f`](https://github.com/nodejs/node/commit/eeb6fdcd0f)] - **doc**: add docs for more stream options (zoubin) [#4639](https://github.com/nodejs/node/pull/4639)
+* [[`b6ab6d2de5`](https://github.com/nodejs/node/commit/b6ab6d2de5)] - **doc**: add branch-diff example to releases.md (Myles Borins) [#4636](https://github.com/nodejs/node/pull/4636)
+* [[`287325c5e8`](https://github.com/nodejs/node/commit/287325c5e8)] - **docs**: update gpg key for Myles Borins (Myles Borins) [#4657](https://github.com/nodejs/node/pull/4657)
+* [[`65825b79aa`](https://github.com/nodejs/node/commit/65825b79aa)] - **docs**: fix npm command in releases.md (Myles Borins) [#4656](https://github.com/nodejs/node/pull/4656)
+* [[`f9a59c1d3b`](https://github.com/nodejs/node/commit/f9a59c1d3b)] - **(SEMVER-MINOR)** **events**: make sure console functions exist (Dave) [#4479](https://github.com/nodejs/node/pull/4479)
+* [[`6039a7c1b5`](https://github.com/nodejs/node/commit/6039a7c1b5)] - **(SEMVER-MINOR)** **fs**: add autoClose option to fs.createWriteStream (Saquib) [#3679](https://github.com/nodejs/node/pull/3679)
+* [[`ed55169834`](https://github.com/nodejs/node/commit/ed55169834)] - **gitignore**: never ignore debug module (Michaël Zasso) [#2286](https://github.com/nodejs/node/pull/2286)
+* [[`d755432fa9`](https://github.com/nodejs/node/commit/d755432fa9)] - **(SEMVER-MINOR)** **http**: improves expect header handling (Daniel Sellers) [#4501](https://github.com/nodejs/node/pull/4501)
+* [[`7ce0e04f44`](https://github.com/nodejs/node/commit/7ce0e04f44)] - **lib**: fix style issues after eslint update (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`ae5bcf9528`](https://github.com/nodejs/node/commit/ae5bcf9528)] - **lib**: use arrow functions instead of bind (Minwoo Jung) [#3622](https://github.com/nodejs/node/pull/3622)
+* [[`0ec093cd41`](https://github.com/nodejs/node/commit/0ec093cd41)] - **lib,test**: remove extra semicolons (Michaël Zasso) [#2205](https://github.com/nodejs/node/pull/2205)
+* [[`d8f5bd4fe1`](https://github.com/nodejs/node/commit/d8f5bd4fe1)] - **module**: avoid ArgumentsAdaptorTrampoline frame (Ben Noordhuis) [#4575](https://github.com/nodejs/node/pull/4575)
+* [[`83f8d98806`](https://github.com/nodejs/node/commit/83f8d98806)] - **module**: cache stat() results more aggressively (Ben Noordhuis) [#4575](https://github.com/nodejs/node/pull/4575)
+* [[`ff64a4c395`](https://github.com/nodejs/node/commit/ff64a4c395)] - **(SEMVER-MINOR)** **node**: allow preload modules with -i (Evan Lucas) [#4696](https://github.com/nodejs/node/pull/4696)
+* [[`4bc1a47761`](https://github.com/nodejs/node/commit/4bc1a47761)] - **querystring**: improve parse() performance (Brian White) [#4675](https://github.com/nodejs/node/pull/4675)
+* [[`ad63d350d4`](https://github.com/nodejs/node/commit/ad63d350d4)] - **readline**: Remove XXX and output debuglog (Kohei TAKATA) [#4690](https://github.com/nodejs/node/pull/4690)
+* [[`da550aa063`](https://github.com/nodejs/node/commit/da550aa063)] - **repl**: make sure historyPath is trimmed (Evan Lucas) [#4539](https://github.com/nodejs/node/pull/4539)
+* [[`1a6e7d1b52`](https://github.com/nodejs/node/commit/1a6e7d1b52)] - **src**: fix negative values in process.hrtime() (Ben Noordhuis) [#4757](https://github.com/nodejs/node/pull/4757)
+* [[`8bad51977a`](https://github.com/nodejs/node/commit/8bad51977a)] - **src**: return UV_EAI_NODATA on empty lookup (cjihrig) [#4715](https://github.com/nodejs/node/pull/4715)
+* [[`761cf2bf6a`](https://github.com/nodejs/node/commit/761cf2bf6a)] - **src**: don't check failure with ERR_peek_error() (Ben Noordhuis) [#4731](https://github.com/nodejs/node/pull/4731)
+* [[`953f4a3999`](https://github.com/nodejs/node/commit/953f4a3999)] - **stream**: prevent object map change in ReadableState (Evan Lucas) [#4761](https://github.com/nodejs/node/pull/4761)
+* [[`e65f1f7954`](https://github.com/nodejs/node/commit/e65f1f7954)] - **test**: fix tls-multi-key race condition (Santiago Gimeno) [#3966](https://github.com/nodejs/node/pull/3966)
+* [[`3727ae0d7d`](https://github.com/nodejs/node/commit/3727ae0d7d)] - **test**: use addon.md block headings as test dir names (Rod Vagg) [#4412](https://github.com/nodejs/node/pull/4412)
+* [[`47960a07c0`](https://github.com/nodejs/node/commit/47960a07c0)] - **test**: make test-cluster-disconnect-leak reliable (Rich Trott) [#4736](https://github.com/nodejs/node/pull/4736)
+* [[`9926b5a25f`](https://github.com/nodejs/node/commit/9926b5a25f)] - **test**: fix issues for space-in-parens ESLint rule (Roman Reiss) [#4753](https://github.com/nodejs/node/pull/4753)
+* [[`d1aabd6264`](https://github.com/nodejs/node/commit/d1aabd6264)] - **test**: fix style issues after eslint update (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`e98bcfa2cb`](https://github.com/nodejs/node/commit/e98bcfa2cb)] - **test**: remove 1 second delay from test (Rich Trott) [#4616](https://github.com/nodejs/node/pull/4616)
+* [[`6cfd0b5a32`](https://github.com/nodejs/node/commit/6cfd0b5a32)] - **test**: fix flaky test-net-socket-local-address (cjihrig) [#4650](https://github.com/nodejs/node/pull/4650)
+* [[`e22cc6c2eb`](https://github.com/nodejs/node/commit/e22cc6c2eb)] - **test**: fix race in test-net-server-pause-on-connect (Rich Trott) [#4637](https://github.com/nodejs/node/pull/4637)
+* [[`9164c00bdb`](https://github.com/nodejs/node/commit/9164c00bdb)] - **test**: move resource intensive tests to sequential (Rich Trott) [#4615](https://github.com/nodejs/node/pull/4615)
+* [[`d8ba2c0de4`](https://github.com/nodejs/node/commit/d8ba2c0de4)] - **test**: fix `http-upgrade-client` flakiness (Santiago Gimeno) [#4602](https://github.com/nodejs/node/pull/4602)
+* [[`6018fa1f57`](https://github.com/nodejs/node/commit/6018fa1f57)] - **test**: fix `http-upgrade-agent` flakiness (Santiago Gimeno) [#4520](https://github.com/nodejs/node/pull/4520)
+* [[`c33f6a87d0`](https://github.com/nodejs/node/commit/c33f6a87d0)] - **tools**: enable space-in-parens ESLint rule (Roman Reiss) [#4753](https://github.com/nodejs/node/pull/4753)
+* [[`162e16afdb`](https://github.com/nodejs/node/commit/162e16afdb)] - **tools**: enable no-extra-semi rule in eslint (Michaël Zasso) [#2205](https://github.com/nodejs/node/pull/2205)
+* [[`031b87d42d`](https://github.com/nodejs/node/commit/031b87d42d)] - **tools**: add license-builder.sh to construct LICENSE (Rod Vagg) [#4194](https://github.com/nodejs/node/pull/4194)
+* [[`ec8e0ae697`](https://github.com/nodejs/node/commit/ec8e0ae697)] - **tools**: fix style issue after eslint update (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`4d5ee7a512`](https://github.com/nodejs/node/commit/4d5ee7a512)] - **tools**: update eslint config (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`2d441493a4`](https://github.com/nodejs/node/commit/2d441493a4)] - **tools**: update eslint to v1.10.3 (Michaël Zasso) [nodejs/io.js#2286](https://github.com/nodejs/io.js/pull/2286)
+* [[`aba3cc834e`](https://github.com/nodejs/node/commit/aba3cc834e)] - **tools**: fix license-builder.sh for ICU (Richard Lau) [#4762](https://github.com/nodejs/node/pull/4762)
+* [[`5f57005ec9`](https://github.com/nodejs/node/commit/5f57005ec9)] - **(SEMVER-MINOR)** **v8,src**: expose statistics about heap spaces (Ben Ripkens) [#4463](https://github.com/nodejs/node/pull/4463)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.5.0/node-v5.5.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.5.0/node-v5.5.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.5.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.5.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.5.0/node-v5.5.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-linux-armv6l.tar.gz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.5.0/node-v5.5.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.5.0/node-v5.5.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.5.0/<br>
+Documentation: https://nodejs.org/docs/v5.5.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+d4fd29e2d501963235104fc715fb0b55b302a40b605f432c456069606b939a46  node-v5.5.0-darwin-x64.tar.gz
+d993c26c6a3127911345f09a7b41a6d124bb894c819e30333ea110c16fe54f7f  node-v5.5.0-darwin-x64.tar.xz
+67ebc3989b98980c13ef17c1336b98ed2975aa093d9b69f399dfb93de5ae74b4  node-v5.5.0-headers.tar.gz
+f98d73e8e466faa526308e57a4f912a9eea0704a9b4cda8db89fee48062b1514  node-v5.5.0-headers.tar.xz
+a9ebfce36675cc8d5e1bea6fa57de7fd80e8016f5957340831fcd03560e59845  node-v5.5.0-linux-arm64.tar.gz
+81e51ee6dafc19bdb3b81fd136010212ee08ed6f58f44788923a2a56a9be86b6  node-v5.5.0-linux-arm64.tar.xz
+a156dfda7fa00ac7ea86ac3cff8d445c44bcec3c677db375776a0489ad7155bd  node-v5.5.0-linux-armv6l.tar.gz
+9cbbcd4ec70b2f2ff2a478c1d83ccda47af3dd96e66d47fee5869212f0d35c5a  node-v5.5.0-linux-armv6l.tar.xz
+cf9832efa0cac6365b4fec83df5dee8ecb67d39931c4e7cdaaa4cb933fb4b78b  node-v5.5.0-linux-armv7l.tar.gz
+cb8a11d3dd154c834373b6243edbd353e637b701ed05db0f3015577efbc66444  node-v5.5.0-linux-armv7l.tar.xz
+3e593d91b6d2ad871efaaf8e9a17b3608ca98904959bcfb7c42e6acce89e80f4  node-v5.5.0-linux-x64.tar.gz
+33b4d062f5ba5c8db86119b693273f0ca764fe0d076558bb8e645c37ea0b22fc  node-v5.5.0-linux-x64.tar.xz
+e384f8beb392cd5df882cd3401e449371190bc139010d391888c2f3346fb5107  node-v5.5.0-linux-x86.tar.gz
+7e4bd588e165aede4df22ea743548c61cee79faed4fd034b4e08e6b429576dfb  node-v5.5.0-linux-x86.tar.xz
+c192270ecc0e1c15513c27cab48811f52f37b3216b20d3bcfdd2172f0a06d7cb  node-v5.5.0.pkg
+e8abb364fc8db51e3a6c8dc14f24ec2c289940386c18da4ecb33462021c1bcef  node-v5.5.0-sunos-x64.tar.gz
+84737dc228b203077d0fe0a55247e7d0f2f68f2e9700bade8eb8cdd1ce1c2872  node-v5.5.0-sunos-x64.tar.xz
+c49c8ce8c997da2cf1ee1cccb55ed457d31aa85d4ec6f58edd868daaf29ddc45  node-v5.5.0-sunos-x86.tar.gz
+cd034dcac4018aa0c8c01142d3d16238ac73d643b7a9b4294542b2ee93e07d09  node-v5.5.0-sunos-x86.tar.xz
+d69b18cc20699a35434858fb853997616762280610a510ec4b4ff1a94798b432  node-v5.5.0.tar.gz
+9c46b4dc9548e43826f71f6571f56e39783c456b9516045b496ea73321731e22  node-v5.5.0.tar.xz
+ba1dcd3035b045fb4ecb254bab1e0dda24934f2a773e6e05d0a54ac4adc4ee3b  node-v5.5.0-x64.msi
+40b667ca279927aacbf65f32f0a3400ff2aba15db46fd3eb1a1d8b94b182bb12  node-v5.5.0-x86.msi
+74abfa53909b3011d67d0b76115d134642b946d19a17293f3421ee5d5d00f20a  win-x64/node.exe
+0cb30f8ab20fc91d72067e7812216b166a71b8de94a16ca79d3b316a76f476ed  win-x64/node.lib
+142156b0b895f4f4f0df80816bf4acde05a6b5166580e8124cfedc8e1a408783  win-x86/node.exe
+ff0f93aff2caaef5c45d1ca261a940ff6ad27148da4ded01d76dfe868a0904db  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJWoEGjAAoJELY7U1pMIGypci0QALw8WgMkTd4rqEqsE6QKoEdB
+iLXXCWf90IDa/4qJHYUX9roxyEV+XEaZjrIkd3HnUYZrjdqTl5Z1Rhe+wD7zH8Jk
+n31JOKaD+btxmhV6Exg2SBLZt38J3eoOwdnrSN0B3bEbC6FEKDdWDk3KPOu9Eh0j
+uIH+chSAlGJqYwC6NO6bxHKh3vlz7klD7KUMzVj2bas32UmdNKNT6r2LRFZMVknd
++GsM5LuHnD/nwh/ENnA2QjcHJEjmxxL1CmJFSMX0ITTMLzBDjcj8FCoDPdYQp0YQ
+ZKCJrvrBUAW+rSWxrDuKP0DqO2/47LmOcssGO3eR/w+q3lXvdj3f0EeLT2tdaiQ5
+eHn6RaJpzk0BTWrYh21C3BkAuZs3+nNG3i7rYxHBtCkYdjx4sNkwxCjblEEJtzJK
+39ygB0zNIrAFFNeqytSzkqjzkx+XD9CwzXVcC+s+zw0fCVOzvwh91jaNaG2haszD
+fDS02nW4VEy+7UQJ3Hf2ojIjetqZTWmGdFH/Y6016s+b9VEObgtEtGU38phatRuQ
+1k34Fk82u2LGAyaTEXuMILDPrONSXOtkaFlM3hkCV/V/1EgSRHTEfQetrrR7fW4R
+LYoyc03CsrjL3hm3gePbOjHqu/vDejqD8zttBwvGE1uPZlCOPiM8bb0IFuAZUzEo
+CtOuU8IYfoBYo8fOVLvl
+=xfMB
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.6.0.md b/locale/uk/blog/release/v5.6.0.md
new file mode 100755
index 0000000000000..1c0ee0d656d11
--- /dev/null
+++ b/locale/uk/blog/release/v5.6.0.md
@@ -0,0 +1,227 @@
+---
+date: 2016-02-09T17:32:46.793Z
+version: 5.6.0
+category: release
+title: Node v5.6.0 (Current)
+slug: node-v5-6-0
+layout: blog-post.hbs
+author: James M Snell
+---
+
+This is an important security release. For full details see https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ for details on patched vulnerabilities.
+
+### Notable changes
+
+* **http**: fix defects in HTTP header parsing for requests and responses that can allow request smuggling (CVE-2016-2086) or response splitting (CVE-2016-2216). HTTP header parsing now aligns more closely with the HTTP spec including restricting the acceptable characters.
+* **http-parser**: upgrade from 2.6.0 to 2.6.1
+* **npm**: upgrade npm from 3.3.12 to 3.6.0 (Rebecca Turner) [#4958](https://github.com/nodejs/node/pull/4958)
+* **openssl**: upgrade from 1.0.2e to 1.0.2f. To mitigate against the Logjam attack, TLS clients now reject Diffie-Hellman handshakes with parameters shorter than 1024-bits, up from the previous limit of 768-bits.
+
+### Commits
+
+* [[`3b6283c163`](https://github.com/nodejs/node/commit/3b6283c163)] - **benchmark**: add a constant declaration for `net` (Minwoo Jung) [#3950](https://github.com/nodejs/node/pull/3950)
+* [[`3175f7450e`](https://github.com/nodejs/node/commit/3175f7450e)] - **buffer**: remove duplicated code in fromObject (HUANG Wei) [#4948](https://github.com/nodejs/node/pull/4948)
+* [[`58d67e26a2`](https://github.com/nodejs/node/commit/58d67e26a2)] - **buffer**: validate list elements in Buffer.concat (Michaël Zasso) [#4951](https://github.com/nodejs/node/pull/4951)
+* [[`bafc86f00e`](https://github.com/nodejs/node/commit/bafc86f00e)] - **buffer**: refactor redeclared variables (Rich Trott) [#4886](https://github.com/nodejs/node/pull/4886)
+* [[`0fa4d90b94`](https://github.com/nodejs/node/commit/0fa4d90b94)] - **build**: Add VARIATION variable to binary target (Stefan Budeanu) [#4631](https://github.com/nodejs/node/pull/4631)
+* [[`ec62789152`](https://github.com/nodejs/node/commit/ec62789152)] - **crypto**: fix memory leak in LoadPKCS12 (Fedor Indutny) [#5109](https://github.com/nodejs/node/pull/5109)
+* [[`d9e934c71f`](https://github.com/nodejs/node/commit/d9e934c71f)] - **crypto**: add `pfx` certs as CA certs too (Fedor Indutny) [#5109](https://github.com/nodejs/node/pull/5109)
+* [[`0d4b538175`](https://github.com/nodejs/node/commit/0d4b538175)] - **crypto**: use SSL_CTX_clear_extra_chain_certs. (Adam Langley) [#4919](https://github.com/nodejs/node/pull/4919)
+* [[`abb0f6cd53`](https://github.com/nodejs/node/commit/abb0f6cd53)] - **crypto**: fix build when OCSP-stapling not provided (Adam Langley) [#4914](https://github.com/nodejs/node/pull/4914)
+* [[`755619c554`](https://github.com/nodejs/node/commit/755619c554)] - **crypto**: use a const SSL_CIPHER (Adam Langley) [#4913](https://github.com/nodejs/node/pull/4913)
+* [[`d5d2f86f89`](https://github.com/nodejs/node/commit/d5d2f86f89)] - **(SEMVER-MINOR)** **deps**: update http-parser to version 2.6.1 (James M Snell)
+* [[`f0bd176d6d`](https://github.com/nodejs/node/commit/f0bd176d6d)] - **deps**: reapply c-ares floating patch (Ben Noordhuis) [#5090](https://github.com/nodejs/node/pull/5090)
+* [[`f1a0827417`](https://github.com/nodejs/node/commit/f1a0827417)] - **deps**: sync with upstream bagder/c-ares@2bae2d5 (Fedor Indutny) [#5090](https://github.com/nodejs/node/pull/5090)
+* [[`cbf36de8f1`](https://github.com/nodejs/node/commit/cbf36de8f1)] - **deps**: upgrade npm to 3.6.0 (Rebecca Turner) [#4958](https://github.com/nodejs/node/pull/4958)
+* [[`dd97d07a0d`](https://github.com/nodejs/node/commit/dd97d07a0d)] - **deps**: backport 8d00c2c from v8 upstream (Gibson Fahnestock) [#5024](https://github.com/nodejs/node/pull/5024)
+* [[`b75263094b`](https://github.com/nodejs/node/commit/b75263094b)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [#1836](https://github.com/nodejs/node/pull/1836)
+* [[`b312b7914f`](https://github.com/nodejs/node/commit/b312b7914f)] - **deps**: upgrade openssl sources to 1.0.2f (Myles Borins) [#4961](https://github.com/nodejs/node/pull/4961)
+* [[`fa0457ed04`](https://github.com/nodejs/node/commit/fa0457ed04)] - **dns**: throw a TypeError in lookupService with invalid port (Evan Lucas) [#4839](https://github.com/nodejs/node/pull/4839)
+* [[`c4c8b3bf2e`](https://github.com/nodejs/node/commit/c4c8b3bf2e)] - **doc**: fix dgram doc indentation (Rich Trott) [#5118](https://github.com/nodejs/node/pull/5118)
+* [[`027cd2719f`](https://github.com/nodejs/node/commit/027cd2719f)] - **doc**: clarify code of conduct reporting (Julie Pagano) [#5107](https://github.com/nodejs/node/pull/5107)
+* [[`9f7aa6f868`](https://github.com/nodejs/node/commit/9f7aa6f868)] - **doc**: clarify dgram socket.send() multi-buffer support (Matteo Collina) [#5130](https://github.com/nodejs/node/pull/5130)
+* [[`a96ae2cb37`](https://github.com/nodejs/node/commit/a96ae2cb37)] - **doc**: console is asynchronous unless it's a file (Ben Noordhuis) [#5133](https://github.com/nodejs/node/pull/5133)
+* [[`4c54c8f309`](https://github.com/nodejs/node/commit/4c54c8f309)] - **doc**: fix typo in dgram doc (Rich Trott) [#5114](https://github.com/nodejs/node/pull/5114)
+* [[`9c93ea3d51`](https://github.com/nodejs/node/commit/9c93ea3d51)] - **doc**: fix links order in Buffer doc (Alexander Makarenko) [#5076](https://github.com/nodejs/node/pull/5076)
+* [[`a0ba378880`](https://github.com/nodejs/node/commit/a0ba378880)] - **doc**: minor improvement in OS docs (Alexander Makarenko) [#5006](https://github.com/nodejs/node/pull/5006)
+* [[`1e2108a6b7`](https://github.com/nodejs/node/commit/1e2108a6b7)] - **doc**: fix links in Addons docs (Alexander Makarenko) [#5072](https://github.com/nodejs/node/pull/5072)
+* [[`e5134b1701`](https://github.com/nodejs/node/commit/e5134b1701)] - **doc**: fix inconsistent styling (Brian White) [#4996](https://github.com/nodejs/node/pull/4996)
+* [[`dde160378e`](https://github.com/nodejs/node/commit/dde160378e)] - **doc**: fix link in cluster documentation (Timothy Gu) [#5068](https://github.com/nodejs/node/pull/5068)
+* [[`e5254c12f4`](https://github.com/nodejs/node/commit/e5254c12f4)] - **doc**: fix reference to  API `hash.final` (Minwoo Jung) [#5050](https://github.com/nodejs/node/pull/5050)
+* [[`87fd9968a8`](https://github.com/nodejs/node/commit/87fd9968a8)] - **doc**: clarify optional arguments of Buffer methods (Michaël Zasso) [#5008](https://github.com/nodejs/node/pull/5008)
+* [[`9908eced24`](https://github.com/nodejs/node/commit/9908eced24)] - **doc**: uppercase 'RSA-SHA256' in crypto.markdown (Rainer Oviir) [#5044](https://github.com/nodejs/node/pull/5044)
+* [[`bf0383bbea`](https://github.com/nodejs/node/commit/bf0383bbea)] - **doc**: apply consistent styling for functions (Rich Trott) [#4974](https://github.com/nodejs/node/pull/4974)
+* [[`8c7f4bab2d`](https://github.com/nodejs/node/commit/8c7f4bab2d)] - **doc**: multiple improvements in Stream docs (Alexander Makarenko) [#5009](https://github.com/nodejs/node/pull/5009)
+* [[`ee013715b9`](https://github.com/nodejs/node/commit/ee013715b9)] - **doc**: improve styling consistency in VM docs (Alexander Makarenko) [#5005](https://github.com/nodejs/node/pull/5005)
+* [[`9824b0d132`](https://github.com/nodejs/node/commit/9824b0d132)] - **doc**: fix anchor links from stream to http and events (piepmatz) [#5007](https://github.com/nodejs/node/pull/5007)
+* [[`2c85f79569`](https://github.com/nodejs/node/commit/2c85f79569)] - **doc**: minor improvement to HTTPS doc (Alexander Makarenko) [#5002](https://github.com/nodejs/node/pull/5002)
+* [[`9cf1370017`](https://github.com/nodejs/node/commit/9cf1370017)] - **doc**: improve styling consistency in Buffer docs (Alexander Makarenko) [#5001](https://github.com/nodejs/node/pull/5001)
+* [[`2750cb0613`](https://github.com/nodejs/node/commit/2750cb0613)] - **doc**: consistent styling for functions in TLS docs (Alexander Makarenko) [#5000](https://github.com/nodejs/node/pull/5000)
+* [[`4758bf13a5`](https://github.com/nodejs/node/commit/4758bf13a5)] - **doc**: update npm LICENSE using license-builder.sh (Rebecca Turner) [#4958](https://github.com/nodejs/node/pull/4958)
+* [[`3b08b5d22c`](https://github.com/nodejs/node/commit/3b08b5d22c)] - **doc**: fix minor typo in process doc (Prayag Verma) [#5018](https://github.com/nodejs/node/pull/5018)
+* [[`129977c9c7`](https://github.com/nodejs/node/commit/129977c9c7)] - **doc**: fix typo in Readme.md (Prayag Verma) [#5017](https://github.com/nodejs/node/pull/5017)
+* [[`5de3dc557f`](https://github.com/nodejs/node/commit/5de3dc557f)] - **doc**: fix `notDeepEqual` API (Minwoo Jung) [#4971](https://github.com/nodejs/node/pull/4971)
+* [[`d47dadcc1f`](https://github.com/nodejs/node/commit/d47dadcc1f)] - **doc**: make buffer methods styles consistent (Timothy Gu) [#4873](https://github.com/nodejs/node/pull/4873)
+* [[`17888b122c`](https://github.com/nodejs/node/commit/17888b122c)] - **doc**: fix JSON generation for aliased methods (Timothy Gu) [#4871](https://github.com/nodejs/node/pull/4871)
+* [[`396e4b9199`](https://github.com/nodejs/node/commit/396e4b9199)] - **doc**: add more details to process.env (Evan Lucas) [#4924](https://github.com/nodejs/node/pull/4924)
+* [[`bc11bf4659`](https://github.com/nodejs/node/commit/bc11bf4659)] - **doc**: don't use "interface" as a variable name (ChALkeR) [#4900](https://github.com/nodejs/node/pull/4900)
+* [[`bcf55d2f44`](https://github.com/nodejs/node/commit/bcf55d2f44)] - **doc**: spell writable consistently (Peter Lyons) [#4954](https://github.com/nodejs/node/pull/4954)
+* [[`4a6d0ac436`](https://github.com/nodejs/node/commit/4a6d0ac436)] - **doc**: update eol handling in readline (Kári Tristan Helgason) [#4927](https://github.com/nodejs/node/pull/4927)
+* [[`e65d3638c0`](https://github.com/nodejs/node/commit/e65d3638c0)] - **doc**: replace function expressions with arrows (Benjamin Gruenbaum) [#4832](https://github.com/nodejs/node/pull/4832)
+* [[`423a58d66f`](https://github.com/nodejs/node/commit/423a58d66f)] - **doc**: show links consistently in deprecations (Sakthipriyan Vairamani) [#4907](https://github.com/nodejs/node/pull/4907)
+* [[`fd87659139`](https://github.com/nodejs/node/commit/fd87659139)] - **doc**: add docs working group (Bryan English) [#4244](https://github.com/nodejs/node/pull/4244)
+* [[`19ed619cff`](https://github.com/nodejs/node/commit/19ed619cff)] - **doc**: remove unnecessary bind(this) (Dmitriy Lazarev) [#4797](https://github.com/nodejs/node/pull/4797)
+* [[`5129930786`](https://github.com/nodejs/node/commit/5129930786)] - **doc**: keep the names in sorted order (Sakthipriyan Vairamani) [#4876](https://github.com/nodejs/node/pull/4876)
+* [[`3c46c10d54`](https://github.com/nodejs/node/commit/3c46c10d54)] - **doc**: fix nonsensical grammar in Buffer::write (Jimb Esser) [#4863](https://github.com/nodejs/node/pull/4863)
+* [[`a1af6fc1a7`](https://github.com/nodejs/node/commit/a1af6fc1a7)] - **doc**: add `servername` parameter docs (Alexander Makarenko) [#4729](https://github.com/nodejs/node/pull/4729)
+* [[`f4eeba8467`](https://github.com/nodejs/node/commit/f4eeba8467)] - **doc**: fix code type of markdowns (Jackson Tian) [#4858](https://github.com/nodejs/node/pull/4858)
+* [[`fa1d453359`](https://github.com/nodejs/node/commit/fa1d453359)] - **doc**: check for errors in 'listen' event (Benjamin Gruenbaum) [#4834](https://github.com/nodejs/node/pull/4834)
+* [[`f462320f74`](https://github.com/nodejs/node/commit/f462320f74)] - **doc**: undo move http.IncomingMessage.statusMessage (Jeff Harris) [#4822](https://github.com/nodejs/node/pull/4822)
+* [[`711245e5ac`](https://github.com/nodejs/node/commit/711245e5ac)] - **doc**: style fixes for the TOC (Roman Reiss) [#4748](https://github.com/nodejs/node/pull/4748)
+* [[`611c2f6fdf`](https://github.com/nodejs/node/commit/611c2f6fdf)] - **doc**: proper markdown escaping -> \_\_, \*, \_ (Robert Jefe Lindstaedt) [#4805](https://github.com/nodejs/node/pull/4805)
+* [[`5a860d9cb7`](https://github.com/nodejs/node/commit/5a860d9cb7)] - **doc**: Examples work when data exceeds buffer size (Glen Arrowsmith) [#4811](https://github.com/nodejs/node/pull/4811)
+* [[`71ba14de86`](https://github.com/nodejs/node/commit/71ba14de86)] - **doc**: update list of personal traits in CoC (Kat Marchán) [#4801](https://github.com/nodejs/node/pull/4801)
+* [[`97eedfc57a`](https://github.com/nodejs/node/commit/97eedfc57a)] - **doc**: harmonize $ node command line notation (Robert Jefe Lindstaedt) [#4806](https://github.com/nodejs/node/pull/4806)
+* [[`2dde0f08c9`](https://github.com/nodejs/node/commit/2dde0f08c9)] - **doc**: add buf.indexOf encoding param with example (Karl Skomski) [#3373](https://github.com/nodejs/node/pull/3373)
+* [[`66c74548de`](https://github.com/nodejs/node/commit/66c74548de)] - **doc**: fenced all code blocks, typo fixes (Robert Jefe Lindstaedt) [#4733](https://github.com/nodejs/node/pull/4733)
+* [[`54e8845b5e`](https://github.com/nodejs/node/commit/54e8845b5e)] - **fs**: refactor redeclared variables (Rich Trott) [#4959](https://github.com/nodejs/node/pull/4959)
+* [[`fa940cf9bc`](https://github.com/nodejs/node/commit/fa940cf9bc)] - **fs**: remove unused branches (Benjamin Gruenbaum) [#4795](https://github.com/nodejs/node/pull/4795)
+* [[`a3b84a4c93`](https://github.com/nodejs/node/commit/a3b84a4c93)] - **(SEMVER-MINOR)** **http**: strictly forbid invalid characters from headers (James M Snell)
+* [[`9b03af254a`](https://github.com/nodejs/node/commit/9b03af254a)] - **http**: remove reference to onParserExecute (Tom Atkinson) [#4773](https://github.com/nodejs/node/pull/4773)
+* [[`101de9de3f`](https://github.com/nodejs/node/commit/101de9de3f)] - **https**: evict cached sessions on error (Fedor Indutny) [#4982](https://github.com/nodejs/node/pull/4982)
+* [[`b2c8b7f6d3`](https://github.com/nodejs/node/commit/b2c8b7f6d3)] - **internal/child_process**: call postSend on error (Fedor Indutny) [#4752](https://github.com/nodejs/node/pull/4752)
+* [[`55030922e5`](https://github.com/nodejs/node/commit/55030922e5)] - **lib**: scope loop variables (Rich Trott) [#4965](https://github.com/nodejs/node/pull/4965)
+* [[`725ad5b1ce`](https://github.com/nodejs/node/commit/725ad5b1ce)] - **lib**: remove string_decoder.js var redeclarations (Rich Trott) [#4978](https://github.com/nodejs/node/pull/4978)
+* [[`c09eb44a59`](https://github.com/nodejs/node/commit/c09eb44a59)] - **module**: refactor redeclared variable (Rich Trott) [#4962](https://github.com/nodejs/node/pull/4962)
+* [[`612ce66c78`](https://github.com/nodejs/node/commit/612ce66c78)] - **net**: refactor redeclared variables (Rich Trott) [#4963](https://github.com/nodejs/node/pull/4963)
+* [[`c9b05dafe0`](https://github.com/nodejs/node/commit/c9b05dafe0)] - **net**: move isLegalPort to internal/net (Evan Lucas) [#4882](https://github.com/nodejs/node/pull/4882)
+* [[`7003a4e3d8`](https://github.com/nodejs/node/commit/7003a4e3d8)] - **node_contextify**: do not incept debug context (Myles Borins) [#4815](https://github.com/nodejs/node/issues/4815)
+* [[`5a77c095a6`](https://github.com/nodejs/node/commit/5a77c095a6)] - **process**: support symbol events (cjihrig) [#4798](https://github.com/nodejs/node/pull/4798)
+* [[`85743c0e92`](https://github.com/nodejs/node/commit/85743c0e92)] - **querystring**: check that maxKeys is finite (Myles Borins) [#5066](https://github.com/nodejs/node/pull/5066)
+* [[`5a10fe932c`](https://github.com/nodejs/node/commit/5a10fe932c)] - **querystring**: use String.prototype.split's limit (Manuel Valls) [#2288](https://github.com/nodejs/node/pull/2288)
+* [[`2844cc03dc`](https://github.com/nodejs/node/commit/2844cc03dc)] - **repl**: remove variable redeclaration (Rich Trott) [#4977](https://github.com/nodejs/node/pull/4977)
+* [[`ac6627a0fe`](https://github.com/nodejs/node/commit/ac6627a0fe)] - **src**: avoid compiler warning in node_revert.cc (James M Snell)
+* [[`459c5844c8`](https://github.com/nodejs/node/commit/459c5844c8)] - **(SEMVER-MINOR)** **src**: add --security-revert command line flag (James M Snell)
+* [[`95615196de`](https://github.com/nodejs/node/commit/95615196de)] - **src**: clean up usage of __proto__ (Jackson Tian) [#5069](https://github.com/nodejs/node/pull/5069)
+* [[`e93b024214`](https://github.com/nodejs/node/commit/e93b024214)] - **src**: remove no longer relevant comments (Chris911) [#4843](https://github.com/nodejs/node/pull/4843)
+* [[`a2c257a3ef`](https://github.com/nodejs/node/commit/a2c257a3ef)] - **src**: fix negative values in process.hrtime() (Ben Noordhuis) [#4757](https://github.com/nodejs/node/pull/4757)
+* [[`b46f3b84d4`](https://github.com/nodejs/node/commit/b46f3b84d4)] - **src,deps**: replace LoadLibrary by LoadLibraryW (Cheng Zhao) [iojs/io.js#226](https://github.com/iojs/io.js/pull/226)
+* [[`ee8d4bb075`](https://github.com/nodejs/node/commit/ee8d4bb075)] - **stream**: prevent object map change in TransformState (Evan Lucas) [#5032](https://github.com/nodejs/node/pull/5032)
+* [[`c8b6de244e`](https://github.com/nodejs/node/commit/c8b6de244e)] - **stream**: refactor redeclared variables (Rich Trott) [#4816](https://github.com/nodejs/node/pull/4816)
+* [[`9dcc45e9c5`](https://github.com/nodejs/node/commit/9dcc45e9c5)] - **test**: enable to work pkcs12 test in FIPS mode (Shigeki Ohtsu) [#5150](https://github.com/nodejs/node/pull/5150)
+* [[`e4390664ae`](https://github.com/nodejs/node/commit/e4390664ae)] - **test**: disable gh-5100 test when in FIPS mode (Fedor Indutny) [#5144](https://github.com/nodejs/node/pull/5144)
+* [[`cf3aa911ec`](https://github.com/nodejs/node/commit/cf3aa911ec)] - **test**: fix flaky test-dgram-pingpong (Rich Trott) [#5125](https://github.com/nodejs/node/pull/5125)
+* [[`63884f57dd`](https://github.com/nodejs/node/commit/63884f57dd)] - **test**: mark flaky tests on Raspberry Pi (Rich Trott) [#5082](https://github.com/nodejs/node/pull/5082)
+* [[`09917c99d8`](https://github.com/nodejs/node/commit/09917c99d8)] - **test**: fix `net-socket-timeout-unref` flakiness (Santiago Gimeno) [#4772](https://github.com/nodejs/node/pull/4772)
+* [[`83da19aa48`](https://github.com/nodejs/node/commit/83da19aa48)] - **test**: fix redeclared test-event-emitter-* vars (Rich Trott) [#4985](https://github.com/nodejs/node/pull/4985)
+* [[`87b27c913d`](https://github.com/nodejs/node/commit/87b27c913d)] - **test**: fix redeclared test-intl var (Rich Trott) [#4988](https://github.com/nodejs/node/pull/4988)
+* [[`e98772d68e`](https://github.com/nodejs/node/commit/e98772d68e)] - **test**: remove redeclared var in test-domain (Rich Trott) [#4984](https://github.com/nodejs/node/pull/4984)
+* [[`443d0463ca`](https://github.com/nodejs/node/commit/443d0463ca)] - **test**: add common.platformTimeout() to dgram test (Rich Trott) [#4938](https://github.com/nodejs/node/pull/4938)
+* [[`90219c3398`](https://github.com/nodejs/node/commit/90219c3398)] - **test**: fix flaky cluster test on Windows 10 (Rich Trott) [#4934](https://github.com/nodejs/node/pull/4934)
+* [[`3488fa81b5`](https://github.com/nodejs/node/commit/3488fa81b5)] - **test**: fix variable redeclarations (Rich Trott) [#4992](https://github.com/nodejs/node/pull/4992)
+* [[`7dc0905d4d`](https://github.com/nodejs/node/commit/7dc0905d4d)] - **test**: fix redeclared test-util-* vars (Rich Trott) [#4994](https://github.com/nodejs/node/pull/4994)
+* [[`53e7d605c9`](https://github.com/nodejs/node/commit/53e7d605c9)] - **test**: fix redeclared vars in sequential tests (Rich Trott) [#4999](https://github.com/nodejs/node/pull/4999)
+* [[`a62ace9f7e`](https://github.com/nodejs/node/commit/a62ace9f7e)] - **test**: fix tls-no-rsa-key flakiness (Santiago Gimeno) [#4043](https://github.com/nodejs/node/pull/4043)
+* [[`9b8f025816`](https://github.com/nodejs/node/commit/9b8f025816)] - **test**: fix redeclared vars in test-url (Rich Trott) [#4993](https://github.com/nodejs/node/pull/4993)
+* [[`51fb8845d5`](https://github.com/nodejs/node/commit/51fb8845d5)] - **test**: fix redeclared test-path vars (Rich Trott) [#4991](https://github.com/nodejs/node/pull/4991)
+* [[`b16b360ae8`](https://github.com/nodejs/node/commit/b16b360ae8)] - **test**: fix var redeclarations in test-os (Rich Trott) [#4990](https://github.com/nodejs/node/pull/4990)
+* [[`d6199773e8`](https://github.com/nodejs/node/commit/d6199773e8)] - **test**: fix test-net-* variable redeclarations (Rich Trott) [#4989](https://github.com/nodejs/node/pull/4989)
+* [[`9dd5b3e01b`](https://github.com/nodejs/node/commit/9dd5b3e01b)] - **test**: fix redeclared test-http-* vars (Rich Trott) [#4987](https://github.com/nodejs/node/pull/4987)
+* [[`835bf13c1d`](https://github.com/nodejs/node/commit/835bf13c1d)] - **test**: fix var redeclarations in test-fs-* (Rich Trott) [#4986](https://github.com/nodejs/node/pull/4986)
+* [[`71d7a4457d`](https://github.com/nodejs/node/commit/71d7a4457d)] - **test**: fix redeclared vars in test-vm-* (Rich Trott) [#4997](https://github.com/nodejs/node/pull/4997)
+* [[`38459402a5`](https://github.com/nodejs/node/commit/38459402a5)] - **test**: fix inconsistent styling in test-url (Brian White) [#5014](https://github.com/nodejs/node/pull/5014)
+* [[`4934798c0d`](https://github.com/nodejs/node/commit/4934798c0d)] - **test**: pummel test fixes (Rich Trott) [#4998](https://github.com/nodejs/node/pull/4998)
+* [[`3970504298`](https://github.com/nodejs/node/commit/3970504298)] - **test**: remove var redeclarations in test-crypto-* (Rich Trott) [#4981](https://github.com/nodejs/node/pull/4981)
+* [[`a2881e2187`](https://github.com/nodejs/node/commit/a2881e2187)] - **test**: remove test-cluster-* var redeclarations (Rich Trott) [#4980](https://github.com/nodejs/node/pull/4980)
+* [[`c3d93299c2`](https://github.com/nodejs/node/commit/c3d93299c2)] - **test**: fix test-http-extra-response flakiness (Santiago Gimeno) [#4979](https://github.com/nodejs/node/pull/4979)
+* [[`0384a43885`](https://github.com/nodejs/node/commit/0384a43885)] - **test**: Add assertion for TLS peer certificate fingerprint (Alan Cohen) [#4923](https://github.com/nodejs/node/pull/4923)
+* [[`48a353fe41`](https://github.com/nodejs/node/commit/48a353fe41)] - **test**: scope redeclared vars in test-child-process* (Rich Trott) [#4944](https://github.com/nodejs/node/pull/4944)
+* [[`89d1149467`](https://github.com/nodejs/node/commit/89d1149467)] - **test**: fix test-tls-zero-clear-in flakiness (Santiago Gimeno) [#4888](https://github.com/nodejs/node/pull/4888)
+* [[`f7ed47341a`](https://github.com/nodejs/node/commit/f7ed47341a)] - **test**: remove Object.observe from tests (Vladimir Kurchatkin) [#4769](https://github.com/nodejs/node/pull/4769)
+* [[`d95e53dc3b`](https://github.com/nodejs/node/commit/d95e53dc3b)] - **test**: refactor switch (Rich Trott) [#4870](https://github.com/nodejs/node/pull/4870)
+* [[`7f1e3e929a`](https://github.com/nodejs/node/commit/7f1e3e929a)] - **test**: remove race condition in http flood test (Rich Trott) [#4793](https://github.com/nodejs/node/pull/4793)
+* [[`6539c64e67`](https://github.com/nodejs/node/commit/6539c64e67)] - **test**: scope redeclared variable (Rich Trott) [#4854](https://github.com/nodejs/node/pull/4854)
+* [[`62fb941557`](https://github.com/nodejs/node/commit/62fb941557)] - **test**: fix irregular whitespace issue (Roman Reiss) [#4864](https://github.com/nodejs/node/pull/4864)
+* [[`3b225209f0`](https://github.com/nodejs/node/commit/3b225209f0)] - **test**: fs.link() test runs on same device (Drew Folta) [#4861](https://github.com/nodejs/node/pull/4861)
+* [[`1860eae110`](https://github.com/nodejs/node/commit/1860eae110)] - **test**: refactor test-net-settimeout (Rich Trott) [#4799](https://github.com/nodejs/node/pull/4799)
+* [[`ae9a8cd053`](https://github.com/nodejs/node/commit/ae9a8cd053)] - **test**: mark test-tick-processor flaky (Rich Trott) [#4809](https://github.com/nodejs/node/pull/4809)
+* [[`57cea9e421`](https://github.com/nodejs/node/commit/57cea9e421)] - **test**: remove test-http-exit-delay (Rich Trott) [#4786](https://github.com/nodejs/node/pull/4786)
+* [[`2119c76d5a`](https://github.com/nodejs/node/commit/2119c76d5a)] - **test**: refactor test-fs-watch (Rich Trott) [#4776](https://github.com/nodejs/node/pull/4776)
+* [[`e487b72459`](https://github.com/nodejs/node/commit/e487b72459)] - **test**: move cluster tests to parallel (Rich Trott) [#4774](https://github.com/nodejs/node/pull/4774)
+* [[`8c694a658c`](https://github.com/nodejs/node/commit/8c694a658c)] - **test**: improve test-cluster-disconnect-suicide-race (Rich Trott) [#4739](https://github.com/nodejs/node/pull/4739)
+* [[`14f5bb7a99`](https://github.com/nodejs/node/commit/14f5bb7a99)] - **test,buffer**: refactor redeclarations (Rich Trott) [#4893](https://github.com/nodejs/node/pull/4893)
+* [[`62479e3406`](https://github.com/nodejs/node/commit/62479e3406)] - **tls**: scope loop vars with let (Rich Trott) [#4853](https://github.com/nodejs/node/pull/4853)
+* [[`d6fbd81a7a`](https://github.com/nodejs/node/commit/d6fbd81a7a)] - **tls_wrap**: reach error reporting for UV_EPROTO (Fedor Indutny) [#4885](https://github.com/nodejs/node/pull/4885)
+* [[`f75d06bf10`](https://github.com/nodejs/node/commit/f75d06bf10)] - **tools**: lint for empty character classes in regex (Rich Trott) [#5115](https://github.com/nodejs/node/pull/5115)
+* [[`53cbd0564f`](https://github.com/nodejs/node/commit/53cbd0564f)] - **tools**: lint for spacing around unary operators (Rich Trott) [#5063](https://github.com/nodejs/node/pull/5063)
+* [[`7fa5959c59`](https://github.com/nodejs/node/commit/7fa5959c59)] - **tools**: fix redeclared vars in doc/json.js (Rich Trott) [#5047](https://github.com/nodejs/node/pull/5047)
+* [[`e95fd6ae70`](https://github.com/nodejs/node/commit/e95fd6ae70)] - **tools**: apply linting to doc tools (Rich Trott) [#4973](https://github.com/nodejs/node/pull/4973)
+* [[`777ed82162`](https://github.com/nodejs/node/commit/777ed82162)] - **tools**: fix detecting constructor for JSON doc (Timothy Gu) [#4966](https://github.com/nodejs/node/pull/4966)
+* [[`5d55f59c85`](https://github.com/nodejs/node/commit/5d55f59c85)] - **tools**: add property types in JSON documentation (Timothy Gu) [#4884](https://github.com/nodejs/node/pull/4884)
+* [[`fd5c56698e`](https://github.com/nodejs/node/commit/fd5c56698e)] - **tools**: add support for subkeys in release tools (Myles Borins) [#4807](https://github.com/nodejs/node/pull/4807)
+* [[`34df6a5c0c`](https://github.com/nodejs/node/commit/34df6a5c0c)] - **tools**: enable assorted ESLint error rules (Roman Reiss) [#4864](https://github.com/nodejs/node/pull/4864)
+* [[`386ad7e0b5`](https://github.com/nodejs/node/commit/386ad7e0b5)] - **tools**: fix setting path containing an ampersand (Brian White) [#4804](https://github.com/nodejs/node/pull/4804)
+* [[`e415eb27e5`](https://github.com/nodejs/node/commit/e415eb27e5)] - **url**: change scoping of variables with let (Kári Tristan Helgason) [#4867](https://github.com/nodejs/node/pull/4867)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.6.0/node-v5.6.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.6.0/node-v5.6.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.6.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.6.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.6.0/node-v5.6.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-x86.tar.gz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-x64.tar.gz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-sunos-x86.tar.gz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-sunos-x64.tar.gz<br>
+ARMv6 32-bit Binary: *Coming soon*<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-armv7l.tar.gz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-arm64.tar.gz<br>
+Source Code: https://nodejs.org/dist/v5.6.0/node-v5.6.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.6.0/<br>
+Documentation: https://nodejs.org/docs/v5.6.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+1ef8f5b627cf980b0d242d5b70be3c6fbefc8e61ecfcaf97930965d68c927bd9  node-v5.6.0-darwin-x64.tar.gz
+c4c263d84de3d7c2b990f97a5fbc3db50519fd67ed34e75388db7fdb2d2c8bf0  node-v5.6.0-darwin-x64.tar.xz
+3eb317571329d1ff345aba83e94d0fd6bf2043697d032fdcffb92265e11b61be  node-v5.6.0-headers.tar.gz
+5e44ce115da250b157841f2655eb399423a99d9f80ac21bf374c3ad0e315d998  node-v5.6.0-headers.tar.xz
+3b22bb5e1579d6e45f31da88c17baeb17a12ecb297c1c69447de6030d626b08d  node-v5.6.0-linux-arm64.tar.gz
+a956f0204bbbb87f0403026c7a6a588c62d9a8f057ccdceaedb8e73df05f4996  node-v5.6.0-linux-arm64.tar.xz
+7e258c59576beddd475fc33a8e57b153f0455cf1a5d801aedc6cee17137e9bae  node-v5.6.0-linux-armv7l.tar.gz
+f44c5b3ae7f78cb4910d238a88c4d97281a87f0848324668162fd90383f73475  node-v5.6.0-linux-armv7l.tar.xz
+6b10e446b5a1227673b87d840e9a500f5d2dbd2b806d96e2d81d634c3381a5f1  node-v5.6.0-linux-x64.tar.gz
+d72e4e264c4a9da6a4fe631f376e84d5a9c1fd0a2eea7514f3e4c1736915b394  node-v5.6.0-linux-x64.tar.xz
+f6fc3391f48a3fc2d077dc0e1673fc3934eb2b9465cbeab334e3967d1503ba49  node-v5.6.0-linux-x86.tar.gz
+a22fe4ab92958e40fda35ec2bc3a0a10b2c56e1ccbc1a0dea8b642e39725fb71  node-v5.6.0-linux-x86.tar.xz
+4cd99f324db690c17b6ba9705db6c1cc172d3d210d003c64c09b1ed60a6ccaf0  node-v5.6.0.pkg
+a7010c2f7ddc5f6fff7f4d04e1f0973edd387ebba891c8905323daf2ba499a4c  node-v5.6.0-sunos-x64.tar.gz
+2b0d631e03f2b5968011dbbc8ff2eef094d580cb774a4c44dcda726568f80fa0  node-v5.6.0-sunos-x64.tar.xz
+30ca440291a06e6f7af77ba072dbe4ce771e80dcd6ce4366ff1c6fa18df45f75  node-v5.6.0-sunos-x86.tar.gz
+7dae04996ce9ea4f16a3dd51a155d98497863153bcdb3cdabb57647387e0efb4  node-v5.6.0-sunos-x86.tar.xz
+3af2cc5e5970afc83e59f2065fea2e2df846a544a100cd3c0527f0db05bec27f  node-v5.6.0.tar.gz
+588341e466ac72f6b8e9fa500f04edf149f7d4e8141c4175c495d6d1484405e3  node-v5.6.0.tar.xz
+dd4734d61ed2da37c114cdecfee298a6dc3cffc2c3a7c7998a74ea1428a4f667  node-v5.6.0-x64.msi
+13f816a2b53a337721414577881a0786240ff53e26d687a4dbde17fbce9e1b15  node-v5.6.0-x86.msi
+692cabe22e81a153fcabada86d69e96af002b908c54a600466fa59c701e52a5a  win-x64/node.exe
+a6c1ae1c8a907ede15c997d0a056247680227cd4328251e840faec15b9eb34bf  win-x64/node.lib
+c78efdd5decb224d39cfcf84819ca7a301da3bf2fc07d32cb31d47e763a0c75c  win-x86/node.exe
+1957ce7915ec342645420373b0a0581b28fa7659b59c7e92a1c84928f354aa22  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEcBAEBCgAGBQJWuhwcAAoJEHNBsVwHCHescgwIAIAh5QLINVL1xfrWdtDZDFar
+kbO61ecgtaw8fB+bdPfSjHARzXFWn5rzlDMXM5Sv8rQOf/Ts+FczEdWhijuO7HYr
+kQEZ2AyKxkhM/o6mUQ1QGF9MkjfGrqfP/a1MmBfVQCKHdy0JnkZaXKx02ou9duWQ
+NpxvKt4CugnPMYngT/zmwZl78f1Gfp5yYB2DyxKdgKLjIaTeQXE15fnUExPZ7hTa
+iCYFgEvRgocvwbHBnHg2XdRyY6XX2IIjx9OnhTATCSXQEcqKN4TLB8X95387iiTe
+UHtTVDJIsbRpqOWM1iRB/kHkQwWMREAx8rBI4PihoRTYBmP5UBvVWZ8Df7R2s2Q=
+=8MEQ
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.7.0.md b/locale/uk/blog/release/v5.7.0.md
new file mode 100755
index 0000000000000..13c106b46d5fa
--- /dev/null
+++ b/locale/uk/blog/release/v5.7.0.md
@@ -0,0 +1,210 @@
+---
+date: 2016-02-23T05:37:34.766Z
+version: 5.7.0
+category: release
+title: Node v5.7.0 (Current)
+slug: node-v5-7-0
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes
+
+* **buffer**:
+  - You can now supply an `encoding` argument when filling a Buffer `Buffer#fill(string[, start[, end]][, encoding])`, supplying an existing Buffer will also work with `Buffer#fill(buffer[, start[, end]])`. See the [API documentation](https://nodejs.org/api/buffer.html#buffer_buf_fill_value_offset_end_encoding) for details on how this works. (Trevor Norris) [#4935](https://github.com/nodejs/node/pull/4935)
+  - `Buffer#indexOf()` no longer requires a `byteOffset` argument if you also wish to specify an `encoding`: `Buffer#indexOf(val[, byteOffset][, encoding])`. (Trevor Norris) [#4803](https://github.com/nodejs/node/pull/4803)
+* **child_process**: `spawn()` and `spawnSync()` now support a `'shell'` option to allow for optional execution of the given command inside a shell. If set to `true`, `cmd.exe` will be used on Windows and `/bin/sh` elsewhere. A path to a custom shell can also be passed to override these defaults. On Windows, this option allows `.bat.` and `.cmd` files to be executed with `spawn()` and `spawnSync()`. (Colin Ihrig) [#4598](https://github.com/nodejs/node/pull/4598)
+* **http_parser**: Update to http-parser 2.6.2 to fix an unintentionally strict limitation of allowable header characters (James M Snell) [#5237](https://github.com/nodejs/node/pull/5237)
+* **dgram**: `socket.send()` now supports accepts an array of Buffers or Strings as the first argument. See the [API docs](https://nodejs.org/download/nightly/v6.0.0-nightly201602102848f84332/docs/api/dgram.html#dgram_socket_send_msg_offset_length_port_address_callback) for details on how this works. (Matteo Collina) [#4374](https://github.com/nodejs/node/pull/4374)
+* **http**: Fix a bug where handling headers will mistakenly trigger an `'upgrade'` event where the server is just advertising its protocols. This bug can prevent HTTP clients from communicating with HTTP/2 enabled servers. (Fedor Indutny) [#4337](https://github.com/nodejs/node/pull/4337)
+* **net**: Added a `listening` Boolean property to `net` and `http` servers to indicate whether the server is listening for connections. (José Moreira) [#4743](https://github.com/nodejs/node/pull/4743)
+* **node**: The C++ `node::MakeCallback()` API is now reentrant and calling it from inside another `MakeCallback()` call no longer causes the `nextTick` queue or Promises microtask queue to be processed out of order. (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* **tls**: Add a new `tlsSocket.getProtocol()` method to get the negotiated TLS protocol version of the current connection. (Brian White) [#4995](https://github.com/nodejs/node/pull/4995)
+* **vm**: Introduce new `'produceCachedData'` and `'cachedData'` options to `new vm.Script()` to interact with V8's code cache. When a new `vm.Script` object is created with the `'produceCachedData'` set to `true` a `Buffer` with V8's code cache data will be produced and stored in `cachedData` property of the returned object. This data in turn may be supplied back to another `vm.Script()` object with a `'cachedData'` option if the supplied source is the same. Successfully executing a script from cached data can speed up instantiation time. See the [API docs](https://nodejs.org/api/vm.html#vm_new_vm_script_code_options) for details. (Fedor Indutny) [#4777](https://github.com/nodejs/node/pull/4777)
+* **performance**: Improvements in:
+  - `process.nextTick()` (Ruben Bridgewater) [#5092](https://github.com/nodejs/node/pull/5092)
+  - `path` module (Brian White) [#5123](https://github.com/nodejs/node/pull/5123)
+  - `querystring` module (Brian White) [#5012](https://github.com/nodejs/node/pull/5012)
+  - `streams` module when processing small chunks (Matteo Collina) [#4354](https://github.com/nodejs/node/pull/4354)
+
+### Commits
+
+* [[`3a96fa0030`](https://github.com/nodejs/node/commit/3a96fa0030)] - **async_wrap**: add parent uid to init hook (Andreas Madsen) [#4600](https://github.com/nodejs/node/pull/4600)
+* [[`4ef04c7c4c`](https://github.com/nodejs/node/commit/4ef04c7c4c)] - **async_wrap**: make uid the first argument in init (Andreas Madsen) [#4600](https://github.com/nodejs/node/pull/4600)
+* [[`4afe801f90`](https://github.com/nodejs/node/commit/4afe801f90)] - **async_wrap**: add uid to all asyncWrap hooks (Andreas Madsen) [#4600](https://github.com/nodejs/node/pull/4600)
+* [[`edf8f8a7da`](https://github.com/nodejs/node/commit/edf8f8a7da)] - **benchmark**: split path benchmarks (Brian White) [#5123](https://github.com/nodejs/node/pull/5123)
+* [[`8d713d8d51`](https://github.com/nodejs/node/commit/8d713d8d51)] - **benchmark**: allow empty parameters (Brian White) [#5123](https://github.com/nodejs/node/pull/5123)
+* [[`eb6d07327a`](https://github.com/nodejs/node/commit/eb6d07327a)] - **(SEMVER-MINOR)** **buffer**: add encoding parameter to fill() (Trevor Norris) [#4935](https://github.com/nodejs/node/pull/4935)
+* [[`60d2048b6c`](https://github.com/nodejs/node/commit/60d2048b6c)] - **(SEMVER-MINOR)** **buffer**: properly retrieve binary length of needle (Trevor Norris) [#4803](https://github.com/nodejs/node/pull/4803)
+* [[`4c67d74607`](https://github.com/nodejs/node/commit/4c67d74607)] - **(SEMVER-MINOR)** **buffer**: allow encoding param to collapse (Trevor Norris) [#4803](https://github.com/nodejs/node/pull/4803)
+* [[`5fa4117bfc`](https://github.com/nodejs/node/commit/5fa4117bfc)] - **build**: add a help message and removed a TODO. (Ojas Shirekar) [#5080](https://github.com/nodejs/node/pull/5080)
+* [[`09bfb865af`](https://github.com/nodejs/node/commit/09bfb865af)] - **build**: remove redundant TODO in configure (Ojas Shirekar) [#5080](https://github.com/nodejs/node/pull/5080)
+* [[`3dfc11c516`](https://github.com/nodejs/node/commit/3dfc11c516)] - **build**: remove Makefile.build (Ojas Shirekar) [#5080](https://github.com/nodejs/node/pull/5080)
+* [[`fc78d3d6a7`](https://github.com/nodejs/node/commit/fc78d3d6a7)] - **build**: skip msi build if WiX is not found (Tsarevich Dmitry) [#5220](https://github.com/nodejs/node/pull/5220)
+* [[`356acb39d7`](https://github.com/nodejs/node/commit/356acb39d7)] - **build**: treat aarch64 as arm64 (Johan Bergström) [#5191](https://github.com/nodejs/node/pull/5191)
+* [[`3b83d42b4a`](https://github.com/nodejs/node/commit/3b83d42b4a)] - **build**: fix build when python path contains spaces (Felix Becker) [#4841](https://github.com/nodejs/node/pull/4841)
+* [[`9e6ad2d8ff`](https://github.com/nodejs/node/commit/9e6ad2d8ff)] - **child_process**: fix data loss with readable event (Brian White) [#5036](https://github.com/nodejs/node/pull/5036)
+* [[`ecc797600f`](https://github.com/nodejs/node/commit/ecc797600f)] - **(SEMVER-MINOR)** **child_process**: add shell option to spawn() (cjihrig) [#4598](https://github.com/nodejs/node/pull/4598)
+* [[`efd6f68dce`](https://github.com/nodejs/node/commit/efd6f68dce)] - **cluster**: dont rely on `this` in `fork` (Igor Klopov) [#5216](https://github.com/nodejs/node/pull/5216)
+* [[`df93d60caf`](https://github.com/nodejs/node/commit/df93d60caf)] - **console**: apply null as `this` for util.format (Jackson Tian) [#5222](https://github.com/nodejs/node/pull/5222)
+* [[`c397ba8fa3`](https://github.com/nodejs/node/commit/c397ba8fa3)] - **contextify**: use offset/length from Uint8Array (Fedor Indutny) [#4947](https://github.com/nodejs/node/pull/4947)
+* [[`3048ac0b57`](https://github.com/nodejs/node/commit/3048ac0b57)] - **crypto**: have fixed NodeBIOs return EOF (Adam Langley) [#5105](https://github.com/nodejs/node/pull/5105)
+* [[`af074846f5`](https://github.com/nodejs/node/commit/af074846f5)] - **debugger**: remove unneeded callback check (Rich Trott) [#5319](https://github.com/nodejs/node/pull/5319)
+* [[`7bac743f36`](https://github.com/nodejs/node/commit/7bac743f36)] - **debugger**: assert test before accessing this.binding (Prince J Wesley) [#5145](https://github.com/nodejs/node/pull/5145)
+* [[`18c94e5a8d`](https://github.com/nodejs/node/commit/18c94e5a8d)] - **deps**: remove unnecessary files (Brian White) [#5212](https://github.com/nodejs/node/pull/5212)
+* [[`967cf97bf0`](https://github.com/nodejs/node/commit/967cf97bf0)] - **deps**: cherry-pick 2e4da65 from v8's 4.8 upstream (Michael Dawson) [#5293](https://github.com/nodejs/node/pull/5293)
+* [[`bbdf2684d5`](https://github.com/nodejs/node/commit/bbdf2684d5)] - **deps**: update to http-parser 2.6.2 (James M Snell) [#5237](https://github.com/nodejs/node/pull/5237)
+* [[`127dd6275a`](https://github.com/nodejs/node/commit/127dd6275a)] - ***Revert*** "**deps**: sync with upstream c-ares/c-ares@4ef6817" (Ben Noordhuis) [#5199](https://github.com/nodejs/node/pull/5199)
+* [[`35c3832994`](https://github.com/nodejs/node/commit/35c3832994)] - **deps**: sync with upstream c-ares/c-ares@4ef6817 (Fedor Indutny) [#5199](https://github.com/nodejs/node/pull/5199)
+* [[`b4db31822f`](https://github.com/nodejs/node/commit/b4db31822f)] - **dgram**: scope redeclared variables (Rich Trott) [#4940](https://github.com/nodejs/node/pull/4940)
+* [[`368c1d1098`](https://github.com/nodejs/node/commit/368c1d1098)] - **(SEMVER-MINOR)** **dgram**: support dgram.send with multiple buffers (Matteo Collina) [#4374](https://github.com/nodejs/node/pull/4374)
+* [[`a8862f59eb`](https://github.com/nodejs/node/commit/a8862f59eb)] - **doc**: update repo docs to use 'CTC' (Alexis Campailla) [#5304](https://github.com/nodejs/node/pull/5304)
+* [[`6cf8ec5bd1`](https://github.com/nodejs/node/commit/6cf8ec5bd1)] - **doc**: s/http/https in Myles Borins' GitHub link (Rod Vagg) [#5356](https://github.com/nodejs/node/pull/5356)
+* [[`0389e3803c`](https://github.com/nodejs/node/commit/0389e3803c)] - **doc**: clarify child_process.execFile{,Sync} file arg (Kevin Locke) [#5310](https://github.com/nodejs/node/pull/5310)
+* [[`c48290d9b7`](https://github.com/nodejs/node/commit/c48290d9b7)] - **doc**: fix buf.length slice example (Chinedu Francis Nwafili) [#5259](https://github.com/nodejs/node/pull/5259)
+* [[`a6e437c619`](https://github.com/nodejs/node/commit/a6e437c619)] - **doc**: fix buffer\[index\] example (Chinedu Francis Nwafili) [#5253](https://github.com/nodejs/node/pull/5253)
+* [[`73ef1bd423`](https://github.com/nodejs/node/commit/73ef1bd423)] - **doc**: fix template string (Rafael Cepeda) [#5240](https://github.com/nodejs/node/pull/5240)
+* [[`fa04daa384`](https://github.com/nodejs/node/commit/fa04daa384)] - **doc**: clarify exceptions during uncaughtException (Noah Rose) [#5180](https://github.com/nodejs/node/pull/5180)
+* [[`22f132e61d`](https://github.com/nodejs/node/commit/22f132e61d)] - **doc**: improvements to console.markdown copy (Alexander Makarenko) [#5225](https://github.com/nodejs/node/pull/5225)
+* [[`48fa6f6063`](https://github.com/nodejs/node/commit/48fa6f6063)] - **doc**: update process.send() signature (cjihrig) [#5284](https://github.com/nodejs/node/pull/5284)
+* [[`35d89d4662`](https://github.com/nodejs/node/commit/35d89d4662)] - **doc**: fix net.createConnection() example (Brian White) [#5219](https://github.com/nodejs/node/pull/5219)
+* [[`149007c9f0`](https://github.com/nodejs/node/commit/149007c9f0)] - **doc**: replace node-forward link in CONTRIBUTING.md (Ben Noordhuis) [#5227](https://github.com/nodejs/node/pull/5227)
+* [[`a6aaf2caab`](https://github.com/nodejs/node/commit/a6aaf2caab)] - **doc**: improve scrolling, various CSS tweaks (Roman Reiss) [#5198](https://github.com/nodejs/node/pull/5198)
+* [[`18b00deeac`](https://github.com/nodejs/node/commit/18b00deeac)] - **doc**: update DCO to v1.1 (Mikeal Rogers) [#5170](https://github.com/nodejs/node/pull/5170)
+* [[`3955bc4cd0`](https://github.com/nodejs/node/commit/3955bc4cd0)] - **doc**: fix minor inconsistencies in repl doc (Rich Trott) [#5193](https://github.com/nodejs/node/pull/5193)
+* [[`287bce7b48`](https://github.com/nodejs/node/commit/287bce7b48)] - **doc**: merging behavior of writeHead vs setHeader (Alejandro Oviedo) [#5081](https://github.com/nodejs/node/pull/5081)
+* [[`529e749d88`](https://github.com/nodejs/node/commit/529e749d88)] - **doc**: fix type references for link gen, link css (Claudio Rodriguez) [#4741](https://github.com/nodejs/node/pull/4741)
+* [[`275f6dbcbb`](https://github.com/nodejs/node/commit/275f6dbcbb)] - **(SEMVER-MINOR)** **doc**: correct tlsSocket.getCipher() description (Brian White) [#4995](https://github.com/nodejs/node/pull/4995)
+* [[`b706b0c2c5`](https://github.com/nodejs/node/commit/b706b0c2c5)] - **http**: remove old, confusing comment (Brian White) [#5233](https://github.com/nodejs/node/pull/5233)
+* [[`ed36235248`](https://github.com/nodejs/node/commit/ed36235248)] - **http**: remove unnecessary check (Brian White) [#5233](https://github.com/nodejs/node/pull/5233)
+* [[`7e82a566b3`](https://github.com/nodejs/node/commit/7e82a566b3)] - **(SEMVER-MINOR)** **http**: allow async createConnection() (Brian White) [#4638](https://github.com/nodejs/node/pull/4638)
+* [[`411d813323`](https://github.com/nodejs/node/commit/411d813323)] - **http**: do not emit `upgrade` on advertisement (Fedor Indutny) [#4337](https://github.com/nodejs/node/pull/4337)
+* [[`bbc786b50f`](https://github.com/nodejs/node/commit/bbc786b50f)] - **http,util**: fix typos in comments (Alexander Makarenko) [#5279](https://github.com/nodejs/node/pull/5279)
+* [[`a2d198c702`](https://github.com/nodejs/node/commit/a2d198c702)] - **net**: use `_server` for internal book-keeping (Fedor Indutny) [#5262](https://github.com/nodejs/node/pull/5262)
+* [[`18d24e60c5`](https://github.com/nodejs/node/commit/18d24e60c5)] - **(SEMVER-MINOR)** **net**: add net.listening boolean property over a getter (José Moreira) [#4743](https://github.com/nodejs/node/pull/4743)
+* [[`9cee86e3e9`](https://github.com/nodejs/node/commit/9cee86e3e9)] - **node**: set process._eventsCount to 0 on startup (Evan Lucas) [#5208](https://github.com/nodejs/node/pull/5208)
+* [[`f2e4f621c5`](https://github.com/nodejs/node/commit/f2e4f621c5)] - **node**: improve process.nextTick performance (Ruben Bridgewater) [#5092](https://github.com/nodejs/node/pull/5092)
+* [[`1c6f927bd1`](https://github.com/nodejs/node/commit/1c6f927bd1)] - **path**: fix input type checking regression (Brian White) [#5244](https://github.com/nodejs/node/pull/5244)
+* [[`4dae8caf7a`](https://github.com/nodejs/node/commit/4dae8caf7a)] - **path**: performance improvements on all platforms (Brian White) [#5123](https://github.com/nodejs/node/pull/5123)
+* [[`46be1f4d0c`](https://github.com/nodejs/node/commit/46be1f4d0c)] - **querystring**: improve escape() performance (Brian White) [#5012](https://github.com/nodejs/node/pull/5012)
+* [[`27e323e8c1`](https://github.com/nodejs/node/commit/27e323e8c1)] - **querystring**: improve unescapeBuffer() performance (Brian White) [#5012](https://github.com/nodejs/node/pull/5012)
+* [[`301023b2b4`](https://github.com/nodejs/node/commit/301023b2b4)] - **querystring**: improve parse() performance (Brian White) [#5012](https://github.com/nodejs/node/pull/5012)
+* [[`98907c716b`](https://github.com/nodejs/node/commit/98907c716b)] - **(SEMVER-MINOR)** **repl**: allow multiline function call (Zirak) [#3823](https://github.com/nodejs/node/pull/3823)
+* [[`c551da8cb4`](https://github.com/nodejs/node/commit/c551da8cb4)] - **repl**: handle quotes within regexp literal (Prince J Wesley) [#5117](https://github.com/nodejs/node/pull/5117)
+* [[`15091ccca2`](https://github.com/nodejs/node/commit/15091ccca2)] - **src**: remove unnecessary check (Brian White) [#5233](https://github.com/nodejs/node/pull/5233)
+* [[`830bb04d90`](https://github.com/nodejs/node/commit/830bb04d90)] - **src**: remove TryCatch in MakeCallback (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* [[`7f22c8c8a6`](https://github.com/nodejs/node/commit/7f22c8c8a6)] - **src**: remove unused TickInfo::in_tick() (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* [[`406eb1f516`](https://github.com/nodejs/node/commit/406eb1f516)] - **src**: remove unused of TickInfo::last_threw() (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* [[`bcec2fecbd`](https://github.com/nodejs/node/commit/bcec2fecbd)] - **src**: add AsyncCallbackScope (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* [[`2cb1594279`](https://github.com/nodejs/node/commit/2cb1594279)] - **src**: fix MakeCallback error handling (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* [[`8d6e679a90`](https://github.com/nodejs/node/commit/8d6e679a90)] - **src,test,tools**: modify for more stringent linting (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`7684b0fcdf`](https://github.com/nodejs/node/commit/7684b0fcdf)] - **stream**: fix no data on partial decode (Brian White) [#5226](https://github.com/nodejs/node/pull/5226)
+* [[`f706cb0189`](https://github.com/nodejs/node/commit/f706cb0189)] - **streams**: 5% throughput gain when sending small chunks (Matteo Collina) [#4354](https://github.com/nodejs/node/pull/4354)
+* [[`25513a473a`](https://github.com/nodejs/node/commit/25513a473a)] - **string_decoder**: fix performance regression (Brian White) [#5134](https://github.com/nodejs/node/pull/5134)
+* [[`0e85530d8c`](https://github.com/nodejs/node/commit/0e85530d8c)] - **test**: use String.prototype.repeat() for clarity (Rich Trott) [#5311](https://github.com/nodejs/node/pull/5311)
+* [[`5683efb90a`](https://github.com/nodejs/node/commit/5683efb90a)] - **test**: remove flaky mark for test-debug-no-context (Rich Trott) [#5317](https://github.com/nodejs/node/pull/5317)
+* [[`c55bb79ace`](https://github.com/nodejs/node/commit/c55bb79ace)] - **test**: add test for https server close event (Braydon Fuller) [#5106](https://github.com/nodejs/node/pull/5106)
+* [[`138ee983b0`](https://github.com/nodejs/node/commit/138ee983b0)] - **test**: refactor test-http-destroyed-socket-write2 (Santiago Gimeno) [#4970](https://github.com/nodejs/node/pull/4970)
+* [[`df7d91f36b`](https://github.com/nodejs/node/commit/df7d91f36b)] - **test**: mitigate flaky test-debug-no-context (Rich Trott) [#5269](https://github.com/nodejs/node/pull/5269)
+* [[`d9177e7c26`](https://github.com/nodejs/node/commit/d9177e7c26)] - **test**: test-process-getactivehandles is flaky (Alexis Campailla) [#5303](https://github.com/nodejs/node/pull/5303)
+* [[`f5cc04732f`](https://github.com/nodejs/node/commit/f5cc04732f)] - **test**: mark test-http-regr-gh-2928 flaky (Rich Trott) [#5280](https://github.com/nodejs/node/pull/5280)
+* [[`78b349d5d1`](https://github.com/nodejs/node/commit/78b349d5d1)] - **test**: disable fs watch tests for AIX (Michael Dawson) [#5187](https://github.com/nodejs/node/pull/5187)
+* [[`82ee5e94df`](https://github.com/nodejs/node/commit/82ee5e94df)] - **test**: mark test-http-agent flaky (Rich Trott) [#5209](https://github.com/nodejs/node/pull/5209)
+* [[`1494d6f213`](https://github.com/nodejs/node/commit/1494d6f213)] - **test**: minimal repl eval option test (Rich Trott) [#5192](https://github.com/nodejs/node/pull/5192)
+* [[`e7bf951136`](https://github.com/nodejs/node/commit/e7bf951136)] - **test**: add addons test for MakeCallback (Trevor Norris) [#4507](https://github.com/nodejs/node/pull/4507)
+* [[`98596a94fa`](https://github.com/nodejs/node/commit/98596a94fa)] - **(SEMVER-MINOR)** **test**: run v8 tests from node tree (Bryon Leung) [#4704](https://github.com/nodejs/node/pull/4704)
+* [[`69c544f245`](https://github.com/nodejs/node/commit/69c544f245)] - **test**: fix flaky test-http-regr-gh-2928 (Rich Trott) [#5154](https://github.com/nodejs/node/pull/5154)
+* [[`7c88410507`](https://github.com/nodejs/node/commit/7c88410507)] - **test**: fix child-process-fork-regr-gh-2847 again (Santiago Gimeno) [#5179](https://github.com/nodejs/node/pull/5179)
+* [[`2c2cb6700d`](https://github.com/nodejs/node/commit/2c2cb6700d)] - **test**: remove unneeded common.indirectInstanceOf() (Rich Trott) [#5149](https://github.com/nodejs/node/pull/5149)
+* [[`6340974f21`](https://github.com/nodejs/node/commit/6340974f21)] - **test**: don't run test-tick-processor.js on Aix (Michael Dawson) [#5093](https://github.com/nodejs/node/pull/5093)
+* [[`a8f4db236c`](https://github.com/nodejs/node/commit/a8f4db236c)] - **test**: improve path tests (Brian White) [#5123](https://github.com/nodejs/node/pull/5123)
+* [[`8301773c1e`](https://github.com/nodejs/node/commit/8301773c1e)] - **test**: fix child-process-fork-regr-gh-2847 (Santiago Gimeno) [#5121](https://github.com/nodejs/node/pull/5121)
+* [[`f2bd86775b`](https://github.com/nodejs/node/commit/f2bd86775b)] - **test**: update arrow function style (cjihrig) [#4813](https://github.com/nodejs/node/pull/4813)
+* [[`aed04b85c2`](https://github.com/nodejs/node/commit/aed04b85c2)] - **tls**: nullify `.ssl` on handle close (Fedor Indutny) [#5168](https://github.com/nodejs/node/pull/5168)
+* [[`c3f8aab652`](https://github.com/nodejs/node/commit/c3f8aab652)] - **(SEMVER-MINOR)** **tls**: add getProtocol() to TLS sockets (Brian White) [#4995](https://github.com/nodejs/node/pull/4995)
+* [[`7fc2e3161f`](https://github.com/nodejs/node/commit/7fc2e3161f)] - **tools**: add Node.js-specific ESLint rules (Rich Trott) [#5320](https://github.com/nodejs/node/pull/5320)
+* [[`983325cb0c`](https://github.com/nodejs/node/commit/983325cb0c)] - **tools**: replace obsolete ESLint rules (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`f601d040b5`](https://github.com/nodejs/node/commit/f601d040b5)] - **tools**: update ESLint to version 2.1.0 (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`13af565759`](https://github.com/nodejs/node/commit/13af565759)] - **tools**: remove obsolete lint rules (Rich Trott) [#5214](https://github.com/nodejs/node/pull/5214)
+* [[`c566f44f1b`](https://github.com/nodejs/node/commit/c566f44f1b)] - **tools**: add recommended ES6 lint rules (Rich Trott) [#5210](https://github.com/nodejs/node/pull/5210)
+* [[`b611caa0ba`](https://github.com/nodejs/node/commit/b611caa0ba)] - **tools**: add recommended linting rules (Rich Trott) [#5188](https://github.com/nodejs/node/pull/5188)
+* [[`b1a16d1202`](https://github.com/nodejs/node/commit/b1a16d1202)] - **tools**: remove excessive comments from .eslintrc (Rich Trott) [#5151](https://github.com/nodejs/node/pull/5151)
+* [[`c4ed5ece4d`](https://github.com/nodejs/node/commit/c4ed5ece4d)] - **tools**: enable no-proto rule for linter (Jackson Tian) [#5140](https://github.com/nodejs/node/pull/5140)
+* [[`86f8477b56`](https://github.com/nodejs/node/commit/86f8477b56)] - **tools**: disallow mixed spaces and tabs for indents (Rich Trott) [#5135](https://github.com/nodejs/node/pull/5135)
+* [[`21fd1496a9`](https://github.com/nodejs/node/commit/21fd1496a9)] - **tools**: alphabetize eslint stylistic issues section (Rich Trott)
+* [[`22c8d50a1f`](https://github.com/nodejs/node/commit/22c8d50a1f)] - **tools**: parse types into links in doc html gen (Claudio Rodriguez) [#4741](https://github.com/nodejs/node/pull/4741)
+* [[`5c54d4987d`](https://github.com/nodejs/node/commit/5c54d4987d)] - **tools**: enable no-redeclare rule for linter (Rich Trott) [#5047](https://github.com/nodejs/node/pull/5047)
+* [[`a3a0cf603a`](https://github.com/nodejs/node/commit/a3a0cf603a)] - **tools**: add arrow function rules to eslint (cjihrig) [#4813](https://github.com/nodejs/node/pull/4813)
+* [[`bcc26f747f`](https://github.com/nodejs/node/commit/bcc26f747f)] - **tools,doc**: fix linting errors (Rich Trott) [#5161](https://github.com/nodejs/node/pull/5161)
+* [[`47274704aa`](https://github.com/nodejs/node/commit/47274704aa)] - **url**: fix lint and deopt issues (Brian White) [#5300](https://github.com/nodejs/node/pull/5300)
+* [[`729ad75860`](https://github.com/nodejs/node/commit/729ad75860)] - **url**: improve url.parse() performance (Brian White) [#4892](https://github.com/nodejs/node/pull/4892)
+* [[`6c8378b15b`](https://github.com/nodejs/node/commit/6c8378b15b)] - **vm**: fix `produceCachedData` (Jiho Choi) [#5343](https://github.com/nodejs/node/pull/5343)
+* [[`d1cacb814f`](https://github.com/nodejs/node/commit/d1cacb814f)] - **(SEMVER-MINOR)** **vm**: introduce `cachedData`/`produceCachedData` (Fedor Indutny) [#4777](https://github.com/nodejs/node/pull/4777)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.7.0/node-v5.7.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.7.0/node-v5.7.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.7.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.7.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.7.0/node-v5.7.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.7.0/node-v5.7.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.7.0/node-v5.7.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.7.0/<br>
+Documentation: https://nodejs.org/docs/v5.7.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+a68a9d45527077e1e044a4036a9b0fc803faa46c97e30fed71b77a759b4fa2fe  node-v5.7.0-darwin-x64.tar.gz
+28b6f045f2e0af49a27b30decbb20fd7ba0fc8e2bd4cb07b195abc1012ba2bb0  node-v5.7.0-darwin-x64.tar.xz
+1ac837924a7fe48f56b04b0952fa15ae6cde6ef968fd10118ca07a09fd182107  node-v5.7.0-headers.tar.gz
+503d2f2cf2575b644fe402e735c8b571f64e66c72ceea619b79261270f0a2447  node-v5.7.0-headers.tar.xz
+2b4de1cca92da4aaec0aec0bc767d7a60d8378e830987abc668176d9b6603ccd  node-v5.7.0-linux-arm64.tar.gz
+e4e1b49269d592719d4064383a5b60d9d37b8a7fe871b133d19636dcf2d9e782  node-v5.7.0-linux-arm64.tar.xz
+844f6707f105f31096579c74ad9928c5a9cce85b2a245bb1d697c06e6a9b1ee8  node-v5.7.0-linux-armv6l.tar.gz
+348665019e7b73f9e0f4b20531523e487fa44ffd4dc5b22530189ef2e7c37416  node-v5.7.0-linux-armv6l.tar.xz
+0712cbe3f05e1828d9cf900ad17007184abc70746bdb2d2064b645f1d3be68c2  node-v5.7.0-linux-armv7l.tar.gz
+f306d89481470a4b0970cb913fe3e2008d0aeae3f137f22491d2f0ee3f6a5e53  node-v5.7.0-linux-armv7l.tar.xz
+ff7d52a87ce152817e3e4e9dba24530b629729539648a0b347bb70d733591a07  node-v5.7.0-linux-ppc64le.tar.gz
+cee33ce09f5a2d31756477d5d45e25293d648e25a31a4b4ea4595a460e67ff1f  node-v5.7.0-linux-ppc64le.tar.xz
+ae24ae3076393e7968316098ddbb0221bde0830a0e9d878c6493604e1cc553c1  node-v5.7.0-linux-x64.tar.gz
+0fe3892820fbd189d72bebe414607485fdca421e86a6c8d60a78ca88585075aa  node-v5.7.0-linux-x64.tar.xz
+09776060a502118765144284c7ad32bd6a737e681819e8349489b9a015a45bbc  node-v5.7.0-linux-x86.tar.gz
+8a3e03c24e3fc03a2996d725d9b6676c5e54ce4a5923fc43daf1821adc4957e8  node-v5.7.0-linux-x86.tar.xz
+52770beac19d56546509ae5b7d0deff69b2ae02151dbbcf3bd410d52229b6e35  node-v5.7.0.pkg
+d8acb8f8fb779d26cda6d3770d48a1f584a0e35ddf154adb4b883bcc4b48a2f2  node-v5.7.0-sunos-x64.tar.gz
+2d2f59c80c31723adddaa0dd2b895c9aa079d7829c71e070f18ad775858100c7  node-v5.7.0-sunos-x64.tar.xz
+208bba5c8a7cf375fa062d489fc413b96665438fd0c3e4a98ca39397c79691d5  node-v5.7.0-sunos-x86.tar.gz
+b8dad0fa46426024abfb7807568547afebe6f0d98165671589c92337b2e6dcc1  node-v5.7.0-sunos-x86.tar.xz
+2338b46a2f45fbb747089c66931f62555f25a5928511d3a43bbb3a39dcded2d8  node-v5.7.0.tar.gz
+7b82697825bd1259d87976608a2d4da609c7bb5eb2d447a58990746317b8c70d  node-v5.7.0.tar.xz
+0567317ba66b7e3f86a1aaf32a54b6485dabff9493d9d651740eccbaedb56b91  node-v5.7.0-x64.msi
+ed2723660c1fd6430987904d305de075b49ce6f5cacc21685e7adf35d0af60c9  node-v5.7.0-x86.msi
+44b77cb1ab7a2b2e8da91e4cacfc250646c9d0fe8c535c4f208bce74611b084c  win-x64/node.exe
+d899a74a6c865c08d0bd6923d202ee21c1f4152868b5559a3b70be7b28c1d775  win-x64/node.lib
+d562d5d6afa66c503df40ba531c1bd2a16c4ef3e875be5a479ffbf9dc2fcdfa9  win-x86/node.exe
+d996aca9ca5d9a370df5c74c88980877f6864c13f326c0cf6e5c4c93ffd62b45  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJWy+++AAoJEMJzeS99g1Rd3skIALQJLDwDo0WuNGFmMWCieq5i
+fNlLQTwrCh284eEnOBSX7YfjsexLCU8ncOYWIYoJQtUioZS53RtoPpsGUxX7dqwS
+T7gaq7WF4kYba+QeWSKbxv2blODDqY5dyys/ck/6Yp2OzxRUy1DkAdkXwa4dMPx/
+5OVn7cn8TY/C5TobAE06BX9CQXP5v0vzqQqgB2fE1sZ7unlFe9xI5Cu5xoqa3G0w
+w1vWFTOug7TJZOUgaIH8O+k53cu0k//bm582285X5YdYMknZ0PYMU+9zqD5AMH6f
+6/iSuuk6lroEX+An5dK37RRXkig9BnHvnRkMxsoARIT33qkI8iauGzxNHt2jB5M=
+=BwDD
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.7.1.md b/locale/uk/blog/release/v5.7.1.md
new file mode 100755
index 0000000000000..73a5024c4721a
--- /dev/null
+++ b/locale/uk/blog/release/v5.7.1.md
@@ -0,0 +1,175 @@
+---
+date: 2016-03-02T23:23:06.216Z
+version: 5.7.1
+category: release
+title: Node v5.7.1 (Current)
+slug: node-v5-7-1
+layout: blog-post.hbs
+author: Jeremiah Senkpiel
+---
+
+### Notable changes
+
+* **governance**: The Core Technical Committee (CTC) added four new members to help guide Node.js core development: Evan Lucas, Rich Trott, Ali Ijaz Sheikh and Сковорода Никита Андреевич (Nikita Skovoroda).
+* **openssl**: Upgrade from 1.0.2f to 1.0.2g (Ben Noordhuis) [#5507](https://github.com/nodejs/node/pull/5507).
+  - Fix a double-free defect in parsing malformed DSA keys that may potentially be used for DoS or memory corruption attacks. It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users. More info is available at [CVE-2016-0705](https://www.openssl.org/news/vulnerabilities.html#2016-0705).
+  - Fix a defect that can cause memory corruption in certain very rare cases relating to the internal `BN_hex2bn()` and `BN_dec2bn()` functions. It is believed that Node.js is not invoking the code paths that use these functions so practical attacks via Node.js using this defect are _unlikely_ to be possible. More info is available at [CVE-2016-0797](https://www.openssl.org/news/vulnerabilities.html#2016-0797).
+  - Fix a defect that makes the _[CacheBleed Attack](https://ssrg.nicta.com.au/projects/TS/cachebleed/)_ possible. This defect enables attackers to execute side-channel attacks leading to the potential recovery of entire RSA private keys. It only affects the Intel Sandy Bridge (and possibly older) microarchitecture when using hyper-threading. Newer microarchitectures, including Haswell, are unaffected. More info is available at [CVE-2016-0702](https://www.openssl.org/news/vulnerabilities.html#2016-0702).
+* Fixed several regressions that appeared in v5.7.0:
+  - **`path.relative()`**:
+    - Output is no longer unnecessarily verbose (Brian White) [#5389](https://github.com/nodejs/node/pull/5389).
+    - Resolving UNC paths on Windows now works correctly (Owen Smith) [#5456](https://github.com/nodejs/node/pull/5456).
+    - Resolving paths with prefixes now works correctly from the root directory (Owen Smith) [#5490](https://github.com/nodejs/node/pull/5490).
+  - **url**: Fixed an off-by-one error with `parse()` (Brian White) [#5394](https://github.com/nodejs/node/pull/5394).
+  - **dgram**: Now correctly handles a default address case when offset and length are specified (Matteo Collina) [#5407](https://github.com/nodejs/node/pull/5407).
+
+### Commits
+
+* [[`7cae774d9b`](https://github.com/nodejs/node/commit/7cae774d9b)] - **benchmark**: refactor to eliminate redeclared vars (Rich Trott) [#5468](https://github.com/nodejs/node/pull/5468)
+* [[`6aebe16669`](https://github.com/nodejs/node/commit/6aebe16669)] - **benchmark**: add benchmark for buf.compare() (Rich Trott) [#5441](https://github.com/nodejs/node/pull/5441)
+* [[`00660f55c8`](https://github.com/nodejs/node/commit/00660f55c8)] - **benchmark**: move string-decoder to its own category (Andreas Madsen) [#5177](https://github.com/nodejs/node/pull/5177)
+* [[`4650cb3818`](https://github.com/nodejs/node/commit/4650cb3818)] - **benchmark**: fix configuation parameters (Andreas Madsen) [#5177](https://github.com/nodejs/node/pull/5177)
+* [[`3ccb275139`](https://github.com/nodejs/node/commit/3ccb275139)] - **benchmark**: merge url.js with url-resolve.js (Andreas Madsen) [#5177](https://github.com/nodejs/node/pull/5177)
+* [[`c1e7dbffaa`](https://github.com/nodejs/node/commit/c1e7dbffaa)] - **benchmark**: move misc to categorized directories (Andreas Madsen) [#5177](https://github.com/nodejs/node/pull/5177)
+* [[`2f9fee6e8e`](https://github.com/nodejs/node/commit/2f9fee6e8e)] - **benchmark**: use strict mode (Rich Trott) [#5336](https://github.com/nodejs/node/pull/5336)
+* [[`4c09e7f359`](https://github.com/nodejs/node/commit/4c09e7f359)] - **build**: remove --quiet from eslint invocation (firedfox) [#5519](https://github.com/nodejs/node/pull/5519)
+* [[`2c619f2012`](https://github.com/nodejs/node/commit/2c619f2012)] - **build**: run lint before tests (Rich Trott) [#5470](https://github.com/nodejs/node/pull/5470)
+* [[`f349a9a2cf`](https://github.com/nodejs/node/commit/f349a9a2cf)] - **build**: update Node.js logo on OSX installer (Rod Vagg) [#5401](https://github.com/nodejs/node/pull/5401)
+* [[`88f393588a`](https://github.com/nodejs/node/commit/88f393588a)] - **crypto**: PBKDF2 works with `int` not `ssize_t` (Fedor Indutny) [#5397](https://github.com/nodejs/node/pull/5397)
+* [[`1e86804503`](https://github.com/nodejs/node/commit/1e86804503)] - **deps**: upgrade openssl to 1.0.2g (Ben Noordhuis) [#5507](https://github.com/nodejs/node/pull/5507)
+* [[`d3f9b84be8`](https://github.com/nodejs/node/commit/d3f9b84be8)] - **dgram**: handle default address case when offset and length are specified (Matteo Collina)
+* [[`f1f3832934`](https://github.com/nodejs/node/commit/f1f3832934)] - **doc**: update NAN urls in ROADMAP.md and doc/releases.md (ronkorving) [#5472](https://github.com/nodejs/node/pull/5472)
+* [[`51bc062dab`](https://github.com/nodejs/node/commit/51bc062dab)] - **doc**: add CTC meeting minutes 2016-02-17 (Rod Vagg) [#5410](https://github.com/nodejs/node/pull/5410)
+* [[`795c85ba1c`](https://github.com/nodejs/node/commit/795c85ba1c)] - **doc**: fix typo in child_process documentation (Evan Lucas) [#5474](https://github.com/nodejs/node/pull/5474)
+* [[`0a56e9690b`](https://github.com/nodejs/node/commit/0a56e9690b)] - **doc**: add note for binary safe string reading (Anton Andesen) [#5155](https://github.com/nodejs/node/pull/5155)
+* [[`ea8331e15f`](https://github.com/nodejs/node/commit/ea8331e15f)] - **doc**: improvements to crypto.markdown copy (Alexander Makarenko) [#5230](https://github.com/nodejs/node/pull/5230)
+* [[`378a772034`](https://github.com/nodejs/node/commit/378a772034)] - **doc**: `require` behavior on case-insensitive systems (Hugo Wood)
+* [[`06b7eb6636`](https://github.com/nodejs/node/commit/06b7eb6636)] - **doc**: document base64url encoding support (Tristan Slominski) [#5243](https://github.com/nodejs/node/pull/5243)
+* [[`8ec3d904cb`](https://github.com/nodejs/node/commit/8ec3d904cb)] - **doc**: improve httpVersionMajor / httpVersionMajor (Jackson Tian) [#5296](https://github.com/nodejs/node/pull/5296)
+* [[`534e88f56c`](https://github.com/nodejs/node/commit/534e88f56c)] - **doc**: fix relative links in net docs (Evan Lucas) [#5358](https://github.com/nodejs/node/pull/5358)
+* [[`7b98a30976`](https://github.com/nodejs/node/commit/7b98a30976)] - **doc**: fix crypto function indentation level (Brian White) [#5460](https://github.com/nodejs/node/pull/5460)
+* [[`c0fd802cc2`](https://github.com/nodejs/node/commit/c0fd802cc2)] - **doc**: link to man pages (dcposch@dcpos.ch) [#5073](https://github.com/nodejs/node/pull/5073)
+* [[`f8c6701e22`](https://github.com/nodejs/node/commit/f8c6701e22)] - **doc**: add missing property in cluster example (Rafael Cepeda) [#5305](https://github.com/nodejs/node/pull/5305)
+* [[`3bfe0483f0`](https://github.com/nodejs/node/commit/3bfe0483f0)] - **doc**: corrected name of argument in socket.send (Chris Dew) [#5449](https://github.com/nodejs/node/pull/5449)
+* [[`c8725f5e95`](https://github.com/nodejs/node/commit/c8725f5e95)] - **doc**: fix links in tls, cluster docs (Alexander Makarenko) [#5364](https://github.com/nodejs/node/pull/5364)
+* [[`7f2cf9af5c`](https://github.com/nodejs/node/commit/7f2cf9af5c)] - **doc**: explicit about VS 2015 support in readme (Phillip Johnsen) [#5406](https://github.com/nodejs/node/pull/5406)
+* [[`12d3cdbfea`](https://github.com/nodejs/node/commit/12d3cdbfea)] - **doc**: remove out-of-date matter from internal docs (Rich Trott) [#5421](https://github.com/nodejs/node/pull/5421)
+* [[`43853679f7`](https://github.com/nodejs/node/commit/43853679f7)] - **doc**: copyedit util doc (Rich Trott) [#5399](https://github.com/nodejs/node/pull/5399)
+* [[`903e8d09e1`](https://github.com/nodejs/node/commit/903e8d09e1)] - **doc**: fix typo in pbkdf2Sync code sample (Marc Cuva) [#5306](https://github.com/nodejs/node/pull/5306)
+* [[`79b1c22c9f`](https://github.com/nodejs/node/commit/79b1c22c9f)] - **doc**: fix buf.readInt16LE output (Chinedu Francis Nwafili) [#5282](https://github.com/nodejs/node/pull/5282)
+* [[`e46915f2f3`](https://github.com/nodejs/node/commit/e46915f2f3)] - **doc**: note util.isError() @@toStringTag limitations (cjihrig) [#5414](https://github.com/nodejs/node/pull/5414)
+* [[`935fd21fff`](https://github.com/nodejs/node/commit/935fd21fff)] - **doc**: clarify error handling in net.createServer (Dirceu Pereira Tiegs) [#5353](https://github.com/nodejs/node/pull/5353)
+* [[`93dce6d4fe`](https://github.com/nodejs/node/commit/93dce6d4fe)] - **doc**: document fs.datasync(Sync) (Ron Korving) [#5402](https://github.com/nodejs/node/pull/5402)
+* [[`96daf51358`](https://github.com/nodejs/node/commit/96daf51358)] - **doc**: add Evan Lucas to the CTC (Rod Vagg) [#5275](https://github.com/nodejs/node/pull/5275)
+* [[`31b405d0cf`](https://github.com/nodejs/node/commit/31b405d0cf)] - **doc**: add Rich Trott to the CTC (Rod Vagg) [#5276](https://github.com/nodejs/node/pull/5276)
+* [[`bcd154e402`](https://github.com/nodejs/node/commit/bcd154e402)] - **doc**: add Ali Ijaz Sheikh to the CTC (Rod Vagg) [#5277](https://github.com/nodejs/node/pull/5277)
+* [[`9d0330c804`](https://github.com/nodejs/node/commit/9d0330c804)] - **doc**: add Сковорода Никита Андреевич to the CTC (Rod Vagg) [#5278](https://github.com/nodejs/node/pull/5278)
+* [[`365cc63783`](https://github.com/nodejs/node/commit/365cc63783)] - **doc**: add "building node with ninja" guide (Jeremiah Senkpiel) [#4767](https://github.com/nodejs/node/pull/4767)
+* [[`2b00c315e1`](https://github.com/nodejs/node/commit/2b00c315e1)] - **doc**: mention prototype check in deepStrictEqual() (cjihrig) [#5367](https://github.com/nodejs/node/pull/5367)
+* [[`ff988b3ee6`](https://github.com/nodejs/node/commit/ff988b3ee6)] - **doc,tools,test**: lint doc-based addon tests (Rich Trott) [#5427](https://github.com/nodejs/node/pull/5427)
+* [[`d77c3bf204`](https://github.com/nodejs/node/commit/d77c3bf204)] - **http_parser**: use `MakeCallback` (Trevor Norris) [#5419](https://github.com/nodejs/node/pull/5419)
+* [[`e3421ac296`](https://github.com/nodejs/node/commit/e3421ac296)] - **lib**: freelist: use .pop() for allocation (Anton Khlynovskiy) [#2174](https://github.com/nodejs/node/pull/2174)
+* [[`91d218d096`](https://github.com/nodejs/node/commit/91d218d096)] - **path**: fix path.relative() for prefixes at root (Owen Smith) [#5490](https://github.com/nodejs/node/pull/5490)
+* [[`ef7a088906`](https://github.com/nodejs/node/commit/ef7a088906)] - **path**: fix win32 parse() (Zheng Chaoping) [#5484](https://github.com/nodejs/node/pull/5484)
+* [[`871396ce8f`](https://github.com/nodejs/node/commit/871396ce8f)] - **path**: fix win32 relative() for UNC paths (Owen Smith) [#5456](https://github.com/nodejs/node/pull/5456)
+* [[`91782f1888`](https://github.com/nodejs/node/commit/91782f1888)] - **path**: fix win32 relative() when "to" is a prefix (Owen Smith) [#5456](https://github.com/nodejs/node/pull/5456)
+* [[`30cec18eeb`](https://github.com/nodejs/node/commit/30cec18eeb)] - **path**: fix verbose relative() output (Brian White) [#5389](https://github.com/nodejs/node/pull/5389)
+* [[`2b88523836`](https://github.com/nodejs/node/commit/2b88523836)] - **repl**: fix stack trace column number in strict mode (Prince J Wesley) [#5416](https://github.com/nodejs/node/pull/5416)
+* [[`51db48f741`](https://github.com/nodejs/node/commit/51db48f741)] - **src,tools**: remove null sentinel from source array (Ben Noordhuis) [#5418](https://github.com/nodejs/node/pull/5418)
+* [[`03a5daba55`](https://github.com/nodejs/node/commit/03a5daba55)] - **src,tools**: drop nul byte from built-in source code (Ben Noordhuis) [#5418](https://github.com/nodejs/node/pull/5418)
+* [[`17d14f3346`](https://github.com/nodejs/node/commit/17d14f3346)] - **src,tools**: allow utf-8 in built-in js source code (Ben Noordhuis) [#5418](https://github.com/nodejs/node/pull/5418)
+* [[`12ae6abc69`](https://github.com/nodejs/node/commit/12ae6abc69)] - **test**: increase timeout for test-tls-fast-writing (Rich Trott) [#5466](https://github.com/nodejs/node/pull/5466)
+* [[`81348e8855`](https://github.com/nodejs/node/commit/81348e8855)] - **test**: apply Linux workaround to Linux only (Rich Trott) [#5471](https://github.com/nodejs/node/pull/5471)
+* [[`c4d9cdb7d0`](https://github.com/nodejs/node/commit/c4d9cdb7d0)] - **test**: allow options for v8 testing (Michael Dawson) [#5502](https://github.com/nodejs/node/pull/5502)
+* [[`d1a82c6824`](https://github.com/nodejs/node/commit/d1a82c6824)] - **test**: retry on known SmartOS bug (Rich Trott) [#5454](https://github.com/nodejs/node/pull/5454)
+* [[`c7f8a13043`](https://github.com/nodejs/node/commit/c7f8a13043)] - **test**: remove unneeded bind() and related comments (Aayush Naik) [#5023](https://github.com/nodejs/node/pull/5023)
+* [[`cc4cbb10df`](https://github.com/nodejs/node/commit/cc4cbb10df)] - **test**: fix flaky child-process-fork-regr-gh-2847 (Santiago Gimeno) [#5422](https://github.com/nodejs/node/pull/5422)
+* [[`0ebbf6cd53`](https://github.com/nodejs/node/commit/0ebbf6cd53)] - **test**: remove flaky designation from fixed tests (Rich Trott) [#5459](https://github.com/nodejs/node/pull/5459)
+* [[`c83725c604`](https://github.com/nodejs/node/commit/c83725c604)] - **test**: add test-cases for posix path.relative() (Owen Smith) [#5456](https://github.com/nodejs/node/pull/5456)
+* [[`22bb7c9d27`](https://github.com/nodejs/node/commit/22bb7c9d27)] - **test**: fix test runner arg regression (Stefan Budeanu) [#5446](https://github.com/nodejs/node/pull/5446)
+* [[`8c67b94b11`](https://github.com/nodejs/node/commit/8c67b94b11)] - **test**: refactor test-dgram-send-callback-recursive (Santiago Gimeno) [#5079](https://github.com/nodejs/node/pull/5079)
+* [[`2c21d34a2f`](https://github.com/nodejs/node/commit/2c21d34a2f)] - **test**: refactor test-dgram-udp4 (Santiago Gimeno) [#5339](https://github.com/nodejs/node/pull/5339)
+* [[`479a43c876`](https://github.com/nodejs/node/commit/479a43c876)] - **test**: allow passing args to executable (Stefan Budeanu) [#5376](https://github.com/nodejs/node/pull/5376)
+* [[`ff75023812`](https://github.com/nodejs/node/commit/ff75023812)] - **test**: fix test-timers.reliability on OS X (Rich Trott) [#5379](https://github.com/nodejs/node/pull/5379)
+* [[`991f82b4bd`](https://github.com/nodejs/node/commit/991f82b4bd)] - **test**: mitigate flaky test-http-agent (Rich Trott) [#5346](https://github.com/nodejs/node/pull/5346)
+* [[`0f54553a99`](https://github.com/nodejs/node/commit/0f54553a99)] - **test**: increase timeouts on some unref timers tests (Jeremiah Senkpiel) [#5352](https://github.com/nodejs/node/pull/5352)
+* [[`25c01cd779`](https://github.com/nodejs/node/commit/25c01cd779)] - **tls**: fix assert in context.\_external accessor (Ben Noordhuis) [#5521](https://github.com/nodejs/node/pull/5521)
+* [[`5ffd7430d1`](https://github.com/nodejs/node/commit/5ffd7430d1)] - **tools**: apply custom buffer lint rule to /lib only (Rich Trott) [#5371](https://github.com/nodejs/node/pull/5371)
+* [[`fa5d28f246`](https://github.com/nodejs/node/commit/fa5d28f246)] - **tools**: enable additional lint rules (Rich Trott) [#5357](https://github.com/nodejs/node/pull/5357)
+* [[`b44b701e5b`](https://github.com/nodejs/node/commit/b44b701e5b)] - **tools,benchmark**: increase lint compliance (Rich Trott) [#5429](https://github.com/nodejs/node/pull/5429)
+* [[`9424fa5732`](https://github.com/nodejs/node/commit/9424fa5732)] - **url**: group slashed protocols by protocol name (nettofarah) [#5380](https://github.com/nodejs/node/pull/5380)
+* [[`dfe45f13e7`](https://github.com/nodejs/node/commit/dfe45f13e7)] - **url**: fix off-by-one error with parse() (Brian White) [#5394](https://github.com/nodejs/node/pull/5394)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.7.1/node-v5.7.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.7.1/node-v5.7.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.7.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.7.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.7.1/node-v5.7.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.7.1/node-v5.7.1-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.7.1/node-v5.7.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.7.1/<br>
+Documentation: https://nodejs.org/docs/v5.7.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+25627633163e6ad47e62cd9aaab04e47707b51ecc5aaa05f35a2d6419dbe054c  node-v5.7.1-darwin-x64.tar.gz
+7d23cb68d8587a6baa8f9023bf326430ca50d669817bac2cd6129cdb435ac0c3  node-v5.7.1-darwin-x64.tar.xz
+6d2241bc1e5049de3651873d63b84c37f8684027b1a34928ce6bbe745057ca70  node-v5.7.1-headers.tar.gz
+655cbc2da0808edbb965fbb698713ea022e9e7d311604e0ae73904de59df528c  node-v5.7.1-headers.tar.xz
+b075aa249eb1e00e1e84e6f5964d4f93c39aa6d817c25280bf885bfcf906c7fc  node-v5.7.1-linux-arm64.tar.gz
+61f411e5352d10533cfde00ff2e5b3bc0c31326d46e4e76a0736cf44e2f031ea  node-v5.7.1-linux-arm64.tar.xz
+ddde92eb9b80e58efec88138fa7351e21000b22414ebff754c7ab38dedbab89f  node-v5.7.1-linux-armv6l.tar.gz
+dd1ade05801824f0386a43890c1500715e628ac4a78b85eb6f2949edad5eaa7c  node-v5.7.1-linux-armv6l.tar.xz
+2370e6ad65dedc1eadcc1b3a481e922a8b5afacee9e90eb6700fee876eb59a5b  node-v5.7.1-linux-armv7l.tar.gz
+4617186ac4e615f2166dbbd0ef923971d37af630f4aad85cd93bacba74c56fb9  node-v5.7.1-linux-armv7l.tar.xz
+f3de80e67a3f055bb3e2ecdb9e4b6cc45183a6cbee2b728f243d46a6fd94f542  node-v5.7.1-linux-ppc64le.tar.gz
+81b0e67145e317f4c6f9be58a3485990285fdd866f2c11509ffc68927d2e75d4  node-v5.7.1-linux-ppc64le.tar.xz
+fcded78b45549e2195eecb36138ba29b6f353d0d136d4e8b80648770418f1e5b  node-v5.7.1-linux-x64.tar.gz
+5584895f87a57ee26a75bf8505f6a2350a3ab219accf1df44c2f6406ddfad6ed  node-v5.7.1-linux-x64.tar.xz
+4382b7366f3448d42f09d63f7dfccf45bf67f8be94d2bfe7203bdc79d0ae64e8  node-v5.7.1-linux-x86.tar.gz
+6a9063fd23bf4e14d966f18b3cf092192f2a05daf8e6253b92adc2be422959e1  node-v5.7.1-linux-x86.tar.xz
+d96c04a7df03f630e66fdf5173912cfb1e412bba4453aad67e007d5bb59d16b4  node-v5.7.1.pkg
+0ebab64c25a417b741f666db1765c7358e413d895d4dd0ca9e967fdbb1770a72  node-v5.7.1-sunos-x64.tar.gz
+8f7bc96926e75971ade13c183378929442021eca5055752b0b47601b60b1a474  node-v5.7.1-sunos-x64.tar.xz
+1deb8d1eee46dfdb15c01fea1b283cc9115d78d2e4757ab6192b80bf52d61f99  node-v5.7.1-sunos-x86.tar.gz
+43221b7de7c0e684d65e1898244f876deb25c3e0d614e7f01261a6af5e39f3b7  node-v5.7.1-sunos-x86.tar.xz
+ecd4956335c6b86f1b72fd203abd9a833717e6800edb12208d0e3ce625330198  node-v5.7.1.tar.gz
+029ed8aeb997c68d1a901cd837af02d24b6b5e20a4ff93bed090fd289f91a9a1  node-v5.7.1.tar.xz
+d453670c8edf551fc319fcb997cae8e19180aa09593d0228730fc8997c02316c  node-v5.7.1-x64.msi
+f486032411c50a6ea40d361067eb78d2e383737f72d0c14e081e04aff23e6991  node-v5.7.1-x86.msi
+de17f951cc28bcd90015703b23e153d19673ee476016d923ff9e5588a6f17593  win-x64/node.exe
+752e5b5ea84e7bc828582bceb5ff2faade62234d63f4924ac935c0cc0d2c1bdf  win-x64/node.lib
+249614b8ab6106d91229c1b3c2732b0985334e9b3c28c25bff2d681ab5730a56  win-x86/node.exe
+4237fb7203656e3caffb4af4ea7875957a4d26860576de52767abfed88f5f7b8  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJW13WxAAoJEEX17r2BPa6OTokP/At3k4PP5DuSviM3hWGINJUB
+FHgtwN5ZhV2L07mLwOsD2uogvjBIe8FnNPtLiB1On80E17lMyvUC8GfYmaxG1QWx
+fYIMA/vDPtEE9ckUJ0zF800z9nECjLbFQ1aJ2iCz5yPS7rg/1RsMokpGa5+PbrRB
+L5DPBU+I9ZImiQKVF4cscIPfCdBd9itPwVSBLNn9silnAdX4s8kMcIg0O3uXI2S5
+k3A3b7tsUDEWhdg3uq4R3t/Y8uzsjpywYRbJQMqQ67RBFE64N3eRRygUWKOgmyob
+rPZNAsARu0k3ORn48gfauCTaxxqsdVd3Wrp2thFD5KOs8/TVXKjIrKkoNynGNgTE
+S+iWCWCj7n7inGMslq6hHCzxwgbhtRQKMyQW7uGJak4OhrlNsn/7GW9HDTQDxSof
+SQgt62++j3wJ4U9Ywl18ZB790BmjxIzH6K5qxK+sW6cADHXRobeYWX/IU5c2y+Gz
+wKMMHejQlSPZM4aZYJlBuUcWlkex7o5Mhkpu5hq+OWIN9c2uPJJ35Jh5m/ZGL8AL
+ZmlrFU2esrO0a7R2PV0+9ESG7x8aizvY7vquuVdF3uMn3CrfWG0ssp/xWpAHWorK
+qUUdd4fdX57rdxuyWj58t7Iq2ri6RxgNf2nnZiFyUyfGdsOzyrNT6ES5exnjdzxw
+K5Jnwx41hOBpEJ1XMwRn
+=8dum
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.8.0.md b/locale/uk/blog/release/v5.8.0.md
new file mode 100755
index 0000000000000..446ca89a3a933
--- /dev/null
+++ b/locale/uk/blog/release/v5.8.0.md
@@ -0,0 +1,128 @@
+---
+date: 2016-03-09T15:57:36.574Z
+version: 5.8.0
+category: release
+title: Node v5.8.0 (Current)
+slug: node-v5-8-0
+layout: blog-post.hbs
+author: Jeremiah Senkpiel
+---
+
+### Notable changes
+
+* **child_process**: `send()` now accepts an options parameter (cjihrig) [#5283](https://github.com/nodejs/node/pull/5283).
+  - Currently the only option is `keepOpen`, which keeps the underlying socket open after the message is sent.
+* **constants**: `ENGINE_METHOD_RSA` is now correctly exposed (Sam Roberts) [#5463](https://github.com/nodejs/node/pull/5463).
+* Fixed two regressions which originated in v5.7.0:
+  - **http**: Errors inside of http client callbacks now propagate correctly (Trevor Norris) [#5591](https://github.com/nodejs/node/pull/5591).
+  - **path**: Fixed normalization of absolute paths (Evan Lucas) [#5589](https://github.com/nodejs/node/pull/5589).
+* **repl**: `start()` no longer requires an options parameter (cjihrig) [#5388](https://github.com/nodejs/node/pull/5388).
+* **util**: Improved `format()` performance 50-300% (Evan Lucas) [#5360](https://github.com/nodejs/node/pull/5360).
+
+### Commits
+
+* [[`12ca84fc7f`](https://github.com/nodejs/node/commit/12ca84fc7f)] - **benchmark**: add util.format benchmark (Evan Lucas) [#5360](https://github.com/nodejs/node/pull/5360)
+* [[`b955d02266`](https://github.com/nodejs/node/commit/b955d02266)] - **benchmark**: fix lint errors (Rich Trott) [#5517](https://github.com/nodejs/node/pull/5517)
+* [[`2abf866b6e`](https://github.com/nodejs/node/commit/2abf866b6e)] - **build**: update Node.js logo on Win installer (Robert Jefe Lindstaedt) [#5531](https://github.com/nodejs/node/pull/5531)
+* [[`86900f8f2b`](https://github.com/nodejs/node/commit/86900f8f2b)] - **build**: correctly detect clang version (Stefan Budeanu) [#5553](https://github.com/nodejs/node/pull/5553)
+* [[`a3017992e4`](https://github.com/nodejs/node/commit/a3017992e4)] - **(SEMVER-MINOR)** **child_process**: add keepOpen option to send() (cjihrig) [#5283](https://github.com/nodejs/node/pull/5283)
+* [[`6d4887ccc2`](https://github.com/nodejs/node/commit/6d4887ccc2)] - **(SEMVER-MINOR)** **child_process**: support options in send() (cjihrig) [#5283](https://github.com/nodejs/node/pull/5283)
+* [[`9db827c7aa`](https://github.com/nodejs/node/commit/9db827c7aa)] - **(SEMVER-MINOR)** **constants**: define ENGINE_METHOD_RSA (Sam Roberts) [#5463](https://github.com/nodejs/node/pull/5463)
+* [[`85013456cd`](https://github.com/nodejs/node/commit/85013456cd)] - **deps**: upgrade to npm 3.7.3 (Kat Marchán) [#5369](https://github.com/nodejs/node/pull/5369)
+* [[`67e9f65958`](https://github.com/nodejs/node/commit/67e9f65958)] - **dgram**: default send address to 127.0.0.1 or ::1 (Matteo Collina) [#5493](https://github.com/nodejs/node/pull/5493)
+* [[`3c92352c8c`](https://github.com/nodejs/node/commit/3c92352c8c)] - **doc**: document directories in test directory (Michael Barrett) [#5557](https://github.com/nodejs/node/pull/5557)
+* [[`7be726f86a`](https://github.com/nodejs/node/commit/7be726f86a)] - **doc**: add info to docs on how to submit docs patch (Sequoia McDowell) [#4591](https://github.com/nodejs/node/pull/4591)
+* [[`eb5a95e04a`](https://github.com/nodejs/node/commit/eb5a95e04a)] - **doc**: fix typo in fs.symlink (Michaël Zasso) [#5560](https://github.com/nodejs/node/pull/5560)
+* [[`9ad901ef44`](https://github.com/nodejs/node/commit/9ad901ef44)] - **doc**: improve unhandledException doc copy (James M Snell) [#5287](https://github.com/nodejs/node/pull/5287)
+* [[`3bd96fdb0f`](https://github.com/nodejs/node/commit/3bd96fdb0f)] - **doc**: update link green to match homepage (silverwind) [#5548](https://github.com/nodejs/node/pull/5548)
+* [[`cb7e4fbac9`](https://github.com/nodejs/node/commit/cb7e4fbac9)] - **doc**: update V8 URL (Craig Akimoto) [#5530](https://github.com/nodejs/node/pull/5530)
+* [[`b54a26fa61`](https://github.com/nodejs/node/commit/b54a26fa61)] - **(SEMVER-MINOR)** **doc**: correct name of engine methods (Sam Roberts) [#5463](https://github.com/nodejs/node/pull/5463)
+* [[`f3971f5817`](https://github.com/nodejs/node/commit/f3971f5817)] - **path**: fix normalize for absolutes (Evan Lucas) [#5589](https://github.com/nodejs/node/pull/5589)
+* [[`e572e421b4`](https://github.com/nodejs/node/commit/e572e421b4)] - **(SEMVER-MINOR)** **repl**: accept no arguments to start() (cjihrig) [#5388](https://github.com/nodejs/node/pull/5388)
+* [[`5e6d706758`](https://github.com/nodejs/node/commit/5e6d706758)] - **src,http**: fix uncaughtException miss in http (Trevor Norris) [#5591](https://github.com/nodejs/node/pull/5591)
+* [[`9dc94d7b09`](https://github.com/nodejs/node/commit/9dc94d7b09)] - **test**: add test-npm-install to parallel tests suite (Myles Borins) [#5166](https://github.com/nodejs/node/pull/5166)
+* [[`4f20f31b3e`](https://github.com/nodejs/node/commit/4f20f31b3e)] - **test**: remove broken debugger scenarios (Rich Trott) [#5532](https://github.com/nodejs/node/pull/5532)
+* [[`29e26b38c5`](https://github.com/nodejs/node/commit/29e26b38c5)] - **test**: bug repro for vm function redefinition (cjihrig) [#5528](https://github.com/nodejs/node/pull/5528)
+* [[`e6210d5f50`](https://github.com/nodejs/node/commit/e6210d5f50)] - **test**: prevent flakey test on pi2 (Trevor Norris) [#5537](https://github.com/nodejs/node/pull/5537)
+* [[`40b36baa2f`](https://github.com/nodejs/node/commit/40b36baa2f)] - **test**: check memoryUsage properties (Wyatt Preul) [#5546](https://github.com/nodejs/node/pull/5546)
+* [[`048c0f4738`](https://github.com/nodejs/node/commit/048c0f4738)] - **tools**: reduce verbosity of cpplint (Sakthipriyan Vairamani) [#5578](https://github.com/nodejs/node/pull/5578)
+* [[`7965c897e0`](https://github.com/nodejs/node/commit/7965c897e0)] - **tools**: enable no-self-assign ESLint rule (Rich Trott) [#5552](https://github.com/nodejs/node/pull/5552)
+* [[`5aa17dc136`](https://github.com/nodejs/node/commit/5aa17dc136)] - **tools**: support testing known issues (cjihrig) [#5528](https://github.com/nodejs/node/pull/5528)
+* [[`9a3e87e9a8`](https://github.com/nodejs/node/commit/9a3e87e9a8)] - **tools**: enable linting for benchmarks (Rich Trott) [#5517](https://github.com/nodejs/node/pull/5517)
+* [[`c4fa2a6715`](https://github.com/nodejs/node/commit/c4fa2a6715)] - **tools**: enable no-extra-parens in ESLint (Rich Trott) [#5512](https://github.com/nodejs/node/pull/5512)
+* [[`971edde0cb`](https://github.com/nodejs/node/commit/971edde0cb)] - **util**: improve format() performance further (Brian White) [#5360](https://github.com/nodejs/node/pull/5360)
+* [[`c32d460747`](https://github.com/nodejs/node/commit/c32d460747)] - **util**: improve util.format performance (Evan Lucas) [#5360](https://github.com/nodejs/node/pull/5360)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.8.0/node-v5.8.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.8.0/node-v5.8.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.8.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.8.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.8.0/node-v5.8.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.8.0/node-v5.8.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.8.0/node-v5.8.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.8.0/<br>
+Documentation: https://nodejs.org/docs/v5.8.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+8c16f21a1c8882ba5875d0da617c817aa5005e514bd460dbf32aaeb3ffa477fe  node-v5.8.0-darwin-x64.tar.gz
+c44e84f6d38e4e71f5d47da29a89ee1501e3006198fa44e1f6ebef37fa69ed74  node-v5.8.0-darwin-x64.tar.xz
+1f8501149f7160d30341df82a9634e0e65256d096f092c68ad820bcd435000eb  node-v5.8.0-headers.tar.gz
+828d525ca284a7a49f02486775173c6b19f2a12587acef4175a7a327ac05732d  node-v5.8.0-headers.tar.xz
+0c2c0fa859c5be13cd1404f3fb14d37e38a67fb2fc075c7a37d4ae70374544bf  node-v5.8.0-linux-arm64.tar.gz
+7fb3085dcd68da5b272452254e2284d53aa9b42fe4b92ec867448b8c4e66278a  node-v5.8.0-linux-arm64.tar.xz
+54c362af9bc80b9e283bee7807fb2b1e9207ac77e61207b13fcf9f9acecd293f  node-v5.8.0-linux-armv6l.tar.gz
+814f7589b932cb88081226ee02212e3593e016945f18940cfdc576c9b15a0575  node-v5.8.0-linux-armv6l.tar.xz
+cdb0355fc41ac7010926f1a35f07f0dfe94020572d70296f91e60d18ab4873f5  node-v5.8.0-linux-armv7l.tar.gz
+fe40ba09733fd754dee864daee4cda9007d4ee8c48c1eb0343dd72ea007e8e8b  node-v5.8.0-linux-armv7l.tar.xz
+59f4745346786fdad8d58022b5eefc7cd5ec143d5cce03c66c1243e531fd10e8  node-v5.8.0-linux-ppc64le.tar.gz
+39f651f94be359f759d8a0634ef1a8afef8b86316d6d86518a7a898bd4536c8b  node-v5.8.0-linux-ppc64le.tar.xz
+3d33efa2421ed0769cc23ac172203b7db9fe4914a186009ddbac28c9aadb0896  node-v5.8.0-linux-x64.tar.gz
+503255baf9517344dc277e6ca4a495defeb4c52e2b5628e67b3522ec6eb5e318  node-v5.8.0-linux-x64.tar.xz
+b302ce9d5d156857576d892cfe8108363b30c20bd3133011fb2050d56bb238e8  node-v5.8.0-linux-x86.tar.gz
+6b324b7568d01ef273223d36d11e1323cbdb43f7fea89a945c132a4163f9fdf6  node-v5.8.0-linux-x86.tar.xz
+e407dd96cfee06f1a79eaa2d26c1745afd7224edb9fe62076a15622798df8479  node-v5.8.0.pkg
+235783950678e3f343c5ce8e567a4600141ff9ad87aca0364bea659a82563f6c  node-v5.8.0-sunos-x64.tar.gz
+736cfacd40a64d2c0036a9a8ddd705978c39059635584f1fd196d2cf8e6b6726  node-v5.8.0-sunos-x64.tar.xz
+5edb23172d0a2b064dddb090ed5dae06a12db50dcc71f652748076d994f607ba  node-v5.8.0-sunos-x86.tar.gz
+76a12b6141b89460fc752a7a726fea50526df6ae70341f6cfad5d48acdf575e7  node-v5.8.0-sunos-x86.tar.xz
+e8cd580cec1c62053e6357633b9e46d49df1fd5b9fc5c804ca59ba80d722b898  node-v5.8.0.tar.gz
+c1246d473d6650ca02ab168eaf840e9edda82a4190ff08165fc44a7b381a9361  node-v5.8.0.tar.xz
+be2d055f593c080f2c48e8b9e3a7f864b34bc8763d8903d4b1470bb153bdaec0  node-v5.8.0-x64.msi
+10a9c0445926e2a2544d426954c6810ef25fdb9f3f16a4a9921e5ba66b5dbb48  node-v5.8.0-x86.msi
+638dc7e840206d03855d940d18e4ed92855034683290ef30ef505a3d1395b88e  win-x64/node.exe
+5cfc85c3ea25fec18abfe3f74d6fc89956a8cce6c6cb1c2a54808cc1213d5b03  win-x64/node.lib
+3b94153c8601764b8ca5b8836270123257c17f1f02c2850540540c3151089d84  win-x86/node.exe
+f274baee290a22510a591595572a4fa7f465a50a4fa94ade3cab72a934558aac  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJW4EN5AAoJEEX17r2BPa6OzqEP/jqXzIjGG+4RWjvnZrsjOUrP
+fWhr3ppECdrHRw20J5aXbUSF8k2mLrDfx8pNvRXbS+aQkkgXCXWnlSnP8uysoEMr
+fgdecsh+gxqEQ9xoC+ZX7r1h3Uog/6xA8iXUiB8R7r1SFQf27UNt0y0EFOjHls3M
+EfblKJ87dK0qRef9adtLqXrRh6Nymwbp4XIf2TtsZwpgwffv72igh96XdptaeDs8
+Bdp7VaeYFfWl/I8cxlbLY4gMNbMkrp3OZAus1hcTFG4pz9X3PD+EPTuMVnOAmSnK
+s23hExZ6HFlR2qi40f/e7wFXRlkbBrvNFvK5/8AV9KdEEB9KWCzjZVIn/SCPpvxE
+OKeStQqai5j2pB+w2nTv/yR/kMz6zagnycqsn3N6Di+r5E1rlE1P6fV41QGBqJZK
+M6gG9Eol+AUSy7r8kW2/DFA96I7LlOGAb4EgPS17/EG9weeLTQqIuAwqGDTnF5HZ
+X8g4nynrHqHwfVNW7t74pbZSVUGYPklI/87J419HPUKpMNhNSQVuwfXdk1r0PbGP
+jpE/SiK29/vah7i4vDqIuCjTSmOsaSvqst1NOEUye9sgos+D91o19cSB8hF5QxDw
+lzBmadMQq7i+uc3L7RVXOZ8jTPHlPySuwvOQOQvOH8veL4tITKWnyACYIlr+ED5I
+5DyqJwkBGgB5A3gWOpu7
+=Giqy
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.9.0.md b/locale/uk/blog/release/v5.9.0.md
new file mode 100755
index 0000000000000..ea2098b3c00e9
--- /dev/null
+++ b/locale/uk/blog/release/v5.9.0.md
@@ -0,0 +1,158 @@
+---
+date: 2016-03-16T21:34:26.150Z
+version: 5.9.0
+category: release
+title: Node v5.9.0 (Current)
+slug: node-v5-9-0
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+### Notable changes
+
+* **contextify**: Fixed a memory consumption issue related to heavy use of `vm.createContext` and `vm.runInNewContext`. (Ali Ijaz Sheikh)
+https://github.com/nodejs/node/pull/5392
+* **governance**: The following members have been added as collaborators:
+ - Andreas Madsen (@AndreasMadsen)
+ - Benjamin Gruenbaum (@benjamingr)
+ - Claudio Rodriguez (@claudiorodriguez)
+ - Glen Keane (@thekemkid)
+ - Jeremy Whitlock (@whitlockjc)
+ - Matt Loring (@matthewloring)
+ - Phillip Johnsen (@phillipj)
+* **lib**: copy arguments object instead of leaking it (Nathan Woltman)
+https://github.com/nodejs/node/pull/4361
+* **src**: allow both -i and -e flags to be used at the same time (Rich Trott)
+https://github.com/nodejs/node/pull/5655
+* **timers**: Internal Node.js timeouts now use the same logic path as those created with `setTimeout()` (Jeremiah Senkpiel) [#4007](https://github.com/nodejs/node/pull/4007)
+  * This may cause a slightly different performance profile in some situations. So far, it has shown to be positive in most cases.
+* **v8**: backport fb4ccae from v8 upstream (Vladimir Krivosheev) #4231
+  -  breakout events from v8 to offer better support for external debuggers
+* **zlib**: add support for concatenated members (Kári Tristan Helgason)
+https://github.com/nodejs/node/pull/5120
+  * Previously, if multiple members were in the same archive, only the first would be read. The others are no longer thrown away.
+
+### Commits
+
+* [[`03b99bf8b9`](https://github.com/nodejs/node/commit/03b99bf8b9)] - **build**: don't install github templates (Johan Bergström) [#5612](https://github.com/nodejs/node/pull/5612)
+* [[`a7819da15a`](https://github.com/nodejs/node/commit/a7819da15a)] - ***Revert*** "**build**: run lint before tests" (Rich Trott) [#5602](https://github.com/nodejs/node/pull/5602)
+* [[`5e9cac4333`](https://github.com/nodejs/node/commit/5e9cac4333)] - **console**: check that stderr is writable (Rich Trott) [#5635](https://github.com/nodejs/node/pull/5635)
+* [[`0662fcf209`](https://github.com/nodejs/node/commit/0662fcf209)] - **contextify**: cache sandbox and context in locals (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`4f2c839d46`](https://github.com/nodejs/node/commit/4f2c839d46)] - **contextify**: replace deprecated SetWeak usage (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`bfff07b4dd`](https://github.com/nodejs/node/commit/bfff07b4dd)] - **contextify**: cleanup weak ref for sandbox (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`93f60cdc54`](https://github.com/nodejs/node/commit/93f60cdc54)] - **contextify**: cleanup weak ref for global proxy (Ali Ijaz Sheikh) [#5392](https://github.com/nodejs/node/pull/5392)
+* [[`b6c355de0d`](https://github.com/nodejs/node/commit/b6c355de0d)] - **(SEMVER-MINOR)** **deps**: backport fb4ccae from v8 upstream (develar) [#4231](https://github.com/nodejs/node/pull/4231)
+* [[`29510aa4fd`](https://github.com/nodejs/node/commit/29510aa4fd)] - **deps**: update openssl config (Shigeki Ohtsu) [#5630](https://github.com/nodejs/node/pull/5630)
+* [[`532d1bf9ce`](https://github.com/nodejs/node/commit/532d1bf9ce)] - **deps**: sync deps/http_parser with nodejs/http_parser (James M Snell) [#5600](https://github.com/nodejs/node/pull/5600)
+* [[`d5d64c327b`](https://github.com/nodejs/node/commit/d5d64c327b)] - **doc**: clarify commit message rules (Wyatt Preul) [#5661](https://github.com/nodejs/node/pull/5661)
+* [[`8c4c84fe5b`](https://github.com/nodejs/node/commit/8c4c84fe5b)] - **doc**: add Testing WG (Rich Trott) [#5461](https://github.com/nodejs/node/pull/5461)
+* [[`434af03825`](https://github.com/nodejs/node/commit/434af03825)] - **doc**: Add note about use of JSON.stringify() (Mithun Patel) [#5723](https://github.com/nodejs/node/pull/5723)
+* [[`62926d85bd`](https://github.com/nodejs/node/commit/62926d85bd)] - **doc**: clarify type of first argument in zlib (Kirill Fomichev) [#5685](https://github.com/nodejs/node/pull/5685)
+* [[`eb73574349`](https://github.com/nodejs/node/commit/eb73574349)] - **doc**: clarify when writable.write callback is called (Kevin Locke) [#4810](https://github.com/nodejs/node/pull/4810)
+* [[`c579507034`](https://github.com/nodejs/node/commit/c579507034)] - **doc**: fix typo in api/addons (Daijiro Wachi) [#5678](https://github.com/nodejs/node/pull/5678)
+* [[`8e45c9d9ea`](https://github.com/nodejs/node/commit/8e45c9d9ea)] - **doc**: fix typo in api/dgram (Daijiro Wachi) [#5678](https://github.com/nodejs/node/pull/5678)
+* [[`44a9b100c5`](https://github.com/nodejs/node/commit/44a9b100c5)] - **doc**: fix typo in api/fs (Daijiro Wachi) [#5678](https://github.com/nodejs/node/pull/5678)
+* [[`b667573bcb`](https://github.com/nodejs/node/commit/b667573bcb)] - **doc**: update fansworld-claudio username on README (Claudio Rodriguez) [#5680](https://github.com/nodejs/node/pull/5680)
+* [[`9794abb5d1`](https://github.com/nodejs/node/commit/9794abb5d1)] - **doc**: add onboarding resources (Jeremiah Senkpiel) [#3726](https://github.com/nodejs/node/pull/3726)
+* [[`31e39fbd7a`](https://github.com/nodejs/node/commit/31e39fbd7a)] - **doc**: remove non-standard use of hyphens (Stefano Vozza)
+* [[`f3e9daa825`](https://github.com/nodejs/node/commit/f3e9daa825)] - **doc**: add clarification on birthtime in fs stat (Kári Tristan Helgason) [#5479](https://github.com/nodejs/node/pull/5479)
+* [[`c379ec6522`](https://github.com/nodejs/node/commit/c379ec6522)] - **doc**: move build instructions to a new document (Johan Bergström) [#5634](https://github.com/nodejs/node/pull/5634)
+* [[`2a442b3dfc`](https://github.com/nodejs/node/commit/2a442b3dfc)] - **doc**: update removeListener behaviour (Vaibhav) [#5201](https://github.com/nodejs/node/pull/5201)
+* [[`f6ee0996e0`](https://github.com/nodejs/node/commit/f6ee0996e0)] - **doc**: fix typo in child_process docs (Benjamin Gruenbaum) [#5681](https://github.com/nodejs/node/pull/5681)
+* [[`dd12661173`](https://github.com/nodejs/node/commit/dd12661173)] - **doc**: include typo in 'unhandledRejection' example (Robert C Jensen) [#5654](https://github.com/nodejs/node/pull/5654)
+* [[`f7aecd6e94`](https://github.com/nodejs/node/commit/f7aecd6e94)] - **doc**: add thekemkid to collaborators (Glen Keane) [#5667](https://github.com/nodejs/node/pull/5667)
+* [[`b81711acfb`](https://github.com/nodejs/node/commit/b81711acfb)] - **doc**: add phillipj to collaborators (Phillip Johnsen) [#5663](https://github.com/nodejs/node/pull/5663)
+* [[`a33f2486f0`](https://github.com/nodejs/node/commit/a33f2486f0)] - **doc**: add fansworld-claudio to collaborators (Claudio Rodriguez) [#5668](https://github.com/nodejs/node/pull/5668)
+* [[`285d5e7ba6`](https://github.com/nodejs/node/commit/285d5e7ba6)] - **doc**: add AndreasMadsen to collaborators (Andreas Madsen) [#5666](https://github.com/nodejs/node/pull/5666)
+* [[`8e1f6706e3`](https://github.com/nodejs/node/commit/8e1f6706e3)] - **doc**: add benjamingr to collaborator list (Benjamin Gruenbaum) [#5664](https://github.com/nodejs/node/pull/5664)
+* [[`f7842cbb24`](https://github.com/nodejs/node/commit/f7842cbb24)] - **doc**: add whitlockjc to collaborators (Jeremy Whitlock) [#5665](https://github.com/nodejs/node/pull/5665)
+* [[`dd6f4ec2e4`](https://github.com/nodejs/node/commit/dd6f4ec2e4)] - **doc**: add mattloring to collaborators (Matt Loring) [#5662](https://github.com/nodejs/node/pull/5662)
+* [[`9ebd559a55`](https://github.com/nodejs/node/commit/9ebd559a55)] - **doc**: fix markdown links (Steve Mao) [#5641](https://github.com/nodejs/node/pull/5641)
+* [[`62d267e1ff`](https://github.com/nodejs/node/commit/62d267e1ff)] - **doc**: fix dns.resolveCname description typo (axvm) [#5622](https://github.com/nodejs/node/pull/5622)
+* [[`9f8e2e2979`](https://github.com/nodejs/node/commit/9f8e2e2979)] - **doc**: update release tweet template (Jeremiah Senkpiel) [#5628](https://github.com/nodejs/node/pull/5628)
+* [[`4d6fe300fe`](https://github.com/nodejs/node/commit/4d6fe300fe)] - **doc**: fix v5.8.0 changelog heading (Jeremiah Senkpiel) [#5559](https://github.com/nodejs/node/pull/5559)
+* [[`4c1fdaeb2a`](https://github.com/nodejs/node/commit/4c1fdaeb2a)] - **docs**: update link to iojs+release ci job (Myles Borins) [#5632](https://github.com/nodejs/node/pull/5632)
+* [[`205bed0bec`](https://github.com/nodejs/node/commit/205bed0bec)] - **lib**: copy arguments object instead of leaking it (Nathan Woltman) [#4361](https://github.com/nodejs/node/pull/4361)
+* [[`b16f67a0b9`](https://github.com/nodejs/node/commit/b16f67a0b9)] - **net**: make `isIPv4` and `isIPv6` more efficient (Vladimir Kurchatkin) [#5478](https://github.com/nodejs/node/pull/5478)
+* [[`4ecd996baa`](https://github.com/nodejs/node/commit/4ecd996baa)] - **(SEMVER-MINOR)** **src**: allow combination of -i and -e cli flags (Rich Trott) [#5655](https://github.com/nodejs/node/pull/5655)
+* [[`f225459496`](https://github.com/nodejs/node/commit/f225459496)] - **test**: improve test-npm-install (Santiago Gimeno) [#5613](https://github.com/nodejs/node/pull/5613)
+* [[`cceae5ae78`](https://github.com/nodejs/node/commit/cceae5ae78)] - **test**: eval a strict function (Kári Tristan Helgason) [#5250](https://github.com/nodejs/node/pull/5250)
+* [[`9a44c8c337`](https://github.com/nodejs/node/commit/9a44c8c337)] - **test**: add batch of known issue tests (cjihrig) [#5653](https://github.com/nodejs/node/pull/5653)
+* [[`1b7b1ed2c9`](https://github.com/nodejs/node/commit/1b7b1ed2c9)] - **timers**: greatly improve code comments (Jeremiah Senkpiel) [#4007](https://github.com/nodejs/node/pull/4007)
+* [[`769254b0ba`](https://github.com/nodejs/node/commit/769254b0ba)] - **timers**: refactor timers (Jeremiah Senkpiel) [#4007](https://github.com/nodejs/node/pull/4007)
+* [[`0b545fb3f8`](https://github.com/nodejs/node/commit/0b545fb3f8)] - **win,build**: support Visual C++ Build Tools 2015 (João Reis) [#5627](https://github.com/nodejs/node/pull/5627)
+* [[`ef774ff9a8`](https://github.com/nodejs/node/commit/ef774ff9a8)] - **(SEMVER-MINOR)** **zlib**: add support for concatenated members (Kári Tristan Helgason) [#5120](https://github.com/nodejs/node/pull/5120)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.9.0/node-v5.9.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.9.0/node-v5.9.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.9.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.9.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.9.0/node-v5.9.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.9.0/node-v5.9.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.9.0/node-v5.9.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.9.0/<br>
+Documentation: https://nodejs.org/docs/v5.9.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+6417022026c30cfb1b8af92f1434c1b202548076ada636708e1874d8af78197b  node-v5.9.0-darwin-x64.tar.gz
+df58c7ec89849a0752f75b9a2e00c7c943089011d7c636920a1e1267d91671c0  node-v5.9.0-darwin-x64.tar.xz
+546c6b43f193ad57638cadded1eb5ee4630b585f4f966e228cd2ae06f44b6c76  node-v5.9.0-headers.tar.gz
+e77ceab9d39bf1086ca12214397a7dd4d2141b8aecbb86f95e60ee369c94445c  node-v5.9.0-headers.tar.xz
+8ce0653a98a7507dc15bd7425154af1113685d054b6dee2c9701fed401feb12a  node-v5.9.0-linux-arm64.tar.gz
+2b8b875022906ed5beabb90de8cc16979f85fba76930c192b80fafd2e72c8831  node-v5.9.0-linux-arm64.tar.xz
+a69cc76e388b44a4c6de8007e0fad67f1308b32284894b4c483180c4aaf10cb4  node-v5.9.0-linux-armv6l.tar.gz
+7f48846c39208ddeff0c3756378c71abf36f4910b3424f870c1e4f0c06e7c907  node-v5.9.0-linux-armv6l.tar.xz
+b7ac2bf673eed236ac636d755874d90aa3563b55caed84730c8342cbdffc4ce3  node-v5.9.0-linux-armv7l.tar.gz
+2cf5136d0342eeb833b0a24588f04d89387925149031886cd2d65ba29bed4388  node-v5.9.0-linux-armv7l.tar.xz
+a2996dc3323579f2d9f306cb91a21a9ed6ec534791003eeed3e9114a0a1b27dd  node-v5.9.0-linux-ppc64le.tar.gz
+45696542c11e0215e39f1a1f8c11246f93dd4b2ea00d1a77edff97646e8d849e  node-v5.9.0-linux-ppc64le.tar.xz
+99c4136cf61761fac5ac57f80544140a3793b63e00a65d4a0e528c9db328bf40  node-v5.9.0-linux-x64.tar.gz
+fc8e01886b0c4ce656163cd5c2d98fb624844243ea0c9fa9fb7114926dff541a  node-v5.9.0-linux-x64.tar.xz
+fca2df390ff964951cc2d18150d17dfe474e5b59864415976b8bad9452f725eb  node-v5.9.0-linux-x86.tar.gz
+43b0564c86812e629c6ede7316cf49e1b0a5e61d04f4e5dd2bc600c3265b4352  node-v5.9.0-linux-x86.tar.xz
+64f0c8b3ba981c1b6569c993423956e7b2d1ee18f982bca88a85b9f445742010  node-v5.9.0.pkg
+47a45169838b74f62c0dbb31643af2f2c2e86bae0920d030113b3aeb0f29275b  node-v5.9.0-sunos-x64.tar.gz
+f2175f16307b458256d3b4c482c643e9487217e9e2a93cf949284526cae62bed  node-v5.9.0-sunos-x64.tar.xz
+835f6d8ec09df20f5280851da0eec44f97d64a2f163a213efe2eac668d0a852a  node-v5.9.0-sunos-x86.tar.gz
+0b0a97caf81901f00a463f83d31a0ea18e4661c0ad486afcff2687f135e5acc9  node-v5.9.0-sunos-x86.tar.xz
+e5175a66481fd9389ef74ef8e8c164d052f139664deffc9e79241d6234760f3e  node-v5.9.0.tar.gz
+9bdf2f8e44a721df459dfad0072a8ac46f11c05d25fc33dc0dc9c522827e34bb  node-v5.9.0.tar.xz
+f53fac35122dfaec568f998fc210d4ead423c7939c024cd51e240879efd6845b  node-v5.9.0-x64.msi
+38e74ba6feced696f5c3de1b12fb5b2f18839abe8e177d895cf5e5436d1362be  node-v5.9.0-x86.msi
+ded3eb5f3e08831d7fc020dd86232ea11400468e3303355a03fa167175ab26b1  win-x64/node.exe
+44e93b651d6b329143d5b708784cd99587e258790cf14f81abdd8cef3cedb422  win-x64/node.lib
+279b6fe04661a6c9430b01535664d0e85998a74ff4c7c76804dfc318a201050a  win-x86/node.exe
+82feb73750de3086db7fea6b933596d45a24019db4eb6f1e424e1036a1929be1  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJW6dEeAAoJELY7U1pMIGypIUMP/1DawXNIxOw67Q/IEU9AUVQi
+Z7laXU8RKewNbr6pGJ+E8Ionr6on5GBujyuFh/Z05t3zZ8vy/ffUfPpxoe+KluF9
+/LafmG0VHDWyL95ZBlLMcQHT7ucoLxRKr444t5VNScwGwrcAFVhUfh9TR/7n+4qe
+TgHPnfVVan9BIPE3l9tYQMoOcDApJTseXhmBBvk1MpXk2/lwEjC9O9idm7ewqmyL
+fZ+gTtEFeLlqpjwoPUmd3Wedpjlezxa2ha2fJY0S7wle9tkbTWPoHSpOUbcDW5UH
+bhRXR6BgCdcuQKwDoXSQKCDaHDQbKCuxGxox6UmPGBs8iKLZ44CDw5T9LEH9T9vo
+KZV8biGRS3ELHLmREcAJtp+wktrv86F/7ylRiQSQ/GmGCxKqtTh3XoE8M2FI3GPd
+vaYpDFz9j75ujpf4PVWiov0uZBnBWia1vjYmW4XezbztmjyjasqfpOgj9+W1+EV+
+351gep52CmRZl0ZbBlgrfybUiKGn43w7COewAljfISs2f4wa3kq8r+hefSFZ5Gkq
+ZRXJ1SVzuCayLskImfGfIPe0TuFnrunPM+CI2gdHIDqM0W4jHeDtaPmEd42f4LQ3
+AB5Ee1GwHlnpPkCO6f+UsLz+UbbcK+AMgddnRn1ieA8wFL4FIl/XMtOqbEps+ZZq
+K+iBWxsEuGMFBw3heC8s
+=9sLm
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v5.9.1.md b/locale/uk/blog/release/v5.9.1.md
new file mode 100755
index 0000000000000..1b43146f50e32
--- /dev/null
+++ b/locale/uk/blog/release/v5.9.1.md
@@ -0,0 +1,137 @@
+---
+date: 2016-03-23T17:40:02.432Z
+version: 5.9.1
+category: release
+title: Node v5.9.1 (Current)
+slug: node-v5-9-1
+layout: blog-post.hbs
+author: Jeremiah Senkpiel
+---
+
+### Notable changes
+
+* **buffer**: Now properly throws `RangeError`s on out-of-bounds writes (Matt Loring) [#5605](https://github.com/nodejs/node/pull/5605).
+  - This effects `write{Float|Double}` when the `noAssert` option is not used.
+* **timers**:
+  - Returned timeout objects now have a `Timeout` constructor name (Jeremiah Senkpiel) [#5793](https://github.com/nodejs/node/pull/5793).
+  - Performance of `Immediate` processing is now ~20-40% faster (Brian White) [#4169](https://github.com/nodejs/node/pull/4169).
+* **vm**: Fixed a contextify regression introduced in v5.9.0 (Ali Ijaz Sheikh) [#5800](https://github.com/nodejs/node/pull/5800).
+
+### Commits
+
+* [[`341b3d01c8`](https://github.com/nodejs/node/commit/341b3d01c8)] - **benchmark**: fix linting errors (Rich Trott) [#5840](https://github.com/nodejs/node/pull/5840)
+* [[`72fb796bed`](https://github.com/nodejs/node/commit/72fb796bed)] - **buffer**: throw range error before truncating write (Matt Loring) [#5605](https://github.com/nodejs/node/pull/5605)
+* [[`c5d83695e1`](https://github.com/nodejs/node/commit/c5d83695e1)] - **contextify**: tie lifetimes of context & sandbox (Ali Ijaz Sheikh) [#5800](https://github.com/nodejs/node/pull/5800)
+* [[`ae24d05451`](https://github.com/nodejs/node/commit/ae24d05451)] - **deps**: remove unused openssl files (Ben Noordhuis) [#5619](https://github.com/nodejs/node/pull/5619)
+* [[`54abbe7e6f`](https://github.com/nodejs/node/commit/54abbe7e6f)] - **dns**: use template literals (Benjamin Gruenbaum) [#5809](https://github.com/nodejs/node/pull/5809)
+* [[`3fef69bf15`](https://github.com/nodejs/node/commit/3fef69bf15)] - **dns**: use isIp consistently (Benjamin Gruenbaum) [#5804](https://github.com/nodejs/node/pull/5804)
+* [[`d2d0fe9d34`](https://github.com/nodejs/node/commit/d2d0fe9d34)] - **doc**: update crypto docs to use good defaults (Bill Automata) [#5505](https://github.com/nodejs/node/pull/5505)
+* [[`1631f06477`](https://github.com/nodejs/node/commit/1631f06477)] - **doc**: add CTC meeting minutes 2016-02-10 (Rod Vagg) [#5273](https://github.com/nodejs/node/pull/5273)
+* [[`7ab597d646`](https://github.com/nodejs/node/commit/7ab597d646)] - **doc**: add CTC meeting minutes 2016-02-03 (Rod Vagg) [#5272](https://github.com/nodejs/node/pull/5272)
+* [[`e20d0b8802`](https://github.com/nodejs/node/commit/e20d0b8802)] - **doc**: explain error message on missing main file (Wolfgang Steiner) [#5812](https://github.com/nodejs/node/pull/5812)
+* [[`e99082e32d`](https://github.com/nodejs/node/commit/e99082e32d)] - **doc**: add a cli options doc page (Jeremiah Senkpiel) [#5787](https://github.com/nodejs/node/pull/5787)
+* [[`0ffd794b27`](https://github.com/nodejs/node/commit/0ffd794b27)] - **doc**: Add windows example for Path.format (Mithun Patel) [#5700](https://github.com/nodejs/node/pull/5700)
+* [[`f53cc37578`](https://github.com/nodejs/node/commit/f53cc37578)] - **doc**: grammar, clarity and links in timers doc (Bryan English) [#5792](https://github.com/nodejs/node/pull/5792)
+* [[`3ada8cc09a`](https://github.com/nodejs/node/commit/3ada8cc09a)] - **doc**: align doc/api/tls.markdown with style guide (Stefano Vozza) [#5706](https://github.com/nodejs/node/pull/5706)
+* [[`5d28ce3942`](https://github.com/nodejs/node/commit/5d28ce3942)] - **doc**: topic blocking vs non-blocking (Jarrett Widman) [#5326](https://github.com/nodejs/node/pull/5326)
+* [[`d9b4e15f75`](https://github.com/nodejs/node/commit/d9b4e15f75)] - **doc**: fix typo in synchronous randomBytes example (Andrea Giammarchi) [#5781](https://github.com/nodejs/node/pull/5781)
+* [[`d8318c2226`](https://github.com/nodejs/node/commit/d8318c2226)] - **doc**: fix crypto update() signatures (Brian White) [#5500](https://github.com/nodejs/node/pull/5500)
+* [[`15c5662959`](https://github.com/nodejs/node/commit/15c5662959)] - **doc**: fix multiline return comments in querystring (Claudio Rodriguez) [#5705](https://github.com/nodejs/node/pull/5705)
+* [[`75f723c0aa`](https://github.com/nodejs/node/commit/75f723c0aa)] - **doc**: fix invalid path doc comments (Rich Trott) [#5670](https://github.com/nodejs/node/pull/5670)
+* [[`724b87d75c`](https://github.com/nodejs/node/commit/724b87d75c)] - **doc**: explain path.format() algorithm (Rich Trott) [#5688](https://github.com/nodejs/node/pull/5688)
+* [[`89df17ed0b`](https://github.com/nodejs/node/commit/89df17ed0b)] - **doc**: fix return value of write methods (Felix Böhm) [#5736](https://github.com/nodejs/node/pull/5736)
+* [[`5ab51ee151`](https://github.com/nodejs/node/commit/5ab51ee151)] - **doc**: reformat & improve node.1 manual page (Jeremiah Senkpiel) [#5497](https://github.com/nodejs/node/pull/5497)
+* [[`f34a00cee2`](https://github.com/nodejs/node/commit/f34a00cee2)] - **docs**: fix man pages link if tok type is code (Mithun Patel) [#5721](https://github.com/nodejs/node/pull/5721)
+* [[`3bff3111f4`](https://github.com/nodejs/node/commit/3bff3111f4)] - **https**: fix ssl socket leak when keepalive is used (Alexander Penev) [#5713](https://github.com/nodejs/node/pull/5713)
+* [[`7b21c09b73`](https://github.com/nodejs/node/commit/7b21c09b73)] - **lib**: simplify code with String.prototype.repeat() (Jackson Tian) [#5359](https://github.com/nodejs/node/pull/5359)
+* [[`c75f97f43b`](https://github.com/nodejs/node/commit/c75f97f43b)] - **lib**: reduce usage of `self = this` (Jackson Tian) [#5231](https://github.com/nodejs/node/pull/5231)
+* [[`1ccf9b4a56`](https://github.com/nodejs/node/commit/1ccf9b4a56)] - **net**: remove unused `var self = this` from old code (Benjamin Gruenbaum) [#5224](https://github.com/nodejs/node/pull/5224)
+* [[`6e5835b8cd`](https://github.com/nodejs/node/commit/6e5835b8cd)] - **path**: refactor path.format() repeated code (Rich Trott) [#5673](https://github.com/nodejs/node/pull/5673)
+* [[`15c7b3a127`](https://github.com/nodejs/node/commit/15c7b3a127)] - **src,tools**: use template literals (Rich Trott) [#5778](https://github.com/nodejs/node/pull/5778)
+* [[`ca971b0d77`](https://github.com/nodejs/node/commit/ca971b0d77)] - **test**: smaller chunk size for smaller person.jpg (Jérémy Lal) [#5813](https://github.com/nodejs/node/pull/5813)
+* [[`f95fc175eb`](https://github.com/nodejs/node/commit/f95fc175eb)] - **test**: strip non-free icc profile from person.jpg (Jérémy Lal) [#5813](https://github.com/nodejs/node/pull/5813)
+* [[`7c2c7b0577`](https://github.com/nodejs/node/commit/7c2c7b0577)] - **test**: remove timer from test-http-1.0 (Santiago Gimeno) [#5129](https://github.com/nodejs/node/pull/5129)
+* [[`70512e51a4`](https://github.com/nodejs/node/commit/70512e51a4)] - **test**: repl tab completion test (Santiago Gimeno) [#5534](https://github.com/nodejs/node/pull/5534)
+* [[`89f091d621`](https://github.com/nodejs/node/commit/89f091d621)] - **test**: make test-net-connect-options-ipv6.js better (Michael Dawson) [#5791](https://github.com/nodejs/node/pull/5791)
+* [[`d2fa64490f`](https://github.com/nodejs/node/commit/d2fa64490f)] - **test**: fix `test-cluster-worker-kill` (Santiago Gimeno) [#5814](https://github.com/nodejs/node/pull/5814)
+* [[`f0d885a0a9`](https://github.com/nodejs/node/commit/f0d885a0a9)] - **test**: fix flaky test-cluster-shared-leak (Claudio Rodriguez) [#5802](https://github.com/nodejs/node/pull/5802)
+* [[`b352cc7db4`](https://github.com/nodejs/node/commit/b352cc7db4)] - **test**: minimize test-http-get-pipeline-problem (Rich Trott) [#5728](https://github.com/nodejs/node/pull/5728)
+* [[`21770c3806`](https://github.com/nodejs/node/commit/21770c3806)] - **test**: reduce brittleness of tab complete test (Matt Loring) [#5772](https://github.com/nodejs/node/pull/5772)
+* [[`46f0e02620`](https://github.com/nodejs/node/commit/46f0e02620)] - **timers**: fix lint from 4fe02e2 (Jeremiah Senkpiel) [#5825](https://github.com/nodejs/node/pull/5825)
+* [[`20a68e9eef`](https://github.com/nodejs/node/commit/20a68e9eef)] - **timers**: give Timeouts a constructor name (Jeremiah Senkpiel) [#5793](https://github.com/nodejs/node/pull/5793)
+* [[`d3654d80f3`](https://github.com/nodejs/node/commit/d3654d80f3)] - **timers**: improve setImmediate() performance (Brian White) [#4169](https://github.com/nodejs/node/pull/4169)
+* [[`b1a4870200`](https://github.com/nodejs/node/commit/b1a4870200)] - **tools**: remove unused imports (Sakthipriyan Vairamani) [#5765](https://github.com/nodejs/node/pull/5765)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v5.9.1/node-v5.9.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v5.9.1/node-v5.9.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v5.9.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v5.9.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v5.9.1/node-v5.9.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v5.9.1/node-v5.9.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v5.9.1/<br>
+Documentation: https://nodejs.org/docs/v5.9.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+90dbbd2072582f0373a738114131112f3f8a2c7f7f64bbf4991a51d2808d4935  node-v5.9.1-darwin-x64.tar.gz
+5e27117f8aa3d684868ac49e808834eff6242a1af3a166bc5dad4f3b175c6845  node-v5.9.1-darwin-x64.tar.xz
+fb16ac5bb0c49f7b4de6a93744fee638c55165f8fac88157a324dc358ae24cb5  node-v5.9.1-headers.tar.gz
+c79c7d524e47ecc6999bfb2a7243bec55328cae773054eabb0cd169f275f5397  node-v5.9.1-headers.tar.xz
+09fd524d987e3c70aed7aa52d21f6448fe06cdd05c627a6de326384b98a3bb0e  node-v5.9.1-linux-arm64.tar.gz
+ec748da69f8033df4f1106183637c547148604986c672132fac3f32f1f4faeb2  node-v5.9.1-linux-arm64.tar.xz
+755965b20e4fa991072e7bb07937bd3c075b689b10d21161bfb34037dd5c52b9  node-v5.9.1-linux-armv6l.tar.gz
+a5ee262f5ffc7146ac4139a9e2fe12a7670d87dce64b14d8a89e38f68272f1e7  node-v5.9.1-linux-armv6l.tar.xz
+b4a7880a9906175121a40ff8862009bc2bf80ac2bfd5e0e4aab6d9088b52fe21  node-v5.9.1-linux-armv7l.tar.gz
+e6ce828dd85f33b55753ed80e3d9bfc214aff55b37b1bb7ba2bc3a8cdeba3f3a  node-v5.9.1-linux-armv7l.tar.xz
+0211aa951355eddadb07ffae0b945b954df7b8ba72231d75d2a8a09335a8f0a6  node-v5.9.1-linux-ppc64le.tar.gz
+3cc17c63f5a0390fa94353b927b54f25587ffb7792e4c08949338bd0455c11a9  node-v5.9.1-linux-ppc64le.tar.xz
+4b9951e6afd75010f53264fc1a61e2d92ae23a590bbb58fea3e62d6f0104f657  node-v5.9.1-linux-x64.tar.gz
+e8da38196c37c07ba922c569356988e01348f48344619b60dc0a1b99c941a3de  node-v5.9.1-linux-x64.tar.xz
+749eb56ae38ee0cb4ac659d6de50954a4e57bd2796fda6bc75725f7b98f21887  node-v5.9.1-linux-x86.tar.gz
+67d9243af1a5660b2c21e83661dab0f77d2c130cc5d1ffd4eb62e0fae0f6b62b  node-v5.9.1-linux-x86.tar.xz
+d2e4c33f7cc5cc379882906e3df9787a7efaec3d9d4eb4076c12211f546e31a1  node-v5.9.1.pkg
+17feb55c0ca64d1fb57e7aa54d3226d1b72adc3484c276f3ac040891b566325c  node-v5.9.1-sunos-x64.tar.gz
+bd3f22203af80497cb63a6c9c40cd8e317b26c90e83a2b628a083438bf367a14  node-v5.9.1-sunos-x64.tar.xz
+8a430122c7ad4271414d3d5b735277d19abe7fc8a3f7d3789630b58908166740  node-v5.9.1-sunos-x86.tar.gz
+978aac18aa9c03e8dbaffe3de9d5c15bac3b0b4e5a037579bdff6416c3a1250f  node-v5.9.1-sunos-x86.tar.xz
+9bfa882ba832c526add1f939121c79d95b9c592785ec8afe043086a0c7a30c18  node-v5.9.1.tar.gz
+668067077dfceb3d2039d0df693fec6aa20b920d01a42b53dc61d4aa91e0ae55  node-v5.9.1.tar.xz
+3090c58cc46d6068dfa7947f734e146481fbc6699bf34bff658fe4fe5ad4b75f  node-v5.9.1-x64.msi
+73eb560ae88336497ea2e9064b1dc90c336024c652196e48f5f6c5576ab28ea1  node-v5.9.1-x86.msi
+d18c47df465b5a59924817c177e3be432495411d5c5cb6e80fc23c3763f17d66  win-x64/node.exe
+ac7f227c1aff701cf3e57e2af8fb21b3ddfdbab5808ba8e685f9a9bafd6ebebe  win-x64/node.lib
+693a85ac8b474d50b419089e295d56f240827473d102412c1a98edafe243606b  win-x86/node.exe
+8d9ca2f0c61715b8539ce9805977adac8bdd1c1049792ed20302ff6d66339727  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJW8tQZAAoJEEX17r2BPa6OcxgP/0Q1bwH5/ekjnPQK0Mb51s6N
+nMEN6GidmijEY7alAIEQvrfIjMo/UCBZEbfKD6oQPwSRqDLxMzmJJWkusezClPWb
+kTA8mB4fWy5I9gQO/HOuJTBRXTZuPJKlV3SjeZtFg/9v5wAdjYpxFu3t9Gy9ePAK
+pZ9kq67PdLTE2Z25wKqqpPSojR508QEHx6/HH/w/g86FCljkT7hGV1A8t6XZyxtr
+NWWEONv7++MZpFHFMHJ4VVi4+BrwR3POC/P93wt36hgKkJ7cfRwrOra9UmgUCpwW
+Ym9zKTxvswHxvz+X2957n64lJO6eGGALyMYSmVG+ozBl6tNyj+eyWtPPOKhBsUL5
+qMRtAmXm6S3zmGLrSNGw5zvhOvlVLAcxtcgQePLanfMg35RhZSmdbb6+GNVN86hZ
+ZzsdCv44STY+7MBdrZ/yN60eVzN6KTYswxLyTJToGHD4rAdwn/0nVHWAB8gveazV
+o95ppu04DYTKAww16Qng+OmXzf8MP0AnY7ODgH3XgdkWrLGkFrc7Vz6ZWsjRVf6r
+nyNM8l1n0unsQbDCpfmelrb+qhxM3aI1D40QoSyb/Eu19hcaCm0jLhvsYo7vb/bo
+WI6pENg0lvKrV+Odt/rTNbFwnvWzQ811JzlLlaRaQFwnRrY4AYEkvz7y3tlqlCLX
+IPT3xpC/2VQXkv3s2bbC
+=BEhZ
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v6.0.0.md b/locale/uk/blog/release/v6.0.0.md
new file mode 100755
index 0000000000000..1fc46e1191d8d
--- /dev/null
+++ b/locale/uk/blog/release/v6.0.0.md
@@ -0,0 +1,374 @@
+---
+date: 2016-04-26T20:35:53.135Z
+version: 6.0.0
+category: release
+title: Node v6.0.0 (Current)
+slug: node-v6-0-0
+layout: blog-post.hbs
+author: James M Snell
+---
+It's here! Just three days shy of exactly six months after we released v5.0.0, the Node.js Foundation is happy to announce that Node.js v6 is available and ready for use! 
+
+This new major version of Node.js delivers significant improvements in performance, reliability, usability and security. Module loading is nearly four times faster than in Node.js v4, tests and documentation have seen significant improvements, usability of the Buffer and File System APIs have been improved, and Node.js now supports [93% of ES6 language features](http://node.green), thanks to V8 version 5.0.
+
+In accordance with our [Long Term Support plan](https://github.com/nodejs/LTS/), Node.js v4 'Argon' will continue to be supported as an *Active* Long Term Support stream until April of 2017, after which it will transition into what we call *Maintenance* LTS. The new Node.js v6 branch will become the new *Active* Long Term Support stream in October of this year, and will continue to be supported actively until April of 2018. If our LTS plan is new to you, [read more](https://medium.com/@nodesource/essential-steps-long-term-support-for-node-js-8ecf7514dbd#.z6bzdfogi) about how it works so that you can make a properly informed decision regarding which version of Node.js to adopt.
+
+The general rule for deciding which version of Node.js to use is:
+
+* Stay on or upgrade to Node.js v4 (currently at v4.4.3) if you need stability and have a complex production environment.
+* Upgrade to Node.js v6 if you have the ability to upgrade versions quickly and want to play with the latest features as they arrive.
+
+Note that while v6 will eventually transition into LTS, until it does, we will still be actively landing new features (semver-minor). This means that there is an increased chance for regressions to be introduced..
+
+The release notes below are annotated with the main breaking changes that warrant the jump to v6. Note that because this new version of Node.js is shipping with a new version of V8, you will need to recompile any native addons you have already installed or you will receive a runtime error when trying to load them. Use `npm rebuild` or simply remove your *node_modules* directory and `npm install` from scratch.
+
+### What about Node.js v5?
+
+Node.js v5 will continue to be supported for the next two months in order to give developers currently using v5 time to transition to Node.js v6.
+
+### What about Node.js v0.10 and v0.12?
+
+If you're still currently using Node.js v0.10 or v0.12, it is time to begin the transition to v4 or v6. Both v0.10 and v0.12 are considered to be in *Maintenance* mode currently and will fall off our support plan completely later this year.
+
+### Current? What happened to Stable?
+
+You may have noticed that the v6 release uses the label `Current` instead of `Stable`. This name change has been made in order to better differentiate the Long Term Support releases from the current active development branches. We
+will be using the `Current` label from here-on instead of `Stable`.
+
+### Notable changes
+
+The following significant changes have been made since the previous Node.js
+v5.0.0 release.
+
+* Buffer
+  * New Buffer constructors have been added
+    [#4682](https://github.com/nodejs/node/pull/4682) and
+    [#5833](https://github.com/nodejs/node/pull/5833).
+  * Existing `Buffer()` and `SlowBuffer()` constructors have been deprecated
+    in docs [#4682](https://github.com/nodejs/node/pull/4682) and
+    [#5833](https://github.com/nodejs/node/pull/5833).
+  * Previously deprecated Buffer APIs are removed
+    [#5048](https://github.com/nodejs/node/pull/5048),
+    [#4594](https://github.com/nodejs/node/pull/4594).
+  * Improved error handling [#4514](https://github.com/nodejs/node/pull/4514).
+  * The `Buffer.prototype.lastIndexOf()` method has been added
+    [#4846](https://github.com/nodejs/node/pull/4846).
+* Cluster
+  * Worker emitted as first argument in 'message' event
+    [#5361](https://github.com/nodejs/node/pull/5361).
+  * The `worker.exitedAfterDisconnect` property replaces `worker.suicide`
+    [#3743](https://github.com/nodejs/node/pull/3743).
+* Console
+  * Calling `console.timeEnd()` with an unknown label now emits a process
+    warning rather than throwing
+    [#5901](https://github.com/nodejs/node/pull/5901).
+* Crypto
+  * Improved error handling [#3100](https://github.com/nodejs/node/pull/3100),
+    [#5611](https://github.com/nodejs/node/pull/5611).
+  * Simplified Certificate class bindings
+    [#5382](https://github.com/nodejs/node/pull/5382).
+  * Improved control over FIPS mode
+    [#5181](https://github.com/nodejs/node/pull/5181).
+  * pbkdf2 digest overloading is deprecated
+    [#4047](https://github.com/nodejs/node/pull/4047).
+* Dependencies
+  * Reintroduce shared c-ares build support
+    [#5775](https://github.com/nodejs/node/pull/5775).
+  * V8 updated to 5.0.71.35 [#6372](https://github.com/nodejs/node/pull/6372).
+* DNS
+  * Add `dns.resolvePtr()` API to query plain DNS PTR records
+    [#4921](https://github.com/nodejs/node/pull/4921).
+* Domains
+  * Clear stack when no error handler
+  [#4659](https://github.com/nodejs/node/pull/4659).
+* Events
+  * The `EventEmitter.prototype._events` object no longer inherits from
+    Object.prototype [#6092](https://github.com/nodejs/node/pull/6092).
+  * The `EventEmitter.prototype.prependListener()` and
+    `EventEmitter.prototype.prependOnceListener()` methods have been added
+    [#6032](https://github.com/nodejs/node/pull/6032).
+* File System
+  * The `fs.realpath()` and `fs.realpathSync()` methods have been updated
+    to use a more efficient libuv-based implementation. This change includes
+    the removal of the `cache` argument and the method can throw new errors
+    [#3594](https://github.com/nodejs/node/pull/3594).
+  * FS apis can now accept and return paths as Buffers
+    [#5616](https://github.com/nodejs/node/pull/5616).
+  * Error handling and type checking improvements
+    [#5616](https://github.com/nodejs/node/pull/5616),
+    [#5590](https://github.com/nodejs/node/pull/5590),
+    [#4518](https://github.com/nodejs/node/pull/4518),
+    [#3917](https://github.com/nodejs/node/pull/3917).
+  * fs.read's string interface is deprecated
+    [#4525](https://github.com/nodejs/node/pull/4525).
+* HTTP
+  * 'clientError' can now be used to return custom errors from an
+    HTTP server [#4557](https://github.com/nodejs/node/pull/4557).
+* Modules
+  * Current directory is now prioritized for local lookups
+    [#5689](https://github.com/nodejs/node/pull/5689).
+  * Symbolic links are preserved when requiring modules
+    [#5950](https://github.com/nodejs/node/pull/5950).
+* Net
+  * DNS hints no longer implicitly set
+    [#6021](https://github.com/nodejs/node/pull/6021).
+  * Improved error handling and type checking
+    [#5981](https://github.com/nodejs/node/pull/5981),
+    [#5733](https://github.com/nodejs/node/pull/5733),
+    [#2904](https://github.com/nodejs/node/pull/2904).
+* OS X
+  * MACOSX_DEPLOYMENT_TARGET has been bumped up to 10.7
+    [#6402](https://github.com/nodejs/node/pull/6402).
+* Path
+  * Improved type checking [#5348](https://github.com/nodejs/node/pull/5348).
+* Process
+  * Introduce process warnings API
+    [#4782](https://github.com/nodejs/node/pull/4782).
+  * Throw exception when non-function passed to nextTick
+    [#3860](https://github.com/nodejs/node/pull/3860).
+* Querystring
+  * The object returned by `querystring.parse()` no longer inherits from
+    Object.prototype [#6055](https://github.com/nodejs/node/pull/6055).
+* Readline
+  * Key info is emitted unconditionally
+    [#6024](https://github.com/nodejs/node/pull/6024).
+  * History can now be explicitly disabled
+    [#6352](https://github.com/nodejs/node/pull/6352).
+* REPL
+  * Assignment to `_` will emit a warning
+    [#5535](https://github.com/nodejs/node/pull/5535).
+  * Expressions will no longer be completed when eval fails
+    [#6328](https://github.com/nodejs/node/pull/6328).
+* Timers
+  * Fail early when callback is not a function
+    [#4362](https://github.com/nodejs/node/pull/4362).
+* Streams
+  * `null` is now an invalid chunk to write in object mode
+    [#6170](https://github.com/nodejs/node/pull/6170).
+* TLS
+  * Rename 'clientError' to 'tlsClientError'
+    [#4557](https://github.com/nodejs/node/pull/4557).
+  * SHA1 used for sessionIdContext
+    [#3866](https://github.com/nodejs/node/pull/3866).
+* TTY
+  * Previously deprecated setRawMode wrapper is removed
+    [#2528](https://github.com/nodejs/node/pull/2528).
+* URL
+  * Username and password will be dropped by `url.resolve()` if the host
+    changes [#1480](https://github.com/nodejs/node/pull/1480).
+* Util
+  * Changes to Error object formatting
+    [#4582](https://github.com/nodejs/node/pull/4582).
+  * The `util._extend()` method has been deprecated
+    [#4903](https://github.com/nodejs/node/pull/4903)
+  * The `util.log()` method has been deprecated
+    [#6161](https://github.com/nodejs/node/pull/6161).
+* Windows
+  * Windows XP and Vista are no longer supported
+    [#5167](https://github.com/nodejs/node/pull/5167).
+* Zlib
+  * Multiple improvements have been made to Zlib processing
+    [#5883](https://github.com/nodejs/node/pull/5883) and
+    [#5707](https://github.com/nodejs/node/pull/5707).
+
+
+### Commits
+
+Semver-major Changes since v5.0.0
+
+* [[`85ab4a5f12`](https://github.com/nodejs/node/commit/85ab4a5f12)] - **(SEMVER-MAJOR)** **buffer**: add .from(), .alloc() and .allocUnsafe() (James M Snell) [#4682](https://github.com/nodejs/node/pull/4682)
+* [[`2c55cc2d2c`](https://github.com/nodejs/node/commit/2c55cc2d2c)] - **(SEMVER-MAJOR)** **buffer**: remove deprecated Buffer.write branch (dcposch@dcpos.ch) [#5048](https://github.com/nodejs/node/pull/5048)
+* [[`101bca988c`](https://github.com/nodejs/node/commit/101bca988c)] - **(SEMVER-MAJOR)** **buffer**: remove deprecated buffer.get/.set methods (Feross Aboukhadijeh) [#4594](https://github.com/nodejs/node/pull/4594)
+* [[`3b27dd5ce1`](https://github.com/nodejs/node/commit/3b27dd5ce1)] - **(SEMVER-MAJOR)** **buffer**: throw if both length and enc are passed (Mathias Buus) [#4514](https://github.com/nodejs/node/pull/4514)
+* [[`3fe204c700`](https://github.com/nodejs/node/commit/3fe204c700)] - **(SEMVER-MAJOR)** **buffer**: docs-only deprecate SlowBuffer (James M Snell) [#5833](https://github.com/nodejs/node/pull/5833)
+* [[`627524973a`](https://github.com/nodejs/node/commit/627524973a)] - **(SEMVER-MAJOR)** **buffer**: add Buffer.allocUnsafeSlow(size) (James M Snell) [#5833](https://github.com/nodejs/node/pull/5833)
+* [[`204f3a8a0b`](https://github.com/nodejs/node/commit/204f3a8a0b)] - **(SEMVER-MAJOR)** **build**: Bump MACOSX_DEPLOYMENT_TARGET to 10.7 (Сковорода Никита Андреевич) [#6402](https://github.com/nodejs/node/pull/6402)
+* [[`90a5fc20be`](https://github.com/nodejs/node/commit/90a5fc20be)] - **(SEMVER-MAJOR)** **build**: remove lint/dotfiles from release tarball (Johan Bergström) [#5695](https://github.com/nodejs/node/pull/5695)
+* [[`66f4586dd0`](https://github.com/nodejs/node/commit/66f4586dd0)] - **(SEMVER-MAJOR)** **cluster**: emit worker as first 'message' event arg (Ben Noordhuis) [#5361](https://github.com/nodejs/node/pull/5361)
+* [[`4f619bde4c`](https://github.com/nodejs/node/commit/4f619bde4c)] - **(SEMVER-MAJOR)** **cluster**: migrate from worker.suicide (Evan Lucas) [#3743](https://github.com/nodejs/node/pull/3743)
+* [[`a5cce79ec3`](https://github.com/nodejs/node/commit/a5cce79ec3)] - **(SEMVER-MAJOR)** **console**: delete timers that have ended (Vladimir Varankin) [#3562](https://github.com/nodejs/node/pull/3562)
+* [[`1c84579031`](https://github.com/nodejs/node/commit/1c84579031)] - **(SEMVER-MAJOR)** **console**: timeEnd() with no label emits warning (Eugene Obrezkov) [#5901](https://github.com/nodejs/node/pull/5901)
+* [[`41feaa89e0`](https://github.com/nodejs/node/commit/41feaa89e0)] - **(SEMVER-MAJOR)** **crypto**: improve error messages (Sakthipriyan Vairamani) [#3100](https://github.com/nodejs/node/pull/3100)
+* [[`f429fe1b88`](https://github.com/nodejs/node/commit/f429fe1b88)] - **(SEMVER-MAJOR)** **crypto**: fail early when loading crypto without openssl (James M Snell) [#5611](https://github.com/nodejs/node/pull/5611)
+* [[`a37401e061`](https://github.com/nodejs/node/commit/a37401e061)] - **(SEMVER-MAJOR)** **crypto**: simplify Certificate class bindings (Alexander Makarenko) [#5382](https://github.com/nodejs/node/pull/5382)
+* [[`7c48cb5601`](https://github.com/nodejs/node/commit/7c48cb5601)] - **(SEMVER-MAJOR)** **crypto**: Improve control of FIPS mode (Stefan Budeanu) [#5181](https://github.com/nodejs/node/pull/5181)
+* [[`a1163582c5`](https://github.com/nodejs/node/commit/a1163582c5)] - **(SEMVER-MAJOR)** **crypto**: pbkdf2 deprecate digest overload. (Tom Gallacher) [#4047](https://github.com/nodejs/node/pull/4047)
+* [[`b010c87164`](https://github.com/nodejs/node/commit/b010c87164)] - **(SEMVER-MAJOR)** **crypto, string_bytes**: treat `buffer` str as `utf8` (Fedor Indutny) [#5522](https://github.com/nodejs/node/pull/5522)
+* [[`1d9451bb5a`](https://github.com/nodejs/node/commit/1d9451bb5a)] - **(SEMVER-MAJOR)** **crypto**: better error message for createHash (Calvin Metcalf) [#6042](https://github.com/nodejs/node/pull/6042)
+* [[`52af5c4eeb`](https://github.com/nodejs/node/commit/52af5c4eeb)] - **(SEMVER-MAJOR)** **deps**: upgrade V8 to 5.0.71.32 (Ali Ijaz Sheikh) [#6111](https://github.com/nodejs/node/pull/6111)
+* [[`2253be95d0`](https://github.com/nodejs/node/commit/2253be95d0)] - **(SEMVER-MAJOR)** **deps**: reintroduce supporting shared c-ares builds (Johan Bergström) [#5775](https://github.com/nodejs/node/pull/5775)
+* [[`4bc1cccb22`](https://github.com/nodejs/node/commit/4bc1cccb22)] - **(SEMVER-MAJOR)** **dgram**: pass null as error on successful send() (cjihrig) [#5929](https://github.com/nodejs/node/pull/5929)
+* [[`dbdbdd4998`](https://github.com/nodejs/node/commit/dbdbdd4998)] - **(SEMVER-MAJOR)** **dns**: add resolvePtr to query plain DNS PTR records (Daniel Turing) [#4921](https://github.com/nodejs/node/pull/4921)
+* [[`c4ab861a49`](https://github.com/nodejs/node/commit/c4ab861a49)] - **(SEMVER-MAJOR)** **dns**: add failure test for dns.resolveXXX (Daniel Turing) [#4921](https://github.com/nodejs/node/pull/4921)
+* [[`f3be421c1c`](https://github.com/nodejs/node/commit/f3be421c1c)] - **(SEMVER-MAJOR)** **dns**: coerce port to number in lookupService (Evan Lucas) [#4883](https://github.com/nodejs/node/pull/4883)
+* [[`4d4f3535a9`](https://github.com/nodejs/node/commit/4d4f3535a9)] - **(SEMVER-MAJOR)** **doc**: general improvements to fs.markdown (James M Snell) [#5616](https://github.com/nodejs/node/pull/5616)
+* [[`d8290286b3`](https://github.com/nodejs/node/commit/d8290286b3)] - **(SEMVER-MAJOR)** **doc**: document deprecation of util._extend (Benjamin Gruenbaum) [#4903](https://github.com/nodejs/node/pull/4903)
+* [[`236b7e8dd1`](https://github.com/nodejs/node/commit/236b7e8dd1)] - **(SEMVER-MAJOR)** **doc**: doc-only deprecation for util.log() (Jackson Tian) [#6161](https://github.com/nodejs/node/pull/6161)
+* [[`90204cc468`](https://github.com/nodejs/node/commit/90204cc468)] - **(SEMVER-MAJOR)** **domains**: clear stack when no error handler (Julien Gilli) [#4659](https://github.com/nodejs/node/pull/4659)
+* [[`e38bade828`](https://github.com/nodejs/node/commit/e38bade828)] - **(SEMVER-MAJOR)** **events**: don't inherit from Object.prototype (Brian White) [#6092](https://github.com/nodejs/node/pull/6092)
+* [[`53a95a5b12`](https://github.com/nodejs/node/commit/53a95a5b12)] - **(SEMVER-MAJOR)** **fs**: make fs.watch error message more useful (James M Snell) [#5616](https://github.com/nodejs/node/pull/5616)
+* [[`060e5f0c00`](https://github.com/nodejs/node/commit/060e5f0c00)] - **(SEMVER-MAJOR)** **fs**: Buffer and encoding enhancements to fs API (James M Snell) [#5616](https://github.com/nodejs/node/pull/5616)
+* [[`8bb60e3c8d`](https://github.com/nodejs/node/commit/8bb60e3c8d)] - **(SEMVER-MAJOR)** **fs**: improve error message for invalid flag (James M Snell) [#5590](https://github.com/nodejs/node/pull/5590)
+* [[`1124de2d76`](https://github.com/nodejs/node/commit/1124de2d76)] - **(SEMVER-MAJOR)** **fs**: deprecate fs.read's string interface (Sakthipriyan Vairamani) [#4525](https://github.com/nodejs/node/pull/4525)
+* [[`2b15e68bbe`](https://github.com/nodejs/node/commit/2b15e68bbe)] - **(SEMVER-MAJOR)** **fs**: fs.read into zero buffer should not throw exception (Feross Aboukhadijeh) [#4518](https://github.com/nodejs/node/pull/4518)
+* [[`8b97249893`](https://github.com/nodejs/node/commit/8b97249893)] - **(SEMVER-MAJOR)** **fs**: fix the error report on fs.link(Sync) (yorkie) [#3917](https://github.com/nodejs/node/pull/3917)
+* [[`b488b19eaf`](https://github.com/nodejs/node/commit/b488b19eaf)] - **(SEMVER-MAJOR)** **fs**: optimize realpath using uv_fs_realpath() (Yuval Brik) [#3594](https://github.com/nodejs/node/pull/3594)
+* [[`5f76b24e5e`](https://github.com/nodejs/node/commit/5f76b24e5e)] - **(SEMVER-MAJOR)** **http**: overridable `clientError` (Fedor Indutny) [#4557](https://github.com/nodejs/node/pull/4557)
+* [[`d01eb6882f`](https://github.com/nodejs/node/commit/d01eb6882f)] - **(SEMVER-MAJOR)** **lib**: add 'pid' prefix in `internal/util` (Minwoo Jung) [#3878](https://github.com/nodejs/node/pull/3878)
+* [[`20285ad177`](https://github.com/nodejs/node/commit/20285ad177)] - **(SEMVER-MAJOR)** **lib**: Consistent error messages in all modules (micnic) [#3374](https://github.com/nodejs/node/pull/3374)
+* [[`94b9948d63`](https://github.com/nodejs/node/commit/94b9948d63)] - **(SEMVER-MAJOR)** **lib,src**: ensure '(node:pid)' prefix for stdout logging (Minwoo Jung) [#3833](https://github.com/nodejs/node/pull/3833)
+* [[`b70dc67828`](https://github.com/nodejs/node/commit/b70dc67828)] - **(SEMVER-MAJOR)** **lib,test**: remove publicly exposed freelist (cjihrig) [#3738](https://github.com/nodejs/node/pull/3738)
+* [[`d38503ab01`](https://github.com/nodejs/node/commit/d38503ab01)] - **(SEMVER-MAJOR)** **module**: prioritize current dir for local lookups (Phillip Johnsen) [#5689](https://github.com/nodejs/node/pull/5689)
+* [[`71470a8e45`](https://github.com/nodejs/node/commit/71470a8e45)] - **(SEMVER-MAJOR)** **module**: pass v8::Object to linked module initialization function (Phillip Kovalev) [#4771](https://github.com/nodejs/node/pull/4771)
+* [[`18490d3d5a`](https://github.com/nodejs/node/commit/18490d3d5a)] - **(SEMVER-MAJOR)** **module**: always decorate thrown errors (Brian White) [#4287](https://github.com/nodejs/node/pull/4287)
+* [[`de1dc0ae2e`](https://github.com/nodejs/node/commit/de1dc0ae2e)] - **(SEMVER-MAJOR)** **module**: preserve symlinks when requiring (Alex Lamar) [#5950](https://github.com/nodejs/node/pull/5950)
+* [[`b85a50b6da`](https://github.com/nodejs/node/commit/b85a50b6da)] - **(SEMVER-MAJOR)** **net**: remove implicit setting of DNS hints (cjihrig) [#6021](https://github.com/nodejs/node/pull/6021)
+* [[`ec49fc8229`](https://github.com/nodejs/node/commit/ec49fc8229)] - **(SEMVER-MAJOR)** **net**: improve socket.write() error message (Phillip Johnsen) [#5981](https://github.com/nodejs/node/pull/5981)
+* [[`d0edabecbf`](https://github.com/nodejs/node/commit/d0edabecbf)] - **(SEMVER-MAJOR)** **net**: strict checking for internal/net isLegalPort (James M Snell) [#5733](https://github.com/nodejs/node/pull/5733)
+* [[`a78b3344f8`](https://github.com/nodejs/node/commit/a78b3344f8)] - **(SEMVER-MAJOR)** **net**: type check createServer options object (Sam Roberts) [#2904](https://github.com/nodejs/node/pull/2904)
+* [[`02ac302b6d`](https://github.com/nodejs/node/commit/02ac302b6d)] - **(SEMVER-MAJOR)** **net**: Validate port in createServer().listen() (Dirceu Pereira Tiegs) [#5732](https://github.com/nodejs/node/pull/5732)
+* [[`25751bedfe`](https://github.com/nodejs/node/commit/25751bedfe)] - **(SEMVER-MAJOR)** **node**: deprecate process.EventEmitter (Evan Lucas) [#5049](https://github.com/nodejs/node/pull/5049)
+* [[`08085c49b6`](https://github.com/nodejs/node/commit/08085c49b6)] - **(SEMVER-MAJOR)** **path**: assert inputs are strings (Brian White) [#5348](https://github.com/nodejs/node/pull/5348)
+* [[`d1000b4137`](https://github.com/nodejs/node/commit/d1000b4137)] - **(SEMVER-MAJOR)** **path**: make format() consistent and more functional (Nathan Woltman) [#2408](https://github.com/nodejs/node/pull/2408)
+* [[`c6656db352`](https://github.com/nodejs/node/commit/c6656db352)] - **(SEMVER-MAJOR)** **process**: add 'warning' event and process.emitWarning() (James M Snell) [#4782](https://github.com/nodejs/node/pull/4782)
+* [[`72e3dd9f43`](https://github.com/nodejs/node/commit/72e3dd9f43)] - **(SEMVER-MAJOR)** **process**: throw on non-function to nextTick() (yorkie) [#3860](https://github.com/nodejs/node/pull/3860)
+* [[`5dafb435d8`](https://github.com/nodejs/node/commit/5dafb435d8)] - **(SEMVER-MAJOR)** **querystring**: using toString for objects on querystring.escape (Igor Kalashnikov) [#5341](https://github.com/nodejs/node/pull/5341)
+* [[`dba245f796`](https://github.com/nodejs/node/commit/dba245f796)] - **(SEMVER-MAJOR)** **querystring**: don't inherit from Object.prototype (Brian White) [#6055](https://github.com/nodejs/node/pull/6055)
+* [[`0a62f929da`](https://github.com/nodejs/node/commit/0a62f929da)] - **(SEMVER-MAJOR)** **readline**: emit key info unconditionally (cjihrig) [#6024](https://github.com/nodejs/node/pull/6024)
+* [[`3de9bc9429`](https://github.com/nodejs/node/commit/3de9bc9429)] - **(SEMVER-MAJOR)** **readline**: document emitKeypressEvents() (cjihrig) [#6024](https://github.com/nodejs/node/pull/6024)
+* [[`ca2e8b292f`](https://github.com/nodejs/node/commit/ca2e8b292f)] - **(SEMVER-MAJOR)** **readline**: deprecate undocumented exports (cjihrig) [#3862](https://github.com/nodejs/node/pull/3862)
+* [[`0303a2552e`](https://github.com/nodejs/node/commit/0303a2552e)] - **(SEMVER-MAJOR)** **readline**: allow history to be disabled (surya panikkal) [#6352](https://github.com/nodejs/node/pull/6352)
+* [[`ad8257fa5b`](https://github.com/nodejs/node/commit/ad8257fa5b)] - **(SEMVER-MAJOR)** **repl**: Assignment of _ allowed with warning (Lance Ball) [#5535](https://github.com/nodejs/node/pull/5535)
+* [[`3ee68f794f`](https://github.com/nodejs/node/commit/3ee68f794f)] - **(SEMVER-MAJOR)** **repl**: don’t complete expressions when eval fails (Anna Henningsen) [#6328](https://github.com/nodejs/node/pull/6328)
+* [[`757fbac64b`](https://github.com/nodejs/node/commit/757fbac64b)] - **(SEMVER-MAJOR)** **src**: remove deprecated internal functions (Ben Noordhuis) [#6053](https://github.com/nodejs/node/pull/6053)
+* [[`4e46931406`](https://github.com/nodejs/node/commit/4e46931406)] - **(SEMVER-MAJOR)** **src**: deprecate undocumented variables (Jackson Tian) [#1838](https://github.com/nodejs/node/pull/1838)
+* [[`57003520f8`](https://github.com/nodejs/node/commit/57003520f8)] - **(SEMVER-MAJOR)** **src**: attach error to stack on displayErrors (cjihrig) [#4874](https://github.com/nodejs/node/pull/4874)
+* [[`e7c077c610`](https://github.com/nodejs/node/commit/e7c077c610)] - **(SEMVER-MAJOR)** **stream**: make null an invalid chunk to write in object mode (Calvin Metcalf) [#6170](https://github.com/nodejs/node/pull/6170)
+* [[`cc0342a517`](https://github.com/nodejs/node/commit/cc0342a517)] - **(SEMVER-MAJOR)** **streams**: update .readable/.writable to false (Brian White) [#4083](https://github.com/nodejs/node/pull/4083)
+* [[`652782d137`](https://github.com/nodejs/node/commit/652782d137)] - **(SEMVER-MAJOR)** **test**: update test-repl-require for local paths (Myles Borins) [#5689](https://github.com/nodejs/node/pull/5689)
+* [[`a5aa7c1713`](https://github.com/nodejs/node/commit/a5aa7c1713)] - **(SEMVER-MAJOR)** **test**: expand test case for unknown file open flags (James M Snell) [#5590](https://github.com/nodejs/node/pull/5590)
+* [[`2c33819370`](https://github.com/nodejs/node/commit/2c33819370)] - **(SEMVER-MAJOR)** **test**: fix tests that check error messages (cjihrig) [#3727](https://github.com/nodejs/node/pull/3727)
+* [[`ac153bd2a6`](https://github.com/nodejs/node/commit/ac153bd2a6)] - **(SEMVER-MAJOR)** **timers**: fail early when callback is not a function (Anna Henningsen) [#4362](https://github.com/nodejs/node/pull/4362)
+* [[`1ab6b21360`](https://github.com/nodejs/node/commit/1ab6b21360)] - **(SEMVER-MAJOR)** **tls**: rename `clientError` to `tlsClientError` (Fedor Indutny) [#4557](https://github.com/nodejs/node/pull/4557)
+* [[`df268f97bc`](https://github.com/nodejs/node/commit/df268f97bc)] - **(SEMVER-MAJOR)** **tls**: use SHA1 for sessionIdContext (Stefan Budeanu) [#3866](https://github.com/nodejs/node/pull/3866)
+* [[`8ffa20c495`](https://github.com/nodejs/node/commit/8ffa20c495)] - **(SEMVER-MAJOR)** **tools**: do not rewrite npm shebang in install.py (Evan Lucas) [#6098](https://github.com/nodejs/node/pull/6098)
+* [[`a2c0aa84e0`](https://github.com/nodejs/node/commit/a2c0aa84e0)] - **(SEMVER-MAJOR)** **tty**: Remove deprecated setRawMode wrapper (Wyatt Preul) [#2528](https://github.com/nodejs/node/pull/2528)
+* [[`eb4201f07a`](https://github.com/nodejs/node/commit/eb4201f07a)] - **(SEMVER-MAJOR)** **url**: drop auth in `url.resolve()` if host changes (Alex Kocharin) [#1480](https://github.com/nodejs/node/pull/1480)
+* [[`e2f47f5698`](https://github.com/nodejs/node/commit/e2f47f5698)] - **(SEMVER-MAJOR)** **util**: Change how Error objects are formatted (Mudit Ameta) [#4582](https://github.com/nodejs/node/pull/4582)
+* [[`93d6b5fb68`](https://github.com/nodejs/node/commit/93d6b5fb68)] - **(SEMVER-MAJOR)** **util**: use consistent Dates in inspect() (Xotic750) [#4318](https://github.com/nodejs/node/pull/4318)
+* [[`24012a879d`](https://github.com/nodejs/node/commit/24012a879d)] - **(SEMVER-MAJOR)** **util**: make inspect more reliable (Evan Lucas) [#4098](https://github.com/nodejs/node/pull/4098)
+* [[`007cfea308`](https://github.com/nodejs/node/commit/007cfea308)] - **(SEMVER-MAJOR)** **util**: remove pump (Wyatt Preul) [#2531](https://github.com/nodejs/node/pull/2531)
+* [[`4cf19ad1bb`](https://github.com/nodejs/node/commit/4cf19ad1bb)] - **(SEMVER-MAJOR)** **util**: Remove exec, has been deprecated for years (Wyatt Preul) [#2530](https://github.com/nodejs/node/pull/2530)
+* [[`34a35919e1`](https://github.com/nodejs/node/commit/34a35919e1)] - **(SEMVER-MAJOR)** **util**: improve typed array formatting (Ben Noordhuis) [#3793](https://github.com/nodejs/node/pull/3793)
+* [[`1cf26c036d`](https://github.com/nodejs/node/commit/1cf26c036d)] - **(SEMVER-MAJOR)** **win**: prevent node from running on Windows Vista or earlier (Alexis Campailla) [#5167](https://github.com/nodejs/node/pull/5167)
+* [[`55db19074d`](https://github.com/nodejs/node/commit/55db19074d)] - **(SEMVER-MAJOR)** **win,msi**: prevent from installing on Windows Vista or earlier (Alexis Campailla) [#5167](https://github.com/nodejs/node/pull/5167)
+* [['54a5287e3e']](https://github.com/nodejs/node/commit/54a5287e3e) -
+**(SEMVER-MAJOR)** **zlib**: fix gzip member head/buffer boundary issue (Anna Henningsen) [#5883](https://github.com/nodejs/node/pull/5883)
+* [[`8b43d3f52d`](https://github.com/nodejs/node/commit/8b43d3f52d)] - **(SEMVER-MAJOR)** **zlib**: do not emit event on *Sync() methods (Rich Trott) [#5707](https://github.com/nodejs/node/pull/5707)
+
+
+Semver-minor and patch commits since v5.11.0
+
+* [[`6c1e5ad3ab`](https://github.com/nodejs/node/commit/6c1e5ad3ab)] - **(SEMVER-MINOR)** **buffer**: add Buffer.prototype.lastIndexOf() (dcposch@dcpos.ch) [#4846](https://github.com/nodejs/node/pull/4846)
+* [[`dd67608bfd`](https://github.com/nodejs/node/commit/dd67608bfd)] - **buffer**: safeguard against accidental kNoZeroFill (Сковорода Никита Андреевич) [nodejs/node-private#30](https://github.com/nodejs/node-private/pull/30)
+* [[`a4b8000029`](https://github.com/nodejs/node/commit/a4b8000029)] - **build**: update android-configure script for npm (Robert Chiras) [#6349](https://github.com/nodejs/node/pull/6349)
+* [[`40ede46690`](https://github.com/nodejs/node/commit/40ede46690)] - **cares**: Support malloc(0) scenarios for AIX (Gireesh Punathil) [#6305](https://github.com/nodejs/node/pull/6305)
+* [[`e5f1e2c1df`](https://github.com/nodejs/node/commit/e5f1e2c1df)] - **deps**: upgrade to V8 5.0.71.35 (Ali Ijaz Sheikh) [#6372](https://github.com/nodejs/node/pull/6372)
+* [[`49e42c530b`](https://github.com/nodejs/node/commit/49e42c530b)] - **deps**: upgrade to V8 5.0.71.34 (Ali Ijaz Sheikh) [#6320](https://github.com/nodejs/node/pull/6320)
+* [[`2011f2c6dc`](https://github.com/nodejs/node/commit/2011f2c6dc)] - **doc**: fix position of `fs.readSync()` (Jeremiah Senkpiel) [#6399](https://github.com/nodejs/node/pull/6399)
+* [[`29a6c7c1f0`](https://github.com/nodejs/node/commit/29a6c7c1f0)] - **doc**: change references to Stable to Current (Myles Borins) [#6318](https://github.com/nodejs/node/pull/6318)
+* [[`a026cd0fa5`](https://github.com/nodejs/node/commit/a026cd0fa5)] - **doc**: update authors (James M Snell) [#6373](https://github.com/nodejs/node/pull/6373)
+* [[`92a02d51dc`](https://github.com/nodejs/node/commit/92a02d51dc)] - **doc**: add JacksonTian to collaborators (Jackson Tian) [#6388](https://github.com/nodejs/node/pull/6388)
+* [[`879aeb5e49`](https://github.com/nodejs/node/commit/879aeb5e49)] - **doc**: add Minqi Pan to collaborators (Minqi Pan) [#6387](https://github.com/nodejs/node/pull/6387)
+* [[`be5d699055`](https://github.com/nodejs/node/commit/be5d699055)] - **doc**: add eljefedelrodeodeljefe to collaborators (Robert Jefe Lindstaedt) [#6389](https://github.com/nodejs/node/pull/6389)
+* [[`916b1a1d44`](https://github.com/nodejs/node/commit/916b1a1d44)] - **doc**: add ronkorving to collaborators (ronkorving) [#6385](https://github.com/nodejs/node/pull/6385)
+* [[`c7066fb853`](https://github.com/nodejs/node/commit/c7066fb853)] - **doc**: add estliberitas to collaborators (Alexander Makarenko) [#6386](https://github.com/nodejs/node/pull/6386)
+* [[`983a809456`](https://github.com/nodejs/node/commit/983a809456)] - **doc**: fix broken references (Alexander Gromnitsky) [#6350](https://github.com/nodejs/node/pull/6350)
+* [[`ae991e7577`](https://github.com/nodejs/node/commit/ae991e7577)] - **doc**: add note for platform specific flags `fs.open()` (Robert Jefe Lindstaedt) [#6136](https://github.com/nodejs/node/pull/6136)
+* [[`f85412d49b`](https://github.com/nodejs/node/commit/f85412d49b)] - **doc**: improvements to child_process, process docs (Alexander Makarenko)
+* [[`f6d90a912b`](https://github.com/nodejs/node/commit/f6d90a912b)] - **doc**: fix a typo in the CONTRIBUTING.md (vsemozhetbyt) [#6343](https://github.com/nodejs/node/pull/6343)
+* [[`6815a3b7f9`](https://github.com/nodejs/node/commit/6815a3b7f9)] - **doc**: add vm example, be able to require modules (Robert Jefe Lindstaedt) [#5323](https://github.com/nodejs/node/pull/5323)
+* [[`7f11634a46`](https://github.com/nodejs/node/commit/7f11634a46)] - **doc**: note that process.config can and will be changed (James M Snell) [#6266](https://github.com/nodejs/node/pull/6266)
+* [[`0e7d57af35`](https://github.com/nodejs/node/commit/0e7d57af35)] - **(SEMVER-MINOR)** **events**: add prependListener() and prependOnceListener() (James M Snell) [#6032](https://github.com/nodejs/node/pull/6032)
+* [[`c1cd64481f`](https://github.com/nodejs/node/commit/c1cd64481f)] - **events**: make eventNames() use Reflect.ownKeys() (Luigi Pinca) [#5822](https://github.com/nodejs/node/pull/5822)
+* [[`f1294f5bfd`](https://github.com/nodejs/node/commit/f1294f5bfd)] - **gyp**: inherit parent for `*.host` (Johan Bergström) [#6173](https://github.com/nodejs/node/pull/6173)
+* [[`d5922bd7a9`](https://github.com/nodejs/node/commit/d5922bd7a9)] - **querystring**: fix comments (Brian White) [#6365](https://github.com/nodejs/node/pull/6365)
+* [[`2c480bdae6`](https://github.com/nodejs/node/commit/2c480bdae6)] - **src**: fix check-imports.py linter errors (Sakthipriyan Vairamani) [#6105](https://github.com/nodejs/node/pull/6105)
+* [[`5eb4ec090d`](https://github.com/nodejs/node/commit/5eb4ec090d)] - **src**: squelch -Wunused-variable in non-icu builds (Ben Noordhuis) [#6351](https://github.com/nodejs/node/pull/6351)
+* [[`a3b5b9cbf2`](https://github.com/nodejs/node/commit/a3b5b9cbf2)] - **src**: fix out-of-bounds write in TwoByteValue (Anna Henningsen) [#6330](https://github.com/nodejs/node/pull/6330)
+* [[`cdba9a6c02`](https://github.com/nodejs/node/commit/cdba9a6c02)] - **src**: add intl and icu configs to process.binding('config') (James M Snell) [#6266](https://github.com/nodejs/node/pull/6266)
+* [[`2e974cdd8c`](https://github.com/nodejs/node/commit/2e974cdd8c)] - **src**: add process.binding('config') (James M Snell) [#6266](https://github.com/nodejs/node/pull/6266)
+* [[`75e073f2b2`](https://github.com/nodejs/node/commit/75e073f2b2)] - **test**: increase the platform timeout for AIX (Michael Dawson) [#6342](https://github.com/nodejs/node/pull/6342)
+* [[`84ebf2b40d`](https://github.com/nodejs/node/commit/84ebf2b40d)] - **test**: add tests for console.assert (Evan Lucas) [#6302](https://github.com/nodejs/node/pull/6302)
+* [[`a770a163ab`](https://github.com/nodejs/node/commit/a770a163ab)] - **test**: v8-flags is sensitive to script caching (Ali Ijaz Sheikh) [#6316](https://github.com/nodejs/node/pull/6316)
+* [[`1e4d053e6b`](https://github.com/nodejs/node/commit/1e4d053e6b)] - **test**: don't assume IPv6 in test-regress-GH-5727 (cjihrig) [#6319](https://github.com/nodejs/node/pull/6319)
+* [[`a7335bd1f0`](https://github.com/nodejs/node/commit/a7335bd1f0)] - **test,benchmark**: use deepStrictEqual() (Rich Trott) [#6213](https://github.com/nodejs/node/pull/6213)
+* [[`6781d917f4`](https://github.com/nodejs/node/commit/6781d917f4)] - **tools**: rewrite check-install.sh in python (Sakthipriyan Vairamani) [#6105](https://github.com/nodejs/node/pull/6105)
+* [[`e84c69310f`](https://github.com/nodejs/node/commit/e84c69310f)] - **tools**: enforce deepStrictEqual over deepEqual (Rich Trott) [#6213](https://github.com/nodejs/node/pull/6213)
+* [[`7940ecfa00`](https://github.com/nodejs/node/commit/7940ecfa00)] - **v8**: warn in Template::Set() on improper use (Ben Noordhuis) [#6277](https://github.com/nodejs/node/pull/6277)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v6.0.0/node-v6.0.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v6.0.0/node-v6.0.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v6.0.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v6.0.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v6.0.0/node-v6.0.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: *Coming soon*<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v6.0.0/node-v6.0.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v6.0.0/node-v6.0.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v6.0.0/<br>
+Documentation: https://nodejs.org/docs/v6.0.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+5be18c5571ce2b33918a3dd0be2f18d2a6939a60754026fb7e7967bec09d9e5e  node-v6.0.0-darwin-x64.tar.gz
+9da8c11bf45f8b6b8c6a720cfaa37624d18d6972d8670c565b6e005e643b572a  node-v6.0.0-darwin-x64.tar.xz
+f72de0e9403dd4ab7b6eec7266a498ba561afe5d5c7aff77b83894b43c959beb  node-v6.0.0-headers.tar.gz
+8b6c5a315fefa7b873cbedd8daf75ee928646df2f05efa60c9c7d3a488851bd1  node-v6.0.0-headers.tar.xz
+c4d7da92f76e77d27ef5650ad01085baad74439fab15e5143a8e9fc6cad13101  node-v6.0.0-linux-arm64.tar.gz
+68d31984e304e5840591331bdd3eaa375fe07fa96307eb7d4681cea5ccb4e669  node-v6.0.0-linux-arm64.tar.xz
+7a29af935545c07ea2eb5bbf6b6fb643765d50ee69d1b4193345a50fb8cb1093  node-v6.0.0-linux-armv7l.tar.gz
+5a9b4c275313c1335819924c5028241cf2ee107032c530836b41938916090bd6  node-v6.0.0-linux-armv7l.tar.xz
+7044f1049d6d8673cff7b0d38cd8c606be56ba149d3d32b34ca3f017df731a2a  node-v6.0.0-linux-ppc64le.tar.gz
+65e208fb8189b264f6e66d0d4974485b5eb83cae2db34cc7d09464cb43142354  node-v6.0.0-linux-ppc64le.tar.xz
+78fa76c77a1168095cf5b8a5018e00e7212d11e485cf10c77ce1c8af4955cdd3  node-v6.0.0-linux-x64.tar.gz
+1e7aa64e28f26887810df74ca4bb0f3c37c332e866aefd16c23daedfcf67935b  node-v6.0.0-linux-x64.tar.xz
+51321999e9706d9c24ea3689a03d049ad96657933228d3ed25d7710bc5d9e9bc  node-v6.0.0-linux-x86.tar.gz
+5b1cbe9a5af935619b7d4a36d09cc3b73ea2605a1bd3ab9121920caba6f95a5e  node-v6.0.0-linux-x86.tar.xz
+6f2114f02252c40304e3951b058ddababfe94b86e25cd8b3dddbf6aaa295ce71  node-v6.0.0.pkg
+dc1345210205380af8fa16a63dca996803af105d7b0e5aa4160df7ed88523f08  node-v6.0.0-sunos-x64.tar.gz
+0f69caa00c56e21c44c849e3e82e2fa3c775f441326f2668ac9503bc349eac03  node-v6.0.0-sunos-x64.tar.xz
+61259a9794d2ed7b0e5331d5d2158da06f6ed5d31cbeae6d71da4d5e941a7754  node-v6.0.0-sunos-x86.tar.gz
+822bd48f5443cc45513747b4ce3aa337ff98e27e8f4c63e6bbba23f7b57d2aa3  node-v6.0.0-sunos-x86.tar.xz
+6db56d81a4e07ff4017809ad4ee49a5256fad804cd8527f8724f8e149e3dfc32  node-v6.0.0.tar.gz
+f0e5bdc3cf4af85b8a24bdbebed81e1a9f7fda91cab8a9475737940aa90da617  node-v6.0.0.tar.xz
+933a15791a67a2740cbd082a8d9aebc43162ec6d4db335abf62121a9561c57d4  node-v6.0.0-x64.msi
+614380711039b7cc23db8d8cbf42ed9f4a6f0501eb8a143490f7ece952037bc9  node-v6.0.0-x86.msi
+e2e434c5d63d684f0f0f074ee97b5a79fd0d9fbb340bac658f325239aec2589f  win-x64/node.exe
+b1c9f9d58ef1fd684f0d136cce002e800c852203f876606b1b641692171783c3  win-x64/node.lib
+675199b7db04f95545d8ca650b87b1cc6616e5e6638b854cd7f2bbabb050d533  win-x86/node.exe
+c2b83ffce6edfdfee450f07fab28d299b99a1046a5ba9452830126303a0739b6  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQEbBAEBCgAGBQJXH8kkAAoJEHNBsVwHCHesjyEH+NCanRJnIPn6HnO7U26Zjht4
+FdNURcOs4ILB+R9vOS0G5OpU5fL8u1PVpPMGhkdOcvV7Xv1Nh1Vm67alOzAFv1Id
+pmepNbT/hA5BGmZvt9K/Pp0+LXKXLaRStooof0QMxR8My/M65V1VNsU1CEY2ffSK
+oNRf6roxvNPE0JcMmwEBDXnrEZ+hi/8R0hIms6zt6tzUcHmvzkdQ+5sGU07kKRdU
+6Ez/0raEteAfzXoUoyerHTzERGP9lE8Gz7TA2vEa2Wz30brBF+FcGw+T+H/nn41N
+WHZwA/fyoZo25rPzpXWygG63u7e/2OUv1pUdYp1tjkTJ+ytdb8l4RX/oOGCM4A==
+=XFwg
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v6.1.0.md b/locale/uk/blog/release/v6.1.0.md
new file mode 100755
index 0000000000000..12bf12910d34d
--- /dev/null
+++ b/locale/uk/blog/release/v6.1.0.md
@@ -0,0 +1,164 @@
+---
+date: 2016-05-05T23:07:06.434Z
+version: 6.1.0
+category: release
+title: Node v6.1.0 (Current)
+slug: node-v6-1-0
+layout: blog-post.hbs
+author: Jeremiah Senkpiel
+---
+
+Please see our [blog post](https://nodejs.org/en/blog/vulnerability/openssl-may-2016/) for more info on the security contents of this release.
+
+### Notable Changes
+
+* **assert**: `deep{Strict}Equal()` now works correctly with circular references. (Rich Trott) [#6432](https://github.com/nodejs/node/pull/6432)
+* **debugger**: Arrays are now formatted correctly in the debugger repl. (cjihrig) [#6448](https://github.com/nodejs/node/pull/6448)
+* **deps**: Upgrade OpenSSL sources to 1.0.2h (Shigeki Ohtsu) [#6550](https://github.com/nodejs/node/pull/6550)
+* **net**: Introduced a `Socket#connecting` property. (Fedor Indutny) [#6404](https://github.com/nodejs/node/pull/6404)
+  - Previously this information was only available as the undocumented, internal `_connecting` property.
+* **process**: Introduced `process.cpuUsage()`. (Patrick Mueller) [#6157](https://github.com/nodejs/node/pull/6157)
+* **stream**: `Writable#setDefaultEncoding()` now returns `this`. (Alexander Makarenko) [#5040](https://github.com/nodejs/node/pull/5040)
+* **util**: Two new additions to `util.inspect()`:
+  - Added a `maxArrayLength` option to truncate the formatting of Arrays. (James M Snell) [#6334](https://github.com/nodejs/node/pull/6334)
+    - This is set to `100` by default.
+  - Added a `showProxy` option for formatting proxy intercepting handlers. (James M Snell) [#6465](https://github.com/nodejs/node/pull/6465)
+    - Inspecting proxies is non-trivial and as such this is off by default.
+
+### Commits
+
+* [[`76c9ab5fcf`](https://github.com/nodejs/node/commit/76c9ab5fcf)] - **assert**: allow circular references (Rich Trott) [#6432](https://github.com/nodejs/node/pull/6432)
+* [[`7b9ae70757`](https://github.com/nodejs/node/commit/7b9ae70757)] - **benchmark**: Fix crash in net benchmarks (Matt Loring) [#6407](https://www.github.com/nodejs/node/pull/6407)
+* [[`0d1985358a`](https://github.com/nodejs/node/commit/0d1985358a)] - **build**: use shorthand lint target from test (Johan Bergström) [#6406](https://github.com/nodejs/node/pull/6406)
+* [[`7153f96f0e`](https://github.com/nodejs/node/commit/7153f96f0e)] - **build**: unbreak -prof, disable PIE on OS X (Ben Noordhuis) [#6453](https://github.com/nodejs/node/pull/6453)
+* [[`8956432e18`](https://github.com/nodejs/node/commit/8956432e18)] - **build**: exclude tap files from tarballs (Brian White) [#6348](https://github.com/nodejs/node/pull/6348)
+* [[`11e7cc5310`](https://github.com/nodejs/node/commit/11e7cc5310)] - **build**: don't compile with -B (Ben Noordhuis) [#6393](https://github.com/nodejs/node/pull/6393)
+* [[`1330496bbf`](https://github.com/nodejs/node/commit/1330496bbf)] - **cluster**: remove use of bind() in destroy() (yorkie) [#6502](https://github.com/nodejs/node/pull/6502)
+* [[`fdde36909c`](https://github.com/nodejs/node/commit/fdde36909c)] - **crypto**: fix error in deprecation message (Rich Trott) [#6344](https://github.com/nodejs/node/pull/6344)
+* [[`2d503b1d4b`](https://github.com/nodejs/node/commit/2d503b1d4b)] - **debugger**: display array contents in repl (cjihrig) [#6448](https://github.com/nodejs/node/pull/6448)
+* [[`54f8600613`](https://github.com/nodejs/node/commit/54f8600613)] - **deps**: update openssl asm and asm_obsolete files (Shigeki Ohtsu) [#6550](https://github.com/nodejs/node/pull/6550)
+* [[`a5a2944877`](https://github.com/nodejs/node/commit/a5a2944877)] - **deps**: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) [nodejs/io.js#1836](https://github.com/nodejs/io.js/pull/1836)
+* [[`3fe68129c8`](https://github.com/nodejs/node/commit/3fe68129c8)] - **deps**: fix asm build error of openssl in x86_win32 (Shigeki Ohtsu) [iojs/io.js#1389](https://github.com/iojs/io.js/pull/1389)
+* [[`d159462fed`](https://github.com/nodejs/node/commit/d159462fed)] - **deps**: fix openssl assembly error on ia32 win32 (Fedor Indutny) [iojs/io.js#1389](https://github.com/iojs/io.js/pull/1389)
+* [[`3af28d3693`](https://github.com/nodejs/node/commit/3af28d3693)] - **deps**: copy all openssl header files to include dir (Shigeki Ohtsu) [#6550](https://github.com/nodejs/node/pull/6550)
+* [[`e6ab3ece65`](https://github.com/nodejs/node/commit/e6ab3ece65)] - **deps**: upgrade openssl sources to 1.0.2h (Shigeki Ohtsu) [#6550](https://github.com/nodejs/node/pull/6550)
+* [[`65b6574d59`](https://github.com/nodejs/node/commit/65b6574d59)] - **deps**: backport IsValid changes from 4e8736d in V8 (Michaël Zasso) [#6544](https://github.com/nodejs/node/pull/6544)
+* [[`33f24c821b`](https://github.com/nodejs/node/commit/33f24c821b)] - **doc**: adds 'close' events to fs.ReadStream and fs.WriteStream (Jenna Vuong) [#6499](https://github.com/nodejs/node/pull/6499)
+* [[`4f728df1bf`](https://github.com/nodejs/node/commit/4f728df1bf)] - **doc**: linkify remaining references to fs.Stats object (Kevin Donahue) [#6485](https://github.com/nodejs/node/pull/6485)
+* [[`9a29b50c52`](https://github.com/nodejs/node/commit/9a29b50c52)] - **doc**: fix the lint of an example in cluster.md (yorkie) [#6516](https://github.com/nodejs/node/pull/6516)
+* [[`d674493fa5`](https://github.com/nodejs/node/commit/d674493fa5)] - **doc**: add missing underscore for markdown italics (Kevin Donahue) [#6529](https://github.com/nodejs/node/pull/6529)
+* [[`7c30f15e1b`](https://github.com/nodejs/node/commit/7c30f15e1b)] - **doc**: ensure consistent grammar in node.1 file (justshiv) [#6426](https://github.com/nodejs/node/pull/6426)
+* [[`e5ce53a217`](https://github.com/nodejs/node/commit/e5ce53a217)] - **doc**: fix sentence fragment in fs doc (Rich Trott) [#6488](https://github.com/nodejs/node/pull/6488)
+* [[`3e028a143c`](https://github.com/nodejs/node/commit/3e028a143c)] - **doc**: remove obsolete comment in isError() example (cjihrig) [#6486](https://github.com/nodejs/node/pull/6486)
+* [[`969f96a019`](https://github.com/nodejs/node/commit/969f96a019)] - **doc**: fix a typo in `__dirname` section (William Luo) [#6473](https://github.com/nodejs/node/pull/6473)
+* [[`ab7055b003`](https://github.com/nodejs/node/commit/ab7055b003)] - **doc**: fix fs.realpath man pg links (phette23) [#6451](https://github.com/nodejs/node/pull/6451)
+* [[`13e660888f`](https://github.com/nodejs/node/commit/13e660888f)] - **doc**: extra clarification of historySize option (vsemozhetbyt) [#6397](https://github.com/nodejs/node/pull/6397)
+* [[`3d5b732660`](https://github.com/nodejs/node/commit/3d5b732660)] - **doc**: clarifies http.serverResponse implementation (Allen Hernandez) [#6072](https://github.com/nodejs/node/pull/6072)
+* [[`7034ebe2bc`](https://github.com/nodejs/node/commit/7034ebe2bc)] - **doc**: use `Node.js` in synopsis document (Rich Trott) [#6476](https://github.com/nodejs/node/pull/6476)
+* [[`4ae39f9863`](https://github.com/nodejs/node/commit/4ae39f9863)] - **doc**: remove all scrollbar styling (Claudio Rodriguez) [#6479](https://github.com/nodejs/node/pull/6479)
+* [[`e6c8da45b1`](https://github.com/nodejs/node/commit/e6c8da45b1)] - **(SEMVER-MINOR)** **doc**: make `writable.setDefaultEncoding()` return `this` (Alexander Makarenko) [#5040](https://github.com/nodejs/node/pull/5040)
+* [[`4068d64f4f`](https://github.com/nodejs/node/commit/4068d64f4f)] - **doc**: fix EventEmitter#eventNames() example (Сковорода Никита Андреевич) [#6417](https://github.com/nodejs/node/pull/6417)
+* [[`bfcde97251`](https://github.com/nodejs/node/commit/bfcde97251)] - **doc**: fix incorrect syntax in examples (Evan Lucas) [#6463](https://github.com/nodejs/node/pull/6463)
+* [[`8eb87ee239`](https://github.com/nodejs/node/commit/8eb87ee239)] - **doc**: Remove extra space in REPL example (Juan) [#6447](https://github.com/nodejs/node/pull/6447)
+* [[`fd37d54eb5`](https://github.com/nodejs/node/commit/fd37d54eb5)] - **doc**: added note warning about change to console.endTime() (Ben Page) [#6454](https://github.com/nodejs/node/pull/6454)
+* [[`b3f75ec801`](https://github.com/nodejs/node/commit/b3f75ec801)] - **doc**: expand documentation for process.exit() (James M Snell) [#6410](https://github.com/nodejs/node/pull/6410)
+* [[`fc0fbf1c63`](https://github.com/nodejs/node/commit/fc0fbf1c63)] - **doc**: subdivide TOC, add auxiliary links (Jeremiah Senkpiel) [#6167](https://github.com/nodejs/node/pull/6167)
+* [[`150dd36503`](https://github.com/nodejs/node/commit/150dd36503)] - **doc**: no Node.js(1) (Jeremiah Senkpiel) [#6167](https://github.com/nodejs/node/pull/6167)
+* [[`ab84d69048`](https://github.com/nodejs/node/commit/ab84d69048)] - **doc**: better example & synopsis (Jeremiah Senkpiel) [#6167](https://github.com/nodejs/node/pull/6167)
+* [[`f6d72791a1`](https://github.com/nodejs/node/commit/f6d72791a1)] - **doc**: update build instructions for OS X (Rich Trott) [#6309](https://github.com/nodejs/node/pull/6309)
+* [[`36207c6daf`](https://github.com/nodejs/node/commit/36207c6daf)] - **doc**: correctly document the behavior of ee.once(). (Lance Ball) [#6371](https://github.com/nodejs/node/pull/6371)
+* [[`19fb1345ba`](https://github.com/nodejs/node/commit/19fb1345ba)] - **doc**: use Buffer.from() instead of new Buffer() (Jackson Tian) [#6367](https://github.com/nodejs/node/pull/6367)
+* [[`fb6753c75c`](https://github.com/nodejs/node/commit/fb6753c75c)] - **doc**: fix v6 changelog (James M Snell) [#6435](https://github.com/nodejs/node/pull/6435)
+* [[`2c92a1fe03`](https://github.com/nodejs/node/commit/2c92a1fe03)] - **events**: pass the original listener added by once (DavidCai) [#6394](https://github.com/nodejs/node/pull/6394)
+* [[`9ea6b282e8`](https://github.com/nodejs/node/commit/9ea6b282e8)] - **meta**: split CHANGELOG into two files (Myles Borins) [#6337](https://github.com/nodejs/node/pull/6337)
+* [[`cbbe95e1e1`](https://github.com/nodejs/node/commit/cbbe95e1e1)] - **(SEMVER-MINOR)** **net**: introduce `Socket#connecting` property (Fedor Indutny) [#6404](https://github.com/nodejs/node/pull/6404)
+* [[`534f03c2f0`](https://github.com/nodejs/node/commit/534f03c2f0)] - **openssl**: fix keypress requirement in apps on win32 (Shigeki Ohtsu) [iojs/io.js#1389](https://github.com/iojs/io.js/pull/1389)
+* [[`1b9fdba04e`](https://github.com/nodejs/node/commit/1b9fdba04e)] - **(SEMVER-MINOR)** **process**: add process.cpuUsage() - implementation, doc, tests (Patrick Mueller) [#6157](https://github.com/nodejs/node/pull/6157)
+* [[`fa9d82d120`](https://github.com/nodejs/node/commit/fa9d82d120)] - **src**: unify implementations of Utf8Value etc. (Anna Henningsen) [#6357](https://github.com/nodejs/node/pull/6357)
+* [[`65030c77b7`](https://github.com/nodejs/node/commit/65030c77b7)] - **test**: fix alpn tests for openssl1.0.2h (Shigeki Ohtsu) [#6550](https://github.com/nodejs/node/pull/6550)
+* [[`7641f9a6de`](https://github.com/nodejs/node/commit/7641f9a6de)] - **test**: refactor large event emitter tests (cjihrig) [#6446](https://github.com/nodejs/node/pull/6446)
+* [[`5fe5fa2897`](https://github.com/nodejs/node/commit/5fe5fa2897)] - **test**: make addon testing part of `make test` (Ben Noordhuis) [#6232](https://github.com/nodejs/node/pull/6232)
+* [[`457d12a0a1`](https://github.com/nodejs/node/commit/457d12a0a1)] - **test**: add failing url parse tests as known_issue (James M Snell) [#5885](https://github.com/nodejs/node/pull/5885)
+* [[`089362f8b8`](https://github.com/nodejs/node/commit/089362f8b8)] - **test,tools**: limit lint tolerance of gc global (Rich Trott) [#6324](https://github.com/nodejs/node/pull/6324)
+* [[`6d1606ee94`](https://github.com/nodejs/node/commit/6d1606ee94)] - **test,tools**: adjust function argument alignment (Rich Trott) [#6390](https://github.com/nodejs/node/pull/6390)
+* [[`08e0884ae0`](https://github.com/nodejs/node/commit/08e0884ae0)] - **tools**: add -F flag for fixing lint issues (Rich Trott) [#6483](https://github.com/nodejs/node/pull/6483)
+* [[`9f23cb24f2`](https://github.com/nodejs/node/commit/9f23cb24f2)] - **tools**: fix exit code when linting from CI (Brian White) [#6412](https://github.com/nodejs/node/pull/6412)
+* [[`e62c42b8f4`](https://github.com/nodejs/node/commit/e62c42b8f4)] - **tools**: remove default parameters from lint rule (Rich Trott) [#6411](https://github.com/nodejs/node/pull/6411)
+* [[`66903f6695`](https://github.com/nodejs/node/commit/66903f6695)] - **tools**: add tests for the doctool (Ian Kronquist) [#6031](https://github.com/nodejs/node/pull/6031)
+* [[`3f608b16a7`](https://github.com/nodejs/node/commit/3f608b16a7)] - **tools**: lint for function argument alignment (Rich Trott) [#6390](https://github.com/nodejs/node/pull/6390)
+* [[`91ab769940`](https://github.com/nodejs/node/commit/91ab769940)] - **(SEMVER-MINOR)** **util**: truncate inspect array and typed array (James M Snell) [#6334](https://github.com/nodejs/node/pull/6334)
+* [[`0bca959617`](https://github.com/nodejs/node/commit/0bca959617)] - **(SEMVER-MINOR)** **util**: fix inspecting of proxy objects (James M Snell) [#6465](https://github.com/nodejs/node/pull/6465)
+
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v6.1.0/node-v6.1.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v6.1.0/node-v6.1.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v6.1.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v6.1.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v6.1.0/node-v6.1.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v6.1.0/node-v6.1.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v6.1.0/node-v6.1.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v6.1.0/<br>
+Documentation: https://nodejs.org/docs/v6.1.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+481aeab001b6c79589daf3e1f8f5b9ad7021a3979b49fd842313010482ff7b56  node-v6.1.0-darwin-x64.tar.gz
+a599974633ffbc8a3964699080d4f369297198eac4e18a990f801a6b42b742e6  node-v6.1.0-darwin-x64.tar.xz
+9419fce25791df7afd27d173a1148ef9f53c349cd9a2e8d9bdac5276d80a1bb5  node-v6.1.0-headers.tar.gz
+8e35bf983def6f7bc321fbabcd3bf5e7909e30417cb9c43f31171a63cf664b10  node-v6.1.0-headers.tar.xz
+87670387877d1cbe36642970e3ca84a77121d3200771b80ec2286bc261e060f7  node-v6.1.0-linux-arm64.tar.gz
+7fde2a7b2b7d96d14d3f3f655474434af38583b471973ba3ff07ae29a1f0d821  node-v6.1.0-linux-arm64.tar.xz
+aeff5e4b77fba25feb19ec4739116373234e93aff0d2c9662c4ebd87fa4b34ae  node-v6.1.0-linux-armv6l.tar.gz
+856120ca6e03501c29fadced18f737487092ad75845247e8e2feea30b97f53c9  node-v6.1.0-linux-armv6l.tar.xz
+55d7a2e5071b13db6fe5d952dc5ee5d2223ae4a0de2f2c2d7a68d65e1cfa377b  node-v6.1.0-linux-armv7l.tar.gz
+ee9583ee94c602b63d758edb564e944a24d4cadac38bde95b25e4995362297e8  node-v6.1.0-linux-armv7l.tar.xz
+bca98e8a4f5c11dee9eb4fec2bd0a42c1f8a921863bba417fc88c7274a0c0c04  node-v6.1.0-linux-ppc64le.tar.gz
+5b2b85bbc2f289d3f6c458fa77cdf7c74befccfade02c7a287c6992addcbf3f0  node-v6.1.0-linux-ppc64le.tar.xz
+ce46dd0188181b70661b9162feffdbd8a860cb75cb6661c37d6d61982e3f72c5  node-v6.1.0-linux-x64.tar.gz
+6ae9d08f8c606810e17db6a6c9ff2689072e27682a0e1875cbb75effa8ae3d5e  node-v6.1.0-linux-x64.tar.xz
+07d6f0b11b98c876f2d029722696da6cc9b93a2ce6b34abb7a517e0afb04fb34  node-v6.1.0-linux-x86.tar.gz
+41b34eef859fb0d39498bc900778f5e692fe4367b7d1588df3ae1f1f98bc4330  node-v6.1.0-linux-x86.tar.xz
+b58bfcbce73dc04342a465dca92d802bf5e437f7da224b6157d6c87fe805c5f6  node-v6.1.0.pkg
+d7cbb0bfe0915ac7bdb37e87ea7145f6e86ef2943e77f306c648e47d3d33c898  node-v6.1.0-sunos-x64.tar.gz
+930596fb6ddb8aedc3c358002786f207f30b3d7f0b377766d5017452ea36196f  node-v6.1.0-sunos-x64.tar.xz
+38ec9537ab2fbf6112365b3a291ebe962d14b384b474e54fa77227b2e98624c9  node-v6.1.0-sunos-x86.tar.gz
+254c080b41db83979d200c4ab28fbbc667b8528d9e260ce9f2599293bb17e4a0  node-v6.1.0-sunos-x86.tar.xz
+9e67ef0b8611e16e6e311eccf0489a50fe76ceebeea3023ef4f51be647ae4bc3  node-v6.1.0.tar.gz
+c7940301917232527490a166df78f9d3d58e70e10fd502f73889d936763cfe84  node-v6.1.0.tar.xz
+b32b1105da5c08023976717d9aaeb0e3ba93d09f170aa3d81ad8ddfb0abfbdd4  node-v6.1.0-x64.msi
+26b762f6066feeae59107c064eeaf70019880cb113279d51e35dff46c6c81be2  node-v6.1.0-x86.msi
+a0f1fa671ae76821dd1098fb67bbc9601bdf5229a1dac5585441d279765d0d20  win-x64/node.exe
+135215ad3ff8774386d6525e69d62ca3a24da5a7962f1464e1b5758b58583eb3  win-x64/node.lib
+a6391706a5ac17bcf9f8ff5fb9c0359b6787dcfd45a6089f91d36edb49738c69  win-x86/node.exe
+17608b03161b6fd3e956ff0a53da0a0d483a3860fa236eb8e1eaf205158916fc  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJXLLHaAAoJEEX17r2BPa6O3C4P+wXrjmby0cm/K1HLpmCtitMu
+4aMpt1/MlVVZjlCrm/vtvt56L7KznU0BgMq0DjJDvmWuWOs6wwWHj9SF69BvsHXV
+A9tKuVHSKq/S9dFqv+Ucz3L+ITYCZSpZubKCfUbRPvCMTl4Aw1lF+JwCzpiB9GCx
+kxJdN+HVuHJonmcSku1V/lP/zSylkHWGC4YvRwmRcZMIPedTfvYtIWHzRXIpMwjN
+WD2BSiHGqqh0U2KFe+drwrZZEYjLfS0urwgIsdnS+BIfDATaMyP5W++iKZ1G9QvD
+bbi+Lyye9jnJNhJvFUHA5df33jn3avfBMFgsToFqWw+nmLTrJyco+kaEBSSnhD5l
+sl1S/Vc7jrZgX1Hz4iiPM8t6c8h1hH/eck5HuqQcP114x/EP3LPlKGdy3MRZcvWO
+VCrI9A3zQitbmiwNC1kml6S50/XrRJL/bLrBPqlg2p42t/LMsq6KKfUDzE9ibooR
+O7gxMd6Bk4B2R8RQtF0uQ6X/KQK4U65RKRjgQznMK+eQfJ/z4D1i1lr2APp8QwiS
+UXMG4zLnJThb7G6z1Z2HtS5RL+0LuOaFj5MH4ft7PTAhvaVybGeGb+qv5s2Hhva/
+RAvkB/wyx/3uCLAJDfDYSH+lFu9hak0+eLY59Qv9hVziTqIOXSTuxiumVAu/gWhS
+MWdeZRgt8pObdLGV1eaW
+=/0Ti
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v6.2.0.md b/locale/uk/blog/release/v6.2.0.md
new file mode 100755
index 0000000000000..da06e58a7a5f3
--- /dev/null
+++ b/locale/uk/blog/release/v6.2.0.md
@@ -0,0 +1,227 @@
+---
+date: 2016-05-17T21:12:15.115Z
+version: 6.2.0
+category: release
+title: Node v6.2.0 (Current)
+slug: node-v6-2-0
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+### Notable Changes
+
+- **buffer**: fix lastIndexOf and indexOf in various edge cases (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+- **child_process**: use /system/bin/sh on android (Ben Noordhuis) [#6745](https://github.com/nodejs/node/pull/6745)
+- **deps**:
+  - upgrade npm to 3.8.9 (Rebecca Turner) [#6664](https://github.com/nodejs/node/pull/6664)
+  - upgrade to V8 5.0.71.47 (Ali Ijaz Sheikh) [#6572](https://github.com/nodejs/node/pull/6572)
+  - upgrade libuv to 1.9.1 (Saúl Ibarra Corretgé) [#6796](https://github.com/nodejs/node/pull/6796)
+  - Intl: ICU 57 bump (Steven R. Loomis) [#6088](https://github.com/nodejs/node/pull/6088)
+- **repl**:
+  - copying tabs shouldn't trigger completion (Eugene Obrezkov) [#5958](https://github.com/nodejs/node/pull/5958)
+  - exports `Recoverable` (Blake Embrey) [#3488](https://github.com/nodejs/node/pull/3488)
+- **src**: add O_NOATIME constant (Rich Trott) [#6492](https://github.com/nodejs/node/pull/6492)
+- **src,module**: add --preserve-symlinks command line flag (James M Snell) [#6537](https://github.com/nodejs/node/pull/6537)
+- **util**: adhere to `noDeprecation` set at runtime (Anna Henningsen) [#6683](https://github.com/nodejs/node/pull/6683)
+
+As of this release the 6.X line now includes 64-bit binaries for Linux on Power Systems
+running in big endian mode in addition to the existing 64-bit binaries for running in little endian mode.
+
+### Commits
+
+* [[`955c90d725`](https://github.com/nodejs/node/commit/955c90d725)] - **benchmark,test,lib**: remove extra spaces (Rich Trott) [#6645](https://github.com/nodejs/node/pull/6645)
+* [[`9cd14ced09`](https://github.com/nodejs/node/commit/9cd14ced09)] - **buffer**: fix UCS2 indexOf for odd buffer length (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`a550ddbf3c`](https://github.com/nodejs/node/commit/a550ddbf3c)] - **buffer**: fix needle length misestimation for UCS2 (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`6fc20c5a97`](https://github.com/nodejs/node/commit/6fc20c5a97)] - **buffer**: fix lastIndexOf crash for overlong needle (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`44015754a3`](https://github.com/nodejs/node/commit/44015754a3)] - **buffer**: fix lastIndexOf index underflow issue (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`6032dc25cc`](https://github.com/nodejs/node/commit/6032dc25cc)] - **build**: add Make `doc-only` target (Jesse McCarthy) [#3888](https://github.com/nodejs/node/pull/3888)
+* [[`3af9382a5d`](https://github.com/nodejs/node/commit/3af9382a5d)] - **build**: don't compile with -B, redux (Ben Noordhuis) [#6650](https://github.com/nodejs/node/pull/6650)
+* [[`5149d66702`](https://github.com/nodejs/node/commit/5149d66702)] - **build**: fix DESTCPU detection for binary target (Richard Lau) [#6310](https://github.com/nodejs/node/pull/6310)
+* [[`6eed6a3ac0`](https://github.com/nodejs/node/commit/6eed6a3ac0)] - **build,test**: fix build-addons dependency chain (Ben Noordhuis) [#6652](https://github.com/nodejs/node/pull/6652)
+* [[`e0240ab592`](https://github.com/nodejs/node/commit/e0240ab592)] - **child_process**: use /system/bin/sh on android (Ben Noordhuis) [#6745](https://github.com/nodejs/node/pull/6745)
+* [[`e8c9f01cdd`](https://github.com/nodejs/node/commit/e8c9f01cdd)] - **crypto**: disable ssl compression at build time (Ben Noordhuis) [#6582](https://github.com/nodejs/node/pull/6582)
+* [[`62690aa0be`](https://github.com/nodejs/node/commit/62690aa0be)] - **deps**: update comment about PURIFY define (Ben Noordhuis) [#6582](https://github.com/nodejs/node/pull/6582)
+* [[`bddf413412`](https://github.com/nodejs/node/commit/bddf413412)] - **deps**: upgrade npm to 3.8.9 (Rebecca Turner) [#6664](https://github.com/nodejs/node/pull/6664)
+* [[`a6ca5e559a`](https://github.com/nodejs/node/commit/a6ca5e559a)] - **deps**: upgrade to V8 5.0.71.47 (Ali Ijaz Sheikh) [#6572](https://github.com/nodejs/node/pull/6572)
+* [[`16159c23ed`](https://github.com/nodejs/node/commit/16159c23ed)] - **deps**: limit regress/regress-crbug-514081 v8 test (Michael Dawson) [#6678](https://github.com/nodejs/node/pull/6678)
+* [[`2d84ac735a`](https://github.com/nodejs/node/commit/2d84ac735a)] - **deps**: upgrade libuv to 1.9.1 (Saúl Ibarra Corretgé) [#6796](https://github.com/nodejs/node/pull/6796)
+* [[`7a6d2ad181`](https://github.com/nodejs/node/commit/7a6d2ad181)] - **deps**: Intl: Check in "small-icu" 57.1 (Steven R. Loomis) [#6088](https://github.com/nodejs/node/pull/6088)
+* [[`ee1e5a267d`](https://github.com/nodejs/node/commit/ee1e5a267d)] - **deps**: Intl: ICU 57 bump (Steven R. Loomis) [#6088](https://github.com/nodejs/node/pull/6088)
+* [[`a4ed7dfb3d`](https://github.com/nodejs/node/commit/a4ed7dfb3d)] - **doc**: Add CTC meeting minutes for 2016-05-04 (Michael Dawson) [#6579](https://github.com/nodejs/node/pull/6579)
+* [[`5c7da210df`](https://github.com/nodejs/node/commit/5c7da210df)] - **doc**: refactor the changelog by version (James M Snell) [#6503](https://github.com/nodejs/node/pull/6503)
+* [[`4f2a55f92f`](https://github.com/nodejs/node/commit/4f2a55f92f)] - **doc**: fix issues related to page scrolling (Roman Reiss)
+* [[`b4fb95eade`](https://github.com/nodejs/node/commit/b4fb95eade)] - **doc**: add `added:` information for assert (Rich Trott) [#6688](https://github.com/nodejs/node/pull/6688)
+* [[`64fcba2a2e`](https://github.com/nodejs/node/commit/64fcba2a2e)] - **doc**: appendFileSync accepts fd as well (Faiz Halde) [#6707](https://github.com/nodejs/node/pull/6707)
+* [[`520369d8e0`](https://github.com/nodejs/node/commit/520369d8e0)] - **doc**: fix exec example in child_process (Evan Lucas) [#6660](https://github.com/nodejs/node/pull/6660)
+* [[`51d1960955`](https://github.com/nodejs/node/commit/51d1960955)] - **doc**: undocument fs.open's 'rs' mode (Saúl Ibarra Corretgé) [#6732](https://github.com/nodejs/node/pull/6732)
+* [[`f1c773d18b`](https://github.com/nodejs/node/commit/f1c773d18b)] - **doc**: add `added:` information for v8 (Rich Trott) [#6684](https://github.com/nodejs/node/pull/6684)
+* [[`29b28a233c`](https://github.com/nodejs/node/commit/29b28a233c)] - **doc**: server.listen truncates socket path on unix (Jean Regisser) [#6659](https://github.com/nodejs/node/pull/6659)
+* [[`c1d5f2e96e`](https://github.com/nodejs/node/commit/c1d5f2e96e)] - **doc**: update releases.md with new changelog structure (James M Snell) [#6503](https://github.com/nodejs/node/pull/6503)
+* [[`d962fbafb2`](https://github.com/nodejs/node/commit/d962fbafb2)] - **doc**: "a" -> "an" in api/documentation.md (Anchika Agarwal) [#6689](https://github.com/nodejs/node/pull/6689)
+* [[`26e22e200a`](https://github.com/nodejs/node/commit/26e22e200a)] - **doc**: move the readme newcomers section (Jeremiah Senkpiel) [#6681](https://github.com/nodejs/node/pull/6681)
+* [[`8f526494b5`](https://github.com/nodejs/node/commit/8f526494b5)] - **doc**: fix deprecation warnings in addon examples (Ben Noordhuis) [#6652](https://github.com/nodejs/node/pull/6652)
+* [[`d34343f0de`](https://github.com/nodejs/node/commit/d34343f0de)] - **doc**: mention existence/purpose of module wrapper (Matt Harrison) [#6433](https://github.com/nodejs/node/pull/6433)
+* [[`5c154a87e0`](https://github.com/nodejs/node/commit/5c154a87e0)] - **doc**: add steps for running addons + npm tests (Myles Borins) [#6231](https://github.com/nodejs/node/pull/6231)
+* [[`6ea43d12f4`](https://github.com/nodejs/node/commit/6ea43d12f4)] - **doc**: improve onboarding-extras.md formatting (Jeremiah Senkpiel) [#6548](https://github.com/nodejs/node/pull/6548)
+* [[`38f5603e97`](https://github.com/nodejs/node/commit/38f5603e97)] - **doc**: fix linewrap in node.1 (Jeremiah Senkpiel) [#6532](https://github.com/nodejs/node/pull/6532)
+* [[`5b47accfa6`](https://github.com/nodejs/node/commit/5b47accfa6)] - **doc**: v8 options can use either `_` or `-` (Jeremiah Senkpiel) [#6532](https://github.com/nodejs/node/pull/6532)
+* [[`fa94a91bbd`](https://github.com/nodejs/node/commit/fa94a91bbd)] - **doc**: v8 functions as methods on v8 (Bryan English) [#6615](https://github.com/nodejs/node/pull/6615)
+* [[`d49b49e8b1`](https://github.com/nodejs/node/commit/d49b49e8b1)] - **doc**: discourage use of util.inherits (Robert Jefe Lindstaedt) [#6514](https://github.com/nodejs/node/pull/6514)
+* [[`925fc36dd9`](https://github.com/nodejs/node/commit/925fc36dd9)] - **doc**: add `added:` information for os (Bryan English) [#6609](https://github.com/nodejs/node/pull/6609)
+* [[`58cd11c844`](https://github.com/nodejs/node/commit/58cd11c844)] - **doc**: add `added:` information for process (Bryan English) [#6589](https://github.com/nodejs/node/pull/6589)
+* [[`d5f7f24aec`](https://github.com/nodejs/node/commit/d5f7f24aec)] - **doc**: add `added:` information for url (Bryan English) [#6593](https://github.com/nodejs/node/pull/6593)
+* [[`715b48c1d3`](https://github.com/nodejs/node/commit/715b48c1d3)] - **doc**: add `added:` information for querystring (Bryan English) [#6593](https://github.com/nodejs/node/pull/6593)
+* [[`04697a5023`](https://github.com/nodejs/node/commit/04697a5023)] - **doc**: correct anchors for buffer.md (Jackson Tian) [#6542](https://github.com/nodejs/node/pull/6542)
+* [[`2d677411a4`](https://github.com/nodejs/node/commit/2d677411a4)] - **doc**: add `added:` information for buffer (Anna Henningsen) [#6495](https://github.com/nodejs/node/pull/6495)
+* [[`49af20c2e6`](https://github.com/nodejs/node/commit/49af20c2e6)] - **doc**: update fs callback example error stack (DavidCai) [#6617](https://github.com/nodejs/node/pull/6617)
+* [[`9196d87704`](https://github.com/nodejs/node/commit/9196d87704)] - **doc**: add `added:` info for `string_decoder` (Rich Trott) [#6741](https://github.com/nodejs/node/pull/6741)
+* [[`688f563ca8`](https://github.com/nodejs/node/commit/688f563ca8)] - **doc**: update vm.runInDebugContext() example (Ben Noordhuis) [#6757](https://github.com/nodejs/node/pull/6757)
+* [[`2273971a69`](https://github.com/nodejs/node/commit/2273971a69)] - **doc**: readline.emitKeypressEvents and raw mode (Arve Seljebu) [#6628](https://github.com/nodejs/node/pull/6628)
+* [[`1c7b6e276f`](https://github.com/nodejs/node/commit/1c7b6e276f)] - **doc**: improve zlib docs (James M Snell) [#6746](https://github.com/nodejs/node/pull/6746)
+* [[`897934a719`](https://github.com/nodejs/node/commit/897934a719)] - **doc**: copyedit maxBuffer note for child_process (Rich Trott) [#6760](https://github.com/nodejs/node/pull/6760)
+* [[`c1bf3fc0b1`](https://github.com/nodejs/node/commit/c1bf3fc0b1)] - **doc**: fix links in socket.connecting (Kirill Fomichev) [#6657](https://github.com/nodejs/node/pull/6657)
+* [[`ad895f490b`](https://github.com/nodejs/node/commit/ad895f490b)] - **doc**: trim GitHub template comments (Rich Trott) [#6755](https://github.com/nodejs/node/pull/6755)
+* [[`af096f1172`](https://github.com/nodejs/node/commit/af096f1172)] - **doc**: add `added` info for `dgram.setBroadcast()` (Rich Trott) [#6750](https://github.com/nodejs/node/pull/6750)
+* [[`e8c0dba4bd`](https://github.com/nodejs/node/commit/e8c0dba4bd)] - **doc,events**: fix a link typo (yorkie) [#6640](https://github.com/nodejs/node/pull/6640)
+* [[`f31a5ec34a`](https://github.com/nodejs/node/commit/f31a5ec34a)] - **handle_wrap**: IsRefed() -> HasRef() (Jeremiah Senkpiel) [#6546](https://github.com/nodejs/node/pull/6546)
+* [[`cc2af793d2`](https://github.com/nodejs/node/commit/cc2af793d2)] - ***Revert*** "**handle_wrap**: IsRefed -> Unrefed, no isAlive check" (Jeremiah Senkpiel) [#6546](https://github.com/nodejs/node/pull/6546)
+* [[`2000072903`](https://github.com/nodejs/node/commit/2000072903)] - **handle_wrap**: IsRefed -> Unrefed, no isAlive check (Jeremiah Senkpiel) [#6204](https://github.com/nodejs/node/pull/6204)
+* [[`d3132048cb`](https://github.com/nodejs/node/commit/d3132048cb)] - **(SEMVER-MINOR)** **handle_wrap**: expose an `isRefed()` check to JS (Jeremiah Senkpiel) [#5834](https://github.com/nodejs/node/pull/5834)
+* [[`59666502c5`](https://github.com/nodejs/node/commit/59666502c5)] - **intl**: Don't crash if v8BreakIterator not available (Steven R. Loomis) [#4253](https://github.com/nodejs/node/pull/4253)
+* [[`74582aa590`](https://github.com/nodejs/node/commit/74582aa590)] - **lib**: replace legacy uses of __defineGetter__ (James M Snell) [#6768](https://github.com/nodejs/node/pull/6768)
+* [[`559c2583e0`](https://github.com/nodejs/node/commit/559c2583e0)] - **lib,test**: update in preparation for linter update (Rich Trott) [#6498](https://github.com/nodejs/node/pull/6498)
+* [[`226b9668db`](https://github.com/nodejs/node/commit/226b9668db)] - **(SEMVER-MINOR)** **repl**: copying tabs shouldn't trigger completion (Eugene Obrezkov) [#5958](https://github.com/nodejs/node/pull/5958)
+* [[`ce2d5be4a1`](https://github.com/nodejs/node/commit/ce2d5be4a1)] - **(SEMVER-MINOR)** **repl**: exports `Recoverable` (Blake Embrey) [#3488](https://github.com/nodejs/node/pull/3488)
+* [[`635357958d`](https://github.com/nodejs/node/commit/635357958d)] - **repl**: create history file with mode 0600 (Carl Lei) [#3394](https://github.com/nodejs/node/pull/3394)
+* [[`e3920d12ef`](https://github.com/nodejs/node/commit/e3920d12ef)] - **src**: fix check-imports.py linter errors (Sakthipriyan Vairamani) [#6105](https://github.com/nodejs/node/pull/6105)
+* [[`bbf3b3ebbb`](https://github.com/nodejs/node/commit/bbf3b3ebbb)] - **src**: simplify handlewrap state tracking logic (Ben Noordhuis) [#6395](https://github.com/nodejs/node/pull/6395)
+* [[`965274d384`](https://github.com/nodejs/node/commit/965274d384)] - **src**: use libuv's refcounting directly (Ben Noordhuis) [#6395](https://github.com/nodejs/node/pull/6395)
+* [[`316871f268`](https://github.com/nodejs/node/commit/316871f268)] - **src**: fix -Wunused-variable compiler warning (Ben Noordhuis) [#6129](https://github.com/nodejs/node/pull/6129)
+* [[`1def098b9f`](https://github.com/nodejs/node/commit/1def098b9f)] - **src**: fix sporadic deadlock in SIGUSR1 handler (Ben Noordhuis) [#5904](https://github.com/nodejs/node/pull/5904)
+* [[`477e61db9f`](https://github.com/nodejs/node/commit/477e61db9f)] - **src**: don't use locale-sensitive strcasecmp() (Ben Noordhuis) [#6582](https://github.com/nodejs/node/pull/6582)
+* [[`1e99643fc9`](https://github.com/nodejs/node/commit/1e99643fc9)] - **src**: remove unused #include statement (Ben Noordhuis) [#6582](https://github.com/nodejs/node/pull/6582)
+* [[`62593bd44c`](https://github.com/nodejs/node/commit/62593bd44c)] - **src**: remove pre-openssl 1.0 legacy code (Ben Noordhuis) [#6582](https://github.com/nodejs/node/pull/6582)
+* [[`27c17ce9d1`](https://github.com/nodejs/node/commit/27c17ce9d1)] - **src**: fix FindFirstCharacter argument alignment (Anna Henningsen) [#6511](https://github.com/nodejs/node/pull/6511)
+* [[`37736f4dad`](https://github.com/nodejs/node/commit/37736f4dad)] - **(SEMVER-MINOR)** **src**: add O_NOATIME constant (Rich Trott) [#6492](https://github.com/nodejs/node/pull/6492)
+* [[`bd4454fa0f`](https://github.com/nodejs/node/commit/bd4454fa0f)] - **src,lib**: minor --debug-brk cleanup (Ali Ijaz Sheikh) [#6599](https://github.com/nodejs/node/pull/6599)
+* [[`95b7560d8e`](https://github.com/nodejs/node/commit/95b7560d8e)] - **(SEMVER-MINOR)** **src,module**: add --preserve-symlinks command line flag (James M Snell) [#6537](https://github.com/nodejs/node/pull/6537)
+* [[`8a7e68ff83`](https://github.com/nodejs/node/commit/8a7e68ff83)] - **test**: check that 2nd handle.close() call is a nop (Ben Noordhuis) [#6395](https://github.com/nodejs/node/pull/6395)
+* [[`ccbc78cfc6`](https://github.com/nodejs/node/commit/ccbc78cfc6)] - **test**: remove common.getServiceName() (Rich Trott) [#6709](https://github.com/nodejs/node/pull/6709)
+* [[`8c634d78f8`](https://github.com/nodejs/node/commit/8c634d78f8)] - **test**: favor strictEqual() in addon test (Rich Trott) [#6704](https://github.com/nodejs/node/pull/6704)
+* [[`1389a4fc5e`](https://github.com/nodejs/node/commit/1389a4fc5e)] - **test**: fix flaky test-preload (Rich Trott) [#6728](https://github.com/nodejs/node/pull/6728)
+* [[`adb2d610e6`](https://github.com/nodejs/node/commit/adb2d610e6)] - **test**: include component in tap output (Ben Noordhuis) [#6653](https://github.com/nodejs/node/pull/6653)
+* [[`abb063a6a3`](https://github.com/nodejs/node/commit/abb063a6a3)] - **test**: fix test-debugger-repl-break-in-module (Rich Trott) [#6686](https://github.com/nodejs/node/pull/6686)
+* [[`5701599767`](https://github.com/nodejs/node/commit/5701599767)] - **test**: fix test-debugger-repl-term (Rich Trott) [#6682](https://github.com/nodejs/node/pull/6682)
+* [[`71c91747ef`](https://github.com/nodejs/node/commit/71c91747ef)] - **test**: add tests for stream3 buffering using cork (Alex J Burke) [#6493](https://github.com/nodejs/node/pull/6493)
+* [[`b1f58edd54`](https://github.com/nodejs/node/commit/b1f58edd54)] - **test**: abstract skip functionality to common (Jeremiah Senkpiel) [#6697](https://github.com/nodejs/node/pull/6697)
+* [[`7d3f5751b3`](https://github.com/nodejs/node/commit/7d3f5751b3)] - **test**: make sure O_NOATIME is present only in Linux (Sakthipriyan Vairamani) [#6614](https://github.com/nodejs/node/pull/6614)
+* [[`75adc6a026`](https://github.com/nodejs/node/commit/75adc6a026)] - **test**: move test-debugger-debug-brk to sequential (Rich Trott) [#6731](https://github.com/nodejs/node/pull/6731)
+* [[`0bc1784529`](https://github.com/nodejs/node/commit/0bc1784529)] - **test**: refactor doctool tests (Rich Trott) [#6719](https://github.com/nodejs/node/pull/6719)
+* [[`89b25fac4c`](https://github.com/nodejs/node/commit/89b25fac4c)] - **test**: fix test-process-exec-argv flakiness (Santiago Gimeno) [#6575](https://github.com/nodejs/node/pull/6575)
+* [[`3f9d72408f`](https://github.com/nodejs/node/commit/3f9d72408f)] - **test**: pass python path to node-gyp (hefangshi) [#6646](https://github.com/nodejs/node/pull/6646)
+* [[`0c62bd13fb`](https://github.com/nodejs/node/commit/0c62bd13fb)] - **test**: ensure test-npm-install uses correct node (Myles Borins) [#6658](https://github.com/nodejs/node/pull/6658)
+* [[`1b71231dd2`](https://github.com/nodejs/node/commit/1b71231dd2)] - **test**: fix test-vm-cached-data to work with old v8 (Myles Borins) [#6317](https://github.com/nodejs/node/pull/6317)
+* [[`0eb25cb4b5`](https://github.com/nodejs/node/commit/0eb25cb4b5)] - **test**: test preloaded modules using stdin or repl (Bradley Meck) [#2253](https://github.com/nodejs/node/pull/2253)
+* [[`577e132f00`](https://github.com/nodejs/node/commit/577e132f00)] - **test**: fix test-debugger-pid (Santiago Gimeno) [#6584](https://github.com/nodejs/node/pull/6584)
+* [[`d74062454b`](https://github.com/nodejs/node/commit/d74062454b)] - **test**: make stdout buffer test more robust (Rich Trott) [#6633](https://github.com/nodejs/node/pull/6633)
+* [[`f264749c5c`](https://github.com/nodejs/node/commit/f264749c5c)] - **test**: build addons with V8_DEPRECATION_WARNINGS=1 (Ben Noordhuis) [#6652](https://github.com/nodejs/node/pull/6652)
+* [[`01f010f669`](https://github.com/nodejs/node/commit/01f010f669)] - **test**: allow out-of-order replies in dgram tests (Anna Henningsen) [#6607](https://github.com/nodejs/node/pull/6607)
+* [[`be241c3262`](https://github.com/nodejs/node/commit/be241c3262)] - **test**: run known_issues tests in CI (Rich Trott) [#6559](https://github.com/nodejs/node/pull/6559)
+* [[`8141c2fce2`](https://github.com/nodejs/node/commit/8141c2fce2)] - **test**: add tests for console.\[info|error|warn\] (Bryan English) [#6538](https://github.com/nodejs/node/pull/6538)
+* [[`83dab801e2`](https://github.com/nodejs/node/commit/83dab801e2)] - **test**: fix unreliable known_issues test (Rich Trott) [#6555](https://github.com/nodejs/node/pull/6555)
+* [[`8c434e6d84`](https://github.com/nodejs/node/commit/8c434e6d84)] - **test**: unmark test-http-regr-gh-2928 as flaky (Rich Trott) [#6540](https://github.com/nodejs/node/pull/6540)
+* [[`916e694b2b`](https://github.com/nodejs/node/commit/916e694b2b)] - **test**: avoid test-cluster-master-* flakiness (Stefan Budeanu) [#6531](https://github.com/nodejs/node/pull/6531)
+* [[`be5386e0cf`](https://github.com/nodejs/node/commit/be5386e0cf)] - **test,dgram**: add tests for setBroadcast() (Rich Trott) [#6750](https://github.com/nodejs/node/pull/6750)
+* [[`1370fdcad5`](https://github.com/nodejs/node/commit/1370fdcad5)] - **test,tools**: test yaml parsing of doctool (Anna Henningsen) [#6495](https://github.com/nodejs/node/pull/6495)
+* [[`347abf341d`](https://github.com/nodejs/node/commit/347abf341d)] - **tools**: enforce linting for unix-style line endings (Rich Trott) [#6685](https://github.com/nodejs/node/pull/6685)
+* [[`a63c556c11`](https://github.com/nodejs/node/commit/a63c556c11)] - **tools**: remove the minifying logic (Sakthipriyan Vairamani) [#6636](https://github.com/nodejs/node/pull/6636)
+* [[`efcbafa3f7`](https://github.com/nodejs/node/commit/efcbafa3f7)] - **tools**: fix regression in doctool (Myles Borins) [#6680](https://github.com/nodejs/node/pull/6680)
+* [[`edb29b8096`](https://github.com/nodejs/node/commit/edb29b8096)] - **tools**: lint for object literal spacing (Rich Trott) [#6592](https://github.com/nodejs/node/pull/6592)
+* [[`6806ebb608`](https://github.com/nodejs/node/commit/6806ebb608)] - **tools**: lint for use of space in template strings (Rich Trott) [#6591](https://github.com/nodejs/node/pull/6591)
+* [[`341eaf202e`](https://github.com/nodejs/node/commit/341eaf202e)] - **tools**: update marked dependency (Daniel Wang) [#6396](https://github.com/nodejs/node/pull/6396)
+* [[`94f82553aa`](https://github.com/nodejs/node/commit/94f82553aa)] - **tools**: allow multiple added: version entries (Anna Henningsen) [#6495](https://github.com/nodejs/node/pull/6495)
+* [[`1de25f208c`](https://github.com/nodejs/node/commit/1de25f208c)] - **tools**: do not build addons during compilation (Myles Borins) [#6723](https://github.com/nodejs/node/pull/6723)
+* [[`26805c97d0`](https://github.com/nodejs/node/commit/26805c97d0)] - **tools**: fix tools/doc/addon-verify.js regression (Anna Henningsen) [#6652](https://github.com/nodejs/node/pull/6652)
+* [[`cea17775e0`](https://github.com/nodejs/node/commit/cea17775e0)] - **tools**: parse documentation metadata (Tristian Flanagan) [#6495](https://github.com/nodejs/node/pull/6495)
+* [[`a568ad4205`](https://github.com/nodejs/node/commit/a568ad4205)] - **tools**: add mock-y js-yaml dependency to doctool (Anna Henningsen) [#6495](https://github.com/nodejs/node/pull/6495)
+* [[`dce6413576`](https://github.com/nodejs/node/commit/dce6413576)] - **tools**: Check in tools for shrinking ICU size, change default to small-icu (Steven R. Loomis) [#6088](https://github.com/nodejs/node/pull/6088)
+* [[`d629f265fe`](https://github.com/nodejs/node/commit/d629f265fe)] - **tools**: update ESLint to 2.9.0 (Rich Trott) [#6498](https://github.com/nodejs/node/pull/6498)
+* [[`6aa92d5a98`](https://github.com/nodejs/node/commit/6aa92d5a98)] - **tools**: disallow multiple spaces except indentation (Rich Trott) [#6645](https://github.com/nodejs/node/pull/6645)
+* [[`ceeae4b180`](https://github.com/nodejs/node/commit/ceeae4b180)] - **tools,test**: make argument linting more stringent (Rich Trott) [#6720](https://github.com/nodejs/node/pull/6720)
+* [[`6d1527bb37`](https://github.com/nodejs/node/commit/6d1527bb37)] - **util**: fix invalid date output with util.inspect (Rumkin) [#6504](https://github.com/nodejs/node/pull/6504)
+* [[`1d6c17efd7`](https://github.com/nodejs/node/commit/1d6c17efd7)] - **util**: adhere to `noDeprecation` set at runtime (Anna Henningsen) [#6683](https://github.com/nodejs/node/pull/6683)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v6.2.0/node-v6.2.0-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v6.2.0/node-v6.2.0-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v6.2.0/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v6.2.0/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v6.2.0/node-v6.2.0.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v6.2.0/node-v6.2.0-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v6.2.0/node-v6.2.0.tar.gz<br>
+Other release files: https://nodejs.org/dist/v6.2.0/<br>
+Documentation: https://nodejs.org/docs/v6.2.0/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+1c8c16bb3df22c7c98cf0c118bd183838b848e36ef1448992cf511c044339823  node-v6.2.0-darwin-x64.tar.gz
+e1c890b47f078a840896b05a3111080e6f410103cc6d338de2a32ebc5a58d545  node-v6.2.0-darwin-x64.tar.xz
+1127a30aa0e728786e4c1b2a568dd74eab8957a271764cec06d3562febee6baa  node-v6.2.0-headers.tar.gz
+7ac466b74c01f1d0e0cf46d62dba32392b6fa4157a8b957fbdec490701d06d35  node-v6.2.0-headers.tar.xz
+bac296f56d071e147e33e7f027efc8b0422a786e3943b18c64c8c8fbf2abae96  node-v6.2.0-linux-arm64.tar.gz
+d81cd7d9a04a68d5a6bd9b36c410e0ac3394d1cec03c647737a41d5772d4f542  node-v6.2.0-linux-arm64.tar.xz
+c297855fd11dc9d58c523f3665b18e5ff932145aabb27c389da3b6b27553fe37  node-v6.2.0-linux-armv6l.tar.gz
+3c0fda6205425a641cac8b71f522bdef28de0d17fa53d3b0987f66a58c416ee1  node-v6.2.0-linux-armv6l.tar.xz
+4804a486b0b0db0f52fc273ccf688f83c06e3fc17641824877e2921518d0e50d  node-v6.2.0-linux-armv7l.tar.gz
+7316c8026c5da22cbda06c6b8f556a326c7c2c81408b9a1f04a01859c6d95787  node-v6.2.0-linux-armv7l.tar.xz
+fbbeaaa5431c6cc5007567c35f13b87c2917d704ae6fd8f6db7792f1ba5349b0  node-v6.2.0-linux-ppc64le.tar.gz
+75d3ed1dda3e29e12a708a4c5084f7a4aaa5485f10a68b4e21c8fe7333720cc1  node-v6.2.0-linux-ppc64le.tar.xz
+69f8f3ffec15f1cddca3f8fca53471123e22db40ae58bea9bd65503d900267d8  node-v6.2.0-linux-ppc64.tar.gz
+7697c259171529ba7ea902437ef8186bde64fb9613ee77ade882549b3cc43ffd  node-v6.2.0-linux-ppc64.tar.xz
+661dba369c277603fa6d0182c4ea7ff074ba6bacd19171826271f872afd6aaa7  node-v6.2.0-linux-x64.tar.gz
+ab28c6af235045def1f65fca7f4848de3c2de4fb62ebce37052f1a10f0b40263  node-v6.2.0-linux-x64.tar.xz
+47c3d613362afd9c64e6468fba0d3f6407ead7d3ea6447deb297c6551dd9d0d4  node-v6.2.0-linux-x86.tar.gz
+6aaf649e9798fdc40c03aa27f63715cfe4c33916f8081607067bdfc16a2a2d9a  node-v6.2.0-linux-x86.tar.xz
+4ce1462c3cf3c327891154ab076f2f5ef16e61b150001d90d8dcaf2ae4e49772  node-v6.2.0.pkg
+f1e8447ff644598c2c24eb6effa12a9d32c6fdad7fa832065dd5f381339b723f  node-v6.2.0-sunos-x64.tar.gz
+8dacb9a2fbc71c78a157c1c6cf1ccb126b7f919775834e7570821b19514603ae  node-v6.2.0-sunos-x64.tar.xz
+bbfce19c47265676fb44a6a1fa10e2e9ec710c8a332a801aa7e3e58648e851a3  node-v6.2.0-sunos-x86.tar.gz
+effdeef23786210846c4d19249bac2ddbabc9f8647deb6803345725acbadec73  node-v6.2.0-sunos-x86.tar.xz
+fcfd81847d78abb690aafaf46223d3b59aedc54fb200a2ab2bfd9a39ad6e94b9  node-v6.2.0.tar.gz
+8633fe606fd1f2235d26901c6bc4c11b5b88fd3c772af18a902e3efd1254e492  node-v6.2.0.tar.xz
+bd1d766e15f75f67befa76738bc0212ee3016444eb0396b29c6fc319658e21a2  node-v6.2.0-x64.msi
+e0e20da53fd7e8ccdd61acf93b4f268189b32c43c15516a272df57808d94b941  node-v6.2.0-x86.msi
+6e8aff84a875d60785d23a3c8fbf6cff82835dde0886e5ed476150b82f1f61fd  win-x64/node.exe
+df99926fcfb98fdf764ab3a4e46fd31ee23863b26bb9b24fcd3b6398aff21d13  win-x64/node.lib
+8003b76b7e45cfd6d44308e17e7d055ed3dd9322a5c0a3bb8f66670a5e8ecb5f  win-x86/node.exe
+9fd0bd7229d637d5e9d2c02bb0325a99fd38bbed6c2f7a37942d6a5951fac344  win-x86/node.lib
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJXO4jZAAoJELY7U1pMIGypvGgP/RWxnq3GhqgMKXEMnkljpSen
+KDNHGGaZJrA6LU6L3my1v0GsP+Pfj+okbzHcZ5jwg9p2tTjXRFBnC+UFz+00G86d
+MFzX1Y9MZk4+9OkJWjO0c5carxtYD68nryohJsIMMh2ipos47SDqYwO7oLVDEZAd
+orc5K1Vtpvkx66VEAVAgTo4eEmyDM3NLHve5oaOHnJ5kdasqqDj+LFXYUT5rKDoQ
+yUMbIZbvj8zrqCd76XTJpw/e9RmQ3v9G2aBXQ+jhzxtADu0vevoyTldld/CiMTkX
+4mDhGMP3AToiF/o5F91GmuzVQJnnOowS02/4k5UpUIyRAvD25podlIJHHs+M1lDs
+NQC7W691mD6WRf6OZROkrWOvrYpoIYYn79GBxyTzLZz2bYCmGxjttB/ETnLpG7mf
+CjMDjOq6B8LTC24JtvqYDt6HIlkOkzZ5vOxAqCqCQC3l6hQUEqVAp7Dack/FOHNv
+pbUqSQwfSu9j+gcoMkUmNDdjSeWEyCHN09XH3dFOQ1Cd6olRh900nkhITmTKEsD7
+U7QZDMp7s6QmtbzF62TskH8jj/QIhQx6qFuyyquHpWAwggrcWbauhMKQFAHc9vI5
+iz2XUKB/yKlcFVomojq+sm4NoBvgy4IZAIHUjv+g4yYzPHmyZrP0I4bMUT9s/1b6
+LunWBUGBWXCXRm4Q6Qar
+=Q/h1
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v6.2.1.md b/locale/uk/blog/release/v6.2.1.md
new file mode 100755
index 0000000000000..1b2c20c8d0977
--- /dev/null
+++ b/locale/uk/blog/release/v6.2.1.md
@@ -0,0 +1,234 @@
+---
+date: 2016-06-02T22:47:05.512Z
+version: 6.2.1
+category: release
+title: Node v6.2.1 (Current)
+slug: node-v6-2-1
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+### Notable changes
+
+* **buffer**: Ignore negative lengths in calls to `Buffer()` and `Buffer.allocUnsafe()`. This fixes a possible security concern (reported by Feross Aboukhadijeh) where user input is passed unchecked to the Buffer constructor or `allocUnsafe()` as it can expose parts of the memory slab used by other Buffers in the application. Note that negative lengths are not supported by the Buffer API and user input to the constructor should always be sanitised and type-checked. (Anna Henningsen) [#7051](https://github.com/nodejs/node/pull/7051)
+* **npm**: Upgrade npm to 3.9.3 (Kat Marchán) [#7030](https://github.com/nodejs/node/pull/7030)
+  - [`npm/npm@42d71be`](https://github.com/npm/npm/commit/42d71be2cec674dd9e860ad414f53184f667620d) [npm/npm#12685](https://github.com/npm/npm/pull/12685) When using `npm ls <pkg>` without a semver specifier, `npm ls` would skip any packages in your tree that matched by name, but had a prerelease version in their `package.json`. ([@zkat](https://github.com/zkat))
+  - [`npm/npm@f04e05`](https://github.com/npm/npm/commit/df04e05af1f257a1903372e1baf334c0969fbdbd) [npm/npm#10013](https://github.com/npm/npm/issues/10013) `read-package-tree@5.1.4`: Fixes an issue where `npm install` would fail if your `node_modules` was symlinked. ([@iarna](https://github.com/iarna))
+  - [`b894413`](https://github.com/npm/npm/commit/b8944139a935680c4a267468bb2d3c3082b5609f) [#12372](https://github.com/npm/npm/issues/12372) Changing a nested dependency in an `npm-shrinkwrap.json` and then running `npm install` would not get up the updated package. This corrects that. ([@misterbyrne](https://github.com/misterbyrne))
+  - This release includes `npm@3.9.0`, which is the result of our Windows testing push -- the test suite (should) pass on Windows now. We're working on getting AppVeyor to a place where we can just rely on it like Travis.
+* **tty**: Default to blocking mode for stdio on OS X. A bug fix in libuv 1.9.0, introduced in Node.js v6.0.0, exposed problems with Node's use of non-blocking stdio, particularly on OS X which has a small output buffer. This change should fix CLI applications that have been having problems with output since Node.js v6.0.0 on OS X. The core team is continuing to address stdio concerns that exist across supported platforms and progress can be tracked at <https://github.com/nodejs/node/issues/6980>. (Jeremiah Senkpiel) [#6895](https://github.com/nodejs/node/pull/6895)
+* **V8**: Upgrade to V8 5.0.71.52. This includes a fix that addresses problems experienced by users of node-inspector since Node.js v6.0.0, see <https://github.com/node-inspector/node-inspector/issues/864> for details. (Michaël Zasso) [#6928](https://github.com/nodejs/node/pull/6928)
+
+### Commits
+
+* [[`99c05a1af0`](https://github.com/nodejs/node/commit/99c05a1af0)] - **async_wrap**: pass uid to JS as double (Trevor Norris) [#7096](https://github.com/nodejs/node/pull/7096)
+* [[`371be9cd80`](https://github.com/nodejs/node/commit/371be9cd80)] - **buffer**: ignore negative allocation lengths (Anna Henningsen) [#7051](https://github.com/nodejs/node/pull/7051)
+* [[`1bcc226edf`](https://github.com/nodejs/node/commit/1bcc226edf)] - **buffer**: fix dataview-set benchmark (Ingvar Stepanyan) [#6922](https://github.com/nodejs/node/pull/6922)
+* [[`98270c6d15`](https://github.com/nodejs/node/commit/98270c6d15)] - **buffer**: fix single digit hex string handling (Justin Sprigg) [#6775](https://github.com/nodejs/node/pull/6775)
+* [[`1fece2f8c0`](https://github.com/nodejs/node/commit/1fece2f8c0)] - **build**: re-add --ninja option to configure (Ehsan Akhgari) [#6780](https://github.com/nodejs/node/pull/6780)
+* [[`e7b03be191`](https://github.com/nodejs/node/commit/e7b03be191)] - **build**: update build-addons when node-gyp changes (Lance Ball) [#6787](https://github.com/nodejs/node/pull/6787)
+* [[`55c0b3e0e5`](https://github.com/nodejs/node/commit/55c0b3e0e5)] - **build**: unbreak configure with python 2.6 (Ben Noordhuis) [#6874](https://github.com/nodejs/node/pull/6874)
+* [[`0503681348`](https://github.com/nodejs/node/commit/0503681348)] - **child_process**: measure buffer length in bytes (Rich Trott) [#6764](https://github.com/nodejs/node/pull/6764)
+* [[`27d0eb054c`](https://github.com/nodejs/node/commit/27d0eb054c)] - **child_process**: emit IPC messages on next tick (cjihrig) [#6909](https://github.com/nodejs/node/pull/6909)
+* [[`b28468e0a7`](https://github.com/nodejs/node/commit/b28468e0a7)] - **child_process**: allow buffer encoding in spawnSync (cjihrig) [#6939](https://github.com/nodejs/node/pull/6939)
+* [[`6a62bb0070`](https://github.com/nodejs/node/commit/6a62bb0070)] - **cluster**: expose result of send() (cjihrig) [#6998](https://github.com/nodejs/node/pull/6998)
+* [[`2132d349b5`](https://github.com/nodejs/node/commit/2132d349b5)] - **cluster**: rewrite debug ports consistently (cjihrig) [#7050](https://github.com/nodejs/node/pull/7050)
+* [[`0bd8f4c4d8`](https://github.com/nodejs/node/commit/0bd8f4c4d8)] - **cluster**: reset handle index on close (Santiago Gimeno) [#6981](https://github.com/nodejs/node/pull/6981)
+* [[`93e150f1d6`](https://github.com/nodejs/node/commit/93e150f1d6)] - **cluster**: guard against undefined message handlers (cjihrig) [#6902](https://github.com/nodejs/node/pull/6902)
+* [[`28b73428e1`](https://github.com/nodejs/node/commit/28b73428e1)] - **cluster**: close ownerless handles on disconnect() (cjihrig) [#6909](https://github.com/nodejs/node/pull/6909)
+* [[`2184e772d2`](https://github.com/nodejs/node/commit/2184e772d2)] - **debugger**: propagate --debug-port= to debuggee (Ben Noordhuis) [#3470](https://github.com/nodejs/node/pull/3470)
+* [[`ded02b909f`](https://github.com/nodejs/node/commit/ded02b909f)] - **deps**: upgrade npm to 3.9.3 (Kat Marchán) [#7030](https://github.com/nodejs/node/pull/7030)
+* [[`bfd7b24c63`](https://github.com/nodejs/node/commit/bfd7b24c63)] - **deps**: upgrade to V8 5.0.71.52 (Michaël Zasso) [#6928](https://github.com/nodejs/node/pull/6928)
+* [[`8e6f8b2fb5`](https://github.com/nodejs/node/commit/8e6f8b2fb5)] - **dgram**: copy the list in send (Matteo Collina) [#6804](https://github.com/nodejs/node/pull/6804)
+* [[`588c76cd5c`](https://github.com/nodejs/node/commit/588c76cd5c)] - **dgram,test**: add addMembership/dropMembership tests (Rich Trott) [#6753](https://github.com/nodejs/node/pull/6753)
+* [[`e93198e86d`](https://github.com/nodejs/node/commit/e93198e86d)] - **doc**: edit pull request template (Rich Trott) [#7058](https://github.com/nodejs/node/pull/7058)
+* [[`1c1256718e`](https://github.com/nodejs/node/commit/1c1256718e)] - **doc**: addresses nits in string_decoder, url, util (Jeremiah Senkpiel) [#7026](https://github.com/nodejs/node/pull/7026)
+* [[`14b3ba35fc`](https://github.com/nodejs/node/commit/14b3ba35fc)] - **doc**: improve debugger doc prose (Rich Trott) [#7007](https://github.com/nodejs/node/pull/7007)
+* [[`3c2c4c8d5c`](https://github.com/nodejs/node/commit/3c2c4c8d5c)] - **doc**: update labels and CI info in onboarding doc (Rich Trott) [#7006](https://github.com/nodejs/node/pull/7006)
+* [[`b5e93c97f8`](https://github.com/nodejs/node/commit/b5e93c97f8)] - **doc**: fix typos in WORKING_GROUPS.md (Joao Andrade) [#7032](https://github.com/nodejs/node/pull/7032)
+* [[`f15448681a`](https://github.com/nodejs/node/commit/f15448681a)] - **doc**: buffers are not sent over IPC with a socket (Tim Kuijsten) [#6951](https://github.com/nodejs/node/pull/6951)
+* [[`3518ab93b1`](https://github.com/nodejs/node/commit/3518ab93b1)] - **doc**: minor improvements to util.md (Sakthipriyan Vairamani) [#6932](https://github.com/nodejs/node/pull/6932)
+* [[`216a3cdcce`](https://github.com/nodejs/node/commit/216a3cdcce)] - **doc**: add `added:` information for vm (Anna Henningsen) [#7011](https://github.com/nodejs/node/pull/7011)
+* [[`b30d07845d`](https://github.com/nodejs/node/commit/b30d07845d)] - **doc**: add `added:` information for console (Adrian Estrada) [#6995](https://github.com/nodejs/node/pull/6995)
+* [[`72d4692e94`](https://github.com/nodejs/node/commit/72d4692e94)] - **doc**: add info on what's used for fswatch on AIX (Michael Dawson) [#6837](https://github.com/nodejs/node/pull/6837)
+* [[`7c38327dee`](https://github.com/nodejs/node/commit/7c38327dee)] - **doc**: update process.hrtime docs to include optional parameter (doug.wade) [#6585](https://github.com/nodejs/node/pull/6585)
+* [[`0f17a28a00`](https://github.com/nodejs/node/commit/0f17a28a00)] - **doc**: improve server.listen() documentation prose (Rich Trott) [#7000](https://github.com/nodejs/node/pull/7000)
+* [[`3ae9f1469d`](https://github.com/nodejs/node/commit/3ae9f1469d)] - **doc**: improve `server.address()` doc text (Rich Trott) [#7001](https://github.com/nodejs/node/pull/7001)
+* [[`ae1bf83b6c`](https://github.com/nodejs/node/commit/ae1bf83b6c)] - **doc**: clarified use of sexual language in the CoC (Bryan Hughes) [#6973](https://github.com/nodejs/node/pull/6973)
+* [[`3909209e7a`](https://github.com/nodejs/node/commit/3909209e7a)] - **doc**: general improvements to tty.md (James M Snell) [#6931](https://github.com/nodejs/node/pull/6931)
+* [[`bc2efe22f6`](https://github.com/nodejs/node/commit/bc2efe22f6)] - **doc**: add `added: ` data for cli.md (Rich Trott) [#6960](https://github.com/nodejs/node/pull/6960)
+* [[`856638d0b7`](https://github.com/nodejs/node/commit/856638d0b7)] - **doc**: add `added:` information for child_process (Anna Henningsen) [#6927](https://github.com/nodejs/node/pull/6927)
+* [[`a5e3eddfbf`](https://github.com/nodejs/node/commit/a5e3eddfbf)] - **doc**: general improvements to url.md copy (James M Snell) [#6904](https://github.com/nodejs/node/pull/6904)
+* [[`b7ca0a2653`](https://github.com/nodejs/node/commit/b7ca0a2653)] - **doc**: add yorkie to collaborators (Yazhong Liu) [#7004](https://github.com/nodejs/node/pull/7004)
+* [[`a9b90a6952`](https://github.com/nodejs/node/commit/a9b90a6952)] - **doc**: general improvements to tls.md copy (James M Snell) [#6933](https://github.com/nodejs/node/pull/6933)
+* [[`5990a7fe91`](https://github.com/nodejs/node/commit/5990a7fe91)] - **doc**: fix broken references (Anna Henningsen) [#6941](https://github.com/nodejs/node/pull/6941)
+* [[`98e497bdad`](https://github.com/nodejs/node/commit/98e497bdad)] - **doc**: fix broken references in changelogs (Anna Henningsen) [#6942](https://github.com/nodejs/node/pull/6942)
+* [[`f3ae42168a`](https://github.com/nodejs/node/commit/f3ae42168a)] - **doc**: general improvements to string_decoder.md copy (James M Snell) [#6940](https://github.com/nodejs/node/pull/6940)
+* [[`8f623a3c75`](https://github.com/nodejs/node/commit/8f623a3c75)] - **doc**: add firedfox to collaborators (Daniel Wang) [#6961](https://github.com/nodejs/node/pull/6961)
+* [[`145a6b946a`](https://github.com/nodejs/node/commit/145a6b946a)] - **doc**: add bmeck to collaborators (Bradley Meck) [#6962](https://github.com/nodejs/node/pull/6962)
+* [[`95f8d59e0d`](https://github.com/nodejs/node/commit/95f8d59e0d)] - **doc**: remove "\" within backticks (Rod Machen) [#6952](https://github.com/nodejs/node/pull/6952)
+* [[`ee1865dd2f`](https://github.com/nodejs/node/commit/ee1865dd2f)] - **doc**: clarify buffer class (Steve Mao) [#6914](https://github.com/nodejs/node/pull/6914)
+* [[`db3d2a7b96`](https://github.com/nodejs/node/commit/db3d2a7b96)] - **doc**: fix typos in timers topic to aid readability (Kevin Donahue) [#6916](https://github.com/nodejs/node/pull/6916)
+* [[`0f0003fc54`](https://github.com/nodejs/node/commit/0f0003fc54)] - **doc**: add jhamhader to collaborators (Yuval Brik) [#6946](https://github.com/nodejs/node/pull/6946)
+* [[`f6558ec537`](https://github.com/nodejs/node/commit/f6558ec537)] - **doc**: add @othiym23 to list of collaborators (Forrest L Norvell) [#6945](https://github.com/nodejs/node/pull/6945)
+* [[`9fa1b19eda`](https://github.com/nodejs/node/commit/9fa1b19eda)] - **doc**: reference list of language-specific globals (Anna Henningsen) [#6900](https://github.com/nodejs/node/pull/6900)
+* [[`15f6224418`](https://github.com/nodejs/node/commit/15f6224418)] - **doc**: make doc-only -> fallback to user binary (Robert Jefe Lindstaedt) [#6906](https://github.com/nodejs/node/pull/6906)
+* [[`a320a019f1`](https://github.com/nodejs/node/commit/a320a019f1)] - **doc**: general improvements to util.md (James M Snell) [#6897](https://github.com/nodejs/node/pull/6897)
+* [[`527a8a4844`](https://github.com/nodejs/node/commit/527a8a4844)] - **doc**: add `added:` information for zlib (Anna Henningsen) [#6840](https://github.com/nodejs/node/pull/6840)
+* [[`cb8de85100`](https://github.com/nodejs/node/commit/cb8de85100)] - **doc**: make the api doc print-friendly (Marian) [#6748](https://github.com/nodejs/node/pull/6748)
+* [[`f1a8c3164a`](https://github.com/nodejs/node/commit/f1a8c3164a)] - **doc**: add bengl to collaborators (Bryan English) [#6921](https://github.com/nodejs/node/pull/6921)
+* [[`565d4ca12e`](https://github.com/nodejs/node/commit/565d4ca12e)] - **doc**: Update DCO to v1.1 (William Kapke) [#6353](https://github.com/nodejs/node/pull/6353)
+* [[`eff73c78c5`](https://github.com/nodejs/node/commit/eff73c78c5)] - **doc**: general improvements to v8.md copy (James M Snell) [#6829](https://github.com/nodejs/node/pull/6829)
+* [[`e5a7cec828`](https://github.com/nodejs/node/commit/e5a7cec828)] - **doc**: fix typo in Error.captureStackTrace (Mohsen) [#6811](https://github.com/nodejs/node/pull/6811)
+* [[`5afb91bef7`](https://github.com/nodejs/node/commit/5afb91bef7)] - **doc**: make param names consistent & fix doc link (Sakthipriyan Vairamani) [#6832](https://github.com/nodejs/node/pull/6832)
+* [[`e1fb4805cf`](https://github.com/nodejs/node/commit/e1fb4805cf)] - **doc**: add `added:` info for `process.cpuUsage` (Anna Henningsen) [#6863](https://github.com/nodejs/node/pull/6863)
+* [[`8a0329f110`](https://github.com/nodejs/node/commit/8a0329f110)] - **doc**: fix mkdtemp example by removing hyphen (Sakthipriyan Vairamani) [#6834](https://github.com/nodejs/node/pull/6834)
+* [[`45ca7cfcdd`](https://github.com/nodejs/node/commit/45ca7cfcdd)] - **doc**: reduce GitHub template verbosity (Rich Trott) [#6801](https://github.com/nodejs/node/pull/6801)
+* [[`12a3d0120b`](https://github.com/nodejs/node/commit/12a3d0120b)] - **doc**: improve vm.md copy (James M Snell) [#6827](https://github.com/nodejs/node/pull/6827)
+* [[`0ae512a3cf`](https://github.com/nodejs/node/commit/0ae512a3cf)] - **doc**: Add resolveNaptr and naptr rrtype docs (Doug Wade) [#6586](https://github.com/nodejs/node/pull/6586)
+* [[`8309dbaf9c`](https://github.com/nodejs/node/commit/8309dbaf9c)] - **doc**: fix name to match git log (Robert Jefe Lindstaedt) [#6880](https://github.com/nodejs/node/pull/6880)
+* [[`b52d838f0d`](https://github.com/nodejs/node/commit/b52d838f0d)] - **doc**: add note for fs.watch virtualized env (Robert Jefe Lindstaedt) [#6809](https://github.com/nodejs/node/pull/6809)
+* [[`08f1361cb6`](https://github.com/nodejs/node/commit/08f1361cb6)] - **doc**: add `added:` information for punycode (Daniel Wang) [#6805](https://github.com/nodejs/node/pull/6805)
+* [[`253db33527`](https://github.com/nodejs/node/commit/253db33527)] - **doc**: add `added:` info for dgram.*Membership() (Rich Trott) [#6753](https://github.com/nodejs/node/pull/6753)
+* [[`5cad04b063`](https://github.com/nodejs/node/commit/5cad04b063)] - **doc**: clarify fs.mkdtemp prefix argument (James M Snell) [#6800](https://github.com/nodejs/node/pull/6800)
+* [[`5a1e823fa5`](https://github.com/nodejs/node/commit/5a1e823fa5)] - **doc**: add `added:` information for fs (Anna Henningsen) [#6717](https://github.com/nodejs/node/pull/6717)
+* [[`bf4724a7bb`](https://github.com/nodejs/node/commit/bf4724a7bb)] - **doc**: remove link to Sign in crypto.md (Kirill Fomichev) [#6812](https://github.com/nodejs/node/pull/6812)
+* [[`ba3089970d`](https://github.com/nodejs/node/commit/ba3089970d)] - **doc**: add `added:` in for `tty` (Rich Trott) [#6783](https://github.com/nodejs/node/pull/6783)
+* [[`758fadfa0d`](https://github.com/nodejs/node/commit/758fadfa0d)] - **doc**: update openssl.org hash links (silverwind) [#6817](https://github.com/nodejs/node/pull/6817)
+* [[`b2c7d466d4`](https://github.com/nodejs/node/commit/b2c7d466d4)] - **doc,test**: add `How to write a Node.js test` guide (Santiago Gimeno) [#6984](https://github.com/nodejs/node/pull/6984)
+* [[`c4329aa226`](https://github.com/nodejs/node/commit/c4329aa226)] - **fs**: move mkdtemp* functions near static functions (Sakthipriyan Vairamani) [#6828](https://github.com/nodejs/node/pull/6828)
+* [[`c068880757`](https://github.com/nodejs/node/commit/c068880757)] - **fs**: mkdtemp shouldn't crash if no callback passed (Sakthipriyan Vairamani) [#6828](https://github.com/nodejs/node/pull/6828)
+* [[`2ab36093e6`](https://github.com/nodejs/node/commit/2ab36093e6)] - **http**: use `localAddress` instead of `path` (Dirceu Pereira Tiegs) [#5190](https://github.com/nodejs/node/pull/5190)
+* [[`6f0d8b3a1b`](https://github.com/nodejs/node/commit/6f0d8b3a1b)] - **installer**: don't install node_internals.h (Ben Noordhuis) [#6913](https://github.com/nodejs/node/pull/6913)
+* [[`178f3080f8`](https://github.com/nodejs/node/commit/178f3080f8)] - **module**: don't cache uninitialized builtins (Anna Henningsen) [#6907](https://github.com/nodejs/node/pull/6907)
+* [[`1908b7f00a`](https://github.com/nodejs/node/commit/1908b7f00a)] - **path**: fix basename() regressions (Brian White) [#6590](https://github.com/nodejs/node/pull/6590)
+* [[`10671406ac`](https://github.com/nodejs/node/commit/10671406ac)] - **process**: internal/process/stdio.js cleanup / modernization (James M Snell) [#6766](https://github.com/nodejs/node/pull/6766)
+* [[`64445674f0`](https://github.com/nodejs/node/commit/64445674f0)] - **src**: add include guards to internal headers (Ben Noordhuis) [#6948](https://github.com/nodejs/node/pull/6948)
+* [[`4333fda46d`](https://github.com/nodejs/node/commit/4333fda46d)] - **src**: no abort from getter if object isn't wrapped (Trevor Norris) [#6184](https://github.com/nodejs/node/pull/6184)
+* [[`4da3e1e461`](https://github.com/nodejs/node/commit/4da3e1e461)] - **src**: always clear wrap before persistent Reset() (Trevor Norris) [#6184](https://github.com/nodejs/node/pull/6184)
+* [[`7e5775704e`](https://github.com/nodejs/node/commit/7e5775704e)] - **src**: inherit first from AsyncWrap (Trevor Norris) [#6184](https://github.com/nodejs/node/pull/6184)
+* [[`0841496992`](https://github.com/nodejs/node/commit/0841496992)] - **src**: fix without-intl build (Anna Henningsen) [#6820](https://github.com/nodejs/node/pull/6820)
+* [[`0d08fc415f`](https://github.com/nodejs/node/commit/0d08fc415f)] - **stream_base**: always use Base template class (Trevor Norris) [#6184](https://github.com/nodejs/node/pull/6184)
+* [[`756ec80d50`](https://github.com/nodejs/node/commit/756ec80d50)] - **string_bytes**: Make base64 encode/decode reusable (Eugene Ostroukhov) [#6910](https://github.com/nodejs/node/pull/6910)
+* [[`79ad172589`](https://github.com/nodejs/node/commit/79ad172589)] - **string_decoder**: rewrite implementation (Brian White) [#6777](https://github.com/nodejs/node/pull/6777)
+* [[`8b720c4582`](https://github.com/nodejs/node/commit/8b720c4582)] - **test**: remove non-incremental common.PORT changes (Rich Trott) [#7055](https://github.com/nodejs/node/pull/7055)
+* [[`6439fbfac0`](https://github.com/nodejs/node/commit/6439fbfac0)] - **test**: test TTY problems by fakeing a TTY using openpty (Jeremiah Senkpiel) [#6895](https://github.com/nodejs/node/pull/6895)
+* [[`81a9f96a29`](https://github.com/nodejs/node/commit/81a9f96a29)] - **test**: make test-child-process-fork-net more robust (Rich Trott) [#7033](https://github.com/nodejs/node/pull/7033)
+* [[`6cf0f622ef`](https://github.com/nodejs/node/commit/6cf0f622ef)] - **test**: fix spurious EADDRINUSE in test-https-strict (Rich Trott) [#7024](https://github.com/nodejs/node/pull/7024)
+* [[`dea120f247`](https://github.com/nodejs/node/commit/dea120f247)] - **test**: update weak module for gc tests (Rich Trott) [#7014](https://github.com/nodejs/node/pull/7014)
+* [[`3bfbe8a62a`](https://github.com/nodejs/node/commit/3bfbe8a62a)] - **test**: remove `common.PORT` from gc tests (Rich Trott) [#7013](https://github.com/nodejs/node/pull/7013)
+* [[`b23cd48ca0`](https://github.com/nodejs/node/commit/b23cd48ca0)] - **test**: fix test-debug-port-numbers on OS X (Santiago Gimeno) [#7046](https://github.com/nodejs/node/pull/7046)
+* [[`0a258e5369`](https://github.com/nodejs/node/commit/0a258e5369)] - **test**: remove modifcation to common.PORT (Rich Trott) [#6990](https://github.com/nodejs/node/pull/6990)
+* [[`8c289df175`](https://github.com/nodejs/node/commit/8c289df175)] - **test**: use strictEqual consistently in agent test (Ben Noordhuis) [#6654](https://github.com/nodejs/node/pull/6654)
+* [[`e4ac808c4d`](https://github.com/nodejs/node/commit/e4ac808c4d)] - **test**: work around debugger not killing inferior (Ben Noordhuis) [#7037](https://github.com/nodejs/node/pull/7037)
+* [[`b5949f8bbc`](https://github.com/nodejs/node/commit/b5949f8bbc)] - **test**: verify cluster worker exit (cjihrig) [#6993](https://github.com/nodejs/node/pull/6993)
+* [[`6f3f5af396`](https://github.com/nodejs/node/commit/6f3f5af396)] - **test**: add regression test for Proxy as vm context (Michaël Zasso) [#6967](https://github.com/nodejs/node/pull/6967)
+* [[`38a3323cc9`](https://github.com/nodejs/node/commit/38a3323cc9)] - **test**: improve debug-break-on-uncaught reliability (Rich Trott) [#6793](https://github.com/nodejs/node/pull/6793)
+* [[`83e6d53817`](https://github.com/nodejs/node/commit/83e6d53817)] - **test**: test cluster worker disconnection on error (Santiago Gimeno) [#6909](https://github.com/nodejs/node/pull/6909)
+* [[`4cc6a18448`](https://github.com/nodejs/node/commit/4cc6a18448)] - **test**: verify IPC messages are emitted on next tick (Santiago Gimeno) [#6909](https://github.com/nodejs/node/pull/6909)
+* [[`69e119dbfb`](https://github.com/nodejs/node/commit/69e119dbfb)] - **test**: refactor spawnSync() cwd test (cjihrig) [#6939](https://github.com/nodejs/node/pull/6939)
+* [[`32cc43a1bd`](https://github.com/nodejs/node/commit/32cc43a1bd)] - **test**: fix component printing on windows (Ben Noordhuis) [#6915](https://github.com/nodejs/node/pull/6915)
+* [[`c81b6f8d0d`](https://github.com/nodejs/node/commit/c81b6f8d0d)] - **test**: refactor to eliminate __defineGetter__ (Rich Trott) [#6774](https://github.com/nodejs/node/pull/6774)
+* [[`1965e445ec`](https://github.com/nodejs/node/commit/1965e445ec)] - **test**: refactor test-tls-reuse-host-from-socket (Rich Trott) [#6756](https://github.com/nodejs/node/pull/6756)
+* [[`2cf3a53ce1`](https://github.com/nodejs/node/commit/2cf3a53ce1)] - **test**: fix test-debug-port-cluster flakiness (Rich Trott) [#6769](https://github.com/nodejs/node/pull/6769)
+* [[`5374afdef8`](https://github.com/nodejs/node/commit/5374afdef8)] - **test**: add logging for test-debug-port-cluster (Rich Trott) [#6769](https://github.com/nodejs/node/pull/6769)
+* [[`bae7adb6fa`](https://github.com/nodejs/node/commit/bae7adb6fa)] - **test**: fix flaky test-stdout-close-catch (Santiago Gimeno) [#6808](https://github.com/nodejs/node/pull/6808)
+* [[`528ca04e8d`](https://github.com/nodejs/node/commit/528ca04e8d)] - **test**: add more path.basename() tests (Brian White) [#6590](https://github.com/nodejs/node/pull/6590)
+* [[`1469b98fa1`](https://github.com/nodejs/node/commit/1469b98fa1)] - **test**: remove duplicate path tests (Brian White) [#6590](https://github.com/nodejs/node/pull/6590)
+* [[`81e765f521`](https://github.com/nodejs/node/commit/81e765f521)] - **test**: robust handling of env for npm-test-install (Myles Borins) [#6797](https://github.com/nodejs/node/pull/6797)
+* [[`2895860138`](https://github.com/nodejs/node/commit/2895860138)] - **test**: cluster-setup-master online workers check (Devon Rifkin) [#6535](https://github.com/nodejs/node/pull/6535)
+* [[`7c932c2d49`](https://github.com/nodejs/node/commit/7c932c2d49)] - **test**: added tests for https-agent-getname (suryagh) [#6762](https://github.com/nodejs/node/pull/6762)
+* [[`827b3eb503`](https://github.com/nodejs/node/commit/827b3eb503)] - **test**: add --repeat option to tools/test.py (Michael Dawson) [#6700](https://github.com/nodejs/node/pull/6700)
+* [[`ea287fc1a6`](https://github.com/nodejs/node/commit/ea287fc1a6)] - **test,win**: skip addons/load-long-path on WOW64 (Alexis Campailla) [#6675](https://github.com/nodejs/node/pull/6675)
+* [[`21e31352d7`](https://github.com/nodejs/node/commit/21e31352d7)] - **tls**: catch `certCbDone` exceptions (Fedor Indutny) [#6887](https://github.com/nodejs/node/pull/6887)
+* [[`257e54b9c0`](https://github.com/nodejs/node/commit/257e54b9c0)] - **tls,https**: respect address family when connecting (Ben Noordhuis) [#6654](https://github.com/nodejs/node/pull/6654)
+* [[`5779ed2a4a`](https://github.com/nodejs/node/commit/5779ed2a4a)] - **tls_wrap**: do not abort on new TLSWrap() (Trevor Norris) [#6184](https://github.com/nodejs/node/pull/6184)
+* [[`108523e06e`](https://github.com/nodejs/node/commit/108523e06e)] - **tools**: make sure doctool anchors respect includes (Anna Henningsen) [#6943](https://github.com/nodejs/node/pull/6943)
+* [[`bf3afce668`](https://github.com/nodejs/node/commit/bf3afce668)] - **tools**: restore change of signatures to opts hashes (Jesse McCarthy) [#6690](https://github.com/nodejs/node/pull/6690)
+* [[`ceee56b28b`](https://github.com/nodejs/node/commit/ceee56b28b)] - **tools**: disallow deprecated define getter/setter (Rich Trott) [#6774](https://github.com/nodejs/node/pull/6774)
+* [[`614907e516`](https://github.com/nodejs/node/commit/614907e516)] - **tools**: print stderr on bad test.py `vmArch` check (Jeremiah Senkpiel) [#6786](https://github.com/nodejs/node/pull/6786)
+* [[`4d3a7594a5`](https://github.com/nodejs/node/commit/4d3a7594a5)] - **tty**: use blocking mode on OS X (Jeremiah Senkpiel) [#6895](https://github.com/nodejs/node/pull/6895)
+* [[`36ed4a2d7a`](https://github.com/nodejs/node/commit/36ed4a2d7a)] - **udp**: use libuv API to get file descriptor (Saúl Ibarra Corretgé) [#6908](https://github.com/nodejs/node/pull/6908)
+* [[`f3e3eebec8`](https://github.com/nodejs/node/commit/f3e3eebec8)] - **unix,stream**: fix getting the correct fd for a handle (Saúl Ibarra Corretgé) [#6753](https://github.com/nodejs/node/pull/6753)
+* [[`d270706881`](https://github.com/nodejs/node/commit/d270706881)] - **util**: pretty-print SIMD types (Ben Noordhuis) [#6917](https://github.com/nodejs/node/pull/6917)
+* [[`55b736a63b`](https://github.com/nodejs/node/commit/55b736a63b)] - **vm**: don't abort process when stack space runs out (Anna Henningsen) [#6907](https://github.com/nodejs/node/pull/6907)
+* [[`cb2ef35b76`](https://github.com/nodejs/node/commit/cb2ef35b76)] - **win,build**: add creation of zip and 7z package (Bartosz Sosnowski) [#5995](https://github.com/nodejs/node/pull/5995)
+* [[`1e26b82ce4`](https://github.com/nodejs/node/commit/1e26b82ce4)] - **zlib**: release callback and buffer after processing (Matt Lavin) [#6955](https://github.com/nodejs/node/pull/6955)
+* [[`64415564de`](https://github.com/nodejs/node/commit/64415564de)] - **zlib**: remove `_closed` in source (Anna Henningsen) [#6574](https://github.com/nodejs/node/pull/6574)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v6.2.1/node-v6.2.1-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v6.2.1/node-v6.2.1-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v6.2.1/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v6.2.1/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v6.2.1/node-v6.2.1.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v6.2.1/node-v6.2.1-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v6.2.1/node-v6.2.1.tar.gz<br>
+Other release files: https://nodejs.org/dist/v6.2.1/<br>
+Documentation: https://nodejs.org/docs/v6.2.1/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+a6e99c2e482133b0f2db6bb8284ef79ea60c554e8dbfc24a1a691671cc5d0517  node-v6.2.1-darwin-x64.tar.gz
+5ccbac97e3e38d9e8531552f670ae62a95c8561e74b7bd218ad92215fa783f06  node-v6.2.1-darwin-x64.tar.xz
+f55aa8ea6de59e074c4f9d5ab65b77e68bcf607971be05ff31b88acb91714f4f  node-v6.2.1-headers.tar.gz
+6c06cc1cbfbcc417acfd83a1a7406f4894e76bba5a0f1dd221fba765fdadee3a  node-v6.2.1-headers.tar.xz
+86f7498f0c355e8f8c17cecaf7e0bd6f68e189e00e0adb6700560e291edce08d  node-v6.2.1-linux-arm64.tar.gz
+040f7f1f31a0ffede00733cffabb5a2e66931345bc3d9cedb1af683304890b31  node-v6.2.1-linux-arm64.tar.xz
+f791c57f336fc67c7231c9c54799b4e39427a2de99decf47898d57353b0fb64b  node-v6.2.1-linux-armv6l.tar.gz
+1cb17dbfb405e750ae323346de5263bd2be4bf30b1211de7ffb07512332558a9  node-v6.2.1-linux-armv6l.tar.xz
+01ac0cbae90a88f73b016db7e8052d05f7ab7083d5a14b6b10067a41eea538ff  node-v6.2.1-linux-armv7l.tar.gz
+aac349e02d41eb9e1205af96e42d9a593ba4827553aa1db988cabaf0041fb08a  node-v6.2.1-linux-armv7l.tar.xz
+2ca673b76add031e6244b36e2cd3c1da1982e21aec84eeda24bcbc1b77772ab2  node-v6.2.1-linux-ppc64le.tar.gz
+f8dfe167d4a43adb05a9a14eb96a7081189dd2036e259972fd1fc643b148a1e8  node-v6.2.1-linux-ppc64le.tar.xz
+4fa09f89af1b835caf4be73ca4c7a02a1bc640c36c4ec512dbdb0827315003e9  node-v6.2.1-linux-ppc64.tar.gz
+6bb127999105e9eb2f4958b0be170aea38951f49a3fa7efacdea344e7b3111b6  node-v6.2.1-linux-ppc64.tar.xz
+c6ae9c90858fb47a2915ad6494e5eb8e6f34f4512de1d5a461e5fb0c003590b1  node-v6.2.1-linux-x64.tar.gz
+1027de8bd78ef2cba2baf5a676d54f185f9632324465cfd8572c3568ca6e1f64  node-v6.2.1-linux-x64.tar.xz
+f5656c288c1dfc760a23000d8dc1eb3d0ff484a7798e5f28718a728ae96e9125  node-v6.2.1-linux-x86.tar.gz
+9d46df7c687f212107a39a667fb6b0da9734c71c3513ff8db21f521a033270f1  node-v6.2.1-linux-x86.tar.xz
+dec8054fdf3266b912842cb3307a3b5e6cc34bf00f2d3bd19a5b71fb4d9a3290  node-v6.2.1.pkg
+c7e931670bca8055ed6d090bab276bee5c2db570e74c0828f64a2b5c6dc9e973  node-v6.2.1-sunos-x64.tar.gz
+550c162ba7dd4d7b1e8dd69f98887e54ebfc79a5fe5ba79308b2166408a4a8a6  node-v6.2.1-sunos-x64.tar.xz
+39ac16d0b200a29261767d6aa99d1a9da343e7c4b629ce332f7d6b9fcfb1767a  node-v6.2.1-sunos-x86.tar.gz
+7fc08597de9b69ba8b38007b0df896e8776d138dc7e4716ce09c325cf8df4aff  node-v6.2.1-sunos-x86.tar.xz
+fa26d4380150fbb69a48bddaec6143e176effe043cfe44e512c5ef9d22618b63  node-v6.2.1.tar.gz
+dbaeb8fb68a599e5164b17c74f66d24f424ee4ab3a25d8de8a3c6808e5b42bfb  node-v6.2.1.tar.xz
+217631ccc76fb869ea9a82e8c12eebbe67c66f877bf98d913bf8f19d1dae56f1  node-v6.2.1-win-x64.7z
+90e93905b52131a84e4c3488177a0bf060a4c3e5633c1f567d580fd9141d2848  node-v6.2.1-win-x64.zip
+4103f49aea62d6b2e7e022493c61af93c401404c5497ddd77f0e3787e0e8bce7  node-v6.2.1-win-x86.7z
+967dd36e2eec59c4e32e7cc3bf565f589080ac1be0cc877ee8aa1240fbb9b7d7  node-v6.2.1-win-x86.zip
+528b7c2cb707e81df4d5e53ea3b8d8c32e71ab3ba7e2ee4993a4f44da6e353ba  node-v6.2.1-x64.msi
+8095a7c506ed1ada1599942ae2a8cb60909def15bc4d97c7dca51c3d02f046ec  node-v6.2.1-x86.msi
+1fea4396837da41f363312d3ee7cbc34ba23edfb24e39c6aa6ced732cdea7878  win-x64/node.exe
+0dca5ad3d2ec6e4eed2f370c812c94fc1f5d5434e44a2b6e970a133d9be5bf37  win-x64/node.lib
+4403d0dd9702907eb2ad8d49b0c7f2af5f5b7d263758bf1e79fe89008f523012  win-x64/node_pdb.7z
+03201f05e0f3f455116f29b03bc7a930d0c4b0c593327944eceb44454f746335  win-x64/node_pdb.zip
+e5d6e2800e05c376f0b13fccf4ea5f45dbc890b13221401fe7ae3bbcf77a9635  win-x86/node.exe
+c7312d02d0b98cbc7700cc22d47f40d4c2284e96410216484d606057936dbad4  win-x86/node.lib
+3e777fe925cb48917cb9748bdff62fb0e8570385572cdcfd9cf5cb68dfcdb784  win-x86/node_pdb.7z
+0b6edd7afb0ea3024a12c55923df448726e99459a9be44d418e7d1d7ad5ab2cd  win-x86/node_pdb.zip
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJXULUeAAoJEMJzeS99g1Rd36wH/3pDBdJVZVgARpEOfJHAWUx7
+Rhma9WpukZ1K7d/5c98jdvgErIUM/aQYx2qKUvDLBHUHdRjQM7uuCHu7bm4AMiYb
+9ugqsAxLqAHKtOzBWaY6SEAtnG7nHUsKsmeVos35Y9VjlGsOymL5VD13Wjv4o/uX
+kL9fFroCv2QJ6Y/ho9PW6t1t4SmvtOpHr4vvtu3SFEnz/Ov9+SAkRHEXPLZZKfkI
+Ul2U2Pq9gG9heLTJMUKmaUFnULA1vejtIfy1fDZpBIxbgSaBLjoVQbQjnnpuF+2r
+BeMzhURkxye584k7noOZbEKIFSM1h6DqJ4fjWjSkJZKnaJ6/WuymInsM3uT3x2I=
+=kvV9
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/release/v6.2.2.md b/locale/uk/blog/release/v6.2.2.md
new file mode 100755
index 0000000000000..778f8f0b15a20
--- /dev/null
+++ b/locale/uk/blog/release/v6.2.2.md
@@ -0,0 +1,165 @@
+---
+date: 2016-06-17T15:53:06.031Z
+version: 6.2.2
+category: release
+title: Node v6.2.2 (Current)
+slug: node-v6-2-2
+layout: blog-post.hbs
+author: Evan Lucas
+---
+
+### Notable changes
+
+* **http**:
+  - `req.read(0)` could cause incoming connections to stall and time out under certain conditions. (Fedor Indutny) [#7211](https://github.com/nodejs/node/pull/7211)
+  - When freeing the socket to be reused in keep-alive Agent wait for both prefinish and end events. Otherwise the next request may be written before the previous one has finished sending the body, leading to parser errors. (Fedor Indutny) [#7149](https://github.com/nodejs/node/pull/7149)
+* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [#7139](https://github.com/nodejs/node/pull/7139)
+
+### Commits
+
+* [[`d71ede8113`](https://github.com/nodejs/node/commit/d71ede8113)] - **benchmark**: don't convert arguments to numbers (Brian White) [#6570](https://github.com/nodejs/node/pull/6570)
+* [[`32f76983e2`](https://github.com/nodejs/node/commit/32f76983e2)] - **benchmark**: increase http token check iterations (Brian White) [#6570](https://github.com/nodejs/node/pull/6570)
+* [[`23a495a9a9`](https://github.com/nodejs/node/commit/23a495a9a9)] - **benchmark**: add benchmark for url.format() (Rich Trott) [#7250](https://github.com/nodejs/node/pull/7250)
+* [[`27ed7fc56c`](https://github.com/nodejs/node/commit/27ed7fc56c)] - **benchmark**: fix child-process-exec-stdout on win (Bartosz Sosnowski) [#7178](https://github.com/nodejs/node/pull/7178)
+* [[`5e5af8b4bb`](https://github.com/nodejs/node/commit/5e5af8b4bb)] - **benchmark**: fix child-process-read on Windows (Bartosz Sosnowski) [#6971](https://github.com/nodejs/node/pull/6971)
+* [[`d24e4095bf`](https://github.com/nodejs/node/commit/d24e4095bf)] - **benchmark**: add benchmark for Buffer.concat (Anna Henningsen) [#7054](https://github.com/nodejs/node/pull/7054)
+* [[`666b6f9302`](https://github.com/nodejs/node/commit/666b6f9302)] - **build**: add REPLACEME tag for version info in docs (Ben Noordhuis) [#6864](https://github.com/nodejs/node/pull/6864)
+* [[`6d3d2d1ae4`](https://github.com/nodejs/node/commit/6d3d2d1ae4)] - **cluster**: don't send messages if no IPC channel (Santiago Gimeno) [#7132](https://github.com/nodejs/node/pull/7132)
+* [[`068718c91c`](https://github.com/nodejs/node/commit/068718c91c)] - **debugger**: remove obsolete setTimeout (Rich Trott) [#7154](https://github.com/nodejs/node/pull/7154)
+* [[`2961f06f6f`](https://github.com/nodejs/node/commit/2961f06f6f)] - **debugger**: fix --debug-brk interaction with -e (Rich Trott) [#7089](https://github.com/nodejs/node/pull/7089)
+* [[`701e699d4f`](https://github.com/nodejs/node/commit/701e699d4f)] - **deps**: upgrade npm to 3.9.5 (Kat Marchán) [#7139](https://github.com/nodejs/node/pull/7139)
+* [[`1095ae1ac5`](https://github.com/nodejs/node/commit/1095ae1ac5)] - **doc**: Add CII Best Practices badge to README.md (David A. Wheeler) [#6819](https://github.com/nodejs/node/pull/6819)
+* [[`0198987b0d`](https://github.com/nodejs/node/commit/0198987b0d)] - **doc**: add internal link in GOVERNANCE.md (Rich Trott) [#7279](https://github.com/nodejs/node/pull/7279)
+* [[`8e14f761bb`](https://github.com/nodejs/node/commit/8e14f761bb)] - **doc**: use `Buffer.byteLength` for Content-Length (kimown) [#7274](https://github.com/nodejs/node/pull/7274)
+* [[`5d03bdd94f`](https://github.com/nodejs/node/commit/5d03bdd94f)] - **doc**: add information for IncomingMessage.destroy() (Rich Trott) [#7237](https://github.com/nodejs/node/pull/7237)
+* [[`a113734099`](https://github.com/nodejs/node/commit/a113734099)] - **doc**: general improvements to path.md copy (James M Snell) [#7122](https://github.com/nodejs/node/pull/7122)
+* [[`b5e44df9a3`](https://github.com/nodejs/node/commit/b5e44df9a3)] - **doc**: make pull request template more concise (Rich Trott) [#7239](https://github.com/nodejs/node/pull/7239)
+* [[`40a5974a0e`](https://github.com/nodejs/node/commit/40a5974a0e)] - **doc**: `url.format()` parameter may be a string (Rich Trott) [#7235](https://github.com/nodejs/node/pull/7235)
+* [[`a7d813915e`](https://github.com/nodejs/node/commit/a7d813915e)] - **doc**: clarify use of `0` port value (Rich Trott) [#7206](https://github.com/nodejs/node/pull/7206)
+* [[`0fc8012b65`](https://github.com/nodejs/node/commit/0fc8012b65)] - **doc**: remove cluster.setupMaster() myth (cjihrig) [#7179](https://github.com/nodejs/node/pull/7179)
+* [[`70167fd1d4`](https://github.com/nodejs/node/commit/70167fd1d4)] - **doc**: fix IRC link (Ilkka Myller) [#7210](https://github.com/nodejs/node/pull/7210)
+* [[`4f2215fd98`](https://github.com/nodejs/node/commit/4f2215fd98)] - **doc**: fix minor nit introduced in readline.md (James M Snell) [#7198](https://github.com/nodejs/node/pull/7198)
+* [[`d31f728e09`](https://github.com/nodejs/node/commit/d31f728e09)] - **doc**: clarify rl.question callback args (James M Snell) [#7022](https://github.com/nodejs/node/pull/7022)
+* [[`70f2f357be`](https://github.com/nodejs/node/commit/70f2f357be)] - **doc**: general improvements to readline.md copy (James M Snell) [#7022](https://github.com/nodejs/node/pull/7022)
+* [[`c2aba5ba27`](https://github.com/nodejs/node/commit/c2aba5ba27)] - **doc**: consolidate test/lint text in GH PR template (Rich Trott) [#7155](https://github.com/nodejs/node/pull/7155)
+* [[`712120112f`](https://github.com/nodejs/node/commit/712120112f)] - **doc**: use consistent typography in streams.md (Rich Trott) [#6986](https://github.com/nodejs/node/pull/6986)
+* [[`e2f6f8061b`](https://github.com/nodejs/node/commit/e2f6f8061b)] - **doc**: general improvements to process.md copy (James M Snell) [#7029](https://github.com/nodejs/node/pull/7029)
+* [[`84ea6fc57c`](https://github.com/nodejs/node/commit/84ea6fc57c)] - **doc**: general improvements to repl.md copy (James M Snell) [#7002](https://github.com/nodejs/node/pull/7002)
+* [[`bfb7e3cc6e`](https://github.com/nodejs/node/commit/bfb7e3cc6e)] - **doc**: add `added:` information for readline (Julian Duque) [#6996](https://github.com/nodejs/node/pull/6996)
+* [[`632b411cd0`](https://github.com/nodejs/node/commit/632b411cd0)] - **doc**: improved syntax consistency in console.md (Jonathan Montane) [#7062](https://github.com/nodejs/node/pull/7062)
+* [[`826bd99486`](https://github.com/nodejs/node/commit/826bd99486)] - **doc**: specify how to link issues in commit log (Luigi Pinca) [#7161](https://github.com/nodejs/node/pull/7161)
+* [[`865644a604`](https://github.com/nodejs/node/commit/865644a604)] - **doc**: general improvements to querystring.md copy (James M Snell) [#7023](https://github.com/nodejs/node/pull/7023)
+* [[`dd4c607267`](https://github.com/nodejs/node/commit/dd4c607267)] - **doc**: fix header depth of util.isSymbol (James M Snell) [#7138](https://github.com/nodejs/node/pull/7138)
+* [[`5086e5f3ee`](https://github.com/nodejs/node/commit/5086e5f3ee)] - **doc**: general improvements to stream.md copy (James M Snell) [#6947](https://github.com/nodejs/node/pull/6947)
+* [[`75d6875034`](https://github.com/nodejs/node/commit/75d6875034)] - **doc**: update licenses (Myles Borins) [#7121](https://github.com/nodejs/node/pull/7121)
+* [[`dc8cb93c4f`](https://github.com/nodejs/node/commit/dc8cb93c4f)] - **doc**: add `added:` information for dns (Julian Duque) [#7021](https://github.com/nodejs/node/pull/7021)
+* [[`a7c85e6fd5`](https://github.com/nodejs/node/commit/a7c85e6fd5)] - **doc**: add `added:` information for path (Julian Duque) [#6985](https://github.com/nodejs/node/pull/6985)
+* [[`026bf17378`](https://github.com/nodejs/node/commit/026bf17378)] - **doc**: add `added` information for net (Italo A. Casas) [#7038](https://github.com/nodejs/node/pull/7038)
+* [[`d4a2c82f5f`](https://github.com/nodejs/node/commit/d4a2c82f5f)] - **doc**: general improvements to punycode.md copy (James M Snell) [#7025](https://github.com/nodejs/node/pull/7025)
+* [[`51d295efe6`](https://github.com/nodejs/node/commit/51d295efe6)] - **doc**: add links to platform specific mechanisms (Michael Dawson) [#7071](https://github.com/nodejs/node/pull/7071)
+* [[`1600966f59`](https://github.com/nodejs/node/commit/1600966f59)] - **fs**: execute mkdtemp's callback with no context (Sakthipriyan Vairamani) [#7068](https://github.com/nodejs/node/pull/7068)
+* [[`ad1045c829`](https://github.com/nodejs/node/commit/ad1045c829)] - **http**: fix no dumping after `maybeReadMore` (Fedor Indutny) [#7211](https://github.com/nodejs/node/pull/7211)
+* [[`2a462ba1e2`](https://github.com/nodejs/node/commit/2a462ba1e2)] - **http**: optimize checkInvalidHeaderChar() (Brian White) [#6570](https://github.com/nodejs/node/pull/6570)
+* [[`4a63be031f`](https://github.com/nodejs/node/commit/4a63be031f)] - **http**: optimize checkIsHttpToken() (Brian White) [#6570](https://github.com/nodejs/node/pull/6570)
+* [[`40e49dee82`](https://github.com/nodejs/node/commit/40e49dee82)] - **http**: wait for both prefinish/end to keepalive (Fedor Indutny) [#7149](https://github.com/nodejs/node/pull/7149)
+* [[`e8c91e7557`](https://github.com/nodejs/node/commit/e8c91e7557)] - **repl**: refine handling of illegal tokens (Rich Trott) [#7104](https://github.com/nodejs/node/pull/7104)
+* [[`cf0928ccb7`](https://github.com/nodejs/node/commit/cf0928ccb7)] - **src**: clean up string_search (Brian White) [#7174](https://github.com/nodejs/node/pull/7174)
+* [[`b0225e5926`](https://github.com/nodejs/node/commit/b0225e5926)] - **stream**: ensure awaitDrain is increased once (David Halls) [#7292](https://github.com/nodejs/node/pull/7292)
+* [[`9c6b69ec1b`](https://github.com/nodejs/node/commit/9c6b69ec1b)] - **stream**: reset awaitDrain after manual .resume() (Anna Henningsen) [#7160](https://github.com/nodejs/node/pull/7160)
+* [[`caa6718a01`](https://github.com/nodejs/node/commit/caa6718a01)] - **test**: fix test-net-* error code check for getaddrinfo(3) (Natanael Copa) [#5099](https://github.com/nodejs/node/pull/5099)
+* [[`535c8dd554`](https://github.com/nodejs/node/commit/535c8dd554)] - **test**: add more http token/value checking tests (Brian White) [#6570](https://github.com/nodejs/node/pull/6570)
+* [[`257f4e6202`](https://github.com/nodejs/node/commit/257f4e6202)] - **test**: add note about duration_ms in TAP reporter (Rod Vagg) [#7216](https://github.com/nodejs/node/pull/7216)
+* [[`798a737f45`](https://github.com/nodejs/node/commit/798a737f45)] - ***Revert*** "**test**: change duration_ms to duration" (Rod Vagg) [#7216](https://github.com/nodejs/node/pull/7216)
+* [[`72e4e43b91`](https://github.com/nodejs/node/commit/72e4e43b91)] - **test**: rebuild add-ons when their sources change (Ben Noordhuis) [#7262](https://github.com/nodejs/node/pull/7262)
+* [[`eded11705b`](https://github.com/nodejs/node/commit/eded11705b)] - **test**: use random ports where possible (Brian White) [#7045](https://github.com/nodejs/node/pull/7045)
+* [[`d54c7c19a6`](https://github.com/nodejs/node/commit/d54c7c19a6)] - **test**: fix spawn on windows (Brian White) [#7049](https://github.com/nodejs/node/pull/7049)
+* [[`e873063a3c`](https://github.com/nodejs/node/commit/e873063a3c)] - **test**: enable test-debug-brk-no-arg (Rich Trott) [#7143](https://github.com/nodejs/node/pull/7143)
+* [[`d6091c8194`](https://github.com/nodejs/node/commit/d6091c8194)] - **test**: use common.fixturesDir almost everywhere (Bryan English) [#6997](https://github.com/nodejs/node/pull/6997)
+* [[`e8b1456d8b`](https://github.com/nodejs/node/commit/e8b1456d8b)] - **test**: change duration_ms to duration (Gibson Fahnestock) [#7133](https://github.com/nodejs/node/pull/7133)
+* [[`6ce26c8c8b`](https://github.com/nodejs/node/commit/6ce26c8c8b)] - **test**: add test for uid/gid setting in spawn (Rich Trott) [#7084](https://github.com/nodejs/node/pull/7084)
+* [[`40604b54d4`](https://github.com/nodejs/node/commit/40604b54d4)] - **test**: remove disabled eio race test (Rich Trott) [#7083](https://github.com/nodejs/node/pull/7083)
+* [[`9545c41cba`](https://github.com/nodejs/node/commit/9545c41cba)] - **tools**: fix license builder to work with icu-small (Myles Borins) [#7119](https://github.com/nodejs/node/pull/7119)
+* [[`6562c9fc75`](https://github.com/nodejs/node/commit/6562c9fc75)] - **tools,doc**: add example usage for REPLACEME tag (Anna Henningsen) [#6864](https://github.com/nodejs/node/pull/6864)
+
+
+Windows 32-bit Installer: https://nodejs.org/dist/v6.2.2/node-v6.2.2-x86.msi<br>
+Windows 64-bit Installer: https://nodejs.org/dist/v6.2.2/node-v6.2.2-x64.msi<br>
+Windows 32-bit Binary: https://nodejs.org/dist/v6.2.2/win-x86/node.exe<br>
+Windows 64-bit Binary: https://nodejs.org/dist/v6.2.2/win-x64/node.exe<br>
+Mac OS X 64-bit Installer: https://nodejs.org/dist/v6.2.2/node-v6.2.2.pkg<br>
+Mac OS X 64-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-darwin-x64.tar.gz<br>
+Linux 32-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-x86.tar.xz<br>
+Linux 64-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-x64.tar.xz<br>
+Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-ppc64le.tar.xz<br>
+SunOS 32-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-sunos-x86.tar.xz<br>
+SunOS 64-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-sunos-x64.tar.xz<br>
+ARMv6 32-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-armv6l.tar.xz<br>
+ARMv7 32-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-armv7l.tar.xz<br>
+ARMv8 64-bit Binary: https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-arm64.tar.xz<br>
+Source Code: https://nodejs.org/dist/v6.2.2/node-v6.2.2.tar.gz<br>
+Other release files: https://nodejs.org/dist/v6.2.2/<br>
+Documentation: https://nodejs.org/docs/v6.2.2/api/
+
+Shasums (GPG signing hash: SHA512, file hash: SHA256):
+```
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+03b9eadd71d73daf2a25c8ea833454b326cb702f717a39f1b2a1324179cab5fa  node-v6.2.2-darwin-x64.tar.gz
+1ef75ae9c3db01eafb0371e4c0e22889b1abd5f37f511569a72b64dcf39c93eb  node-v6.2.2-darwin-x64.tar.xz
+c02d78470afb83d4473f196a5ff3725f028cd661c4d50d0337f817c7af02e0e7  node-v6.2.2-headers.tar.gz
+2e84e6aa370c06544392a3724c4cbccad1846d854ec5dddba08ccb63d92854ab  node-v6.2.2-headers.tar.xz
+1eaac04e632e633197c764a65817909667a700a657b1de463a45efcd40d236c7  node-v6.2.2-linux-arm64.tar.gz
+02c5b6b54b036d0e7d7fea58c6a344be9cdb6d40e2c3bef76639827669d6e1e6  node-v6.2.2-linux-arm64.tar.xz
+92b41e1c31a64024c5386df3cb6b9c0e00ecb097c2f7d0413364e20b7b836ae9  node-v6.2.2-linux-armv6l.tar.gz
+3f6125c849aa7af16732e1e948e236a4ab31efaeb121cca1eb2e19e50396a07a  node-v6.2.2-linux-armv6l.tar.xz
+ecaa5ccdad2d3e9efc8944e5c57971753bacbd7c171b6a4445e76e5fb9ebc69b  node-v6.2.2-linux-armv7l.tar.gz
+03cc16e0839c65e36c34d8802d7c8e3110d60a53eef49584928314d2b8f18fb4  node-v6.2.2-linux-armv7l.tar.xz
+b3e2e27ad4e52610fc971ef7c32cfb7c3f9db03a0b49e8bd422383ff30197263  node-v6.2.2-linux-ppc64le.tar.gz
+282b60f64ee8793c0d8a2f8849bdd13130a1a296d54ab947ae527d7bc2eb8b10  node-v6.2.2-linux-ppc64le.tar.xz
+ff307b8602808e799cef488c55f1fe646cd169c44464c4c53b56e61d181d06a6  node-v6.2.2-linux-ppc64.tar.gz
+cbb956214dd864725aaa5cd6d507faf520886b61fa66fb6f25fb7a4b9a579883  node-v6.2.2-linux-ppc64.tar.xz
+7a6df881183e70839857b51653811aaabc49a2ffb93416a1c9bd333dcef84ea3  node-v6.2.2-linux-x64.tar.gz
+dd8231b89c57c51b298563fd5e9c594d3ced9cb5f3153dcc05d55444b5d0dc4b  node-v6.2.2-linux-x64.tar.xz
+71a3ec010acaa3c5d26429b6670f4895cd494199ffa07b1773e63619559c32c1  node-v6.2.2-linux-x86.tar.gz
+c00150ed1e4971394136d4ff086fb726f592b0615fa8f7aa64d14d2e338be2b8  node-v6.2.2-linux-x86.tar.xz
+122c74d5864f99530638f35652129c8b2ba3163317a7c404e1a058f97ceba7d4  node-v6.2.2.pkg
+d4a4c601ee6ce311193c1445ca2efbad75a6adbe407ce787381c4b620ac62eeb  node-v6.2.2-sunos-x64.tar.gz
+4ada036c9b5f5c1b73e305e1bb05f8d31f44f2535495f26f24666b3d8eb9cd52  node-v6.2.2-sunos-x64.tar.xz
+94fecfccdc903d0df685850fa8a34c28528e79634bea7569ca7b570a39d2a7ce  node-v6.2.2-sunos-x86.tar.gz
+dab2c5cabd9ac7a6bf79fdb902cdb862ea0757799d4dc189d483568418697af3  node-v6.2.2-sunos-x86.tar.xz
+b6baee57a0ede496c7c7765001f7495ad74c8dfe8c34f1a6fb2cd5d8d526ffce  node-v6.2.2.tar.gz
+2dfeeddba750b52a528b38a1c31e35c1fb40b19cf28fbf430c3c8c7a6517005a  node-v6.2.2.tar.xz
+33fffbe79ed5ec422f8be12f7f87f616e98b630ed40f10cfe84e373122c04589  node-v6.2.2-win-x64.7z
+df66df9c3c1e069cb5a59d5077dca54af4ccf48fb13d1e85eb1aa72297f9952b  node-v6.2.2-win-x64.zip
+db2e898eea4204a247827e288311b05f93f57c6c08f29e6b415b1301b4fce9ca  node-v6.2.2-win-x86.7z
+77ad948abdb861bbe23259a18adf77dac094847f66ded0cd9e70871336eb3935  node-v6.2.2-win-x86.zip
+d7e9f474de0605addb6bbb1c5d01b45de88b704f1d72e8f026171baa7cbf75d1  node-v6.2.2-x64.msi
+2c186a625473796c2fd70948fa85c8a1e087033fbf25ae16866e2f2f347f0e38  node-v6.2.2-x86.msi
+b900e6c16576bf389c034580678c10fed1970b640456706182d028697b7a0c1f  win-x64/node.exe
+4d4417c20bad483c9a8a7a3ee49278c4ad4b608efdfa4c6d9db671d608ac5ee5  win-x64/node.lib
+973c7a6c114ee6d43ffc973764c35ad7af7a5f811172b2b6f36820de727bb6b7  win-x64/node_pdb.7z
+06e0a8e5625186a430fb55a09655f47d574a27f886fd5ac83f4ee2a0abd5eb7c  win-x64/node_pdb.zip
+9cb8c4f4c427ab6cf73ce38523bfaa2d094bbe45d614805b2d34dc5078f0b821  win-x86/node.exe
+f0cc06d127ee17de4213315ba96276dffdcb16708a5b432770f49eaf63007e9e  win-x86/node.lib
+0257c8d092b65410f2f75d065284894f0667b68effe873072afb679873d0d323  win-x86/node_pdb.7z
+d950aee2eeb69c666e0391b2c692728e69ec2dd2e58a6d38b11e8303c74476dd  win-x86/node_pdb.zip
+-----BEGIN PGP SIGNATURE-----
+Comment: GPGTools - https://gpgtools.org
+
+iQIcBAEBCgAGBQJXZBwgAAoJELY7U1pMIGyp/UUQANLiIQthoyGS7tAlN4ehlyPF
+kaKNchNhEMBI8uD0Sd//wtasXOmcxXnpwBcmZ96horx7VnJeyqYRx9/+GQUJ7XhE
+X4AtJcCxWqpuzc7FIL01AfK1L8LydHHUb7NxFbqy2VtvRG/rHk4EXsKtYnnwHlQV
+k04902E9XC236ED2gIBtrmyWJoYuxTuhuNnv/VXErm7y2gQmWak5FkdVL1sQD2Wg
+dkdvZ2EpV8Gato1tAMLwoOoGdDMBloltEbp7EFlxCb1h0Fr5Pi+PQXv9bQebevAy
+7cLleiodYHVSWcDfvWYHlss99MZZMbdNh7DGUv0DtC2AkdlebyUMYXe4npQfNzA1
+6QeAXjg43RoaINx9uLEmA9wI5Po1Uj/j0wIom7mtfl8KAAUhHdcdSspnqbM2Jlp2
+OdX4rnv9yKI+s655mbO7JkHyc8REiFl0qwOc6kIuikr17SpPj4jm7hyCEI1FiBKh
+302xwERedltNkPk2YgifvNfiSbbN95q0a+hpQi3g2+r369RSFnjAkiltRLrylkyy
+vQWdWyVf+H6BR0nQ9Sst28Xr68ys+1O+IFnXnorbZU98wSTBJQ9x10h8u1OChPzZ
++gZQfwUK6QEmOkALmFliqAUm7B7zRgm9jLrUrAfbjJmYv6qC+gPnf/MlnBQ099ho
+vqiNTA+C9QDmER2PoS4r
+=U+qh
+-----END PGP SIGNATURE-----
+
+```
diff --git a/locale/uk/blog/uncategorized/an-easy-way-to-build-scalable-network-programs.md b/locale/uk/blog/uncategorized/an-easy-way-to-build-scalable-network-programs.md
new file mode 100755
index 0000000000000..f1e1391f92889
--- /dev/null
+++ b/locale/uk/blog/uncategorized/an-easy-way-to-build-scalable-network-programs.md
@@ -0,0 +1,19 @@
+---
+title: An Easy Way to Build Scalable Network Programs
+author: ryandahl
+date: 2011-10-04T22:39:56.000Z
+status: publish
+category: Uncategorized
+slug: an-easy-way-to-build-scalable-network-programs
+layout: blog-post.hbs
+---
+
+Suppose you're writing a web server which does video encoding on each file upload. Video encoding is very much compute bound. Some recent blog posts suggest that Node.js would fail miserably at this.
+
+Using Node does not mean that you have to write a video encoding algorithm in JavaScript (a language without even 64 bit integers) and crunch away in the main server event loop. The suggested approach is to separate the I/O bound task of receiving uploads and serving downloads from the compute bound task of video encoding. In the case of video encoding this is accomplished by forking out to ffmpeg. Node provides advanced means of asynchronously controlling subprocesses for work like this.
+
+It has also been suggested that Node does not take advantage of multicore machines. Node has long supported load-balancing connections over multiple processes in just a few lines of code - in this way a Node server will use the available cores. In coming releases we'll make it even easier: just pass <code>--balance</code> on the command line and Node will manage the cluster of processes.
+
+Node has a clear purpose: provide an easy way to build scalable network programs. It is not a tool for every problem. Do not write a ray tracer with Node. Do not write a web browser with Node. Do however reach for Node if tasked with writing a DNS server, DHCP server, or even a video encoding server.
+
+By relying on the kernel to schedule and preempt computationally expensive tasks and to load balance incoming connections, Node appears less magical than server platforms that employ userland scheduling. So far, our focus on simplicity and transparency has paid off: <a href="http://www.joyent.com/blog/node-js-meetup-distributed-web-architectures/">the</a> <a href="http://venturebeat.com/2011/08/16/linkedin-node/">number</a> <a href="http://corp.klout.com/blog/2011/10/the-tech-behind-klout-com/">of</a> <a href="http://www.joelonsoftware.com/items/2011/09/13.html">success</a> <a href="http://pow.cx/">stories</a> from developers and corporations who are adopting the technology continues to grow.
diff --git a/locale/uk/blog/uncategorized/bnoordhuis-departure.md b/locale/uk/blog/uncategorized/bnoordhuis-departure.md
new file mode 100755
index 0000000000000..877935027773b
--- /dev/null
+++ b/locale/uk/blog/uncategorized/bnoordhuis-departure.md
@@ -0,0 +1,20 @@
+---
+title: Ben Noordhuis's Departure
+date: 2013-12-03T22:13:57.000Z
+slug: bnoordhuis-departure
+layout: blog-post.hbs
+---
+
+As of this past weekend, Ben Noordhuis has decided to step away from
+Node.js and libuv, and is no longer acting as a core committer.
+
+Ben has done a tremendous amount of great work in the past. We're sad
+to lose the benefit of his continued hard work and expertise, and
+extremely grateful for what he has added to Node.js and libuv over the
+years.
+
+Many of you already have expressed your opinion regarding recent
+drama, and I'd like to ask that you please respect our wishes to let
+this issue rest, so that we can all focus on the road forward.
+
+Thanks.
diff --git a/locale/uk/blog/uncategorized/development-environment.md b/locale/uk/blog/uncategorized/development-environment.md
new file mode 100755
index 0000000000000..7fbd77c847c36
--- /dev/null
+++ b/locale/uk/blog/uncategorized/development-environment.md
@@ -0,0 +1,28 @@
+---
+title: Development Environment
+author: ryandahl
+date: 2011-04-05T03:16:27.000Z
+status: publish
+category: Uncategorized
+slug: development-environment
+layout: blog-post.hbs
+---
+
+If you're compiling a software package because you need a particular version (e.g. the latest), then it requires a little bit more maintenance than using a package manager like <code>dpkg</code>. Software that you compile yourself should *not* go into <code>/usr</code>, it should go into your home directory. This is part of being a software developer. 
+
+One way of doing this is to install everything into <code>$HOME/local/$PACKAGE</code>. Here is how I install node on my machine:<pre>./configure --prefix=$HOME/local/node-v0.4.5 &amp;&amp; make install</pre>
+
+To have my paths automatically set I put this inside my <code>$HOME/.zshrc</code>:<pre>PATH="$HOME/local/bin:/opt/local/bin:/usr/bin:/sbin:/bin"
+LD_LIBRARY_PATH="/opt/local/lib:/usr/local/lib:/usr/lib"
+for i in $HOME/local/*; do
+  [ -d $i/bin ] &amp;&amp; PATH="${i}/bin:${PATH}"
+  [ -d $i/sbin ] &amp;&amp; PATH="${i}/sbin:${PATH}"
+  [ -d $i/include ] &amp;&amp; CPATH="${i}/include:${CPATH}"
+  [ -d $i/lib ] &amp;&amp; LD_LIBRARY_PATH="${i}/lib:${LD_LIBRARY_PATH}"
+  [ -d $i/lib/pkgconfig ] &amp;&amp; PKG_CONFIG_PATH="${i}/lib/pkgconfig:${PKG_CONFIG_PATH}"
+  [ -d $i/share/man ] &amp;&amp; MANPATH="${i}/share/man:${MANPATH}"
+done</pre>
+
+Node is under sufficiently rapid development that <i>everyone</i> should be compiling it themselves. A corollary of this is that <code>npm</code> (which should be installed alongside Node) does not require root to install packages.
+
+CPAN and RubyGems have blurred the lines between development tools and system package managers. With <code>npm</code> we wish to draw a clear line: it is not a system package manager. It is not for installing firefox or ffmpeg or OpenSSL; it is for rapidly downloading, building, and setting up Node packages. <code>npm</code> is a <i>development</i> tool. When a program written in Node becomes sufficiently mature it should be distributed as a tarball, <code>.deb</code>, <code>.rpm</code>, or other package system. It should not be distributed to end users with <code>npm</code>.
diff --git a/locale/uk/blog/uncategorized/evolving-the-node-js-brand.md b/locale/uk/blog/uncategorized/evolving-the-node-js-brand.md
new file mode 100755
index 0000000000000..1d51c80222cf7
--- /dev/null
+++ b/locale/uk/blog/uncategorized/evolving-the-node-js-brand.md
@@ -0,0 +1,37 @@
+---
+title: Evolving the Node.js Brand
+author: Emily Tanaka-Delgado
+date: 2011-07-11T19:02:45.000Z
+status: publish
+category: Uncategorized
+slug: evolving-the-node-js-brand
+layout: blog-post.hbs
+---
+
+To echo <a href="https://nodejs.org/">Node</a>’s evolutionary nature, we have refreshed the identity to help mark an exciting time for developers, businesses and users who benefit from the pioneering technology.
+
+<strong>Building a brand</strong>
+
+We began exploring elements to express Node.js and jettisoned preconceived notions about what we thought Node should look like, and focused on what Node is: <strong>kinetic</strong>,<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:32"></ins><strong>connected</strong>, <strong>scalable</strong>, <strong>modular</strong>, <strong>mechanical</strong> and <strong>organic</strong>. Working with designer <a href="http://www.chrisglass.com">Chris Glass</a>, our explorations emphasized Node's dynamism and formed a visual language based on structure, relationships and interconnectedness.
+
+<img class="alignnone size-full wp-image-184" title="grid" src="https://nodeblog.files.wordpress.com/2011/07/grid.png" alt="" width="520" height="178" />
+
+Inspired by <strong>process visualization, </strong>we discovered pattern, form, and by relief, the hex shape. The angled infrastructure encourages energy to move through the letterforms.
+
+<img class="alignnone size-full wp-image-185" title="nodejs" src="https://nodeblog.files.wordpress.com/2011/07/nodejs.png" alt="" width="520" height="178" />
+
+This language can expand into the organic network topography of Node or distill down into a single hex connection point.
+
+This scaling represents the dynamic nature of Node in a simple, distinct manner.
+
+<img title="Node.js network" src="https://joyeur.files.wordpress.com/2011/07/network.png" alt="" width="560" height="270" />
+
+We look forward to exploring<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:30"> </ins>this visual language as the technology charges into a very promising future.
+
+<img title="Node.js nebula" src="https://joyeur.files.wordpress.com/2011/07/node.png" alt="" width="560" height="460" />
+
+We hope you'll have fun using it.
+
+To download the new logo, visit <a href="https://nodejs.org/en/about/resources/">nodejs.org/en/about/resources/</a>.
+
+<ins cite="mailto:EMILY%20TANAKA-DELGADO" datetime="2011-07-09T18:32"><img title="Tri-color Node" src="https://joyeur.files.wordpress.com/2011/07/tri-color-node.png" alt="" width="560" height="180" /></ins>
diff --git a/locale/uk/blog/uncategorized/growing-up.md b/locale/uk/blog/uncategorized/growing-up.md
new file mode 100755
index 0000000000000..57fd44251544a
--- /dev/null
+++ b/locale/uk/blog/uncategorized/growing-up.md
@@ -0,0 +1,15 @@
+---
+title: Growing up
+author: ryandahl
+date: 2011-12-15T19:59:15.000Z
+status: publish
+category: Uncategorized
+slug: growing-up
+layout: blog-post.hbs
+---
+
+This week Microsoft announced <a href="https://www.windowsazure.com/en-us/develop/nodejs/">support for Node in Windows Azure</a>, their cloud computing platform. For the Node core team and the community, this is an important milestone. We've worked hard over the past six months reworking Node's machinery to support IO completion ports and Visual Studio to provide a good native port to Windows. The overarching goal of the port was to expand our user base to the largest number of developers. Happily, this has paid off in the form of being a first class citizen on Azure. Many users who would have never used Node as a pure unix tool are now up and running on the Windows platform. More users translates into a deeper and better ecosystem of modules, which makes for a better experience for everyone.
+
+We also redesigned <a href="https://nodejs.org">our website</a> - something that we've put off for a long time because we felt that Node was too nascent to dedicate marketing to it. But now that we have binary distributions for Macintosh and Windows, have bundled npm, and are <a href="https://twitter.com/#!/mranney/status/145778414165569536">serving millions of users</a> at various companies, we felt ready to indulge in a new website and share of a few of our success stories on the home page.
+
+Work is on-going. We continue to improve the software, making performance improvements and adding isolate support, but Node is growing up.
diff --git a/locale/uk/blog/uncategorized/index.md b/locale/uk/blog/uncategorized/index.md
new file mode 100755
index 0000000000000..173323545cc10
--- /dev/null
+++ b/locale/uk/blog/uncategorized/index.md
@@ -0,0 +1,6 @@
+---
+title: Uncategorized
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/uncategorized/jobs-nodejs-org.md b/locale/uk/blog/uncategorized/jobs-nodejs-org.md
new file mode 100755
index 0000000000000..c75e9d9ad7696
--- /dev/null
+++ b/locale/uk/blog/uncategorized/jobs-nodejs-org.md
@@ -0,0 +1,17 @@
+---
+title: jobs.nodejs.org
+author: ryandahl
+date: 2011-03-25T06:05:22.000Z
+status: publish
+category: Uncategorized
+slug: jobs-nodejs-org
+layout: blog-post.hbs
+---
+
+We are starting an official jobs board for Node. There are two goals for this
+
+1. Promote the small emerging economy around this platform by having a central space for employers to find Node programmers.
+
+2. Make some money. We work hard to build this platform and taking a small tax for job posts seems a like reasonable "tip jar".
+
+<a href="http://jobs.nodejs.org">jobs.nodejs.org</a>
diff --git a/locale/uk/blog/uncategorized/ldapjs-a-reprise-of-ldap.md b/locale/uk/blog/uncategorized/ldapjs-a-reprise-of-ldap.md
new file mode 100755
index 0000000000000..933199ac862f0
--- /dev/null
+++ b/locale/uk/blog/uncategorized/ldapjs-a-reprise-of-ldap.md
@@ -0,0 +1,87 @@
+---
+title: "ldapjs: A reprise of LDAP"
+author: mcavage
+date: 2011-09-08T21:25:43.000Z
+status: publish
+category: Uncategorized
+slug: ldapjs-a-reprise-of-ldap
+layout: blog-post.hbs
+---
+
+This post has been about 10 years in the making. My first job out of college was at IBM working on the <a title="Tivoli Directory Server" href="http://www-01.ibm.com/software/tivoli/products/directory-server/">Tivoli Directory Server</a>, and at the time I had a preconceived notion that working on anything related to Internet RFCs was about as hot as you could get. I spent a lot of time back then getting "down and dirty" with everything about LDAP: the protocol, performance, storage engines, indexing and querying, caching, customer use cases and patterns, general network server patterns, etc. Basically, I soaked up as much as I possibly could while I was there. On top of that, I listened to all the "gray beards" tell me about the history of LDAP, which was a bizarre marriage of telecommunications conglomerates and graduate students. The point of this blog post is to give you a crash course in LDAP, and explain what makes <a title="ldapjs" href="http://ldapjs.org">ldapjs</a> different. Allow me to be the gray beard for a bit...
+<h2>What is LDAP and where did it come from?</h2>
+
+Directory services were largely pioneered by the telecommunications companies (e.g., AT&amp;T) to allow fast information retrieval of all the crap you'd expect would be in a telephone book and directory. That is, given a name, or an address, or an area code, or a number, or a foo support looking up customer records, billing information, routing information, etc. The efforts of several telcos came to exist in the <a title="X.500" href="http://en.wikipedia.org/wiki/X.500">X.500</a> standard(s). An X.500 directory is one of the most complicated beasts you can possibly imagine, but on a high note, there's
+probably not a thing you can imagine in a directory service that wasn't thought of in there. It is literally the kitchen sink. Oh, and it doesn't run over IP (it's <em>actually</em> on the <a title="OSI Model" href="http://en.wikipedia.org/wiki/OSI_model">OSI</a> model).
+
+Several years after X.500 had been deployed (at telcos, academic institutions, etc.), it became clear that the Internet was "for real." <a title="LDAP" href="http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol">LDAP</a>, the "Lightweight Directory Access Protocol," was invented to act purely as an IP-accessible gateway to an X.500 directory.
+
+At some point in the early 90's, a <a title="Tim Howes" href="http://en.wikipedia.org/wiki/Tim_Howes">graduate student</a> at the University of Michigan (with some help) cooked up the "grandfather" implementation of the LDAP protocol, which wasn't actually a "gateway," but rather a stand-alone implementation of LDAP. Said implementation, like many things at the time, was a process-per-connection concurrency model, and had "backends" (aka storage engine) for the file system and the Unix DB API. At some point the <a title="Berkeley Database" href="http://www.oracle.com/technetwork/database/berkeleydb/index.html">Berkeley Database </a>(BDB) was put in, and still remains the de facto storage engine for most LDAP directories.
+
+Ok, so some a graduate student at UM wrote an LDAP server that wasn't a gateway. So what? Well, that UM code base turns out to be the thing that pretty much every vendor did a source license for. Those graduate students went off to Netscape later in the 90's, and largely dominated the market of LDAP middleware until <a title="Active Directory" href="http://en.wikipedia.org/wiki/Active_Directory">Active Directory</a> came along many years later (as far as I know, Active Directory is "from scratch", since while it's "almost" LDAP, it's different in a lot of ways). That Netscape code base was further bought and sold over the years to iPlanet, Sun Microsystems, and Red Hat (I'm probably missing somebody in that chain). It now lives in the Fedora umbrella as '<a title="389 Directory Server" href="http://directory.fedoraproject.org/">389 Directory Server</a>.' Probably the most popular fork of that code base now is <a title="OpenLDAP" href="http://www.openldap.org/">OpenLDAP</a>.
+
+IBM did the same thing, and the Directory Server I worked on was a fork of the UM code too, but it heavily diverged from the Netscape branches. The divergence was primarily due to: (1) backing to DB2 as opposed to BDB, and (2) needing to run on IBM's big iron like OS/400 and Z series mainframes.
+
+Macro point is that there have actually been very few "fresh" implementations of LDAP, and it gets a pretty bad reputation because at the end of the day you've got 20 years of "bolt-ons" to grad student code. Oh, and it was born out of ginormous telcos, so of course the protocol is overly complex.
+
+That said, while there certainly is some wacky stuff in the LDAP protocol itself, it really suffered from poor and buggy implementations more than the fact that LDAP itself was fundamentally flawed. As <a title="Engine Yard LDAP" href="http://www.engineyard.com/blog/2009/ldap-directories-the-forgotten-nosql/">engine yard pointed out a few years back</a>, you can think of LDAP as the original NoSQL store.
+<h2>LDAP: The Good Parts</h2>
+
+So what's awesome about LDAP? Since it's a directory system it maintains a hierarchy of your data, which as an information management pattern aligns
+with _a lot_ of use case (the quintessential example is white pages for people in your company, but subscriptions to SaaS applications, "host groups"
+for tracking machines/instances, physical goods tracking, etc., all have use cases that fit that organization scheme). For example, presumably at your job
+you have a "reporting chain." Let's say a given record in LDAP (I'll use myself as a guinea pig here) looks like:
+<pre>    firstName: Mark
+    lastName: Cavage
+    city: Seattle
+    uid: markc
+    state: Washington
+    mail: mcavagegmailcom
+    phone: (206) 555-1212
+    title: Software Engineer
+    department: 123456
+    objectclass: joyentPerson</pre>
+The record for me would live under the tree of engineers I report to (and as an example some other popular engineers under said vice president) would look like:
+<pre>                   uid=david
+                    /
+               uid=bryan
+            /      |      \
+      uid=markc  uid=ryah  uid=isaacs</pre>
+Ok, so we've got a tree. It's not tremendously different from your filesystem, but how do we find people? LDAP has a rich search filter syntax that makes a lot of sense for key/value data (far more than tacking Map Reduce jobs on does, imo), and all search queries take a "start point" in the tree. Here's an example: let's say I wanted to find all "Software Engineers" in the entire company, a filter would look like:
+<pre>     (title="Software Engineer")</pre>
+And I'd just start my search from 'uid=david' in the example above. Let's say I wanted to find all software engineers who worked in Seattle:
+<pre>     (&amp;(title="Software Engineer")(city=Seattle))</pre>
+I could keep going, but the gist is that LDAP has "full" boolean predicate logic, wildcard filters, etc. It's really rich.
+
+Oh, and on top of the technical merits, better or worse, it's an established standard for both administrators and applications (i.e., most "shipped" intranet software has either a local user repository or the ability to leverage an LDAP server somewhere). So there's a lot of compelling reasons to look at leveraging LDAP.
+<h2>ldapjs: Why do I care?</h2>
+
+As I said earlier, I spent a lot of time at IBM observing how customers used LDAP, and the real items I took away from that experience were:
+<ul>
+	<li>LDAP implementations have suffered a lot from never having been designed from the ground up for a large number of concurrent connections with asynchronous operations.</li>
+	<li>There are use cases for LDAP that just don't always fit the traditional "here's my server and storage engine" model. A lot of simple customer use cases wanted an LDAP access point, but not be forced into taking the heavy backends that came with it (they wanted the original gateway model!). There was an entire "sub" industry for this known as "<a title="Metadirectory" href="http://en.wikipedia.org/wiki/Metadirectory">meta directories</a>" back in the late 90's and early 2000's.</li>
+	<li>Replication was always a sticking point. LDAP vendors all tried to offer a big multi-master, multi-site replication model. It was a lot of "bolt-on" complexity, done before the <a title="CAP Theorem" href="http://en.wikipedia.org/wiki/CAP_theorem">CAP theorem</a> was written, and certainly before it was accepted as "truth."</li>
+	<li>Nobody uses all of the protocol. In fact, 20% of the features solve 80% of the use cases (I'm making that number up, but you get the idea).</li>
+</ul>
+
+For all the good parts of LDAP, those are really damned big failing points, and even I eventually abandoned LDAP for the greener pastures of NoSQL somewhere
+along the way. But it always nagged at me that LDAP didn't get it's due because of a lot of implementation problems (to be clear, if I could, I'd change some
+aspects of the protocol itself too, but that's a lot harder).
+
+Well, in the last year, I went to work for <a title="Joyent" href="http://www.joyent.com/">Joyent</a>, and like everyone else, we have several use problems that are classic directory service problems. If you break down the list I outlined above:
+<ul>
+	<li><strong>Connection-oriented and asynchronous:</strong> Holy smokes batman, <a title="node.js" href="https://nodejs.org/">node.js</a> is a completely kick-ass event-driven asynchronous server platform that manages connections like a boss. Check!</li>
+	<li><strong>Lots of use cases:</strong> Yeah, we've got some. Man, the <a title="sinatra" href="http://www.sinatrarb.com/">sinatra</a>/<a title="express" href="http://expressjs.com/">express</a> paradigm is so easy to slap over anything. How about we just do that and leave as many use cases open as we can. Check!</li>
+	<li><strong>Replication is hard. CAP is right:</strong> There are a lot of distributed databases out vying to solve exactly this problem. At Joyent we went with <a title="Riak" href="http://www.basho.com/">Riak</a>. Check!</li>
+	<li><strong>Don't need all of the protocol:</strong> I'm lazy. Let's just skip the stupid things most people don't need. Check!</li>
+</ul>
+
+So that's the crux of ldapjs right there. Giving you the ability to put LDAP back into your application while nailing those 4 fundamental problems that plague most existing LDAP deployments.
+
+The obvious question is how it turned out, and the answer is, honestly, better than I thought it would. When I set out to do this, I actually assumed I'd be shipping a much smaller percentage of the RFC than is there. There's actually about 95% of the core RFC implemented. I wasn't sure if the marriage of this protocol to node/JavaScript would work out, but if you've used express ever, this should be _really_ familiar. And I tried to make it as natural as possible to use "pure" JavaScript objects, rather than requiring the developer to understand <a title="ASN.1" href="http://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One">ASN.1</a> (the binary wire protocol) or the<a title="RFC 4510" href="http://tools.ietf.org/html/rfc4510"> LDAP RFC</a> in detail (this one mostly worked out; ldap_modify is still kind of a PITA).
+
+Within 24 hours of releasing ldapjs on <a title="twitter" href="http://twitter.com/#!/mcavage/status/106767571012952064">Twitter</a>, there was an <a title="github ldapjs address book" href="https://gist.github.com/1173999">implementation of an address book</a> that works with Thunderbird/Evolution, by the end of that weekend there was some <a href="http://i.imgur.com/uR16U.png">slick integration with CouchDB</a>, and ldapjs even got used in one of the <a href="http://twitter.com/#!/jheusala/status/108977708649811970">node knockout apps</a>. Off to a pretty good start!
+
+<h2>The Road Ahead</h2>
+
+Hopefully you've been motivated to learn a little bit more about LDAP and try out <a href="http://ldapjs.org">ldapjs</a>. The best place to start is probably the <a title="ldapjs guide" href="http://ldapjs.org/guide.html">guide</a>. After that you'll probably need to pick up a book from <a href="http://www.amazon.com/Understanding-Deploying-LDAP-Directory-Services/dp/0672323168">back in the day</a>. ldapjs itself is still in its infancy; there's quite a bit of room to add some slick client-side logic (e.g., connection pools, automatic reconnects), easy to use schema validation, backends, etc. By the time this post is live, there will be experimental <a href="http://en.wikipedia.org/wiki/DTrace">dtrace</a> support if you're running on Mac OS X or preferably Joyent's <a href="http://smartos.org/">SmartOS</a> (shameless plug). And that nagging percentage of the protocol I didn't do will get filled in over time I suspect. If you've got an interest in any of this, send me some pull requests, but most importantly, I just want to see LDAP not just be a skeleton in the closet and get used in places where you should be using it. So get out there and write you some LDAP.
diff --git a/locale/uk/blog/uncategorized/libuv-status-report.md b/locale/uk/blog/uncategorized/libuv-status-report.md
new file mode 100755
index 0000000000000..fcba0bcf9aaba
--- /dev/null
+++ b/locale/uk/blog/uncategorized/libuv-status-report.md
@@ -0,0 +1,48 @@
+---
+title: libuv status report
+author: ryandahl
+date: 2011-09-23T19:45:50.000Z
+status: publish
+category: Uncategorized
+slug: libuv-status-report
+layout: blog-post.hbs
+---
+
+We <a href="http://blog.nodejs.org/2011/06/23/porting-node-to-windows-with-microsoft%E2%80%99s-help/">announced</a> back in July that with Microsoft's support Joyent would be porting Node to Windows. This effort is ongoing but I thought it would be nice to make a status report post about the new platform library <code><a href="https://github.com/libuv/libuv">libuv</a></code> which has resulted from porting Node to Windows.
+
+<code>libuv</code>'s purpose is to abstract platform-dependent code in Node into one place where it can be tested for correctness and performance before bindings to V8 are added. Since Node is totally non-blocking, <code>libuv</code> turns out to be a rather useful library itself: a BSD-licensed, minimal, high-performance, cross-platform networking library.
+
+We attempt to not reinvent the wheel where possible. The entire Unix backend sits heavily on Marc Lehmann's beautiful libraries <a href="http://software.schmorp.de/pkg/libev.html">libev</a> and <a href="http://software.schmorp.de/pkg/libeio.html">libeio</a>. For DNS we integrated with Daniel Stenberg's <a href="http://c-ares.haxx.se/">C-Ares</a>. For cross-platform build-system support we're relying on Chrome's <a href="http://code.google.com/p/gyp/">GYP</a> meta-build system.
+
+The current implemented features are:
+<ul>
+    <li>Non-blocking TCP sockets (using IOCP on Windows)</li>
+    <li>Non-blocking named pipes</li>
+    <li>UDP</li>
+    <li>Timers</li>
+    <li>Child process spawning</li>
+    <li>Asynchronous DNS via <a href="http://c-ares.haxx.se/">c-ares</a> or <code>uv_getaddrinfo</code>.</li>
+    <li>Asynchronous file system APIs <code>uv_fs_*</code></li>
+    <li>High resolution time <code>uv_hrtime</code></li>
+    <li>Current executable path look up <code>uv_exepath</code></li>
+    <li>Thread pool scheduling <code>uv_queue_work</code></li>
+</ul>
+The features we are working on still are
+<ul>
+    <li>File system events (Currently supports inotify, <code>ReadDirectoryChangesW</code> and will support kqueue and event ports in the near future.) <code>uv_fs_event_t</code></li>
+    <li>VT100 TTY <code>uv_tty_t</code></li>
+    <li>Socket sharing between processes <code>uv_ipc_t (<a href="https://gist.github.com/1233593">planned API</a>)</code></li>
+</ul>
+For complete documentation see the header file: <a href="https://github.com/libuv/libuv/blob/03d0c57ea216abd611286ff1e58d4e344a459f76/include/uv.h">include/uv.h</a>. There are a number of tests in <a href="https://github.com/libuv/libuv/tree/3ca382be741ec6ce6a001f0db04d6375af8cd642/test">the test directory</a> which demonstrate the API.
+
+<code>libuv</code> supports Microsoft Windows operating systems since Windows XP SP2. It can be built with either Visual Studio or MinGW. Solaris 121 and later using GCC toolchain. Linux 2.6 or better using the GCC toolchain. Macinotsh Darwin using the GCC or XCode toolchain. It is known to work on the BSDs but we do not check the build regularly.
+
+In addition to Node v0.5, a number of projects have begun to use <code>libuv</code>:
+<ul>
+    <li>Mozilla's <a href="https://github.com/graydon/rust">Rust</a></li>
+    <li>Tim Caswell's <a href="https://github.com/creationix/luanode">LuaNode</a></li>
+    <li>Ben Noordhuis and Bert Belder's <a href="https://github.com/bnoordhuis/phode">Phode</a> async PHP project</li>
+    <li>Kerry Snyder's <a href="https://github.com/kersny/libuv-csharp">libuv-csharp</a></li>
+    <li>Andrea Lattuada's <a href="https://gist.github.com/1195428">web server</a></li>
+</ul>
+We hope to see more people contributing and using <code>libuv</code> in the future!
diff --git a/locale/uk/blog/uncategorized/node-interactive-convince-boss.md b/locale/uk/blog/uncategorized/node-interactive-convince-boss.md
new file mode 100755
index 0000000000000..b13aeac5e1401
--- /dev/null
+++ b/locale/uk/blog/uncategorized/node-interactive-convince-boss.md
@@ -0,0 +1,35 @@
+---
+title: “Convince Your Boss” Letter
+date: 2015-10-22T17:00:00.000Z
+status: publish
+category: Uncategorized
+slug: node-interactive-convince-boss
+layout: blog-post.hbs
+---
+
+Want to attend Node.js Interactive happening in Portland from December 8-9, 2015, but don’t know how to bring it up to your boss (the person with the money)? We laid out a simple letter explaining why it is important. Use it in full or use snippets of it, whatever it takes to get you in Portland, OR!
+
+#### “Convince Your Boss” Letter 
+
+Dear `Boss Name`,
+
+I’d like to attend **[Node.js Interactive 2015](http://events.linuxfoundation.org/events/node-interactive)** taking place December 8-9, 2015, in Portland, OR. There are a lot of Node.js conferences during the year, but this is the premier conference put on by the Node.js Foundation. Vendor-neutral by design, it is focused on everything from fine-tuning my skills in Node.js to the future of the platform. Node.js is penetrating almost every single aspect of technology from powering robots to enterprise, and is downloaded 2 million times per month. It’s a pretty big deal.
+
+They are anticipating more than 700 individuals will attend the event. The conference welcomes experienced developers as well as those interested in learning how to implement Node.js into their business, and everyone inbetween. The tracks focus on IoT, frontend and backend technologies. Here are just a few advantages of me going to the conference. 
+* One of the great features about the technology is how diverse it is. It can be used to build mobile apps or enterprise apps, and almost every single big named company is using it from LinkedIn to IBM to Netflix. If we decide to build out our product strategy or offering, it is likely that Node.js will be the technology that I use across the board. 
+
+* There will be more than 50 sessions in the two day conference. These sessions include visionary keynotes, hands-on tutorials, deep-dive technical lectures, and presentations.
+
+* The session will not only craft my skills with Node.js, but also help me learn how best to adopt the technology to our business for smoother transitions and a more united IT team.
+
+* Key session include: how to build and engage high performance teams in the Node.js ecosystem, home automation with Node.js, how to develop Node.js in the next-generation of IoT, Node International: Where We Are and What's Next, and many more. The full list of program can be found [here](http://nodejspdx2015.sched.org/). 
+
+* There are some awesome companies presenting including Uber, IBM, Intel, New Relic, Eventbrite, Bloomberg L.P, Microsoft, Getty Images and more.
+
+Early bird registration price of US$325 ends Friday, October 23, 2015. It includes registration and full access to all of the events happening at the Node.js Interactive. Standard registration closes November 21, 2015, after which the conference price will increase from $425 to $525. Discounted hotel rates are also available until Wednesday, November 11, 2015. 
+
+I would be happy to write a post-conference report and share with other members of the team on what I’ve learned and how we can implement Node.js as well as open source governing practices into our business strategy.
+
+Thanks,
+
+`Your Name`
diff --git a/locale/uk/blog/uncategorized/node-meetup-this-thursday.md b/locale/uk/blog/uncategorized/node-meetup-this-thursday.md
new file mode 100755
index 0000000000000..73d4b31c402d3
--- /dev/null
+++ b/locale/uk/blog/uncategorized/node-meetup-this-thursday.md
@@ -0,0 +1,14 @@
+---
+title: Node Meetup this Thursday
+author: ryandahl
+date: 2011-08-03T04:37:02.000Z
+status: publish
+category: Uncategorized
+slug: node-meetup-this-thursday
+layout: blog-post.hbs
+---
+
+<a href="https://nodejs.org/meetup/" title="https://nodejs.org/meetup/ ">https://nodejs.org/meetup/</a>
+<a href="http://nodemeetup.eventbrite.com/">http://nodemeetup.eventbrite.com/</a>
+
+Three companies will describe their distributed Node applications. Sign up soon, space is limited!
diff --git a/locale/uk/blog/uncategorized/node-office-hours-cut-short.md b/locale/uk/blog/uncategorized/node-office-hours-cut-short.md
new file mode 100755
index 0000000000000..7195c41e01063
--- /dev/null
+++ b/locale/uk/blog/uncategorized/node-office-hours-cut-short.md
@@ -0,0 +1,15 @@
+---
+title: Node Office Hours Cut Short
+author: ryandahl
+date: 2011-04-28T16:04:35.000Z
+status: publish
+category: Uncategorized
+slug: node-office-hours-cut-short
+layout: blog-post.hbs
+---
+
+This week office hours are only from 4pm to 6pm. Isaac will be in the Joyent office in SF - everyone else is out of town. Sign up at http://nodeworkup.eventbrite.com/ if you would like to come.
+
+The week after, Thursday May 5th, we will all be at NodeConf in Portland.
+
+Normal office hours resume Thursday May 12th.
diff --git a/locale/uk/blog/uncategorized/notes-from-the-road.md b/locale/uk/blog/uncategorized/notes-from-the-road.md
new file mode 100755
index 0000000000000..9495613d29a6c
--- /dev/null
+++ b/locale/uk/blog/uncategorized/notes-from-the-road.md
@@ -0,0 +1,103 @@
+---
+title: Notes from the Road
+author: tjfontaine
+date: 2014-06-11T16:00:00.000Z
+status: publish
+category: Uncategorized
+slug: notes-from-the-road
+layout: blog-post.hbs
+---
+
+## Notes from the Road
+
+As Project Lead for Node.js, I was excited to have the opportunity to go on the
+road and bring production stories to all of our users. We've had amazing
+speakers and turn out in San Francisco, Seattle, Portland, Boston, and New
+York. But I wanted to make sure we reached more than just our coasts, so soon
+we'll be in
+[Minneapolis](http://www.joyent.com/noderoad/cities/minneapolis-6-17-2014) and
+I'll be returning to my home state of Ohio and doing an event in
+[Cincinnati](http://www.joyent.com/noderoad/cities/cincinnati-6-19-2014). The
+Node.js community is all over the world, and hopefully Node on the Road can
+reach as many of you as it can. Nominate your city to be a future stop on the
+Node.js on the Road series
+[here](http://www.joyent.com/noderoad/cities/suggest).
+
+These Node on the Road events are successful because of the incredible support
+from the community and the existing meetup organizations in their respective
+cities. But the biggest advantage is that the project gets to solicit feedback
+directly from our users about what is and isn't working for them in Node.js,
+what modules they're using, and where they need Node to do better.
+
+## Release schedules
+
+Some of the feedback we've received has been about the upgrade process for
+Node. Veteran Node.js alums will occasionally sit around campfires and tell the
+stories of when things would break every release, or how long they stayed on
+0.4 before upgrading to 0.6. Some production companies are still out there
+running on 0.8 afraid to make the jump to 0.10. While other companies advise
+people to avoid upgrading to a new release of a Node version until the patch
+number hits double digits. It's those sorts of stories that make it important
+for us to get the release for 0.12 right, from the get go.
+
+Node is in a fantastic place right now, it's maturing quickly and finding its
+footing in new environments with new users and new use cases. The expectation
+for Node is getting higher each day with every release. There are multiple
+interests at stake, keeping Node lean, keeping it up to date with languages and
+standards, keeping it fast, and balanced with keeping it stable such that we
+don't upset the adoption rate. That means Node needs to make the right choices
+that balance the needs of all of our users without closing the doors to others.
+
+All of these conversations are helping to shape the release process going
+forward, and helping to scope just what does go into a release and how fast
+people want to see those happen. In fact something we've been considering is
+eliminating the confusion around our Stable/Unstable branches, and instead
+moving to releases that are always stable. But it's important that the features
+and changes that go into a release are shaped by user feedback, which is why
+events like Node on the Road are vital.
+
+## Better Documentation
+
+Another key piece of feedback has consistently been around our documentation.
+Users need us to clean up our API reference documentation, there are lots of
+undocumented and under-documented methods and properties that are being used or
+should be used. Node needs to include what errors may be delivered as part of
+the operation of your application, as well as what methods will throw and under
+what circumstances.
+
+But mostly users are looking for more general purpose documentation that can
+help both new and veteran Node.js users be more productive with Node. And the
+people who are most equipped to provide that documentation are the users
+themselves who've already been successful.
+
+## Easier Contribution
+
+Aside from soliciting feedback from users of Node.js and bringing production
+stories to our users, Node on the Road has also been about highlighting the
+various ways you as a member of the community can contribute. There are many
+ways you can contribute from meetups and conferences, to publishing modules, to
+finding issues in modules or core, to fixing issues in modules or core, or even
+adding features to modules or core. Where ever you are passionate about Node.js
+there are ways you can contribute back to Node.
+
+Node.js has inherited many things from our largest dependency V8, we've adopted
+their build system GYP, we use their test runner (which is unfortunately in
+python), and when we were structuring the project we brought along the
+Contributor License Agreement (CLA) that Google uses to manage contributions
+for Chromium and V8. The CLA is there as a way for a project to audit itself
+and to give itself the opportunity to relicense itself in the future if
+necessary. Node.js though is distributed under the venerable
+[MIT](http://opensource.org/licenses/MIT) license, and that's not going to
+change. The MIT license is one of the most permissible open source licenses out
+there, and has fostered a ton of development with Node.js and we want that to
+continue. 
+
+In an effort to make it easier for users to contribute to Node.js the project
+has decided to lift the requirement of signing the CLA before contributions are
+eligible for integration. Having to sign the CLA could at times be a stumbling
+block for a contribution. It could involve a long conversation with your legal
+department to ultimately contribute typo corrections.
+
+I'm excited to see what contributions will be coming from the community in the
+future, excited to see where our users take Node.js, and excited to be
+participating with all of you on this project.
diff --git a/locale/uk/blog/uncategorized/office-hours.md b/locale/uk/blog/uncategorized/office-hours.md
new file mode 100755
index 0000000000000..1ab29e543ba7c
--- /dev/null
+++ b/locale/uk/blog/uncategorized/office-hours.md
@@ -0,0 +1,15 @@
+---
+title: Office Hours
+author: ryandahl
+date: 2011-03-24T04:42:47.000Z
+status: publish
+category: Uncategorized
+slug: office-hours
+layout: blog-post.hbs
+---
+
+Starting next Thursday Isaac, Tom, and I will be holding weekly office hours at <a href="http://maps.google.com/maps?q=345+California+St,+San+Francisco,+CA+94104&amp;layer=c&amp;sll=37.793040,-122.400491&amp;cbp=13,178.31,,0,-60.77&amp;cbll=37.793131,-122.400484&amp;hl=en&amp;sspn=0.006295,0.006295&amp;ie=UTF8&amp;hq=&amp;hnear=345+California+St,+San+Francisco,+California+94104&amp;ll=37.793131,-122.400484&amp;spn=0.001295,0.003428&amp;z=19&amp;panoid=h0dlz3VG-hMKlzOu0LxMIg">Joyent HQ</a> in San Francisco. Office hours are meant to be subdued working time - there are no talks and no alcohol. Bring your bugs or just come and hack with us.
+
+Our building requires that everyone attending be on a list so you must sign up at <a href="http://nodeworkup01.eventbrite.com/">Event Brite</a>.
+
+We start at 4p and end promptly at 8p.
diff --git a/locale/uk/blog/uncategorized/porting-node-to-windows-with-microsofts-help.md b/locale/uk/blog/uncategorized/porting-node-to-windows-with-microsofts-help.md
new file mode 100755
index 0000000000000..56d0f8af2b4ec
--- /dev/null
+++ b/locale/uk/blog/uncategorized/porting-node-to-windows-with-microsofts-help.md
@@ -0,0 +1,15 @@
+---
+title: Porting Node to Windows With Microsoft’s Help
+author: ryandahl
+date: 2011-06-23T22:22:58.000Z
+status: publish
+category: Uncategorized
+slug: porting-node-to-windows-with-microsofts-help
+layout: blog-post.hbs
+---
+
+I'm pleased to announce that Microsoft is partnering with Joyent in formally contributing resources towards porting Node to Windows. As you may have heard in <a href="/static/documents/nodeconf.pdf">a talk</a> we gave earlier this year, we have started the undertaking of a native port to Windows - targeting the high-performance IOCP API.
+ 
+This requires a rather large modification of the core structure, and we're very happy to have official guidance and engineering resources from Microsoft. <a href="https://www.cloudkick.com/">Rackspace</a> is also contributing <a href="https://github.com/piscisaureus">Bert Belder</a>'s time to this undertaking.
+ 
+The result will be an official binary node.exe releases on nodejs.org, which will work on Windows Azure and other Windows versions as far back as Server 2003.
diff --git a/locale/uk/blog/uncategorized/profiling-node-js.md b/locale/uk/blog/uncategorized/profiling-node-js.md
new file mode 100755
index 0000000000000..c03b0b324827f
--- /dev/null
+++ b/locale/uk/blog/uncategorized/profiling-node-js.md
@@ -0,0 +1,62 @@
+---
+title: Profiling Node.js
+author: Dave Pacheco
+date: 2012-04-25T20:48:58.000Z
+status: publish
+category: Uncategorized
+slug: profiling-node-js
+layout: blog-post.hbs
+---
+
+It's incredibly easy to visualize where your Node program spends its time using DTrace and <a href="http://github.com/davepacheco/node-stackvis">node-stackvis</a> (a Node port of Brendan Gregg's <a href="http://github.com/brendangregg/FlameGraph/">FlameGraph</a> tool):
+
+<ol>
+    <li>Run your Node.js program as usual.</li>
+    <li>In another terminal, run:
+        <pre><code>$ dtrace -n 'profile-97/execname == "node" &amp;&amp; arg1/{
+    @[jstack(150, 8000)] = count(); } tick-60s { exit(0); }' &gt; stacks.out</code></pre>
+        This will sample about 100 times per second for 60 seconds and emit results to stacks.out. <strong>Note that this will sample all running programs called "node".  If you want a specific process, replace <code>execname == "node"</code> with <code>pid == 12345</code> (the process id).</strong>
+    </li>
+    <li>Use the "stackvis" tool to transform this directly into a flame graph. First, install it:
+        <pre><code>$ npm install -g stackvis</code></pre>
+        then use <code>stackvis</code> to convert the DTrace output to a flamegraph:
+        <pre><code>$ stackvis dtrace flamegraph-svg &lt; stacks.out &gt; stacks.svg</code></pre>
+    </li>
+    <li>Open stacks.svg in your favorite browser.</li>
+</ol>
+
+You'll be looking at something like this:
+
+<a href="https://www.cs.brown.edu/~dap/helloworld.svg" class="imagelink"><img src="https://www.cs.brown.edu/~dap/helloworld.svg" alt="'Hello World' HTTP server flame graph" /></a>
+
+This is a visualization of all of the profiled call stacks. This example is from the "hello world" HTTP server on the <a href="https://nodejs.org">Node.js</a> home page under load. Start at the bottom, where you have "main", which is present in most Node stacks because Node spends most on-CPU time in the main thread. Above each row, you have the functions called by the frame beneath it. As you move up, you'll see actual JavaScript function names. The boxes in each row are not in chronological order, but their width indicates how much time was spent there. When you hover over each box, you can see exactly what percentage of time is spent in each function. This lets you see at a glance where your program spends its time.
+
+That's the summary. There are a few prerequisites:
+
+<ul>
+    <li>You must gather data on a system that supports DTrace with the Node.js ustack helper. For now, this pretty much means <a href="http://illumos.org/">illumos</a>-based systems like <a href="http://smartos.org/">SmartOS</a>, including the Joyent Cloud. <strong>MacOS users:</strong> OS X supports DTrace, but not ustack helpers. The way to get this changed is to contact your Apple developer liaison (if you're lucky enough to have one) or <strong>file a bug report at bugreport.apple.com</strong>. I'd suggest referencing existing bugs 5273057 and 11206497. More bugs filed (even if closed as dups) show more interest and make it more likely Apple will choose to fix this.</li>
+    <li>You must be on 32-bit Node.js 0.6.7 or later, built <code>--with-dtrace</code>. The helper doesn't work with 64-bit Node yet. On illumos (including SmartOS), development releases (the 0.7.x train) include DTrace support by default.</li>
+</ul>
+
+There are a few other notes:
+
+<ul>
+    <li>You can absolutely profile apps <strong>in production</strong>, not just development, since compiling with DTrace support has very minimal overhead. You can start and stop profiling without restarting your program.</li>
+    <li>You may want to run the stacks.out output through <code>c++filt</code> to demangle C++ symbols. Be sure to use the <code>c++filt</code> that came with the compiler you used to build Node. For example:
+    <pre>c++filt &lt; stacks.out &gt; demangled.out</pre>
+    then you can use demangled.out to create the flamegraph.
+    </li>
+    <li>If you want, you can filter stacks containing a particular function.  The best way to do this is to first collapse the original DTrace output, then grep out what you want:
+        <pre>
+$ stackvis dtrace collapsed &lt; stacks.out | grep SomeFunction &gt; collapsed.out
+$ stackvis collapsed flamegraph-svg &lt; collapsed.out &gt; stacks.svg</pre>
+    </li>
+    <li>If you've used Brendan's FlameGraph tools, you'll notice the coloring is a little different in the above flamegraph. I ported his tools to Node first so I could incorporate it more easily into other Node programs, but I've also been playing with different coloring options. The current default uses hue to denote stack depth and saturation to indicate time spent. (These are also indicated by position and size.) Other ideas include coloring by module (so V8, JavaScript, libc, etc. show up as different colors.)
+    </li>
+</ul>
+
+For more on the underlying pieces, see my <a href="http://dtrace.org/blogs/dap/2012/01/05/where-does-your-node-program-spend-its-time/">previous post on Node.js profiling</a> and <a href="http://dtrace.org/blogs/brendan/2011/12/16/flame-graphs/">Brendan's post on Flame Graphs</a>.
+
+<hr />
+
+Dave Pacheco blogs at <a href="http://dtrace.org/blogs/dap">dtrace.org</a>
diff --git a/locale/uk/blog/uncategorized/some-new-node-projects.md b/locale/uk/blog/uncategorized/some-new-node-projects.md
new file mode 100755
index 0000000000000..bd4c75c9263df
--- /dev/null
+++ b/locale/uk/blog/uncategorized/some-new-node-projects.md
@@ -0,0 +1,16 @@
+---
+title: Some New Node Projects
+author: ryandahl
+date: 2011-08-29T15:30:41.000Z
+status: publish
+category: Uncategorized
+slug: some-new-node-projects
+layout: blog-post.hbs
+---
+
+<ul>
+<li>Superfeedr released <a href="http://blog.superfeedr.com/node-xmpp-server/">a Node XMPP Server</a>. "<i>Since <a href="http://spaceboyz.net/~astro/">astro</a> had been doing an <strong>amazing work</strong> with his <a href="https://github.com/astro/node-xmpp">node-xmpp</a> library to build <em>Client</em>, <em>Components</em> and even <em>Server to server</em> modules, the logical next step was to try to build a <em>Client to Server</em> module so that we could have a full blown server. That&#8217;s what we worked on the past couple days, and <a href="https://github.com/superfeedr/node-xmpp">it&#8217;s now on Github</a>!</i></li>
+
+<li>Joyent's Mark Cavage released <a href="http://ldapjs.org/">LDAP.js</a>. "<i>ldapjs is a pure JavaScript, from-scratch framework for implementing <a href="http://tools.ietf.org/html/rfc4510">LDAP</a> clients and servers in <a href="https://nodejs.org">Node.js</a>.  It is intended for developers used to interacting with HTTP services in node and <a href="http://expressjs.com">express</a>.</i></li>
+
+<li>Microsoft's Tomasz Janczuk released <a href="http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html">iisnode</a> "<i>The <a href="https://github.com/tjanczuk/iisnode">iisnode</a> project provides a native IIS 7.x module that allows hosting of node.js applications in IIS.</i><br /><br />Scott Hanselman posted <a href="http://www.hanselman.com/blog/InstallingAndRunningNodejsApplicationsWithinIISOnWindowsAreYouMad.aspx">a detailed walkthrough</a> of how to get started with iisnode
diff --git a/locale/uk/blog/uncategorized/the-videos-from-node-meetup.md b/locale/uk/blog/uncategorized/the-videos-from-node-meetup.md
new file mode 100755
index 0000000000000..29aa28b0b1512
--- /dev/null
+++ b/locale/uk/blog/uncategorized/the-videos-from-node-meetup.md
@@ -0,0 +1,13 @@
+---
+title: The Videos from the Meetup
+author: ryandahl
+date: 2011-08-12T07:14:34.000Z
+status: publish
+category: Uncategorized
+slug: the-videos-from-node-meetup
+layout: blog-post.hbs
+---
+
+Uber, Voxer, and Joyent described how they use Node in production
+
+<a href="http://www.joyent.com/blog/node-js-meetup-distributed-web-architectures/">http://www.joyent.com/blog/node-js-meetup-distributed-web-architectures/</a>
diff --git a/locale/uk/blog/uncategorized/tj-fontaine-new-node-lead.md b/locale/uk/blog/uncategorized/tj-fontaine-new-node-lead.md
new file mode 100755
index 0000000000000..2917716ffa856
--- /dev/null
+++ b/locale/uk/blog/uncategorized/tj-fontaine-new-node-lead.md
@@ -0,0 +1,57 @@
+---
+title: The Next Phase of Node.js
+date: 2014-01-15T17:00:00.000Z
+author: Isaac Z. Schlueter
+slug: the-next-phase-of-node-js
+layout: blog-post.hbs
+---
+
+Node's growth has continued and accelerated immensely over the last
+few years.  More people are developing and sharing more code with Node
+and npm than I would have ever imagined.  Countless companies are
+using Node, and npm along with it.
+
+Over the last year, [TJ Fontaine](https://twitter.com/tjfontaine) has become absolutely essential to the
+Node.js project.  He's been building releases, managing the test bots,
+[fixing nasty
+bugs](http://www.joyent.com/blog/walmart-node-js-memory-leak) and
+making decisions for the project with constant focus on the needs of
+our users.  He was responsible for an update to MDB to [support
+running ::findjsobjects on Linux core
+dumps](http://www.slideshare.net/bcantrill/node-summit2013), and is
+working on a shim layer that will provide a stable C interface for
+Node binary addons.  In partnership with Joyent and The Node Firm,
+he's helped to create a path forward for scalable issue triaging.
+He's become the primary point of contact keeping us all driving the
+project forward together.
+
+Anyone who's been close to the core project knows that he's been
+effectively leading the project for a while now, so we're making it
+official.  Effective immediately, TJ Fontaine is the Node.js project
+lead.  I will remain a Node core committer, and expect to continue to
+contribute to the project in that role.  My primary focus, however,
+will be npm.
+
+At this point, npm needs work, and I am eager to deliver what the Node
+community needs from its package manager.  I am starting a company,
+npm, Inc., to deliver new products and services related to npm.  I'll
+be sharing many more details soon about exactly how this is going to
+work, and what we'll be offering.  For now, suffice it to say that
+everything currently free will remain free, and everything currently
+flaky will get less flaky.  Pursuing new revenue is how we can keep
+providing the npm registry service in a long-term sustainable way, and
+it has to be done very carefully so that we don't damage what we've
+all built together.
+
+npm is what I'm most passionate about, and I am now in a position to
+give it my full attention.  I've done more than I could have hoped to
+accomplish in running Node core, and it's well past time to hand the
+control of the project off to its next gatekeeper.
+
+TJ is exactly the leader who can help us take Node.js to 1.0 and
+beyond.  He brings professionalism, rigor, and a continued focus on
+inclusive community values and culture.  In the coming days, TJ will
+spell out his plans in greater detail.  I look forward to the places
+that Node will go with his guidance.
+
+Please join me in welcoming him to this new role :)
diff --git a/locale/uk/blog/uncategorized/trademark.md b/locale/uk/blog/uncategorized/trademark.md
new file mode 100755
index 0000000000000..c664559cda638
--- /dev/null
+++ b/locale/uk/blog/uncategorized/trademark.md
@@ -0,0 +1,20 @@
+---
+title: Trademark
+author: ryandahl
+date: 2011-04-29T08:54:18.000Z
+status: publish
+category: Uncategorized
+slug: trademark
+layout: blog-post.hbs
+---
+
+One of the things Joyent accepted when we took on the Node project was to provide resources to help the community grow. The Node project is amazing because of the expertise, dedication and hard work of the community. However in all communities there is the possibility of people acting inappropriately. We decided to introduce trademarks on the “Node.js” and the “Node logo” in order to ensure that people or organisations who are not investing in the Node community misrepresent, or create confusion about the role of themselves or their products with Node.
+
+We are big fans of the people who have contributed to Node and we have worked hard to make sure that existing members of the community will be unaffected by this change. For most people they don’t have to do anything they are free to use the Node.js marks in their free open source projects (see guidelines). For others we’ve already granted them licenses to use Node.js marks in their domain names and their businesses. We value all of these contributions to the Node community and hope that we can continue to protect their good names and hard work.
+
+Where does our trademark policy come from? We started by looking at popular open source foundations like the Apache Software Foundation and Linux. By strongly basing our policy on the one used by the Apache Software Foundation we feel that we’ve created a policy which is liberal enough to allow the open source community to easily make use of the mark in the context of free open source software, but secure enough to protect the community’s work from being misrepresented by other organisations.
+
+While we realize that any changes involving lawyers can be intimidating to the community we want to make this transition as smoothly as possible and welcome your questions and feedback on the policy and how we are implementing it.
+
+<a href="/static/documents/trademark-policy.pdf">trademark-policy.pdf</a>
+trademark@joyent.com
diff --git a/locale/uk/blog/uncategorized/version-0-6.md b/locale/uk/blog/uncategorized/version-0-6.md
new file mode 100755
index 0000000000000..d20be11789dd9
--- /dev/null
+++ b/locale/uk/blog/uncategorized/version-0-6.md
@@ -0,0 +1,26 @@
+---
+title: Version 0.6 Coming Soon
+author: ryandahl
+date: 2011-10-25T22:26:23.000Z
+status: publish
+category: Uncategorized
+slug: version-0-6
+layout: blog-post.hbs
+---
+
+Version 0.6.0 will be released next week. Please spend some time this
+week upgrading your code to v0.5.10. Report any API differences at <a
+href="https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6">https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6</a>
+or report a bug to us at <a
+href="http://github.com/joyent/node/issues">http://github.com/joyent/node/issues</a>
+if you hit problems.
+
+The API changes between v0.4.12 and v0.5.10 are 99% cosmetic, minor,
+and easy to fix. Most people are able to migrate their code in 10
+minutes. Don't fear.
+
+Once you've ported your code to v0.5.10 please help out by testing
+third party modules. Make bug reports. Encourage authors to publish
+new versions of their modules. Go through the list of modules at <a
+href="https://npmjs.com/">npmjs.com</a> and try out random
+ones. This is especially encouraged of Windows users!
diff --git a/locale/uk/blog/video/bert-belder-libuv-lxjs-2012.md b/locale/uk/blog/video/bert-belder-libuv-lxjs-2012.md
new file mode 100755
index 0000000000000..e4f2a0ab5461f
--- /dev/null
+++ b/locale/uk/blog/video/bert-belder-libuv-lxjs-2012.md
@@ -0,0 +1,16 @@
+---
+title: Bert Belder - libuv at LXJS 2012
+slug: bert-belder-libuv-lxjs-2012
+category: video
+date: 2012-09-30T17:28:45.000Z
+layout: blog-post.hbs
+---
+
+Node core committer Bert Belder gave a talk at
+[LXJS](http://2012.lxjs.org/).  If you are interested in how Node does
+asynchronous I/O across platforms, then you should definitely watch
+this video.
+
+<iframe width="640" height="360"
+src="https://www.youtube.com/embed/nGn60vDSxQ4" frameborder="0"
+allowfullscreen></iframe>
diff --git a/locale/uk/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md b/locale/uk/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md
new file mode 100755
index 0000000000000..08782b6514e3d
--- /dev/null
+++ b/locale/uk/blog/video/bryan-cantrill-instrumenting-the-real-time-web.md
@@ -0,0 +1,18 @@
+---
+title: "Bryan Cantrill: Instrumenting the Real Time Web"
+author: Isaac Schlueter
+date: 2012-05-08T17:00:34.000Z
+status: publish
+category: video
+slug: bryan-cantrill-instrumenting-the-real-time-web
+layout: blog-post.hbs
+---
+Bryan Cantrill, VP of Engineering at Joyent, describes the challenges of instrumenting a distributed, dynamic, highly virtualized system -- and what their experiences taught them about the problem, the technologies used to tackle it, and promising approaches.
+
+This talk was given at Velocity Conf in 2011.
+
+<iframe width="640" height="360"
+src="https://www.youtube.com/embed/F5jCXdTYJYc" frameborder="0"
+allowfullscreen></iframe>
+
+<iframe src="https://slideshare.net/slideshow/embed_code/key/DVu5NQDhPXN709" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe> <div style="margin-bottom:5px"> <strong> <a href="https://slideshare.net/bcantrill/instrumenting-the-realtime-web" title="Instrumenting the real-time web" target="_blank">Instrumenting the real-time web</a> </strong> from <strong><a href="//www.slideshare.net/bcantrill" target="_blank">bcantrill</a></strong> </div>
diff --git a/locale/uk/blog/video/index.md b/locale/uk/blog/video/index.md
new file mode 100755
index 0000000000000..0093724485dbb
--- /dev/null
+++ b/locale/uk/blog/video/index.md
@@ -0,0 +1,6 @@
+---
+title: Videos
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/video/welcome-to-the-node-blog.md b/locale/uk/blog/video/welcome-to-the-node-blog.md
new file mode 100755
index 0000000000000..5d4138058db1c
--- /dev/null
+++ b/locale/uk/blog/video/welcome-to-the-node-blog.md
@@ -0,0 +1,15 @@
+---
+title: Welcome to the Node blog
+author: ryandahl
+date: 2011-03-18T03:17:12.000Z
+status: publish
+category: video
+slug: welcome-to-the-node-blog
+layout: blog-post.hbs
+---
+Since Livejournal is disintegrating into Russian spam, I'm moving my technical blog to http://blog.nodejs.org/. I hope to do frequent small posts about what's going on in Node development and include posts from other core Node developers. Please subscribe to the RSS feed.
+
+To avoid making this post completely devoid of content, here is a new video from a talk I gave at the SF PHP group tastefully produced by <A href="http://marakana.com/forums/java/general/278.html">Marakana</a>:
+<iframe width="640" height="360"
+src="https://www.youtube.com/embed/jo_B4LTHi3I" frameborder="0"
+allowfullscreen></iframe>
diff --git a/locale/uk/blog/vulnerability/cve-2015-8027_cve-2015-6764.md b/locale/uk/blog/vulnerability/cve-2015-8027_cve-2015-6764.md
new file mode 100755
index 0000000000000..8a7a8fe3f905d
--- /dev/null
+++ b/locale/uk/blog/vulnerability/cve-2015-8027_cve-2015-6764.md
@@ -0,0 +1,87 @@
+---
+date: 2015-11-25T22:06:05.316Z
+category: vulnerability
+title: CVE-2015-8027 Denial of Service Vulnerability / CVE-2015-6764 V8 Out-of-bounds Access Vulnerability
+slug: cve-2015-8027_cve-2015-6764
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+This announcement is for:
+
+* CVE-2015-8027: a high-impact denial of service vulnerability
+* CVE-2015-6764: a low-impact V8 out-of-bounds access vulnerability
+
+## CVE-2015-8027 Denial of Service Vulnerability
+
+### Description and CVSS Score
+
+A bug exists in Node.js, all versions of v0.12.x through to v5.x inclusive, whereby an external attacker can cause a denial of service. The severity of this issue is high (see CVSS scoring below) and users of the affected versions should plan to upgrade when a fix is made available.
+
+* Versions 0.10.x of Node.js are ***not affected***.
+* Versions 0.12.x of Node.js are ***vulnerable***.
+* Versions 4.x, including LTS Argon, of Node.js are ***vulnerable***.
+* Versions 5.x of Node.js are ***vulnerable***.
+
+Full details of this vulnerability are embargoed until new releases are available on **Wednesday the 2nd of December 2015, UTC** _(Tuesday the 1st of December US time)_.
+
+Common Vulnerability Scoring System (CVSS) v3 Base Score:
+
+| Metric                      | Score                      |
+|-----------------------------|----------------------------|
+| **Base Score:**             | **7.5 (High)**             |
+| **Base Vector:**            | [CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
+| **Attack Vector:**          | Network (AV:N)             |
+| **Attack Complexity:**      | Low (AC:L)                 |
+| **Privileges Required:**    | None (PR:N)                |
+| **User Interaction:**       | None (UI:N)                |
+| **Scope of Impact:**        | Unchanged (S:U)            |
+| **Confidentiality Impact:** | None (C:N)                 |
+| **Integrity Impact:**       | None (I:N)                 |
+| **Availability Impact:**    | High (A:H)                 |
+
+Complete CVSS v3 Vector: [CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:R/CR:L/IR:L/AR:H/MAV:N/MAC:L/MPR:N/MUI:N/MS:U/MC:N/MI:N/MA:H](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:R/CR:L/IR:L/AR:H/MAV:N/MAC:L/MPR:N/MUI:N/MS:U/MC:N/MI:N/MA:H). Refer to the [CVSS v3 Specification](https://www.first.org/cvss/specification-document) for details on the meanings and application of the vector components.
+
+CVE-2015-8027 is listed on the [MITRE CVE dictionary](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8027) and [NIST NVD](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8027).
+
+## CVE-2015-6764 V8 Out-of-bounds Access Vulnerability
+
+### Description and CVSS Score
+
+An additional bug exists in Node.js, all versions of v4.x and v5.x, whereby an attacker may be able to trigger an out-of-bounds access and/or denial of service if user-supplied JavaScript can be executed by an application. The severity of this issue is considered medium for Node.js users (see CVSS scoring below), but only under circumstances where an attacker may cause user-supplied JavaScript to be executed within a Node.js application. Fixes will be shipped for the v4.x and v5.x release lines along with fixes for CVE-2015-8027.
+
+* Versions 0.10.x of Node.js are ***not affected***.
+* Versions 0.12.x of Node.js are ***not affected***.
+* Versions 4.x, including LTS Argon, of Node.js are ***vulnerable***.
+* Versions 5.x of Node.js are ***vulnerable***.
+
+Full details of this vulnerability are embargoed until new releases are available on **Wednesday the 2nd of December 2015, UTC** _(Tuesday the 1st of December US time)_.
+
+Common Vulnerability Scoring System (CVSS) v3 Base Score:
+
+| Metric                      | Score                      |
+|-----------------------------|----------------------------|
+| **Base Score:**             | **4.4 (Medium)**           |
+| **Base Vector:**            | [CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H)
+| **Attack Vector:**          | Network (AV:N)             |
+| **Attack Complexity:**      | Medium (AC:H)              |
+| **Privileges Required:**    | High (PR:H)                |
+| **User Interaction:**       | None (UI:N)                |
+| **Scope of Impact:**        | Unchanged (S:U)            |
+| **Confidentiality Impact:** | None (C:N)                 |
+| **Integrity Impact:**       | None (I:N)                 |
+| **Availability Impact:**    | High (A:H)                 |
+
+Complete CVSS v3 Vector: [CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:R/CR:L/IR:L/AR:M/MAV:N/MAC:H/MPR:N/MUI:N/MS:U/MC:N/MI:N/MA:H](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:R/CR:L/IR:L/AR:M/MAV:N/MAC:H/MPR:N/MUI:N/MS:U/MC:N/MI:N/MA:H). Refer to the [CVSS v3 Specification](https://www.first.org/cvss/specification-document) for details on the meanings and application of the vector components.
+
+CVE-2015-6764 is listed on the [MITRE CVE dictionary](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-6764) and [NIST NVD](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-6764).
+
+## Action and updates
+
+New releases of v0.12.x, v4.x and v5.x on **Wednesday the 2nd of December 2015, UTC** will be made available with appropriate fixes for CVE-2015-8027 and CVE-2015-6764 (for v4.x and v5.x only) along with disclosure of the details of the bug to allow for complete impact assessment by users.
+
+## Contact and future updates
+
+Please contact security@nodejs.org if you wish to report a vulnerability in Node.js.
+
+Please subscribe to the low-volume announcement-only **nodejs-sec** mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date with security vulnerabilities in Node.js and the projects maintained in the **nodejs** [GitHub organisation](http://github.com/nodejs/).
\ No newline at end of file
diff --git a/locale/uk/blog/vulnerability/december-2015-security-release-update.md b/locale/uk/blog/vulnerability/december-2015-security-release-update.md
new file mode 100755
index 0000000000000..f6cc20330d941
--- /dev/null
+++ b/locale/uk/blog/vulnerability/december-2015-security-release-update.md
@@ -0,0 +1,49 @@
+---
+date: 2015-12-01T01:13:57.544Z
+category: vulnerability
+title: December Security Release Schedule Update
+slug: december-2015-security-release-update
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+The OpenSSL project [announced](https://mta.openssl.org/pipermail/openssl-announce/2015-November/000045.html) today that they will be releasing security updates for versions 1.0.2, 1.0.1, 1.0.0 and 0.9.8 on the 3rd of December UTC. The updates will fix a number of security defects, the highest of which is classified as "moderate" severity according to their [severity scale](https://www.openssl.org/policies/secpolicy.html):
+
+> MODERATE Severity. This includes issues like crashes in client applications, flaws in protocols that are less commonly used (such as DTLS), and local flaws. These will in general be kept private until the next release, and that release will be scheduled so that it can roll up several such flaws at one time.
+
+Node.js versions v0.10.x and v0.12.x depend on OpenSSL v1.0.1 and versions v4.x (LTS Argon) and v5.x depend on OpenSSL v1.0.2. As the Node.js build process statically links OpenSSL into binaries, we will be required to release patch-level updates to all of our actively supported versions to include the upstream fixes. While we are unaware of the exact nature of the OpenSSL vulnerabilities being fixed, we must consider it likely that Node.js releases will be required in order to protect users.
+
+Since the OpenSSL release schedule is two days after our [announced updates](https://groups.google.com/forum/#!topic/nodejs-sec/Zf7Nxtg230E) for v0.12.x, v4.x and v5.x, we have decided to **postpone our security releases to coincide with OpenSSL release availability**. We will also be **including v0.10 in our set of releases**.
+
+Therefore, we are moving our planned security releases for Node.js from Wednesday the 2nd of December 2015, UTC to the **Friday, the 4th of December 2015, UTC** _(Thursday the 3rd of December US time)_. We understand that the timing of this during the work-week is unfortunate but we must take into account the possibility of introducing a vulnerability gap between disclosure of OpenSSL vulnerabilities and patched releases by Node.js and therefore must respond as quickly as practical. Please be aware that patching and testing of OpenSSL updates is a non-trivial exercise and there will be significant delay after the OpenSSL releases before we can be confident that Node.js builds are stable and suitable for release.
+
+An updated summary of the release inclusions is available below:
+
+---------------------------------------------
+
+## CVE-2015-8027 Denial of Service Vulnerability
+
+A bug exists in Node.js, all versions of v0.12.x through to v5.x inclusive, whereby an external attacker can cause a denial of service. The severity of this issue is high and users of the affected versions should plan to upgrade when a fix is made available.
+
+* Versions 0.10.x of Node.js are ***not affected***.
+* Versions 0.12.x of Node.js are ***vulnerable***.
+* Versions 4.x, including LTS Argon, of Node.js are ***vulnerable***.
+* Versions 5.x of Node.js are ***vulnerable***.
+
+## CVE-2015-6764 V8 Out-of-bounds Access Vulnerability
+
+An additional bug exists in Node.js, all versions of v4.x and v5.x, whereby an attacker may be able to trigger an out-of-bounds access and/or denial of service if user-supplied JavaScript can be executed by an application. The severity of this issue is considered medium for Node.js users, but only under circumstances where an attacker may cause user-supplied JavaScript to be executed within a Node.js application. Fixes will be shipped for the v4.x and v5.x release lines along with fixes for CVE-2015-8027.
+
+* Versions 0.10.x of Node.js are ***not affected***.
+* Versions 0.12.x of Node.js are ***not affected***.
+* Versions 4.x, including LTS Argon, of Node.js are ***vulnerable***.
+* Versions 5.x of Node.js are ***vulnerable***.
+
+## OpenSSL Moderate Severity Update
+
+The OpenSSL project has [announced](https://mta.openssl.org/pipermail/openssl-announce/2015-November/000045.html) a set of releases which contain fixes for multiple vulnerabilities, the highest severity being labelled "moderate". Consult the [OpenSSL security policy](https://www.openssl.org/policies/secpolicy.html) for details on this definition. New releases of all actively maintained Node.js release lines are required in order to protect users against potential vulnerabilities in their applications. We do not have details on the nature of any of the included vulnerabilities or their fixes, users should plan for upgrades as soon as practical.
+
+* Versions 0.10.x of Node.js ***may be vulnerable***.
+* Versions 0.12.x of Node.js ***may be vulnerable***.
+* Versions 4.x, including LTS Argon, of Node.js ***may be vulnerable***.
+* Versions 5.x of Node.js ***may be vulnerable***.
diff --git a/locale/uk/blog/vulnerability/december-2015-security-releases.md b/locale/uk/blog/vulnerability/december-2015-security-releases.md
new file mode 100755
index 0000000000000..7a8521f6adf1c
--- /dev/null
+++ b/locale/uk/blog/vulnerability/december-2015-security-releases.md
@@ -0,0 +1,60 @@
+---
+date: 2015-12-04T03:05:00.000Z
+category: vulnerability
+title: December Security Release Summary
+slug: december-2015-security-releases
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+Last week we [announced](https://groups.google.com/d/msg/nodejs-sec/Zf7Nxtg230E/eX4UCWf0BAAJ) the planned release of patch updates to the v0.12.x, v4.x and v5.x lines to fix two vulnerabilities. That was further amended by the [announcement](https://mta.openssl.org/pipermail/openssl-announce/2015-November/000045.html) of OpenSSL updates with fixes for vulnerabilities labelled _medium_ severity. The OpenSSL update impacts all active release lines, including v0.10.x.
+
+Today we have released Node.js [v0.10.41 (Maintenance)](/en/blog/release/v0.10.41/), [v0.12.9 (LTS)](/en/blog/release/v0.12.9/), [v4.2.3 "Argon" (LTS)](/en/blog/release/v4.2.3/) and [v5.1.1 (Stable)](/en/blog/release/v5.1.1/) with fixes for the announced vulnerabilities and updates to OpenSSL.
+
+For the purpose of understanding the impact that the fixed vulnerabilities have on your Node.js deployment and the urgency of the upgrades for your circumstances we are providing details below.
+
+### CVE-2015-8027 Denial of Service Vulnerability
+
+This critical denial of service (DoS) vulnerability impacts all versions of v0.12.x through to v5.x, inclusive. The vulnerability was discovered by Node.js core team member Fedor Indutny and relates to HTTP pipelining. Under certain conditions an HTTP socket may no longer have a parser associated with it but a pipelined request can trigger a pause or resume on the non-existent parser thereby causing an `uncaughtException` to be thrown. As these conditions can be created by an external attacker and cause a Node.js service to be shut down we consider this a critical vulnerability. It is recommended that users of impacted versions of Node.js exposing HTTP services upgrade to the appropriate patched versions as soon as practical.
+
+* Versions 0.10.x of Node.js are not affected.
+* Versions 0.12.x of Node.js are **vulnerable**, please upgrade to [v0.12.9 (LTS)](/en/blog/release/v0.12.9/).
+* Versions 4.x, including LTS Argon, of Node.js are **vulnerable**, please upgrade to [v4.2.3 "Argon" (LTS)](/en/blog/release/v4.2.3/).
+* Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.1.1 (Stable)](/en/blog/release/v5.1.1/).
+
+### CVE-2015-6764 V8 Out-of-bounds Access Vulnerability
+
+A bug was discovered in V8's implementation of `JSON.stringify()` that can result in out-of-bounds reads on arrays. The patch was included in this week's [update of Chrome Stable](http://googlechromereleases.blogspot.nl/2015/12/stable-channel-update.html). While this bug is high severity for browsers, it is considered lower risk for Node.js users as it requires the execution of third-party JavaScript within an application in order to be exploitable.
+
+Node.js users who expose services that process untrusted user-supplied JavaScript are at obvious risk. However, we recommend that all users of impacted versions of Node.js upgrade to the appropriate patched version in order to protect against malicious third-party JavaScript that may be executed within a Node.js process by other means.
+
+* Versions 0.10.x of Node.js are not affected.
+* Versions 0.12.x of Node.js are not affected.
+* Versions 4.x, including LTS Argon, of Node.js are **vulnerable**, please upgrade to [v4.2.3 "Argon" (LTS)](/en/blog/release/v4.2.3/).
+* Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.1.1 (Stable)](/en/blog/release/v5.1.1/).
+
+### CVE-2015-3193 OpenSSL BN_mod_exp may produce incorrect results on x86_64
+
+A bug exists in OpenSSL v1.0.2 in the [Montgomery squaring](https://en.wikipedia.org/wiki/Exponentiation_by_squaring#Montgomery.27s_ladder_technique) procedure on the x64 architecture that expose potential attack vectors. Attacks against RSA and DSA are considered possible but with a very high degree of difficulty. Attacks against DHE key exchange is considered feasible but difficult. EC algorithms are not vulnerable. Node.js TLS servers using DHE key exchange are considered at highest risk although it is believed that Node.js' existing use of `SSL_OP_SINGLE_DH_USE` may make [DHE attacks impractical](https://blog.fuzzing-project.org/31-Fuzzing-Math-miscalculations-in-OpenSSLs-BN_mod_exp-CVE-2015-3193.html). Details are available at <http://openssl.org/news/secadv/20151203.txt>.
+
+OpenSSL v1.0.2 is used in Node.js v4.x LTS and v5.x. It is strongly recommended that Node.js users exposing TLS servers upgrade to patched versions as soon as practical.
+
+* Versions 0.10.x of Node.js are not affected.
+* Versions 0.12.x of Node.js are not affected.
+* Versions 4.x, including LTS Argon, of Node.js are **vulnerable**, please upgrade to [v4.2.3 "Argon" (LTS)](/en/blog/release/v4.2.3/).
+* Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.1.1 (Stable)](/en/blog/release/v5.1.1/).
+
+### CVE-2015-3194 OpenSSL Certificate verify crash with missing PSS parameter
+
+A bug exists in OpenSSL v1.0.1 and v1.0.2 that may cause a crash during certificate verification procedures when supplied with a malformed ASN.1 signature using the RSA PSS algorithm. This may be used as a the basis of a denial of service (DoS) attack against Node.js TLS servers using client authentication. Node.js TLS clients are also impacted if supplied with malformed certificates for verification. Details are available at <http://openssl.org/news/secadv/20151203.txt>.
+
+OpenSSL v1.0.0 is used in Node.js v0.10.x and v0.12.x. OpenSSL v1.0.2 is used in Node.js v4.x LTS and v5.x. It is strongly recommended that Node.js users employing either TLS client or server code upgrade as soon as practical.
+
+* Versions 0.10.x of Node.js are **vulnerable**, please upgrade to [v0.10.41 (Maintenance)](/en/blog/release/v0.10.41/).
+* Versions 0.12.x of Node.js are **vulnerable**, please upgrade to [v0.12.9 (LTS)](/en/blog/release/v0.12.9/).
+* Versions 4.x, including LTS Argon, of Node.js are **vulnerable**, please upgrade to [v4.2.3 "Argon" (LTS)](/en/blog/release/v4.2.3/).
+* Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.1.1 (Stable)](/en/blog/release/v5.1.1/).
+
+**Note:** Node.js users are not considered vulnerable to the two additional announced OpenSSL vulnerabilities: CVE-2015-3195 "X509_ATTRIBUTE memory leak" and CVE-2015-3196 "Race condition handling PSK identify hint". However, fixes for these bugs are included with the new versions of OpenSSL bundled with the newly patched versions of Node.js.
+
+
diff --git a/locale/uk/blog/vulnerability/february-2016-security-releases.md b/locale/uk/blog/vulnerability/february-2016-security-releases.md
new file mode 100755
index 0000000000000..96c5a0b9d82f4
--- /dev/null
+++ b/locale/uk/blog/vulnerability/february-2016-security-releases.md
@@ -0,0 +1,74 @@
+---
+date: 2016-02-09T17:40:00.212Z
+category: vulnerability
+title: February 2016 Security Release Summary
+slug: february-2016-security-releases
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+Two weeks ago we [announced](https://groups.google.com/d/msg/nodejs-sec/G8IA0G4uA88/So3Cw84YDwAJ) the planned release of updates to all active release lines, v0.10, v0.12, v4 and v5, to fix HTTP related vulnerabilities and to upgrade the bundled versions of OpenSSL.
+
+Upon release of the OpenSSL updates we posted an [impact assessment](https://groups.google.com/d/msg/nodejs-sec/G8IA0G4uA88/-UB4DpG1DwAJ) for Node.js users. We noted that the updates contained only one minor change that impacted Node.js users.
+
+Today we have released Node.js [v0.10.42 (Maintenance)](/en/blog/release/v0.10.42/), [v0.12.10 (LTS)](/en/blog/release/v0.12.10/), [v4.3.0 "Argon" (LTS)](/en/blog/release/v4.3.0/) and [v5.6.0 (Stable)](/en/blog/release/v5.6.0/) with fixes for the announced vulnerabilities and updates to OpenSSL.
+
+**Please note that our LTS "Argon" release line has moved from v4.2.x to v4.3.x due to the security fixes enclosed. There will be no further updates to v4.2.x.** Users are advised to upgrade to v4.3.0 as soon as possible.
+
+For the purpose of understanding the impact that the fixed vulnerabilities have on your Node.js deployment and the urgency of the upgrades for your circumstances we are providing details below.
+
+### CVE-2016-2086 Request Smuggling Vulnerability
+
+Régis Leroy reported defects in Node.js that can make [request smuggling](https://tools.ietf.org/html/rfc7230#section-9.5) attacks possible under certain circumstances. To fix these defects, HTTP header parsing in Node.js, for both requests and responses, is moving closer to the formal HTTP specification in its handling of `Content-Length`.
+
+While the impact of this vulnerability is application and network dependent, it is likely to be difficult to assess whether a Node.js deployment is vulnerable to attack. We therefore recommend that all users upgrade.
+
+* Versions 0.10.x of Node.js are **vulnerable**, please upgrade to [v0.10.42 (Maintenance)](/en/blog/release/v0.10.42/).
+* Versions 0.12.x of Node.js are **vulnerable**, please upgrade to [v0.12.10 (LTS)](/en/blog/release/v0.12.10/).
+* Versions 4.x, including LTS Argon, of Node.js are **vulnerable**, please upgrade to [v4.3.0 "Argon" (LTS)](/en/blog/release/v4.3.0/).
+* Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.6.0 (Stable)](/en/blog/release/v5.6.0/).
+
+### CVE-2016-2216 Response Splitting Vulnerability
+
+Сковорода Никита Андреевич (Nikita Skovoroda / [@ChALkeR](https://github.com/chalker)) and Amit Klein (of [Safebreach](http://safebreach.com/)) separately reported ways in which HTTP header parsing in Node.js can be used to perform [response splitting](https://tools.ietf.org/html/rfc7230#section-9.4) attacks (new-line / CRLF injection). While Node.js has been protecting against response splitting attacks by checking for CRLF characters, it is possible to compose response headers using Unicode characters that decompose to these characters, bypassing the checks previously in place.
+
+To fix this defect, HTTP header parsing in Node.js, for both requests and responses, is moving closer to the formal HTTP specification. HTTP headers containing characters outside of the [valid set for tokens](https://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2) will be rejected. This check is performed for both requests and responses, for Node.js HTTP servers and clients.
+
+It is possible that there exist Node.js applications that rely on the lax behaviour of HTTP header parsing for Node.js clients and/or servers. This change is therefore a breaking change that would normally be reserved for a semver-major version increment. However, as per our [LTS](https://github.com/nodejs/LTS/) policy, we are introducing this change as a semver-minor in Node.js v4 (hence the move from v4.2.x to v4.3.x) and v5 and semver-patch in v0.10 and v0.12.
+
+Node.js LTS releases, v0.10.42, v0.12.10 and v4.3.0 (but not v5.6.0) also include a new command-line argument that can be used to turn off this new strict header parsing. By supplying `--security-revert=CVE-2016-2216` when starting Node.js, the previous lenient HTTP header character checks will be used instead. Use of this option is not recommended and should only be used as a temporary migration tool where the implications of reverting the new behavior are fully understood.
+
+We recommend that all users upgrade to receive this fix.
+
+* Versions 0.10.x of Node.js are **vulnerable**, please upgrade to [v0.10.42 (Maintenance)](/en/blog/release/v0.10.42/).
+* Versions 0.12.x of Node.js are **vulnerable**, please upgrade to [v0.12.10 (LTS)](/en/blog/release/v0.12.10/).
+* Versions 4.x, including LTS Argon, of Node.js are **vulnerable**, please upgrade to [v4.3.0 "Argon" (LTS)](/en/blog/release/v4.3.0/).
+* Versions 5.x of Node.js are **vulnerable**, please upgrade to [v5.6.0 (Stable)](/en/blog/release/v5.6.0/).
+
+### OpenSSL upgrade summary
+
+Node.js v0.10.42 and v0.12.10 upgrades the bundled version of OpenSSL from 1.0.1q to 1.0.1r. Full details can be found in the [OpenSSL 1.0.1 changelog](https://www.openssl.org/news/cl101.txt).
+
+Node.js v4.3.0 and v5.6.0 upgrades the bundled version of OpenSSL from 1.0.2e to 1.0.2f. Full details can be found in the [OpenSSL 1.0.2 changelog](https://www.openssl.org/news/cl102.txt).
+
+As per our [impact assessment](https://groups.google.com/d/msg/nodejs-sec/G8IA0G4uA88/-UB4DpG1DwAJ), the following applies to these releases:
+
+**DH small subgroups (CVE-2016-0701)**
+
+Node.js v0.10 and v0.12 are not affected by this defect.
+
+Node.js v4 and v5 use the `SSL_OP_SINGLE_DH_USE` option already and are therefore not affected by this defect.
+
+**SSLv2 doesn't block disabled ciphers (CVE-2015-3197)**
+
+Node.js v0.10 and v0.12 disable SSLv2 by default and are not affected _unless_ the `--enable-ssl2` command line argument is being used (not recommended).
+
+Node.js v4 and v5 do not support SSLv2.
+
+**An update on DHE man-in-the-middle protection (Logjam)**
+
+Previous releases of OpenSSL (since Node.js v0.10.39, v0.12.5, v4.0.0 and v5.0.0) mitigated against [Logjam](https://en.wikipedia.org/wiki/Logjam_%28computer_security%29) for TLS _clients_ by rejecting connections from servers where Diffie-Hellman parameters were shorter than 768-bits.
+
+The new OpenSSL release, for all Node.js lines, increases this to 1024-bits. The change only impacts TLS clients connecting to servers with weak DH parameter lengths.
+
+Please tune in to **nodejs-sec** (https://groups.google.com/forum/#!forum/nodejs-sec) to receive security announcements. An [Atom feed](https://nodejs.org/en/feed/vulnerability.xml) is also available for security-only posts to the [nodejs.org blog](http://nodejs.org/en/blog/).
diff --git a/locale/uk/blog/vulnerability/http-server-pipeline-flood-dos.md b/locale/uk/blog/vulnerability/http-server-pipeline-flood-dos.md
new file mode 100755
index 0000000000000..605dc855d41ce
--- /dev/null
+++ b/locale/uk/blog/vulnerability/http-server-pipeline-flood-dos.md
@@ -0,0 +1,39 @@
+---
+title: DoS Vulnerability (fixed in Node v0.8.26 and v0.10.21)
+date: 2013-10-22T17:42:10.000Z
+slug: cve-2013-4450-http-server-pipeline-flood-dos
+category: vulnerability
+layout: blog-post.hbs
+---
+Node.js is vulnerable to a denial of service attack when a client
+sends many pipelined HTTP requests on a single connection, and the
+client does not read the responses from the connection.
+
+We recommend that anyone using Node.js v0.8 or v0.10 to run HTTP
+servers in production please update as soon as possible.
+
+* v0.10.21 <http://blog.nodejs.org/2013/10/18/node-v0-10-21-stable/>
+* v0.8.26 <http://blog.nodejs.org/2013/10/18/node-v0-8-26-maintenance/>
+
+This is fixed in Node.js by pausing both the socket and the HTTP
+parser whenever the downstream writable side of the socket is awaiting
+a drain event.  In the attack scenario, the socket will eventually
+time out, and be destroyed by the server.  If the "attacker" is not
+malicious, but merely sends a lot of requests and reacts to them
+slowly, then the throughput on that connection will be reduced to what
+the client can handle.
+
+There is no change to program semantics, and except in the
+pathological cases described, no changes to behavior.
+
+If upgrading is not possible, then putting an HTTP proxy in front of
+the Node.js server can mitigate the vulnerability, but only if the
+proxy parses HTTP and is not itself vulnerable to a pipeline flood
+DoS.
+
+For example, nginx will prevent the attack (since it closes
+connections after 100 pipelined requests by default), but HAProxy in
+raw TCP mode will not (since it proxies the TCP connection without
+regard for HTTP semantics).
+
+This addresses CVE-2013-4450.
diff --git a/locale/uk/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md b/locale/uk/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md
new file mode 100755
index 0000000000000..b0cf814f0a8e8
--- /dev/null
+++ b/locale/uk/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md
@@ -0,0 +1,47 @@
+---
+title: "HTTP Server Security Vulnerability: Please upgrade to 0.6.17"
+author: Isaac Schlueter
+date: 2012-05-07T17:02:01.000Z
+status: publish
+category: vulnerability
+slug: http-server-security-vulnerability-please-upgrade-to-0-6-17
+layout: blog-post.hbs
+---
+<h2>tl;dr</h2>
+
+<ul><li><p>A carefully crafted attack request can cause the contents of the HTTP parser's buffer to be appended to the attacking request's header, making it appear to come from the attacker.  Since it is generally safe to echo back contents of a request, this can allow an attacker to get an otherwise correctly designed server to divulge information about other requests.  It is theoretically possible that it could enable header-spoofing attacks, though such an attack has not been demonstrated.</li>
+<li>Versions affected: All versions of the 0.5/0.6 branch prior to 0.6.17, and all versions of the 0.7 branch prior to 0.7.8.  Versions in the 0.4 branch are not affected.</li>
+<li>Fix: Upgrade to <a href="http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/">v0.6.17</a>, or apply the fix in <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a> to your system.</li></ul>
+
+<h2>Details</h2>
+
+<p>A few weeks ago, Matthew Daley found a security vulnerability in Node&#39;s HTTP implementation, and thankfully did the responsible thing and reported it to us via email.  He explained it quite well, so I'll quote him here:</p>
+<blockquote>
+<p>There is a vulnerability in node&#39;s `http_parser` binding which allows information disclosure to a remote attacker:
+
+</p>
+<p>In node::StringPtr::Update, an attempt is made at an optimization on certain inputs (`node_http_parser.cc`, line 151). The intent is that if the current string pointer plus the current string size is equal to the incoming string pointer, the current string size is just increased to match, as the incoming string lies just beyond the current string pointer. However, the check to see whether or not this can be done is incorrect; &quot;size&quot; is used whereas &quot;size_&quot; should be used. Therefore, an attacker can call Update with a string of certain length and cause the current string to have other data appended to it. In the case of HTTP being parsed out of incoming socket data, this can be incoming data from other sockets.
+
+</p>
+<p>Normally node::StringPtr::Save, which is called after each execution of `http_parser`, would stop this from being exploitable as it converts strings to non-optimizable heap-based strings. However, this is not done to 0-length strings. An attacker can therefore exploit the mistake by making Update set a 0-length string, and then Update past its boundary, so long as it is done in one `http_parser` execution. This can be done with an HTTP header with empty value, followed by a continuation with a value of certain length.
+
+</p>
+<p>The <a href="https://gist.github.com/2628868">attached files</a> demonstrate the issue:  </p>
+<pre><code>$ ./node ~/stringptr-update-poc-server.js &amp;
+[1] 11801
+$ ~/stringptr-update-poc-client.py
+HTTP/1.1 200 OK
+Content-Type: text/plain
+Date: Wed, 18 Apr 2012 00:05:11 GMT
+Connection: close
+Transfer-Encoding: chunked
+
+64
+X header:
+ This is private data, perhaps an HTTP request with a Cookie in it.
+0</code></pre>
+</blockquote>
+<p>The fix landed on <a href="https://github.com/joyent/node/commit/7b3fb22">7b3fb22</a> and <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a>, for master and v0.6, respectively.  The innocuous commit message does not give away the security implications, precisely because we wanted to get a fix out before making a big deal about it.  </p>
+<p>The first releases with the fix are v0.7.8 and 0.6.17.  So now is a good time to make a big deal about it.  </p>
+<p>If you are using node version 0.6 in production, please upgrade to at least <a href="http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/">v0.6.17</a>, or at least apply the fix in <a href="https://github.com/joyent/node/commit/c9a231d">c9a231d</a> to your system. (Version 0.6.17 also fixes some other important bugs, and is without doubt the most stable release of Node 0.6 to date, so it&#39;s a good idea to upgrade anyway.)  </p>
+<p>I&#39;m extremely grateful that Matthew took the time to report the problem to us with such an elegant explanation, and in such a way that we had a reasonable amount of time to fix the issue before making it public. </p>
diff --git a/locale/uk/blog/vulnerability/index.md b/locale/uk/blog/vulnerability/index.md
new file mode 100755
index 0000000000000..f08bfb1319034
--- /dev/null
+++ b/locale/uk/blog/vulnerability/index.md
@@ -0,0 +1,6 @@
+---
+title: Vulnerabilities
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/vulnerability/june-2016-security-releases.md b/locale/uk/blog/vulnerability/june-2016-security-releases.md
new file mode 100755
index 0000000000000..9f380675495ee
--- /dev/null
+++ b/locale/uk/blog/vulnerability/june-2016-security-releases.md
@@ -0,0 +1,126 @@
+---
+date: 2016-06-13T12:57:51.617Z
+category: vulnerability
+title: Security updates for all active release lines, June 2016
+slug: june-2016-security-releases
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+## _(Update 23-June-2016)_ Releases available
+
+After a thorough assessment of the fixes we were planning on including, we have decided to scale back this security update to only include a subset. We are deferring some fixes while we improve the required API changes in order to decrease the disruption that it may cause to users. The vulnerabilities that the deferred fixes address are low severity.
+
+Note that there is **no Node.js v6 release** in this set of updates as it is not impacted by the vulnerabilities being patched.
+
+The fixes we are including in this update are:
+
+### [CVE-2016-1669](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1669) Buffer overflow in V8
+
+Under certain conditions, V8 may improperly expand memory allocations in the `Zone::New` function. This could potentially be used to cause a Denial of Service via buffer overflow or as a trigger for a remote code execution.
+
+Although this bug is marked as [high severity](http://googlechromereleases.blogspot.com.au/2016/05/stable-channel-update.html) in the corresponding Chromium release (50.0.2661.102), our assessment is that this is low severity for Node.js users due to the level of difficulty in making use of this vulnerability. However, users are encouraged to upgrade their Node.js installation to ensure they are properly protected.
+
+* Node.js v6 (Current) ***is not affected*** as of v6.2.0 due to an update to V8 5.0.71.47, versions prior to v6.2.0 **are affected**
+* Node.js v5 ***is affected***
+* Node.js v4 (LTS "Argon") ***is affected***
+* Node.js v0.12 (Maintenance) ***is affected***
+* Node.js v0.10 (Maintenance) ***is affected***
+
+### [CVE-2014-9748](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9748) Unsafe use of read/write locks on Windows 2003 and XP in libuv
+
+Prior to libuv version 1.7.4, a flaw in the read/write locks implementation for Windows XP and Windows 2003 could lead to unlocking a CRITICAL_SECTION on the wrong thread, resulting in undefined and potentially unsafe behavior. This problem was identified by Zhou Ran. Node.js v4 and later are not affected as the usage of read/write was replaced with simple mutexes. Further details can be found on the [libuv repository](https://github.com/libuv/libuv/issues/515).
+
+* Node.js v6 (Current) ***is not affected***
+* Node.js v5 ***is not affected***
+* Node.js v4 (LTS "Argon") ***is not affected***
+* Node.js v0.12 (Maintenance) ***is affected***
+* Node.js v0.10 (Maintenance) ***is affected***
+
+### Downloads
+
+* [Node.js v5.12.0](https://nodejs.org/en/blog/release/v5.12.0/)
+* [Node.js v4.4.6 (LTS "Argon")](https://nodejs.org/en/blog/release/v4.4.6/)
+* [Node.js v0.12.15 (Maintenance)](https://nodejs.org/en/blog/release/v0.12.15/)
+* [Node.js v0.10.46 (Maintenance)](https://nodejs.org/en/blog/release/v0.10.46/)
+
+Please note that this may be the final release of the v5.x line as support ends on the 30th of June.
+
+--------------------------------------
+
+## _(Update 16-June-2016)_ Adjusted release schedule
+
+Unfortunately we have to announce that we are delaying our security releases by a week. We have concluded that pushing forward with the releases this week would unnecessarily compromise the quality of the fixes we intended to include. Instead, we will be taking the extra time to be sure that we are delivering the stability and quality that Node.js users expect.
+
+We now intend to make releases available on or soon after **Thursday, the 23rd of June, 2016, UTC**.
+
+***Original post is included below***
+
+--------------------------------------
+
+The Node.js project has scheduled updates for all of its active release lines to patch two security flaws and one security-related usability flaw. We do not consider any of our updates to be critical, however, it is recommended that all production instances of Node.js be upgraded when the releases are made available.
+
+We intend to make releases available on or soon after **Thursday, the 16th of June, 2016, UTC**.
+
+We consider some of the patches in these releases to be API _breaking_ changes which would normally warrant an increase in the major-version number of Node.js. However, in accordance with our security procedures we will be delivering these changes in minor-version increases _(the y in x.y.z)_ where appropriate, and patch-version increases in v0.10 an v0.12 releases.
+
+Therefore, we expect to be releasing:
+
+* Node.js v6.3.0 (Current)
+* Node.js v5.12.0
+* Node.js v4.5.0 (LTS "Argon")
+* Node.js v0.12.15 (Maintenance)
+* Node.js v0.10.46 (Maintenance)
+
+While we anticipate minimal impact from the breaking changes, please be sure to review the details once they are released and make an assessment regarding the impact on your applications.
+
+Additional notes:
+* It is our intention to stop releasing critical updates for the v5 release line at the end of this month, you should migrate to to v6 or v4 LTS if you have not already done so.
+* In accordance with our security release procedures, we will be limiting changes included in the LTS and Maintenance lines (v4, v0.12 and v0.10) _for these updates_ to only security-related and critical fixes to provide maximum stability for users.
+
+## V8 security defect
+
+The V8 team has identified and patched a potential security vulnerability. We will be backporting the fix to all active release lines of Node.js. Our current assessment is that this vulnerability should be considered low-severity for Node.js users with an exploit being very difficult to develop and execute.
+
+**All versions of Node.js are affected.**
+
+## HTTP processing security defect (CVE-2016-5325)
+
+We will be including fixes relating to Node.js HTTP processing. We categorise these as low-severity and are not aware of any existing exploits leveraging the defects. Full details are embargoed until new releases are available.
+
+Common Vulnerability Scoring System (CVSS) v3 Base Score:
+
+| Metric                      | Score                      |
+|-----------------------------|----------------------------|
+| **Base Score:**             | 4.8 (Medium)               |
+| **Base Vector:**            | [CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
+| **Attack Vector:**          | Network (AV:N)             |
+| **Attack Complexity:**      | High (AC:H)                |
+| **Privileges Required:**    | None (PR:N)                |
+| **User Interaction:**       | None (UI:N)                |
+| **Scope of Impact:**        | Unchanged (S:U)            |
+| **Confidentiality Impact:** | Low (C:L)                  |
+| **Integrity Impact:**       | Low (I:L)                  |
+| **Availability Impact:**    | None (A:N)                 |
+
+Refer to the [CVSS v3 Specification](https://www.first.org/cvss/specification-document) for details on the meanings and application of the vector components.
+
+**All versions of Node.js are affected.**
+
+This defect will identified as [CVE-2016-5325](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5325)
+
+## Security-related HTTP client usability flaw
+
+We intend to also include a patch for HTTP client in Node.js. While we do not consider this to be strictly a security concern for Node.js core, it poses a usability concern that may easily enable users to write code that exposes vulnerabilities in their applications.
+
+**All versions of Node.js are affected.**
+
+## Contact and future updates
+
+Please monitor the nodejs-sec Google Group for updates: https://groups.google.com/forum/#!forum/nodejs-sec or the Node.js website for release announcements: https://nodejs.org/en/blog/
+
+The current Node.js security policy can be found at <https://nodejs.org/en/security/>.
+
+Please contact security@nodejs.org if you wish to report a vulnerability in Node.js.
+
+Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organisation](http://github.com/nodejs/).
diff --git a/locale/uk/blog/vulnerability/npm-tokens-leak-march-2016.md b/locale/uk/blog/vulnerability/npm-tokens-leak-march-2016.md
new file mode 100755
index 0000000000000..d32c052a46316
--- /dev/null
+++ b/locale/uk/blog/vulnerability/npm-tokens-leak-march-2016.md
@@ -0,0 +1,31 @@
+---
+date: 2016-03-31T10:41:46.216Z
+category: vulnerability
+title: npm security updates v2.15.1 and v3.8.3
+slug: npm-tokens-leak-march-2016
+layout: blog-post.hbs
+author: Forrest Norvell
+---
+
+_This announcement is also covered on the npm blog: <http://blog.npmjs.org/post/142036323955/fixing-a-bearer-token-vulnerability>._
+
+The primary npm registry has, since late 2014, used HTTP bearer tokens to authenticate requests from the npm command-line interface. Due to a design flaw in the CLI, these bearer tokens were sent with every request made by the CLI for logged-in users, regardless of the destination of the request. They should instead only be included for requests made against the registry or registries used for the current install.
+
+This flaw allows an attacker to set up an HTTP server that could collect authentication information they could use to impersonate the users whose tokens they collected. This impersonation would allow them to do anything the compromised users could do, including publishing new versions of packages.
+
+This flaw has been fixed in [npm@2.15.1](https://github.com/npm/npm/commit/fea8cc92cee02c720b58f95f14d315507ccad401) (npm LTS) and [npm@3.8.3](https://github.com/npm/npm/commit/f67ecad59e99a03e5aad8e93cd1a086ae087cb29). The npm CLI team believes that the fix won't break any existing registry setups, but due to the large number of registry software suites in the wild, it's possible that this change will be breaking in some cases. If so, please [file an issue](https://github.com/npm/npm/issues/new) describing the software you're using and how it broke, and the team will work with you to mitigate the breakage.
+
+If you believe that your bearer token may have been leaked, it should be sufficient to [invalidate your current npm bearer tokens](https://www.npmjs.com/settings/tokens) and to rerun npm login to generate new tokens. Keep in mind that this may cause continuous integration builds in services like Travis to break, in which case you'll need to update the tokens in your CI server's configuration.
+
+Thanks to Mitar, Will White & the team at Mapbox, Max Motovilov, and James Taylor for reporting this vulnerability to npm.
+
+As Node.js ships with npm, releases for the active lines will be made available shortly for your convenience. Please watch the [Node.js news feed](https://nodejs.org/en/blog/) for the following releases:
+
+* **v0.10 (Maintenance)**: [Node.js v0.10.44](http://nodejs.org/en/blog/release/v0.10.44/) includes npm LTS v2.15.1. This is a major upgrade of npm from v1 which has previously been deprecated. No fix is being made available for npm v1, please upgrade to npm v2 as soon as possible.
+* **v0.12 (LTS)**: [Node.js v0.12.13](http://nodejs.org/en/blog/release/v0.12.13/) includes npm LTS v2.15.1.
+* **v4 (LTS "Argon")**: [Node.js v4.4.2](http://nodejs.org/en/blog/release/v4.4.2/) includes npm LTS v2.15.1.
+* **v5 (Stable)**: [Node.js v5.10.0](http://nodejs.org/en/blog/release/v5.10.0/) includes npm v3.8.3.
+
+**Update:** Unfortunately the version of npm that was bundled with Node.js version v0.10.44, v0.12.13 and v4.4.2 did not include the correct version string, `npm -v` reports `2.15.0`, however the code is v2.15.1.
+
+**Note that you can upgrade your installed version of npm manually** without requiring a Node.js update by using the command `npm install npm@2 -g` for npm LTS v2.15.2 or `npm install npm@3 -g` for npm v3.8.5.
diff --git a/locale/uk/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md b/locale/uk/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md
new file mode 100755
index 0000000000000..b6e8ca2c41c2e
--- /dev/null
+++ b/locale/uk/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016.md
@@ -0,0 +1,112 @@
+---
+date: 2016-01-27T11:34:41.011Z
+category: vulnerability
+title: OpenSSL upgrade low-severity Node.js security fixes
+slug: openssl-and-low-severity-fixes-jan-2016
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+***(Updates to this post, including a schedule change are included below)***
+
+### Summary
+
+The Node.js project will be releasing new versions across all of its active release lines early next week (possibly sooner, pending full impact assessment) to incorporate upstream patches from OpenSSL and some additional low-severity fixes relating to HTTP handling. Please read on for full details.
+
+### OpenSSL
+
+The OpenSSL project [announced](https://mta.openssl.org/pipermail/openssl-announce/2016-January/000058.html) this week that they will be releasing versions 1.0.2f and 1.0.1r on the 28th of January, UTC. The releases will fix two security defects that are labelled as "high" severity under their [security policy](https://www.openssl.org/policies/secpolicy.html), meaning they are:
+
+> ... issues that are of a lower risk than critical, perhaps due to affecting less common configurations, or which are less likely to be exploitable.
+
+Node.js v0.10 and v0.12 both use OpenSSL v1.0.1 and Node.js v4 and v5 both use OpenSSL v1.0.2 and are normally statically compiled. Therefore, all active release lines are impacted by this update.
+
+At this stage, due to embargo, the exact nature of these defects is uncertain as well as the impact they will have on Node.js users.
+
+### Low-severity Node.js security fixes
+
+In addition, we have some fixes to release relating to Node.js HTTP processing. We categorise these as low-severity and are not aware of any existing exploits leveraging the defects. Full details are embargoed until new releases are available.
+
+Common Vulnerability Scoring System (CVSS) v3 Base Score:
+
+| Metric                      | Score                      |
+|-----------------------------|----------------------------|
+| **Base Score:**             | **4.8 (Medium)**           |
+| **Base Vector:**            | [CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
+| **Attack Vector:**          | Network (AV:N)             |
+| **Attack Complexity:**      | High (AC:H)                |
+| **Privileges Required:**    | None (PR:N)                |
+| **User Interaction:**       | None (UI:N)                |
+| **Scope of Impact:**        | Unchanged (S:U)            |
+| **Confidentiality Impact:** | Low (C:L)                  |
+| **Integrity Impact:**       | Low (I:L)                  |
+| **Availability Impact:**    | None (A:N)                 |
+
+Refer to the [CVSS v3 Specification](https://www.first.org/cvss/specification-document) for details on the meanings and application of the vector components.
+
+### Impact
+
+Both the OpenSSL updates and the Node.js fixes affect all actively maintained release lines of Node.js.
+
+ * Versions 0.10.x of Node.js **are affected**.
+ * Versions 0.12.x of Node.js **are affected**.
+ * Versions 4.x, including LTS Argon, of Node.js **are affected**.
+ * Versions 5.x of Node.js **are affected**.
+
+### Release timing
+
+As the OpenSSL release is planned for late in the week, we are currently planning on deferring Node.js releases until early next week due to the complexity of the upgrade process and a preference for not releasing security fixes at the end of the work-week or on the weekend.
+
+Releases will be available at, or shortly after, **Monday the 1st of February, 11pm UTC** _(Monday the 1st of February, 3pm Pacific Time)_ along with disclosure of the details defects to allow for complete impact assessment by users.
+
+However, when details of the OpenSSL defects are released on the 28th, our crypto team will be making a more detailed assessment on the likely severity for Node.js users. In the event that the team determines that the fixes are critical in nature for Node.js users **we may choose to expedite releases for Friday or Saturday** in order to ensure that users have the ability to protect their deployments against a disclosed vulnerability.
+
+Please monitor the **nodejs-sec** Google Group for updates, including a decision within 24 hours after the OpenSSL release regarding release timing, and full details of the defects upon eventual release: https://groups.google.com/forum/#!forum/nodejs-sec
+
+### Contact and future updates
+
+The current Node.js security policy can be found at <https://nodejs.org/en/security/>.
+
+Please contact [security@nodejs.org](mailto:security@nodejs.org) if you wish to report a vulnerability in Node.js.
+
+Subscribe to the low-volume announcement-only **nodejs-sec** mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organisation](https://github.com/nodejs).
+
+## _(Update 29-Jan-2016)_ OpenSSL Impact Assessment
+
+OpenSSL versions 1.0.1r and 1.0.21 have been released, the announcement can be found here: https://mta.openssl.org/pipermail/openssl-announce/2016-January/000061.html
+
+Our team has made an assessment of the impact of the disclosed defects and concluded that there is no urgency in releasing patched versions of Node.js in response to this release. Therefore, we will be proceeding as planned and attempt to release new versions of each of our active release lines on or after
+**Monday the 1st of February, 11pm UTC** _(Monday the 1st of February, 3pm Pacific Time)_. Please note that this is simply an approximation of release timing. Please tune in to **nodejs-sec** (https://groups.google.com/forum/#!forum/nodejs-sec) where we will announce the availability of releases.
+
+### Details
+
+**DH small subgroups (CVE-2016-0701)**
+
+Node.js v0.10 and v0.12 are not affected by this defect.
+
+Node.js v4 and v5 use the `SSL_OP_SINGLE_DH_USE` option already and are therefore not affected by this defect.
+
+**SSLv2 doesn't block disabled ciphers (CVE-2015-3197)**
+
+Node.js v0.10 and v0.12 disable SSLv2 by default and are not affected _unless_ the `--enable-ssl2` command line argument is being used (not recommended).
+
+Node.js v4 and v5 do not support SSLv2.
+
+**An update on DHE man-in-the-middle protection (Logjam)**
+
+Previous releases of OpenSSL (since Node.js v0.10.39, v0.12.5, v4.0.0 and v5.0.0) mitigated against [Logjam](https://en.wikipedia.org/wiki/Logjam_%28computer_security%29) for TLS _clients_ by rejecting connections from servers where Diffie-Hellman parameters were shorter than 768-bits.
+
+The new OpenSSL release, for all Node.js lines, increases this to 1024-bits. The change only impacts TLS clients connecting to servers with weak DH parameter lengths.
+
+<a name="_-update-29-jan-2016-_-openssl-impact-assessment"></a>
+
+## _(Update 30-Jan-2016)_ Release postponement
+
+The announced security releases will not go ahead for the 1st of February as previously announced. Instead, our new target for release will be on or shortly after **Tuesday, the 9th of February, 11pm UTC** _(Tuesday, the 9th of February, 3pm Pacific Time)_.
+
+The planned fixes include a backward-incompatible change that, under normal circumstances, would be deferred until the next major-version of Node.js, v6. However, because the fix addresses a security concern that exists across all release lines (including our LTS lines: v4, v0.12 and v0.10) we require the additional time to further review the changes and consider how best to achieve minimal impact to users.
+
+We apologise for any inconvenience this schedule change may cause.
+
+Please tune in to **nodejs-sec** (https://groups.google.com/forum/#!forum/nodejs-sec) to be notified of any further updates.
+
diff --git a/locale/uk/blog/vulnerability/openssl-and-utf8.md b/locale/uk/blog/vulnerability/openssl-and-utf8.md
new file mode 100755
index 0000000000000..6612783a88f34
--- /dev/null
+++ b/locale/uk/blog/vulnerability/openssl-and-utf8.md
@@ -0,0 +1,79 @@
+---
+title: OpenSSL and Breaking UTF-8 Change (fixed in Node v0.8.27 and v0.10.29)
+date: 2014-06-16T15:46:10.000Z
+slug: openssl-and-breaking-utf-8-change
+category: vulnerability
+layout: blog-post.hbs
+---
+Today we are releasing new versions of Node:
+
+ * [node-v0.8.27](https://nodejs.org/dist/v0.8.27)
+ * [node-v0.10.29](https://nodejs.org/dist/v0.10.29)
+
+First and foremost these releases address the current OpenSSL vulnerability
+[CVE-2014-0224](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224),
+for both 0.8 and 0.10 we've upgraded the version of the bundled OpenSSL to
+their fixed versions v1.0.0m and v1.0.1h respectively.
+
+Additionally these releases address the fact that V8 UTF-8 encoding would allow
+unmatched surrogate pairs. That is to say, previously you could construct a
+valid JavaScript string (which are stored internally as UCS-2), pass it to a
+`Buffer` as UTF-8, send and consume that string in another process and it would
+fail to interpret because the UTF-8 string was invalid.
+
+Note, the results encoded by V8 in this case are exactly what was passed into
+the encoding routine. There is no overflow, underflow, or the inclusion of
+other arbitrary memory, merely an unmatched UTF-8 surrogate resulting in
+invalid UTF-8.
+
+As of these releases, if you try and pass a string with an unmatched surrogate
+pair, Node will replace that character with the unknown unicode character
+(U+FFFD). To preserve the old behavior set the environment variable
+`NODE_INVALID_UTF8` to anything (even nothing). If the environment variable is
+present at all it will revert to the old behavior.
+
+This breaks backward compatibility for the specific reason that unsanitized
+strings sent as a text payload for an RFC compliant WebSocket implementation
+should result in the disconnection of the client. If the client attempts to
+reconnect and receives another invalid payload it must disconnect again. If
+there is no logic to handle the reconnection attempts, this may lead to a
+denial of service attack. For instance `socket.io` attempts to reconnect by
+default.
+
+```javascript
+// Prior to these releases:
+new Buffer('ab\ud800cd', 'utf8');
+// <Buffer 61 62 ed a0 80 63 64>
+
+// After this release:
+new Buffer('ab\ud800cd', 'utf8');
+// <Buffer 61 62 ef bf bd 63 64>
+
+// This is an explicit conversion to a Buffer, but the implicit
+// .write('ab\ud800cd') also results in the same pattern
+websocket.write(new Buffer('ab\ud800cd', 'utf8'));
+// This would result in the client disconnecting.
+```
+
+Node's default encoding for strings is `UTF-8`, so even if you're not
+explicitly creating `Buffer`s out of strings, Node may be doing so under the
+hood. If what you're passing is not actually `UTF-8` then when you call
+`.write(str)` you could be specific and say `.write(str, 'binary')` which
+signals Node to pass the string through without interpreting it.
+
+You can also mitigate this in pure JavaScript by sanitizing your strings, as an
+example see
+[node-unicode-sanitize](https://github.com/felixge/node-unicode-sanitize/blob/master/index.js)
+which will similarly replace unmatched surrogate pairs with the unknown unicode
+character.
+
+Thanks to Node.js alum Felix Geisendörfer for finding, getting the fixes
+[upstreamed](https://code.google.com/p/v8/source/detail?r=18683), and helping
+with the testing and mitigation. Also for helping to inform and improve the
+process for Node.js security issues.
+
+To float these fixes in your own builds you can apply the following patch with
+`git am`
+
+ * For v0.10 branch https://gist.github.com/tjfontaine/f869f373a8e9416809ba/raw/e3eb85201413a79d12ce24a7cb4b02edf0abc1a5/v0.10-invalid-utf8.patch
+ * For v0.8 branch https://gist.github.com/tjfontaine/f869f373a8e9416809ba/raw/8633aba88fa867a88b1b3ab88d13671a78dab187/v0.8-invalid-utf8.patch
diff --git a/locale/uk/blog/vulnerability/openssl-march-2016.md b/locale/uk/blog/vulnerability/openssl-march-2016.md
new file mode 100755
index 0000000000000..371a1e6308711
--- /dev/null
+++ b/locale/uk/blog/vulnerability/openssl-march-2016.md
@@ -0,0 +1,138 @@
+---
+date: 2016-02-29T02:08:06.186Z
+category: vulnerability
+title: OpenSSL updates, 1.0.2g and 1.0.1s
+slug: openssl-march-2016
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+***(Updates to this post, including a schedule change are included below)***
+
+The OpenSSL project has [announced](https://mta.openssl.org/pipermail/openssl-announce/2016-February/000063.html) that that they will be releasing versions 1.0.2g and 1.0.1s this week, on **Tuesday the 1st of March, UTC**. The releases will fix _"several defects"_ that are labelled as _"high"_ severity under their security policy, meaning they are:
+
+> ... issues that are of a lower risk than critical, perhaps due to affecting less common configurations, or which are less likely to be exploitable.
+
+Node.js v0.10 and v0.12 both use OpenSSL v1.0.1 and Node.js v4 and v5 both use OpenSSL v1.0.2 and releases from nodejs.org and some other popular distribution sources are statically compiled. Therefore, all active release lines are impacted by this update.
+
+At this stage, due to embargo, it is uncertain the exact nature of these defects, nor what impact they will have on Node.js users, if any.
+
+As we already had minor, non-security releases scheduled for each of our active release lines during this week and next, we will be adjusting our schedule to adapt to the OpenSSL releases depending on their impact on Node.js users.
+
+We will therefore proceed as follows:
+
+Within approximately 24 hours of the OpenSSL releases, our crypto team will make an impact assessment for Node.js users of the OpenSSL releases. This information may vary depending for the different active release lines and will be posted here.
+
+As part of that impact assessment we will announce our release plans for each of the active release lines to take into account any impact. **Please be prepared for the possibility of important updates to Node.js v0.10, v0.12, v4 and v5 soon after Tuesday, the 1st of March.**
+
+### Node.js v0.10 (Maintenance)
+
+A release of Node.js v0.10.43 has been proposed for this week, it currently contains fixes for domains and an important fix for a regression in http_parser that was introduced in v0.10.42. Details of the changes included in this release along with instructions on how to download and use a release candidate (v0.10.43-rc.1) can be found in <https://github.com/nodejs/node/pull/5404>. Node.js v0.10 users are encouraged to test the release candidate build to ensure compatibility with existing deployments.
+
+If the OpenSSL 1.0.1s release contains important fixes that impact Node.js v0.10 we will endeavour to ensure that our v0.10.43 release contains the update.
+
+### Node.js v0.12 (LTS)
+
+A release of Node.js v0.12.11 has been proposed for this week, it currently contains fixes for domains, an important fix for a regression in http_parser that was introduced in v0.12.10, and some other minor fixes. Details of the changes included in this release along with instructions on how to download and use a release candidate (v0.12.11-rc.1) can be found in <https://github.com/nodejs/node/pull/5403>. Node.js v0.12 users are encouraged to test the release candidate build to ensure compatibility with existing deployments.
+
+If the OpenSSL 1.0.1s release contains important fixes for Node.js v0.12 we will endevour to ensure that our v0.12.11 release contains the update.
+
+### Node.js v4 (LTS "Argon")
+
+A significant update to Node.js v4 has been proposed for next week, the 8th of March. You can read about what will be included in Node.js v4.4.0 and find release candidates to test against your deployments at <https://github.com/nodejs/node/pull/5301>.
+
+If the OpenSSL 1.0.2g update includes important fixes that impact Node.js v4, we may release a v4.3.2 _this week_ with only the security updates in order to provide a low-risk path for Node.js v4 users.
+
+If the OpenSSL 1.0.2g update _does not include_ important fixes that impact Node.js v4, we will continue with our planned v4.4.0 release and also attempt to include the OpenSSL 1.0.2g upgrade. Users of Node.js v4 can then upgrade to v4.4.0 in their own time and allow for proper testing of the changes included.
+
+### Node.js v5 (Stable)
+
+A regular update to Node.js v5 has been proposed for this week. You can read about what will be included in the proposed Node.js v5.7.1 at <https://github.com/nodejs/node/pull/5464>. We are excluding any semver-minor changes from this release although it has fixes for some regressions 
+
+If the OpenSSL 1.0.2g release contains important fixes for Node.js v5, we will endevour to ensure that our v5.7.1 release contains the update.
+
+### Summary
+
+* Expect an impact assessment of the OpenSSL updates within 24 hours of their release
+* Expect releases of Node.js v0.10, v0.12 and v5 this week, possibly containing important security releases
+* Expect a Node.js v4.4.0 release next with the possibility of a v4.3.2 security update this week
+
+Please monitor the **nodejs-sec** Google Group for updates, including an impact assessment and updated details on release timing within approximately 24 hours after the OpenSSL release: https://groups.google.com/forum/#!forum/nodejs-sec
+
+### Contact and future updates
+
+The current Node.js security policy can be found at <https://nodejs.org/en/security/>.
+
+Please contact [security@nodejs.org](mailto:security@nodejs.org) if you wish to report a vulnerability in Node.js.
+
+Subscribe to the low-volume announcement-only **nodejs-sec** mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organisation](https://github.com/nodejs).
+
+## _(Update 2-Mar-2016)_ OpenSSL Impact Assessment
+
+Our crypto team (Ben Noordhuis, Shigeki Ohtsu and Fedor Indutny) have performed an analysis of the defects addressed in this week's OpenSSL releases, [1.0.2g](https://www.openssl.org/news/openssl-1.0.2-notes.html) and [1.0.1s](https://www.openssl.org/news/openssl-1.0.1-notes.html). The results of this analysis are included below.
+
+The overall impact to Node.js users is low, however we will be producing new versions this week for all of our release lines containing the new versions of OpenSSL in order to provide security assurance.
+
+* **[v0.10.43 (Maintenance)](https://github.com/nodejs/node/pull/5404)** will proceed as planned for this week, it includes fixes for domains and an important fix for a regression in http_parser that was introduced in v0.10.42. It will also now include an upgrade of OpenSSL to 1.0.1s. An important change will be the **complete removal of SSLv2 support**, see CVE-2016-0800 below.
+* **[v0.12.11 (LTS)](https://github.com/nodejs/node/pull/5403)** will proceed as planned for this week, it includes fixes for domains, an important fix for a regression in http_parser that was introduced in v0.12.10, and some other minor fixes. It will also now include an upgrade of OpenSSL to 1.0.1s. An important change will be the **complete removal of SSLv2 support**, see CVE-2016-0800 below.
+* **[v4.4.0 (LTS Argon)](https://github.com/nodejs/node/pull/5301)** will proceed as planned for next week and will include an upgrade of OpenSSL to 1.0.2g. We will also produce a **v4.3.2** this week with _only_ the OpenSSL upgrade in order to provide a more conservative upgrade path for users wishing to use the new OpenSSL without having to also include all of the additional non-security fixes in v4.4.0.
+* **[v5.7.1 (Stable)](https://github.com/nodejs/node/pull/5464)** will proceed as planned for this week and will include fixes for a number of regressions introduced in v5.7.0 as well as an upgrade of OpenSSL to 1.0.2g.
+
+**Release announcements for each of these will be made on the [Node.js blog](http://nodejs.org/en/blog/).**
+
+### [CVE-2016-0800](https://www.openssl.org/news/vulnerabilities.html#2016-0800): Disable SSLv2 default build, default negotiation and weak ciphers
+
+**Assessment:**
+
+* Node.js v0.10 an v0.12 **are unaffected**, unless manually enabling SSLv2 with `--enable-ssl2`
+* Node.js v4 and v5 **are unaffected**
+
+This vulnerability has been labelled the _[DROWN Attack](https://drownattack.com/)_ and only impacts servers supporting SSLv2:
+
+> Modern servers and clients use the TLS encryption protocol. However, due to misconfigurations, many servers also still support SSLv2, a 1990s-era predecessor to TLS. This support did not matter in practice, since no up-to-date clients actually use SSLv2. Therefore, even though SSLv2 is known to be badly insecure, until now, merely supporting SSLv2 was not considered a security problem, because clients never used it.
+
+> DROWN shows that merely supporting SSLv2 is a threat to modern servers and clients. It allows an attacker to decrypt modern TLS connections between up-to-date clients and servers by sending probes to a server that supports SSLv2 and uses the same private key.
+
+It is important to note that simply supporting SSLv2 on an HTTPS socket enables this vulnerability, regardless of whether clients are actively using SSLv2.
+
+Since Node.js v0.10.29, SSLv2 and SSLv3 have been disabled by default. It has remained possible to enable them with the `--enable-ssl2` and `--enable-ssl3` command-line arguments to `node`. As these protocols have consistently been demonstrated to be insecure, keeping SSLv2 and SSLv3 disabled has been strongly encouraged.
+
+If you are using the `--enable-ssl2` command-line argument with `node` then HTTPS servers are vulnerable to this attack. You should stop using this argument to avoid potential decryption of your secure data.
+
+**SSLv2 support is being removed**
+
+Given the additional barriers introduced in OpenSSL 1.0.1s to retaining SSLv2 support and the long list of known SSLv2 vulnerabilities, Node.js v0.10.43 and v0.12.11 will be completely remove SSLv2 support and the `--enable-ssl2` command-line argument.
+
+### [CVE-2016-0705](https://www.openssl.org/news/vulnerabilities.html#2016-0705): Fix a double-free in DSA code
+
+**Assessment**: All versions of Node.js **are affected**, with low severity
+
+This defect allows the use of malformed DSA to be used as a potential Denial of Service (DoS) vector or for causing memory corruption. However it is likely to be very difficult to use in practice and is therefore considered low severity for Node.js users.
+
+### [CVE-2016-0798](https://www.openssl.org/news/vulnerabilities.html#2016-0798): Disable SRP fake user seed to address a server memory leak
+
+**Assessment**: All versions of Node.js **are unaffected**
+
+The [Secure Remote Password (SRP)](https://en.wikipedia.org/wiki/Secure_Remote_Password_protocol) feature of OpenSSL is not exposed via Node.js, therefore all versions are unaffected by this defect.
+
+### [CVE-2016-0797](https://www.openssl.org/news/vulnerabilities.html#2016-0797): Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
+
+**Assessment**: All versions of Node.js **may be affected**, with low severity
+
+This defect can cause memory corruption in certain very rare cases. Additionally, the `BN_hex2bn()` and `BN_dec2bn()` functions are not explicitly used in Node.js, however they are used internally by OpenSSL for some APIs. While we are unable to confirm with certainty at this stage, we believe that Node.js is not invoking the code paths that use these functions.
+
+Combined with the difficulty of exploiting this defect and the likelihood that Node.js is not using APIs that require the internal use of these functions, this defect is considered to have a very low severity for Node.js users.
+
+### [CVE-2016-0799](https://www.openssl.org/news/vulnerabilities.html#2016-0799): Fix memory issues in BIO_*printf functions
+
+**Assessment**: All versions of Node.js **are unaffected**
+
+This defect can serve as a potential Denial of Service (DoS) vector or be used for causing memory corruption. The `BIO_*printf()` functions are used internally by OpenSSL, however the only path by which an API call by Node.js invokes these functions has a default certificate size limit, which is not changed by Node.js, that removes the possibility of exploiting this defect. Therefore we believe that Node.js is unaffected by this defect.
+
+### [CVE-2016-0702](https://www.openssl.org/news/vulnerabilities.html#2016-0702): Fix side channel attack on modular exponentiation
+
+**Assessment**: All versions of Node.js **are affected**, with low severity
+
+This defect has been labelled the _[CacheBleed Attack](https://ssrg.nicta.com.au/projects/TS/cachebleed/)_.
+
+This defect enables attackers to execute side-channel attacks leading to the potential recovery of entire RSA private keys. It only affects the Intel [Sandy Bridge](https://en.wikipedia.org/wiki/Sandy_Bridge) (and possibly older) microarchitecture when using hyper-threading. Newer microarchitectures, including Haswell, are unaffected. Disabling hyper-threading is an option for mitigating against this attack.
diff --git a/locale/uk/blog/vulnerability/openssl-may-2016.md b/locale/uk/blog/vulnerability/openssl-may-2016.md
new file mode 100755
index 0000000000000..c3c3270d9f059
--- /dev/null
+++ b/locale/uk/blog/vulnerability/openssl-may-2016.md
@@ -0,0 +1,86 @@
+---
+date: 2016-05-02T11:16:10.977Z
+category: vulnerability
+title: OpenSSL updates, 1.0.1t and 1.0.2h
+slug: openssl-may-2016
+layout: blog-post.hbs
+author: Rod Vagg
+---
+
+## _(Update 6-May-2016)_ New Node.js Releases
+
+The following releases have been made available to include the security updates to OpenSSL discussed in the post below. Please upgrade your Node.js installation as soon as possible in order to be protected against the disclosed vulnerabilities.
+
+* **Node v6.1.0 (Current)**: http://nodejs.org/en/blog/release/v6.1.0/
+* **Node v5.11.1**: http://nodejs.org/en/blog/release/v5.11.1/
+* **Node v4.4.4 (LTS)**: http://nodejs.org/en/blog/release/v4.4.4/
+* **Node v0.12.14 (Maintenance)**: http://nodejs.org/en/blog/release/v0.12.14/
+* **Node v0.10.45 (Maintenance)**: http://nodejs.org/en/blog/release/v0.10.45/
+
+***Original post is included below, along with an update containing a risk assessment***
+
+The OpenSSL project has [announced](https://mta.openssl.org/pipermail/openssl-announce/2016-April/000069.html) that that they will be releasing versions 1.0.1t and 1.0.2h this week, on **Tuesday the 3rd of May, UTC**. The releases will fix _"several security defects"_ that are labelled as _"high"_ severity under their security policy, meaning they are:
+
+> ... issues that are of a lower risk than critical, perhaps due to affecting less common configurations, or which are less likely to be exploitable.
+
+
+Node.js v0.10 and v0.12 both use OpenSSL v1.0.1 and Node.js v4, v5 and v6 use OpenSSL v1.0.2 and releases from [nodejs.org](https://nodejs.org/) and some other popular distribution sources are statically compiled. Therefore, all active release lines are impacted by this update.
+
+At this stage, due to embargo, it is uncertain the exact nature of these defects, nor what impact they will have on Node.js users, if any. We will proceed as follows:
+
+Within approximately 24 hours of the OpenSSL releases, our crypto team will make an impact assessment for Node.js users of the OpenSSL releases. This information may vary depending for the different active release lines and will be posted here.
+
+As part of that impact assessment we will announce our release plans for each of the active release lines to take into account any impact. **Please be prepared for the possibility of important updates to Node.js v0.10, v0.12, v4, v5 and v6 soon after Tuesday, the 3rd of May**. It is likely that if upgrades are required that they will be ready on or after Thursday, the 5th of May.
+
+Note that Node.js v5 will be supported until June and will therefore be included in this set of releases.
+
+Please monitor the **nodejs-sec** Google Group for updates, including an impact assessment and updated details on release timing within approximately 24 hours after the OpenSSL release: https://groups.google.com/forum/#!forum/nodejs-sec
+
+## Contact and future updates
+
+The current Node.js security policy can be found at <https://nodejs.org/en/security/>.
+
+Please contact [security@nodejs.org](mailto:security@nodejs.org) if you wish to report a vulnerability in Node.js.
+
+Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the [nodejs GitHub organisation](https://github.com/nodejs).
+
+## _(Update 4-May-2016)_ OpenSSL Impact Assessment
+
+Our crypto team (Ben Noordhuis, Shigeki Ohtsu and Fedor Indutny) have performed an analysis of the defects addressed in this week's OpenSSL releases, [1.0.2h](https://www.openssl.org/news/openssl-1.0.2-notes.html) and [1.0.1t](https://www.openssl.org/news/openssl-1.0.1-notes.html). The results of this analysis are included below.
+
+We will be producing new versions this week for all of our active release lines containing the new versions of OpenSSL in order to provide security assurance. We will provide an update here once all releases are available. **We anticipate that they will be available on, or soon after, Thursday the 5th of May, UTC**.
+
+### [CVE-2016-2107](https://www.openssl.org/news/vulnerabilities.html#2016-2107): Padding oracle in AES-NI CBC MAC check
+
+A man-in-the-middle (MITM) attacker may be able to execute a [padding oracle attack](https://en.wikipedia.org/wiki/Padding_oracle_attack) to decrypt traffic when a connection uses an AES-CBC cipher and the server runs on an Intel CPU supporting AES-NI. This is a common configuration for TLS servers.
+
+The OpenSSL project has labelled this vulnerability _high severity_.
+
+**Assessment**: All versions of Node.js are **affected** by this vulnerability.
+
+### [CVE-2016-2105](https://www.openssl.org/news/vulnerabilities.html#2016-2105): EVP_EncodeUpdate overflow
+
+An overflow can occur in the OpenSSL `EVP_EncodeUpdate()` function which is used for Base64 encoding of binary data. An attacker must be able to supply large amounts of input data in order to cause an overflow.
+
+Node.js uses the `EVP_EncodeUpdate()` internally during calls to [`crypto.Certificate#exportPublicKey()`](https://nodejs.org/api/crypto.html#crypto_certificate_exportpublickey_spkac) for [SPKAC](https://en.wikipedia.org/wiki/SPKAC) Certificate Signing Requests. User-supplied data must be passed to this method for applications to be vulnerable. This method has been available since Node.js v0.12.
+
+The OpenSSL project has labelled this vulnerability _low severity_.
+
+* Node.js v0.10 is **unaffected**
+* Node.js v0.12, v4, v5 and v6 **are affected**
+
+### [CVE-2016-2108](https://www.openssl.org/news/vulnerabilities.html#2016-2108): Memory corruption in the ASN.1 encoder
+
+**Assessment**: All versions of Node.js are believed to be **unaffected** by this vulnerability.
+
+### [CVE-2016-2106](https://www.openssl.org/news/vulnerabilities.html#2016-2106): EVP_EncryptUpdate overflow
+
+**Assessment**: All versions of Node.js are believed to be **unaffected** by this vulnerability
+
+### [CVE-2016-2109](https://www.openssl.org/news/vulnerabilities.html#2016-2109): ASN.1 BIO excessive memory allocation (CVE-2016-2109)
+
+**Assessment**: All versions of Node.js are believed to be **unaffected** by this vulnerability
+
+### [CVE-2016-2176](https://www.openssl.org/news/vulnerabilities.html#2016-2176): EBCDIC overread
+
+**Assessment**: All versions of Node.js are believed to be **unaffected** by this vulnerability
diff --git a/locale/uk/blog/vulnerability/v8-memory-corruption-stack-overflow.md b/locale/uk/blog/vulnerability/v8-memory-corruption-stack-overflow.md
new file mode 100755
index 0000000000000..118c2179a084b
--- /dev/null
+++ b/locale/uk/blog/vulnerability/v8-memory-corruption-stack-overflow.md
@@ -0,0 +1,77 @@
+---
+title: V8 Memory Corruption and Stack Overflow (fixed in Node v0.8.28 and v0.10.30)
+date: 2014-07-31T19:00:00.000Z
+slug: v8-memory-corruption-stack-overflow
+category: vulnerability
+layout: blog-post.hbs
+---
+
+A memory corruption vulnerability, which results in a denial-of-service, was
+identified in the versions of V8 that ship with Node.js 0.8 and 0.10. In
+certain circumstances, a particularly deep recursive workload that may trigger
+a GC and receive an interrupt may overflow the stack and result in a
+segmentation fault. For instance, if your work load involves successive
+`JSON.parse` calls and the parsed objects are significantly deep, you may
+experience the process aborting while parsing.
+
+This issue was identified by Tom Steele of [^Lift
+Security](https://liftsecurity.io/) and Fedor Indunty, Node.js Core Team member
+worked closely with the V8 team to find our resolution. 
+
+The V8 issue is described here https://codereview.chromium.org/339883002
+
+It has landed in the Node repository here:
+https://github.com/joyent/node/commit/530af9cb8e700e7596b3ec812bad123c9fa06356
+
+And has been released in the following versions:
+
+ * [v0.10.30](https://nodejs.org/dist/v0.10.30)
+ * [v0.8.28](https://nodejs.org/dist/v0.8.28)
+
+### The Fix
+
+The backport of the fix for Node.js is
+
+```
+diff --git a/deps/v8/src/isolate.h b/deps/v8/src/isolate.h
+index b90191d..2769ca7 100644
+--- a/deps/v8/src/isolate.h
++++ b/deps/v8/src/isolate.h
+@@ -1392,14 +1392,9 @@ class StackLimitCheck BASE_EMBEDDED {
+  public:
+   explicit StackLimitCheck(Isolate* isolate) : isolate_(isolate) { }
+ 
+-  bool HasOverflowed() const {
++  inline bool HasOverflowed() const {
+     StackGuard* stack_guard = isolate_->stack_guard();
+-    // Stack has overflowed in C++ code only if stack pointer exceeds the C++
+-    // stack guard and the limits are not set to interrupt values.
+-    // TODO(214): Stack overflows are ignored if a interrupt is pending. This
+-    // code should probably always use the initial C++ limit.
+-    return (reinterpret_cast<uintptr_t>(this) < stack_guard->climit()) &&
+-           stack_guard->IsStackOverflow();
++    return reinterpret_cast<uintptr_t>(this) < stack_guard->real_climit();
+   }
+  private:
+   Isolate* isolate_;
+```
+
+### Remediation
+
+The best course of action is to patch or upgrade Node.js.
+
+### Mitigation
+
+To mitigate against deep JSON parsing you can limit the size of the string you
+parse against, or ban clients who trigger a `RangeError` for parsing JSON.
+
+There is no specific maximum size of a JSON string, though keeping the max to
+the size of your known message bodies is suggested. If your message bodies
+cannot be over 20K, there's no reason to accept 1MB bodies.
+
+For web frameworks that do automatic JSON parsing, you may need to configure
+the routes that accept JSON payloads to have a maximum body size.
+
+ * [expressjs](http://expressjs.com) and [krakenjs](http://krakenjs.com) used with the [body-parser](https://github.com/expressjs/body-parser#bodyparserjsonoptions) plugin accepts a `limit` parameter in your JSON config
+ * [Hapi.js](http://hapijs.com) has `payload.maxBytes` https://github.com/spumko/hapi/blob/master/docs/Reference.md
+ * [restify](http://mcavage.me/node-restify/#Bundled-Plugins) bundled `bodyParser` accepts a `maxBodySize`
diff --git a/locale/uk/blog/weekly-updates/index.md b/locale/uk/blog/weekly-updates/index.md
new file mode 100755
index 0000000000000..e28599e07dced
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/index.md
@@ -0,0 +1,6 @@
+---
+title: Weekly Updates
+layout: category-index.hbs
+listing: true
+robots: noindex, follow
+---
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-02-06.md b/locale/uk/blog/weekly-updates/weekly-update.2015-02-06.md
new file mode 100755
index 0000000000000..f06dc74dbcbc6
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-02-06.md
@@ -0,0 +1,30 @@
+---
+title: Weekly Update - Feb 6th, 2015
+author: Tierney Coren (@bnb)
+date: 2015-02-06T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-02-06
+layout: blog-post.hbs
+---
+
+Every Friday we're going to start posting weekly updates of the activity in and around the project. I'll kick off a new issue each week and we can comment and collaboratively edit it before publication.
+
+# io.js in the week of February 6th 2015
+
+We looked back at all the contributions in January and found that this is the 3rd most active month in Node history (294 commits) and the single most active month in almost three years (308 commits in February 2012). With the contribution growth we've seen so far we expect February to be even more active.
+
+* 1.1.0 release. https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md#2015-02-03-version-110-chrisdickinson
+* Simplified Stream Construction https://github.com/nodejs/node/commit/50daee7243a3f987e1a28d93c43f913471d6885a
+* io.js support added to Travis CI http://docs.travis-ci.com/user/build-environment-updates/2015-02-03/
+* codeship supports io.js https://codeship.com/documentation/languages/nodejs/#iojs
+* Atom Editor moved to io.js. https://github.com/atom/atom/releases/tag/v0.177.0
+* nw.js (formerly node-webkit) moved to io.js https://github.com/nwjs/nw.js/issues/2742
+* New Tessel Hardware will support io.js http://blog.technical.io/post/110115579867/upcoming-hardware-from-technical-machine
+* Chris Dickinson on-boarded six new committers, bringing the total number of active committers to 23. https://github.com/nodejs/node/issues/680#issuecomment-73089691
+* WIP: Stability and Compatibility Policy https://github.com/nodejs/node/issues/725
+* TC Meeting Highlights
+* Website Working Group Highlights
+* First Tracing Working Group Meeting
+* We've started reaching out to companies for feedback on our roadmap. https://github.com/iojs/roadmap/issues/13 If there are any companies we missed please drop the contact information in to that GitHub Issue.
+* Next week is Node Summit w/ many io.js people speaking and in attendance. Bert Belder,  Thorsten Lorenz, will be speaking Isaac Schlueter.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-02-13.md b/locale/uk/blog/weekly-updates/weekly-update.2015-02-13.md
new file mode 100755
index 0000000000000..b6c18675ffea6
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-02-13.md
@@ -0,0 +1,99 @@
+---
+title: Weekly Update - Feb 13th, 2015
+author: Tierney Coren (@bnb)
+date: 2015-02-13T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-02-13
+layout: blog-post.hbs
+---
+
+## io.js support added by...
+* [Postmark](http://blog.postmarkapp.com/post/110829734198/its-official-were-getting-cozy-with-node-js)
+* [node-serialport](https://github.com/voodootikigod/node-serialport/issues/439)
+* [Microsoft Azure](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/)
+
+## io.js breaks 10,000 stars on GitHub
+On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. We couldn't have done it without the support of the amazing community behind JavaScript. Thank you alll!
+
+## io.js 1.2.0 released
+* **stream**: Simpler stream construction ([readable-stream/issues#102[(https://github.com/iojs/readable-stream/issues/102))
+* **dns**: `lookup()` now supports an `'all'` boolean option, default to `false` but when turned on will cause the method to return an array of all resolved names for an address, see, ([iojs/pull#744](https://github.com/nodejs/node/pull/744))
+* **assert**: Remove `prototype` property comparison in `deepEqual()` ([iojs/issues#636](https://github.com/nodejs/node/pull/636)); introduce a `deepStrictEqual()` method to mirror `deepEqual()` but performs strict equality checks on primitives ([iojs/issues#639](https://github.com/nodejs/node/pull/639)).
+* **tracing**: Add [LTTng](http://lttng.org/) (Linux Trace Toolkit Next Generation) when compiled with the `--with-lttng option`. Trace points match those available for DTrace and ETW. ([iojs/issues#702](https://github.com/nodejs/node/pull/702))
+* **docs**: Lots of doc updates, see individual commits; new Errors page discussing JavaScript errors, V8 specifics, and io.js specific error details.
+* **npm** upgrade to 2.5.1
+* **libuv** upgrade to 1.4.0, see libuv [ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog)
+* Add new collaborators:
+  * Aleksey Smolenchuk (@lxe)
+  * Shigeki Ohtsu (@shigeki)
+
+## Opened our doors to the international community
+View the [original article](https://medium.com/@mikeal/how-io-js-built-a-146-person-27-language-localization-effort-in-one-day-65e5b1c49a62) on Medium.
+* Added interested contributors to teams for their language.
+* Teams registered Twitter accounts for their teams and other relevant social media accounts.
+* Teams came up with their own ways of working together, and they became more of "community organizers," as opposed to just "translators"
+
+### Stats for Localizations:
+
+* 146 people signed up to help with the localizations the first day (over 160 signed up now)
+* 27 languages communities created the first day (already up to 29)
+
+### Language Communities
+
+* [`iojs-bn`](https://github.com/iojs/iojs-bn) Bengali Community
+* [`iojs-cn`](https://github.com/iojs/iojs-cn) Chinese Community
+* [`iojs-cs`](https://github.com/iojs/iojs-cs) Czech Community
+* [`iojs-da`](https://github.com/iojs/iojs-da) Danish Community
+* [`iojs-de`](https://github.com/iojs/iojs-de) German Community
+* [`iojs-el`](https://github.com/iojs/iojs-el) Greek Community
+* [`iojs-es`](https://github.com/iojs/iojs-es) Spanish Community
+* [`iojs-fa`](https://github.com/iojs/iojs-fa) Persian Community
+* [`iojs-fi`](https://github.com/iojs/iojs-fi) Finnish Community
+* [`iojs-fr`](https://github.com/iojs/iojs-fr) French Community
+* [`iojs-he`](https://github.com/iojs/iojs-he) Hebrew Community
+* [`iojs-hi`](https://github.com/iojs/iojs-hi) Hindi Community
+* [`iojs-hu`](https://github.com/iojs/iojs-hu) Hungarian Community
+* [`iojs-id`](https://github.com/iojs/iojs-id) Indonesian Community
+* [`iojs-it`](https://github.com/iojs/iojs-it) Italian Community
+* [`iojs-ja`](https://github.com/iojs/iojs-ja) Japanese Community
+* [`iojs-ka`](https://github.com/iojs/iojs-ka) Georgian Community
+* [`iojs-kr`](https://github.com/iojs/iojs-kr) Korean Community
+* [`iojs-mk`](https://github.com/iojs/iojs-mk) Macedonian Community
+* [`iojs-nl`](https://github.com/iojs/iojs-nl) Dutch Community
+* [`iojs-no`](https://github.com/iojs/iojs-no) Norwegian Community
+* [`iojs-pl`](https://github.com/iojs/iojs-pl) Polish Community
+* [`iojs-pt`](https://github.com/iojs/iojs-pt) Portuguese Community
+* [`iojs-ro`](https://github.com/iojs/iojs-ro) Romanian Community
+* [`iojs-ru`](https://github.com/iojs/iojs-ru) Russian Community
+* [`iojs-sv`](https://github.com/iojs/iojs-sv) Swedish Community
+* [`iojs-tr`](https://github.com/iojs/iojs-tr) Turkish Community
+* [`iojs-tw`](https://github.com/iojs/iojs-tw) Taiwan Community
+* [`iojs-uk`](https://github.com/iojs/iojs-uk) Ukranian Community
+
+## io.js and Node.js
+View the [original article](https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be) on Medium.
+* Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the node.js.
+
+#### In only a few months io.js...
+* Has grown to 23 active core team members
+* Has several working groups
+* Has 29 language localization teams,
+* Has drawn more contributors to the project than we’ve ever had in the history of node.js, and
+* Has been able to release quality software at a good pace with the support of an exceptional community.
+
+> We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.
+
+### The Future
+* Talks with the node.js foundation are ongoing.
+* Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join.
+
+  * This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built.
+
+> For the community, nothing has changed.
+
+### What to do right now
+* Continue to send your pull requests to io.js
+* Join one of the 27 [language localization teams](https://github.com/iojs/website/issues/125)
+* Contribute to io.js’ working groups ([streams](https://github.com/iojs/readable-stream), [website](https://github.com/iojs/website), [evangelism](https://github.com/iojs/website/labels/evangelism), [tracing](https://github.com/iojs/tracing-wg), [build](https://github.com/iojs/build), [roadmap](https://github.com/iojs/roadmap)) and
+* Continue to adopt io.js in your applications.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-02-20.md b/locale/uk/blog/weekly-updates/weekly-update.2015-02-20.md
new file mode 100755
index 0000000000000..0de7b293a1125
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-02-20.md
@@ -0,0 +1,38 @@
+---
+title: Weekly Update - Feb 20th, 2015
+author: Tierney Coren (@bnb)
+date: 2015-02-20T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-02-20
+layout: blog-post.hbs
+---
+
+## io.js Releases 1.3.0
+Notable changes include:
+* **url**: `url.resolve('/path/to/file', '.')` now returns `/path/to/` with the trailing slash, `url.resolve('/', '.')` returns `/` [#278](https://github.com/nodejs/node/pull/278) (Amir Saboury)
+* **tls**: The default cipher suite used by `tls` and `https` has been changed to one that achieves Perfect Forward Secrecy with all modern browsers. Additionally, insecure RC4 ciphers have been excluded. If you absolutely require RC4, please specify your own cipher suites. [#826](https://github.com/nodejs/node/pull/826) (Roman Reiss)
+
+## Notable Events in the Community
+* **Node Governance** - [William Bert](https://twitter.com/williamjohnbert) created http://nodegovernance.io/ to alert Scott Hammond, CEO of Joyent, of the desire of the community for the io.js open-governance model to be the base upon which the Node Foundation's Technical Committee. The response from the community was _fantastic_!
+* **Node.js and io.js Performance Improves** - Raygun.io did performance tests with both Node.js and io.js recently, and both are improving performance with each release! [Read the full article](https://raygun.io/blog/2015/02/node-js-performance-node-js-vs-io-js/).
+* **LTTng Basics** - [LTTing Basics](https://asciinema.org/a/16785) with io.js by user jgalar on asciinema
+* **io.js Roadmap Slides** - Slide deck for the current roadmap of io.js up.
+
+### io.js Support Added
+* [TravisCI](https://travis-ci.org/) added io.js.The day the last Weekly Update was posted, Hiro Asari (あさり) [tweeted](https://twitter.com/hiro_asari/status/566268486012633088) that about 10% of Node projects were running io.js.
+* @thlorenz updated [nad](https://github.com/thlorenz/nad), Node Addon Developer, to [support io.js](https://twitter.com/thlorenz/status/566328088121081856)
+* [Catberry.js](https://github.com/catberry/catberry) added support for io.js.
+* Official mongodb node module supports io.js in [v. 2.0.16 2015-02-16](https://github.com/mongodb/node-mongodb-native/blob/2.0/HISTORY.md).
+* [The Native Web](http://www.thenativeweb.io/) now has a [io.js Docker container](https://registry.hub.docker.com/u/thenativeweb/iojs/)
+* [DNSChain](https://github.com/okTurtles/dnschain) by [okTurtles](https://okturtles.com/) added support for io.js.
+* [TDPAHACLPlugin](https://github.com/neilstuartcraig/TDPAHACLPlugin) and [TDPAHAuthPlugin](https://github.com/neilstuartcraig/TDPAHAuthPlugin) for [actionHero](http://www.actionherojs.com/) now support io.js.
+* [node-sass](https://npmjs.org/package/node-sass) added support for io.js 1.2 in node-sass [v. 2.0.1](https://github.com/sass/node-sass/issues/655)
+* [total.js](https://www.totaljs.com/) added support for io.js in [v. 1.7.1](https://github.com/totaljs/framework/releases/tag/v1.7.1)
+* [Clever Cloud](https://www.clever-cloud.com/) added [support for io.js](https://www.clever-cloud.com/blog/features/2015/01/23/introducing-io.js/)
+
+## io.js Working Group Meetings
+* io.js Tracing Working Group Meeting - Feb. 19, 2015: [YouTube](https://www.youtube.com/watch?v=wvBVjg8jkv0) - [Minutes](https://docs.google.com/document/d/1_ApOMt03xHVkaGpTEPMDIrtkjXOzg3Hh4ZcyfhvMHx4/edit)
+* io.js Build Working Group Meeting - Feb. 19, 2015: [YouTube](https://www.youtube.com/watch?v=OKQi3pTF7fs) - [SoundCloud](https://soundcloud.com/iojs/iojs-build-wg-meeting-2015-02-19) - [Minutes](https://docs.google.com/document/d/1vRhsYBs4Hw6vRu55h5eWTwDzS1NctxdTvMMEnCbDs14/edit)
+* io.js Technical Committee Meeting - Feb. 18, 2015: [YouTube](https://www.youtube.com/watch?v=jeBPYLJ2_Yc) - [SoundCloud](https://soundcloud.com/iojs/iojs-tc-meeting-meeting-2015-02-18) - [Minutes](https://docs.google.com/document/d/1JnujRu6Rfnp6wvbvwCfxXnsjLySunQ_yah91pkvSFdQ/edit)
+* io.js Website Working Group Meeting - Feb. 16, 2015: [YouTube](https://www.youtube.com/watch?v=UKDKhFV61ZA) - [SoundCloud](https://soundcloud.com/iojs/iojs-website-wg-meeting-2015-02-16) - [Minutes](https://docs.google.com/document/d/1R8JmOoyr64tt-QOj27bD19ZOWg63CujW7GeaAHIIkUs/edit)
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-02-27.md b/locale/uk/blog/weekly-updates/weekly-update.2015-02-27.md
new file mode 100755
index 0000000000000..a312ae7a4ea98
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-02-27.md
@@ -0,0 +1,55 @@
+---
+title: Weekly Update - Feb 27th, 2015
+author: Emily Rose (@emilyrose)
+date: 2015-02-27T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-02-27
+layout: blog-post.hbs
+---
+
+# io.js 1.4.1 Release
+
+_Note: version **1.4.0** was tagged and built but not released. A libuv bug was discovered in the process so the release was aborted. We have jumped to 1.4.1 to avoid confusion._
+
+## Notable changes
+
+* **process** / **promises**: An`'unhandledRejection'` event is now emitted on `process` whenever a `Promise` is rejected and no error handler is attached to the `Promise` within a turn of the event loop. A `'rejectionHandled'` event is now emitted whenever a `Promise` was rejected and an error handler was attached to it later than after an event loop turn.  [#758](https://github.com/nodejs/node/pull/758) (Petka Antonov)
+* **streams**: you can now use regular streams as an underlying socket for `tls.connect()` [#926](https://github.com/nodejs/node/pull/926) (Fedor Indutny)
+* **http**: A new `'abort'` event emitted when a `http.ClientRequest` is aborted by the client. [#945](https://github.com/nodejs/node/pull/945) (Evan Lucas)
+* **V8**: Upgrade V8 to 4.1.0.21. Includes an embargoed fix, details should be available when embargo is lifted. A breaking ABI change has been held back from this upgrade, possibly to be included when io.js merges V8 4.2. See [#952](https://github.com/nodejs/node/pull/952) for discussion.
+* **npm**: Upgrade npm to 2.6.0. Includes features to support the new registry and to prepare for `npm@3`. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v260-2015-02-12) for details. Summary:
+  * [#5068](https://github.com/npm/npm/issues/5068) Add new logout command, and make it do something useful on both bearer-based and basic-based authed clients.
+  * [#6565](https://github.com/npm/npm/issues/6565) Warn that `peerDependency` behavior is changing and add a note to the docs.
+  * [#7171](https://github.com/npm/npm/issues/7171) Warn that `engineStrict` in `package.json` will be going away in the next major version of npm (coming soon!)
+* **libuv**: Upgrade to 1.4.2. See [libuv ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details of fixes.
+
+# ARM offers support for io.js on ARMv8
+
+ARM contacted Rod Vagg, lead of the io.js Build Working Group, to offer their support to the io.js project. ARM and their hardware partners are on track to make ARMv8 a viable server platform and the nimble nature of server-side JavaScript make it a perfect fit to run on the new ARM.
+
+Since ARMv8 is already being adopted by mobile device manufacturers, newer versions of V8 already have good support. Because of V8's pivotal role in Android, io.js is perfectly suited to track that support, and even contribute to it given our new relationships with the V8 team.
+
+From the beginning of the io.js project, Rod has championed the role of ARM for io.js, for IoT, hobbyist, and server use. We already have ARMv6 builds of each release for devices such as Raspberry Pi. and ARMv7 builds for many more popular devices (including the Online Labs ARM-based cloud platform, who have also offered help to io.js). ARMv8 is the logical extension of this, but also has exciting potential for server-side applications, particularly given the new 64-bit support.
+
+The build team is in the process of being given access to the Linaro ARMv8 Server Cluster for integration with the io.js CI platform, which should eventually lead to regular ARMv8 binary releases.
+
+# Community Updates
+
+* [**Reconciliation Proposal**](https://github.com/nodejs/node/issues/978): The io.js project is preparing a plan for reconciliation that can be brought to The Node.js Foundation. Input from the community is very important at this early stage so please leave a comment.
+* **New internal C++ Streams API**: A [fresh C++ Streams API](https://github.com/nodejs/node/commit/b9686233fc0be679d7ba1262b611711629ee334e) landed in io.js this week, allowing you to wrap a TLS stream into another TLS stream.
+* **io.js Roadmap**: [The Roadmap](https://github.com/nodejs/node/blob/v1.x/ROADMAP.md) is the plan for the future of io.js. It presents the plans for the stability policy, and lists what the immediate priorities for io.js as a whole are.
+* **Roadmap Slides Finished and Ready for Translation**: The set of introductory slides for the Roadmap of io.js [have been finished, and are ready for translation](https://github.com/iojs/roadmap/issues/18). Do you think you could present them to a group near you? Comment and we'll work with you to prepare you to present!
+* **Microsoft io.js How-To for Azure Websites**: Microsoft [published a how-to](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/) tutorial for their Azure platform that describes how to use io.js with Azure Websites.
+* **Floobits moves to io.js**: The code pairing software Floobits [converted their platform to io.js](https://news.floobits.com/2015/02/23/on-moving-to-io.js/), in part because of frustration with Node's slower release cycle, because the inclusion of more ES6 features without the need for the `--harmony` flag, and because they felt changes from 0.10.0 to 0.12.0 weren't very big.
+* **Anand Mani Sankar's _Node.js vs io.js: Why the fork?!?_**: Anand wrote a good, for the most part objective, [post about the recent history of io.js](http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/#.VO82hE60PVw.twitter), and what we hope to achieve with it. A good read for people who aren't engaged in the community to catch up with.
+* **iojs-jp - New io.js Japanese Blog**: The iojs-jp community has created a [localized io.js related blog](http://blog.iojs.jp/) to disseminate content in their language. If you're interested, take a look!
+* **iojs-cn - New io.js Chinese Blog**: Similarly to the iojs-jp community, the iojs-cn community created a [localized blog](http://cn.iojs.org/) to publish posts about io.js to in their language. Make sure to visit if you're curious about iojs-cn or Chinese news about io.js!
+* **[Roadmap Slides Review](https://www.youtube.com/watch?v=etI_UD4wXlo)** - A review of the roadmap slides before they were released to ensure they met with the message the project upholds.
+
+# io.js Support Added
+* **[Wallaby.js](http://wallabyjs.com/)**, a while-you-write testing library for JavaScript, hit version 1.0 and [added support for io.js](http://dm.gl/2015/02/23/wallaby-version-one/)!
+* **[jsdom](https://github.com/tmpvar/jsdom)**, an implementation of the WHATWG DOM and HTML standards, just hit [version 4.0.0](https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400), which added a _requirement_ of io.js.
+* **[give](https://github.com/mmalecki/give)**'s creator [tweeted](https://twitter.com/maciejmalecki/status/569629100215816192) that newer versions of give support io.js. Give is a git-based node.js/io.js version manager.
+* The **Firebase Realtime Client**, the official web/node.js JavaScript client for Firebase, [tweeted](https://twitter.com/FirebaseRelease/status/570000737343647744) that they added support for io.js in [version 2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client)
+* **Semaphore**, a hosted continuous integrations service, [tweeted](https://twitter.com/semaphoreapp/status/570987355005431809) about added io.js support in their [Platform update on February 24th, 2015](https://semaphoreapp.com/blog/2015/02/17/platform-update-on-february-24th.html?utm_source=twitter&utm_medium=social&utm_content=platform_update_launch&utm_campaign=platformupdate).
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-03-06.md b/locale/uk/blog/weekly-updates/weekly-update.2015-03-06.md
new file mode 100755
index 0000000000000..f411f1305b28a
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-03-06.md
@@ -0,0 +1,61 @@
+---
+title: Weekly Update - Mar 6th, 2015
+author: Ross Kukulinski (@rosskukulinksi)
+date: 2015-03-06T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-03-06
+layout: blog-post.hbs
+---
+
+# io.js 1.5.0 Release
+
+On Friday, March 6th, [@rvagg](https://github.com/rvagg) released io.js [**v1.5.0**](https://iojs.org/dist/latest/).  The complete change log can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+* **buffer**: New `Buffer#indexOf()` method, modelled off [`Array#indexOf()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/indexOf). Accepts a String, Buffer or a Number. Strings are interpreted as UTF8. (Trevor Norris) [#561](https://github.com/nodejs/node/pull/561)
+* **fs**: `options` object properties in `'fs'` methods no longer perform a `hasOwnProperty()` check, thereby allowing options objects to have prototype properties that apply. (Jonathan Ong) [#635](https://github.com/nodejs/node/pull/635)
+* **tls**: A likely TLS memory leak was reported by PayPal. Some of the recent changes in **stream_wrap** appear to be to blame. The initial fix is in [#1078](https://github.com/nodejs/node/pull/1078), you can track the progress toward closing the leak at [#1075](https://github.com/nodejs/node/issues/1075) (Fedor Indutny).
+* **npm**: Upgrade npm to 2.7.0. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v270-2015-02-26) for details including why this is a semver-minor when it could have been semver-major.
+* **TC**: Colin Ihrig (@cjihrig) resigned from the TC due to his desire to do more code and fewer meetings.
+
+### Known issues
+
+* Possible TLS-related memory leak, details at [#1075](https://github.com/nodejs/node/issues/1075).
+* Windows still reports some minor test failures and we are continuing to address all of these as a priority. See [#1005](https://github.com/nodejs/node/issues/1005).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* Not possible to build io.js as a static library [#686](https://github.com/nodejs/node/issues/686)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+
+# Community Updates
+
+* You can relax knowing that io.js and latest node.js [**are not affected**](https://strongloop.com/strongblog/are-node-and-io-js-affected-by-the-freak-attack-openssl-vulnerability/) by the [FREAK Attack](https://freakattack.com/).  You are running io.js or the latest version of node.js, right?
+
+* Walmart is now sponsoring a build machine for the io.js Jenkins CI system.  The @iojs/build team is working on creating io.js SunOS binaries (like you can get from nodejs.org).  A V8 fix ([iojs/io.js#1079](https://github.com/nodejs/node/pull/1079)) needs to be landed first before more progress can be made.
+* We would also like to thank the following companies for contributing hardware and related technology/support/engineering for io.js builds:
+  * **Digital Ocean** (mainly Linux)
+  * **Rackspace** (mainly Windows)
+  * **Voxer** (OS X and FreeBSD)
+  * **NodeSource** (ARMv6 & ARMv7)
+  * **Linaro** (ARMv8)
+  * **Walmart** (SmartOS / Solaris)
+* The io.js community has been hard at work on the internationalization of all of its content.  There are now over 20 active languages published on [iojs.org](http://iojs.org) and i18n community sites.  Additionally, i18n links ([iojs/website#258](https://github.com/iojs/website/pull/258)) have been added to the website footer for easy access.  Are we missing your language?  [Help us add it!](https://github.com/iojs/website/blob/master/TRANSLATION.md)
+* Speaking of translations, the [io.js roadmap presentation](http://roadmap.iojs.org/) has been updated to link to other language versions.
+
+* It seems that **PayPal** is running an experiment comparing [Kappa](https://www.npmjs.com/package/kappa)  on io.js vs node.js 0.12 vs node.js v0.10.  The PayPal team identified a likely TLS memory leak. Initial fix is in [#1078](https://github.com/nodejs/node/pull/1078) and progress towards closing is in [#1075](https://github.com/nodejs/node/issues/1075)
+
+* [**NodeSource**](http://nodesource.com) is now providing io.js [Linux binary](https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories) packages for Ubuntu/Debian as well as RHEL/Fedora distributions.
+* The io.js [Docker build](https://registry.hub.docker.com/u/library/iojs/) is one of thirteen new [official Docker repositories](http://blog.docker.com/2015/03/thirteen-new-official-repositories-added-in-january-and-february/) added in January and February.
+
+* NodeBots and IoT people should be happy to hear that the just-announced [**Tessel2**](http://blog.technical.io/post/112787427217/tessel-2-new-hardware-for-the-tessel-ecosystem) runs [io.js natively](http://blog.technical.io/post/112888410737/moving-faster-with-io-js).
+* [**@maxbeatty**](https://twitter.com/maxbeatty) is working on a new version of the [jsperf.com](http://jsperf.com/) backend, running on io.js and it is entirely [open source](https://github.com/jsperf/jsperf.com).  Contributions are welcome!
+
+* [@eranhammer](https://twitter.com/eranhammer) wrote a blog post called [The Node Version Dilemma](http://hueniverse.com/2015/03/02/the-node-version-dilemma/) which discusses the various node.js / io.js versions and proposes which ones to use and when to use them.
+
+
+
+# io.js Support Added
+
+* **[scrypt](https://npmjs.com/scrypt)** now supports io.js. Learn more from this [GitHub issue](https://github.com/barrysteyn/node-scrypt/issues/39)
+* **[proxyquire](https://github.com/thlorenz/proxyquire)** v1.3.2 published with support for iojs.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-03-13.md b/locale/uk/blog/weekly-updates/weekly-update.2015-03-13.md
new file mode 100755
index 0000000000000..7afb0b44f35b7
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-03-13.md
@@ -0,0 +1,43 @@
+---
+title: Weekly Update - Mar 13th, 2015
+author: Julian Duque (julianduque) & Yosuke Furukawa (yosuke-furukawa)
+date: 2015-03-13T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-03-13
+layout: blog-post.hbs
+---
+
+# io.js 1.5.1 Release
+
+On Monday, March 9th, [@rvagg](https://github.com/rvagg) released io.js [v1.5.1](https://iojs.org/dist/v1.5.1/). The complete change log can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+* **tls**: The reported TLS memory leak has been resolved via various commits in this release. Current testing indicated that there _may_ still be some leak problems. Track complete progress at [#1075](https://github.com/nodejs/node/issues/1075).
+* **http**: Fixed an error reported at [joyent/node#9348](https://github.com/joyent/node/issues/9348) and [npm/npm#7349](https://github.com/npm/npm/issues/7349). Pending data was not being fully read upon an `'error'` event leading to an assertion failure on `socket.destroy()`. (Fedor Indutny) [#1103](https://github.com/nodejs/node/pull/1103)
+
+### Known issues
+
+* Possible remaining TLS-related memory leak(s), details at [#1075](https://github.com/nodejs/node/issues/1075).
+* Windows still reports some minor test failures and we are continuing to address all of these as a priority. See [#1005](https://github.com/nodejs/node/issues/1005).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* Not possible to build io.js as a static library [#686](https://github.com/nodejs/node/issues/686)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+
+# Community Updates
+
+* [Tony Pujals](https://twitter.com/subfuzion) gave [the io.js roadmap presentation](http://roadmap.iojs.org/) to [BayNode](http://www.meetup.com/BayNode/events/220246228/). The video was posted to [vimeo](https://vimeo.com/121707989) on March 9. Slides are available for anyone to give at their [local meetup](mailto:ron.buell@rd.io).
+* [Johan Bergström](https://github.com/jbergstroem) is working on getting a patch into [V8](https://codereview.chromium.org/990063002) on behalf of io.js to bring Solaris support back into the latest version
+* [NodeUp Episode 84](http://nodeup.com/eightyfour) it's io.js update #1 with [Mikeal Rogers](https://github.com/mikeal), [Trevor Norris](https://github.com/trevnorris) and [Bradley Meck](https://github.com/bmeck)
+* [Mikeal Rogers](https://github.com/mikeal) was interviewed for [Descriptive](http://descriptive.audio) podcast on an episoded called [We've Never Had This Many Active Contributors to Core Before](http://descriptive.audio/episodes/12)
+* [Mark Wolfe](https://twitter.com/wolfeidau) gave a [talk about io.js](https://twitter.com/wolfeidau/status/575785856545378304) at [@melbjs](https://twitter.com/melbjs) meetup, slides are published [here](https://speakerdeck.com/wolfeidau/iojs-bringing-es6-to-the-node)
+* [dockeri.co](http://dockeri.co/) now runs on io.js, you can see the announcement [here](https://twitter.com/wjblankenship/status/575867637680369665)
+* [Node.js Advisory Board](https://nodejs.org/about/advisory-board/) are talking about the [io.js/Node.js reconciliation proposal](https://github.com/nodejs/node/issues/978), you can check the meeting minutes [here](https://github.com/joyent/nodejs-advisory-board/blob/master/meetings/2015-03-09/minutes.md#nodejsiojs-reconciliation-bb)
+
+# Upcoming Events
+
+* [NodeConf](http://nodeconf.com/) tickets are on sale, June 8th and 9th at Oakland, CA and NodeConf Adventure for June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-03-20.md b/locale/uk/blog/weekly-updates/weekly-update.2015-03-20.md
new file mode 100755
index 0000000000000..c20a53cefd697
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-03-20.md
@@ -0,0 +1,52 @@
+---
+title: Weekly Update - Mar 20th, 2015
+author: Julian Duque (julianduque)
+date: 2015-03-20T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-03-20
+layout: blog-post.hbs
+---
+
+# io.js 1.6 release
+This week we had a two io.js releases [v1.6.1](https://iojs.org/dist/v1.6.1/) and  [v1.6.0](https://iojs.org/dist/v1.6.0/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+#### 1.6.1
+
+* **path**: New type-checking on `path.resolve()` [#1153](https://github.com/nodejs/node/pull/1153) uncovered some edge-cases being relied upon in the wild, most notably `path.dirname(undefined)`. Type-checking has been loosened for `path.dirname()`, `path.basename()`, and `path.extname()` (Colin Ihrig) [#1216](https://github.com/nodejs/node/pull/1216).
+* **querystring**: Internal optimizations in `querystring.parse()` and `querystring.stringify()` [#847](https://github.com/nodejs/node/pull/847) prevented `Number` literals from being properly converted via `querystring.escape()` [#1208](https://github.com/nodejs/node/issues/1208), exposing a blind-spot in the test suite. The bug and the tests have now been fixed (Jeremiah Senkpiel) [#1213](https://github.com/nodejs/node/pull/1213).
+
+#### 1.6.0
+
+* **node**: a new `-r` or `--require` command-line option can be used to pre-load modules at start-up (Ali Ijaz Sheikh) [#881](https://github.com/nodejs/node/pull/881).
+* **querystring**: `parse()` and `stringify()` are now faster (Brian White) [#847](https://github.com/nodejs/node/pull/847).
+* **http**: the `http.ClientRequest#flush()` method has been deprecated and replaced with `http.ClientRequest#flushHeaders()` to match the same change now in Node.js v0.12 as per [joyent/node#9048](https://github.com/joyent/node/pull/9048) (Yosuke Furukawa) [#1156](https://github.com/nodejs/node/pull/1156).
+* **net**: allow `server.listen()` to accept a `String` option for `port`, e.g. `{ port: "1234" }`, to match the same option being accepted in `net.connect()` as of [joyent/node#9268](https://github.com/joyent/node/pull/9268) (Ben Noordhuis) [#1116](https://github.com/nodejs/node/pull/1116).
+* **tls**: further work on the reported memory leak although there appears to be a minor leak remaining for the use-case in question, track progress at [#1075](https://github.com/nodejs/node/issues/1075).
+* **v8**: backport a fix for an integer overflow when `--max_old_space_size` values above `4096` are used (Ben Noordhuis) [#1166](https://github.com/nodejs/node/pull/1166).
+* **platforms**: the io.js CI system now reports passes on **FreeBSD** and **SmartOS** (_Solaris_).
+* **npm**: upgrade npm to 2.7.1. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v271-2015-03-05) for details.
+
+### Known Issues
+
+* Possible remaining TLS-related memory leak(s), details at [#1075](https://github.com/nodejs/node/issues/1075).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* Not possible to build io.js as a static library [#686](https://github.com/nodejs/node/issues/686)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+
+# Community Updates
+
+* browserify supports io.js, you can check the announcement [here](https://twitter.com/yosuke_furukawa/status/577150547850969088)
+* express.js added [support](https://github.com/strongloop/express/commit/165660811aa9ba5f3733a7b033894f3d9a9c5e60) to io.js
+* Over the last two weeks we got access to hardware from Joyent and upstreamed a patch to V8 so we got io.js building. After that we worked on passing tests for both [SmartOS](https://github.com/iojs/build/pull/64) and [FreeBSD](https://github.com/nodejs/node/pull/1167) which as of two days ago now pass, this was thanks to the amazing work of the build team and [Johan Bergström](https://github.com/jbergstroem)
+* [Petka Antonov](https://github.com/petkaantonov) is proposing a workers implementation in io.js under an experimental flag, you can join the discussion [here](https://github.com/nodejs/node/pull/1159)
+* io.js [upgraded](https://github.com/nodejs/node/pull/1206) openssl to `1.0.1m`
+
+# Upcoming Events
+
+* [NodeConf](http://nodeconf.com/) tickets are on sale, June 8th and 9th at Oakland, CA and NodeConf Adventure for June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-03-27.md b/locale/uk/blog/weekly-updates/weekly-update.2015-03-27.md
new file mode 100755
index 0000000000000..425cd767db05e
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-03-27.md
@@ -0,0 +1,42 @@
+---
+title: Weekly Update - Mar 27th, 2015
+author: Yosuke Furukawa (yosuke-furukawa)
+date: 2015-03-27T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-03-27
+layout: blog-post.hbs
+---
+
+# io.js 1.6.2 release
+This week we had one io.js releases [v1.6.2](https://iojs.org/dist/v1.6.2/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+#### 1.6.2
+
+* **Windows**: The ongoing work in improving the state of Windows support has resulted in full test suite passes once again. As noted in the release notes for v1.4.2, CI system and configuration problems prevented it from properly reporting problems with the Windows tests, the problems with the CI and the codebase appear to have been fully resolved.
+* **FreeBSD**: A [kernel bug](https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055043.html) impacting io.js/Node.js was [discovered](https://github.com/joyent/node/issues/9326) and a patch has been introduced to prevent it causing problems for io.js (Fedor Indutny) [#1218](https://github.com/nodejs/node/pull/1218).
+* **module**: you can now `require('.')` instead of having to `require('./')`, this is considered a bugfix (Michaël Zasso) [#1185](https://github.com/nodejs/node/pull/1185).
+* **v8**: updated to 4.1.0.25 including patches for `--max_old_space_size` values above `4096` and Solaris support, both of which are already included in io.js.
+
+### Known issues
+
+* Possible small memory leak(s) may still exist but have yet to be properly identified, details at [#1075](https://github.com/nodejs/node/issues/1075).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* Not possible to build io.js as a static library [#686](https://github.com/nodejs/node/issues/686)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+
+# Community Updates
+
+* Node.js Technical Governance Draft is proposed, you can check the draft [here](https://github.com/joyent/nodejs-advisory-board/pull/30)
+* Microsoft Visual Studio team releases Node.js Tools 1.0 for Visual Studio, the release includes rich editor, code completions, interactive window, advanced debugging and profiling. Check [the announcement](http://blogs.msdn.com/b/visualstudio/archive/2015/03/25/node-js-tools-1-0-for-visual-studio.aspx).
+* [SPM monitor supports node.js and io.js](http://blog.sematext.com/2015/03/30/nodejs-iojs-monitoring/), the monitor adds performance monitoring, alerting, and anomaly detection.
+
+# Upcoming Events
+
+* [NodeConf](http://nodeconf.com/) tickets are on sale, June 8th and 9th at Oakland, CA and NodeConf Adventure for June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [nodeSchool tokyo](http://nodejs.connpass.com/event/13182/) will be held in April 12th at Tokyo, Japan
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-04-03.md b/locale/uk/blog/weekly-updates/weekly-update.2015-04-03.md
new file mode 100755
index 0000000000000..47868df7ed5cd
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-04-03.md
@@ -0,0 +1,49 @@
+---
+title: Weekly Update - Apr 3rd, 2015
+author:  Giovanny Gioyik (@Gioyik)
+date: 2015-04-03T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-04-03
+layout: blog-post.hbs
+---
+
+# io.js 1.6.3 release
+This week we had one io.js release [v1.6.3](https://iojs.org/dist/v1.6.3/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+* **fs**: corruption can be caused by `fs.writeFileSync()` and append-mode `fs.writeFile()` and `fs.writeFileSync()` under certain circumstances, reported in [#1058](https://github.com/nodejs/node/issues/1058), fixed in [#1063](https://github.com/nodejs/node/pull/1063) (Olov Lassus).
+* **iojs**: an "internal modules" API has been introduced to allow core code to share JavaScript modules internally only without having to expose them as a public API, this feature is for core-only [#848](https://github.com/nodejs/node/pull/848) (Vladimir Kurchatkin).
+* **timers**: two minor problems with timers have been fixed:
+  - `Timer#close()` is now properly idempotent [#1288](https://github.com/nodejs/node/issues/1288) (Petka Antonov).
+  - `setTimeout()` will only run the callback once now after an `unref()` during the callback [#1231](https://github.com/nodejs/node/pull/1231) (Roman Reiss).
+  - NOTE: there are still other unresolved concerns with the timers code, such as [#1152](https://github.com/nodejs/node/pull/1152).
+* **Windows**: a "delay-load hook" has been added for compiled add-ons on Windows that should alleviate some of the problems that Windows users may be experiencing with add-ons in io.js [#1251](https://github.com/nodejs/node/pull/1251) (Bert Belder).
+* **V8**: minor bug-fix upgrade for V8 to 4.1.0.27.
+* **npm**: upgrade npm to 2.7.4. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v274-2015-03-20) for details.
+
+### Known issues
+
+* Some problems exist with timers and `unref()` still to be resolved. See [#1152](https://github.com/nodejs/node/pull/1152).
+* Possible small memory leak(s) may still exist but have yet to be properly identified, details at [#1075](https://github.com/nodejs/node/issues/1075).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* Not possible to build io.js as a static library [#686](https://github.com/nodejs/node/issues/686)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+
+### Community Updates
+
+* [Scaleway](https://www.scaleway.com/) provides some ARM resources for the iojs test/build infrastructure.
+* New post on Medium about Node.js reconciliation: [Help us reconcile node.js and io.js](https://medium.com/node-js-javascript/help-us-reconcile-node-js-and-io-js-c060a9ec1bd4)
+* Added support for iojs in [Reactive-Extensions/RxJS](https://travis-ci.org/Reactive-Extensions/RxJS/builds/56671837)
+* [joyent/nodejs-advisory-board#30](https://github.com/joyent/nodejs-advisory-board/pull/30) merged
+* Mikeal Rogers working on reconciling Project Lifecycle and WG [joyent/nodejs-advisory-board#33](https://github.com/joyent/nodejs-advisory-board/pull/33)
+* Rod Vagg opened the discussion forum about Node.js reconciliation in [iojs/io.js#1336](https://github.com/nodejs/node/issues/1336)
+
+### Upcoming Events
+
+* [NodeConf](http://nodeconf.com/) tickets are on sale, June 8th and 9th at Oakland, CA and NodeConf Adventure for June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [nodeSchool tokyo](http://nodejs.connpass.com/event/13182/) will be held in April 12th at Tokyo, Japan
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-04-10.md b/locale/uk/blog/weekly-updates/weekly-update.2015-04-10.md
new file mode 100755
index 0000000000000..6b9b8ada8a20c
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-04-10.md
@@ -0,0 +1,42 @@
+---
+title: Weekly Update - Apr 10th, 2015
+author:  Giovanny Gioyik (@Gioyik) & Julian Duque (@julianduque)
+date: 2015-04-10T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-04-10
+layout: blog-post.hbs
+---
+
+# io.js 1.6.4 release
+This week we had one io.js release [v1.6.4](https://iojs.org/dist/v1.6.4/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+* **npm**: upgrade npm to 2.7.5. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v275-2015-03-26) for details. Includes two important security fixes.
+* **openssl**: preliminary work has been done for an upcoming upgrade to OpenSSL 1.0.2a [#1325](https://github.com/nodejs/node/pull/1325) (Shigeki Ohtsu). See [#589](https://github.com/nodejs/node/issues/589) for additional details.
+* **timers**: a minor memory leak when timers are unreferenced was fixed, alongside some related timers issues [#1330](https://github.com/nodejs/node/pull/1330) (Fedor Indutny). This appears to have fixed the remaining leak reported in [#1075](https://github.com/nodejs/node/issues/1075).
+* **android**: it is now possible to compile io.js for Android and related devices [#1307](https://github.com/nodejs/node/pull/1307) (Giovanny Andres Gongora Granada).
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* Not possible to build io.js as a static library [#686](https://github.com/nodejs/node/issues/686)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+
+### Community Updates
+
+* Node Foundation dev policy draft is [here](https://github.com/jasnell/dev-policy)
+* ARMv8 / ARM64 [support](https://twitter.com/rvagg/status/586050873349939201) on io.js
+* Continued work on a new dev policy for [node.js/io.js](https://github.com/jasnell/dev-policy)
+* TC call from [Wednesday](https://www.youtube.com/watch?v=OjlK8k10oyo)
+
+### Upcoming Events
+
+* [JSConf Uruguay](http://jsconf.uy) tickets are on sale, April 24th & 25th at Montevideo, Uruguay
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [nodeSchool Tokyo](http://nodejs.connpass.com/event/13182/) will be held in April 12th at Tokyo, Japan
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-04-17.md b/locale/uk/blog/weekly-updates/weekly-update.2015-04-17.md
new file mode 100755
index 0000000000000..c597afc86d73d
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-04-17.md
@@ -0,0 +1,47 @@
+---
+title: Weekly Update - Apr 17th, 2015
+author:  Giovanny Gioyik (@Gioyik)
+date: 2015-04-17T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-04-17
+layout: blog-post.hbs
+---
+
+
+# io.js 1.7 releases
+This week we had two io.js releases [v1.7.0](https://iojs.org/dist/v1.7.0/) and [v1.7.1](https://iojs.org/dist/v1.7.1/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+* **build**: A syntax error in the Makefile for release builds caused 1.7.0 to be DOA and unreleased. (Rod Vagg) [#1421](https://github.com/nodejs/node/pull/1421).
+* **C++ API**: Fedor Indutny contributed a feature to V8 which has been backported to the V8 bundled in io.js. `SealHandleScope` allows a C++ add-on author to _seal_ a `HandleScope` to prevent further, unintended allocations within it. Currently only enabled for debug builds of io.js. This feature helped detect the leak in [#1075](https://github.com/nodejs/node/issues/1075) and is now activated on the root `HandleScope` in io.js. (Fedor Indutny) [#1395](https://github.com/nodejs/node/pull/1395).
+* **ARM**: This release includes significant work to improve the state of ARM support for builds and tests. The io.js CI cluster's ARMv6, ARMv7 and ARMv8 build servers are now all (mostly) reporting passing builds and tests.
+  * ARMv8 64-bit (AARCH64) is now properly supported, including a backported fix in libuv that was mistakenly detecting the existence of `epoll_wait()`. (Ben Noordhuis) [#1365](https://github.com/nodejs/node/pull/1365).
+  * ARMv6: [#1376](https://github.com/nodejs/node/issues/1376) reported a problem with `Math.exp()` on ARMv6 (including Raspberry Pi). The culprit is erroneous codegen for ARMv6 when using the "fast math" feature of V8. `--nofast_math` has been turned on for all ARMv6 variants by default to avoid this, fast math can be turned back on with `--fast_math`. (Ben Noordhuis) [#1398](https://github.com/nodejs/node/pull/1398).
+  * Tests: timeouts have been tuned specifically for slower platforms, detected as ARMv6 and ARMv7. (Roman Reiss) [#1366](https://github.com/nodejs/node/pull/1366).
+* **npm**: Upgrade npm to 2.7.6. See the [release notes](https://github.com/npm/npm/releases/tag/v2.7.6) for details.
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* readline: split escapes are processed incorrectly, see [#1403](https://github.com/nodejs/node/issues/1403)
+
+### Community Updates
+
+* Difference between io.js and The Node Foundation [iojs/io.js#1416](https://github.com/nodejs/node/issues/1416).
+* NPM launches private modules and npm inc [raises](http://techcrunch.com/2015/04/14/popular-javascript-package-manager-npm-raises-8m-launches-private-modules/).
+* Thoughts of Node.js Foundation on [Medium](https://medium.com/@programmer/thoughts-on-node-foundation-abcf86c72786).
+* io.js v1.8.0 crypto performance on [io.js wiki](https://github.com/nodejs/node/wiki/Crypto-Performance-Notes-for-OpenSSL-1.0.2a-on-iojs-v1.8.0).
+* io.js mention on [Oracle's blog](https://blogs.oracle.com/java-platform-group/entry/node_js_and_io_js).
+* State of the io.js Build [April 2015](https://github.com/iojs/build/issues/77)
+
+### Upcoming Events
+
+* [JSConf Uruguay](http://jsconf.uy) tickets are on sale, April 24th & 25th at Montevideo, Uruguay
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-04-24.md b/locale/uk/blog/weekly-updates/weekly-update.2015-04-24.md
new file mode 100755
index 0000000000000..bc323f169db9d
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-04-24.md
@@ -0,0 +1,50 @@
+---
+title: Weekly Update - Apr 24th, 2015
+author:  Giovanny Gioyik (@Gioyik)
+date: 2015-04-24T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-04-24
+layout: blog-post.hbs
+---
+
+
+# io.js 1.8.1 release
+This week we had one io.js release [v1.8.1](https://iojs.org/dist/v1.8.1/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+* **NOTICE**: Skipped v1.8.0 due to problems with release tooling.
+  See [#1436](https://github.com/nodejs/node/issues/1436) for details.
+* **build**: Support for building io.js as a static library (Marat Abdullin) [#1341](https://github.com/nodejs/node/pull/1341)
+* **deps**: Upgrade openssl to 1.0.2a (Shigeki Ohtsu) [#1389](https://github.com/nodejs/node/pull/1389)
+  * Users should see performance improvements when using the crypto API.
+  See [here](https://github.com/nodejs/node/wiki/Crypto-Performance-Notes-for-OpenSSL-1.0.2a-on-iojs-v1.8.0)
+  for details.
+* **npm**: Upgrade npm to 2.8.3. See the [release notes](https://github.com/npm/npm/releases/tag/v2.8.3) for details. Includes improved git support.
+* **src**: Allow multiple arguments to be passed to process.nextTick (Trevor Norris) [#1077](https://github.com/nodejs/node/pull/1077)
+* **module**: The interaction of `require('.')` with `NODE_PATH` has been restored and deprecated. This functionality
+will be removed at a later point. (Roman Reiss) [#1363](https://github.com/nodejs/node/pull/1363)
+
+### Known issues
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* readline: split escapes are processed incorrectly, see [#1403](https://github.com/nodejs/node/issues/1403)
+
+### Community Updates
+
+* Fedor Indutny opened discussion about removing TLS `newSession` and `resumeSession` event. [iojs/io.js#1462](https://github.com/nodejs/node/issues/1462)
+* Proposal to change the C HTTP parser JS HTTP parser [here](https://github.com/nodejs/node/pull/1457)
+* NPM founder talks about io.js at [InfoWorld](http://www.infoworld.com/article/2910594/node-js/npm-founder-foresees-merger-node-js-io-js.html)
+* Proposal to add mikeal, mscdex, shigeki as new TC members. [iojs/io.js#1483](https://github.com/nodejs/node/issues/1483#issuecomment-95128140)
+
+### Upcoming Events
+
+* [JSConf Uruguay](http://jsconf.uy) tickets are on sale, April 24th & 25th at Montevideo, Uruguay
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-05-01.md b/locale/uk/blog/weekly-updates/weekly-update.2015-05-01.md
new file mode 100755
index 0000000000000..f883aa8e720ca
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-05-01.md
@@ -0,0 +1,35 @@
+---
+title: Weekly Update - May 1st, 2015
+author:  Giovanny Gioyik (@Gioyik)
+date: 2015-05-01T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-05-01
+layout: blog-post.hbs
+---
+
+# io.js 2.0 release candidate
+This week we had one io.js nightly release [v2.0](https://iojs.org/download/nightly/v2.0.0-nightly20150501b4ad5d7050/), complete changelog will be found soon [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Community Updates
+
+* New [johnny-five](http://johnny-five.io/) site launched.
+* iojs.io domain was donated to the project and it will redirect to iojs.org [iojs/io.js#1534](https://github.com/nodejs/node/issues/1534)
+* david-dm.org is [now running](https://twitter.com/_alanshaw/status/592855646124531713) on iojs
+* io.js v2.0 release candidate is [out](https://iojs.org/download/nightly/v2.0.0-nightly20150501b4ad5d7050/).
+* io.js [ARM cluster](https://twitter.com/rvagg/status/593226114992087041) is growing.
+* Onboarding another batch of committers [iojs/io.js#1552](https://github.com/nodejs/node/issues/1552)
+* io.js TC meeting 4/29 on [YouTube](https://www.youtube.com/watch?v=-e675TT4WEA) and [SoundCloud](https://twitter.com/dotproto/status/594145574204510208).
+* io.js/node.js code [convergence plan draft](https://github.com/jasnell/dev-policy/blob/master/convergence.md).
+* initial [repo](https://github.com/jasnell/node.js-convergence) for code convergence work for io.js/node.js.
+* Node.js Foundation Governance/Convergence Call on [YouTube](https://www.youtube.com/watch?v=u9h0s3YtNAU).
+* Microsoft releases new [Visual Studio Code](https://code.visualstudio.com/) based on Electron (AtomShell).
+* io.js support coming to [Modulus](http://blog.modulus.io/upcoming-updates-for-nodejs-applications)
+* Yosuke Furukawa created [iojs-new-features repo](https://github.com/yosuke-furukawa/iojs-new-features) with upcoming changes in io.js v2.0.
+
+### Upcoming Events
+
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-05-08.md b/locale/uk/blog/weekly-updates/weekly-update.2015-05-08.md
new file mode 100755
index 0000000000000..9c863b28a802c
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-05-08.md
@@ -0,0 +1,90 @@
+---
+title: Weekly Update - May 8th, 2015
+author: Giovanny Gioyik (@Gioyik) & Daijiro Wachi (@watilde)
+date: 2015-05-08T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-05-08
+layout: blog-post.hbs
+---
+
+# io.js 2.0 releases
+This week we had two io.js releases [v2.0.0](https://iojs.org/dist/v2.0.0/) and [v2.0.1](https://iojs.org/dist/v2.0.1/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable changes
+
+#### 2.0.1
+* **async_wrap**: (Trevor Norris) [#1614](https://github.com/nodejs/node/pull/1614)
+  - it is now possible to filter by providers
+  - bit flags have been removed and replaced with method calls on the binding object
+  - _note that this is an unstable API so feature additions and breaking changes won't change io.js semver_
+* **libuv**: resolves numerous io.js issues:
+  - [#862](https://github.com/nodejs/node/issues/862) prevent spawning child processes with invalid stdio file descriptors
+  - [#1397](https://github.com/nodejs/node/issues/1397) fix EPERM error with fs.access(W_OK) on Windows
+  - [#1621](https://github.com/nodejs/node/issues/1621) build errors associated with the bundled libuv
+  - [#1512](https://github.com/nodejs/node/issues/1512) should properly fix Windows termination errors
+* **addons**: the `NODE_DEPRECATED` macro was causing problems when compiling addons with older compilers, this should now be resolved (Ben Noordhuis) [#1626](https://github.com/nodejs/node/pull/1626)
+* **V8**: upgrade V8 from 4.2.77.18 to 4.2.77.20 with minor fixes, including a bug preventing builds on FreeBSD
+
+#### 2.0.0
+* **crypto**: significantly reduced memory usage for TLS (Fedor Indutny & Сковорода Никита Андреевич) [#1529](https://github.com/nodejs/node/pull/1529)
+* **net**: `socket.connect()` now accepts a `'lookup'` option for a custom DNS resolution mechanism, defaults to `dns.lookup()` (Evan Lucas) [#1505](https://github.com/nodejs/node/pull/1505)
+* **npm**: Upgrade npm to 2.9.0. See the [v2.8.4](https://github.com/npm/npm/releases/tag/v2.8.4) and [v2.9.0](https://github.com/npm/npm/releases/tag/v2.9.0) release notes for details. Notable items:
+  - Add support for default author field to make `npm init -y` work without user-input (@othiym23) [npm/npm/d8eee6cf9d](https://github.com/npm/npm/commit/d8eee6cf9d2ff7aca68dfaed2de76824a3e0d9af)
+  - Include local modules in `npm outdated` and `npm update` (@ArnaudRinquin) [npm/npm#7426](https://github.com/npm/npm/issues/7426)
+  - The prefix used before the version number on `npm version` is now configurable via `tag-version-prefix` (@kkragenbrink) [npm/npm#8014](https://github.com/npm/npm/issues/8014)
+* **os**: `os.tmpdir()` is now cross-platform consistent and will no longer returns a path with a trailing slash on any platform (Christian Tellnes) [#747](https://github.com/nodejs/node/pull/747)
+* **process**:
+  - `process.nextTick()` performance has been improved by between 2-42% across the benchmark suite, notable because this is heavily used across core (Brian White) [#1571](https://github.com/nodejs/node/pull/1571)
+  - New `process.geteuid()`, `process.seteuid(id)`, `process.getegid()` and `process.setegid(id)` methods allow you to get and set effective UID and GID of the process (Evan Lucas) [#1536](https://github.com/nodejs/node/pull/1536)
+* **repl**:
+  - REPL history can be persisted across sessions if the `NODE_REPL_HISTORY_FILE` environment variable is set to a user accessible file, `NODE_REPL_HISTORY_SIZE` can set the maximum history size and defaults to `1000` (Chris Dickinson) [#1513](https://github.com/nodejs/node/pull/1513)
+  - The REPL can be placed in to one of three modes using the `NODE_REPL_MODE` environment variable: `sloppy`, `strict` or `magic` (default); the new `magic` mode will automatically run "strict mode only" statements in strict mode (Chris Dickinson) [#1513](https://github.com/nodejs/node/pull/1513)
+* **smalloc**: the 'smalloc' module has been deprecated due to changes coming in V8 4.4 that will render it unusable
+* **util**: add Promise, Map and Set inspection support (Christopher Monsanto) [#1471](https://github.com/nodejs/node/pull/1471)
+* **V8**: upgrade to 4.2.77.18, see the [ChangeLog](https://chromium.googlesource.com/v8/v8/+/refs/heads/4.2.77/ChangeLog) for full details. Notable items:
+  - Classes have moved out of staging; the `class` keyword is now usable in strict mode without flags
+  - Object literal enhancements have moved out of staging; shorthand method and property syntax is now usable (`{ method() { }, property }`)
+  - Rest parameters (`function(...args) {}`) are implemented in staging behind the `--harmony-rest-parameters` flag
+  - Computed property names (`{['foo'+'bar']:'bam'}`) are implemented in staging behind the `--harmony-computed-property-names` flag
+  - Unicode escapes (`'\u{xxxx}'`) are implemented in staging behind the `--harmony_unicode` flag and the `--harmony_unicode_regexps` flag for use in regular expressions
+* **Windows**:
+  - Random process termination on Windows fixed (Fedor Indutny)  [#1512](https://github.com/nodejs/node/issues/1512) / [#1563](https://github.com/nodejs/node/pull/1563)
+  - The delay-load hook introduced to fix issues with process naming (iojs.exe / node.exe) has been made opt-out for native add-ons. Native add-ons should include `'win_delay_load_hook': 'false'` in their binding.gyp to disable this feature if they experience problems . (Bert Belder) [#1433](https://github.com/nodejs/node/pull/1433)
+* **Governance**:
+  - Rod Vagg (@rvagg) was added to the Technical Committee (TC)
+  - Jeremiah Senkpiel (@Fishrock123) was added to the Technical Committee (TC)
+
+### Breaking changes
+
+Full details at https://github.com/nodejs/node/wiki/Breaking-Changes#200-from-1x
+
+* V8 upgrade to 4.2, minor changes to C++ API
+* `os.tmpdir()` is now cross-platform consistent and will no longer returns a path with a trailling slash on any platform
+* While not a *breaking change* the 'smalloc' module has been deprecated in anticipation of it becoming unsupportable with a future upgrade to V8 4.4. See [#1451](https://github.com/nodejs/node/issues/1451)  for further information.
+
+_Note: a new version of the 'url' module was reverted prior to release as it was decided the potential for breakage across the npm ecosystem was too great and that more compatibility work needed to be done before releasing it. See [#1602](https://github.com/nodejs/node/pull/1602) for further information._
+
+### Known issues
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+* readline: split escapes are processed incorrectly, see [#1403](https://github.com/nodejs/node/issues/1403)
+
+### Community Updates
+
+* Michael Dawson creates [WG proposal](https://github.com/mhdawson/workgroup-proposals) under the Node Foundation.
+* Mikeal Rogers wrote about growing up of io.js [on Medium](https://medium.com/node-js-javascript/growing-up-27d6cc8b7c53).
+* CodeSchool [blog post](https://www.codeschool.com/blog/2015/05/08/whats-new-in-io-js-2-0-0/) on what's new in io.js 2.0.
+* Node Lead TJ Fontaine [steps back](http://blog.nodejs.org/2015/05/08/next-chapter/) from leader.
+
+### Upcoming Events
+
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-05-15.md b/locale/uk/blog/weekly-updates/weekly-update.2015-05-15.md
new file mode 100755
index 0000000000000..9272d459cee3d
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-05-15.md
@@ -0,0 +1,34 @@
+---
+title: Weekly Update - May 15th, 2015
+author: Giovanny Gioyik (@Gioyik) & Takashi Fujita (@tgfjt)
+date: 2015-05-15T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-05-15
+layout: blog-post.hbs
+---
+
+# io.js News
+
+We are happy to announce this news, **"io.js decides to join the Node Foundation"**. And our organization name will be renamed `nodejs`.
+
+As a first step, we will move from `iojs` organization to `nodejs` organization and will converge `joyent/node` gradually. We will continue to release `io.js` until the convergence have done.
+
+If you would like to see the convergence plan in detail, please check it at [jasnell repo](https://github.com/jasnell/dev-policy/blob/master/convergence.md). When you would like to ask questions, feel free to ask [@Fishrock123](mailto:fishrock123@rocketmail.com). The discussion log is [here](https://github.com/nodejs/node/issues/1664).
+
+### Community Updates
+
+* [Performance Showdown](https://raygun.io/blog/2015/05/performance-showdown-node-js-vs-io-js-v2-0-0/): Node.js vs. io.js v2.0.0.
+* Microsoft has [node.js](https://github.com/Microsoft/node) running on their JavaScript VM `Chakra`.
+* {node,io}.js [benchmark graphs](http://thlorenz.com/benchgraph/).
+* [TC members](https://twitter.com/rvagg/status/598605393636429825) decide to move io.js to Node Foundation and the organization name will be renamed nodejs.
+* Hardware WG Meeting on [YouTube](https://www.youtube.com/watch?v=EFJVMGRtDWE).
+* `io.js/node.js` Build Convergence Meeting on [YouTube](https://www.youtube.com/watch?v=8dxkM9vHmrY).
+* TC Meeting on [YouTube](https://www.youtube.com/watch?v=UbYiFLf7MpU).
+
+### Upcoming Events
+
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-05-22.md b/locale/uk/blog/weekly-updates/weekly-update.2015-05-22.md
new file mode 100755
index 0000000000000..0d6ff1f053db6
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-05-22.md
@@ -0,0 +1,64 @@
+---
+title: Weekly Update - May 22nd, 2015
+author: Giovanny Gioyik (@Gioyik) & Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-05-22T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-05-22
+layout: blog-post.hbs
+---
+
+# io.js 1.8, 2.0 and 2.1 releases
+This week we had three io.js releases [v1.8.2](https://iojs.org/dist/v1.8.2/), [v2.0.2](https://iojs.org/dist/v2.0.2/) and [v2.1.0](https://iojs.org/dist/v2.1.0/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+#### 1.8.2
+
+**Maintenance release**
+
+* **crypto**: significantly reduced memory usage for TLS (Fedor Indutny & Сковорода Никита Андреевич) [#1529](https://github.com/nodejs/node/pull/1529)
+* **npm**: Upgrade npm to 2.9.0. See the [v2.8.4](https://github.com/npm/npm/releases/tag/v2.8.4) and [v2.9.0](https://github.com/npm/npm/releases/tag/v2.9.0) release notes for details.
+
+#### 2.0.2
+
+* **win,node-gyp**: the delay-load hook for windows addons has now been correctly enabled by default, it had wrongly defaulted to off in the release version of 2.0.0 (Bert Belder) [#1433](https://github.com/nodejs/node/pull/1433)
+* **os**: `tmpdir()`'s trailing slash stripping has been refined to fix an issue when the temp directory is at '/'. Also considers which slash is used by the operating system. (cjihrig) [#1673](https://github.com/nodejs/node/pull/1673)
+* **tls**: default ciphers have been updated to use gcm and aes128 (Mike MacCana) [#1660](https://github.com/nodejs/node/pull/1660)
+* **build**: v8 snapshots have been re-enabled by default as suggested by the v8 team, since prior security issues have been resolved. This should give some perf improvements to both startup and vm context creation. (Trevor Norris) [#1663](https://github.com/nodejs/node/pull/1663)
+* **src**: fixed preload modules not working when other flags were used before `--require` (Yosuke Furukawa) [#1694](https://github.com/nodejs/node/pull/1694)
+* **dgram**: fixed `send()`'s callback not being asynchronous (Yosuke Furukawa) [#1313](https://github.com/nodejs/node/pull/1313)
+* **readline**: emitKeys now keeps buffering data until it has enough to parse. This fixes an issue with parsing split escapes. (Alex Kocharin) [#1601](https://github.com/nodejs/node/pull/1601)
+* **cluster**: works now properly emit 'disconnect' to `cluster.worker` (Oleg Elifantiev) [#1386](https://github.com/nodejs/node/pull/1386)
+* **events**: uncaught errors now provide some context (Evan Lucas) [#1654](https://github.com/nodejs/node/pull/1654)
+
+#### 2.1.0
+
+* **crypto**: Diffie-Hellman key exchange (DHE) parameters (`'dhparams'`) must now be 1024 bits or longer or an error will be thrown. A warning will also be printed to the console if you supply less than 2048 bits. See https://weakdh.org/ for further context on this security concern (Shigeki Ohtsu) [#1739](https://github.com/nodejs/node/pull/1739).
+* **node**: A new `--trace-sync-io` command line flag will print a warning and a stack trace whenever a synchronous API is used. This can be used to track down synchronous calls that may be slowing down an application (Trevor Norris) [#1707](https://github.com/nodejs/node/pull/1707).
+* **node**: To allow for chaining of methods, the `setTimeout()`, `setKeepAlive()`, `setNoDelay()`, `ref()` and `unref()` methods used in `'net'`, `'dgram'`, `'http'`, `'https'` and `'tls'` now return the current instance instead of `undefined` (Roman Reiss & Evan Lucas) [#1699](https://github.com/nodejs/node/pull/1699) [#1768](https://github.com/nodejs/node/pull/1768) [#1779](https://github.com/nodejs/node/pull/1779).
+* **npm**: Upgraded to v2.10.1, release notes can be found in <https://github.com/npm/npm/releases/tag/v2.10.1> and <https://github.com/npm/npm/releases/tag/v2.10.0>.
+* **util**: A significant speed-up (in the order of 35%) for the common-case of a single string argument to `util.format()`, used by `console.log()` (Сковорода Никита Андреевич) [#1749](https://github.com/nodejs/node/pull/1749).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* Mikeal Rogers post about **Promise errors in io.js** on [Modulus.io](http://blog.modulus.io/promise-errors-in-iojs)
+* [NodeSchool International Day](http://nodeschool.io/international-day/) has been held for the first time. [40 cities](https://github.com/nodeschool/international-day/issues?q=label%3Arollcall-2015+is%3Aclosed) joined.
+* [Logjam](https://weakdh.org/) attack vulnerability detected on Diffie-Hellman Key exchange. io.js [fixed the vulnerability](https://github.com/nodejs/node/pull/1739) on [v2.1.0](https://github.com/nodejs/node/blob/master/CHANGELOG.md#2015-05-24-version-210-rvagg).
+
+### Upcoming Events
+
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-05-29.md b/locale/uk/blog/weekly-updates/weekly-update.2015-05-29.md
new file mode 100755
index 0000000000000..62407987c078b
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-05-29.md
@@ -0,0 +1,51 @@
+---
+title: Weekly Update - May 29th, 2015
+author: Giovanny Gioyik (@Gioyik)
+date: 2015-05-29T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-05-29
+layout: blog-post.hbs
+---
+
+# io.js 2.2 releases
+This week we had two io.js releases [v2.2.0](https://iojs.org/dist/v2.2.0/) and [v2.2.1](https://iojs.org/dist/v2.2.1/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+#### v2.2.0
+
+* **node**: Speed-up `require()` by replacing usage of `fs.statSync()` and `fs.readFileSync()` with internal variants that are faster for this use-case and do not create as many objects for the garbage collector to clean up. The primary two benefits are: significant increase in application start-up time on typical applications and better start-up time for the debugger by eliminating almost all of the thousands of exception events. (Ben Noordhuis) [#1801](https://github.com/nodejs/node/pull/1801).
+* **node**: Resolution of pre-load modules (`-r` or `--require`) now follows the standard `require()` rules rather than just resolving paths, so you can now pre-load modules in node_modules. (Ali Ijaz Sheikh) [#1812](https://github.com/nodejs/node/pull/1812).
+* **npm**: Upgraded npm to v2.11.0. New hooks for `preversion`, `version`, and `postversion` lifecycle events, some SPDX-related license changes and license file inclusions. See the [release notes](https://github.com/npm/npm/releases/tag/v2.11.0) for full details.
+
+#### v2.2.1
+
+* **http**: reverts the removal of an undocumented `client` property on client connections, this property is being used in the wild, most notably by [request](https://github.com/request/request) which is used by npm. (Michaël Zasso) [#1852](https://github.com/nodejs/node/pull/1852).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* [Schism and Reconciliation](https://nodesource.com/blog/was-this-trip-really-necessary) in the Node Community by Rod Vagg.
+* First Node TSC Meeting available on [SoundCloud](https://soundcloud.com/node-foundation/tsc-meeting-2015-05-27).
+* io.js have got a new Benchmarking Working Group [nodejs/benchmarking#1](https://github.com/nodejs/benchmarking/issues/1).
+* Blog post about iojs + node.js under Node Foundation by [nodejs.com](http://blog.nodejs.org/2015/05/15/the-nodejs-foundation-benefits-all/).
+* io.js implements new [`good first contribution`](https://github.com/nodejs/node/labels/good%20first%20contribution) tag for new contributors.
+* Blog post from [TheNewStack](http://thenewstack.io/io-js-and-node-js-have-united-and-thats-a-good-thing/) about iojs and node.js new relation.
+* Oliver Zeigermann created a [repo](https://github.com/DJCordhose/ecmascript-2015-iojs) about ES6 and iojs implementation.
+
+### Upcoming Events
+
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-06-05.md b/locale/uk/blog/weekly-updates/weekly-update.2015-06-05.md
new file mode 100755
index 0000000000000..b0631b76fe126
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-06-05.md
@@ -0,0 +1,26 @@
+---
+title: Weekly Update - Jun 5th, 2015
+author: Giovanny Gioyik (@Gioyik)
+date: 2015-06-05T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-06-05
+layout: blog-post.hbs
+---
+
+# io.js News
+This week we hadn't io.js releases, complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Community Updates
+
+* [Marius.co](https://twitter.com/edatrero/status/605040698992164864) switches to io.js from Node 0.10
+* Up and running with io.js and Docker by [CodeFresh.io](http://blog.codefresh.io/up-and-running-with-io-js-and-docker/)
+* New PluralSight course: [io.js](http://www.marcusoft.net/2015/06/new-pluralsight-course-iojs-or-is-it.html)
+* StrongLoop article: [New io.js Features You May Not Be Using](https://strongloop.com/strongblog/new-io-js-features-you-may-not-be-using/)
+
+### Upcoming Events
+
+* [NodeConf Adventure](http://nodeconf.com/) tickets are on sale, June 11th - 14th at Walker Creek Ranch, CA
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-06-12.md b/locale/uk/blog/weekly-updates/weekly-update.2015-06-12.md
new file mode 100755
index 0000000000000..530d3e6acce9a
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-06-12.md
@@ -0,0 +1,58 @@
+---
+title: Weekly Update - Jun 12th, 2015
+author: Giovanny Gioyik (@Gioyik)
+date: 2015-06-12T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-06-12
+layout: blog-post.hbs
+---
+
+# io.js 2.3 releases
+This week we had one io.js release [v2.3.0](https://iojs.org/dist/v2.3.0/), complete changelog can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **libuv**: Upgraded to 1.6.0 and 1.6.1, see [full ChangeLog](https://github.com/libuv/libuv/blob/60e515d9e6f3d86c0eedad583805201f32ea3aed/ChangeLog#L1-L36) for details. (Saúl Ibarra Corretgé) [#1905](https://github.com/nodejs/node/pull/1905) [#1889](https://github.com/nodejs/node/pull/1889). Highlights include:
+  - Fix TTY becoming blocked on OS X
+  - Fix UDP send callbacks to not to be synchronous
+  - Add `uv_os_homedir()` (exposed as `os.homedir()`, see below)
+* **npm**: See full [release notes](https://github.com/npm/npm/releases/tag/v2.11.1) for details. (Kat Marchán) [#1899](https://github.com/nodejs/node/pull/1899). Highlight:
+  - Use GIT_SSH_COMMAND (available as of Git 2.3)
+* **openssl**:
+  - Upgrade to 1.0.2b and 1.0.2c, introduces DHE man-in-the-middle protection (Logjam) and fixes malformed ECParameters causing infinite loop (CVE-2015-1788). See the [security advisory](https://www.openssl.org/news/secadv_20150611.txt) for full details. (Shigeki Ohtsu) [#1950](https://github.com/nodejs/node/pull/1950) [#1958](https://github.com/nodejs/node/pull/1958)
+  - Support [FIPS](https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards) mode of OpenSSL, see [README](https://github.com/nodejs/node#building-iojs-with-fips-compliant-openssl) for instructions. (Fedor Indutny) [#1890](https://github.com/nodejs/node/pull/1890)
+* **os**: Add `os.homedir()` method. (Colin Ihrig) [#1791](https://github.com/nodejs/node/pull/1791)
+* **smalloc**: Deprecate whole module. (Vladimir Kurchatkin) [#1822](https://github.com/nodejs/node/pull/1822)
+* Add new collaborators:
+  - Alex Kocharin ([@rlidwka](https://github.com/rlidwka))
+  - Christopher Monsanto ([@monsanto](https://github.com/monsanto))
+  - Ali Ijaz Sheikh ([@ofrobots](https://github.com/ofrobots))
+  - Oleg Elifantiev ([@Olegas](https://github.com/Olegas))
+  - Domenic Denicola ([@domenic](https://github.com/domenic))
+  - Rich Trott ([@Trott](https://github.com/Trott))
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* Openssl vulnerabilities are updated on io.js. **Resume:** *Upgrade to 1.0.2b and 1.0.2c, introduces DHE man-in-the-middle protection (Logjam) and fixes malformed ECParameters causing infinite loop (CVE-2015-1788). See the security advisory for full details. (Shigeki Ohtsu) #1950 #1958*
+* io.js 2.3.0 os.homedir() [ponyfill](http://t.co/2XQV5XQblu)
+* ["Should I use Node.js or io.js? And which version?"](https://strongloop.com/strongblog/should-i-use-node-js-or-io-js-and-which-version/) article by StrongLoop
+* iojs now supports [`--use_strong`](https://t.co/4t1EaiiK27). Strong mode (part of Google v8 experiments) implements a stronger semantics.
+* ["Node.js and io.js Merge Under the Node Foundation"](http://www.infoq.com/news/2015/05/nodejs-iojs#.VX41fCR99Kc.twitter) by InfoQ.
+
+### Upcoming Events
+
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-06-19.md b/locale/uk/blog/weekly-updates/weekly-update.2015-06-19.md
new file mode 100755
index 0000000000000..8f77dc1a7b209
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-06-19.md
@@ -0,0 +1,54 @@
+---
+title: Weekly Update - Jun 19th, 2015
+author: Giovanny Gioyik (@Gioyik)
+date: 2015-06-19T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-06-19
+layout: blog-post.hbs
+---
+
+# io.js and Node.js News
+This week we didn't have io.js releases, complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Community Updates
+
+* ES2015 is approved, ES2015 is now an [ecma standard](https://esdiscuss.org/topic/ecmascript-2015-is-now-an-ecma-standard).
+* Linux foundation announces [Node.js Foundation](http://www.linuxfoundation.org/news-media/announcements/2015/06/nodejs-foundation-advances-community-collaboration-announces-new)
+* IBM VP Angel Diaz talks about the new Node.js Foundation. Video on [YouTube](https://www.youtube.com/watch?v=9iuqi8c91mg&feature=youtu.be)
+* Blog post by Raymond Camden: [Using Cloud Code, Mobile Application Security, Node.js and Bluemix](http://www.raymondcamden.com/2015/06/09/using-cloud-code-mobile-application-security-node-js-and-bluemix)
+* [Deploying Multiple Node.js Apps with strong-pm.io](https://strongloop.com/strongblog/deploying-multiple-node-js-apps-with-strong-pm-io/) article by Strongloop
+* [How to Implement Node + React Isomorphic JavaScript & Why it Matters](https://strongloop.com/strongblog/node-js-react-isomorphic-javascript-why-it-matters/) article by Strongloop
+* [The smartest way to program smart things: Node.js](http://radar.oreilly.com/2015/06/the-smartest-way-to-program-smart-things-node-js.html) article on O'Reilly Radar by Leah Hunter
+* Blog post by Sebastian Seilund: [Node.js async in practice: When to use what?](http://www.sebastianseilund.com/nodejs-async-in-practice)
+* [Not Really Single Page Apps](http://dailyjs.com/2015/06/19/not-really-single-page-apps/) blog post on DailyJS
+* [Containerizing Node.js Apps with Docker and StrongLoop](https://strongloop.com/strongblog/containerizing-node-js-apps-with-docker-and-strongloop/) article by Strongloop
+* [Built in Node.js](http://builtinnode.com/): startups, apps, projects using Node
+* Interview in [Free Software Magazine](http://www.freesoftwaremagazine.com/articles/interview_mikeal_rogers_nodejs_fork_ended_giant_unifying_step_forward) about the merge and the foundation
+* [Why Node.js is hitting the big time in Enterprise Markets](http://apmblog.dynatrace.com/2015/04/09/node-js-is-hitting-the-big-time-in-enterprise-markets/) and [Keeping things simple with Node.js](http://apmblog.dynatrace.com/2015/06/02/keeping-things-simple-with-node-js/) articles by Daniel Khan
+* Blog post by Paul Sauve: [Comparing NodeJS IDEs (now with ST3 and WebStorm!)](https://paulb.gd/comparing-nodejs-ides/)
+* [Understanding npm](https://unpm.nodesource.com/) and [blog post](https://medium.com/@nodesource/npm-is-massive-2bdd9417591c) about it by Nodesource.
+* [Node.js High Availability](https://www.box.com/blog/node-js-high-availability-at-box/) article by Box
+* Deploying a Scalable Node.js Application with Docker by Nodevember. Video on [YouTube](https://www.youtube.com/watch?v=uhNpSWI8MTM)
+* [Top 10 Reasons To Use Node.js](http://blog.modulus.io/top-10-reasons-to-use-node) article by Modulus.io
+* [Painless Microsoft SQL Server with Node.js and seriate](http://developer.leankit.com/painless-sql-server-with-nodejs-and-seriate/) article by Leankit
+* Blog post: [Golden rules for JS introduction to your EE project](http://blog.upwardsmotion.com/golden-rules-for-js-introduction-to-your-ee-project/)
+* [The State of Node in the Enterprise](https://medium.com/@nodesource/the-state-of-node-in-the-enterprise-e513fbc0bdc) by Rod Vagg
+* Organizations joining the Node.js Foundation:
+  * [Modulus/Progress](http://blog.modulus.io/modulus-and-progress-software-join-nodejs-foundation)
+  * [IBM](https://developer.ibm.com/bluemix/2015/06/16/node-js-foundation-launched/)
+  * [Groupon](https://engineering.groupon.com/2015/node-js/groupon-is-proud-to-be-a-part-of-the-new-node-js-foundation/)
+  * [NodeSource](https://nodesource.com/blog/nodesource-to-join-the-nodejs-foundation)
+  * [Famous Industries](https://blog.famous.org/famous-industries-joins-the-node-foundation/)
+  * [Nearform](http://www.nearform.com/nodecrunch/thanks-everybody-making-node-foundation-happen/)
+  * [Strongloop](https://strongloop.com/strongblog/announcing-the-node-js-foundation/)
+  * [GoDaddy](https://garage.godaddy.com/godaddy/godaddy-supports-the-new-node-js-foundation/)
+  * [Microsoft](http://blogs.microsoft.com/firehose/2015/02/11/microsoft-joins-industry-to-create-node-js-foundation/)
+
+### Upcoming Events
+
+* [Nodeday](http://nodeday.com) tickets are free, June 26th at DigitasLBi, London
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-06-26.md b/locale/uk/blog/weekly-updates/weekly-update.2015-06-26.md
new file mode 100755
index 0000000000000..15053a198c677
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-06-26.md
@@ -0,0 +1,47 @@
+---
+title: Weekly Update - Jun 26th, 2015
+author: Giovanny Gioyik (@Gioyik)
+date: 2015-06-26T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-06-26
+layout: blog-post.hbs
+---
+
+# io.js and Node.js News
+This week we have one io.js [release v2.3.1](https://github.com/nodejs/node/blob/master/CHANGELOG.md#2015-06-23-version-231-rvagg), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **module**: The number of syscalls made during a `require()` have been significantly reduced again (see [#1801](https://github.com/nodejs/node/pull/1801) from v2.2.0 for previous work), which should lead to a performance improvement (Pierre Inglebert) [#1920](https://github.com/nodejs/node/pull/1920).
+* **npm**:
+  * Upgrade to [v2.11.2](https://github.com/npm/npm/releases/tag/v2.11.2) (Rebecca Turner) [#1956](https://github.com/nodejs/node/pull/1956).
+  * Upgrade to [v2.11.3](https://github.com/npm/npm/releases/tag/v2.11.3) (Forrest L Norvell) [#2018](https://github.com/nodejs/node/pull/2018).
+* **zlib**: A bug was discovered where the process would abort if the final part of a zlib decompression results in a buffer that would exceed the maximum length of `0x3fffffff` bytes (~1GiB). This was likely to only occur during buffered decompression (rather than streaming). This is now fixed and will instead result in a thrown `RangeError` (Michaël Zasso) [#1811](https://github.com/nodejs/node/pull/1811).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760) and fix in [#774](https://github.com/nodejs/node/issues/774)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* Slide deck: [Bluemix Webinar: Deploying a Full Stack Node.js Application to IBM Bluemix](https://speakerdeck.com/bradleyholt/bluemix-webinar-deploying-a-full-stack-node-dot-js-application-to-ibm-bluemix)
+* Article by RisingStack: [How to Use Rust with Node.js When Performance Matters](http://blog.risingstack.com/how-to-use-rust-with-node-when-performance-matters/)
+* Device Atlas API now [supports Node.js](https://deviceatlas.com/blog/deviceatlas-api-node-js?utm_source=twitter&utm_medium=update&utm_campaign=node%20js%20support)
+* [On Maintaining a Native Node Module](http://www.voodootikigod.com/on-maintaining-a-native-node-module/) by Chris Williams
+* [nodei.co](http://twitter.com/rvagg/status/613688739030679552) is running with io.js
+* npm [3.0.0 pre-release](https://github.com/npm/npm/releases/tag/v3.0.0)
+
+### Upcoming Events
+
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-07-03.md b/locale/uk/blog/weekly-updates/weekly-update.2015-07-03.md
new file mode 100755
index 0000000000000..97f24bb73c0f2
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-07-03.md
@@ -0,0 +1,61 @@
+---
+title: Weekly Update - Jul 3rd, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-07-03T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-07-03
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — July 3rd
+Important patches for io.js 1.8 and 2.3 and upcoming events.
+
+### io.js 1.8 and 2.3 Releases
+
+This week we have three io.js releases: [v2.3.2](https://iojs.org/dist/v2.3.2/) and two following important security patches [v1.8.3](https://iojs.org/dist/v1.8.3/) and [v2.3.3](https://iojs.org/dist/v2.3.3/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md) with the [v1.x changelog here](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable Changes
+
+#### 1.8.3
+
+**Maintenance release**
+
+* **v8**: Fixed an out-of-band write in utf8 decoder. **This is an important security update** as it can be used to cause a denial of service attack.
+* **openssl**: Upgrade to 1.0.2b and 1.0.2c, introduces DHE man-in-the-middle protection (Logjam) and fixes malformed ECParameters causing infinite loop (CVE-2015-1788). See the [security advisory](https://www.openssl.org/news/secadv_20150611.txt) for full details. (Shigeki Ohtsu) [#1950](https://github.com/nodejs/node/pull/1950) [#1958](https://github.com/nodejs/node/pull/1958)
+* **build**:
+  * Added support for compiling with Microsoft Visual C++ 2015
+  * Started building and distributing headers*only tarballs along with binaries
+
+#### 2.3.2
+
+* **build**:
+  * Added support for compiling with Microsoft Visual C++ 2015
+  * Started building and distributing headers-only tarballs along with binaries
+
+#### 2.3.3
+
+* **deps**: Fixed an out-of-band write in utf8 decoder. **This is an important security update** as it can be used to cause a denial of service attack.
+
+### Known Issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* Yosuke Furukawa will give a talk about the past, present, and future of Node.js in [YAPC Asia 2015](http://yapcasia.org/2015/), the largest conference in Japan's programming community. It will be hosted at Tokyo on August 20th - 22nd and his talk will specifically be on the 22nd. Details of the talk can be found [here](http://yapcasia.org/2015/talk/show/82e93a96-f60e-11e4-907e-8ab37d574c3a).
+* A security issue is found in v8 that can be used for DoS attacks against Node.js applications and servers running 0.12 and all versions of io.js. Critical security upgrades ([Node.js v0.12.6](https://nodejs.org/dist/v0.12.6/), [io.js 2.3.3](https://iojs.org/dist/v2.3.3/) and [io.js 1.8.3](https://iojs.org/dist/v1.8.3/)) have been released. Also, details about the issue can be found [on one of our Medium post](https://medium.com/@iojs/important-security-upgrades-for-node-js-and-io-js-8ac14ece5852). If you're running v1.8.2 or below, or v2.3.2 or below, please update them to io.js versions 1.8.3 and 2.3.3.
+
+### Upcoming Events
+
+* [CascadiaJS](http://2015.cascadiajs.com/) tickets are on sale, July 8th - 10th at Washington State
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-07-10.md b/locale/uk/blog/weekly-updates/weekly-update.2015-07-10.md
new file mode 100755
index 0000000000000..d9bd2e3e026d2
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-07-10.md
@@ -0,0 +1,53 @@
+---
+title: Weekly Update - Jul 10th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-07-10T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-07-10
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — July 10th
+Security patches for io.js 1.8 and 2.3 and upcoming events.
+
+### io.js 1.8 and 2.3 Releases
+
+This week we have two io.js releases: [v2.3.4](https://iojs.org/dist/v2.3.4/) and [v1.8.4](https://iojs.org/dist/v1.8.4/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md) with the [v1.x changelog here](https://github.com/nodejs/node/blob/v1.x/CHANGELOG.md).
+
+### Notable Changes
+
+#### 1.8.4
+
+**Maintenance release**
+
+* **openssl**: Upgrade to 1.0.2d, fixes CVE-2015-1793 (Alternate Chains Certificate Forgery) [#2141](https://github.com/nodejs/node/pull/2141).
+
+
+#### 2.3.4
+
+* **openssl**: Upgrade to 1.0.2d, fixes CVE-2015-1793 (Alternate Chains Certificate Forgery) (Shigeki Ohtsu) [#2141](https://github.com/nodejs/node/pull/2141).
+* **npm**: Upgraded to v2.12.1, release notes can be found in <https://github.com/npm/npm/releases/tag/v2.12.0> and <https://github.com/npm/npm/releases/tag/v2.12.1> (Kat Marchán) [#2112](https://github.com/nodejs/node/pull/2112).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* OpenSSL published a [high severity security issue](https://mta.openssl.org/pipermail/openssl-announce/2015-July/000037.html), io.js and Node.js have upgraded OpenSSL version and fixed the problem on latest version.
+* Node.js LTS WG has updated [their proposed LTS plan](https://github.com/nodejs/LTS/blob/master/README.md#example). They need some feedbacks from Noders.
+* ReactNative required io.js as [their test platform](https://github.com/facebook/react-native/blob/master/.travis.yml#L24).
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-07-17.md b/locale/uk/blog/weekly-updates/weekly-update.2015-07-17.md
new file mode 100755
index 0000000000000..3dbf0ca7d307d
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-07-17.md
@@ -0,0 +1,48 @@
+---
+title: Weekly Update - Jul 17th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-07-17T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-07-17
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — July 17th
+io.js 2.4.0 is released, Apigee joined our foundation and Intl WG start.
+
+### io.js 2.4 Release
+
+This week we have one io.js release: [v2.4.0](https://iojs.org/dist/v2.4.0/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable Changes
+
+#### 2.4.0
+
+* **src**: Added a new `--track-heap-objects` flag to track heap object allocations for heap snapshots (Bradley Meck) [#2135](https://github.com/nodejs/node/pull/2135).
+* **readline**: Fixed a freeze that affected the repl if the keypress event handler threw (Alex Kocharin) [#2107](https://github.com/nodejs/node/pull/2107).
+* **npm**: Upgraded to v2.13.0, release notes can be found in <https://github.com/npm/npm/releases/tag/v2.13.0> (Forrest L Norvell) [#2152](https://github.com/nodejs/node/pull/2152).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* NodeSource announces N|Support on [their blog post](https://nodesource.com/blog/nodesource-announces-nsupport). N|Support is a premium support offering for Node.js developers, DevOps and IT operations teams. To learn more about N|Support offerings, check out [the solution page](https://nodesource.com/products/nsupport).
+* [Apigee](https://apigee.com/) is [added to the Node Foundation](https://github.com/nodejs/nodejs.org/pull/151)
+* [joyent/docker-node](https://github.com/joyent/docker-node) team is moved to [nodejs/docker](https://github.com/nodejs/docker-iojs) team. As a result, [@chorrell](https://github.com/chorrell) and [@dcrudgington](https://github.com/dcrudgington) joined [@nodejs/docker](https://github.com/orgs/nodejs/teams/docker) team.
+* [Intl](https://github.com/nodejs/intl) WG is launched. They are dedicated to support and improvement of Internationalization and Localization in Node. Intl WG calls for participants in [their issue](https://github.com/nodejs/Intl/issues/5).
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-07-24.md b/locale/uk/blog/weekly-updates/weekly-update.2015-07-24.md
new file mode 100755
index 0000000000000..e61a3c627db31
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-07-24.md
@@ -0,0 +1,24 @@
+---
+title: Weekly Update - Jul 24th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa) & Steven Sinatra (@diagramatics)
+date: 2015-07-24T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-07-24
+layout: blog-post.hbs
+---
+
+# io.js and Node.js News
+This week we didn't have io.js releases. Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Community Updates
+
+* Rod Vagg posted [an article about Node.js LTS](https://medium.com/@nodesource/essential-steps-long-term-support-for-node-js-8ecf7514dbd) on nodesource blog.
+* Daniel Khan has written a blog post about [NODE_ENV in Express](http://apmblog.dynatrace.com/2015/07/22/the-drastic-effects-of-omitting-node_env-in-your-express-js-applications/).
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-07-31.md b/locale/uk/blog/weekly-updates/weekly-update.2015-07-31.md
new file mode 100755
index 0000000000000..45f96038dce72
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-07-31.md
@@ -0,0 +1,49 @@
+---
+title: Weekly Update - Jul 31st, 2015
+author: Steven Sinatra (@diagramatics)
+date: 2015-07-31T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-07-31
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — July 31st
+io.js v2.5.0 and our call for an LTS build V8 maintainer.
+
+### io.js 2.5 Release
+
+This week we have released io.js [v2.5.0](https://iojs.org/dist/v2.5.0/). The complete changelog for this version and previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **https**: TLS sessions in Agent are reused (Fedor Indutny) [#2228](https://github.com/nodejs/node/pull/2228)
+* **src**: base64 decoding is now 50% faster (Ben Noordhuis) [#2193](https://github.com/nodejs/node/pull/2193)
+* **npm**: Upgraded to v2.13.2, release notes can be found in <https://github.com/npm/npm/releases/tag/v2.13.2> (Kat Marchán) [#2241](https://github.com/nodejs/node/pull/2241).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* We need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* [Milo Mordaunt](https://twitter.com/bananaoomarang) has written about [extending IFTTT with Webtask.io running Node.js code](https://auth0.com/blog/2015/07/28/if-this-then-node-dot-js-extending-ifttt-with-webtask-dot-io/?utm_source=io.js+and+Node.js+News&utm_medium=article) over on [Auth0](https://auth0.com/blog).
+* [Hemanth.HM](https://twitter.com/gnumanth), an author and contributor of more than 200 modules on npm, has written about [authoring Node modules](http://h3manth.com/new/blog/2015/authoring-node-modules/?utm_source=io.js+and+Node.js+News&utm_medium=article).
+
+If you have spotted or written something about Node.js and io.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
+
+Have an event about Node.js and io.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-08-07.md b/locale/uk/blog/weekly-updates/weekly-update.2015-08-07.md
new file mode 100755
index 0000000000000..bbe10d5502640
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-08-07.md
@@ -0,0 +1,91 @@
+---
+title: Weekly Update - Aug 7th, 2015
+author: Steven Sinatra (@diagramatics)
+date: 2015-08-07T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-08-07
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — August 7th
+io.js v3.0 and the new goodness, breaking changes, and our ongoing call for an LTS build V8 maintainer.
+
+### io.js v3.0 Release
+
+This week, io.js [v3.0.0](https://iojs.org/dist/v3.0.0/) is released! Since this is a major version bump, new features have been introduced to io.js. These are:
+- V8 upgrade from v4.2 to v4.4. Rod Vagg ([@rvagg](http://twitter.com/rvagg)) has [a Gist containing the changelogs of v4.3 and v4.4](https://gist.github.com/rvagg/1f115074cb3c890985bf).
+- Computed property names (`{['foo'+'bar']:'bam'}`) is now shipped without the need for any `harmony-` flag.
+- Unicode escape sequence (`\u{xxxxx}`) is also shipped. There is no need for the `--harmony` option anymore.
+- Previously classes are available but built-in Array subclasses are not supported or [problematic](https://code.google.com/p/v8/issues/detail?can=2&q=3930&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Area%20Stars&id=3930). The new version of V8 has solved this problem.
+- The spread operator (`...`) is supported with the `--es-staging` flag. This allows you to use it in places where multiple arguments (for function calls) or multiple elements (for array literals) are expected.
+- The Rest parameters (`function(...args) {}`) are implemented behind the `--es-staging` flag as well.
+- REPL now gets a history file. Previously REPL needs to specify `NODE_REPL_HISTORY_FILE` but the current version will have the history saved by default.
+- Buffer is now a subclass of Uint8Array.
+- The `smalloc` module has been removed, and the `freelist` module has now been deprecated.
+
+With a major version bump, there are also breaking changes. These include:
+- Changes on `Buffer.concat`, `dgram send()` error and `http` server timing behaviors.
+- The upgrade on V8, which gives the need for recompiling of all native add-ons and the new `Maybe<>` and `MaybeLocal<>` types for add-on authors to transition to these new APIs as soon as possible.
+- HTTP status codes. The code mappings conform to the [IANA standard](http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) now and will be a backwards incompatible change to consumers that depend on the text value of a header.
+- The HTTP agent `.getName()`, which fixes the unnecessary extra colon at the end of the return values.
+
+You can find out more information about this release in the [complete changelog](https://github.com/nodejs/node/blob/master/CHANGELOG.md), the [Breaking Changes document](https://github.com/nodejs/node/wiki/Breaking-Changes#300-from-2x) and the [pull request for the release proposal](https://github.com/nodejs/node/pull/2299). In addition, [Yosuke Furukawa](https://twitter.com/yosuke_furukawa) has made a [repo with details about the new features](https://github.com/yosuke-furukawa/iojs-new-features).
+
+#### Notable changes
+
+* **buffer**:
+  * Due to changes in V8, it has been necessary to reimplement `Buffer` on top of V8's `Uint8Array`. Every effort has been made to minimize the performance impact, however `Buffer` instantiation is measurably slower. Access operations may be faster in some circumstances but the exact performance profile and difference over previous versions will depend on how `Buffer` is used within applications. (Trevor Norris) [#1825](https://github.com/nodejs/node/pull/1825).
+  * `Buffer` can now take `ArrayBuffer`s as a constructor argument (Trevor Norris) [#2002](https://github.com/nodejs/node/pull/2002).
+  * When a single buffer is passed to `Buffer.concat()`, a new, copied `Buffer` object will be returned; previous behavior was to return the original `Buffer` object (Sakthipriyan Vairamani) [#1937](https://github.com/nodejs/node/pull/1937).
+* **build**: PPC support has been added to core to allow compiling on pLinux BE and LE (AIX support coming soon) (Michael Dawson) [#2124](https://github.com/nodejs/node/pull/2124).
+* **dgram**: If an error occurs within `socket.send()` and a callback has been provided, the error is only passed as the first argument to the callback and not emitted on the `socket` object; previous behavior was to do both (Matteo Collina & Chris Dickinson) [#1796](https://github.com/nodejs/node/pull/1796)
+* **freelist**: Deprecate the undocumented `freelist` core module (Sakthipriyan Vairamani) [#2176](https://github.com/nodejs/node/pull/2176).
+* **http**:
+  * Status codes now all use the official [IANA names](http://www.iana.org/assignments/http-status-codes) as per [RFC7231](https://tools.ietf.org/html/rfc7231), e.g. `http.STATUS_CODES[414]` now returns `'URI Too Long'` rather than `'Request-URI Too Large'` (jomo) [#1470](https://github.com/nodejs/node/pull/1470).
+  * Calling .getName() on an HTTP agent no longer returns a trailing colon, HTTPS agents will no longer return an extra colon near the middle of the string (Brendan Ashworth) [#1617](https://github.com/nodejs/node/pull/1617).
+* **node**:
+  * `NODE_MODULE_VERSION` has been bumped to `45` to reflect the break in ABI (Rod Vagg) [#2096](https://github.com/nodejs/node/pull/2096).
+  * Introduce a new `process.release` object that contains a `name` property set to `'io.js'` and `sourceUrl`, `headersUrl` and `libUrl` (Windows only) properties containing URLs for the relevant resources; this is intended to be used by node-gyp (Rod Vagg) [#2154](https://github.com/nodejs/node/pull/2154).
+  * The version of node-gyp bundled with io.js now downloads and uses a tarball of header files from iojs.org rather than the full source for compiling native add-ons; it is hoped this is a temporary floating patch and the change will be upstreamed to node-gyp soon (Rod Vagg) [#2066](https://github.com/nodejs/node/pull/2066).
+* **repl**: Persistent history is now enabled by default. The history file is located at ~/.node_repl_history, which can be overridden by the new environment variable `NODE_REPL_HISTORY`. This deprecates the previous `NODE_REPL_HISTORY_FILE` variable. Additionally, the format of the file has been changed to plain text to better handle file corruption. (Jeremiah Senkpiel) [#2224](https://github.com/nodejs/node/pull/2224).
+* **smalloc**: The `smalloc` module has been removed as it is no longer possible to provide the API due to changes in V8 (Ben Noordhuis) [#2022](https://github.com/nodejs/node/pull/2022).
+* **tls**: Add `server.getTicketKeys()` and `server.setTicketKeys()` methods for [TLS session key](https://www.ietf.org/rfc/rfc5077.txt) rotation (Fedor Indutny) [#2227](https://github.com/nodejs/node/pull/2227).
+* **v8**: Upgraded to 4.4.63.26
+  * ES6: Enabled [computed property names](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer#Computed_property_names)
+  * ES6: `Array` can now be subclassed in strict mode
+  * ES6: Implement [rest parameters](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Functions/rest_parameters) in staging, use the `--harmony-rest-parameters` command line flag
+  * ES6: Implement the [spread operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator) in staging, use the `--harmony-spreadcalls` command line flag
+  * Removed `SetIndexedPropertiesToExternalArrayData` and related APIs, forcing a shift to `Buffer` to be reimplemented based on `Uint8Array`
+  * Introduction of `Maybe` and `MaybeLocal` C++ API for objects which _may_ or _may not_ have a value.
+  * Added support for PPC
+
+See also https://github.com/nodejs/node/wiki/Breaking-Changes#300-from-2x for a summary of the breaking changes (SEMVER-MAJOR).
+
+#### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* We *still* need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* [webkid.io](http://webkid.io) co-founder [Moritz Klack](http://twitter.com/moklick) has written about [creating a REST API with Hapi, Dogwater and Bedwetter](http://blog.webkid.io/how-to-create-a-rest-api-with-hapi/?utm_source=io.js+and+Node.js+News&utm_medium=article).
+* [RisingStack](http://risingstack.com) CEO [Gergely Nemeth](http://twitter.com/nthgergo) has a post in the company blog about [using GraphQL with Graffiti](https://blog.risingstack.com/start-using-graphql-with-graffiti/?utm_source=io.js+and+Node.js+News&utm_medium=article).
+* [Samsung banks on JavaScript, Node.js for IoT](http://www.infoworld.com/article/2953719/javascript/samsung-banks-on-javascript-node-js-for-iot.html?utm_source=io.js+and+Node.js+News&utm_medium=article), as reported by [Paul Krill](https://twitter.com/pjkrill), editor at large at [InfoWorld](http://www.infoworld.com/).
+
+If you have spotted or written something about Node.js and io.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
+
+Have an event about Node.js and io.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-08-14.md b/locale/uk/blog/weekly-updates/weekly-update.2015-08-14.md
new file mode 100755
index 0000000000000..ff6b228cbc23a
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-08-14.md
@@ -0,0 +1,48 @@
+---
+title: Weekly Update - Aug 14th, 2015
+author: Steven Sinatra (@diagramatics)
+date: 2015-08-14T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-08-14
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — August 14th
+The move of nodejs/io.js to nodejs/node, the Collaborator Summit, and more.
+
+### nodejs/io.js has moved to nodejs/node!
+[Rod Vagg](http://twitter.com/rvagg) made a [proposal](https://github.com/nodejs/node/issues/2327) regarding the convergence work between io.js and Node.js earlier this week, and one of them is about renaming the nodejs/io.js repository to [nodejs/node](https://github.com/nodejs/node). A decision has been made, and [nodejs/node](https://github.com/nodejs/node) is our new home!
+
+With the new repository name, io.js v3.x will be our last major version of io.js as the next (v4.x) will be Node.js v4.x.
+
+Other points in the proposal are:
+
+* The new repository to be the host of all future releases including io.js v3 and Node.js 0.10 and 0.12. The suggestion is that they will be in separate branches named v0.10.x and v0.12.x alongside with the existing v3.x branch.
+* Leaving [joyent/node](https://github.com/joyent/node) in place for now, encouraging all new issues and pull requests in it to be filed in nodejs/node instead. There is also a possibility to move joyent/node to nodejs/node-legacy or a similarly named repository.
+* Documenting a new, simpler version of CONTRIBUTING.md for casual contributions, as contributions need to be documented according to the new branch structure nodejs/node will have. With the new branches hosting the different versions, contributors will need to be aware which branch they need to file a pull request to and which version are their issues related to.
+
+Jump on the conversation on the [nodejs/node issue page](https://github.com/nodejs/node/issues/2327).
+
+### Community Updates
+
+* We *still* need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* As mentioned up top, io.js v4.x will be Node.js v4.x. Or as [Mikeal Rogers](http://twitter.com/mikeal) said, [4.0 is the new 1.0](https://medium.com/node-js-javascript/4-0-is-the-new-1-0-386597a3436d).
+* The Node.js Collaborator Summit was hosted on 6th – 7th August in San Fransisco. You can see the notes in the [nodejs/summit](https://github.com/nodejs/summit) repository, [the GitHub issue](https://github.com/nodejs/summit/issues/11), or on [the Google Docs folder](https://drive.google.com/folderview?id=0B4tYrG9tjAW0fk9VOG52R2VQMmZHNWdpYnpqWU5MYUlfamNycktmeEl3UkNhdk1PS1Rid3c&usp=sharing).
+* [nodejs/collaboration](https://github.com/nodejs/collaboration) was made along with [the team](https://github.com/orgs/nodejs/teams/collaboration) to help with communication between Working Groups, as well as getting better ways to have evangelism, website, documentation and the 30+ i18n groups work together.
+* The new [Intl WG](https://github.com/nodejs/Intl) had [a meeting](https://github.com/nodejs/Intl/issues/8) on August 11th.
+* [David Walsh](https://twitter.com/davidwalshblog) has written about [using yargs to get Node.js command line arguments](http://davidwalsh.name/nodejs-arguments-yargs/?utm_source=io.js+and+Node.js+News&utm_medium=article).
+* [Reindex](https://www.reindex.io/?utm_source=io.js+and+Node.js+News&utm_medium=article) has a post about [building a GraphQL server with Node.js and SQL](https://www.reindex.io/blog/building-a-graphql-server-with-node-js-and-sql/?utm_source=io.js+and+Node.js+News&utm_medium=article)
+* [Amine Kabab](https://twitter.com/aminekabab) made [a QR code generator library for Node.js](https://github.com/kabab/qr-cairo/?utm_source=io.js+and+Node.js+News&utm_medium=article)
+
+If you have spotted or written something about Node.js and io.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+
+Have an event about Node.js and io.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-08-21.md b/locale/uk/blog/weekly-updates/weekly-update.2015-08-21.md
new file mode 100755
index 0000000000000..6fdc01f43858d
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-08-21.md
@@ -0,0 +1,64 @@
+---
+title: Weekly Update - Aug 21st, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-08-21T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-08-21
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — August 21st
+io.js v3.1.0 and the v0.12 LTS plan, ARM build, nodeday event.
+
+### io.js v3.1.0 Release
+
+### Notable changes
+
+* **buffer**: Fixed a couple large memory leaks (Ben Noordhuis) [#2352](https://github.com/nodejs/node/pull/2352).
+* **crypto**:
+  - Fixed a couple of minor memory leaks (Karl Skomski) [#2375](https://github.com/nodejs/node/pull/2375).
+  - Signing now checks for OpenSSL errors (P.S.V.R) [#2342](https://github.com/nodejs/node/pull/2342). **Note that this may expose previously hidden errors in user code.**
+* **intl**: Intl support using small-icu is now enabled by default in builds (Steven R. Loomis) [#2264](https://github.com/nodejs/node/pull/2264).
+  - [`String#normalize()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/normalize) can now be used for unicode normalization.
+  - The [`Intl`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Intl) object and various `String` and `Number` methods are present, but only support the English locale.
+  - For support of all locales, node must be built with [full-icu](https://github.com/nodejs/node#build-with-full-icu-support-all-locales-supported-by-icu).
+* **tls**: Fixed tls throughput being much lower after an incorrect merge (Fedor Indutny) [#2381](https://github.com/nodejs/node/pull/2381).
+* **tools**: The v8 tick processor now comes bundled with node (Matt Loring) [#2090](https://github.com/nodejs/node/pull/2090).
+  - This can be used by producing performance profiling output by running node with `--perf`, then running your appropriate platform's script on the output as found in [tools/v8-prof](https://github.com/nodejs/node/tree/master/tools/v8-prof).
+* **util**: `util.inspect(obj)` now prints the constructor name of the object if there is one (Christopher Monsanto) [#1935](https://github.com/nodejs/node/pull/1935).
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+
+### Node.js v0.12 LTS plan has been shortened
+
+* Node.js v0.12 LTS plan has been shortened to end at the end of 2016, because OpenSSL 1.0.1 LTS is scheduled until the end of 2016. The detail is [here](https://github.com/nodejs/LTS/pull/36).
+
+### Community Updates
+
+* We *still* need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* [Marko Bonaći](https://github.com/mbonaci) published [his blog post](http://blog.sematext.com/2015/07/15/logging-cli-writing-first-node-project/) about his first useful Node.js product which can search log files.
+* [Rod Vagg](https://github.com/rvagg) updated [his post about the state of the Node.js build on ARM](https://medium.com/@rvagg/node-js-io-js-state-of-the-build-arm-2f24c18e1ab4). In the entry, Rod details how Node core members test and build Node.js for ARM hardware.
+
+If you have spotted or written something about Node.js and io.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [BrazilJS Conf](http://braziljs.com.br/) tickets are on sale, August 21st - 22nd at Shopping Center BarraShoppingSul
+* [nodeday](http://nodeday.com/) tickets are on sale, September 10th at Karnataka, India
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+
+
+Have an event about Node.js and io.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-08-28.md b/locale/uk/blog/weekly-updates/weekly-update.2015-08-28.md
new file mode 100755
index 0000000000000..8c50928b6d353
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-08-28.md
@@ -0,0 +1,93 @@
+---
+title: Weekly Update - Aug 28th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-08-28T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-08-28
+layout: blog-post.hbs
+---
+
+### io.js and Node.js News — August 28th
+io.js v3.2.0/v3.3.0 and Node v4 evangelism, nodejs.org, nodefest/empirenode event.
+
+### io.js 3.2 and 3.3 Releases
+
+This week we have two io.js releases: [v3.2.0](https://iojs.org/dist/v3.2.0/) and [v3.3.0](https://iojs.org/dist/v3.3.0/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+
+### io.js v3.3.0 Notable changes
+
+* **build**: Add a `--link-module` option to `configure` that can be used to bundle additional JavaScript modules into a built binary (Bradley Meck) [#2497](https://github.com/nodejs/node/pull/2497)
+* **docs**: Merge outstanding doc updates from joyent/node (James M Snell) [#2378](https://github.com/nodejs/node/pull/2378)
+* **http_parser**: Significant performance improvement by having `http.Server` consume all initial data from its `net.Socket` and parsing directly without having to enter JavaScript. Any `'data'` listeners on the `net.Socket` will result in the data being "unconsumed" into JavaScript, thereby undoing any performance gains. (Fedor Indutny) [#2355](https://github.com/nodejs/node/pull/2355)
+* **libuv**: Upgrade to 1.7.3 (from 1.6.1), see [ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details (Saúl Ibarra Corretgé) [#2310](https://github.com/nodejs/node/pull/2310)
+* **V8**: Upgrade to 4.4.63.30 (from 4.4.63.26) (Michaël Zasso) [#2482](https://github.com/nodejs/node/pull/2482)
+
+### io.js v3.2.0 Notable changes
+
+* **events**: Added `EventEmitter#listenerCount(event)` as a replacement for `EventEmitter.listenerCount(emitter, event)`, which has now been marked as deprecated in the docs. (Sakthipriyan Vairamani) [#2349](https://github.com/nodejs/node/pull/2349)
+* **module**: Fixed an error with preloaded modules when the current working directory doesn't exist. (Bradley Meck) [#2353](https://github.com/nodejs/node/pull/2353)
+* **node**: Startup time is now about 5% faster when not passing V8 flags. (Evan Lucas) [#2483](https://github.com/nodejs/node/pull/2483)
+* **repl**: Tab-completion now works better with arrays. (James M Snell) [#2409](https://github.com/nodejs/node/pull/2409)
+* **string_bytes**: Fixed an unaligned write in the handling of UCS2 encoding. (Fedor Indutny) [#2480](https://github.com/nodejs/node/pull/2480)
+* **tls**: Added a new `--tls-cipher-list` flag that can be used to override the built-in default cipher list. (James M Snell) [#2412](https://github.com/nodejs/node/pull/2412) _Note: it is suggested you use the built-in cipher list as it has been carefully selected to reflect current security best practices and risk mitigation._
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some uses of computed object shorthand properties are not handled correctly by the current version of V8. e.g. `[{ [prop]: val }]` evaluates to `[{}]`. [#2507](https://github.com/nodejs/node/issues/2507)
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/node/issues/760).
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+
+### We need Node.js v4 evangelists
+
+* Node.js v4 is released soon. We need evangelists for Node.js v4. If you have an interest to evangelize, provide your information in [this issue](https://github.com/nodejs/node/issues/2633).
+* Current members:
+- Fedor Indutny ([@indutny](https://github.com/indutny))
+- Yosuke Furukawa ([@yosuke-furukawa](https://github.com/yosuke-furukawa))
+- Sakthipriyan Vairamani ([@thefourtheye](https://github.com/thefourtheye))
+- Jackson Tian ([@JacksonTian](https://github.com/JacksonTian))
+- P.S.V.R ([@pmq20](https://github.com/pmq20))
+- James M Snell ([@pmq20](https://github.com/pmq20))
+- Mikeal Rogers ([@mikeal](https://github.com/mikeal))
+- Colin Ihrig ([@cjihrig](https://github.com/cjihrig))
+- Jeremiah Senkpiel ([@Fishrock123](https://github.com/Fishrock123))
+- Rich Trott ([@Trott](https://github.com/Trott))
+- Julian Duque ([@julianduque](https://github.com/julianduque))
+- Stephen Belanger ([@Qard](https://github.com/Qard))
+- Ben Noordhuis ([@bnoordhuis](https://github.com/bnoordhuis))
+- Trevor Norris ([@trevnorris](https://github.com/trevnorris))
+- Rod Vagg ([@rvagg](https://github.com/rvagg))
+- Evan Lucas ([@evanlucas](https://github.com/evanlucas))
+- Daniel Khan ([@danielkhan](https://github.com/danielkhan))
+- Raja Sekar ([@rajzshkr](https://github.com/rajzshkr))
+
+### New nodejs.org went live today
+
+* New nodejs.org went live today, served from DigitalOcean and CloudFlare, contributors should go to [https://github.com/nodejs/nodejs.org](https://github.com/nodejs/nodejs.org).
+
+### Community Updates
+
+* We *still* need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* npm posts an blog entry about tips for [testing and deploy](http://blog.npmjs.org/post/127671403050/testing-and-deploying-with-ordered-npm-run-scripts).
+
+If you have spotted or written something about Node.js and io.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf EU](http://nodeconf.eu/) tickets are on sale, September 6th - 9th at Waterford, Ireland
+* [nodeday](http://nodeday.com/) tickets are on sale, September 10th at Karnataka, India
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+
+
+Have an event about Node.js and io.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-09-04.md b/locale/uk/blog/weekly-updates/weekly-update.2015-09-04.md
new file mode 100755
index 0000000000000..15cb875e5db49
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-09-04.md
@@ -0,0 +1,74 @@
+---
+title: Weekly Update - Sep 4th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-09-04T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-09-04
+layout: blog-post.hbs
+---
+
+### Node.js News — September 4th
+Node.js v4.0.0 is released
+
+### Node.js v4.0.0
+
+This week is the most historical week. Finally we have released Node.js v4.0.0(stable). Thanks to the every Node/io.js collaborator. This Node.js is the most stable Node ever. We have reviewed all of patches and the state of the test suite is more stable and there are more active contributors in new Node.
+
+We would like to talk about this news, changes, features. But currently we don't have so much spaces and times. We hope that Node community will post more blog entries or more news.
+
+### Node.js v4.0.0 Notable changes
+
+This list of changes is relative to the last io.js v3.x branch release, v3.3.0. Please see the list of notable changes in the v3.x, v2.x and v1.x releases for a more complete list of changes from 0.12.x. Note, that some changes in the v3.x series as well as major breaking changes in this release constitute changes required for full convergence of the Node.js and io.js projects.
+
+* **child_process**: `ChildProcess.prototype.send()` and `process.send()` operate asynchronously across all platforms so an optional callback parameter has been introduced that will be invoked once the message has been sent, i.e. `.send(message[, sendHandle][, callback])` (Ben Noordhuis) [#2620](https://github.com/nodejs/node/pull/2620).
+* **node**: Rename "io.js" code to "Node.js" (cjihrig) [#2367](https://github.com/nodejs/node/pull/2367).
+* **node-gyp**: This release bundles an updated version of node-gyp that works with all versions of Node.js and io.js including nightly and release candidate builds. From io.js v3 and Node.js v4 onward, it will only download a headers tarball when building addons rather than the entire source. (Rod Vagg) [#2700](https://github.com/nodejs/node/pull/2700)
+* **npm**: Upgrade to version 2.14.2 from 2.13.3, includes a security update, see https://github.com/npm/npm/releases/tag/v2.14.2 for more details, (Kat Marchán) [#2696](https://github.com/nodejs/node/pull/2696).
+* **timers**: Improved timer performance from porting the 0.12 implementation, plus minor fixes (Jeremiah Senkpiel) [#2540](https://github.com/nodejs/node/pull/2540), (Julien Gilli) [nodejs/node-v0.x-archive#8751](https://github.com/nodejs/node-v0.x-archive/pull/8751) [nodejs/node-v0.x-archive#8905](https://github.com/nodejs/node-v0.x-archive/pull/8905)
+* **util**: The `util.is*()` functions have been deprecated, beginning with deprecation warnings in the documentation for this release, users are encouraged to seek more robust alternatives in the npm registry, (Sakthipriyan Vairamani) [#2447](https://github.com/nodejs/node/pull/2447).
+* **v8**: Upgrade to version 4.5.103.30 from 4.4.63.30 (Ali Ijaz Sheikh) [#2632](https://github.com/nodejs/node/pull/2632).
+ - Implement new `TypedArray` prototype methods: `copyWithin()`, `every()`, `fill()`, `filter()`, `find()`, `findIndex()`, `forEach()`, `indexOf()`, `join()`, `lastIndexOf()`, `map()`, `reduce()`, `reduceRight()`, `reverse()`, `slice()`, `some()`, `sort()`. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information.
+ - Implement new `TypedArray.from()` and `TypedArray.of()` functions. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information.
+ - Implement arrow functions, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions for further information.
+ - Full ChangeLog available at https://github.com/v8/v8-git-mirror/blob/4.5.103/ChangeLog
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some uses of computed object shorthand properties are not handled correctly by the current version of V8. e.g. `[{ [prop]: val }]` evaluates to `[{}]`. [#2507](https://github.com/nodejs/node/issues/2507)
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Node.js v4.0.0(stable) entry is posted
+
+* We have posted [Node v4.0.0](https://nodejs.org/en/blog/release/v4.0.0/) entry. This entry has more details about Node.js v4.0.0.
+
+### We are creating the list of modules that currently do not work with Node.js v4.0.0
+
+* We are listing modules that do not work with Node.js v4.0.0, If you have some troubles in your modules with Node.js v4.0.0, please provide information in this [issue](https://github.com/nodejs/node/issues/2798).
+
+### Community Updates
+
+* We *still* need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* Jeremiah Senkpiel, Node TSC member, has introduced Node.js v4.0.0 deeply. Please check [this blog](https://medium.com/@nodesource/node-js-v4-0-0-node-at-its-best-54a93fd2e0c6)
+* Daniel Khan posted the entry about Node.js v4.0 performance, features and LTS. His entry will help your [migration](http://apmblog.dynatrace.com/2015/09/05/all-you-need-to-know-about-node-js-4-0/).
+
+If you have spotted or written something about Node.js and io.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+
+
+Have an event about Node.js and io.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-09-11.md b/locale/uk/blog/weekly-updates/weekly-update.2015-09-11.md
new file mode 100755
index 0000000000000..9d0762c262224
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-09-11.md
@@ -0,0 +1,80 @@
+---
+title: Weekly Update - Sep 11th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-09-11T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-09-11
+layout: blog-post.hbs
+---
+
+### Node.js News — September 11th
+Node.js v4.1.0 / io.js v3.3.1 are released
+
+### Node.js v4.1.0 and io.js v3.3.1 Releases
+
+This week we have two releases: [Node.js v4.1.0](https://nodejs.org/dist/v4.1.0/) and [io.js v3.3.1](https://iojs.org/dist/v3.3.1/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Node.js v4.1.0 Notable changes
+
+* **buffer**:
+  - Buffers are now created in JavaScript, rather than C++. This increases the speed of buffer creation (Trevor Norris) [#2866](https://github.com/nodejs/node/pull/2866).
+  - `Buffer#slice()` now uses `Uint8Array#subarray()` internally, increasing `slice()` performance (Karl Skomski) [#2777](https://github.com/nodejs/node/pull/2777).
+* **fs**:
+  - `fs.utimes()` now properly converts numeric strings, `NaN`, and `Infinity` (Yazhong Liu) [#2387](https://github.com/nodejs/node/pull/2387).
+  - `fs.WriteStream` now implements `_writev`, allowing for super-fast bulk writes (Ron Korving) [#2167](https://github.com/nodejs/node/pull/2167).
+* **http**: Fixed an issue with certain `write()` sizes causing errors when using `http.request()` (Fedor Indutny) [#2824](https://github.com/nodejs/node/pull/2824).
+* **npm**: Upgrade to version 2.14.3, see https://github.com/npm/npm/releases/tag/v2.14.3 for more details (Kat Marchán) [#2822](https://github.com/nodejs/node/pull/2822).
+* **src**: V8 cpu profiling no longer erroneously shows idle time (Oleksandr Chekhovskyi) [#2324](https://github.com/nodejs/node/pull/2324).
+* **timers**: `#ref()` and `#unref()` now return the timer they belong to (Sam Roberts) [#2905](https://github.com/nodejs/node/pull/2905).
+* **v8**: Lateral upgrade to 4.5.103.33 from 4.5.103.30, contains minor fixes (Ali Ijaz Sheikh) [#2870](https://github.com/nodejs/node/pull/2870).
+  - This fixes a previously known bug where some computed object shorthand properties did not work correctly ([#2507](https://github.com/nodejs/node/issues/2507)).
+
+### io.js v3.3.1 Notable changes
+
+* **buffer**: Fixed a minor errors that was causing crashes (Michaël Zasso) [#2635](https://github.com/nodejs/node/pull/2635),
+* **child_process**: Fix error that was causing crashes (Evan Lucas) [#2727](https://github.com/nodejs/node/pull/2727)
+* **crypto**: Replace use of rwlocks, unsafe on Windows XP / 2003 (Ben Noordhuis) [#2723](https://github.com/nodejs/node/pull/2723)
+* **libuv**: Upgrade from 1.7.3 to 1.7.4 (Saúl Ibarra Corretgé) [#2817](https://github.com/nodejs/node/pull/2817)
+* **node**: Fix faulty `process.release.libUrl` on Windows (Rod Vagg) [#2699](https://github.com/nodejs/node/pull/2699)
+* **node-gyp**: Float v3.0.3 which has improved support for Node.js and io.js v0.10 to v4+ (Rod Vagg) [#2700](https://github.com/nodejs/node/pull/2700)
+* **npm**: Upgrade to version 2.14.3 from 2.13.3, includes a security update, see https://github.com/npm/npm/releases/tag/v2.14.2 for more details, (Kat Marchán) [#2696](https://github.com/nodejs/node/pull/2696).
+* **timers**: Improved timer performance from porting the 0.12 implementation, plus minor fixes (Jeremiah Senkpiel) [#2540](https://github.com/nodejs/node/pull/2540), (Julien Gilli) [nodejs/node-v0.x-archive#8751](https://github.com/nodejs/node-v0.x-archive/pull/8751) [nodejs/node-v0.x-archive#8905](https://github.com/nodejs/node-v0.x-archive/pull/8905)
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some uses of computed object shorthand properties are not handled correctly by the current version of V8. e.g. `[{ [prop]: val }]` evaluates to `[{}]`. [#2507](https://github.com/nodejs/node/issues/2507)
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Node.js Foundation Combines Node.js and io.js Into Single Codebase in New Release
+
+Node.js Foundation posts an entry about Node.js new release and introduction of Node Foundation. [The details are here](https://nodejs.org/en/blog/announcements/foundation-v4-announce/)
+
+### Node.js Interactive
+
+[Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive) is a new, annual, vendor-neutral conference for Node.js.  It is being led by the newly formed Node.js Foundation.
+
+### Community Updates
+
+* We *still* need a V8 maintainer for our LTS build! Head on over [to GitHub](https://github.com/nodejs/LTS/issues/28) to see if the requirements match your capabilities.
+* According to [Raygun blog](https://raygun.io/blog/2015/09/nodejs-and-io-js-are-now-one/), Node.js v4.0.0 is 8% faster than Node.js v0.12.
+* Tony Pujals, evangelism WG member, posts an [entry about Node.js v4.0.0](https://www.linkedin.com/pulse/node-v400-here-tony-pujals), He discusses ES6 in Node.js v4.0.0, LTS, and SemVer.
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9 at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-09-18.md b/locale/uk/blog/weekly-updates/weekly-update.2015-09-18.md
new file mode 100755
index 0000000000000..c45ed440330c9
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-09-18.md
@@ -0,0 +1,55 @@
+---
+title: Weekly Update - Sep 18th, 2015
+author: Yosuke Furukawa (@yosuke-furukawa)
+date: 2015-09-18T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-09-18
+layout: blog-post.hbs
+---
+
+### Node.js News — September 18th
+Node.js v4.1.1 is released
+
+### Node.js v4.1.1 Releases
+
+This week we have one release: [Node.js v4.1.1](https://nodejs.org/dist/v4.1.1/), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Node.js v4.1.1 Notable changes
+
+* **buffer**: Fixed a bug introduced in v4.1.0 where allocating a new zero-length buffer can result in the _next_ allocation of a TypedArray in JavaScript not being zero-filled. In certain circumstances this could result in data leakage via reuse of memory space in TypedArrays, breaking the normally safe assumption that TypedArrays should be always zero-filled. (Trevor Norris) [#2931](https://github.com/nodejs/node/pull/2931).
+* **http**: Guard against response-splitting of HTTP trailing headers added via [`response.addTrailers()`](https://nodejs.org/api/http.html#http_response_addtrailers_headers) by removing new-line (`[\r\n]`) characters from values. Note that standard header values are already stripped of new-line characters. The expected security impact is low because trailing headers are rarely used. (Ben Noordhuis) [#2945](https://github.com/nodejs/node/pull/2945).
+* **npm**: Upgrade to npm 2.14.4 from 2.14.3, see [release notes](https://github.com/npm/npm/releases/tag/v2.14.4) for full details (Kat Marchán) [#2958](https://github.com/nodejs/node/pull/2958)
+  - Upgrades `graceful-fs` on multiple dependencies to no longer rely on monkey-patching `fs`
+  - Fix `npm link` for pre-release / RC builds of Node
+* **v8**: Update post-mortem metadata to allow post-mortem debugging tools to find and inspect:
+  - JavaScript objects that use dictionary properties (Julien Gilli) [#2959](https://github.com/nodejs/node/pull/2959)
+  - ScopeInfo and thus closures (Julien Gilli) [#2974](https://github.com/nodejs/node/pull/2974)
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Community Updates
+
+* [NodeSource announced N|Solid](https://nodesource.com/blog/nsolid-enterprise-node-finally), "a platform built on Node.js and designed specifically for the unique needs of the enterprise" with a focus on insight, control and protection.
+* [NodeUp nintyone](http://nodeup.com/ninetyone) An Onboarding Show.
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9 at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-10-02.md b/locale/uk/blog/weekly-updates/weekly-update.2015-10-02.md
new file mode 100755
index 0000000000000..50431c2e9da60
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-10-02.md
@@ -0,0 +1,70 @@
+---
+title: Weekly Update - Oct 2nd, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-10-02T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-10-02
+layout: blog-post.hbs
+---
+
+### Node.js News — October 2nd
+Node.js v4.1.2 release proposal
+
+### Node.js v4.1.2 Release proposal
+
+This week we have one release proposal: [Node.js v4.1.2](https://github.com/nodejs/node/pull/3128), complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Node.js v4.1.2 Notable changes
+
+* **buffer**: Fixed a bug introduced in v4.1.0 where allocating a new zero-length buffer can result in the _next_ allocation of a TypedArray in JavaScript not being zero-filled. In certain circumstances this could result in data leakage via reuse of memory space in TypedArrays, breaking the normally safe assumption that TypedArrays should be always zero-filled. (Trevor Norris) [#2931](https://github.com/nodejs/node/pull/2931).
+* **http**: Guard against response-splitting of HTTP trailing headers added via [`response.addTrailers()`](https://nodejs.org/api/http.html#http_response_addtrailers_headers) by removing new-line (`[\r\n]`) characters from values. Note that standard header values are already stripped of new-line characters. The expected security impact is low because trailing headers are rarely used. (Ben Noordhuis) [#2945](https://github.com/nodejs/node/pull/2945).
+* **npm**: Upgrade to npm 2.14.4 from 2.14.3, see [release notes](https://github.com/npm/npm/releases/tag/v2.14.4) for full details (Kat Marchán) [#2958](https://github.com/nodejs/node/pull/2958)
+  - Upgrades `graceful-fs` on multiple dependencies to no longer rely on monkey-patching `fs`
+  - Fix `npm link` for pre-release / RC builds of Node
+* **v8**: Update post-mortem metadata to allow post-mortem debugging tools to find and inspect:
+  - JavaScript objects that use dictionary properties (Julien Gilli) [#2959](https://github.com/nodejs/node/pull/2959)
+  - ScopeInfo and thus closures (Julien Gilli) [#2974](https://github.com/nodejs/node/pull/2974)
+
+### Node.js Help Repository
+
+[Node.js Help](https://github.com/nodejs/help) is open. Need help with Node? Please feel free to ask.
+Want to help others with issues? You can start simply, by answering open questions.
+
+Please do come over to our [Node.js Help](https://github.com/nodejs/help) to create a new issue if you have any questions.
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Security Updates
+
+* [CVE-2015-7384 Denial of Service Vulnerability](https://groups.google.com/forum/#!topic/nodejs-sec/fSNEQiuof6I), "A new v4.x release on **Monday the 5th of October 2015** will be made available with appropriate fixes for this vulnerability along with disclosure of the details of the bug to allow for complete impact assessment by users"
+* Please subscribe to the low-volume announcement-only **nodejs-sec** mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date with security vulnerabilities in Node.js and the projects maintained in the **nodejs** [GitHub organization](http://github.com/nodejs/).
+
+Please contact secu...@nodejs.org if you wish to report a vulnerability in Node.js.
+
+### Community Updates
+
+* [StrongLoop introduces Arrow functions](https://strongloop.com/strongblog/an-introduction-to-javascript-es6-arrow-functions/), "Arrow functions serve two main purposes: more concise syntax and sharing lexical this with the parent scope."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20 – 23th at Queensland, Australia
+* [Playnode](https://playnode.io), call-for-proposals, November, Korea
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9 at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-10-09.md b/locale/uk/blog/weekly-updates/weekly-update.2015-10-09.md
new file mode 100755
index 0000000000000..1332b5bab8c2b
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-10-09.md
@@ -0,0 +1,62 @@
+---
+title: Weekly Update - Oct 9th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-10-09T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-10-09
+layout: blog-post.hbs
+---
+
+### Node.js News — October 9th
+Node.js v4.1.2 is released
+
+### Node.js v4.1.2 Releases
+
+This week we have one release: [Node.js v4.1.2](https://nodejs.org/en/blog/release/v4.1.2/). complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **http**:
+  - Fix out-of-order 'finish' event bug in pipelining that can abort execution, fixes DoS vulnerability [CVE-2015-7384](https://github.com/nodejs/node/issues/3138) (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+  - Account for pending response data instead of just the data on the current request to decide whether pause the socket or not (Fedor Indutny) [#3128](https://github.com/nodejs/node/pull/3128)
+* **libuv**: Upgraded from v1.7.4 to v1.7.5, see [release notes](https://github.com/libuv/libuv/releases/tag/v1.7.5) for details (Saúl Ibarra Corretgé) [#3010](https://github.com/nodejs/node/pull/3010)
+  - A better rwlock implementation for all Windows versions
+  - Improved AIX support
+
+### Known issues
+
+See https://github.com/nodejs/node/labels/confirmed-bug for complete and current list of known issues.
+
+* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/node/issues/1264).
+* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/node/issues/690)
+* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/node/issues/894)
+* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/node/issues/1435).
+
+### Node.js Foundation Welcomes Red Hat as Newest Platinum Member
+
+* The Node.js Foundation, a community-led and industry-backed consortium to advance the development of the Node.js platform, announced Red Hat, Inc. has joined the Foundation as a Platinum member. 
+* Red Hat joins platinum members, including Famous, IBM, Intel, Joyent, Microsoft and PayPal, to provide support in the adoption, development and long-term success of the Node.js project.
+
+See https://www.redhat.com/en/about/press-releases/red-hat-joins-nodejs-foundation for more information.
+
+### Community Updates
+
+* [StrongLoop provides "An Introduction to JavaScript ES6 Arrow Functions"](https://strongloop.com/strongblog/an-introduction-to-javascript-es6-arrow-functions/), "Arrow functions serve two main purposes: more concise syntax and sharing lexical this with the parent scope."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Italian Conference](http://nodejsconf.it/) tickets are on sale, October 10th at Desenzano - Brescia, Italy
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Stack Exchange HQ, Old St
+* [Node Girls London](https://nodegirls.typeform.com/to/atW4HR), November 7th at Stack Exchange HQ, Old St
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20 – 23th at Queensland, Australia
+* [Playnode](https://playnode.io), call-for-proposals, November, Korea
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9 at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-10-16.md b/locale/uk/blog/weekly-updates/weekly-update.2015-10-16.md
new file mode 100755
index 0000000000000..20505bcaee95a
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-10-16.md
@@ -0,0 +1,51 @@
+---
+title: Weekly Update - Oct 16th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-10-16T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-10-16
+layout: blog-post.hbs
+---
+
+### Node.js News — October 16th
+Node.js v4.2.1 (LTS), v4.2.0 (LTS) are released
+
+### Node.js v4.2.1 (LTS) and v4.2.0 (LTS) Releases
+
+This week we have two releases: [Node.js v4.2.1 (LTS)](https://nodejs.org/en/blog/release/v4.2.1/) and [Node.js v4.2.0 (LTS)](https://nodejs.org/en/blog/release/v4.2.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes : v4.2.1 (LTS)
+
+* Includes fixes for two regressions
+  - Assertion error in WeakCallback  - see [#3329](https://github.com/nodejs/node/pull/3329)
+  - Undefined timeout regression - see [#3331](https://github.com/nodejs/node/pull/3331)
+
+### Notable changes : v4.2.0 (LTS)
+
+* **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) [#3281](https://github.com/nodejs/node/pull/3281)
+* **node**:
+  - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) [#2411](https://github.com/nodejs/node/pull/2411)
+  - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) [#3102](https://github.com/nodejs/node/pull/3102)
+
+### Community Updates
+
+* [Node.js v4.2.1 Release Summary and Stats](https://nodesource.com/blog/nodejs-v421-release-summary-and-stats), "Closely tracking the Long Term Support plan, 4.2.0 and 4.2.1 have been released this week as LTS. v4.2.1 has been released to fix two critical regressions in v4.2.0. It is highly suggested you use v4.2.1 instead of v4.2.0"
+* [A Hubot Plugin that Helps You to Choose Where to Drink Coffee](http://ditrospecta.com/javascript/plugin/hubot/2015/10/03/hubot-plugin-choose-place-to-drink-coffee.html), "Hubot is a very friendly and easy extensible bot written in Coffeescript"
+* [Linux and Node.js in Production using Daemontools and NDT](http://www.serverpals.com/blog/linux-nodejs-in-production-using-daemontools-ndt), "Putting the application to the test with Linux and Node.js in Production using Daemontools and NDT"
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [JSConf CO](http://www.jsconf.co/), October 16th - 17th at Ruta N, Medellin, Colombia
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Node Girls London](https://nodegirls.typeform.com/to/atW4HR), November 7th at London, UK
+* [Playnode](http://playnode.io/), November 12nd at Seoul, South Korea
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20 – 23th at Queensland, Australia
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9 at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-10-23.md b/locale/uk/blog/weekly-updates/weekly-update.2015-10-23.md
new file mode 100755
index 0000000000000..48a8f46090386
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-10-23.md
@@ -0,0 +1,69 @@
+---
+title: Weekly Update - Oct 23rd, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-10-23T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-10-23
+layout: blog-post.hbs
+---
+
+### Node.js News — October 23rd
+Node.js v5.0.0 release proposal
+
+### Node.js v5.0.0 release proposal
+
+This week we have one release proposal: [Node.js v5.0.0](https://github.com/nodejs/node/pull/3466). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* console: console.time has been changed to log with sub-millisecond accuracy (Michaël Zasso) [#3166](https://github.com/nodejs/node/pull/3166).
+  - Values reported by console.time will now have 3 decimals of accuracy added.
+* fs: Added file descriptor support to *File functions (Johannes Wüller) [#3163](https://github.com/nodejs/node/pull/3163)
+  - fs.readFile, fs.writeFile, and fs.appendFile now also accept a file descriptor as their first argument.
+
+### Node.js foundation is considering an iteration on the official logo
+
+* [Please click here](https://github.com/nodejs/evangelism/issues/179) to post images and ideas.
+* The Marketing Committee will look over ideas at some point in the future and potentially select one or take some of the ideas/direction and handoff to a designer.
+* Final logo will have to be approved by the Board of Directors.
+
+### Node.js foundation announces programming for Node.js interactive
+
+* The Node.js Foundation, a community-led and industry-backed consortium to advance the development of the Node.js platform, announced initial programming for Node.js Interactive.
+* This inaugural event, which is being led by the newly formed Node.js Foundation in cooperation with the Linux Foundation, will be held December 8-9, 2015, in Portland, Ore.
+* Node.js Interactive will also focus on three tracks: Frontend, Backend and the Internet of Things (IoT).
+
+See https://nodejs.org/en/blog/announcements/interactive-2015-programming for more information.
+
+### NodeUp Podcast
+
+* NodeUp podcast episode 92 was published this week: <http://nodeup.com/ninetytwo>.
+* The subject of the podcast is Node 4.0 and the participants are Rod Vagg, Evan Lucas, and Rich Trott.
+
+### Good First Contribution
+
+* Start getting involved in Node.js with [`good-first-contribution` issues](https://github.com/nodejs/node/labels/good%20first%20contribution).
+* Want to help others with issues? You can start simply, by answering [open questions](https://github.com/nodejs/node/labels/good%20first%20contribution) with `good-first-contribution` tag.
+
+See https://github.com/nodejs/node/labels/good%20first%20contribution for more information.
+
+### Community Updates
+
+* [Node.js for the Real World](http://www.technology-ebay.de/the-teams/mobile-de/blog/nodejs-real-world), "Node.js as back-end for the user-interface layer is a perfect usecase"
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [EmpireNode](http://2015.empirenode.org/), October 23rd at New York, US.
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Node Knockout](http://www.nodeknockout.com/), November 7 - 8th, Worldwide
+* [Node Girls London](https://nodegirls.typeform.com/to/atW4HR), November 7th at London, UK
+* [Playnode](http://playnode.io/), November 12nd at Seoul, South Korea
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20 – 23th at Queensland, Australia
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-10-30.md b/locale/uk/blog/weekly-updates/weekly-update.2015-10-30.md
new file mode 100755
index 0000000000000..b73a03f1fe0e5
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-10-30.md
@@ -0,0 +1,50 @@
+---
+title: Weekly Update - Oct 30th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-10-30T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-10-30
+layout: blog-post.hbs
+---
+
+### Node.js News — October 30th
+Node.js v5.0.0 (Current) is released
+
+### Node.js v5.0.0 (Current) Releases
+
+This week we have one release: [Node.js v5.0.0 (Current)](https://nodejs.org/en/blog/release/v5.0.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes : v5.0.0 (Current)
+
+* **v8**: _(Breaking)_ Upgraded to 4.6.85.25 from 4.5.103.35  (Ali Ijaz Sheikh) [#3351](https://github.com/nodejs/node/pull/3351).
+  - Implements the spread operator, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator for further information.
+* **npm**: Upgraded to version 3.3.6 from 2.14.7, see https://github.com/npm/npm/releases/tag/v3.3.6 for more details. This is a major version bump for npm and it has seen a significant amount of change. Please see the original [npm v3.0.0 release notes](https://github.com/npm/npm/blob/master/CHANGELOG.md#v300-2015-06-25) for a list of major changes (Rebecca Turner) [#3310](https://github.com/nodejs/node/pull/3310).
+
+### Node.js foundation is considering an iteration on the official logo
+
+* [Please click here](https://github.com/nodejs/evangelism/issues/179) to post images and ideas.
+* The Marketing Committee will look over ideas at some point in the future and potentially select one or take some of the ideas/direction and handoff to a designer.
+* Final logo will have to be approved by the Board of Directors.
+
+### Community Updates
+
+* [NodeSource - Need to Node Ep.3: Office Hours with Rod Vagg](https://vimeo.com/143308094), "Rod answers questions about the Node.js TSC, discusses what is happening with Node.js, provides updates on how the reconciliation of Node.js & io.js is going and outlines what's coming up next with Node.js."
+* [Using Node.js for everything](https://codek.tv/2095), "Charlie Key, CEO at Modulus, covers how a fast-moving company can use Node.js and JavaScript for basically everything and succeed."
+* [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/), "checklist to help you guide through the must have security checks before your application is enabled to thousands of users/customers."
+* [IBM acquires StrongLoop, helping clients extend their enterprise reach](http://www.thoughtsoncloud.com/2015/09/ibm-acquires-strongloop-helping-clients-extend-their-enterprise-reach/), "IBM announced that it acquired StrongLoop to help you accelerate your digital transformation."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Node Knockout](http://www.nodeknockout.com/), November 7 - 8th, Worldwide
+* [Node Girls London](https://nodegirls.typeform.com/to/atW4HR), November 7th at London, UK
+* [Playnode](http://playnode.io/), November 12nd at Seoul, South Korea
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20 – 23th at Queensland, Australia
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8-9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-11-06.md b/locale/uk/blog/weekly-updates/weekly-update.2015-11-06.md
new file mode 100755
index 0000000000000..4a76d56a3fe06
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-11-06.md
@@ -0,0 +1,50 @@
+---
+title: Weekly Update - Nov 6th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-11-06T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-11-06
+layout: blog-post.hbs
+---
+
+### Node.js News — November 6th
+Node.js v4.2.2 (LTS) is released
+
+### Node.js v4.2.2 (LTS) Releases
+
+This week we have one release: [Node.js v4.2.2 (LTS)](https://nodejs.org/en/blog/release/v4.2.2/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+This is an LTS maintenance release that addresses a number of issues:
+
+* [[`1d0f2cbf87`](https://github.com/nodejs/node/commit/1d0f2cbf87)] - **buffer**: fix value check for writeUInt{B,L}E (Trevor Norris) [#3500](https://github.com/nodejs/node/pull/3500)
+* [[`2a45b72b4a`](https://github.com/nodejs/node/commit/2a45b72b4a)] - **buffer**: don't CHECK on zero-sized realloc (Ben Noordhuis) [#3499](https://github.com/nodejs/node/pull/3499)
+
+### NodeUp Podcast
+
+* NodeUp podcast episode 93, 94 were published this week: <http://nodeup.com/ninetythree>, <http://nodeup.com/ninetyfour>.
+* The subjects of the podcast are "An LTS Show with Kat Marchán, James Snell, and Rich Trott", "A Node.js Interactive Show with Dan Shaw, Mikeal Rogers, and Kassandra Perch.".
+
+
+### Community Updates
+
+* [Understanding Garbage Collection and hunting Memory Leaks in Node.js](http://apmblog.dynatrace.com/2015/11/04/understanding-garbage-collection-and-hunting-memory-leaks-in-node-js/), "Covers how Node.js manages memory and how to trace down memory-related problems"
+* [Node.js v4 gets an A+ for SSL Labs with no configuration](https://certsimple.com/blog/node-js-ssl-labs), "Node has one of the best out-of-the-box SSL setups of any web server."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeFest](http://nodefest.jp/2015/), November 7th at Tokyo, Japan
+* [Node Knockout](http://www.nodeknockout.com/), November 7th - 8th, Worldwide
+* [Node Girls London](https://nodegirls.typeform.com/to/atW4HR), November 7th at London, UK
+* [Playnode](http://playnode.io/), November 12nd at Seoul, South Korea
+* [Nodevember](http://nodevember.org/?utm_source=io.js+and+Node.js+News&utm_medium=article), November 14th - 15th at Nashville, Tennessee, US.
+* [JSConf.Asia](http://2015.jsconf.asia/), November 19th - 20th in Singapore.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20th – 23th at Queensland, Australia
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8th - 9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-11-13.md b/locale/uk/blog/weekly-updates/weekly-update.2015-11-13.md
new file mode 100755
index 0000000000000..667880f835cb1
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-11-13.md
@@ -0,0 +1,41 @@
+---
+title: Weekly Update - Nov 13th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-11-13T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-11-13
+layout: blog-post.hbs
+---
+
+### Node.js News — November 13th
+
+### Node.js Foundation Individual Membership Now Open
+
+* With the support of the Linux Foundation we are now able to launch an Individual Membership program.
+* These members will be electing two representatives to the Board of Directors this January who will be responsible for representing the diverse needs of the Node.js community in the administration of the Node.js Foundation.
+
+See https://nodejs.org/en/blog/community/individual-membership/ for more information.
+
+### SF Node Meetup
+
+* ["The Journey To Node 4" by Joe McCann](https://www.youtube.com/watch?v=jZpnF0zOSvY): Node.js, io.js, the Node Foundation, Node v4, etc.
+* ["Our Journey With Node.js" by Mick Ryan](https://www.youtube.com/watch?v=uFY_p1YZ2cE): How Node.js was introduced at BigCommerce, pitfalls, benefits, etc.
+* ["YOU Are Invited"](https://www.youtube.com/watch?v=1F8F-EbdX40): Rich Trott encouraged people to contribute to Node and tried to point out some non-obvious on-ramps.
+
+### Community Updates
+
+* [10 Habits of a Happy Node Hacker (2016)](http://blog.heroku.com/archives/2015/11/10/node-habits-2016), "Here are ten habits for happy Node.js hackers as we enter 2016. They're specifically for app developers"
+* [Understanding Garbage Collection and hunting Memory Leaks in Node.js](http://apmblog.dynatrace.com/2015/11/04/understanding-garbage-collection-and-hunting-memory-leaks-in-node-js/), "Covers how Node.js manages memory and how to trace down memory-related problems"
+* [Node.js v4 gets an A+ for SSL Labs with no configuration](https://certsimple.com/blog/node-js-ssl-labs), "Node has one of the best out-of-the-box SSL setups of any web server."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [JSConf.Asia](http://2015.jsconf.asia/), November 19th - 20th in Singapore.
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20th – 23th at Queensland, Australia
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8th - 9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-11-20.md b/locale/uk/blog/weekly-updates/weekly-update.2015-11-20.md
new file mode 100755
index 0000000000000..e5b2dd4d4f499
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-11-20.md
@@ -0,0 +1,59 @@
+---
+title: Weekly Update - Nov 20th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-11-20T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-11-20
+layout: blog-post.hbs
+---
+
+### Node.js News — November 20th
+Node.js v5.1.0 (Current) is released
+
+### Node.js v5.1.0 (Current) Releases
+
+This week we have one release: [Node.js v5.1.0 (Current)](https://nodejs.org/en/blog/release/v5.1.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **doc**: All of the API docs have been re-ordered so as to read in alphabetical order (Tristian Flanagan) [#3662](https://github.com/nodejs/node/pull/3662).
+* **http_parser**: update http-parser to 2.6.0 from 2.5.0 (James M Snell) [#3569](https://github.com/nodejs/node/pull/3569).
+  - Now supports the following HTTP methods: `LINK`, `UNLINK`, `BIND`, `REBIND`, `UNBIND`.
+  - Also added ACL and IPv6 Zone ID support.
+* **npm**: upgrade npm to 3.3.12 from v3.3.6 (Rebecca Turner) [#3685](https://github.com/nodejs/node/pull/3685).
+  - See the release notes for [v3.3.7](https://github.com/npm/npm/releases/tag/v3.3.7), [v3.3.8](https://github.com/npm/npm/releases/tag/v3.3.8), [v3.3.9](https://github.com/npm/npm/releases/tag/v3.3.9), [v3.3.10](https://github.com/npm/npm/releases/tag/v3.3.10), [v3.3.11](https://github.com/npm/npm/releases/tag/v3.3.11), and [v3.3.12](https://github.com/npm/npm/releases/tag/v3.3.12) for more details.
+
+### npm announces Private Packages for Organizations
+
+* npm released a set of features: Private Packages for Organizations.
+* This release allows teams to use private npm packages more effectively.
+* It’s intended for businesses that manage developer teams, with varying permissions and multiple projects.
+
+See http://blog.npmjs.org/post/133542170540/private-packages-for-organizations for more information.
+
+### Open-sourced Visual Studio Code is based on Node
+
+* Microsoft has open-sourced Visual Studio Code and it's a lot of TypeScript and Node.
+* Visual Studio Code is based on Electron, a framework which is used to deploy Node.js applications for the desktop running on Blink layout engine.
+
+See https://github.com/Microsoft/vscode for more information.
+
+### NodeUp
+
+* [NodeUp 95](http://nodeup.com/ninetyfive): A Build/CI Show with Rod Vagg, Alexis Campailla, João Reis, and Hans Kristian Flaatten.
+
+### Community Updates
+
+* [Node Knockout](http://www.nodeknockout.com/), "Node Knockout winners have been announced."
+* [Introduction to Testing Node.js](https://www.youtube.com/watch?v=u2XCdkL4bWI), "A video of Jordan Kasper how to test Node.js apps with Mocha."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Barcelona](https://ti.to/barcelonajs/nodeconf-barcelona-2015), November 21st at Barcelona, Spain
+* [CampJS VI](http://vi.campjs.com), November 20th – 23th at Queensland, Australia
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8th - 9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-11-27.md b/locale/uk/blog/weekly-updates/weekly-update.2015-11-27.md
new file mode 100755
index 0000000000000..996d79593d6e1
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-11-27.md
@@ -0,0 +1,49 @@
+---
+title: Weekly Update - Nov 27th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-11-27T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-11-27
+layout: blog-post.hbs
+---
+
+### Node.js News — November 27th
+Node v0.12.8 (LTS) is released
+
+### Node v0.12.8 (LTS) Releases
+
+This week we have one release: [Node v0.12.8 (LTS)](https://nodejs.org/en/blog/release/v0.12.8/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* [[`7d11208f68`](https://github.com/nodejs/node/commit/7d11208f68)] - **build**: backport tools/release.sh (Rod Vagg) [#3642](https://github.com/nodejs/node/pull/3642)
+* [[`6fb0b92fa0`](https://github.com/nodejs/node/commit/6fb0b92fa0)] - **build**: backport config for new CI infrastructure (Rod Vagg) [#3642](https://github.com/nodejs/node/pull/3642)
+* [[`83441616a5`](https://github.com/nodejs/node/commit/83441616a5)] - **build**: fix --without-ssl compile time error (Ben Noordhuis) [#3825](https://github.com/nodejs/node/pull/3825)
+
+### CVE-2015-8027 Denial of Service Vulnerability / CVE-2015-6764 V8 Out-of-bounds Access Vulnerability
+
+* Security release coming on December 1 or December 2 (depending on your timezone) will resolve a denial-of-service vulnerability. Be prepared to update!
+* New releases of v0.12.x, v4.x and v5.x will be made available with appropriate fixes for CVE-2015-8027 and CVE-2015-6764 (for v4.x and v5.x only)
+* Please contact security@nodejs.org if you wish to report a vulnerability in Node.js.
+
+See https://nodejs.org/en/blog/vulnerability/cve-2015-8027_cve-2015-6764/ for more information.
+
+### NodeUp
+
+* [NodeUp 96](http://nodeup.com/ninetysix): "A Node v5.0 Show" with Rebecca Turner, Rod Vagg, and Rich Trott".
+
+### Community Updates
+
+* [Top Node.js metrics to watch](https://www.oreilly.com/ideas/top-nodejs-metrics-to-watch), "Track key metrics to keep your Node.js apps running smoothly."
+* [Why we stopped vendoring our npm dependencies](http://blog.bithound.io/why-we-stopped-vendoring-our-npm-dependencies/), "Should I check my node_modules directory into my repository?"
+* [Clearing the air: Is WordPress being rewritten in Node.js and React?](http://wesbos.com/wordpress-calypso-react/), "Almost all front-end tooling is built in Node.js."
+* [Massive Memory Gains in Node.js 4.2](http://goldfirestudios.com/blog/140/Massive-Memory-Gains-in-Node.js-4.2), "Not only did we see our memory graphs smooth out significantly, but the total memory usage dropped."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8th - 9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-12-04.md b/locale/uk/blog/weekly-updates/weekly-update.2015-12-04.md
new file mode 100755
index 0000000000000..2e3193d92f239
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-12-04.md
@@ -0,0 +1,33 @@
+---
+title: Weekly Update - Dec 4th, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-12-04T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-12-04
+layout: blog-post.hbs
+---
+
+### Node.js News — December 4th
+Node v5.1.1 (Current), v4.2.3 "Argon" (LTS), v0.12.9 (LTS) and v0.10.41 (Maintenance) are released
+
+### December Security Release Summary
+* This is an important security release. Please update your Node.js installation.
+* We have released Node.js [v0.10.41 (Maintenance)](/en/blog/release/v0.10.41/), [v0.12.9 (LTS)](/en/blog/release/v0.12.9/), [v4.2.3 "Argon" (LTS)](/en/blog/release/v4.2.3/) and [v5.1.1 (Current)](/en/blog/release/v5.1.1/) with fixes for the announced vulnerabilities and updates to OpenSSL.
+* All Node.js users should consult our December Security Release Summary for details on patched vulnerabilities.
+
+See https://nodejs.org/en/blog/vulnerability/december-2015-security-releases/ for more information.
+
+### Community Updates
+
+* [Node.js running in the new Airbus A350 inflight servers](http://reaktor.com/blog/aircraft-customer-experience-on-a-new-level/), "We were allowed to run our own node.js-server on the inflight servers of the aircraft."
+* [Automatic cat feeder powered by Node.js](https://github.com/rachelnicole/robokitty), "Is a DIY cat (or dog, or human) feeder controlled over the web."
+* [Netflix' Node powered interfaces](http://thenewstack.io/netflix-uses-node-js-power-user-interface/), "Shifting its user interfaces to Node.js, Netflix has been able to streamline the development."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node.js Interactive](http://events.linuxfoundation.org/events/node-interactive), December 8th - 9th at Portland, US.
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2015-12-11.md b/locale/uk/blog/weekly-updates/weekly-update.2015-12-11.md
new file mode 100755
index 0000000000000..c0b37da1bfcb5
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2015-12-11.md
@@ -0,0 +1,61 @@
+---
+title: Weekly Update - Dec 11st, 2015
+author: Minwoo Jung (@jmwsoft)
+date: 2015-12-11T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2015-12-11
+layout: blog-post.hbs
+---
+
+### Node.js News — December 11st
+Node v5.2.0 (Current) is released
+
+### Node.js v5.2.0 (Current) Releases
+
+This week we have one release: [Node.js v5.2.0 (Current)](https://nodejs.org/en/blog/release/v5.2.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **build**:
+  - Add support for Intel's VTune JIT profiling when compiled with `--enable-vtune-profiling`. For more information about VTune, see <https://software.intel.com/en-us/node/544211>. (Chunyang Dai) [#3785](https://github.com/nodejs/node/pull/3785).
+  - Properly enable V8 snapshots by default. Due to a configuration error, snapshots have been kept off by default when the intention is for the feature to be enabled. (Fedor Indutny) [#3962](https://github.com/nodejs/node/pull/3962).
+* **crypto**:
+  - Simplify use of ECDH (Elliptic Curve Diffie-Hellman) objects (created via `crypto.createECDH(curve_name)`) with private keys that are not dynamically generated via `generateKeys()`. The public key is now computed when explicitly setting a private key. Added validity checks to reduce the possibility of computing weak or invalid shared secrets. Also, deprecated the `setPublicKey()` method for ECDH objects as its usage is unnecessary and can lead to inconsistent state. (Michael Ruddy) [#3511](https://github.com/nodejs/node/pull/3511).
+  - Update root certificates from the current list stored maintained by Mozilla NSS. (Ben Noordhuis) [#3951](https://github.com/nodejs/node/pull/3951).
+  - Multiple CA certificates can now be passed with the `ca` option to TLS methods as an array of strings or in a single new-line separated string. (Ben Noordhuis) [#4099](https://github.com/nodejs/node/pull/4099)
+* **tools**: Include a tick processor in core, exposed via the `--prof-process` command-line argument which can be used to process V8 profiling output files generated when using the `--prof` command-line argument. (Matt Loring) [#4021](https://github.com/nodejs/node/pull/4021).
+
+### Apigee, RisingStack and Yahoo Join the Node.js Foundation
+
+* [The Node.js Foundation](https://nodejs.org/en/foundation/), a community-led and industry-backed consortium to advance the development of the Node.js platform, announced Apigee, RisingStack and Yahoo are joining the Foundation as Silver Members to build and support the Node.js platform.
+* With over 2 million downloads per month, Node.js is the runtime of choice for developers building everything from enterprise applications to Industrial IoT.
+* The Node.js Foundation members work together alongside the community to help grow this diverse technology for large financial services, web-scale, cloud computing companies, and more.
+* The newly added [Long-Term Support](https://nodejs.org/en/blog/release/v4.2.0/) release version 4.0 is just one of the many initiatives from the Foundation, which addresses the needs of enterprises that are using Node.js in more complex production environments, and signals the growing maturity of the technology.
+
+See https://nodejs.org/en/blog/announcements/apigee-rising-stack-yahoo/ for more information.
+
+### Node.js Foundation Advances Platform with More Than Three Million Users
+
+* [The Node.js Foundation](https://nodejs.org/en/foundation/), announced major community, code and membership growth, adoption statistics of the technology at large, and the Foundation’s new incubation program.
+* Since the independent Node.js Foundation launched earlier this year, development progress continues to accelerate with dramatic increases in contributions to the project.
+* The first Node.js Interactive event unites more than 700 developers, engineers, system architects, DevOps professionals and users representing a wide range of projects, products and companies in Portland, Ore.
+* Node.js Interactive brings together a broad range of speakers to help experienced and novice Node.js users alike learn tips, best practices, new skills, as well as gain insight into future developments for the technology.
+* The Node.js Foundation announced its first incubation project libuv.
+* The project is both critical to Node.js and already widely used, making it a natural fit for the Foundation.
+* Under the Foundation's umbrella, it will receive additional support and mentorship.
+
+See https://nodejs.org/en/blog/announcements/foundation-advances-growth/ for more information.
+
+### Community Updates
+
+* [Finding a Memory Leak in Node.js](https://blog.risingstack.com/finding-a-memory-leak-in-node-js/), "We compiled a bunch of methods and tools that could help"
+* [Node.js running in the new Airbus A350 inflight servers](http://reaktor.com/blog/aircraft-customer-experience-on-a-new-level/), "We were allowed to run our own Node.js-server on the inflight servers of the aircraft."
+* [Automatic cat feeder powered by Node.js](https://github.com/rachelnicole/robokitty), "A DIY cat (or dog, or human) feeder controlled over the web."
+* [Netflix' Node powered interfaces](http://thenewstack.io/netflix-uses-node-js-power-user-interface/), "Shifting its user interfaces to Node.js, Netflix has been able to streamline the development."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-01-01.md b/locale/uk/blog/weekly-updates/weekly-update.2016-01-01.md
new file mode 100755
index 0000000000000..7ef3b3816055f
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-01-01.md
@@ -0,0 +1,40 @@
+---
+title: Weekly Update - Jan 1st, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-01-01T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-01-01
+layout: blog-post.hbs
+---
+
+### Node.js News — January 1st
+Node Node v4.2.4 (LTS) is released
+
+### Node.js Node v4.2.4 (LTS) Releases
+
+This week we have one release: [Node.js Node v4.2.4 (LTS)](https://nodejs.org/en/blog/release/v4.2.4/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+Node.js v4.2.4 is a Long Term Support Maintenance Update. There are a number
+of fixes and documentation updates.
+
+* Roughly 78% of the commits are documentation and test improvements
+* **domains**:
+** Fix handling of uncaught exceptions (Julien Gilli) [#3884](https://github.com/nodejs/node/pull/3884)
+* **deps**:
+** Upgrade to npm 2.14.12 (Kat Marchán) [#4110](https://github.com/nodejs/node/pull/4110)
+** Backport 819b40a from V8 upstream (Michaël Zasso) [#3938](https://github.com/nodejs/node/pull/3938)
+** Updated node LICENSE file with new npm license (Kat Marchán) [#4110](https://github.com/nodejs/node/pull/4110)
+
+### Community Updates
+
+* [History of Node.js on a Timeline](https://blog.risingstack.com/history-of-node-js/), "This is the history of Node.js on a timeline, from 2009 until now (December 2015)"
+* [What the web platform can learn from Node.js](https://developer.atlassian.com/blog/2015/11/what-the-web-platform-can-learn-from-nodejs/), "Evolving the platform"
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-01-11.md b/locale/uk/blog/weekly-updates/weekly-update.2016-01-11.md
new file mode 100755
index 0000000000000..62dd6b7bba3e9
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-01-11.md
@@ -0,0 +1,43 @@
+---
+title: Weekly Update - Jan 11th, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-01-11T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-01-11
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v5.4.0 (Current) is released
+
+### Node v5.4.0 (Current) Releases
+
+Last week we had one release: [Node v5.4.0 (Current)](https://nodejs.org/en/blog/release/v5.4.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable changes
+
+* **http**:
+  - A new status code was added: 451 - "Unavailable For Legal Reasons" (Max Barinov) [#4377](https://github.com/nodejs/node/pull/4377).
+  - Idle sockets that have been kept alive now handle errors (José F. Romaniello) [#4482](https://github.com/nodejs/node/pull/4482).
+* This release also includes several minor performance improvements:
+  - **assert**: deepEqual is now speedier when comparing TypedArrays (Claudio Rodriguez) [#4330](https://github.com/nodejs/node/pull/4330).
+  - **lib**: Use arrow functions instead of bind where possible (Minwoo Jung) [node#3622](https://github.com/nodejs/node/pull/3622).
+  - **node**: Improved accessor perf of `process.env` (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780).
+  - **node**: Improved performance of `process.hrtime()` (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780), (Evan Lucas) [#4484](https://github.com/nodejs/node/pull/4484).
+  - **node**: Improved GetActiveHandles performance (Trevor Norris) [#3780](https://github.com/nodejs/node/pull/3780).
+  - **util**: Use faster iteration in `util.format()` (Jackson Tian) [#3964](https://github.com/nodejs/node/pull/3964).
+
+### Community Updates
+
+* [History of Node.js on a Timeline](https://blog.risingstack.com/history-of-node-js/), "This is the history of Node.js on a timeline, from 2009 until now (December 2015)"
+* [What the web platform can learn from Node.js](https://developer.atlassian.com/blog/2015/11/what-the-web-platform-can-learn-from-nodejs/), "Evolving the platform"
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-01-18.md b/locale/uk/blog/weekly-updates/weekly-update.2016-01-18.md
new file mode 100755
index 0000000000000..fbc59948bb598
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-01-18.md
@@ -0,0 +1,67 @@
+---
+title: Weekly Update - Jan 18th, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-01-18T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-01-18
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v5.4.1 (Current) is released
+
+### Node v5.4.1 (Current) Releases
+
+Last week we had one release: [Node v5.4.1 (Current)](https://nodejs.org/en/blog/release/v5.4.1/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Notable Changes
+
+* Minor performance improvements:
+  - **module**: move unnecessary work for early return (Andres Suarez) [#3579](https://github.com/nodejs/node/pull/3579)
+* Various bug fixes
+* Various doc fixes
+* Various test improvements
+
+### Nodesource Updates
+
+* [Node by Numbers 2015](https://nodesource.com/blog/node-by-numbers-2015/), "By analyzing the logs for binary and source downloads, we get to discover some interesting patterns."
+* [The (Enterprise) Node Community](https://nodesource.com/blog/the-enterprise-node-community/), "At NodeSource, we believe that by embracing the greater Node.js community of developers, operations folks and even executives in the enterprise can radically expand our community."
+* [N|Solid v1.2 - monitoring Node.js at scale](https://nodesource.com/blog/n-solid-v1-2-monitoring-node-js-at-scale/), "N|Solid v1.2 adds new functionality that greatly simplifies monitoring Node at scale across your environment."
+
+### Nominations for the 2016 election
+
+[Nominations](https://github.com/nodejs/membership/issues/12) closed last Friday for the individual member representative to the Node.js Foundation Board. 12 members put their hands up with nominations:
+  - **[@guyellis](https://github.com/guyellis)**: [nomination post](http://www.guyellisrocks.com/2015/11/node-foundation-membership-election.html), [Q/A thread](https://github.com/nodejs/membership/issues/19)
+  - **[@sup](https://github.com/sup)**: [nomination post](http://jona.io/blog/board-application/), [Q/A thread](https://github.com/nodejs/membership/issues/20)
+  - **[@ashleygwilliams](https://github.com/ashleygwilliams)**: [nomination post](https://medium.com/@ag_dubs/hi-i-m-running-for-the-node-foundation-board-of-directors-c87d762cb78b), [Q/A thread](https://github.com/nodejs/membership/issues/21)
+  - **[@contra](https://github.com/contra)**: [nomination post](http://contra.io/node_board.txt), [Q/A thread](https://github.com/nodejs/membership/issues/22)
+  - **[@geek](https://github.com/geek)**: [nomination post](http://jsgeek.com/posts/node-foundation-board-nomination.html), [Q/A thread](https://github.com/nodejs/membership/issues/23)
+  - **[@jaredhanson](https://github.com/jaredhanson)**: [nomination post](http://jaredhanson.net/blog/2016/01/13/im-running-for-the-node-js-foundation-bod/), [Q/A thread](https://github.com/nodejs/membership/issues/24)
+  - **[@tejasmanohar](https://github.com/tejasmanohar)**: [nomination post](https://medium.com/@tejasmanohar/node-js-foundation-board-of-directors-5514e8faa660), [Q/A thread](https://github.com/nodejs/membership/issues/25)
+  - **[@bnb](https://github.com/bnb)**: [nomination post](http://bnb.im/blog/Individual-Membership-on-the-Board-of-Directors-for-Node-js.html), [Q/A thread](https://github.com/nodejs/membership/issues/26)
+  - **[@watson](https://github.com/watson)**: [nomination post](https://medium.com/@wa7son/why-i-m-running-for-the-node-js-foundation-board-of-directors-253bc2e3a834), [Q/A thread](https://github.com/nodejs/membership/issues/27)
+  - **[@feross](https://github.com/feross)**: [nomination post](http://feross.org/node-board/), [Q/A thread](https://github.com/nodejs/membership/issues/28)
+  - **[@pgte](https://github.com/pgte)**: [nomination post](https://gist.github.com/pgte/cfbf468202b35be78c66), [Q/A thread](https://github.com/nodejs/membership/issues/29)
+  - **[@ecowden](https://github.com/ecowden)**: [nomination post](https://medium.com/@evan.cowden/the-world-s-worst-resume-e0adf234baa0), [Q/A thread](https://github.com/nodejs/membership/issues/30)
+
+A ballot will be distributed to individual members on January 20th, with the election completed by January 30th.
+
+To be eligible to vote, you must be signed up as an individual member of the Node.js Foundation, more information can be found here: https://nodejs.org/en/blog/community/individual-membership/
+
+### Nodeup Updates
+
+* [ninetyseven](http://nodeup.com/ninetyseven), "A Front-end npm Show"
+
+### Community Updates
+
+* [How to track down CPU issues in Node.js](http://apmblog.dynatrace.com/2016/01/14/how-to-track-down-cpu-issues-in-node-js/), "CPU aspects of Node.js including the event loop and how to track down tasks that consume too much CPU time and slow down the whole process."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-01-22.md b/locale/uk/blog/weekly-updates/weekly-update.2016-01-22.md
new file mode 100755
index 0000000000000..ea8b700999824
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-01-22.md
@@ -0,0 +1,46 @@
+---
+title: Weekly Update - Jan 22th, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-01-22T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-01-22
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v4.2.6 (LTS), Node v5.5.0 (Current), Node v4.2.5 (LTS) are released
+
+### Nominations for the 2016 election
+
+[Nominations](https://github.com/nodejs/membership/issues/12) closed last Friday for the individual member representative to the Node.js Foundation Board. 12 members put their hands up with nominations:
+  - **[@guyellis](https://github.com/guyellis)**: [nomination post](http://www.guyellisrocks.com/2015/11/node-foundation-membership-election.html), [Q/A thread](https://github.com/nodejs/membership/issues/19)
+  - **[@sup](https://github.com/sup)**: [nomination post](http://jona.io/blog/board-application/), [Q/A thread](https://github.com/nodejs/membership/issues/20)
+  - **[@ashleygwilliams](https://github.com/ashleygwilliams)**: [nomination post](https://medium.com/@ag_dubs/hi-i-m-running-for-the-node-foundation-board-of-directors-c87d762cb78b), [Q/A thread](https://github.com/nodejs/membership/issues/21)
+  - **[@contra](https://github.com/contra)**: [nomination post](http://contra.io/node_board.txt), [Q/A thread](https://github.com/nodejs/membership/issues/22)
+  - **[@geek](https://github.com/geek)**: [nomination post](http://jsgeek.com/posts/node-foundation-board-nomination.html), [Q/A thread](https://github.com/nodejs/membership/issues/23)
+  - **[@jaredhanson](https://github.com/jaredhanson)**: [nomination post](http://jaredhanson.net/blog/2016/01/13/im-running-for-the-node-js-foundation-bod/), [Q/A thread](https://github.com/nodejs/membership/issues/24)
+  - **[@tejasmanohar](https://github.com/tejasmanohar)**: [nomination post](https://medium.com/@tejasmanohar/node-js-foundation-board-of-directors-5514e8faa660), [Q/A thread](https://github.com/nodejs/membership/issues/25)
+  - **[@bnb](https://github.com/bnb)**: [nomination post](http://bnb.im/blog/Individual-Membership-on-the-Board-of-Directors-for-Node-js.html), [Q/A thread](https://github.com/nodejs/membership/issues/26)
+  - **[@watson](https://github.com/watson)**: [nomination post](https://medium.com/@wa7son/why-i-m-running-for-the-node-js-foundation-board-of-directors-253bc2e3a834), [Q/A thread](https://github.com/nodejs/membership/issues/27)
+  - **[@feross](https://github.com/feross)**: [nomination post](http://feross.org/node-board/), [Q/A thread](https://github.com/nodejs/membership/issues/28)
+  - **[@pgte](https://github.com/pgte)**: [nomination post](https://gist.github.com/pgte/cfbf468202b35be78c66), [Q/A thread](https://github.com/nodejs/membership/issues/29)
+  - **[@ecowden](https://github.com/ecowden)**: [nomination post](https://medium.com/@evan.cowden/the-world-s-worst-resume-e0adf234baa0), [Q/A thread](https://github.com/nodejs/membership/issues/30)
+
+A ballot will be distributed to individual members on January 20th, with the election completed by January 30th.
+
+To be eligible to vote, you must be signed up as an individual member of the Node.js Foundation, more information can be found here: https://nodejs.org/en/blog/community/individual-membership/
+
+### Community Updates
+
+* [Node by Numbers 2015](https://nodesource.com/blog/node-by-numbers-2015/), "By analyzing the logs for binary and source downloads, we get to discover some interesting patterns."
+* [ninetyseven](http://nodeup.com/ninetyseven), "A Front-end npm Show"
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-01-29.md b/locale/uk/blog/weekly-updates/weekly-update.2016-01-29.md
new file mode 100755
index 0000000000000..53b892965594a
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-01-29.md
@@ -0,0 +1,56 @@
+---
+title: Weekly Update - Jan 29th, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-01-29T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-01-29
+layout: blog-post.hbs
+---
+
+### Node.js News
+
+The Node.js project will be releasing new versions across all of its active release lines early next week (possibly sooner, pending full impact assessment) to incorporate upstream patches from OpenSSL and some additional low-severity fixes relating to HTTP handling. Please read on for full details.
+
+See https://nodejs.org/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016/ for more information.
+
+### OpenSSL Impact Assessment
+
+OpenSSL versions 1.0.1r and 1.0.21 have been released, the announcement can be found here: https://mta.openssl.org/pipermail/openssl-announce/2016-January/000061.html
+
+Our team has made an assessment of the impact of the disclosed defects and concluded that there is no urgency in releasing patched versions of Node.js in response to this release. Therefore, we will be proceeding as planned and attempt to release new versions of each of our active release lines on or after
+**Monday the 1st of February, 11pm UTC** _(Monday the 1st of February, 3pm Pacific Time)_. Please note that this is simply an approximation of release timing. Please tune in to **nodejs-sec** (https://groups.google.com/forum/#!topic/nodejs-sec) where we will announce the availability of releases.
+
+### Nominations for the 2016 election
+
+[Nominations](https://github.com/nodejs/membership/issues/12) closed for the individual member representative to the Node.js Foundation Board. 12 members put their hands up with nominations:
+  - **[@guyellis](https://github.com/guyellis)**: [nomination post](http://www.guyellisrocks.com/2015/11/node-foundation-membership-election.html), [Q/A thread](https://github.com/nodejs/membership/issues/19)
+  - **[@sup](https://github.com/sup)**: [nomination post](http://jona.io/blog/board-application/), [Q/A thread](https://github.com/nodejs/membership/issues/20)
+  - **[@ashleygwilliams](https://github.com/ashleygwilliams)**: [nomination post](https://medium.com/@ag_dubs/hi-i-m-running-for-the-node-foundation-board-of-directors-c87d762cb78b), [Q/A thread](https://github.com/nodejs/membership/issues/21)
+  - **[@contra](https://github.com/contra)**: [nomination post](http://contra.io/node_board.txt), [Q/A thread](https://github.com/nodejs/membership/issues/22)
+  - **[@geek](https://github.com/geek)**: [nomination post](http://jsgeek.com/posts/node-foundation-board-nomination.html), [Q/A thread](https://github.com/nodejs/membership/issues/23)
+  - **[@jaredhanson](https://github.com/jaredhanson)**: [nomination post](http://jaredhanson.net/blog/2016/01/13/im-running-for-the-node-js-foundation-bod/), [Q/A thread](https://github.com/nodejs/membership/issues/24)
+  - **[@tejasmanohar](https://github.com/tejasmanohar)**: [nomination post](https://medium.com/@tejasmanohar/node-js-foundation-board-of-directors-5514e8faa660), [Q/A thread](https://github.com/nodejs/membership/issues/25)
+  - **[@bnb](https://github.com/bnb)**: [nomination post](http://bnb.im/blog/Individual-Membership-on-the-Board-of-Directors-for-Node-js.html), [Q/A thread](https://github.com/nodejs/membership/issues/26)
+  - **[@watson](https://github.com/watson)**: [nomination post](https://medium.com/@wa7son/why-i-m-running-for-the-node-js-foundation-board-of-directors-253bc2e3a834), [Q/A thread](https://github.com/nodejs/membership/issues/27)
+  - **[@feross](https://github.com/feross)**: [nomination post](http://feross.org/node-board/), [Q/A thread](https://github.com/nodejs/membership/issues/28)
+  - **[@pgte](https://github.com/pgte)**: [nomination post](https://gist.github.com/pgte/cfbf468202b35be78c66), [Q/A thread](https://github.com/nodejs/membership/issues/29)
+  - **[@ecowden](https://github.com/ecowden)**: [nomination post](https://medium.com/@evan.cowden/the-world-s-worst-resume-e0adf234baa0), [Q/A thread](https://github.com/nodejs/membership/issues/30)
+
+A ballot was distributed to individual members on January 20th, with the election completed by January 30th.
+
+To be eligible to vote, you must be signed up as an individual member of the Node.js Foundation, more information can be found here: https://nodejs.org/en/blog/community/individual-membership/
+
+### Community Updates
+
+* [Node by Numbers 2015](https://nodesource.com/blog/node-by-numbers-2015/), "By analyzing the logs for binary and source downloads, we get to discover some interesting patterns."
+* [ninetyseven](http://nodeup.com/ninetyseven), "A Front-end npm Show"
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-02-08.md b/locale/uk/blog/weekly-updates/weekly-update.2016-02-08.md
new file mode 100755
index 0000000000000..fceb6c1108931
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-02-08.md
@@ -0,0 +1,28 @@
+---
+title: Weekly Update - Feb 8th, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-02-08T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-02-08
+layout: blog-post.hbs
+---
+
+### Node.js News
+
+### 2016 Election
+
+The 2016 election was the first Individual Membership Election. The winner of the
+election is serving a two year term and the runner-up is serving a one year term.
+Future elections will happen each year for a new two year term.
+
+- The board members elected in the 2016 election are:
+  - Ashley Williams [@ashleygwilliams](https://github.com/ashleygwilliams) for a 2 year term.
+  - Feross Aboukhadijeh [@feross](https://github.com/feross) for a 1 year term.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-02-15.md b/locale/uk/blog/weekly-updates/weekly-update.2016-02-15.md
new file mode 100755
index 0000000000000..774362969994f
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-02-15.md
@@ -0,0 +1,36 @@
+---
+title: Weekly Update - Feb 15th, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-02-15T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-02-15
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v0.10.42 (LTS), Node v0.12.10 (LTS), Node v4.3.0 (LTS) and Node v5.6.0 (Current) are released.
+
+### February 2016 Security Release Summary
+We had released Node.js [v0.10.42 (Maintenance)](/en/blog/release/v0.10.42/), [v0.12.10 (LTS)](/en/blog/release/v0.12.10/), [v4.3.0 "Argon" (LTS)](/en/blog/release/v4.3.0/) and [v5.6.0 (Current)](/en/blog/release/v5.6.0/) with fixes for the announced vulnerabilities and updates to OpenSSL.
+
+**Please note that our LTS "Argon" release line has moved from v4.2.x to v4.3.x due to the security fixes enclosed. There will be no further updates to v4.2.x.** Users are advised to upgrade to v4.3.0 as soon as possible.
+
+For the purpose of understanding the impact that the fixed vulnerabilities
+have on your Node.js deployment and the urgency of the upgrades for your
+circumstances we are providing details below.
+
+See https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ for more information.
+
+### OpenSSL upgrade summary
+
+Node.js v0.10.42 and v0.12.10 upgrade the bundled version of OpenSSL from 1.0.1q to 1.0.1r. Full details can be found in the [OpenSSL 1.0.1 changelog](https://www.openssl.org/news/cl101.txt).
+
+Node.js v4.3.0 and v5.6.0 upgrade the bundled version of OpenSSL from 1.0.2e to 1.0.2f. Full details can be found in the [OpenSSL 1.0.2 changelog](https://www.openssl.org/news/cl102.txt).
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-02-22.md b/locale/uk/blog/weekly-updates/weekly-update.2016-02-22.md
new file mode 100755
index 0000000000000..2e9f61ad4e3c6
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-02-22.md
@@ -0,0 +1,27 @@
+---
+title: Weekly Update - Feb 23rd, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-02-23T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-02-23
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v4.3.1 (LTS), Node v4.4.0 (RC) and Node v5.7.0 (Current) are released.
+
+### Node v4.3.1 (LTS), Node v4.4.0 (RC) and Node v5.7.0 (Current) Releases
+
+We have three releases: [Node v4.3.1 (LTS)](https://nodejs.org/en/blog/release/v4.3.1/), [Node v4.4.0 (RC)](https://github.com/nodejs/node/pull/5301) and [Node v5.7.0 (Current)](https://nodejs.org/en/blog/release/v5.7.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### New official Node.js logo
+As a result of an iteration on the official logo, we are proud to introduce and unveil our new logo
+
+<img src="https://cloud.githubusercontent.com/assets/43438/13207731/d7c62f3e-d94c-11e5-8ff8-f32c74b13cc3.png" width="200">
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-03-01.md b/locale/uk/blog/weekly-updates/weekly-update.2016-03-01.md
new file mode 100755
index 0000000000000..a7b8fca3cc87f
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-03-01.md
@@ -0,0 +1,44 @@
+---
+title: Weekly Update - Mar 1st, 2016
+author: Minwoo Jung (@jmwsoft)
+date: 2016-03-01T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-03-01
+layout: blog-post.hbs
+---
+
+### Node.js News
+
+### OpenSSL updates, 1.0.2g and 1.0.1s
+
+Our crypto team will make an impact assessment for Node.js users of the OpenSSL releases. This information may vary depending on the different active release lines and will be posted here.
+
+As part of that impact assessment we will announce our release plans for each of the active release lines to take into account any impact. Please be prepared for the possibility of important updates to Node.js v0.10, v0.12, v4 and v5 soon after Tuesday, the 1st of March.
+
+* Expect an impact assessment of the OpenSSL updates within 24 hours of their release
+* Expect releases of Node.js v0.10, v0.12 and v5 this week, possibly containing important security releases
+* Expect a Node.js v4.4.0 release next with the possibility of a v4.3.2 security update this week
+
+See https://nodejs.org/en/blog/vulnerability/openssl-march-2016/ for more information.
+
+Please monitor the **nodejs-sec** Google Group for updates, including an impact assessment and updated details on release timing within approximately 24 hours after the OpenSSL release: https://groups.google.com/forum/#!forum/nodejs-sec
+
+### Linux PPC LE 64-bit Binaries
+
+Linux PPC LE 64-bit Binaries are included in the stable release for the first time as part of v5.7.0
+
+Get them here: https://nodejs.org/dist/v5.7.0/
+
+### Community Updates
+
+* [Presentation: Top Node.js Metrics to Watch](http://blog.sematext.com/2016/02/26/top-node-js-metrics-to-watch/)
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-03-07.md b/locale/uk/blog/weekly-updates/weekly-update.2016-03-07.md
new file mode 100755
index 0000000000000..99061e662621d
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-03-07.md
@@ -0,0 +1,39 @@
+---
+title: Weekly Update - Mar 7th, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-03-07T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-03-07
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v0.10.43 (Maintenance), Node v0.12.11 (LTS), Node v5.7.1 (Current) and Node v4.3.2 (LTS) are released.
+
+### Node v0.10.43 (Maintenance), Node v0.12.11 (LTS), Node v5.7.1 (Current) and Node v4.3.2 (LTS) Releases
+
+We have four releases: [Node v0.10.43 (Maintenance)](https://nodejs.org/en/blog/release/v0.10.43/), [Node v0.12.11 (LTS)](https://nodejs.org/en/blog/release/v0.12.11/), [Node v5.7.1 (Current)](https://nodejs.org/en/blog/release/v5.7.1/) and [Node v4.3.2 (LTS)](https://nodejs.org/en/blog/release/v4.3.2/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Initial benchmark data
+
+Initial benchmark data is now available here: https://benchmarking.nodejs.org/. 
+
+For more information on the process of how these are generated check out: https://github.com/nodejs/benchmarking/blob/master/benchmarks/README.md
+
+### New Core Technical Committee (CTC) members
+
+The Core Technical Committee (CTC) added four new members to help guide Node.js core development: Evan Lucas, Rich Trott, Ali Ijaz Sheikh and Сковорода Никита Андреевич (Nikita Skovoroda).
+
+### Community Updates
+
+* [Presentation: Top Node.js Metrics to Watch](http://blog.sematext.com/2016/02/26/top-node-js-metrics-to-watch/)
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), TICKETS ARE AVAILABLE NOW, March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-03-14.md b/locale/uk/blog/weekly-updates/weekly-update.2016-03-14.md
new file mode 100755
index 0000000000000..08496aac64165
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-03-14.md
@@ -0,0 +1,43 @@
+---
+title: Weekly Update - Mar 14th, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-03-14T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-03-14
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node Node v4.4.0 (LTS), Node v5.8.0 (Current) and Node v0.12.12 (LTS) are released.
+
+### Node Node v4.4.0 (LTS), Node v5.8.0 (Current) and Node v0.12.12 (LTS) Releases
+
+We have three releases: [Node v4.4.0 (LTS)](https://nodejs.org/en/blog/release/v4.4.0/), [Node v5.8.0 (Current)](https://nodejs.org/en/blog/release/v5.8.0/) and [Node v0.12.12 (LTS)](https://nodejs.org/en/blog/release/v0.12.12/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### AppDynamics, New Relic, Opbeat and Sphinx Join the Node.js Foundation as Silver Members
+
+The Node.js Foundation, a community-led and industry-backed consortium to advance the development of the Node.js platform, announced AppDynamics, New Relic, Opbeat and Sphinx are joining the Foundation as Silver Members to continue to sustain and grow the Node.js platform.
+
+Many of the new members are within the application performance management industry, both established and up-and-coming vendors. Application performance management is an essential part of any infrastructure and there is a need across public, private and hybrid clouds to ensure that current and future products offer next-generation application performance with Node.js as a core component to the stability and potential of these offerings.
+
+See https://nodejs.org/en/blog/announcements/appdynamics-newrelic-opbeat-sphinx/ for more information.
+
+### Initial benchmark data
+
+Initial benchmark data is now available here: https://benchmarking.nodejs.org/. 
+
+For more information on the process of how these are generated check out: https://github.com/nodejs/benchmarking/blob/master/benchmarks/README.md
+
+### Community Updates
+
+* [Presentation: Top Node.js Metrics to Watch](http://blog.sematext.com/2016/02/26/top-node-js-metrics-to-watch/)
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [NationJS Node Day Conference](http://nationjs.com/), March 11, 2016 - Washington, DC
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-04-17.md b/locale/uk/blog/weekly-updates/weekly-update.2016-04-17.md
new file mode 100755
index 0000000000000..fac8703600164
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-04-17.md
@@ -0,0 +1,35 @@
+---
+title: Weekly Update - Apr 17th, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-04-17T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-04-17
+layout: blog-post.hbs
+---
+
+### Node.js News
+Node v4.4.3 (LTS) is released.
+
+### Node v4.4.3 (LTS) Release
+
+We have one release: [Node v4.4.3 (LTS)](https://nodejs.org/en/blog/release/v4.4.3/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### New Node.js Foundation Survey Reports New “Full Stack” In Demand Among Enterprise Developers
+
+The Node.js User Survey report features insights on emerging trends happening in this massive community that serves as a leading indicator on trends like microservices architectures, real-time web applications, Internet of Things (IoT). The report paints a detailed picture of the technologies that are being used, in particular, with Node.js in production and language preferences (current and future) for front end, back end and IoT developers.
+
+See https://nodejs.org/en/blog/announcements/nodejs-foundation-survey/ for more information.
+
+### Community Updates
+
+* [NodeUp podcast episode 100](http://nodeup.com/onehundred): A Creative Coding Show with Mariko Kosaka, Kassandra Perch, Myles Borins, and Rich Trott.
+* [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-04-23.md b/locale/uk/blog/weekly-updates/weekly-update.2016-04-23.md
new file mode 100755
index 0000000000000..099b0487f2fa0
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-04-23.md
@@ -0,0 +1,26 @@
+---
+title: Weekly Update - Apr 23rd, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-04-23T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-04-23
+layout: blog-post.hbs
+---
+
+### Node v5.11.0 (Stable) Release
+
+[Node v5.11.0 (Stable)](https://nodejs.org/en/blog/release/v5.11.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Community Updates
+
+* [NodeUp podcast episode 100](http://nodeup.com/onehundred): A Creative Coding Show with Mariko Kosaka, Kassandra Perch, Myles Borins, and Rich Trott.
+* [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-04-29.md b/locale/uk/blog/weekly-updates/weekly-update.2016-04-29.md
new file mode 100755
index 0000000000000..f811008c96f28
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-04-29.md
@@ -0,0 +1,42 @@
+---
+title: Weekly Update - Apr 29th, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-04-29T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-04-29
+layout: blog-post.hbs
+---
+
+### Node v6.0.0 (Current) Release
+
+[Node v6.0.0 (Current)](https://nodejs.org/en/blog/release/v6.0.0/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+See [Breaking changes between v5 and v6](https://github.com/nodejs/node/wiki/Breaking-changes-between-v5-and-v6) for more information.
+
+You may have noticed that the v6 release uses the label `Current` instead of `Stable`. This name change has been made in order to better differentiate the Long Term Support releases from the current active development branches. We
+will be using the `Current` label from here-on instead of `Stable`.
+
+### World’s Fastest Growing Open Source Platform Pushes Out New Release
+
+Performance improvements are key in this latest release with one of the most significant improvements coming from module loading, which is currently four times faster than Node.js version 4 (Node.js v4). This will help developers dramatically decrease the startup time of large applications for the best productivity in development cycles and more seamless experience with end users. In addition, Node.js v6 comes equipped with v8 JavaScript engine 5.0, which has improved ECMAScript 2015 (ES6) support. Ninety-three percent of ES6 features are also now supported in the Node.js v6 release, up from 56 percent for Node.js v5 and 50 percent for Node.js v4. Key features from ES6 include: default and rest parameters, destructuring, class and super keywords.
+
+See https://nodejs.org/en/blog/announcements/v6-release/ for more information.
+
+### Community Updates
+
+* [Node Hero - Getting Started With Node.js](https://blog.risingstack.com/node-hero-tutorial-getting-started-with-node-js/): you can learn how to get started with Node.js and deliver software products using it.
+* [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf London](http://london.nodeconf.com) - May 11th, 2016
+* [Node.js Live (Beijing)](http://live.nodejs.org/events/beijing.html) - May, 21st - 22nd, 2016
+* [NodeConf Brazil](http://brazil.nodeconf.com) - June 4th - 5th, 2016
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [Node PDX](http://nodepdx.org) - June 19-21st, 2016
+* [NodeConf Argentina](https://2016.nodeconf.com.ar) - 18 - 19th November, 2016
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-05-30.md b/locale/uk/blog/weekly-updates/weekly-update.2016-05-30.md
new file mode 100755
index 0000000000000..4ed1e6bcf1d15
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-05-30.md
@@ -0,0 +1,30 @@
+---
+title: Weekly Update - May 30th, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-05-30T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-05-30
+layout: blog-post.hbs
+---
+
+### Node v4.4.5 (LTS) Release
+
+[Node v4.4.5 (LTS)](https://nodejs.org/en/blog/release/v4.4.5/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Community Updates
+
+* [NodeUp podcast episode 102](http://nodeup.com/onehundredtwo): A Node v6.0 Show with Anna Henningsen, James Snell, Rich Trott, and Rod Vagg.
+* [Node Hero - Getting Started With Node.js](https://blog.risingstack.com/node-hero-tutorial-getting-started-with-node-js/): you can learn how to get started with Node.js and deliver software products using it.
+* [A Quick Guide To Reading Node.js Core Source](https://medium.com/@Trott/a-quick-guide-to-reading-node-js-core-source-c968d83e4194#.mmontrmvg): One person's approach to understanding the source code that makes up Node.js core. "Your mileage may vary. Warranty void if seal is broken."
+
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [NodeConf Brazil](http://brazil.nodeconf.com) - June 4th - 5th, 2016
+* [NodeConf Adventure 2016](https://ti.to/nodeconf/adventure-2016), "First batch of NodeConf Adventure tickets are up!", June 9th–12th, 2016 - Walker Creek Ranch, Marin, CA, USA
+* [Node PDX](http://nodepdx.org) - June 19-21st, 2016
+* [NodeConf Argentina](https://2016.nodeconf.com.ar) - 18 - 19th November, 2016
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/blog/weekly-updates/weekly-update.2016-06-16.md b/locale/uk/blog/weekly-updates/weekly-update.2016-06-16.md
new file mode 100755
index 0000000000000..bd173b898585c
--- /dev/null
+++ b/locale/uk/blog/weekly-updates/weekly-update.2016-06-16.md
@@ -0,0 +1,38 @@
+---
+title: Weekly Update - June 16th, 2016
+author: Minwoo Jung (github.com/JungMinu)
+date: 2016-06-16T12:00:00.000Z
+status: publish
+category: weekly
+slug: weekly-update-2016-06-16
+layout: blog-post.hbs
+---
+
+### Node v6.2.1 (Current) Release
+
+[Node v6.2.1 (Current)](https://nodejs.org/en/blog/release/v6.2.1/). Complete changelog from previous releases can be found [on GitHub](https://github.com/nodejs/node/blob/master/CHANGELOG.md).
+
+### Binaries for Linux on Power Systems
+
+Community downloads now include binaries for Linux on Power Systems with big endian in addition to the existing little endian binaries.
+
+See https://nodejs.org/en/download/.
+
+### Security updates for all active release lines, June 2016
+
+We now intend to make releases available on or soon after **Thursday, the 23rd of June, 2016, UTC**.
+
+See https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/ for more information.
+
+### Community Updates
+
+* [How to Get Node.js Logging Right](https://blog.risingstack.com/node-js-logging-tutorial/): The aim of this article is to provide help with logging in Node.js modules, applications and distributed systems
+* [Node Hero - Node.js Unit Testing Tutorial](https://blog.risingstack.com/node-hero-node-js-unit-testing-tutorial/): you can learn how to get started with Node.js and deliver software products using it.
+If you have spotted or written something about Node.js, do come over to our [Evangelism team repo](https://github.com/nodejs/evangelism) and suggest it on the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
+
+### Upcoming Events
+
+* [Node PDX](http://nodepdx.org) - June 19-21st, 2016
+* [NodeConf Argentina](https://2016.nodeconf.com.ar) - 18 - 19th November, 2016
+
+Have an event about Node.js coming up? You can put your events here through the [Evangelism team repo](https://github.com/nodejs/evangelism) and announce it in the [Issues page](https://github.com/nodejs/evangelism/issues), specifically the Weekly Updates issue.
diff --git a/locale/uk/docs/es6.md b/locale/uk/docs/es6.md
new file mode 100755
index 0000000000000..649efc7826262
--- /dev/null
+++ b/locale/uk/docs/es6.md
@@ -0,0 +1,39 @@
+---
+title: ECMAScript 2015 (ES6) та вище
+layout: docs.hbs
+---
+# ECMAScript 2015 (ES6) та вище
+
+Node.js побудований на сучасних версіях [V8](https://developers.google.com/v8/).  Ми певні в тому, що новий функціонал зі [специфікації JavaScript ECMA-262 ](http://www.ecma-international.org/publications/standards/Ecma-262.htm) постачається Node.js–розробникам поступово, для подальшого підвищення швидкодії та стабільності, оскільки використовуємо найсвіжіші релізи цього рушія.
+
+Весь ECMAScript 2015 (ES6) функціонал поділяється на три групи: **доставлені**, **підготовлені** та **у процесі**:
+
+* Весь **доставлений** функціонал, який вважається у V8 стабільним, **увімкнений  у Node.js за замовчуванням** і **НЕ** потребує будь–якого флага для оточення.
+* **Підготовлений** функціонал, що містить майже готові нововведення, що розглядаються командою V8 як нестабільні, потребують флагу: `--harmony`.
+* Функціонал **у процесі** може вмикатись окремо через власні harmony–флаги, хоча це не рекомендується, за виключенням, якщо ви звісно не тестуєте цей функціонал. Зауважте: ці флаги визначаються V8 і можуть бути змінені без будь–якого попередження.
+
+## Який функціонал вже постачається з Node.js за замовчуванням?
+
+Сайт [node.green](http://node.green) надає прекрасний огляд всіх нововведень ECMAScript, що підтримуються у різних версіях Node.js, та базується на таблицях сумісності kangax.
+
+## Який функціонал знаходиться у процесі підготовки?
+
+Новий функціонал постійно додається у рушій V8. Взагалі кажучи очікується, що вони всі будуть підтримуватись у майбутньому релізі Node.js, хоча терміни поки невідомі.
+
+Ви можете побачити список всього функціоналу, що знаходиться *у процесі* в кожній версії Node.js через грепінг з аргументом `--v8-options`. Майте на увазі, що цей функціонал може бути незакінченим, або зламаним функціоналом V8, тому його використання - це ваш власний ризик:
+
+```bash
+node --v8-options | grep "in progress"
+```
+
+## В мене є мої налаштування інфраструктури, що використовують флаг --harmony. Чи слід мені відмовитись від нього?
+
+Наразі флаг `--harmony` в Node.js вмикає лише **підготовлений** функціонал. Зрештою, тепер це синонім  `--es_staging`. Як згадано вище, цей функціонал є завершеним, але ще не вважається стабільним. Якщо ви хочете використовувати його безпечно, особливо на production–середовищах, краще видалити цей флаг з оточення, поки від не буде постачатись з V8 і, відповідно, у Node.js за замовчування. Якщо ви залишите його увімкненим, вам слід бути готовими до можливих оновлень Node.js, що зламають ваш код, якщо зміни у V8, їхня семантика буде більш точно відповідати стандарту.
+
+## Як я можу дізнатись яка версія V8 постачається з певною версією Node.js?
+
+Node.js надає простий спосіб для отримання списку залежностей та їх версій, що постачаються з певним бінарником через глобальний об’єкт `process`. У випадку з рушієм V8, введіть це в терміналі і ви отримаєте його версію:
+
+```bash
+node -p process.versions.v8
+```
diff --git a/locale/uk/docs/faq.md b/locale/uk/docs/faq.md
new file mode 100755
index 0000000000000..e6497ad416244
--- /dev/null
+++ b/locale/uk/docs/faq.md
@@ -0,0 +1,19 @@
+---
+title: FAQ
+layout: docs.hbs
+---
+# FAQ
+
+## Як я можу допомогти?
+
+Будь–хто може допомогти. Node.js дотримується [правил поведінки](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-of-conduct), а співпраця, релізи та внески від спільноти керуються моделлю [відкритого керівництва](https://github.com/nodejs/node/blob/master/GOVERNANCE.md#readme).
+
+Щоб почати, почніть нову [дискусію на GitHub](https://github.com/nodejs/node/issues) — ми раді почути ваші думки. Залучення у дискусію є хорошим способом отримати розуміння того, як ви можете допомогти в подальшому. Якщо є щось, що ви можете, будь–ласка, відкрийте [зробіть пул–реквест](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-contributions).
+
+## Де відбуваються дискусії?
+
+На Freenode IRC є канал #node.js. Ми зберігаємо записи з цього каналу [тут](http://logs.libuv.org/node.js/latest).
+
+## Що таке відкрите управління?
+
+Відкрите управління виступає за застосування філософії відкритого коду та відкритого вмісту, щоб дати змогу будь–якій зацікавленій особі долучатись до створення кінцевого продукту так, як і з вікі–документом. Юридичні аспекти демократично відкриті для широких мас, що використовують свою колективну мудрість, щоб принести користь процесу прийняття рішень і вдосконалення демократії. [[source]](https://en.wikipedia.org/wiki/Open-source_governance)
diff --git a/locale/uk/docs/guides/anatomy-of-an-http-transaction.md b/locale/uk/docs/guides/anatomy-of-an-http-transaction.md
new file mode 100755
index 0000000000000..73b4d1d64f02b
--- /dev/null
+++ b/locale/uk/docs/guides/anatomy-of-an-http-transaction.md
@@ -0,0 +1,441 @@
+---
+title: Anatomy of an HTTP Transaction
+layout: docs.hbs
+---
+
+# Anatomy of an HTTP Transaction
+
+The purpose of this guide is to impart a solid understanding of the process of
+Node.js HTTP handling. We'll assume that you know, in a general sense, how HTTP
+requests work, regardless of language or programming environment. We'll also
+assume a bit of familiarity with Node.js [`EventEmitters`][] and [`Streams`][].
+If you're not quite familiar with them, it's worth taking a quick read through
+the API docs for each of those.
+
+## Create the Server
+
+Any node web server application will at some point have to create a web server
+object. This is done by using [`createServer`][].
+
+```javascript
+var http = require('http');
+
+var server = http.createServer(function(request, response) {
+  // magic happens here!
+});
+```
+
+The function that's passed in to [`createServer`][] is called once for every
+HTTP request that's made against that server, so it's called the request
+handler. In fact, the [`Server`][] object returned by [`createServer`][] is an
+[`EventEmitter`][], and what we have here is just shorthand for creating a
+`server` object and then adding the listener later.
+
+```javascript
+var server = http.createServer();
+server.on('request', function(request, response) {
+  // the same kind of magic happens here!
+});
+```
+
+When an HTTP request hits the server, node calls the request handler function
+with a few handy objects for dealing with the transaction, `request` and
+`response`. We'll get to those shortly.
+
+In order to actually serve requests, the [`listen`][] method needs to be called
+on the `server` object. In most cases, all you'll need to pass to `listen` is
+the port number you want the server to listen on. There are some other options
+too, so consult the [API reference][].
+
+## Method, URL and Headers
+
+When handling a request, the first thing you'll probably want to do is look at
+the method and URL, so that appropriate actions can be taken. Node makes this
+relatively painless by putting handy properties onto the `request` object.
+
+```javascript
+var method = request.method;
+var url = request.url;
+```
+> **Note:** The `request` object is an instance of [`IncomingMessage`][].
+
+The `method` here will always be a normal HTTP method/verb. The `url` is the
+full URL without the server, protocol or port. For a typical URL, this means
+everything after and including the third forward slash.
+
+Headers are also not far away. They're in their own object on `request` called
+`headers`.
+
+```javascript
+var headers = request.headers;
+var userAgent = headers['user-agent'];
+```
+
+It's important to note here that all headers are represented in lower-case only,
+regardless of how the client actually sent them. This simplifies the task of
+parsing headers for whatever purpose.
+
+If some headers are repeated, then their values are overwritten or joined
+together as comma-separated strings, depending on the header. In some cases,
+this can be problematic, so [`rawHeaders`][] is also available.
+
+## Request Body
+
+When receiving a `POST` or `PUT` request, the request body might be important to
+your application. Getting at the body data is a little more involved than
+accessing request headers. The `request` object that's passed in to a handler
+implements the [`ReadableStream`][] interface. This stream can be listened to or
+piped elsewhere just like any other stream. We can grab the data right out of
+the stream by listening to the stream's `'data'` and `'end'` events.
+
+The chunk emitted in each `'data'` event is a [`Buffer`][]. If you know it's
+going to be string data, the best thing to do is collect the data in an array,
+then at the `'end'`, concatenate and stringify it.
+
+```javascript
+var body = [];
+request.on('data', function(chunk) {
+  body.push(chunk);
+}).on('end', function() {
+  body = Buffer.concat(body).toString();
+  // at this point, `body` has the entire request body stored in it as a string
+});
+```
+
+> **Note:** This may seem a tad tedious, and in many cases, it is. Luckily,
+there are modules like [`concat-stream`][] and [`body`][] on [`npm`][] which can
+help hide away some of this logic. It's important to have a good understanding
+of what's going on before going down that road, and that's why you're here!
+
+## A Quick Thing About Errors
+
+Since the `request` object is a [`ReadableStream`][], it's also an
+[`EventEmitter`][] and behaves like one when an error happens.
+
+An error in the `request` stream presents itself by emitting an `'error'` event
+on the stream. **If you don't have a listener for that event, the error will be
+*thrown*, which could crash your Node.js program.** You should therefore add an
+`'error'` listener on your request streams, even if you just log it and
+continue on your way. (Though it's probably best to send some kind of HTTP error
+response. More on that later.)
+
+```javascript
+request.on('error', function(err) {
+  // This prints the error message and stack trace to `stderr`.
+  console.error(err.stack);
+});
+```
+
+There are other ways of [handling these errors][] such as
+other abstractions and tools, but always be aware that errors can and do happen,
+and you're going to have to deal with them.
+
+## What We've Got so Far
+
+At this point, we've covered creating a server, and grabbing the method, URL,
+headers and body out of requests. When we put that all together, it might look
+something like this:
+
+```javascript
+var http = require('http');
+
+http.createServer(function(request, response) {
+  var headers = request.headers;
+  var method = request.method;
+  var url = request.url;
+  var body = [];
+  request.on('error', function(err) {
+    console.error(err);
+  }).on('data', function(chunk) {
+    body.push(chunk);
+  }).on('end', function() {
+    body = Buffer.concat(body).toString();
+    // At this point, we have the headers, method, url and body, and can now
+    // do whatever we need to in order to respond to this request.
+  });
+}).listen(8080); // Activates this server, listening on port 8080.
+```
+
+If we run this example, we'll be able to *receive* requests, but not *respond*
+to them. In fact, if you hit this example in a web browser, your request would
+time out, as nothing is being sent back to the client.
+
+So far we haven't touched on the `response` object at all, which is an instance
+of [`ServerResponse`][], which is a [`WritableStream`][]. It contains many
+useful methods for sending data back to the client. We'll cover that next.
+
+## HTTP Status Code
+
+If you don't bother setting it, the HTTP status code on a response will always
+be 200. Of course, not every HTTP response warrants this, and at some point
+you'll definitely want to send a different status code. To do that, you can set
+the `statusCode` property.
+
+```javascript
+response.statusCode = 404; // Tell the client that the resource wasn't found.
+```
+
+There are some other shortcuts to this, as we'll see soon.
+
+## Setting Response Headers
+
+Headers are set through a convenient method called [`setHeader`][].
+
+```javascript
+response.setHeader('Content-Type', 'application/json');
+response.setHeader('X-Powered-By', 'bacon');
+```
+
+When setting the headers on a response, the case is insensitive on their names.
+If you set a header repeatedly, the last value you set is the value that gets
+sent.
+
+## Explicitly Sending Header Data
+
+The methods of setting the headers and status code that we've already discussed
+assume that you're using "implicit headers". This means you're counting on node
+to send the headers for you at the correct time before you start sending body
+data.
+
+If you want, you can *explicitly* write the headers to the response stream.
+To do this, there's a method called [`writeHead`][], which writes the status
+code and the headers to the stream.
+
+```javascript
+response.writeHead(200, {
+  'Content-Type': 'application/json',
+  'X-Powered-By': 'bacon'
+});
+```
+
+Once you've set the headers (either implicitly or explicitly), you're ready to
+start sending response data.
+
+## Sending Response Body
+
+Since the `response` object is a [`WritableStream`][], writing a response body
+out to the client is just a matter of using the usual stream methods.
+
+```javascript
+response.write('<html>');
+response.write('<body>');
+response.write('<h1>Hello, World!</h1>');
+response.write('</body>');
+response.write('</html>');
+response.end();
+```
+
+The `end` function on streams can also take in some optional data to send as the
+last bit of data on the stream, so we can simplify the example above as follows.
+
+```javascript
+response.end('<html><body><h1>Hello, World!</h1></body></html>');
+```
+
+> **Note:** It's important to set the status and headers *before* you start
+writing chunks of data to the body. This makes sense, since headers come before
+the body in HTTP responses.
+
+## Another Quick Thing About Errors
+
+The `response` stream can also emit `'error'` events, and at some point you're
+going to have to deal with that as well. All of the advice for `request` stream
+errors still applies here.
+
+## Put It All Together
+
+Now that we've learned about making HTTP responses, let's put it all together.
+Building on the earlier example, we're going to make a server that sends back
+all of the data that was sent to us by the user. We'll format that data as JSON
+using `JSON.stringify`.
+
+```javascript
+
+var http = require('http');
+
+http.createServer(function(request, response) {
+  var headers = request.headers;
+  var method = request.method;
+  var url = request.url;
+  var body = [];
+  request.on('error', function(err) {
+    console.error(err);
+  }).on('data', function(chunk) {
+    body.push(chunk);
+  }).on('end', function() {
+    body = Buffer.concat(body).toString();
+    // BEGINNING OF NEW STUFF
+
+    response.on('error', function(err) {
+      console.error(err);
+    });
+
+    response.statusCode = 200;
+    response.setHeader('Content-Type', 'application/json');
+    // Note: the 2 lines above could be replaced with this next one:
+    // response.writeHead(200, {'Content-Type': 'application/json'})
+
+    var responseBody = {
+      headers: headers,
+      method: method,
+      url: url,
+      body: body
+    };
+
+    response.write(JSON.stringify(responseBody));
+    response.end();
+    // Note: the 2 lines above could be replaced with this next one:
+    // response.end(JSON.stringify(responseBody))
+
+    // END OF NEW STUFF
+  });
+}).listen(8080);
+```
+
+## Echo Server Example
+
+Let's simplify the previous example to make a simple echo server, which just
+sends whatever data is received in the request right back in the response. All
+we need to do is grab the data from the request stream and write that data to
+the response stream, similar to what we did previously.
+
+```javascript
+var http = require('http');
+
+http.createServer(function(request, response) {
+  var body = [];
+  request.on('data', function(chunk) {
+    body.push(chunk);
+  }).on('end', function() {
+    body = Buffer.concat(body).toString();
+    response.end(body);
+  });
+}).listen(8080);
+```
+
+Now let's tweak this. We want to only send an echo under the following
+conditions:
+
+* The request method is GET.
+* The URL is `/echo`.
+
+In any other case, we want to simply respond with a 404.
+
+```javascript
+var http = require('http');
+
+http.createServer(function(request, response) {
+  if (request.method === 'GET' && request.url === '/echo') {
+    var body = [];
+    request.on('data', function(chunk) {
+      body.push(chunk);
+    }).on('end', function() {
+      body = Buffer.concat(body).toString();
+      response.end(body);
+    })
+  } else {
+    response.statusCode = 404;
+    response.end();
+  }
+}).listen(8080);
+```
+
+> **Note:** By checking the URL in this way, we're doing a form of "routing".
+Other forms of routing can be as simple as `switch` statements or as complex as
+whole frameworks like [`express`][]. If you're looking for something that does
+routing and nothing else, try [`router`][].
+
+Great! Now let's take a stab at simplifying this. Remember, the `request` object
+is a [`ReadableStream`][] and the `response` object is a [`WritableStream`][].
+That means we can use [`pipe`][] to direct data from one to the other. That's
+exactly what we want for an echo server!
+
+```javascript
+var http = require('http');
+
+http.createServer(function(request, response) {
+  if (request.method === 'GET' && request.url === '/echo') {
+    request.pipe(response);
+  } else {
+    response.statusCode = 404;
+    response.end();
+  }
+}).listen(8080);
+```
+
+Yay streams!
+
+We're not quite done yet though. As mentioned multiple times in this guide,
+errors can and do happen, and we need to deal with them.
+
+To handle errors on the request stream, we'll log the error to `stderr` and send
+a 400 status code to indicate a `Bad Request`. In a real-world application,
+though, we'd want to inspect the error to figure out what the correct status code
+and message would be. As usual with errors, you should consult the
+[`Error` documentation][].
+
+On the response, we'll just log the error to `stdout`.
+
+```javascript
+var http = require('http');
+
+http.createServer(function(request, response) {
+  request.on('error', function(err) {
+    console.error(err);
+    response.statusCode = 400;
+    response.end();
+  });
+  response.on('error', function(err) {
+    console.error(err);
+  });
+  if (request.method === 'GET' && request.url === '/echo') {
+    request.pipe(response);
+  } else {
+    response.statusCode = 404;
+    response.end();
+  }
+}).listen(8080);
+```
+
+We've now covered most of the basics of handling HTTP requests. At this point,
+you should be able to:
+
+* Instantiate an HTTP server with a request handler function, and have it listen
+on a port.
+* Get headers, URL, method and body data from `request` objects.
+* Make routing decisions based on URL and/or other data in `request` objects.
+* Send headers, HTTP status codes and body data via `response` objects.
+* Pipe data from `request` objects and to `response` objects.
+* Handle stream errors in both the `request` and `response` streams.
+
+From these basics, Node.js HTTP servers for many typical use cases can be
+constructed. There are plenty of other things these APIs provide, so be sure to
+read through the API docs for [`EventEmitters`][], [`Streams`][], and [`HTTP`][].
+
+
+
+[`EventEmitters`]: https://nodejs.org/api/events.html
+[`Streams`]: https://nodejs.org/api/stream.html
+[`createServer`]: https://nodejs.org/api/http.html#http_http_createserver_requestlistener
+[`Server`]: https://nodejs.org/api/http.html#http_class_http_server
+[`listen`]: https://nodejs.org/api/http.html#http_server_listen_port_hostname_backlog_callback
+[API reference]: https://nodejs.org/api/http.html
+[`IncomingMessage`]: https://nodejs.org/api/http.html#http_class_http_incomingmessage
+[`ReadableStream`]: https://nodejs.org/api/stream.html#stream_class_stream_readable
+[`rawHeaders`]: https://nodejs.org/api/http.html#http_message_rawheaders
+[`Buffer`]: https://nodejs.org/api/buffer.html
+[`concat-stream`]: https://www.npmjs.com/package/concat-stream
+[`body`]: https://www.npmjs.com/package/body
+[`npm`]: https://www.npmjs.com
+[`EventEmitter`]: https://nodejs.org/api/events.html#events_class_eventemitter
+[handling these errors]: https://nodejs.org/api/errors.html
+[`domains`]: https://nodejs.org/api/domain.html
+[`ServerResponse`]: https://nodejs.org/api/http.html#http_class_http_serverresponse
+[`setHeader`]: https://nodejs.org/api/http.html#http_response_setheader_name_value
+[`WritableStream`]: https://nodejs.org/api/stream.html#stream_class_stream_writable
+[`writeHead`]: https://nodejs.org/api/http.html#http_response_writehead_statuscode_statusmessage_headers
+[`express`]: https://www.npmjs.com/package/express
+[`router`]: https://www.npmjs.com/package/router
+[`pipe`]: https://nodejs.org/api/stream.html#stream_readable_pipe_destination_options
+[`Error` documentation]: https://nodejs.org/api/errors.html
+[`HTTP`]: https://nodejs.org/api/http.html
diff --git a/locale/uk/docs/guides/index.md b/locale/uk/docs/guides/index.md
new file mode 100755
index 0000000000000..5b657e81fa3d9
--- /dev/null
+++ b/locale/uk/docs/guides/index.md
@@ -0,0 +1,6 @@
+---
+title: Керівництва
+layout: guides-index.hbs
+---
+
+# Guides
diff --git a/locale/uk/docs/guides/nodejs-docker-webapp.md b/locale/uk/docs/guides/nodejs-docker-webapp.md
new file mode 100755
index 0000000000000..373375694da4c
--- /dev/null
+++ b/locale/uk/docs/guides/nodejs-docker-webapp.md
@@ -0,0 +1,240 @@
+---
+title: Dockerizing a Node.js web app
+layout: docs.hbs
+---
+
+# Dockerizing a Node.js web app
+
+The goal of this example is to show you how to get a Node.js application into a
+Docker container. The guide is intended for development, and *not* for a
+production deployment. The guide also assumes you have a working [Docker
+installation](https://docs.docker.com/engine/installation/) and a basic
+understanding of how a Node.js application is structured.
+
+In the first part of this guide we will create a simple web application in
+Node.js, then we will build a Docker image for that application, and lastly we
+will run the image as a container.
+
+Docker allows you to package an application with all of its dependencies into a
+standardized unit, called a container, for software development. A container is
+a stripped-to-basics version of a Linux operating system. An image is software
+you load into a container.
+
+## Create the Node.js app
+
+First, create a new directory where all the files would live. In this directory
+create a `package.json` file that describes your app and its dependencies:
+
+```javascript
+{
+  "name": "docker_web_app",
+  "version": "1.0.0",
+  "description": "Node.js on Docker",
+  "author": "First Last <first.last@example.com>",
+  "main": "server.js",
+  "scripts": {
+    "start": "node server.js"
+  },
+  "dependencies": {
+    "express": "^4.13.3"
+  }
+}
+```
+
+Then, create a `server.js` file that defines a web app using the
+[Express.js](http://expressjs.com/) framework:
+
+```javascript
+'use strict';
+
+const express = require('express');
+
+// Constants
+const PORT = 8080;
+
+// App
+const app = express();
+app.get('/', function (req, res) {
+  res.send('Hello world\n');
+});
+
+app.listen(PORT);
+console.log('Running on http://localhost:' + PORT);
+```
+
+In the next steps, we'll look at how you can run this app inside a Docker
+container using the official Docker image. First, you'll need to build a Docker
+image of your app.
+
+## Creating a Dockerfile
+
+Create an empty file called `Dockerfile`:
+
+```markup
+touch Dockerfile
+```
+
+Open the `Dockerfile` in your favorite text editor
+
+The first thing we need to do is define from what image we want to build from.
+Here we will use the latest LTS (long term support) version `argon` of `node`
+available from the [Docker Hub](https://hub.docker.com/):
+
+```docker
+FROM node:argon
+```
+
+Next we create a directory to hold the application code inside the image, this
+will be the working directory for your application:
+
+```docker
+# Create app directory
+RUN mkdir -p /usr/src/app
+WORKDIR /usr/src/app
+```
+
+This image comes with Node.js and NPM already installed so the next thing we
+need to do is to install your app dependencies using the `npm` binary:
+
+```docker
+# Install app dependencies
+COPY package.json /usr/src/app/
+RUN npm install
+```
+
+To bundle your app's source code inside the Docker image, use the `COPY`
+instruction:
+
+```docker
+# Bundle app source
+COPY . /usr/src/app
+```
+
+Your app binds to port `8080` so you'll use the `EXPOSE` instruction to have it
+mapped by the `docker` daemon:
+
+```docker
+EXPOSE 8080
+```
+
+Last but not least, define the command to run your app using `CMD` which defines
+your runtime. Here we will use the basic `npm start` which will run 
+`node server.js` to start your server:
+
+```docker
+CMD [ "npm", "start" ]
+```
+
+Your `Dockerfile` should now look like this:
+
+```docker
+FROM node:argon
+
+# Create app directory
+RUN mkdir -p /usr/src/app
+WORKDIR /usr/src/app
+
+# Install app dependencies
+COPY package.json /usr/src/app/
+RUN npm install
+
+# Bundle app source
+COPY . /usr/src/app
+
+EXPOSE 8080
+CMD [ "npm", "start" ]
+```
+
+## Building your image
+
+Go to the directory that has your `Dockerfile` and run the following command to
+build the Docker image. The `-t` flag lets you tag your image so it's easier to
+find later using the `docker images` command:
+
+```bash
+$ docker build -t <your username>/node-web-app .
+```
+
+Your image will now be listed by Docker:
+
+```bash
+$ docker images
+
+# Example
+REPOSITORY                      TAG        ID              CREATED
+node                            argon      539c0211cd76    3 weeks ago
+<your username>/node-web-app    latest     d64d3505b0d2    1 minute ago
+```
+
+## Run the image
+
+Running your image with `-d` runs the container in detached mode, leaving the
+container running in the background. The `-p` flag redirects a public port to a
+private port inside the container. Run the image you previously built:
+
+```bash
+$ docker run -p 49160:8080 -d <your username>/node-web-app
+```
+
+Print the output of your app:
+
+```bash
+# Get container ID
+$ docker ps
+
+# Print app output
+$ docker logs <container id>
+
+# Example
+Running on http://localhost:8080
+```
+
+If you need to go inside the container you can use the `exec` command:
+
+```bash
+# Enter the container
+$ docker exec -it <container id> /bin/bash
+```
+
+## Test
+
+To test your app, get the port of your app that Docker mapped:
+
+```bash
+$ docker ps
+
+# Example
+ID            IMAGE                                COMMAND    ...   PORTS
+ecce33b30ebf  <your username>/node-web-app:latest  npm start  ...   49160->8080
+```
+
+In the example above, Docker mapped the `8080` port inside of the container to
+the port `49160` on your machine.
+
+Now you can call your app using `curl` (install if needed via: `sudo apt-get
+install curl`):
+
+```bash
+$ curl -i localhost:49160
+
+HTTP/1.1 200 OK
+X-Powered-By: Express
+Content-Type: text/html; charset=utf-8
+Content-Length: 12
+Date: Sun, 02 Jun 2013 03:53:22 GMT
+Connection: keep-alive
+
+Hello world
+```
+
+We hope this tutorial helped you get up and running a simple Node.js application
+on Docker.
+
+You can find more information about Docker and Node.js on Docker in the
+following places:
+
+* [Official Node.js Docker Image](https://registry.hub.docker.com/_/node/)
+* [Node.js Docker Best Practices Guide](https://github.com/nodejs/docker-node/blob/master/docs/BestPractices.md)
+* [Official Docker documentation](https://docs.docker.com/)
+* [Docker Tag on StackOverflow](http://stackoverflow.com/questions/tagged/docker)
+* [Docker Subreddit](https://reddit.com/r/docker)
diff --git a/locale/uk/docs/guides/simple-profiling.md b/locale/uk/docs/guides/simple-profiling.md
new file mode 100755
index 0000000000000..9baf1d41f9436
--- /dev/null
+++ b/locale/uk/docs/guides/simple-profiling.md
@@ -0,0 +1,282 @@
+---
+title: Easy profiling for Node.js Applications
+layout: docs.hbs
+---
+
+# Easy profiling for Node.js Applications
+
+There are many third party tools available for profiling Node.js applications
+but, in many cases, the easiest option is to use the Node.js built in profiler.
+The built in profiler uses the [profiler inside V8][] which samples the stack at
+regular intervals during program execution. It records the results of these
+samples, along with important optimization events such as jit compiles, as a
+series of ticks:
+
+```
+code-creation,LazyCompile,0,0x2d5000a337a0,396,"bp native array.js:1153:16",0x289f644df68,~
+code-creation,LazyCompile,0,0x2d5000a33940,716,"hasOwnProperty native v8natives.js:198:30",0x289f64438d0,~
+code-creation,LazyCompile,0,0x2d5000a33c20,284,"ToName native runtime.js:549:16",0x289f643bb28,~
+code-creation,Stub,2,0x2d5000a33d40,182,"DoubleToIStub"
+code-creation,Stub,2,0x2d5000a33e00,507,"NumberToStringStub"
+```
+
+In the past you need the V8 source code to be able to interpret the ticks.
+Luckily, tools have recently been introduced into Node.js 4.4.0 that facilitate
+the consumption of this information without separately building V8 from source.
+Let's see how the built-in profiler can help provide insight into application
+performance.
+
+To illustrate the use of the tick profiler, we will work with a simple Express
+application. Our application will have two handlers, one for adding new users to
+our system:
+
+```javascript
+app.get('/newUser', function (req, res) {
+  var username = req.query.username || '';
+  var password = req.query.password || '';
+
+  username = username.replace(/[!@#$%^&*]/g, '');
+
+  if (!username || !password || users.username) {
+    return res.sendStatus(400);
+  }
+
+  var salt = crypto.randomBytes(128).toString('base64');
+  var hash = crypto.pbkdf2Sync(password, salt, 10000, 512);
+
+  users[username] = {
+    salt: salt,
+    hash: hash
+  };
+
+  res.sendStatus(200);
+});
+```
+
+and another for validating user authentication attempts:
+
+```javascript
+app.get('/auth', function (req, res) {
+  var username = req.query.username || '';
+  var password = req.query.password || '';
+
+  username = username.replace(/[!@#$%^&*]/g, '');
+
+  if (!username || !password || !users[username]) {
+    return res.sendStatus(400);
+  }
+
+  var hash = crypto.pbkdf2Sync(password, users[username].salt, 10000, 512);
+
+  if (users[username].hash.toString() === hash.toString()) {
+    res.sendStatus(200);
+  } else {
+    res.sendStatus(401);
+  }
+});
+```
+
+*Please note that these are NOT recommended handlers for authenticating users in
+your Node.js applications and are used purely for illustration purposes. You
+should not be trying to design your own cryptographic authentication mechanisms
+in general. It is much better to use existing, proven authentication solutions.*
+
+Now assume that we've deployed our application and users are complaining about
+high latency on requests. We can easily run the app with the built in profiler:
+
+```
+NODE_ENV=production node --prof app.js
+```
+
+and put some load on the server using ab:
+
+```
+curl -X GET "http://localhost:8080/newUser?username=matt&password=password"
+ab -k -c 20 -n 250 "http://localhost:8080/auth?username=matt&password=password"
+```
+
+and get an ab output of:
+
+```
+Concurrency Level:      20
+Time taken for tests:   46.932 seconds
+Complete requests:      250
+Failed requests:        0
+Keep-Alive requests:    250
+Total transferred:      50250 bytes
+HTML transferred:       500 bytes
+Requests per second:    5.33 [#/sec] (mean)
+Time per request:       3754.556 [ms] (mean)
+Time per request:       187.728 [ms] (mean, across all concurrent requests)
+Transfer rate:          1.05 [Kbytes/sec] received
+
+...
+
+Percentage of the requests served within a certain time (ms)
+  50%   3755
+  66%   3804
+  75%   3818
+  80%   3825
+  90%   3845
+  95%   3858
+  98%   3874
+  99%   3875
+ 100%   4225 (longest request)
+```
+
+From this output, we see that we're only managing to serve about 5 requests per
+second and that the average request takes just under 4 seconds round trip. In a
+real world example, we could be doing lots of work in many functions on behalf
+of a user request but even in our simple example, time could be lost compiling
+regular expressions, generating random salts, generating unique hashes from user
+passwords, or inside the Express framework itself.
+
+Since we ran our application using the `--prof` option, a tick file was generated
+in the same directory as your local run of the application. It should have the
+form `isolate-0xnnnnnnnnnnnn-v8.log` (where `n` is a digit).
+
+In order to make sense of this file, we need to use the tick processor bundled
+with the Node.js binary. To run the processor, use the `--prof-process` flag:
+
+```
+node --prof-process isolate-0xnnnnnnnnnnnn-v8.log > processed.txt
+```
+
+Opening processed.txt in your favorite text editor will give you a few different
+types of information. The file is broken up into sections which are again broken
+up by language. First, we look at the summary section and see:
+
+```
+ [Summary]:
+   ticks  total  nonlib   name
+     79    0.2%    0.2%  JavaScript
+  36703   97.2%   99.2%  C++
+      7    0.0%    0.0%  GC
+    767    2.0%          Shared libraries
+    215    0.6%          Unaccounted
+```
+
+This tells us that 97% of all samples gathered occurred in C++ code and that
+when viewing other sections of the processed output we should pay most attention
+to work being done in C++ (as opposed to Javascript). With this in mind, we next
+find the [C++] section which contains information about which C++ functions are
+taking the most CPU time and see:
+
+```
+ [C++]:
+   ticks  total  nonlib   name
+  19557   51.8%   52.9%  node::crypto::PBKDF2(v8::FunctionCallbackInfo<v8::Value> const&)
+   4510   11.9%   12.2%  _sha1_block_data_order
+   3165    8.4%    8.6%  _malloc_zone_malloc
+```
+
+We see that the top 3 entries account for 72.1% of CPU time taken by the
+program. From this output, we immediately see that at least 51.8% of CPU time is
+taken up by a function called PBKDF2 which corresponds to our hash generation
+from a user's password. However, it may not be immediately obvious how the lower
+two entries factor into our application (or if it is we will pretend otherwise
+for the sake of example). To better understand the relationship between these
+functions, we will next look at the [Bottom up (heavy) profile] section which
+provides information about the primary callers of each function. Examining this
+section, we find:
+
+```
+   ticks parent  name
+  19557   51.8%  node::crypto::PBKDF2(v8::FunctionCallbackInfo<v8::Value> const&)
+  19557  100.0%    v8::internal::Builtins::~Builtins()
+  19557  100.0%      LazyCompile: ~pbkdf2 crypto.js:557:16
+
+   4510   11.9%  _sha1_block_data_order
+   4510  100.0%    LazyCompile: *pbkdf2 crypto.js:557:16
+   4510  100.0%      LazyCompile: *exports.pbkdf2Sync crypto.js:552:30
+
+   3165    8.4%  _malloc_zone_malloc
+   3161   99.9%    LazyCompile: *pbkdf2 crypto.js:557:16
+   3161  100.0%      LazyCompile: *exports.pbkdf2Sync crypto.js:552:30
+```
+
+Parsing this section takes a little more work than the raw tick counts above.
+Within each of the "call stacks" above, the percentage in the parent column
+tells you the percentage of samples for which the function in the row above was
+called by the function in the current row. For example, in the middle "call
+stack" above for _sha1_block_data_order, we see that _sha1_block_data_order occurred
+in 11.9% of samples, which we knew from the raw counts above. However, here, we
+can also tell that it was always called by the pbkdf2 function inside the
+Node.js crypto module. We see that similarly, _malloc_zone_malloc was called
+almost exclusively by the same pbkdf2 function. Thus, using the information in
+this view, we can tell that our hash computation from the user's password
+accounts not only for the 51.8% from above but also for all CPU time in the top
+3 most sampled functions since the calls to _sha1_block_data_order and
+_malloc_zone_malloc were made on behalf of the pbkdf2 function.
+
+At this point, it is very clear that the password based hash generation should
+be the target of our optimization. Thankfully, you've fully internalized the
+[benefits of asynchronous programming][] and you realize that the work to
+generate a hash from the user's password is being done in a synchronous way and
+thus tying down the event loop. This prevents us from working on other incoming
+requests while computing a hash.
+
+To remedy this issue, you make a small modification to the above handlers to use
+the asynchronous version of the pbkdf2 function:
+
+```javascript
+app.get('/auth', function (req, res) {
+  var username = req.query.username || '';
+  var password = req.query.password || '';
+
+  username = username.replace(/[!@#$%^&*]/g, '');
+
+  if (!username || !password || !users[username]) {
+    return res.sendStatus(400);
+  }
+
+  crypto.pbkdf2(password, users[username].salt, 10000, 512, function(err, hash) {
+    if (users[username].hash.toString() === hash.toString()) {
+      res.sendStatus(200);
+    } else {
+      res.sendStatus(401);
+    }
+  });
+});
+```
+
+A new run of the ab benchmark above with the asynchronous version of your app
+yields:
+
+```
+Concurrency Level:      20
+Time taken for tests:   12.846 seconds
+Complete requests:      250
+Failed requests:        0
+Keep-Alive requests:    250
+Total transferred:      50250 bytes
+HTML transferred:       500 bytes
+Requests per second:    19.46 [#/sec] (mean)
+Time per request:       1027.689 [ms] (mean)
+Time per request:       51.384 [ms] (mean, across all concurrent requests)
+Transfer rate:          3.82 [Kbytes/sec] received
+
+...
+
+Percentage of the requests served within a certain time (ms)
+  50%   1018
+  66%   1035
+  75%   1041
+  80%   1043
+  90%   1049
+  95%   1063
+  98%   1070
+  99%   1071
+ 100%   1079 (longest request)
+```
+
+Yay! Your app is now serving about 20 requests per second, roughly 4 times more
+than it was with the synchronous hash generation. Additionally, the average
+latency is down from the 4 seconds before to just over 1 second.
+
+Hopefully, through the performance investigation of this (admittedly contrived)
+example, you've seen how the V8 tick processor can help you gain a better
+understanding of the performance of your Node.js applications.
+
+[profiler inside V8]: https://developers.google.com/v8/profiler_example
+[benefits of asynchronous programming]: https://nodesource.com/blog/why-asynchronous
diff --git a/locale/uk/docs/guides/working-with-different-filesystems.md b/locale/uk/docs/guides/working-with-different-filesystems.md
new file mode 100755
index 0000000000000..36494b9bb1642
--- /dev/null
+++ b/locale/uk/docs/guides/working-with-different-filesystems.md
@@ -0,0 +1,224 @@
+---
+title: Working with Different Filesystems
+layout: docs.hbs
+---
+
+# Working with Different Filesystems
+
+Node exposes many features of the filesystem. But not all filesystems are alike.
+The following are suggested best practices to keep your code simple and safe
+when working with different filesystems.
+
+## Filesystem Behavior
+
+Before you can work with a filesystem, you need to know how it behaves.
+Different filesystems behave differently and have more or less features than
+others: case sensitivity, case insensitivity, case preservation, Unicode form
+preservation, timestamp resolution, extended attributes, inodes, Unix
+permissions, alternate data streams etc.
+
+Be wary of inferring filesystem behavior from `process.platform`. For example,
+do not assume that because your program is running on Darwin that you are
+therefore working on a case-insensitive filesystem (HFS+), as the user may be
+using a case-sensitive filesystem (HFSX). Similarly, do not assume that because
+your program is running on Linux that you are therefore working on a filesystem
+which supports Unix permissions and inodes, as you may be on a particular
+external drive, USB or network drive which does not.
+
+The operating system may not make it easy to infer filesystem behavior, but all
+is not lost. Instead of keeping a list of every known filesystem and behavior
+(which is always going to be incomplete), you can probe the filesystem to see
+how it actually behaves. The presence or absence of certain features which are
+easy to probe, are often enough to infer the behavior of other features which
+are more difficult to probe.
+
+Remember that some users may have different filesystems mounted at various paths
+in the working tree.
+
+## Avoid a Lowest Common Denominator Approach
+
+You might be tempted to make your program act like a lowest common denominator
+filesystem, by normalizing all filenames to uppercase, normalizing all filenames
+to NFC Unicode form, and normalizing all file timestamps to say 1-second
+resolution. This would be the lowest common denominator approach.
+
+Do not do this. You would only be able to interact safely with a filesystem
+which has the exact same lowest common denominator characteristics in every
+respect. You would be unable to work with more advanced filesystems in the way
+that users expect, and you would run into filename or timestamp collisions. You
+would most certainly lose and corrupt user data through a series of complicated
+dependent events, and you would create bugs that would be difficult if not
+impossible to solve.
+
+What happens when you later need to support a filesystem that only has 2-second
+or 24-hour timestamp resolution? What happens when the Unicode standard advances
+to include a slightly different normalization algorithm (as has happened in the
+past)?
+
+A lowest common denominator approach would tend to try to create a portable
+program by using only "portable" system calls. This leads to programs that are
+leaky and not in fact portable.
+
+## Adopt a Superset Approach
+
+Make the best use of each platform you support by adopting a superset approach.
+For example, a portable backup program should sync btimes (the created time of a
+file or folder) correctly between Windows systems, and should not destroy or
+alter btimes, even though btimes are not supported on Linux systems. The same
+portable backup program should sync Unix permissions correctly between Linux
+systems, and should not destroy or alter Unix permissions, even though Unix
+permissions are not supported on Windows systems.
+
+Handle different filesystems by making your program act like a more advanced
+filesystem. Support a superset of all possible features: case-sensitivity,
+case-preservation, Unicode form sensitivity, Unicode form preservation, Unix
+permissions, high-resolution nanosecond timestamps, extended attributes etc.
+
+Once you have case-preservation in your program, you can always implement
+case-insensitivity if you need to interact with a case-insensitive filesystem.
+But if you forego case-preservation in your program, you cannot interact safely
+with a case-preserving filesystem. The same is true for Unicode form
+preservation and timestamp resolution preservation.
+
+If a filesystem provides you with a filename in a mix of lowercase and
+uppercase, then keep the filename in the exact case given. If a filesystem
+provides you with a filename in mixed Unicode form or NFC or NFD (or NFKC or
+NFKD), then keep the filename in the exact byte sequence given. If a filesystem
+provides you with a millisecond timestamp, then keep the timestamp in
+millisecond resolution.
+
+When you work with a lesser filesystem, you can always downsample appropriately,
+with comparison functions as required by the behavior of the filesystem on which
+your program is running. If you know that the filesystem does not support Unix
+permissions, then you should not expect to read the same Unix permissions you
+write. If you know that the filesystem does not preserve case, then you should
+be prepared to see `ABC` in a directory listing when your program creates `abc`.
+But if you know that the filesystem does preserve case, then you should consider
+`ABC` to be a different filename to `abc`, when detecting file renames or if the
+filesystem is case-sensitive.
+
+## Case Preservation
+
+You may create a directory called `test/abc` and be surprised to see sometimes
+that `fs.readdir('test')` returns `['ABC']`. This is not a bug in Node. Node
+returns the filename as the filesystem stores it, and not all filesystems
+support case-preservation. Some filesystems convert all filenames to uppercase
+(or lowercase).
+
+## Unicode Form Preservation
+
+*Case preservation and Unicode form preservation are similar concepts. To
+understand why Unicode form should be preserved , make sure that you first
+understand why case should be preserved. Unicode form preservation is just as
+simple when understood correctly.*
+
+Unicode can encode the same characters using several different byte sequences.
+Several strings may look the same, but have different byte sequences. When
+working with UTF-8 strings, be careful that your expectations are in line with
+how Unicode works. Just as you would not expect all UTF-8 characters to encode
+to a single byte, you should not expect several UTF-8 strings that look the same
+to the human eye to have the same byte representation. This may be an
+expectation that you can have of ASCII, but not of UTF-8.
+
+You may create a directory called `test/café` (NFC Unicode form with byte
+sequence `<63 61 66 c3 a9>` and `string.length === 5`) and be surprised to see
+sometimes that `fs.readdir('test')` returns `['café']` (NFD Unicode form with
+byte sequence `<63 61 66 65 cc 81>` and `string.length === 6`). This is not a
+bug in Node. Node returns the filename as the filesystem stores it, and not all
+filesystems support Unicode form preservation.
+
+HFS+, for example, will normalize all filenames to a form almost always the same
+as NFD form. Do not expect HFS+ to behave the same as NTFS or EXT4 and
+vice-versa. Do not try to change data permanently through normalization as a
+leaky abstraction to paper over Unicode differences between filesystems. This
+would create problems without solving any. Rather, preserve Unicode form and use
+normalization as a comparison function only.
+
+## Unicode Form Insensitivity
+
+Unicode form insensitivity and Unicode form preservation are two different
+filesystem behaviors often mistaken for each other. Just as case-insensitivity
+has sometimes been incorrectly implemented by permanently normalizing filenames
+to uppercase when storing and transmitting filenames, so Unicode form
+insensitivity has sometimes been incorrectly implemented by permanently
+normalizing filenames to a certain Unicode form (NFD in the case of HFS+) when
+storing and transmitting filenames. It is possible and much better to implement
+Unicode form insensitivity without sacrificing Unicode form preservation, by
+using Unicode normalization for comparison only.
+
+## Comparing Different Unicode Forms
+
+Node provides `string.normalize('NFC' / 'NFD')` which you can use to normalize a
+UTF-8 string to either NFC or NFD. You should never store the output from this
+function but only use it as part of a comparison function to test whether two
+UTF-8 strings would look the same to the user.
+
+You can use `string1.normalize('NFC') === string2.normalize('NFC')` or
+`string1.normalize('NFD') === string2.normalize('NFD')` as your comparison
+function. Which form you use does not matter.
+
+Normalization is fast but you may want to use a cache as input to your
+comparison function to avoid normalizing the same string many times over. If the
+string is not present in the cache then normalize it and cache it. Be careful
+not to store or persist the cache, use it only as a cache.
+
+Note that using `normalize()` requires that your version of Node include ICU
+(otherwise `normalize()` will just return the original string). If you download
+the latest version of Node from the website then it will include ICU.
+
+## Timestamp Resolution
+
+You may set the `mtime` (the modified time) of a file to `1444291759414`
+(millisecond resolution) and be surprised to see sometimes that `fs.stat`
+returns the new mtime as `1444291759000` (1-second resolution) or
+`1444291758000` (2-second resolution). This is not a bug in Node. Node returns
+the timestamp as the filesystem stores it, and not all filesystems support
+nanosecond, millisecond or 1-second timestamp resolution. Some filesystems even
+have very coarse resolution for the atime timestamp in particular, e.g. 24 hours
+for some FAT filesystems.
+
+## Do Not Corrupt Filenames and Timestamps Through Normalization
+
+Filenames and timestamps are user data. Just as you would never automatically
+rewrite user file data to uppercase the data or normalize `CRLF` to `LF`
+line-endings, so you should never change, interfere or corrupt filenames or
+timestamps through case / Unicode form / timestamp normalization. Normalization
+should only ever be used for comparison, never for altering data.
+
+Normalization is effectively a lossy hash code. You can use it to test for
+certain kinds of equivalence (e.g. do several strings look the same even though
+they have different byte sequences) but you can never use it as a substitute for
+the actual data. Your program should pass on filename and timestamp data as is.
+
+Your program can create new data in NFC (or in any combination of Unicode form
+it prefers) or with a lowercase or uppercase filename, or with a 2-second
+resolution timestamp, but your program should not corrupt existing user data by
+imposing case / Unicode form / timestamp normalization. Rather, adopt a superset
+approach and preserve case, Unicode form and timestamp resolution in your
+program. That way, you will be able to interact safely with filesystems which do
+the same.
+
+## Use Normalization Comparison Functions Appropriately
+
+Make sure that you use case / Unicode form / timestamp comparison functions
+appropriately. Do not use a case-insensitive filename comparison function if you
+are working on a case-sensitive filesystem. Do not use a Unicode form
+insensitive comparison function if you are working on a Unicode form sensitive
+filesystem (e.g. NTFS and most Linux filesystems which preserve both NFC and NFD
+or mixed Unicode forms). Do not compare timestamps at 2-second resolution if you
+are working on a nanosecond timestamp resolution filesystem.
+
+## Be Prepared for Slight Differences in Comparison Functions
+
+Be careful that your comparison functions match those of the filesystem (or
+probe the filesystem if possible to see how it would actually compare).
+Case-insensitivity for example is more complex than a simple `toLowerCase()`
+comparison. In fact, `toUpperCase()` is usually better than `toLowerCase()`
+(since it handles certain foreign language characters differently). But better
+still would be to probe the filesystem since every filesystem has its own case
+comparison table baked in.
+
+As an example, Apple's HFS+ normalizes filenames to NFD form but this NFD form
+is actually an older version of the current NFD form and may sometimes be
+slightly different from the latest Unicode standard's NFD form. Do not expect
+HFS+ NFD to be exactly the same as Unicode NFD all the time.
diff --git a/locale/uk/docs/index.md b/locale/uk/docs/index.md
new file mode 100755
index 0000000000000..ae83221bbdcee
--- /dev/null
+++ b/locale/uk/docs/index.md
@@ -0,0 +1,39 @@
+---
+title: Документація
+layout: docs.hbs
+labels:
+  lts: LTS
+---
+
+# Про документацію
+
+Є три типи документації, що доступні на цьому сайті:
+
+* довідкова документація про API;
+* функціонал ES6;
+* часті запитання.
+
+### Довідкова документація про API
+
+[Довідкова документація про API](/api/) надає детальну інформацію про функції та об’єкти у Node.js. Ця документація показує які аргументи приймають методи, які значення ці методи повертають та які помилки пов'язані з цими методами. Вона також показує які методи доступні для різних версій Node.js.
+
+Ця документація описує вбудовані модулі, які надаються Node.js. Вона не документує модулі, що надаються спільнотою.
+
+<div class="highlight-box">
+    <h4>Шукаєте документацію про API для попередніх релізів?</h4>
+
+    <ul>
+        <li><a href="https://nodejs.org/docs/latest-v5.x/api/">Node.js 5.x</a></li>
+        <li><a href="https://nodejs.org/docs/latest-v0.12.x/api/">Node.js 0.12.x</a></li>
+        <li><a href="https://nodejs.org/docs/latest-v0.10.x/api/">Node.js 0.10.x</a></li>
+        <li><a href="https://nodejs.org/docs/">всі версії</a></li>
+    </ul>
+</div>
+
+### Функціонал ES6
+
+[Секція ES6](/en/docs/es6/) описує три групи функціоналу ES6 і описує який функціонал наразі доступний у Node.js за замовчуванням разом з пояснювальними посиланнями. Вона також показує звідки дізнатись яка версія V8 постачається з певним релізом Node.js.
+
+### Часті запитання
+
+[FAQ](/en/docs/faq/) покриває ту частину інформації, яка пояснює як будь–хто може зробити свій внесок у Node.js, наші правила поведінки та модель управління, як бути в курсі справ на GitHub та IRC і як допомогти з впорядкуванням іш’ю.
diff --git a/locale/uk/docs/meta/topics/dependencies.md b/locale/uk/docs/meta/topics/dependencies.md
new file mode 100755
index 0000000000000..6e7a44eabdb3c
--- /dev/null
+++ b/locale/uk/docs/meta/topics/dependencies.md
@@ -0,0 +1,94 @@
+---
+title: Залежності
+layout: docs.hbs
+---
+
+# Залежності
+
+Node.js використовує кілька залежностей, на які використовуються для забезпечення його роботи.
+
+- [Бібліотеки](#Бібліотеки)
+  - [V8](#V8)
+  - [libuv](#libuv)
+  - [http-parser](#http-parser)
+  - [c-ares](#c-ares)
+  - [OpenSSL](#OpenSSL)
+  - [zlib](#zlib)
+- [Інструменти](#Інструменти)
+  - [npm](#npm)
+  - [gyp](#gyp)
+  - [gtest](#gtest)
+
+## Бібліотеки
+
+### V8
+
+Бібліотека V8 надає Node.js JavaScript–рушій, який Node.js керується через V8 C++ API. V8 підтримується Google для використання у Chrome.
+
+- [Документація](https://v8docs.nodesource.com/)
+
+### libuv
+
+Іншою важливою залежністю є libuv, C–бібліотека, що використовується для
+абстрагування неблокуючих I/O–операцій у консистентний інтерфейс
+для всіх платформ, що підтримуються. Вона надає механізм для маніпуляцій
+файловою системою, DNS, мережею, дочірними процесами, пайпами,
+сигналами, запитами та потоками. Вона також включає тред для розвантаження
+роботи, що може бути виконана асинхронно на рівні операційної системи.
+
+- [Документація](http://docs.libuv.org/)
+
+### http-parser
+
+Парсинг HTTP відбувається з допомогою легкої С–бібліотеки,
+яка називається http-parser. Вона спроектована так, щоб не робити жодних
+системних викликів або алокацій, тому вона використовує дуже мало пам’яті
+для обробки кожного запиту.
+
+- [Документація](https://github.com/joyent/http-parser/)
+
+### c-ares
+
+Для деяких асинхронних DNS–запитів Node.js використовує C–бібліотеку
+під назвою c-ares. Вона використовується через DNS–модуль у JavaScript
+в якості сім’ї функцій resolve(). Функція lookup(),
+яку використовує решту ядра, використовується для getaddrinfo(3)
+викликів у libuv. Причиною цього є те, що c-ares підтримує /etc/hosts,
+/etc/resolv.conf та /etc/svc.conf, проте не речі, на зразок mDNS.
+
+- [Документація](http://c-ares.haxx.se/docs.html)
+
+### OpenSSL
+
+OpenSSL широко використовується у модулях `tls` та `crypto`. Вона надає добре протестовані імплементації багатьох криптографічних функцій, які використовуються у сучасному вебі для безпеки.
+
+- [Документація](https://www.openssl.org/docs/)
+
+### zlib
+
+Для компресії та декомпресії Node.js використовує де–факто стандартну в
+індустрії бібліотеку zlib, яка також використовується у gzip та libpng.
+Node.js використовує zlib для створення синхронних, асинхронних
+та потокових інтерфейсів компресії та декомпресії
+
+- [Документація](http://www.zlib.net/manual.html)
+
+## Інструменти
+
+### npm
+
+Node.js є модульним, а це вимагає наявності якісного пакетного менеджера і саме для цієї потреби був розроблений npm. Разом з npm надходить велика кількість пакетів для будь–якої програмної екосистеми, що робить побудову додатків на  Node.js швидким та легким процесом.
+
+- [Документація](https://docs.npmjs.com/)
+
+### gyp
+
+Система збірки керується через gyp (генератор проектів взятий з V8, що написаний на Python). Вона може генерувати файли для проектів,щоб використовувати їх у системах збірки на багатьох платформах. Node.js потребує системи збірки, оскільки велика кількість його частин, його залежності, написані на мовах, що потребують компіляції.
+
+- [Документація](https://chromium.googlesource.com/external/gyp/+/master/docs/UserDocumentation.md)
+
+### gtest
+
+Нативний код можна тестувати через gtest, який взятий з Chromium. Він дозволяє тестувати C/C++ без потреби у існуючій збірці node.
+
+- [Документація](https://code.google.com/p/googletest/wiki/V1_7_Documentation)
diff --git a/locale/uk/download/current.md b/locale/uk/download/current.md
new file mode 100755
index 0000000000000..e691113706cfd
--- /dev/null
+++ b/locale/uk/download/current.md
@@ -0,0 +1,22 @@
+---
+layout: download-current.hbs
+title: Завантажити
+download: Завантажити
+downloads:
+    headline: Завантаження
+    lts: LTS
+    current: Поточна
+    tagline-current: Найновіші можливості
+    tagline-lts: Рекомандовано для більшості
+    display-hint: Показати завантаження для
+    intro: >
+        Завантажте початковий код Node.js або інсталятор для вашої платформи та почніть розробку сьогодні.
+    currentVersion: Поточна версія
+    buildDisclaimer: "Зауважте: Для побудови з початкового коду необхідний Python 2.6 або 2.7."
+additional:
+    headline: Додаткові платформи
+    intro: >
+        Учасники спільноти Node.js підтримують неофіційні збірки Node.js для додаткових платформ. Майте на увазі, що ці збірки не підтримуються основною командою Node.js і можуть не мати того ж функціоналу що й поточний реліз Node.js.
+    platform: Платформа
+    provider: Провайдер
+---
diff --git a/locale/uk/download/index.md b/locale/uk/download/index.md
new file mode 100755
index 0000000000000..f155f5ff9e12c
--- /dev/null
+++ b/locale/uk/download/index.md
@@ -0,0 +1,22 @@
+---
+layout: download.hbs
+title: Завантажити
+download: Завантажити
+downloads:
+    headline: Завантаження
+    lts: LTS
+    current: Поточна
+    tagline-current: Найновіші можливості
+    tagline-lts: Рекомандовано для більшості
+    display-hint: Показати завантаження для
+    intro: >
+        Завантажте початковий код Node.js або інсталятор для вашої платформи та почніть розробку сьогодні.
+    currentVersion: Поточна версія
+    buildDisclaimer: "Зауважте: Для побудови з початкового коду необхідний Python 2.6 або 2.7."
+additional:
+    headline: Додаткові платформи
+    intro: >
+        Учасники спільноти Node.js підтримують неофіційні збірки Node.js для додаткових платформ. Майте на увазі, що ці збірки не підтримуються основною командою Node.js і можуть не мати тієї ж функціональності що й поточний реліз Node.js.
+    platform: Платформа
+    provider: Провайдер
+---
diff --git a/locale/uk/download/package-manager.md b/locale/uk/download/package-manager.md
new file mode 100755
index 0000000000000..6f2343c66a210
--- /dev/null
+++ b/locale/uk/download/package-manager.md
@@ -0,0 +1,376 @@
+---
+layout: page.hbs
+title: Installing Node.js via package manager
+---
+
+# Installing Node.js via package manager
+
+***Note:*** The packages on this page are maintained and supported by their respective packagers, **not** the Node.js core team. Please report any issues you encounter to the package maintainer. If it turns out your issue is a bug in Node.js itself, the maintainer will report the issue upstream.
+
+----------------------------
+
+* [Arch Linux](#arch-linux)
+* [Debian and Ubuntu based Linux distributions](#debian-and-ubuntu-based-linux-distributions)
+* [Enterprise Linux and Fedora](#enterprise-linux-and-fedora)
+* [FreeBSD and OpenBSD](#freebsd-and-openbsd)
+* [Gentoo](#gentoo)
+* [NetBSD](#netbsd)
+* [openSUSE and SLE](#opensuse-and-sle)
+* [OSX](#osx)
+* [SmartOS and illumos](#smartos-and-illumos)
+* [Void Linux](#void-linux)
+* [Windows](#windows)
+
+----------------------------
+
+## Arch Linux
+
+Node.js and npm packages are available in the Community Repository.
+
+```bash
+pacman -S nodejs npm
+```
+
+
+## Debian and Ubuntu based Linux distributions
+
+Also including: **Linux Mint**, **Linux Mint Debian Edition (LMDE)**, **elementaryOS** and others.
+
+Node.js is available from the [NodeSource](https://nodesource.com) Debian and Ubuntu binary distributions repository (formerly [Chris Lea's](https://github.com/chrislea) Launchpad PPA). Support for this repository, along with its scripts, can be found on GitHub at [nodesource/distributions](https://github.com/nodesource/distributions).
+
+**NOTE:** If you are using Ubuntu Precise or Debian Wheezy, you might want to read about [running Node.js >= 4.x on older distros](https://github.com/nodesource/distributions/blob/master/OLDER_DISTROS.md).
+
+```bash
+curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
+sudo apt-get install -y nodejs
+```
+
+Alternatively, for Node.js v6:
+
+```bash
+curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
+sudo apt-get install -y nodejs
+```
+
+***Optional***: install build tools
+
+To compile and install native addons from npm you may also need to install build tools:
+
+```bash
+sudo apt-get install -y build-essential
+```
+
+**Available architectures:**
+
+* **i386** (32-bit)
+* **amd64** (64-bit)
+* **armhf** (ARM 32-bit hard-float, ARMv7 and up: _arm-linux-gnueabihf_)
+
+**Supported Ubuntu versions:**
+
+* **Ubuntu 12.04 LTS** (Precise Pangolin)
+* **Ubuntu 14.04 LTS** (Trusty Tahr)
+* **Ubuntu 15.04** (Vivid Vervet)
+
+**Supported Debian versions:**
+
+* **Debian 7** (wheezy)
+* **Debian 8 / stable** (jessie)
+* **Debian testing** (stretch, aliased to jessie)
+* **Debian unstable** (sid)
+
+A Node.js package is also available in the [official repo](http://packages.debian.org/search?searchon=names&keywords=nodejs) for Debian Sid (unstable), Jessie (testing) and Wheezy (wheezy-backports) as "nodejs". It only installs a `nodejs` binary.
+
+The [nodejs-legacy package](http://packages.debian.org/search?searchon=names&keywords=nodejs-legacy) installs a `node` symlink that is needed by many modules to build and run correctly.
+The Node.js modules available in the distribution official repositories do not need it.
+
+**Supported Linux Mint versions:**
+
+* **Linux Mint 13 "Maya"** (via Ubuntu 12.04 LTS)
+* **Linux Mint 17 "Qiana"** (via Ubuntu 14.04 LTS)
+* **Linux Mint 17.1 "Rebecca"** (via Ubuntu 14.04 LTS)
+* **Linux Mint 17.2 "Rafaela"** (via Ubuntu 14.04 LTS)
+* **Linux Mint Debian Edition (LMDE) 2 "Betsy"** (via Debian 8)
+
+**Supported elementary OS versions:**
+
+* **elementary OS Luna** (via Ubuntu 12.04 LTS)
+* **elementary OS Freya** (via Ubuntu 14.04 LTS)
+
+**Supported Trisquel versions:**
+
+* **Trisquel 6 "Toutatis"** (via Ubuntu 12.04 LTS)
+* **Trisquel 7 "Belenos"** (via Ubuntu 14.04 LTS)
+
+**Supported BOSS versions:**
+
+* **BOSS 5.0 "Anokha"** (via Debian 7)
+
+## Enterprise Linux and Fedora
+
+Including **Red Hat® Enterprise Linux®** / **RHEL**, **CentOS** and **Fedora**.
+
+Node.js is available from the [NodeSource](https://nodesource.com) Enterprise Linux and Fedora binary distributions repository. Support for this repository, along with its scripts, can be found on GitHub at [nodesource/distributions](https://github.com/nodesource/distributions).
+
+Note that the Node.js packages for EL 5 (RHEL5 and CentOS 5) depend on the **[EPEL](https://fedoraproject.org/wiki/EPEL)** repository being available. The setup script will check and provide instructions if it is not installed.
+
+Run as root on RHEL, CentOS or Fedora, for Node.js v4 LTS Argon:
+
+```bash
+curl --silent --location https://rpm.nodesource.com/setup_4.x | bash -
+```
+
+Alternatively for Node.js v6:
+
+```bash
+curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -
+```
+
+Alternatively for Node.js 0.10:
+
+```bash
+curl --silent --location https://rpm.nodesource.com/setup | bash -
+```
+
+Then install, as root:
+
+```bash
+yum -y install nodejs
+```
+
+***Optional***: install build tools
+
+To compile and install native addons from npm you may also need to install build tools:
+
+```bash
+yum install gcc-c++ make
+# or: yum groupinstall 'Development Tools'
+```
+
+**Available architectures:**
+
+* **i386** (32-bit, not available for EL7)
+* **x86_64** (64-bit)
+
+**Supported Red Hat® Enterprise Linux® versions:**
+
+* **RHEL 5** (32-bit and 64-bit)
+* **RHEL 6** (32-bit and 64-bit)
+* **RHEL 7** (64-bit)
+
+**Supported CentOS versions:**
+
+* **CentOS 5** (32-bit and 64-bit)
+* **CentOS 6** (32-bit and 64-bit)
+* **CentOS 7** (64-bit)
+
+**Supported CloudLinux versions:**
+* **CloudLinux 6** (32-bit and 64-bit)
+
+**Supported Fedora versions:**
+
+* **Fedora 21 (Twenty One)** (32-bit and 64-bit)
+* **Fedora 20 (Heisenbug)** (32-bit and 64-bit)
+* **Fedora 19 (Schrödinger's Cat)** (32-bit and 64-bit)
+
+**Other distributions known to be supported:**
+
+* **Oracle Linux** (mirrors RHEL very closely)
+* **Amazon Linux** (tested on 2014.03)
+
+### Alternatives
+
+Official **Fedora** [Node.js](https://apps.fedoraproject.org/packages/nodejs) and [npm](https://apps.fedoraproject.org/packages/npm) packages are available in Fedora 18 and later.  Install with:
+
+```bash
+sudo yum install nodejs npm
+```
+
+In a hurry for the latest updates?  [Grab them from updates-testing.](https://fedoraproject.org/wiki/QA:Updates_Testing)
+
+**Enterprise Linux** (RHEL and CentOS) users may use the Node.js and npm packages from the [EPEL](https://fedoraproject.org/wiki/EPEL) repository.
+
+Install the appropriate *epel-release* RPM for your version (found on the [EPEL](https://fedoraproject.org/wiki/EPEL) repository homepage), then run:
+
+```bash
+sudo yum install nodejs npm --enablerepo=epel
+```
+
+In a hurry for the latest updates?  [Grab them from epel-testing.](https://fedoraproject.org/wiki/EPEL/testing)
+
+**Available architectures:**
+
+* **i686** (32-bit, not available for EL7)
+* **x86_64** (64-bit)
+* **armv6hl** (Raspberry Pi, [Pidora](http://pidora.ca) only)
+* **armv7hl** (32-bit ARM hard-float, ARMv7 and up, Fedora only)
+
+**Supported Red Hat® Enterprise Linux® versions:**
+
+* **RHEL 6** (i686/x86_64)
+* **RHEL 7** (x86_64)
+
+Additionally, versions of **CentOS** and **Scientific Linux** corresponding to the above RHEL versions are also officially supported by all EPEL packages, including nodejs.  Amazon Linux is not officially supported by EPEL due to significant incompatibilities previously reported to the epel-devel mailing list, however you might find that nodejs at least still works.
+
+**Supported Fedora versions:**
+
+* **Fedora Rawhide** (i686/x86_64/armv7hl)
+* **Fedora 21** (i686/x86_64/armv7hl)
+* **Fedora 20 (Heisenbug)** (i686/x86_64/armv6hl/armv7hl)
+* **Fedora 19 (Schrödinger's Cat)** (i686/x86_64/armv7hl)
+
+
+## FreeBSD and OpenBSD
+
+Node.js is available through the ports system.
+
+```bash
+/usr/ports/www/node
+```
+
+Development versions are also available using ports
+
+```bash
+cd /usr/ports/www/node-devel/ && make install clean
+```
+
+Or packages on FreeBSD:
+
+```bash
+pkg_add -r node-devel
+```
+
+Using [pkg-ng](https://wiki.freebsd.org/pkgng) on FreeBSD
+
+```bash
+pkg install node
+```
+
+Or the development versions:
+
+```bash
+pkg install node-devel
+```
+
+
+## Gentoo
+
+Node.js is available in the portage tree.
+
+```bash
+emerge nodejs
+```
+
+
+## NetBSD
+
+Node.js is available in the pkgsrc tree:
+
+```bash
+cd /usr/pkgsrc/lang/nodejs && make install
+```
+
+Or install a binary package (if available for your platform) using pkgin:
+
+```bash
+pkgin -y install nodejs
+```
+
+
+## openSUSE and SLE
+
+[Download Node.js via openSUSE one-click](http://software.opensuse.org/download.html?project=devel%3Alanguages%3Anodejs&package=nodejs).
+
+Available RPM packages for: openSUSE 11.4, 12.1, 12.2, 12.3, 13.1, Factory and Tumbleweed; SLE 11 (with SP1/SP2/SP3 variations).
+
+Example install on openSUSE 13.1:
+
+```bash
+sudo zypper ar \
+  http://download.opensuse.org/repositories/devel:/languages:/nodejs/openSUSE_13.1/ \
+  Node.js
+sudo zypper in nodejs nodejs-devel
+```
+
+
+## OSX
+
+Simply download the [Macintosh Installer](http://nodejs.org/#download) direct from the [nodejs.org](http://nodejs.org) web site.
+
+_If you want to download the package with bash:_
+
+```bash
+curl "https://nodejs.org/dist/latest/node-${VERSION:-$(wget -qO- https://nodejs.org/dist/latest/ | sed -nE 's|.*>node-(.*)\.pkg</a>.*|\1|p')}.pkg" > "$HOME/Downloads/node-latest.pkg" && sudo installer -store -pkg "$HOME/Downloads/node-latest.pkg" -target "/"
+```
+
+### Alternatives
+
+Using **[Homebrew](http://brew.sh/)**:
+
+```bash
+brew install node
+```
+
+Using **[MacPorts](http://www.macports.org/)**:
+
+```bash
+port install nodejs
+```
+
+Using **[pkgsrc](https://pkgsrc.joyent.com/install-on-osx/)**:
+
+Install the binary package:
+
+```bash
+pkgin -y install nodejs
+```
+
+Or build manually from pkgsrc:
+
+```bash
+cd pkgsrc/lang/nodejs && bmake install
+```
+
+## SmartOS and illumos
+
+SmartOS images come with pkgsrc pre-installed.  On other illumos distributions, first install **[pkgsrc](https://pkgsrc.joyent.com/install-on-illumos/)**, then you may install the binary package as normal:
+
+```bash
+pkgin -y install nodejs
+```
+
+Or build manually from pkgsrc:
+
+```bash
+cd pkgsrc/lang/nodejs && bmake install
+```
+
+
+## Void Linux
+
+Void Linux ships node.js stable in the main repository.
+
+```bash
+xbps-install -Sy nodejs
+```
+
+
+## Windows
+
+Simply download the [Windows Installer](http://nodejs.org/#download) directly from the [nodejs.org](http://nodejs.org) web site.
+
+### Alternatives
+
+Using **[Chocolatey](http://chocolatey.org)**:
+
+```bash
+cinst nodejs
+# or for full install with npm
+cinst nodejs.install
+```
+
+Using **[Scoop](http://scoop.sh/)**:
+
+```bash
+scoop install nodejs
+```
diff --git a/locale/uk/download/releases.md b/locale/uk/download/releases.md
new file mode 100755
index 0000000000000..b1bf1bca73f2f
--- /dev/null
+++ b/locale/uk/download/releases.md
@@ -0,0 +1,20 @@
+---
+layout: download-releases.hbs
+title: Previous Releases
+modules: "<code>NODE_MODULE_VERSION</code> refers to the ABI (application binary interface) version number of Node.js, used to determine which versions of Node.js compiled C++ add-on binaries can be loaded in to without needing to be re-compiled. It used to be stored as hex value in earlier versions, but is now represented as an integer."
+---
+
+### io.js та Node.js
+Релізи від 1.x до 3.x називались "io.js", оскільки вони були частиною форку io.js. Node.js 4.0.0 є загальним релізом io.js об'єднаного з Node.js 0.12.x у спільні релізи Node.js.
+
+<div class="highlight-box">
+    Шукаєте останній реліз певної версії?
+
+    <ul class="list-divider-pipe">
+        <li><a href="https://nodejs.org/dist/latest-v6.x/">Node.js 6.x</a></li>
+        <li><a href="https://nodejs.org/dist/latest-v5.x/">Node.js 5.x</a></li>
+        <li><a href="https://nodejs.org/dist/latest-v0.12.x/">Node.js 0.12.x</a></li>
+        <li><a href="https://nodejs.org/dist/latest-v0.10.x/">Node.js 0.10.x</a></li>
+        <li><a href="https://nodejs.org/dist/">усі версії</a></li>
+    </ul>
+</div>
diff --git a/locale/uk/foundation/announcements.md b/locale/uk/foundation/announcements.md
new file mode 100755
index 0000000000000..34e7279625ac4
--- /dev/null
+++ b/locale/uk/foundation/announcements.md
@@ -0,0 +1,4 @@
+---
+title: Анонси
+layout: announcements.hbs
+---
diff --git a/locale/uk/foundation/board.md b/locale/uk/foundation/board.md
new file mode 100755
index 0000000000000..73c2f2b9877f6
--- /dev/null
+++ b/locale/uk/foundation/board.md
@@ -0,0 +1,20 @@
+---
+title: Рада директорів Node.js Foundation
+layout: foundation.hbs
+---
+
+Рада директорів складається з представників від корпоративних учасників, представників Технічного виконавчого комітету (Technical Steering Committee (TSC)), та представників, що обираються окремими учасниками.
+
+* Голова: **Danese Cooper**, шановний член технічного персоналу - open source в PayPal.
+* Заступник голови: **Scott Hammond**, головний виконавчий директор (СTO) в Joyent.
+* Директор TSC: **Rod Vagg**, директор стосовно node в NodeSource.
+* Золотий директор: **Charlie Robbins**, директор з інженерії в GoDaddy.com.
+* Срібний директор: **Brian McCallister**, головний виконавчий директор (СTO) платформ в Groupon.
+* Директор: **Todd Moore**, заступник президента стосовно відкритих технологій в IBM.
+* Директор: **Colleen Evans**, провідний програмний менеджер в Microsoft.
+* Директор: **Rich Sharples**, старший директор з управління продуктами компанії Red Hat.
+* Директор: **Imad Sousou**, заступник президента та генеральний менеджер в Intel.
+* Директор: **Ashley Williams**, директор від індивідуальних членів.
+* Директор: **Feross Aboukhadijeh**, директор від індивідуальних членів.
+
+Незалежно від ради, технічний виконавчий комітет встановлює напрямок технічного розвитку проекту, включаючи релізи, стандарти якості, управління проектом, хостинг репозиторіїв на GitHub і тд. Rod Vagg є членом та представником Технічного виконавчого комітету у раді директорів.
diff --git a/locale/uk/foundation/case-studies.md b/locale/uk/foundation/case-studies.md
new file mode 100755
index 0000000000000..637034721ed5d
--- /dev/null
+++ b/locale/uk/foundation/case-studies.md
@@ -0,0 +1,28 @@
+---
+title: Ресурси Node.js Foundation
+layout: foundation.hbs
+---
+
+## Результати опитування Node.js Foundation
+
+З понад 3,5 мільйонами користувачів та постійним щорічним зростанням на
+100%, Node.js стає універсальною платформою для веб–додатків, IoT
+та підприємництва. Звіт про результати опитування Node.js стосовно
+нових тенденцій, що відбуваються в цій величезній спільноті,
+служить ключовим індикатором тенденцій, як от архітектура мікросервісів,
+real-time веб–додатки, та інтернету речей (IOT). Звіт створює
+детальну картину технологій, що використовуються, зокрема,
+стосовно Node.js у production та мов, яким надають переваги
+(зараз і в майбутньому) у фронт–енді, бек—енді та IoT розробці.
+
+* [Читати повний анонс.](/en/blog/announcements/nodejs-foundation-survey/)
+* [Подивитись інфографіку.](/static/documents/2016-survey-infographic.png)
+* [Читати повний звіт.](/static/documents/2016-survey-report.pdf)
+
+## Node.js забезпечує масштабованість та надійність в Uber
+
+Транспортна платформа Uber має амбітну мету: зробити транспорт надійним
+скрізь і для всіх. Дізнайтеся, чому Uber обрав Node.js для побудови
+своєї платформи і масивної системи для пошуку співпадінь.
+
+Читайте [повне дослідження](/static/documents/casestudies/Nodejs-at-Uber.pdf).
diff --git a/locale/uk/foundation/in-the-news.md b/locale/uk/foundation/in-the-news.md
new file mode 100755
index 0000000000000..a1fad06ca81c0
--- /dev/null
+++ b/locale/uk/foundation/in-the-news.md
@@ -0,0 +1,4 @@
+---
+title: Node.js Foundation у новинах
+layout: in-the-news.hbs
+---
diff --git a/locale/uk/foundation/index.md b/locale/uk/foundation/index.md
new file mode 100755
index 0000000000000..279ede8df01fd
--- /dev/null
+++ b/locale/uk/foundation/index.md
@@ -0,0 +1,55 @@
+---
+title: Node.js Foundation
+layout: foundation.hbs
+---
+
+# Node.js Foundation
+
+Місією Node.js Foundation є забезпечення масштабного поширення і прискорення розвитоку Node.js та інших пов'язаних модулів через модель відкритого управління, яка заохочує участь, технічну співпрацю, а також основу для довгострокового стратегічного управління через екосистему, яка сприяла успіху Node.js.
+
+## Огляд
+
+<iframe class="center" src="//www.slideshare.net/slideshow/embed_code/key/gmABh2vHJx5OcI"
+        width="425" height="355"
+        frameborder="0" marginwidth="0" marginheight="0"
+        scrolling="no"
+        style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen>
+</iframe>
+
+<div style="text-align:center; margin-bottom:5px">
+    <strong>
+        <a href="//www.slideshare.net/NodejsFoundation/node-foundation-membership-overview-20150505"
+            title="Node.js Foundation Membership Overview 20150505"
+            target="_blank">
+            Node.js Foundation Membership Overview 2015-05-05
+        </a>
+    </strong> from <strong>
+        <a href="//www.slideshare.net/NodejsFoundation" target="_blank">
+            Node.js Foundation
+        </a>
+    </strong>
+</div>
+
+## Ключові документи
+
+- [Technical Steering Committee (TSC) Charter](https://github.com/nodejs/TSC/blob/master/TSC-Charter.md)
+- [Governance](https://github.com/nodejs/TSC)
+- [By-laws](/static/documents/node-foundation-by-laws.pdf)
+- [Membership Agreement](http://f.cl.ly/items/0N1m3x0I3S2L203M1h1r/nodejs-foundation-membership-agreement-2015-march-04.pdf)
+- [Certificate of Incorporation](http://f.cl.ly/items/2b1b1o0v1e1u2i1L2w1a/nodejs-foundation-certificate-of-incorporation-2014-august-01.pdf)
+- [Trademark Guidelines](https://nodejs.org/static/documents/trademark-policy.pdf)
+
+## Зустрічі керівництва
+- [2015-07-27](/static/documents/minutes/nodejs-foundation-board-meeting-2015-07-27.pdf)
+- [2015-08-31](/static/documents/minutes/nodejs-foundation-board-meeting-2015-08-31.pdf)
+- [2015-09-28](/static/documents/minutes/nodejs-foundation-board-meeting-2015-09-28.pdf)
+- [2015-11-02](/static/documents/minutes/nodejs-foundation-board-meeting-2015-11-02.pdf)
+- [2016-02-29](/static/documents/minutes/nodejs-foundation-board-meeting-2016-02-29.pdf)
+
+## Контакти
+
+Для запитань, що стосуються використання торгової марки Node.js&reg;, звертайтесь за адресою <a href="mailto:trademark@nodejs.org?subject=Trademark">trademark@nodejs.org</a>.
+
+Щоб отримувати новини про Node.js Foundation зареєструйтись нижче.
+
+<iframe src="https://go.pardot.com/l/6342/2015-09-15/2sgqpp" width="100%" height="500" type="text/html" frameborder="0" allowTransparency="true" style="border: 0"></iframe>
diff --git a/locale/uk/foundation/members.md b/locale/uk/foundation/members.md
new file mode 100755
index 0000000000000..713ed57a598a1
--- /dev/null
+++ b/locale/uk/foundation/members.md
@@ -0,0 +1,121 @@
+---
+title: Члени Node.js Foundation
+layout: foundation.hbs
+---
+# Члени фундації
+
+Для запиту інформації стосовно приєднання до Node.js Foundation, пишіть за адресою:
+[membership@nodejs.org](mailto:membership@nodejs.org).
+
+Node.js Foundation відкритий для бізнесу та окремих осіб. Окремі члени обиратимуть у січні двох представників до складу Ради директорів, які будуть відповідати за подання різноманітних потреб спільноти Node.js в управлінні Node.js Foundation.
+
+## Стати окремим учасником
+
+Індивідуальне членство коштує [$100 на рік, або $25 для студентів](https://identity.linuxfoundation.org/user?destination=pid/99) (дисконтний код для студентів: **NodeStudentN10HM**). Співучасники проекту Node.js, включаючи всі робочі групи та підпроекти, мають право на безкоштовне членство.
+
+Вам необхідний GitHub–аккаунт для реєстрації.
+
+# Корпоративні учасники
+
+## Платинові
+
+<div style="text-align:center;">
+<a target="_new" class="imagelink" href="http://ibm.com">
+  <img alt="IBM" class="memberlogo" src="/static/images/foundation/ibmLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="http://intel.com">
+  <img alt="Intel" class="memberlogo" src="/static/images/foundation/intelLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//joyent.com">
+  <img alt="Joyent" class="memberlogo" src="/static/images/foundation/joyentLogo.svg" />
+</a>
+<a target="_new" class="imagelink" href="//microsoft.com">
+  <img alt="Microsoft" class="memberlogo" src="/static/images/foundation/microsoftLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//paypal.com">
+  <img alt="PayPal" class="memberlogo" src="/static/images/foundation/paypalLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//redhat.com">
+  <img alt="Red Hat" class="memberlogo" src="/static/images/foundation/redhatLogo.png" />
+</a>
+</div>
+
+## Золоті
+
+<div style="text-align:center;">
+<a target="_new" class="imagelink" href="//godaddy.com">
+  <img alt="GoDaddy" class="memberlogo" src="/static/images/foundation/godaddyLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//nodesource.com">
+  <img alt="NodeSource" class="memberlogo" src="/static/images/foundation/nodesourceLogo.png" />
+</a>
+</div>
+
+## Срібні
+
+<div style="text-align:center;">
+<a target="_new" class="imagelink" href="http://apigee.com">
+  <img alt="Apigee" class="memberlogo" src="/static/images/foundation/apigee_logo_md.png" />
+</a>
+<a target="_new" class="imagelink" href="http://appdynamics.com">
+  <img alt="AppDynamics" class="memberlogo" src="/static/images/foundation/appdynamics.png" />
+</a>
+<a target="_new" class="imagelink" href="http://codefresh.io">
+  <img alt="CodeFresh" class="memberlogo" src="/static/images/foundation/codefreshLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//digitalocean.com">
+  <img alt="DigitalOcean" class="memberlogo" src="/static/images/foundation/digitaloceanLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//fidelity.com">
+  <img alt="Fidelity" class="memberlogo" src="/static/images/foundation/fidelityLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="https://google.com">
+  <img alt="Google" class="memberlogo" src="/static/images/foundation/googleLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//groupon.com">
+  <img alt="Groupon" class="memberlogo" src="/static/images/foundation/grouponLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="http://nearform.com">
+  <img alt="nearForm" class="memberlogo" src="/static/images/foundation/nearformLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="http://newrelic.com">
+  <img alt="New Relic" class="memberlogo" src="/static/images/foundation/NewRelic.png" />
+</a>
+<a target="_new" class="imagelink" href="//npmjs.org">
+  <img alt="npm" class="memberlogo" src="/static/images/foundation/npmLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="http://opbeat.com">
+  <img alt="opbeat" class="memberlogo" src="/static/images/foundation/opbeat.png" />
+</a>
+<a target="_new" class="imagelink" href="//risingstack.com">
+  <img alt="RisingStack" class="memberlogo" src="/static/images/foundation/risingstack_logo.png" />
+</a>
+<a target="_new" class="imagelink" href="http://sap.com">
+  <img alt="SAP" class="memberlogo" src="/static/images/foundation/sapLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//saucelabs.com">
+  <img alt="Saucelabs" class="memberlogo" src="/static/images/foundation/saucelabsLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="http://sphinx.sg/">
+  <img alt="Sphinx" class="memberlogo" src="/static/images/foundation/sphinx.png" />
+</a>
+<a target="_new" class="imagelink" href="//strongloop.com">
+  <img alt="StrongLoop" class="memberlogo" src="/static/images/foundation/strongloopLogo.png" />
+</a>
+<a target="_new" class="imagelink" href="//yahoo.com">
+  <img alt="Yahoo!" class="memberlogo" src="/static/images/foundation/yahoo.png" />
+</a>
+<a target="_new" class="imagelink" href="//yld.io">
+  <img alt="yld!" class="memberlogo" src="/static/images/foundation/yldLogo.png" />
+</a>
+</div>
+
+Для запиту інформації стосовно приєднання до Node.js Foundation, пишіть за адресою:
+[membership@nodejs.org](mailto:membership@nodejs.org).
+
+<iframe class="center"
+ src="https://go.pardot.com/l/6342/2015-05-15/2cnz97"
+ frameborder="0" marginwidth="0" marginheight="0"
+ style="width:90%;height:600px;"
+ >
+</iframe>
diff --git a/locale/uk/foundation/newsletter.md b/locale/uk/foundation/newsletter.md
new file mode 100755
index 0000000000000..9fe4ce473b445
--- /dev/null
+++ b/locale/uk/foundation/newsletter.md
@@ -0,0 +1,8 @@
+---
+title: Підписка на поштове розсилання
+layout: foundation.hbs
+---
+
+Щоб отримувати новини про Node.js Foundation зареєструйтесь нижче:
+
+<iframe src="https://go.pardot.com/l/6342/2015-09-15/2sgqpp" width="100%" height="300" type="text/html" frameborder="0" allowTransparency="true" style="border: 0"></iframe>
diff --git a/locale/uk/foundation/resources.md b/locale/uk/foundation/resources.md
new file mode 100755
index 0000000000000..c6e41cc8b5695
--- /dev/null
+++ b/locale/uk/foundation/resources.md
@@ -0,0 +1,10 @@
+---
+title: Node.js Foundation дослідження
+layout: foundation.hbs
+---
+
+## Node.js забезпечує масштабованість та надійність в Uber
+
+Транспортна платформа Uber має амбітну мету: зробити транспорт надійним скрізь і для всіх. Дізнайтеся, чому Uber обрав Node.js для побудови своєї платформи і масивної системи для пошуку співпадінь.
+
+Читайте [повне дослідження](/static/documents/casestudies/Nodejs-at-Uber.pdf).
diff --git a/locale/uk/foundation/tsc/index.md b/locale/uk/foundation/tsc/index.md
new file mode 100755
index 0000000000000..060383cddeb38
--- /dev/null
+++ b/locale/uk/foundation/tsc/index.md
@@ -0,0 +1,46 @@
+---
+title: Технічний виконавчий комітет
+layout: foundation.hbs
+---
+
+# Співавтори та Технічний виконавчий комітет
+
+Проект Node.js спонсорується Node.js Foundation і підтримується окремими
+учасниками. Технічний керівний комітет (Technical Steering Committee (TSC))
+складається з ключових учасників, що продемонстрували як свої спеціальні
+технічні знання і практичну підтримку, так і сприяння потсупальному розвиткові
+проекту та спільноті.
+
+You can read more about how to become a collaborator and a TSC member in [the
+contributing section](/en/get-involved/contribute/).
+
+Ви можете дізнатись більше про те, як стати учасником та членом TSC у
+[розділі для учасників](/contribute/).
+
+### Поточні учасники
+
+На разі, проект Node.js має понад 300 учасників, що активно працюють над різними
+частинами проекту. Поточний список учасників можна знайти у
+[профілі проекту на GitHub](https://github.com/orgs/nodejs/people).
+
+### Поточні члени Технічного керівного комітету
+
+* Alexis Campailla ([orangemocha](https://github.com/orangemocha))
+* Ben Noordhuis ([bnoordhuis](https://github.com/bnoordhuis))
+* Bert Belder ([piscisaureus](https://github.com/piscisaureus))
+* Brian White ([mscdex](https://github.com/mscdex))
+* Chris Dickinson ([chrisdickinson](https://github.com/chrisdickinson))
+* Colin Ihrig ([cjihrig](https://github.com/cjihrig))
+* Fedor Indutny ([indutny](https://github.com/indutny))
+* James M Snell ([jasnell](https://github.com/jasnell))
+* Jeremiah Senkpiel ([Fishrock123](https://github.com/Fishrock123))
+* Julien Gilli ([misterdjules](https://github.com/misterdjules))
+* Michael Dawson ([mhdawson](https://github.com/mhdawson))
+* Rod Vagg ([rvagg](https://github.com/rvagg))
+* Shigeki Ohtsu ([shigeki](https://github.com/shigeki))
+* Steven R Loomis ([srl295](https://github.com/srl295))
+* Trevor Norris ([trevnorris](https://github.com/trevnorris))
+
+## Зустрічі Технічного виконавчого комітету
+
+[Meeting minutes](minutes/)
diff --git a/locale/uk/foundation/tsc/minutes.md b/locale/uk/foundation/tsc/minutes.md
new file mode 100755
index 0000000000000..445a0786abba6
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes.md
@@ -0,0 +1,4 @@
+---
+title: Зустрічі Технічного виконавчого комітету
+layout: foundation-tsc-minutes-index.hbs
+---
diff --git a/locale/uk/foundation/tsc/minutes/2014-12-10.md b/locale/uk/foundation/tsc/minutes/2014-12-10.md
new file mode 100755
index 0000000000000..fa9ac99533ffb
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2014-12-10.md
@@ -0,0 +1,60 @@
+---
+title: Minutes for the Node.js core team meeting of 12/10/2014
+date: 2014-12-10
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Team announcements
+
+Colin Ihrig is promoted to apprentice. Chris Dickinson and Julien Gilli are
+promoted from apprentice to core team members.
+
+## Next releases
+
+### 0.10.34
+
+The next stable release, 0.10.34, is imminent and should be available in the
+next few days. The only issue remaining is that recently libuv added an entry
+to the public API (see https://github.com/libuv/libuv/commit/9da5fd443ebc2c56a
+7f5946f0a1e04801b370a33). Node will need to find a way to not cause any
+problems for users who link node with a dynamic shared libuv.
+
+### 0.11.15
+
+Nobody had any blocker for the next developement release, whose release is
+also scheduled to happen in the next few days. The priority is given to
+releasing 0.10.34 first though.
+
+### 0.12
+
+#### Potential V8 upgrade
+
+During the previous meeting, the possibility of upgrading V8 to a more recent
+release was discussed. While everyone agreed that upgrading V8 to a version
+that is closer to what the V8 team considers to be stable would benefit all
+users in terms of new features (e.g generators), several concerns were
+expressed:
+
+* It is not clear what impact it would have on binary modules.
+
+* Users would need to upgrade their toolchain, as V8 moved to C++11. It's not a
+problem for individual developers, as they can upgrade easily most of the
+time. However, it could be a problem for distributions (an example is CentOS),
+and people who followed the 0.11.x branch for a long time and don't expect
+such a change.
+
+Moreover, everyone agreed that performing this upgrade that late in the
+development process and so close to a new stable relase is risky.
+
+The consensus seems to be leaning towards not upgrading V8 again before 0.12,
+and instead having a smaller list of features and fixes for the next stable
+release, with a much shorter release time. One of the first thing that would
+be done in the next unstable branch (0.13) would be a V8 upgrade.
+
+## TODO for next meeting
+
+Next meeting is December 11th at 9:00AM PST.
+
+* Come up with a list of the following GitHub issues:
+  * Needed for 0.12.0.
+  * Needed 0.12.1.
diff --git a/locale/uk/foundation/tsc/minutes/2014-12-16.md b/locale/uk/foundation/tsc/minutes/2014-12-16.md
new file mode 100755
index 0000000000000..a71744415f119
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2014-12-16.md
@@ -0,0 +1,147 @@
+---
+title: Minutes for the Node.js core team meeting of 12/16/2014
+date: 2014-12-16
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Chris Dickinson.
+* TJ Fontaine.
+* Julien Gilli.
+* Colin Ihrig.
+* Wyatt Preul.
+* James M Snell.
+
+## Upcoming releases
+
+### 0.10.34
+
+Work on releasing 0.10.34 had already started, and is scheduled to be done
+today (12/16/2014) or tomorrow (12/17/2014).
+
+### 0.10.35
+
+It is still not clear if and when a 0.10.35 version will be released, but
+Chris Dickinson already identified [one of his pull-requests](TODO: Chris,
+could you please provide the link to your PR about improving buffers'
+performance?) as a good candidate for inclusion in this release.
+
+### 0.11.15
+
+Work on releasing 0.11.15 has already started. TODO: do we want to fix all
+issues with --with-intl=small-icu before doing this release?
+
+### 0.12.1
+
+0.12.0 is not yet released, but some issues/PR can already be added to the
+0.12.1 milestone. Good candidates for the 0.12.1 milestone are things we know
+in the v0.12 branch are bugs but not blockers, and that we know are not API
+changes that would break backward compatibility.
+
+A good example is for instance the inclusion of the full ICU data in binary
+installers for OS X and Windows.
+
+## Node.js' Website
+
+Wyatt Preul and other contributors have been very active recently in
+integrating contributions to the Node.js' website that had been on hold for a
+while. The core team discussed some of the current contributions/issues as
+well as potential future improvements.
+
+### Security page
+
+One of these contributions is [the addition of a page dedicated to security
+related informations](https://github.com/joyent/node-website/pull/60). In
+order to make progress on that front, Wyatt needs the approval from the core
+team.
+
+### Future work on documentation
+
+In the future, ideally users would be able to choose the version of the API
+documentation they want to read. More general documentation (e.g tutorials,
+best practices, etc) would also be very welcome. However, the goal would be to
+not recommend any specific third party modules or application. A good example
+of some more general documentation would be an article on "How to use Node.js'
+http module efficiently?"
+
+The team agreed on updating the documentation as soon as possible. In
+practice, that means as soon as documentation PRs are landed. The Makefile
+included in Node.js' source repository should already make this easy.
+
+Regarding the merge of documentation changes, they should follow the same
+process as code changes. Documentation changes should be made in the oldest
+supported version that is affected, and merges should happen as soon as
+possible and should land in any version also affected by the change.
+
+### Discussions on the process to add a new page
+
+The participants agreed that before adding any new page to the Website, the
+core team should approve it by adding a comment in the associated pull-request
+page on GitHub.
+
+## Other dicussions
+
+### Development process
+
+There has been some discussions on how and when to land contributions in the
+source tree, and when to merge them into other branches. The team agreed on
+merging early and often, which hasn't necessarily been the case recently.
+
+Changes should be landed in the branch representing the oldest supported
+version affected by the change (v0.10 as of now). Merges should be done as
+soon as possible in branches representing any other version affected.
+
+The team also agreed to try to use GitHub milestones more. Three new
+milestones have been created: 0.11.16, 0.12.0 and 0.12.1. The team should make
+sure that any issue or PR that should be considered for these releases be
+added to the appropriate milestone.
+
+However, milestones on GitHub are quite limited. For instance, it is not
+possible to add an issue or a PR to more than one milestone. When this is
+needed, labels can be used to add the appriopriate information.
+
+### ICU support
+
+ICU will be enabled for as many platforms as possible (with `--with-intl=small-
+icu`, which includes only the English locale) in the 0.11.15 release. Steven R.
+Loomis and Julien Gilli are currently working on fixing the latest remaining
+issues. As of today, all builds and tests pass on all supported platforms, but
+some PRs need to be reviewed and landed.
+
+The 0.12.0 release will not be blocked by these issues. In the worse case,
+platforms for which ICU support is not working properly will be fixed in the
+0.12.1 release.
+
+Support for full ICU data (with many more locales) will be provided in a later
+0.12.x release (ideally 0.12.1). Note that this will not change the `Intl`
+API, so there's no need to worry about backward compatibility.
+
+### OpenSSL patches queue and handling dependencies
+
+Chris Dickinson started to work on a way to use a patches queue to handle
+Node.js' dependency on OpenSSL.
+
+Ideally, instead of writing its own gyp files to build OpenSSL, Node.js would
+apply custom patches from a patch queue and use gyp only to drive OpenSSL's
+original build process (e.g `./configure && make && make install`).
+
+TODO Chris Dickinson: Could you please  mention the only patch that needs to
+be submitted upstream for OpenSSL? I think you mentioned something like a
+"return" patch?
+
+Ideally, that approach would be generalized to as many dependencies as
+possible (e.g zlib).
+
+### Recent changes to mdb
+
+TJ Fontaine has done some very exciting progress on mdb. He added a new
+`::jsscope` command that allows users to examine the content of a given
+function's closure. (TODO: TJ, could you please correct any
+approximation/mistake and add any relevant info?).
+
+### Planning of next core team meetings
+
+Every Tuesday, Chris Dickinson will send and e-mail to team@nodejs.org to ask
+for things people want to discuss on the next core team meeting happening
+every Thursday.
diff --git a/locale/uk/foundation/tsc/minutes/2014-12-18.md b/locale/uk/foundation/tsc/minutes/2014-12-18.md
new file mode 100755
index 0000000000000..502c1b9a9b403
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2014-12-18.md
@@ -0,0 +1,79 @@
+---
+title: Minutes for the Node.js core team meeting of 12/18/2014
+date: 2014-12-18
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Chris Dickinson
+* TJ Fontaine
+* Julien Gilli
+* Colin Ihrig
+* Steven R. Loomis
+
+## Update on ICU
+
+### Build process
+
+The team agreed that the download of ICU's source code should be opt-in
+instead of the default. This would bring node's ICU support more in line with
+the build process of most other projects. This is not considered a a blocker
+for 0.11.15.
+
+### Tests
+
+Standard tests have already been run on all supported platforms with node
+built with --with-intl=small-icu, and no error has been found. However, there
+is currently just one ICU specific test (in `test/simple/test-intl.js`).
+
+Tests for the support of full ICU data shipped with binary packages have
+started. They  pass for the OS X installer. Support for shipping full ICU data
+needs to be implemented on Windows (in the MSI installer), SmartOS and Linux
+(in binary tarballs). However, this is not a priority for the 0.12.0 release.
+
+There is currently no test in the node code base to test full ICU support, all
+tests for full ICU support have been done manually so far.
+
+#### Packaging full ICU data
+
+The team agreed to store full ICU data in a separate file located relative to
+node's binary. It will be loaded by computing its location at runtime relative
+to Node.j's executable path. Steven noted that ICU supports a list of paths to
+load data from, which could help to supports platforms like Windows that do
+not put the node binary in a separate "bin" subdirectory.
+
+The participants also agreed to implement this at the C++ layer.
+
+## 0.10.34 release
+
+The 0.10.34 version released on 12/17/2014 has three different issues:
+
+* SSL/TLS connections to some servers, including amazon servers throw an
+exception because of an untrusted certificate. Participants agreed to fix this
+issue by putting 1024 bits length certificates back in the trusted
+certificates store.
+
+* A minor timer issue due to a typo in a fix for a memory leak.
+
+* A less minor timer issue due to a bug in the refactoring of `_unrefActive`
+done to improve performance.
+
+## Discussions around tools for developers of Node
+
+The participants discussed about various tools that could improve the workflow
+of contributors to Node.js' core.
+
+### A tool to apply pull requests
+
+This tool could be an equivalent of `curl PR.patch | git am - --signoff`, with
+additional features like:
+
+* Adding metadata from the GitHub PR.
+* Updating the AUTHORS file.
+
+### nodebug.me command line version
+
+Chris Dickinson recently released a command line interface to its great
+http://nodebug.me/ issues/PRs triaging tool.
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-01-15.md b/locale/uk/foundation/tsc/minutes/2015-01-15.md
new file mode 100755
index 0000000000000..0a170c8a01ea5
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-01-15.md
@@ -0,0 +1,50 @@
+---
+title: Minutes for the Node.js core team meeting of 01/15/2015
+date: 2015-01-15
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Timothy J Fontaine
+* Julien Gilli
+* Robert Kowalski
+
+## Topics
+
+### Website
+
+The only topic that was discussed during this meeting was the Node.js website.
+
+#### HTTPS access
+
+Robert suggested adding HTTPS access for Node.js' website. TJ mentioned that
+there is already a HTTPS endpoint on the website, but that clients (browsers,
+etc.) are not *redirected* by default from http to https, because doing so was
+breaking a lot of people (e.g nvm).
+
+Proposed solution by TJ: redirect everything by default to https except
+nodejs.org/dist.
+
+Robert proposed to setup a clone of the website with this change to be able to
+test it.
+
+#### Documentation versions
+
+Robert suggested a new feature for the documentation available on Node.js'
+website: accessing docs for different versions.
+
+Robert asked if regenerating the documentation for versions older than 0.10
+makes sense. TJ mentioned that we probably don't want to go back further than
+0.10. However, participants agreed that in the future, publishing older
+documentation could be fun and/or interesting.
+
+TJ suggested that documentation generation tools could be refactored and
+published as npm packages so that they can work standalone. That could make
+generating documentation for different versions easier.
+
+TJ also pointed out that a significant SEO effort went into making sure that
+the latest Node.js documentation shows up when searching for Node
+documentation, and that any change to the website's documentation should
+preserve that.
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-01-22.md b/locale/uk/foundation/tsc/minutes/2015-01-22.md
new file mode 100755
index 0000000000000..0161ce99ec34c
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-01-22.md
@@ -0,0 +1,88 @@
+---
+title: Minutes for the Node.js core team meeting of 01/22/2015
+date: 2015-01-22
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Michael Dawson
+* Chris Dickinson
+* TJ Fontaine
+* Julien Gilli
+* Colin Ihrig
+* Robert Kowalski
+* Steven R Loomis
+* Trevor Norris
+
+## Minutes
+
+### Update on the state of 0.11.16
+
+#### Tool to update AUTHORS file
+
+The current tooling to update the AUTHORS and .mailmap file should be
+refactored to:
+- Order authors by name using a stable sort algorithm.
+- Update the .mailmap file with authors' email addresses.
+
+Julien has been assigned to this and work is in progress at
+https://github.com/joyent/node/pull/9088.
+
+Participants agreed that eventually the project should have more tooling to
+land changes from contributors and that these tools would also take care of
+updating authors files each time a contribution is integrated in the code
+repository.
+
+#### url.format/url.parse
+
+The only issue non-straightforward issue remaining in the 0.11.6 milestone is a
+[recent regression in
+`url.format`](https://github.com/joyent/node/issues/9070).
+
+Two discussions started, one that was about what can be done before v0.12.0 is
+released, and another one about what can be done post v0.12.0. Some
+participants mentioned that ultimately, the goal would probably be to conform
+to the whatwg spec and deprecate the current `url` module.
+
+All participants agreed that before v0.12.0 is released, `url.format` should
+throw on conflicting properties. Chris was assigned to this task.
+
+#### Target date
+
+The target date for releasing 0.11.16 is "as soon as possible". Being a
+development release, there's no constraint on which day of the week the
+release should be done.
+
+### Update on ICU (i18n) for 0.12.0
+
+Steven tested the English language support included in the v0.11.15 release.
+He mentioned that it seems to be working fine, but that he hadn't had the
+opportunity to test loading additional data.
+
+Robert, Steven and TJ also discussed updating the website to document how to
+load additional data.
+
+### Website / Documentation effort
+
+Robert and TJ discussed how to to factor out the documentation from the
+project. Robert also mentioned that he'd like to work with Chris on the
+website to integrate features/tools that are now available in io.js (for
+instance, comments in documentation).
+
+Robert also mentioned that he's going to check-in the website's configuration
+file in source control.
+
+### Node on Power processors
+
+Michael Dawson from IBM talked about Node.js on PowerPC processors. TJ and
+Michael agreed that the target for such a port would likely be 0.14.0. Michael
+mentioned that ideally the process of upstreaming changes to V8 would be done
+by that time. If not, there has been discussions recently between TJ and Chris
+on refactoring the dependencies management so that maintaining floating
+patches (also for other dependencies liek c-ares and OpenSSL) would be easier.
+
+### 0.10.36 release
+
+The 0.10.36 milestone is done, and the release is planned for today (Thursday
+January 22nd).
diff --git a/locale/uk/foundation/tsc/minutes/2015-01-29.md b/locale/uk/foundation/tsc/minutes/2015-01-29.md
new file mode 100755
index 0000000000000..434a0382bfb36
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-01-29.md
@@ -0,0 +1,50 @@
+---
+title: Minutes for the Node.js core team meeting of 01/29/2015
+date: 2015-01-29
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Michal Dawson
+* TJ Fontaine
+* Colin Ihrig
+* Julien Gilli
+* Robert Kowalski
+* James Snell
+
+## Website
+
+Robert: Partially redirected http -> https for api docs and docs. Only blog
+page missing. Learning about SNI. Documentation generation tool: created a
+tests suite that runs some smoke tests. Hopes to get a PR for that next week.
+
+TJ: We have a wildcard cert for the blog, so using this cert might be easier
+than using SNI.
+
+## 0.11.16 release
+
+Colin: has two bug fixes not API breaking that could go in for 0.11.16.
+
+TJ: Would like to put https://github.com/joyent/node/pull/8966 in v0.10. Colin
+hasn't tried to rebase it on v0.10, but will do today.
+
+## Building dependencies
+
+James: Working on refactoring the way dependencies (deps/) are built.
+
+TJ: The build refactoring should target the master branch, and then might get
+backported to v0.12.
+
+## PRs/Issues in io.js
+
+TJ: When we see bugs in io.js that are also in Node.js, then please report
+these bugs.
+
+James: I'm going to go through the recent changes in io.js and will report
+issues/PRs.
+
+## PowerPC support
+
+Michael, James and TJ: Jenkins agents building and running tests for the Power
+platform will be hooked up asap.
diff --git a/locale/uk/foundation/tsc/minutes/2015-02-05.md b/locale/uk/foundation/tsc/minutes/2015-02-05.md
new file mode 100755
index 0000000000000..fbc9fe82c4e5b
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-02-05.md
@@ -0,0 +1,66 @@
+---
+title: Minutes for the Node.js core team meeting of 02/05/2015
+date: 2015-02-05
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Michael Dawson
+* TJ Fontaine
+* Julien Gilli
+* Colin Ihrig
+* Trevor Norris
+* Wyatt Preul
+* James Snell
+
+## Discussions
+
+### 0.12.0 release
+
+Julien: Remaining issues to release 0.12.0 are in the 0.11.17 milestone on GitHub.
+Everyone agreed that there's no blocker for this release.
+
+TJ: will put a draft for blog post for release notes up and the rest of the team will review it.
+
+#### Native modules breakage
+
+TJ: some modules that don't use nan or other ways to build with V8 shipped by
+node v0.12.x will break. These modules will need to be fixed on a case by case
+basis.
+
+### Website
+
+Wyatt: security page published.
+
+### Post 0.12.0
+
+TJ: From now on, it would be nice if core team members would use
+https://github.com/joyent/git-apply-pr to land PRs/contributions. It's a work
+in progress, bug fixes/improvements are more than welcome!
+
+TJ: We may discuss what to integrate from the core team working group of the
+Node.js Advisory Board (https://github.com/joyent/nodejs-advisory-board)
+during the next core team call.
+
+### Testing downstream modules and applications
+
+Michael Dawson: need for higher level benchmarks (for upper layers like
+express, etc.).
+
+TJ: Some people have been working on downstream integration tests (for
+instance, Julien with test-node-apps)
+
+TJ: Downstream integration tests, downstream benchmarking desirable in the
+future.
+
+James: identify the top 120 most depended on modules, determine what core
+modules they use, and create a tests framework around that.
+
+Michael: Michael and James already have something simple that run tests for
+some npm modules.
+
+### Node summit
+
+TJ: Tentative meeting on Monday 2pm to 4pm: purely technical meeting about
+roadmap, not a meeting about governance.
diff --git a/locale/uk/foundation/tsc/minutes/2015-02-09.md b/locale/uk/foundation/tsc/minutes/2015-02-09.md
new file mode 100755
index 0000000000000..a3a7541ad96a5
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-02-09.md
@@ -0,0 +1,228 @@
+---
+title: Minutes for the Node Summit technical roadmap meeting of 02/09/2015
+date: 2015-02-09
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* Michael Dawson
+* TJ Fontaine
+* Julien Gilli
+* Jacob Groundwater
+* Steven Loomis
+* Trevor Norris
+* Issac Roth
+* Todd Moore
+* Dan Shaw
+* James Snell
+* Erik Toth
+
+## TJ: Updating V8 versions
+
+Difference between communities. Important for IBM's regarding upstream power port.
+
+Michael Dawson: Regarding porting to power, upstreamed 2 out of the three
+parts. Started discussions on optimizations. Hoping to get this upstreamed
+this quarter. It's gonna be a little longer for the zSeries support.
+
+TJ: proposed solution: being able to run the V8 runtome as a dynamic library.
+Potential issues: modules and user land code might have to perform runtime tests to
+figure out if specific features in the JavaScript runtime are present.
+
+Dan Shaw: How to handle Node.js' JavaScript APIs using recent runtime's
+capabilities (promises) that are not present in all versions of V8?
+
+TJ: That's already a problem today, and this proposed solution doesn't
+eliminate this problem. Maybe use the "engines" properties in package.json
+for user land modules to express their requirements.
+
+Dan Shaw: Do we need a baseline for a minimum supported set of
+language/runtime level features?
+
+TJ: Having a specification of a fundamental base layer on the runtime side.
+
+Alexis Campailla: How to handle different versions of V8?
+
+TJ: my preference would be to use something like node-addon-layer as an
+abstraction layer.
+
+Alexis, TJ: that would become the blessed V8/JSruntime API for binary add-ons.
+
+TJ: C++ ABI has worked so far, but probably because we've been lucky. So C API
+makes more sense and would be more robust accross different platforms.
+
+Alexis Campailla: What about nan?
+
+TJ: nan is a header only C++ library, so it wouldn't solve the case of loading
+runtimes dynamically. However, as a lot of users of Node.js use nan, we might
+have to provide a double abstraction.
+
+Isaac Roth: All of that sounds good, but it puts a lot of burden on module
+authors.
+
+TJ: Bert mentioned previously that using NaCl could be interesting.
+
+## Issues with specing what a Node.js runtime baseline is
+
+Erik Toth: Paypal has problems with JavaScript, not with Node.js. EcmaScript
+standard is a bit nebulous, and so talking about a platform identified with an
+Ecma Script version is very confusing.
+
+James Snell: That's why we would need a baseline spec for what would be a
+compatible Node.js runtime.
+
+IBM: Specs will be unsufficient, we'll need tests also.
+
+TJ: Asynchronous code can be made easier to troubleshoot with using other
+mechanisms than promises, for instance vasync module, or other tooling.
+
+Dan Shaw: ES6 2015/2016 is coming way faster than I expected. Node.js should be
+a runtime where we can run untranspiled/untransformed code. Problems with
+JavaScript should be separated from problems that we have with Node.js itself.
+
+Issac Roth: Promises, generators, etc. will happen anyway, so we have to
+support that.
+
+Issac Roth: Promises is a core abstraction, and so promises are unavoidable.
+
+TJ: Problem of re-using code written for the browser which uses promises.
+
+Trevor: What is the point of the discussion?
+
+Trevor: The interface between the JavaScript layer and the native layer is a
+mess, cleaning that up will allow to build whatever type of interface to the
+code native layer.
+
+Trevor: You can't transition all asynchronous APIs to promises (e.g event
+emitters)
+
+Trevor: 1st priority should be to refactor some core layers to use lower level
+APIs to improve performance (e.g http should use tcp_wrap instead of
+lib/net.js).
+
+Trevor: Before supporting promises at the core layer, we'd have to do some
+simplification work.
+
+Trevor: Supporting loading different runtimes will make supporting existing
+(memory monitors, tracking GC events, etc.) tooling much more difficult.
+
+## Issac Roth: Internationalization
+
+Issac Roght: Ability to translate/localize error messages.
+
+James Snell: One of IBM's mandate is to be able to ship code localized for 70
+countries, otherwise needs to get exceptions.
+
+TJ: Also, concept of cleaning up error messages/objects related to i18n of error
+messages.
+
+## Dan Shaw: We talked about abstracting V8, what about libuv?
+
+TJ: libuv doesn't fit the same kind of niche as V8. However, an abstraction
+layer would be helpful.
+
+Dan Shaw: Concern of how and when Node.js will catch up with libuv?
+
+TJ: At some point in the release cycle, we have to close the gates and we
+can't integrate latest versions of dependencies.
+
+TJ: Carefully scoped roadmap and more frequent releases should allow us to integrate
+newer versions of dependencies often.
+
+Isaac Roth: It will be difficult to get broad agreement on a roadmap. Usually,
+open source projects work by integrating changes organically from contributors
+dependening on what they want to work on.
+
+TJ: Have the requirement of at any time, the tip of the development
+branch can be used as a release candidate.
+
+## Alexis Campailla: Work to build all PRs on every supported platforms.
+
+Alexis Campailla: I've been doing some work to be able to build/test code from
+any GitHub pull request.
+
+## Alexis Campailla: Running benchmarks for Windows.
+
+Julien: Tracking benchmarks results accross every commit would be very useful
+to identify the causes of performance regressions.
+
+James Snell, Michael Dawson: IBM started to run benchmarks for downstream
+dependencies, and wants to do more of that.
+
+## TJ: cluster
+
+James: Cluster seems to be used only by 6 npm modules (grepped 'cluster'
+through 120 most used modules). However, these modules could (and probably)
+use pm2 or other abstraction on top of cluster.
+
+TJ: Cluster is mostly used internally by glue code.
+
+Alexis: Datagram socket not supported on Windows. There's a lot of room for
+improvement in the implementation.
+
+Isaac: Performance of the cluster module is not satisfying, made some
+comparison with nginx and cluster seems to be 3x slower. Could need a rewrite.
+
+Jacob: Lots of users who directly use cluster module, sometimes by just
+copy/pasting code from the doc. I would say cluster is used widely.
+
+TJ: Preference would have been to improve child_process and have userland
+modules implement clustering features.
+
+## James Snell: Crypto improvements
+
+James Snell : Better access to crypto hardware is needed.
+
+TJ: libressl came out with a very compelling C API that Node.js could use.
+
+## Julien Gilli: stricter APIs
+
+Julien Gilli: There are a lot of fragile APIs in Node.js. It makes these APIs
+hard to use correctly, and it is also very time consuming for contributors who
+help users troubleshoot issues related to misuses of APIs.
+
+Julien: Example of recent improvement was making net.Socket.setTimeout's API
+stricter.
+
+TJ: Differences between browser APIs strictness and Node.js API strictness.
+It's also a documentation effort and is related to better error messages.
+
+Erik Toth: Ecma has a formal type proposal that could be related.
+
+## Julien Gilli: lldb-v8
+
+Julien: lldb-v8 is a great tool that, if working more reliably with different
+versions of node, could help both users and the core team to investigate bugs.
+
+TJ: I believe IBM has another toolchain that they use.
+
+## Erik Toth: What's the plan with async_wrap?
+
+Dan Shaw: Gathering input from potential users currently.
+
+TJ: Some interesting output from the meeting in Vancouver last summer.
+
+Erik Toth: Lower level thing that we want to see where it goes.
+
+Jacob: Various needs for tracing, some fairly basic (intercepting what is
+logged by console.log), some much more advanced like inspecting V8 internals.
+Needs to move slowly to make sure these broad needs are satisfied.
+
+IBM: Performance is crucial.
+
+Isaac Roth: Had to constantly reimplement tracing solutions because of
+changing requirements from users. Maybe need to be very generic about this.
+
+TJ: My proposed solution was to inject calls to probes that are interpreted by
+platform-specific tracing frameworks (dtrace, ETW, etc.)
+
+Issac Roth: Building a more generic layer that other user land modules can
+build upon.
+
+## Closing comments and action items
+
+James Snell: Need to prioritize things.
+
+TJ: Post ideas for roadmap somewhere where people can comment.
diff --git a/locale/uk/foundation/tsc/minutes/2015-02-19.md b/locale/uk/foundation/tsc/minutes/2015-02-19.md
new file mode 100755
index 0000000000000..598ec6161c4c4
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-02-19.md
@@ -0,0 +1,193 @@
+---
+title: Minutes for the Node.js core team meeting of 02/19/2015
+date: 2015-02-19
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+### Present
+
+* Alexis Campailla
+* Michael Dawson
+* TJ Fontaine
+* Julien Gilli
+* Colin Ihrig
+* Steven Loomis
+* Bradley Meck
+* Trevor Norris
+* Wyatt Preul
+
+### Regrets
+* James Snell
+  * Working on:
+    * Enabling openssl tests during the build similar to how I enabled the v8 tests.
+    * Resource and message bundle support.
+
+* Robert Kowalski
+  * Progress:
+    * I fixed the bad merge for https://github.com/joyent/node-documentation-
+     generator and will continue to work on it, next items are .markdown
+     support and sending a PR to node and node-website to make use of the
+     module.
+
+    * It is [not possible any more to accidentally deploy an outdated version of
+     the website](https://github.com/joyent/node-website/commit/dc1ab6f2037a9005d7fc44e73001bf9067e25d5b).
+
+  * Blocked by:
+    * I'm still waiting for a fixed SSl Cert for https://blog.nodejs.org/ to
+    continue with https://github.com/joyent/node-website/issues/68.
+
+## Current state of v0.12.0
+
+### V8 issues
+
+Julien: A lot of issues related to V8 came up recently after v0.12.0 was
+released. I believe Trevor is working on most of them right now.
+
+Trevor: Yes, I'm currently investigating.
+
+#### V8 max_old_space issue
+
+See https://github.com/joyent/node/pull/9200#issuecomment-75001656.
+
+TJ: We'll float the patch as it's pretty uncontroversial.
+
+#### VM module
+
+See https://github.com/joyent/node/issues/9084.
+
+TJ: would like to reboot the VM module. Will do a writeup in
+https://github.com/joyent/node/issues/9084. Who would like to work on
+implementing the proposed enhancements?
+
+Colin: I would like to work on this.
+
+TJ: alright!
+
+#### let issue
+
+See https://github.com/joyent/node/issues/9113.
+
+TJ: This one should be able to be debugged with only d8 to identify if and
+what version of V8 introduced the bug.
+
+### node::Makecallback issue
+
+See https://github.com/joyent/node/issues/9245.
+
+Trevor: there's a case with some developers add-on where calling
+`MakeCallback` processes next tick callbacks. I'm working on a fix that would
+make calling MakeCallback safe in every case.
+
+### Security issue with shared OpenSSL
+
+See https://github.com/nodejs/node/pull/800.
+
+### --abort-on-uncaught-exception and domains
+
+Colin: abort on uncaught exception fix hasn't been forward ported to 0.12.0,
+so that prevents us from upgrading to 0.12.0.
+
+Julien: There's an issue in the 0.12.1 milestone that tracks this. See
+https://github.com/joyent/node/issues/8877.
+
+### Installer on Windows not updating PATH
+
+See https://github.com/joyent/node/issues/4356.
+
+Alexis: issue with installer on Windows. Julien: fixed in io.js. Alexis: I
+will take care of this.
+
+### TCP_NODELAY issue
+
+See https://github.com/joyent/node/issues/9235.
+
+Michael Dawson: I have a candidate for a patch, would like to get feedback on that.
+
+### test-http-destroyed-socket-write2.js failing on AIX
+
+See https://github.com/joyent/node/issues/9234.
+
+Michael Dawson: I also have a patch for that, feedback wanted.
+
+## Website
+
+Use tracing documentation as starting point for the general documentation.
+
+## i18n
+
+TJ: what's the status on the bug with data customiser.
+
+Steven: thought it was an endianness issue. Updated the wiki to warn users.
+
+Steven: want to make full data available. Currently testing his solution.
+
+Bradley Meck, TJ and Steven Loomis will discuss bundles and resources today.
+
+## Issues triaging and general workflow
+
+Julien: I submitted a proposal to improve our workflow here:
+https://gist.github.com/misterdjules/50d78ed4b0c5a156edd1.
+
+Steven: It would be nice to know what's the focus on a release, so that we
+know what issues to put in the next milestones.
+
+Steven: Having the meeting to be a go/no-go meeting would help in being more
+efficient in this.
+
+Alexis: Doing triaging during weekly meetings would also be beneficial.
+
+TJ: call tomorrow where everyone comes up with a list of priorities for next
+milestone.
+
+TJ: call tomorrow to discuss the proposal sent by Julien.
+
+## libuv upgrade
+
+See https://github.com/joyent/node/pull/9179.
+
+TJ: Caveats in the GitHub issue are the only concerns that I have. enum/int
+ABI issue, not sure if it's an actual issue or not. Would like to get more
+feedback from more knowledgeable C/C++ users. Concerned by some of the
+behavior changes in libuv.
+
+Alexis: Users can use type casting if they have issues with the sizeof(enum)
+vs sizeof(int).
+
+TJ: also, probably doesn't affect a lot of packages since it affects only the
+`uv_tty` API.
+
+Julien: Failures on Windows.
+
+Alexis: I can help to look into that.
+
+## Team organization updates
+
+TJ: I would like to propose that Colin move from apprentice to core team
+member, and that Michael and Steven be appointed as apprenticies.
+
+## Publication of minutes
+
+TJ: we want to publish every meeting's minutes on the website.
+
+## Testing
+
+Michael Dawson: what tests should be run on a regular basis by any
+implementation?
+
+TJ: would like to have make test run as many tests suite as possible. At least
+we can make it run simple, message, gc and internet today.
+
+Michael Dawson: When do pummel, internet and other tests are run?
+
+TJ: Historically, we've run them when building nightlies for instance. Some
+pummel tests take a long time to run on virtualized windows environments.
+
+TJ, Michael Dawson: would like to have a mechanism to have platform specific
+tests.
+
+## Next core team meeting
+
+Thursday February 26th 2015.
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-02-26.md b/locale/uk/foundation/tsc/minutes/2015-02-26.md
new file mode 100755
index 0000000000000..1144d0ec5ff7d
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-02-26.md
@@ -0,0 +1,79 @@
+---
+title: Minutes for the Node.js core team meeting of 02/26/2015
+date: 2015-02-26
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Present
+-----
+- Alexis Campailla
+- Colin Ihrig
+- TJ Fontaine
+- James Snell
+- Robert Kowalski
+- Michael Dawson
+- Chris Dickinson
+
+## Discussion
+
+### General
+
+TJ has pull request to update the core team - active contributors page.
+Attendees reviewed and it should go out imminently.
+
+Discussed proposal to have github project for core team to capture
+discussions, initially to be used to capture some ci configuration. TJ is
+going to set this up.
+
+### Delivery of ICU data
+
+Steven Loomis mentioned there was a suggestion to delivery to an npm.
+Attendees seemed to like this idea and discussion will be carried forward in
+https://github.com/joyent/node/pull/9091.
+
+### Website updates
+
+Discussion of proposal to rewrite node.js.org to https minus a few exceptions.
+Expecting pull request in next week or so.
+
+### Node Internationalization
+
+James looking at 2 aspects:
+
+* Internationalize Node itself, going to start on this next week.  Will use ICU
+if present, if not still need to figure out what the fallback will be.
+* Resource bundle loading.
+
+
+### Next Releases
+
+#### 0.10.X
+
+* In maintenance mode, new releases generally to  address security or larger
+performance issues.
+* 0.10.37 to go out this week, early next.  Main update is newer version of
+libuv.
+* TJ asked Michael to look to do some pre-validation on AIX.
+
+#### 0.12.X
+
+* Some failing tests in 0.12 head now.
+* Working to get jenkins job in place that can be run before integrating
+changes.
+* Seeing some memory issues, some because node generates more garbage some
+because V8 gc is less aggressive. TJ still investigating some others which
+look to be real issues.
+
+#### 0.12.1 release
+
+Key priority issues:
+
+* libuv upgrade to 1.4, some issues seen on Windows, Alexis investigating.
+* VM.
+* joyent/node#9628 pull request for passing in 0 for port.
+* Set server issue (James investigating).
+* Abort on uncaught exception (io.js issue #836 for reference).
+
+Colin raised issue of pull request to add abort to http.
+Since this would change the API needs to be done in 0.14 as opposed to 0.12.
+TJ suggested a work around for current releases.
diff --git a/locale/uk/foundation/tsc/minutes/2015-03-05.md b/locale/uk/foundation/tsc/minutes/2015-03-05.md
new file mode 100755
index 0000000000000..3fc442d88f628
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-03-05.md
@@ -0,0 +1,78 @@
+---
+title: Minutes for the Node.js core team meeting on 03/05/2015
+date: 2015-03-05
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Present
+-----
+- Alexis Campailla
+- James Snell
+- Michael Dawson
+- Julien Gilli
+- Trevor Norris
+- Steven Loomis
+
+## Discussion
+
+### General
+
+### Leap second
+
+There will be a leap second between July 30th and June 1st. There was
+discussion with respect to how this might affect Node. From the consumer
+perspective this may seen as clock drift which is quite common. In 0.12 Node
+uses absolute times, not dates. 0.10.X used to use dates. Most time dependant
+functions are handled by either libuv or v8. We should likely ask these
+communities what they expect the effect of the leap second to be. Michael to
+open a libuv issue to ask this question and also to see if we can  find who is
+the right person to ask in respect to V8. Steven volunteered to write up a FAQ
+covering the issue.
+
+### Better way to manage dependencies
+
+Alexis initiated the discussion on a better way to manage dependencies and
+will write up a proposal. It would be nice if tests for Node ran in the test
+suites executed by the dependency teams. Failing that we should look at
+pulling in the dependencies more frequently in our CI, run the Node tests and
+provide feedback to the external teams.
+
+### Next releases
+
+#### 0.10.37
+
+* Upgrade to libuv 0.10.36 in progress, code review planned for today, should
+land soon.
+
+* 0.10.37 will possibly go out next week.
+
+* Priority issues for 0.10.37 - issue #9092 and reverting change to url that
+caused a regression.
+
+#### 0.12.1 release
+
+Key priority issues:
+
+* libuv upgrade to 1.4.0, down to 1 test failing on OSX, ok on windows side now,
+Julien working on this.
+
+* V8 lateral upgrade, Trevor still working on identifying goood V8 level (issue
+9185).
+
+* Issue #8540, #9204 discussing whether to pull fix from io.js or one developed in
+Node.js based on which is better.
+
+* Issue #9245, Trevor working on this, 2 ways to make callback and depending on
+which one is called can lead to subtle bugs.
+
+* Issue #9339 - to be reviewed and committed
+
+* Issue #9317 - fix available in io.js other core team members to review to see
+if it can be pulled in.
+
+* Issue #9235 - ensuring NODELAY is on for all platforms.  Michael would like it
+on for AIX Julien/Alexis to review in context of Windows and other platforms.
+
+* Issue #9334 - tests fail when run in deep directory paths.  Julien and other
+core team members to review and comment.
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-03-12.md b/locale/uk/foundation/tsc/minutes/2015-03-12.md
new file mode 100755
index 0000000000000..6ee08b737deb3
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-03-12.md
@@ -0,0 +1,154 @@
+---
+title: Minutes for the Node.js core team meeting of 03/12/2015
+date: 2015-03-12
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* Julien Gilli
+* Michael Dawson
+* Steven Loomis
+* TJ Fontaine
+* Trevor Norris
+
+## Discussion
+
+### Upcoming releases
+
+#### v0.10.37
+
+Julien: All binaries, files and tarballs are available at
+https://nodejs.org/dist/v0.10.37. I'm currently coordinating with people from
+Heroku and New Relic to have it tested. Once I hear back from them, we can
+make the announcement.
+
+TJ: It would be great to have a channel where we announce release candidates,
+and have other people willing to test them subscribe to it.
+
+Michael: Once we know there are binaries we can put that into our testing
+queue.
+
+Alexis: Microsoft doesn't have additional tests besides the ones that already
+run on Jenkins.
+
+TJ: We should write a proposal for an improved release workflow.
+
+#### v0.12.1
+
+##### libuv upgrade to 1.4.0
+
+Julien: Discussion around floating patches on top of 1.4.0 or waiting for
+1.5.0 to float less patches.
+
+TJ,Trevor: Upgrade to the latest 1.4.x, float patches and rerun the tests.
+
+Trevor: We should probably make sure to integrate
+https://github.com/joyent/node/issues/9342.
+
+##### V8 "lateral" upgrade
+
+Trevor: Almost there.
+
+##### Various V8 bugs
+
+TJ: It would be great to track down current V8 bugs with people who have
+experience with codegen in V8.
+
+Michael: We can probably work on that.
+
+##### ICU related issues
+
+Steven: Looking into doing an npm based install of full-ICU data.
+
+##### FreeBSD crash
+
+TJ will provision a FreeBSD server for Trevor to take a look at this issue.
+
+##### Other issues
+
+Michael: https://github.com/joyent/node/issues/9317, I will create a PR for
+that.
+
+Michael: https://github.com/joyent/node/issues/9334, I'll take a look at the
+comments.
+
+##### VM module
+
+TJ: VM module leaks a lot of memory, basically never frees any resource.
+
+### Port of V8 to Power and other IBM architectures
+
+Michael: We are well into our testing cycle for v0.12.0 on power.
+
+### Floating patches on top of V8
+
+Michael: How open are we to floating patches on V8? For instance, issue
+with profiler performance.
+
+Steven: Also https://code.google.com/p/v8/issues/detail?id=3348.
+
+TJ: We're going to have more scenarios where we need to float patches. We need
+a way to manage a queue of patches (e.g quilt). Long term solution: have a
+vanilla V8 in tree and a queue of patches.
+
+Alexis: Other way is to fork repositories, didn't have time to write the
+proposal I talked about last time, but will do as soon as possible.
+
+TJ: Problem with having our own forks is not every dependency uses Git.
+
+### Leap second
+
+Steven: started an FAQ on leap seconds:
+https://gist.github.com/srl295/e74710ae42e8d13b96e7.
+
+TJ: Does faketime have a way to "simulate leap seconds"?
+
+Julien: I don't think so, but it's worth taking a look.
+
+TJ: Maybe Steven you could use that to run tests regarding leap seconds.
+
+TJ: libuv uses monotonic time for all its operations. In node, the last
+remaining place where we were using wall clock has been fixed in 0.10.30 or
+0.10.31.
+
+Trevor: libuv uses epoll_wait, does it use monotonic/hrtime on all
+systems?
+
+TJ: Generally yes.
+
+Alexis: On Windows, for node v0.12 yes, for node v0.10 no.
+
+Alexis: We can backport the hrtime fix for v0.10.
+
+Michael: OpenSSL, c-ares and npm seem to use wall clock (gettimeofday).
+
+TJ: Apparently c-ares uses gettimeofday only if it can't use a clock
+monotonic.
+
+Alexis, Steven: Potential issues with leap seconds: negative time difference,
+minutes taking more than 60 seconds.
+
+Julien: OpenSSL might be using wall clock not for comparing dates/times, but
+for instance for inserting dates into certificates.
+
+TJ: To conclude, largest concern is backporting hrtime fix to v0.10 on
+windows.
+
+Steven: Would be great to have a statement from V8 and OpenSSL.
+
+### Governance proposal
+
+TJ: I want to make sure that everyone can give feedback, so please reach out
+to me if you'd like to talk about it.
+
+Steven, Michael: Could be useful to have a separate meeting soon to discuss
+that.
+
+TJ: Will find a time slot that works for everyone soon.
+
+### Update on workflow/issues management proposal
+
+Julien: Still gathering feedback from other projects, goal is to start using
+it starting next week.
diff --git a/locale/uk/foundation/tsc/minutes/2015-03-19.md b/locale/uk/foundation/tsc/minutes/2015-03-19.md
new file mode 100755
index 0000000000000..c72f191a630dd
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-03-19.md
@@ -0,0 +1,88 @@
+---
+title: Minutes for the Node.js core team meeting of 03/19/2015
+date: 2015-03-19
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* James Snell
+* Julien Gilli
+* Michael Dawson
+* Steven Loomis
+* TJ Fontaine
+* Trevor Norris
+
+## Discussion
+
+New Openssl vulnerabilities reported today. Important but not a panic. Node
+uses openssl 1.0.1  and higher severity issues were reported against 1.0.2.
+James will create pull request and we'd like to see the update go out either
+Friday (torrow) or Monday.
+
+We discussed different options and agreed that 0.10.38 will be the same as
+0.10.37 plus the new openssl level and similarlty 0.12.1 will be the same as
+0.12.0 plus the new openssl level.
+
+There was some discussion about including the changes that have gone into the
+existing 0.12.1 branch but we agreed it was best not to do this.
+
+### Upcoming releases
+
+#### v0.10.38
+
+Only discussion was related to openssl issue as covered above.
+
+#### v0.12.1
+
+Trevor: still having some issues with building on BSD 10.1. TJ is going to
+have a look at it to see if he can help out.
+
+Libuv upgrade, should be ready just need to run accept job to pull it in.
+
+Michael raised issue 9439 which covers a patch to v8 to bring profiling
+for 0.12.X back up to the level of 0.10.X. TJ identified that the next
+steps for 0.12.2 are:
+
+* Libuv update.
+* Lateral V8 change.
+* floating patches for v8.
+* Look at adding the floating patch for 9439.
+
+### Update on workflow/issues management proposal
+
+Julien: We will roll this out in stages over the new few weeks. At this point
+we should be using the node-accept-pull-request jenkins jobs to
+accept/validate pull requests. Julien will add to node websites the parts we
+are putting into use. Next to be added is nomination for milestones which
+we'll probably start using in a couple of weeks.
+
+### General
+
+#### Next V8 upgrade
+
+Michael asked about how we'd choose the next V8 version. TJ confirmed it would
+most likely be the current stable V8 level when 0.13/0.14 get started, however
+there are issues around the toolset needed to support the latest V8 releases
+and how we can maintain support for older OS levels might affect this.
+
+#### ICU crash - Issue 9361
+
+Fix for this is already integrated in a later V8 version. Steven Loomis is
+looking at this and there is a pull request ready to backport the existing
+fix. There was some discussion about the best approach and in the end we
+agreed the existing fix is appropriate and we should just backport it to
+0.12.2.
+
+#### Testing release candidates
+
+Julien is talking with some groups about doing some pre-release testing on
+release candidates. TJ suggested we should ask for volunteers on the blog or
+twitter. It will need to be a full blown release candiate due to gyp
+dependencies etc. Julien will write up a proposal.
+
+#### Tooling around issues/PR triaging
+
+There was some discussion about whether GitHub is the best tooling, in general
+more investigation/discussion is required before doing anything.
diff --git a/locale/uk/foundation/tsc/minutes/2015-03-26.md b/locale/uk/foundation/tsc/minutes/2015-03-26.md
new file mode 100755
index 0000000000000..e55e44060ae86
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-03-26.md
@@ -0,0 +1,152 @@
+---
+title: Minutes for the Node.js core team meeting of 03/26/2015
+date: 2015-03-26
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* Colin Ihrig
+* James Snell
+* Julien Gilli
+* Michael Dawson
+* Robert Kowalski
+* TJ Fontaine
+* Trevor Norris
+* Wyatt Preul
+
+## Discussions
+
+### Foundation charter
+
+TJ: We want to make sure that we're participating in this process.
+
+TJ: Now could be a good time for everyone to talk about tools they know that
+would work well to help the work done by the foundation.
+
+### Benchmarks
+
+Michael: We'd like to have tools to make sure there's no performance
+regression between releases.
+
+Michael: We could use https://github.com/acmeair/acmeair, and there's a
+Node.js version: https://github.com/acmeair/acmeair-nodejs.
+
+Michael: Have talked to maintainer of acme-air and they are willing to
+collaborate, we could also get them to give us an intro to the benchmark if
+that makes sense.
+
+TJ: We also want a benchmark specifically for low-latency and high
+concurrency.
+
+TJ: How do we want to start with that? Also should assess what we already have.
+
+Michael: Might want to form a performance working group.
+
+Michael: Good idea to reach out to io.js too.
+
+TJ to forward to Michael contacts at Yahoo, Netflix and Paypal that might be
+interested in participating.
+
+### OOB OSX
+
+v0.10.37 fixed an issue in kqueue regarding out of band data. The reporter
+never heard back from Apple, and no CVE  has been assigned. Could lead to a
+DOS scenario.
+
+### Security issue in vm.js
+
+TJ: Got an email about a user concerned about the fact that the parent of a
+sliced buffer can be traversed across VMs.
+
+Trevor: this has been known for a while.
+
+TJ: sandbox is a not a security context sandbox, but more a "programming
+sandbox".
+
+TJ: In my opinion, mostly a documentation bug on our part.
+
+### Putting a link to IBM Node.js SDK on nodejs.org
+
+TJ: I don't have any objection. What link would we use?
+
+James: We have a landing page for this SDK for Node.js. Easiest thing would be
+to land to this page.
+
+TJ: I want to avoid confusion if the versions are not in sync between the two
+projects.
+
+James: We can make it clear on this landing page.
+
+TJ: Can the additional debugging stuff be upstreamed?
+
+Michael: We want to make that available, maybe via npm. Same for IDDE.
+
+TJ: Would be great to have the additional debugging support in the code base
+too, so that people can load core files from z platforms and do debugging.
+
+## Releases
+
+### v0.10.38
+
+Julien: Would be great to document how to upgrade OpenSSL.
+
+James: Had an item in my todo list to do that.
+
+Julien: We can team up to do that.
+
+TJ: I would suggest to start shipping an alternate binary linked with shared
+dynamic libraries for libuv, OpenSSL, etc.
+
+TJ: Might be difficult to do that for dependencies where we have floating
+patches.
+
+### v0.12.2
+
+Julien: New P-1 issue added: debugger is very slow, takes 1 or 2 minutes to do
+basic operations, see https://github.com/joyent/node/issues/9125 for more
+information.
+
+Trevor: There's a major issue with buffer
+(https://github.com/joyent/node/issues/9180) that causes asserts for a lot of
+users, can we get a v0.12.2 release asap with the current state of v0.12, and
+move everything else from the 0.12.2 milestone to 0.12.3?
+
+Julien: We may also want to add an upgrade to npm 2.7.3 for this release.
+
+Trevor: See also https://github.com/joyent/node/issues/14165.
+
+No objection from anyone.
+
+## Tool for testing npm modules
+
+James: Currently porting from Python to Node.js. Will put in a separate repo.
+Some issues regarding non-uniform tests output and additional npm
+dependencies.
+
+## Discussions with PM2 developers
+
+TJ: Met recently with developers from PM2. Would like to have a discussion
+with them around potential improvements to the cluster module.
+
+## Crypto performance
+
+James: Interested in getting some work to propose enhancements to crypto
+performance. What do you think about adding async mechanisms to crypto?
+
+TJ: Could have a discussion of what we'd like as an async API. Could also
+broaden the discussion to a long term goal of having better TLS performance.
+That will be even more important with HTTP/2.
+
+James: Can start the conversation with a proposal of improvements.
+
+## Website
+
+TJ: We'll have a new single certificate with support for subdomains.
+
+Robert: Need some feedback on https://github.com/joyent/node-
+website/issues/81.
+
+Robert: Made changes to the license here: https://github.com/joyent/node-
+website/pull/93.
diff --git a/locale/uk/foundation/tsc/minutes/2015-04-09.md b/locale/uk/foundation/tsc/minutes/2015-04-09.md
new file mode 100755
index 0000000000000..7ab99d2dc74a2
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-04-09.md
@@ -0,0 +1,115 @@
+---
+title: Minutes for the Node.js core team meeting of 04/09/2015
+date: 2015-04-09
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* Colin Ihrig
+* Julien Gilli
+* James Snell
+* Michael Dawson
+* TJ Fontaine
+
+## Discussions
+
+### Agenda
+
+* RC4 vulnerability.
+* v0.12.3 status.
+* dev policy sync before meeting.
+
+### RC4 vulnerability
+
+We want to iterate a few more times before we release.
+
+James has a new set of PRs for review.
+
+Julien ran the ssl upgrade test, and found a potential security issue.
+
+There is an additional note for getLegacyCiphers, throwing for an unknown
+string.
+
+How do we want to release this? Is it separate, or should we include it along
+with a blog post and documentation about the changes?
+
+IBM security identified it as being important enough to have a fix.
+
+Are we doing our normal v0.12.3 gestation, or are we doing a v0.12.2 with only
+this fix?
+
+io.js updated their defaults a month ago.
+
+Continue conversation on email and make a decision on the release for Monday.
+
+This particular issue should be handled for v0.10.39, but for v0.12.3 we
+include what has been already landed.
+
+Potential Security Issue:
+* Julien will send an email to security@ with a description for a discussion.
+* Validate the concerns of this issue and determine if it should be included
+with the RC4 fix.
+
+IBM runs a lot of tests on multiple platforms for their releases, and the RC4
+fixes for v0.10 have been internally validated.
+
+James is looking at improving the SSL/TLS cipher test suite
+
+### v0.12.3
+
+Not much has changed since last week, as many people were working on
+Foundation pieces.
+
+Many of the P-1 issues can be easily managed once we have more time.
+
+Are any small enough for inclusion before Monday.
+
+A FreeBSD fix still needs more iteration.
+
+Ideally we continue focusing on the RC4 and related security issues.
+
+No one has indicated being blocked on others.
+
+### Release Candidate work 
+
+Julien submitted a PR to describe the policy.
+
+Ideally running the release of v0.12.4 in this policy.
+
+Some platform providers are not sure about the RC portion will be useful for
+them.
+
+TJ would like to introduce the Yahoo team to Julien to see if they'd be
+interested in release candidates.
+
+Also would be good to reach out to Forrest for npm mechanisms.
+
+node-gyp still relies on the internet.
+
+### Windows MSI install
+
+We should look to unify on install.py and the location.
+
+Deployment on windows is particularly hard.
+
+Compilers for production deployments is odd.
+
+JXCore has an API/ABI shim and engine abstraction layer.
+ 
+### Development Policy
+
+Meeting today at 12PM PDT.
+
+Work between James and Mikeal on describing the iojs policy and adding in the
+things that the Node.js core team cares about.
+
+Trying to walk the line and balance innovation and speed with stability.
+
+The core team needs to provide feedback, before and during the meeting.
+
+Convergence Working Group would merge the code bases between iojs and Node.js,
+in the mean time the projects would work independently.
+
+The potential release number would be 2.0.0.
diff --git a/locale/uk/foundation/tsc/minutes/2015-04-16.md b/locale/uk/foundation/tsc/minutes/2015-04-16.md
new file mode 100755
index 0000000000000..6881f840de177
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-04-16.md
@@ -0,0 +1,151 @@
+---
+title: Minutes for the Node.js core team meeting of 2015-04-16
+date: 2015-04-16
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* [Alexis Campailla](https://github.com/orangemocha)
+* [Colin Ihrig](https://github.com/cjihrig)
+* [Julien Gilli](https://github.com/misterdjules)
+* [Michael Dawson](https://github.com/mhdawson)
+* [TJ Fontaine](https://github.com/tjfontaine)
+* [Steven R. Loomis](https://github.com/srl295) (scribe)
+
+## Discussions
+
+### Releases
+
+#### v0.12.3
+
+JGI: some progress , still slow.
+On v8 upgrade [#9185](https://github.com/joyent/node/pull/9185), made
+progress, trevor is working on until next week.
+Additional patches all in the comments.
+Help wanted to finish v8 integration.
+
+##### Profiler
+
+JGI: [#14576](https://github.com/joyent/node/issues/14576) An issue -
+profiler causing v8 to stall?
+
+##### FreeBSD flag
+
+JGI: [#8540](https://github.com/joyent/node/issues/8540) - FreeBSD
+flag. Input needed. The parameter is exposed to JS.
+
+JGI: finishing other P-1 issues before release.
+
+### Other discussions
+
+#### Bar Mitzvah
+
+JGI: [#15445](https://github.com/joyent/node/issues/15445) - Bar
+Mitzvah issue - 2 questions, feedback needed:
+
+* Need to be able to get prior (insecure) behavior back if needed.
+* How best to name the option?
+
+MD: Don't want to do this in perpetuity - RC4. Expand documentation.
+
+SRL: Should it be named 'enable-insecure'?
+
+JGI: Always possible for users to specify custom cipher lists.
+
+TJ: Balance between platform users and application users.
+
+JGI: Need to get the main scenarios, come up with use cases first.
+
+MD: This is a tempoary fix, most people (hopefully) are using defaults.
+
+TJ: This setting is used more in minor versions, when people are
+bringing up [some version of an] app.
+
+#### Wrong checksum for node v0.12.2
+
+JGI: This issue will be investigated.
+
+#### Leap Second
+
+SRL: Existing issue: [#9382](https://github.com/joyent/node/issues/9382)
+
+SRL: Probably can do more testing.
+
+TJ / JGI: - did a test suitewith faketime. That may not work on windows.
+
+TJ: "no known issues" - some may want more documentation.
+
+TJ: Blog post, link to documentation/faq.
+
+TJ/AC: Clock used on windows for 0.10 is less precise but still monotonic.
+
+MD: Google response on v8 - "thats a good question".
+
+TJ: This should be first class documentation.
+
+Action: SRL to open a new ticket. Document that Date.now != how timers work.
+(in `doc/timers`).
+
+#### Documentation of OpenSSL upgrades
+
+JGI: Need to document openssl upgrades:
+* Upgrades can be confusing
+* Often these upgrades are done in 'less than ideal' situations
+(pressure to fix a critical issue).
+
+#### Documenting how to upgrade v8
+
+James and Julien are working on docs of how to do the update,.
+Missing some of the history, but at least it can be well understood.
+Ideally anyone on the team or community can understand how it is done.
+
+TJ: no specific home for this doc, in the wiki right now (link)
+
+JGI: Current state of the documentation may not include all floating patches.
+
+TJ: docs should live in the code eventually.
+JGI: may take another form.
+
+Action: SRL: document how to upgrade ICU.
+
+#### Joint node.js/io.js meetings
+
+CI: joint TC call.
+
+ALL: People don't want extra meetings - may be a little disorganized.
+
+TJ: - hard but necessary -- there's a lot of work to do around merging
+two projects:
+
+* Need to work together to maintain stable release (LTS/platform etc)
+has to be comfortable integrating into the entire project.
+* Innovation + ideals of LTS working group.  Required amount of tension.
+* Hopefully good agendas.
+
+SRL: More of a concatenation than a merge. agenda and time management
+will become critical.
+
+TJ: Needs time management - "we have 5 minutes to discuss this".
+
+ALL: Proposed time is "Wednesday and it has been 1pm-2pm pacific since PDT
+kicked in (it was noon-1 before that)."
+
+ALL: This time seemed good.
+
+SRL: Formal scheduling of agenda items?
+
+TJ: Yes, people should propose a time length when items come in.
+
+JGI: Two goals - 1. identify divergence, and 2. get used to other members.
+
+JGI: Maybe 15 minutes joint meeting, then individual meetings if needed.
+
+#### Call for help triaging incoming bugs
+
+JGI: Help wanted triaging incoming bugs.
+
+#### Crash from command line (Intl)
+
+SRL: investigating crash from command line
+[#9361](https://github.com/joyent/node/issues/9361).
diff --git a/locale/uk/foundation/tsc/minutes/2015-04-24.md b/locale/uk/foundation/tsc/minutes/2015-04-24.md
new file mode 100755
index 0000000000000..c728864071b9d
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-04-24.md
@@ -0,0 +1,70 @@
+---
+title: Minutes for the Node.js core team meeting of 04/24/2015
+date: 2015-04-24
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* James Snell
+* Julien Gilli
+* Michael Dawson
+* Steven Loomis
+* TJ Fontaine
+* Colin Ihrig
+
+### Upcoming releases
+
+#### v0.10.39
+
+Discussion around removal of RC4 to address Bar Mitzva attack.  Progress
+being made, need to update to clarify precedence of command line 
+options (https://github.com/joyent/node/pull/19148), update code/tests to 
+match this descripton (James), finalize release notes (Julien with input from all) 
+and then do one final review before release (all).   Important that we add
+tests to make sure merge with 0.12.X can be easily validated.
+
+#### v0.12.3
+
+Same discussion of removal of RC4 to address Bar Mitzva attack.  Just need
+to do commits in a way that facilitates merge from 0.10.X later
+
+Julien: looking at completing V8 lateral upgrade.  Will be v0.12.3 unless
+removal of RC4 is ready before it is.
+
+### Internationalization
+
+James: io.js looking at Globalize as an alternative, because they would like
+it to be more modular in terms of how features (like collation)/languages get pulled in.
+
+If the two code bases are merged not including ICU would be a forced break.  Current
+understanding is that merged code base would be everything from both code bases.  
+If instead individual pieces are not going to be included then likely convergence working 
+group would need to build list to cover these pieces and work through an appropriate
+approach to deal with each one. 
+
+In advance, we should start looking to see if we can make the inclusion of ICU more
+modular in a non breaking way.  Action: Michael to setup meeting with Steven/James
+to better understand dependencies between startup and V8 with respect to ICU.
+
+### Windows Build Issues
+
+Alexis working on PR to fix some windows build issues, will do review on PR
+
+### JxCore
+
+Michael/James talked to JxCore team to see if the C API that they have for separating
+core from Javascript engine and multi-isolate support might be starting point
+for Node.  JxCore team seems interested in collaborating.  Next logical step
+likely to form working group in Foundation to cover these two. 
+
+TJ: We should also be looking at formalizing the internal layer (for example 
+TCPWrap) as part of introducing the required separation.
+
+### Dev Policy
+
+James: looking to add some representation for user requirements. Proposed a working
+group, alternative may be an evolution of the advisory board into that role.
+
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-04-30.md b/locale/uk/foundation/tsc/minutes/2015-04-30.md
new file mode 100755
index 0000000000000..40614b9fa23a0
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-04-30.md
@@ -0,0 +1,130 @@
+---
+title: Minutes for the Node.js core team meeting of 04/30/2015
+date: 2015-04-30
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Colin Ihrig.
+* James Snell.
+* Julien Gilli.
+* Michael Dawson.
+* Steven Loomis.
+* Trevor Norris.
+* Wyatt Preul.
+
+## Discussions
+
+### Upcoming releases
+
+#### 0.10.39
+
+##### Fixes to the bar mitzvah attacks
+
+James: Will update recent ciphers list changes with some fixes.
+
+Julien: Will review as soon as possible.
+
+##### TLS default ciphers not used if ciphers null or undefined
+
+Julien: See https://github.com/joyent/node/pull/23947. This must probably be
+considered before releasing the other changes to the default ciphers lists
+that have already landed in v0.10.
+
+##### Timer fixes
+
+Julien: Current PR here: https://github.com/joyent/node/pull/17203.
+
+Julien: Need more feedback on whether to land this in v0.10.39. Recent changes
+to the timers module broke a lot of users in the past few v0.10.x releases, so
+we definitely need to be careful. This one seems safer than the previous ones
+though.
+
+#### v0.12.3
+
+##### V8 lateral upgrade and other V8 fixes
+
+Julien: https://github.com/joyent/node/pull/18206 landed, as well as the
+floating patch to fix let bindings in for loops
+(https://github.com/joyent/node/pull/23948).
+
+#####  Upgrade npm to 2.8.4
+
+Julien: There's a PR from Forrest that upgrades to npm 2.8.4. It fixes some
+significant issues (including security issues). We will want to include an
+upgraded version of npm with the next v0.12 release. Will review this PR and
+land if tests pass and that version is still what makes sense.
+
+Michael: We could probably create a Jenkins job to run the test-npm make target.
+
+##### net/HTTP servers with implicit binding to IPv6 addresses
+
+Colin: This issue was reported a while ago, and we probably need to make a
+decision about it sooner than later:
+https://github.com/joyent/node/issues/9195.
+
+James: I would suggest updating the docs in 0.12, and wait to have more input
+to maybe make a change in behavior on master.
+
+Colin and ALL: agreed.
+
+### Convergence plan
+
+James: Initial convergance plan: https://github.com/jasnell/dev-policy/pull/66.
+
+James: nothing set in stone. Current plan:
+
+* io.js organization transfered to nodejs organization. Will keep everything
+they've already setup.
+* joyent/node and other joyent/node-related repos will also be transfered to
+this organization.
+* Both joyent/node and iojs/iojs repos would be under the foundation.
+* For the converged repo, a fork of iojs repo would be created.
+* New repo would be the next major release.
+
+James: Details for LTS policies still need to be figured out.
+
+James: Next work will be focused on the CI infrastructure.
+
+James: most importantly, need to agree that the merging process will be io.js
+forked and picking changes from joyent/node.
+
+James: Will also need to catalog other resources like twitter handles, domain
+names, etc.
+
+__Action Item:__ Julien to send James the list of assets used by the current
+CI platform.
+
+### Intl
+
+James: io.js not OK with current intl support in v0.12 due to lack of
+modularity and issues around new command line switches.
+
+James: Putting together a plan that would make sense so that we can track that
+refactoring. Would be targeted to 0.13, and would make it more palatable for
+the io.js team.
+
+Steven: Concerns around the data size, confident that this proposal will
+improve the user experience.
+
+Steven: What it doesn't address is splitting the data in micro pieces. Not
+convinced by the use case for that, especially due to the amount of work
+required.
+
+James: In discussions witb Bert and others to know what the use cases are for
+the modularity.
+
+Michael: On board with being able to install data from npm, but not sure what
+the
+
+Steven: Two different types of usage: desktop of server. ICU point of view is
+to support user's language on the desktop and whatever comes on the wire in
+the server model.
+
+James, Steven: Working group about i18n will likely be created in the Node.js
+foundation, more discussions about that in upcoming convergence meetings.
+
+
+
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-05-07.md b/locale/uk/foundation/tsc/minutes/2015-05-07.md
new file mode 100755
index 0000000000000..e706df47a6a6c
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-05-07.md
@@ -0,0 +1,216 @@
+---
+title: Minutes for the Node.js core team meeting of 05/07/2015
+date: 2015-05-07
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* Colin Ihrig
+* James Snell
+* Julien Gilli
+* Michael Dawson
+* Robert Kowalski
+
+
+## Discussions
+
+### Upcoming releases: v0.12.3 and v0.10.39
+
+Julien: We should release 0.10.39 and 0.12.3 next week. A few important issues
+affecting many users.
+
+#### npm upgrade to 2.8.4
+Julien:
+Current npm version (2.7.4) is broken for a lot of users. npm 2.8.4 fixes a
+lot of issues.
+The reason why we didn't catch it, the current makefile doesn't trigger an
+error if you don't have CouchDB installed. It just gives a warning, that's
+easy to miss.
+
+
+Going to open a PR to make sure we catch these issues.
+
+Michael:
+Made some progress on Jenkins job that runs npm tests. Currently passes
+only on OSX. I'll keep working on it.
+
+Julien:
+CouchDB is the server for the npm registry. There are some tests that perform
+requests to CouchDB. If not installed, the tests don't run.
+CouchDB needs to be installed on each of the Jenkins machines.
+
+#### Latest libuv release (1.5.0)
+
+Julien:
+Will review changes to see if there are any important fixes, or changes to
+the API/ABI, to determine if we want this in the next release.
+
+
+#### Other PRs for the upcoming release
+
+Julien: Identified 5 different PRs that we could land before the release.
+Most of them already reviewed, we can land them pretty soon.
+https://github.com/joyent/node/pull/8875
+https://github.com/joyent/node/pull/9448
+https://github.com/joyent/node/issues/25137
+https://github.com/joyent/node/pull/25100
+https://github.com/joyent/node/pull/14193
+
+Another issue was with inconsistency of styles of invocations of makeCallback.
+Trevor working on it. Might not make it for the next 0.12 release.
+
+#### RC4 deprecation
+James, Julien:
+Need to address the problem if cyphers is undefined or null.
+Need to do a last pass on the pull request, to review tests/documentation.
+If we can nail this by end of week, we could make the next release next Tuesday.
+If we can't land the RC4 fixes, maybe we should revert the existing fixes for
+now. And do the release. And make the RC4 fixes in the next release.
+
+James: we should be able to finish the work this week.
+If delayed just a day, we'll wait.
+
+
+#### More release discussions
+Alexis: motivation for urgency?
+
+Julien: 
+- v8 lateral upgrade. A lot of impact on users. 
+  https://github.com/joyent/node/pull/18206 
+- Fixes on freeBSD
+  https://github.com/joyent/node/pull/14819
+  https://github.com/joyent/node/issues/8540
+
+Colin: can we land this too? https://github.com/joyent/node/pull/9159
+
+Michael: Christian is away for a couple weeks. I will need to take over one of
+the PRs on the list.
+
+Julien: try to sprint until Friday. We only want to land stuff that meets the
+usual quality bar.
+
+James: once RC4 issues are fixed in 0.12, we should be able to land them in
+0.10.39.
+
+Julien: start in 0.10.39, then port to 0.12.
+
+Julien: Alexis, your PR should be added to to the 0.10.39 milestone.
+https://github.com/joyent/node/pull/25100
+
+Julien:
+For 10.39, there's also a fix for timers:
+https://github.com/joyent/node/pull/17203
+First fix was already reviewed. Then I submitted a simpler fix. Looking for a
+second review.
+It shouldn't hold up the release, but it should be pretty safe and it fixes
+some annoying issues.
+
+### Flaky tests support
+Alexis: io.js removed support for flaky tests. https://github.com/nodejs/node/pull/812
+It looks like this issue might be slightly controversial.
+I am guessing they thought it was a mechanism for ignoring test failures in
+general, while it is only meant to support the automatic merge in
+node-accept-pull-request.
+
+Julien:
+In io.js they run CI to test every pull request, but they do the merge manually.
+io.js folks mentioned not been able to change the commit message as a downside
+of node-accept-pull-request.
+
+Let's communicate why it's useful.
+We should definitely log issues for flaky tests.
+
+Colin: how about policy for removing the test out of flaky -say- after a week?
+Somebody has to fix it. Or it should be deleted from the tests.
+
+Alexis, Julien: The moment we mark a test as flaky, we should open an issue
+and treat it as high priority.
+
+### Node.js API working group
+Alexis: there was a request for participation in this working group. Do you
+know more about the charter of this working group?
+
+Julien:
+Dan Shaw has been trying to get together a group people for a standard on what
+an official Node.js API is.
+Maybe to enable people to implement another runtime that is compatible with
+Node.
+
+Is the working group about the external or the internal API?
+
+James to seek more clarifications on the email thread.
+
+### Convergence process
+
+Alexis: in anticipation of the convergence work, where should we make changes?
+Node, io, and/or convergence repo?
+
+James: when we do our next major release, is it going to be based on
+the convergence repo? If so, that's where we should be landing the new
+features.
+
+Michael: But it won't be in stable working conditions for a while.
+So until we get the CI, we still do it in Node.
+
+If we make a change in joyent/node master, we can also port it to the
+convergence repo.
+
+Colin: what if we started cherry picking stuff to io.js?
+
+James: that works too.
+
+Julien: still a lot users of 0.12
+
+James: are we going to cut new releases from joyent\node master? 
+
+Julien: not a lot of work in master at this time.
+
+Julien: Still waiting for io.js to vote on whether they want to merge.
+
+James: possible alternate routes. If they choose not to come into the
+foundation, we can still fork io.js and use it as our own converged stream.
+We still need to give it some thought.
+
+Michael: agree with Julien on deferring until io.js decision takes place.
+
+### Triaging issues:
+Julien: how to do a better job at triaging issues coming in on github.
+948 issues open. A lot more coming in.
+Hard to triage them all, let alone fix them.
+Could we spend a little time every day to review the issues?
+
+Michael: schedule a slot to do everything together.
+
+Robert: using this process in CouchDB with very good results.
+
+Robert: we are using Jira.
+
+Alexis: increase the bandwidth by doing it in smaller groups or
+individually?
+
+Julien: good team exercise to do it together.
+
+Robert: let's just try it for a few weeks and see how it goes.
+
+Julien: schedule something just to try it out, see if it works.
+
+Everybody: ok :)
+
+Alexis: we'll need to find a way to use github effectively.
+
+Michael: I assume we can invite other people too.
+
+Julien: it's also a good way to onboard additional contributors.
+
+Schedule first meeting with existing collaborators. And if it works, we can
+extend it to more collaborators.
+
+Julien: any volunteers to lead this? If not I'll do it.
+
+Julien: maybe we can use Slack?
+
+Alexis: I vote for slack.
+
+Colin: +1 for Slack.
diff --git a/locale/uk/foundation/tsc/minutes/2015-05-21.md b/locale/uk/foundation/tsc/minutes/2015-05-21.md
new file mode 100755
index 0000000000000..53d6e83352885
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-05-21.md
@@ -0,0 +1,70 @@
+---
+title: Node 0.10.X/0.12.X LTS team meeting 05/21/2015
+date: 2015-05-21
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Alexis Campailla
+* James Snell
+* Julien Gilli
+* Michael Dawson
+
+### Upcoming releases
+
+#### v0.12.4
+Looking to do a 0.12.4 release soon, end of this week or early next week to address:
+
+* breaking v8 change https://github.com/joyent/node/issues/25324 - have PR ready
+* Windows XP issues, have pull request from io.js, ready to pull over
+
+James also has RC4/Bar Mitzvah fix ready to go back in as well
+
+If time permits Alexis will do more investigation to identify what caused the XP issue
+
+### npm testing
+
+Michael: update to npm 2.8.4 broke our test-npm target.  PR to fix is here: 
+https://github.com/joyent/node/issues/25290.  Previously you could run tests without
+install but now install is required or tests don't run. 
+
+Julien: we shoul talk with npm team on how to make sure the best way to run the tests
+
+Action: Michael to follow up with Forrest Norvell to discuss
+
+### LTS
+
+
+James: Some concern over moving directly to next LTS based on converged repo, we may need
+to allow for a 0.14.X
+
+After discussion we agreed that we need to provide more information so that people have
+a better idea of what will be changing and the impact.  More specifically:
+
+* gather list of breaking changes that will be in converged repo so that we can document
+and better communicate what will be different
+
+* reach out broadly to users to gather input on what their specific concerns might be
+in terms of an LTS release, including timing, content etc.
+
+Overall we want to figure out what the right answer is and be open to that alternative.
+
+Action: James will push on these 2 aspects. 
+
+### Deprecation
+
+There was some discussion about how a platform would be deprecated.  One suggestion was that for 
+platforms that no longer have vendor support (ex Windows XP) we would deprecate.  It might also
+be appropriate for non-core platforms if there is nobody actively maintaining them.   It is a relatively
+complex issue so Alexis will open an issue on github (in the LTS repo) to discuss.
+
+### Logjam
+
+https://weakdh.org/
+
+James/Julien had run tools provided in report against Node 0.10.X and 0.12.X and they don't report an
+issue so its only the second part which applies.  This is related to allowing short key lengths. 
+There are already some patches in io.js that may be pulled across although we likely would want a 
+fallback option that they may not contain.  Based on the report we want to move this forward but
+its not urgent. 
diff --git a/locale/uk/foundation/tsc/minutes/2015-06-04.md b/locale/uk/foundation/tsc/minutes/2015-06-04.md
new file mode 100755
index 0000000000000..e90042dda7b23
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-06-04.md
@@ -0,0 +1,64 @@
+---
+title: Minutes for the joyent/node TSC meeting of 06/04/2015
+date: 2015-06-04
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Colin Ihrig
+* James Snell
+* Julien Gilli
+* Michael Dawson
+
+## Discussions
+
+### Weekly calls
+
+Julien: Do we want to keep doing weekly calls with the current contributors to
+joyent/node, or should all discussions be moved to the combined Node.js TSC
+meeting?
+
+James: Still has value in the short term. Maybe have them not every week but
+when needed?
+
+Michael: Maybe part of the LTS working group?
+
+Colin: Need to make sure we bring joyent/node issues to the combined TSC call,
+during the last two calls we had no discussions around joyent/node.
+
+Julien: For instance adding collaborators from io.js to joyent/node is a topic
+that I'd like to discuss in the combined call.
+
+Michael: Actually another topic could be this very discussion that we have now
+about transitioning this weekly call into the LTS working group call.
+
+Action item: propose during next combined TSC call that this weekly call be
+transitioned to the LTS working group call.
+
+### Upgrade to libuv 1.6.0
+
+Julien: the issue with OSX and tty is not severe to me. It's been present
+since v0.11.12, happens on OSX only and is specific to TTY handling.
+
+Michael: It seems that there's no need to rush the next v0.12.x release for
+this particular issue, we should aim at including the fix in the next one when
+it's ready.
+
+James, Colin, Julien: agreed.
+
+### Security report from HP
+
+Julien: HP recently sent a security report mentioning potential security
+issues, but all of them seem to be false positives. Currently finishing
+investigations to be sure of that and communicating with them.
+
+### RC4 deprecation fixes
+
+Julien: Did another round of review and we're making progress. James will be
+on vacation for the next 2 weeks so I'll do my best to take it from there.
+We'll revert what's landed in v0.10 so far to prevent this from holding back
+other changes, and submit a new single PR that contains all changes so that
+there's only one place to comment.
+
+Michael: If you need help with this just let us know.
diff --git a/locale/uk/foundation/tsc/minutes/2015-06-11.md b/locale/uk/foundation/tsc/minutes/2015-06-11.md
new file mode 100755
index 0000000000000..86c09d2b47447
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-06-11.md
@@ -0,0 +1,65 @@
+---
+title: Node 0.10.X/0.12.X LTS team meeting 06/11/2015
+date: 2015-06-11
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+*  Julien Gilli
+*  Alexis Campailla
+*  Michael Dawson
+*  Colin Ihrig
+
+## Agenda
+
+*  Logjam/openssl upgrade
+*  Upgrade of libuv to 1.6.1
+*  First draft of breaking changes between io.js/Node 0.12
+*  Windows Installer Changes
+
+
+## Minutes
+
+###  Logjam/openssl upgrade
+
+Michael: Expect OpenSSL upgrade imminently. Just drop support for smaller size. Do we expect that to break users?
+
+Michael: should also consider including:
+
+*  https://github.com/nodejs/node/pull/1739
+*  https://github.com/nodejs/node/pull/1831
+*  https://github.com/joyent/node/issues/25366  (checked and docs for io.js indicate modp1 is still there)
+
+Michael: Stewart on my team has volunteered to create a PR against Node.js to upgrade OpenSSL.
+
+### Libuv upgrade to 1.6.1
+
+Julien: Libuv PR, fixes annoying issue on OSX 10. Worth reviewing soon.
+
+Colin: PR already landed in io.js
+
+Julien: top priority to review that ABI/API hasn.t changed in a breaking way.
+
+Julien: Julien to try and review today, likely to be included in release for openssl upgrade
+
+### Breaking changes between io.js and Node 0.12.X
+
+First draft of doc of breaking changes between 0.12 and next LTS.
+
+Julien: https://github.com/nodejs/node/wiki/Breaking-changes-between-v0.12-and-next-LTS-release
+
+Based on io.js issue tracker, joyent\node backport commit log. v8 breaking changes from release notes (?)
+
+Please review and comment on issue.
+
+### Debug port issues
+
+Colin working to fix https://github.com/nodejs/node/pull/1949 - new debug port for each worker.
+
+### Windows installer changes
+
+Alexis: https://github.com/joyent/node/issues/5849 - currently a hybrid/broken, will submit PR to do full install for all users, to be added to next milestone
+
+https://github.com/joyent/node/issues/25087, same upgrade code used for 32/64 bit which is not good practice.  Can result in binaries from one (32/64) being put into the other.  Will move to use 2 upgrade codes, but this will break upgrade. Going to add manual action to check for old code and give message saying you cannot upgrade and that you should un-install and install again
+
diff --git a/locale/uk/foundation/tsc/minutes/2015-06-18.md b/locale/uk/foundation/tsc/minutes/2015-06-18.md
new file mode 100755
index 0000000000000..926ce05a38d11
--- /dev/null
+++ b/locale/uk/foundation/tsc/minutes/2015-06-18.md
@@ -0,0 +1,124 @@
+---
+title: Node.js LTS team meeting of 06/18/2015
+date: 2015-06-18
+layout: foundation-tsc-minutes-post.hbs
+---
+
+## Participants
+
+* Joao Reis
+* Julien Gilli
+* Michael Dawson
+* Steven Loomis
+
+## Discussions
+
+### Upcoming releases
+
+#### node v0.10.39
+
+Julien: What's left to do: I suggest to revert
+https://github.com/joyent/node/pull/25511.
+
+Michael: We have another security release with logjam fixes scheduled for
+v0.12, so that's ok with me to move that until next couple of v0.10/v0.12
+releases.
+
+Julien: I might have time to start the release process for v0.10.29 today.
+Once v0.10 is released, I can move on to releasing v0.12.5.
+
+#### node v0.12.5
+
+Julien: We have [a PR to upgrade npm to
+2.11.2](https://github.com/joyent/node/pull/25517). It seems to be a small
+change from the current version, so I would advocate for landing that now.
+
+Michael: Playing devil's advocate: would it delay the OpenSSL upgrade? If so,
+then we could postpone it to 0.12.6. If the risk is low, and it's fairly quick
+to land it, I'm ok with that.
+
+Julien: Breaking changes for v0.12: the OpenSSL upgrade prevents TLS clients
+to connect to servers that use DH params with keys that are too short to be
+safe.
+
+Michael: Yes, and deferring the change to prevent servers to use shorter keys
+until next release.
+
+### Moving this weekly call to the LTS WG call
+
+Julien: We have [a new
+doodle](https://github.com/nodejs/LTS/issues/6#issuecomment-112976451) to try
+to come up with the best time slot to have these meetings, please fill it out
+if you haven't yet.
+
+### Having more than one person managing releases
+
+Julien: having only one person who manage releases is not sustainable, I would
+like to have a team of release managers for v0.10.x and v0.12.x releases, and
+future LTS releases.
+
+Julien: I've made some good progress on documenting the release process and
+improving some of the build scripts and Jenkins jobs to make them usable by
+other people than me. Hopefully that will be ready not too long from now.
+
+Julien: In the meantime, I'd like to raise that to the broader LTS group and
+see who would be interested in being a release manager.
+
+Steven: I have some experience with releases in the ICU project and other open
+source projects, so I can definitely help, even to review and give feedback on
+the release process.
+
+Julien: I'll create an issue in nodejs/LTS to gather initial feedback and see
+who could be interested.
+
+### Deprecation of shorter keys in DH param server side
+
+Michael: The OpenSSL upgrade to 1.0.1o prevents clients from connecting to
+servers using DH parameters that have a key that is too small to be safe. We
+should deprecate passing DH params that are unsafe when creating TLS servers
+too. I suggested [some changes to do that on
+GitHub](https://github.com/joyent/node/issues/25509#issuecomment-112596586),
+could you please provide feedback on these changes?
+
+### Transition from v0.12 to next converged LTS release
+
+Michael: Julien started documenting breaking changes between v0.12.x and
+what's currently in the converged repository. Julien, is there any way we can help?
+
+Julien: Documenting the changes is really the first step. What I need from you
+and other members of the LTS working group is to review this list and give
+feedback. Once we're confident that we have an accurate list of breaking
+changes, the next step is to reach out to various user communities and
+determine what we need to do to make the transition as smooth as possible.
+
+Michael: It seems that there were some productive discussions during Nodeconf
+about requirements from users regarding LTS releases.
+
+Julien: Yes, and there are other additional ways we can reach out to the
+broader community: leveraging the Node.js Advisory Board, reaching out to
+Joyent's Node.js Incubator participants, the broader community on GitHub, etc.
+We will need some coordination between a lot of entities within the Node.js
+project.
+
+Michael: I would suggest reaching out to nan maintainers to identify V8
+breaking changes that would be handled by nan.
+
+Julien: Sounds like a good idea!
+
+Michael: Maybe instead of commenting in an existing issue, Julien could create
+new issue on GitHub to get more attention with all details that he
+mentioned.
+
+Julien: agreed.
+
+Julien: One other thing that I'd like to use to make the transition even
+smoother is release candidates. I had started some work around that a while
+ago and unfortunately I haven't had the time to continue working on it. I
+think that Rod Vagg did some work around that for io.js and it might be ready
+there. Anyway, having release candidates for the next cycle of LTS releases
+would probably make things easier.
+
+Michael: Definitely, this is a broader topic for the LTS working group that we
+should probably even consider separately.
+
+
diff --git a/locale/uk/get-involved/code-and-learn.md b/locale/uk/get-involved/code-and-learn.md
new file mode 100755
index 0000000000000..b4ac4505c471e
--- /dev/null
+++ b/locale/uk/get-involved/code-and-learn.md
@@ -0,0 +1,12 @@
+---
+title: Code + Learn
+layout: contribute.hbs
+---
+
+# Code + Learn
+
+Code + Learn це всесвітня ініціатива воркшопів, що мають за мету познайомити нових розробників з тим, як працювати з Node.js. Консультуючі практичні сесії під наставництвом поточних співавторів та вирішення реальних проблем.
+
+Запущені у вересні 2015–го, воркшопи відбуваються у Дубліні та Лондоні (під керівництвом [LNUG](http://lnug.org/)).
+
+- [Code + Learn event listings](https://ti.to/code-and-learn)
diff --git a/locale/uk/get-involved/contribute.md b/locale/uk/get-involved/contribute.md
new file mode 100755
index 0000000000000..45c9d94235ba5
--- /dev/null
+++ b/locale/uk/get-involved/contribute.md
@@ -0,0 +1,33 @@
+---
+title: Співпраця
+layout: contribute.hbs
+---
+
+# Співпраця
+
+Дякуємо, що ви зацікавлені у співпраці з Node.js. Існує багато способів та місць де ви можете співпрацювати і ми тут, щоб допомогти вам з цим.
+
+## Повідомлення про проблему
+
+Якщо ви знайшли щось, що на вашу думку може бути помилкою у Node.js, будь–ласка не соромтесь відкрити іш’ю на сторінці проекту на GitHub. При заповненні вашого іш’ю, будь–ласка, впевніться, що ви можете підкріпити ваше іш’ю відповідними тестами, і цей тест не містить жодних додаткових залежностей. Тобто цей тест можна виконати лише з самим Node.js.
+
+При повідомленні про помилку ми також потребуємо якомога більше інформації про ваше середовище. Ми ніколи не знаємо яка інформація може стати корисною при вирішенні певної проблеми. Ваше іш’ю має містити принаймні таку інформацію:
+
+* версія Node;
+* платформа, на якій ви працюєте (macOS, SunOS, Linux, Windows);
+* архітектура, на якій ви працюєте (32bit або 64bit та x86 або ARM).
+
+На разі, проект Node.js розподіляється між кількома різними GitHub–репозиторіями, кожен зі своєю власною базою іш’ю. Якщо можливо, просимо надсилати іш’ю безпосередньо у потрібний репозиторій, проте не хвилюйтесь якщо ви надішлете його у неправильне місце, спільнота учасників радо спрямує вас у правильному напрямку.
+
+* Щоб повідомити про проблему, що стосується Node.js, будь ласка, скористайтесь [nodejs/node](https://github.com/nodejs/node)
+* Щоб повідомити про проблему, що стосується цього сайту, будь ласка, скористайтесь [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Участь у розробці
+
+Якщо ви хочете виправити помилку, або додати у Node.js новий функціонал, будь ласка, переконайтесь, що ви знайомі з [політикою розробки Node.js (Node.js Development Policy)](/en/get-involved/development/).
+
+Кожна зміна, перед тим як стати частиною проекту, має бути переглянута учасниками, відповідно до керування встановленого у [політиці розробки Node.js (Node.js Development Policy)](/en/get-involved/development/).
+
+## Стати співавтором
+
+Ставши співавтором, учасник має більший вплив на проект. Він може допомагати іншим учасникам з переглядом їхніх змін, сортуванням іш’ю та впливати на майбутнє проекту більшою мірою. Проект Node.js завжди шукає людей, що зацікавлені в тому, щоб стати співавторами. Якщо ви зацікавлені, переконайтесь, що ви знайомі з  [політикою розробки Node.js (Node.js Development Policy)](/en/get-involved/development/).
diff --git a/locale/uk/get-involved/development.md b/locale/uk/get-involved/development.md
new file mode 100755
index 0000000000000..147e7aca2be39
--- /dev/null
+++ b/locale/uk/get-involved/development.md
@@ -0,0 +1,354 @@
+---
+title: Розробка
+layout: contribute.hbs
+---
+
+# Розробка
+
+## Table of Contents
+
+- [Guiding Principles](#guiding-principles)
+- [Contributing](#contributing)
+  - [Collaborators](#collaborators)
+  - [Accepting Modifications](#accepting-modifications-through-a-consensus-seeking-process)
+  - [Release-related Commits](#release-related-commits-and-error-corrections)
+  - [Landing Pull Requests](#landing-pull-requests)
+  - [Issue Tagging](#issue-and-pull-request-tagging)
+- [Release Process and Branching Model](#release-process-and-branching-model)
+  - [Release Versioning](#release-versioning)
+  - [Release Process for Master](#release-process-for-master)
+- [Long Term Support Working Group](#long-term-support-working-group-roadmap)
+- [Issues Workflow](#issues-workflow)
+- [Stability Policy](#stability-policy)
+  - [Implicit vs. Explicit API Stability](#implicit-vs-explicit-api-stability)
+  - [Platform Stability](#platform-stability)
+  - [Dependency Stability](#dependency-stability)
+- [Working Groups](#working-groups)
+- [Developer's Certificate of Origin 1.1](#developers-certificate-of-origin)
+- [A Few Open Questions](#a-few-open-questions)
+- [Notes](#notes)
+
+---
+
+## Guiding Principles
+
+The Fundamental goal of the Node.js Project is to provide a JavaScript-based application development platform that is *current*, *reliable* and *stable*.
+
+Contributors to Node.js work in concert with one another *on behalf of* the Community of users who build their applications and businesses on top of the Node.js platform. Accordingly, contributors must demonstrate an ongoing commitment, not only to the Project, but to the stability and vitality of the Community as a whole.
+
+It is vital that users trust the Contributors to have their best interests in mind while making decisions affecting the overall direction of the platform. This means having defined guidelines, stable APIs, a clear roadmap, and a predictable release schedule. The user community and developer ecosystem must be included in the decision making process.
+
+Adoption of new capabilities and features within Node.js must be carefully balanced by the expressed needs of the users and the community. Change just for the sake of change must be avoided and a guaranteed long term support policy must be established.
+
+Node.js owes much of its success to the existing ecosystem of module and add-on developers. The Node.js project should do everything it can to support the continued growth and stability of that ecosystem. This includes, but is not limited to, keeping Node.js focused on providing a minimal kernel of core functionality while deferring, as much as possible, additional capabilities and features to add-on modules or applications.
+
+In order to best serve the Node.js Community as a whole, the development, release and issue management processes adopted by the Node.js Foundation TSC must reflect these guiding principles.
+
+
+## Contributing
+
+### Collaborators
+
+The Node.js project is maintained by individual Collaborators. The Technical Steering Committee (TSC) membership consists of key Collaborators who have demonstrated both technical expertise critical to the ongoing maintenance and evolution of the project and a long term commitment to driving the project and community forward.
+
+Individuals can be nominated as Collaborators by TSC members. Once the nomination is approved by the TSC, the invitation to become a Collaborator is extended to the individual. The invitation must include a copy of the project Developer’s Certificate of Origin (DCO, see below). Assuming the individual accepts the invitation, they are granted commit-access to the project.
+
+Nominations for Collaborator Status happen through the typical TSC decision making process. That is, to nominate one or more Collaborators, an issue containing the names of all collaborators being nominated is created and put on the TSC meeting agenda. The issue is approved or rejected following the same Consensus Seeking Process used for any other issue or PR.
+
+Individuals can self-petition the TSC for Collaborator status by submitting an issue requesting to be put on the TSC meeting agenda. In order to be considered however, such self-nominations must be sponsored by an existing TSC member, after which it follows the same process as above. To sponsor a nomination, the TSC member must indicate consent within the issue text or associated comment thread.
+
+Collaborators can be nominated to become members of the TSC following the same nomination and approval model. However, Collaborators cannot nominate themselves for TSC membership. An individual cannot be nominated and accepted into the TSC without first having been nominated and accepted as a Collaborator.
+
+### Accepting Modifications through a Consensus Seeking Process
+
+A "Contribution" to the Project is any work that is voluntarily submitted to the project. These include not only source code in the form of bug fixes, code improvements, new functions, etc, but contributions to documentation, design etc that are intended for the overall improvement of the project.
+
+Contributions to the Project are made on a collaborative basis. Any individual with a GitHub account may propose a Contribution by submitting a Pull Request (PR). Like the TSC governance, acceptance of Contributions (a.k.a. "landing a Pull Request") into the Project follows the Consensus Seeking decision making model as described in the Project TSC Charter.
+
+All Pull Requests submitted by individuals who are not Collaborators must be signed-off on by an existing Collaborator before the PR can be landed. The sponsoring Collaborator becomes responsible for the PR. Pull Requests from an existing Collaborator must be signed-off on by at least one other Collaborator.
+
+Before any Pull Request is landed, sufficient time should be given to receive input from other Collaborators with sufficient expertise to evaluate the changes. Specifically, at least 48 hours during the typical working week and 72 hours over weekends should be given to account for international time differences and work schedules. Trivial Pull Requests may be landed after a shorter delay.
+
+If it becomes apparent that the changes proposed by a given Pull Request: (a) have significant impact on the project as a whole; (b) are inherently controversial; or (c) have failed to reach consensus amongst Collaborators, the Pull Request can be elevated for review by either a specific Working Group (by attaching a WG specific tag to the PR) or the TSC (by attaching the *tsc-agenda* tag to the PR). Pull Requests that have been flagged for TSC or Working Group review must not be landed until the TSC or Working Group has had sufficient opportunity to review the issue and render a decision. A Working Group may choose to defer the issue to the TSC.
+
+Pull Requests that require an increase in the Major version must be elevated for review by the TSC. This does not necessarily mean that the PR must be put onto the TSC meeting agenda. If enough TSC members sign-off on the PR and there is clear consensus among TSC members for the change, the Pull Request can be landed. Where there is disagreement among TSC members, *semver-major* Pull Requests should be put on the TSC meeting agenda.
+
+Specific Collaborators or Working Groups can be requested to review any PR by using an *@-mention* either within the PR text itself or the associated comment stream.
+
+Collaborators sign-off on a Pull Request by explicitly stating their approval in the PR text or associated comment stream. If a Collaborator is unsure about the modification or is not prepared to take full responsibility for the change, they should defer to another Collaborator.
+
+Exception to this process is allowed for high-priority changes that address security vulnerabilities. A shorter review period and modified sign-off process may be necessary depending on the nature of the change and severity of the issue. It is recommended that the TSC establish a Security Working Group of Collaborators with recognized security expertise that can be tasked with reviewing security related Pull Requests and determining an appropriate review process.
+
+All Pull Requests that either fix bugs or introduce new functionality require at least one test case demonstrating the defect or validating the intended functionality. For bug fixes, the test should fail before the change, and pass after the change. In exceptional cases, such as environments or failure modes that are difficult to reproduce, a detailed description of how to verify the fix may be accepted in lieu of a specific test.
+
+Pull Requests for changes intended to improve performance require a benchmark demonstrating the performance impact. The benchmark should demonstrate improved performance after the change is applied.
+
+### Release-related Commits and error corrections
+
+When cutting a new release, it is typically necessary to commit a few specific changes to the repository. These include tasks like updating the release notes and incrementing the current version number.
+
+It's also possible for errors to come up in the basic management of the project repository (caused either by simple human error or bugs in the tooling used to manage the project). Correction of such errors may require additional changes to be landed.
+
+Such changes can be landed after a significantly shorter review period if the changes are strictly targeted at repairing the current state of the repository or cutting a new release. Effort should still be made to solicit review of such changes in advance of landing them.
+
+### Landing Pull Requests
+
+When Landing a Pull Request, a Collaborator must modify the original commit message to include the following additional meta information regarding the change process:
+
+* A `Reviewed-By: Name <email>` line for yourself and any other Collaborators who have reviewed the change.
+* A `PR-URL:` line that references the full GitHub URL of the original Pull Request being merged so it's easy to trace a commit back to the conversation that lead up to that change.
+* A `Fixes: X` line as appropriate, where `X` includes the full GitHub URL for an issue, and/or the complete or abbreviated hash identifier and commit message if the commit fixes a bug in a previous commit. Multiple `Fixes:` lines may be added if appropriate.
+
+Additionally, Collaborators should:
+
+* Double check Pull Requests to make sure the author's full name and email address are correct before merging.
+* Verify that every commit passes all tests.
+
+### Issue and Pull Request Tagging
+
+All Issues and Pull Requests should be tagged with their respective feature areas. This helps organize issues and makes it easier for Collaborators to keep track of the items most relevant to them.
+
+The labels *discuss*, *meta*, *future*, and *ideas* are used to label issues that are not bugs or features requests.
+
+The *help-wanted* tag is used to draw attention to Issues and Pull Requests that need contributions.
+
+When a Pull Request is not ready to merge, and is still being iterated on or reviewed, it should have the *in-progress* tag applied.
+
+The *semver-minor* and *semver-major* tags are used for Pull Requests that will cause a version iteration other than patch once released.
+
+The *tsc-agenda* tag is used to elevate items to the next TSC meeting. TSC meeting notes and announcements should have the *tsc-meeting* tag.
+
+Every Working Group must specify a tag that can be used to indicate items for review by the Working Group and a tag that can be used to identify Working Group meeting notes and announcements.
+
+## Release Process and Branching Model
+
+The Project source repository will be organized into a single `master` branch, multiple maintenance branches, and multiple development branches. All modifications intended for the current major release line must be made to the `master` branch and must follow the guidelines detailed in this document.
+
+At each new *semver-patch*, a Release tag is cut (e.g. `v2.0.0`, `v2.0.1`, `v2.1.0`, etc).
+
+```
+          (dev branches)         (dev branches)
+          ⇗  ⇗      ⇘  ⇘       ⇗  ⇗      ⇘  ⇘
+  -----------------------------------------------------------------> master
+      ⇣          ⇣          ⇣          ⇣         ⇣          ⇣
+  tag:v2.0.0 tag:v2.1.0 tag:v2.2.0 tag:v3.0.0 tag:v3.1.0 tag:v3.2.0  (releases)
+
+```
+
+Before a new *semver-major*, `master` is branched for maintenance of the prior major (e.g. `v1.x`, `v2.x`).
+
+```
+                                        v2.x ------> maintenance
+                                       ⇗
+  -------------------------------------------------> master
+       ⇣          ⇣          ⇣         ⇣
+   tag:v2.0.0 tag:v2.1.0 tag:v2.2.0 tag:v3.0.0
+
+```
+
+Modifications to maintenance branches are limited to bug fixes, with priority given to changes that address specific security vulnerabilities. Oversight of the maintenance branches belongs to the Long Term Support (LTS) Working Group. The LTS Working Group will establish policies for landing Pull Requests into maintenance branches.
+
+The LTS Working Group may choose to use its own tags to identify LTS Release Candidates and LTS Releases and can choose to create additional maintenance branches if need arises. The LTS Working Group may also choose to use extended version metadata for tracking changes that land within maintenance branches.
+
+Additionally there are branches for stable release lines prior to 1.0 of minor versions. Example: `v0.8.x`, `v0.10.x`, `v0.12.x`.
+
+
+### Release Versioning
+
+#### Patches
+
+Patch releases are defined as bug, performance, and security fixes. They do not change or add any public interfaces. They do not change the expected behavior of a given interface. They are meant to correct behavior when it doesn't match the documentation, without also introducing a change that makes seamless upgrades impossible.
+
+#### Minors
+
+Minors are the addition and refinements of APIs or subsystems. They do not change APIs or introduce backwards compatible breaking changes. These are mostly completely additive releases.
+
+#### Majors
+
+Majors contain changes in behavior that could potentially break code that worked in prior releases.
+
+### Release Process for Master
+
+Releases should not contain too many code changes and if the rate of code changes is high then it should correspond to an increase in the rate of releases. It is expected that there should be about one release per week.
+
+Master must pass a full CI test run prior to release.
+
+If master contains changes which are tagged *semver-minor* then the release should bump the minor version otherwise it is a patch release.
+
+## Long Term Support Working Group Roadmap
+
+The LTS WG is expected to establish a regular and predictable cadence of LTS Releases. To this end, the LTS WG must maintain and regularly publish a clear Roadmap that outlines the priorities and milestones for upcoming LTS Releases. The goal of the Roadmap is to help guide the project's evolution as opposed to constraining it.
+
+## Issues Workflow
+
+The tracking and management of issues is still an open discussion. See https://github.com/jasnell/dev-policy/issues/9 and https://github.com/jasnell/dev-policy/issues/8
+
+## Stability Policy
+
+The most important consideration in every code change is the impact it will have, positive or negative, on the ecosystem (modules and applications). To this end, all Collaborators must work collectively to ensure that changes do not needlessly break backwards compatibility, introduce performance or functional regressions, or negatively impact the usability of the Project on any of the platforms officially targeted for support by the Project. The TSC is responsible for determining the list of supported platforms.
+
+When discussing stability, it is important to first review Node.js' layered architecture:
+
+```
+   +---------------------------------------------------+
+   |          Module and Application Ecosystem         |
+   +---------------------------------------------------+
+        |                |            |              |
+        |                | +----------------------+  |
+        |                | |  Binary Abstraction  |  |
+        |                | |        Layer         |  |
+        |                | +----------------------+  |
+        |                |     |             |       |
+   +----------------+    |     |             |       /
+   |  Node.js Core  |    |     |             |      /
+   |  Library API   |    |     |             |     /
+   +----------------+    |     |             |    /
+   |     js impl    |    |     |             |   /
+   +----------------+    |     |             |  /
+            |            |     |             | /
+   +--------------------------------------+  |/
+   | Node.js Application Binary Interface |  |
+   +--------------------------------------|  |
+   |              C/C++ impl              |  |
+   +--------------------------------------+  |
+                      |                      |
+        +---------------------------------------+
+        | Dependencies: v8, libuv, openssl, etc |
+        +---------------------------------------+
+```
+
+Node.js currently builds on top of several key dependencies including the V8 JavaScript engine, libuv, openssl and others. The Node.js Application Binary Interface provides access to functionality central to how Node.js operates. The Node.js Core Library is the primary interface through which most Modules and Applications built on top of Node perform I/O operations, manipulate data, access the network, etc. Some modules and applications choose to go beyond the Core Library and bind directly to the Application Binary Interface and dependencies to perform more advanced operations. An optional Binary abstraction layer is used to buffer module and application developers from changes in the Application Binary Interface and Dependencies.
+
+Due to the existing layering, modules and applications are sensitive not only to changes in the Core Library API, but the Application Binary Interface and dependencies as well.
+
+Any API *addition* to either the Node.js Core Library API or Application Binary Interface must result in a *semver-minor* version increase.
+
+Any *backwards incompatible* change to either the Node.js Core Library API or Application Binary Interface must result in a *semver-major* version increase.
+
+Any Modification to the ABI, dependencies or Native abstractions that require a developer to *modify code* and then recompile is considered a backwards incompatible change that must result in a *semver-major* version increase.
+
+Reversions of any changes landed into `master` are to be handled just like any other type of pre- or post-release modification.
+
+### Implicit vs. Explicit API Stability
+
+The Node.js Core Library API, Application Binary Interface and Binary Abstraction layer each expose methods, events, behaviors and default values that together comprise the implicit Node.js "Public API". This "Public API" is used  by application and module developers and changes will have direct impact on the Community.
+
+Methods exposed by the API can have either strongly or weakly typed input parameters and return values. Methods may also throw any number of exceptions or trigger certain sequences of events or side effects. When such types, exceptions, events or side-effects are *documented*, they become part of the Node.js *Explicit API*.
+
+Likewise, when the ordering of events triggered by Node.js, the default values of optional input parameters and constants, or the type and structure of return values and event payloads are *documented*, they become part of the *Explicit API*.
+
+*Undocumented* types, return values, exceptions, events and side effects are considered to be part of the *Implicit API*.
+
+The ecosystem of application and module developers must be able to rely on the stability of both *Implicit* and *Explicit* APIs as much as possible. Changes to these APIs that are made prior to their inclusion within a Release are generally straightforward and can be made with appropriate review. Changes after the APIs have been included within a Release, however, require Collaborators to be much more careful.
+
+Backwards incompatible changes to *Explicit* APIs that have previously been included in a Release *must* follow a clear and predictable deprecation process in which the existing documented API: (a) is clearly marked for deprecation and (b) can change only after the next *semver-major* version increase.
+
+Backwards incompatible changes to *Implicit* APIs that have been included in a Release *should* be handled the same as *Explicit* API changes. However, exception to this rule can be allowed if the proposed change can be reliably demonstrated to have minimal impact *in practice* and either:
+
+  (a) the proposed change reconciles *documented* behavior with *implemented* behavior (i.e. the documentation needs to be updated to accurately reflect how the code actually works);
+
+  (b) it is clear that the Implicit API being modified was originally intended for internal use as part of the underlying implementation (as opposed to being targeted at developers); or
+
+  (c) it can be demonstrated that the Implicit API never worked correctly to begin with.
+
+That said, changes to any of the APIs should not be made lightly as there is currently no reliable means of determining in advance the impact any change may have on existing applications and modules. Collaborators must use their best judgement to determine whether any given change is "technically backwards incompatible but in practice should not be", then approach landing the change accordingly.
+
+There should never be any API change in a maintenance branch unless the change is required to address a critical security vulnerability.  
+
+### Platform Stability
+
+The Platforms supported by the Node.js project are generally divided into three distinct categories: *Supported*, *Experimental* and *Deprecated*.
+
+*Supported* platforms consist of those with support in the `master` branch. For every release, the build must complete successfully and pass a full CI test run on every *Supported* platform.
+
+*Experimental* Platforms consist of those for which there is active ongoing development to port Node.js to the platform but functionality may not yet be feature complete or fully operational. Support for experimental platforms may not yet have been committed to `master` and might be done in a Development branch or separate repository entirely.
+
+*Supported* and *Experimental* Platforms remain active so long as there are Collaborators actively maintaining support for them.
+
+*Deprecated* Platforms consist of platforms for which: (a) there is no active development, (b) there are no Collaborators actively maintaining support, or (c) it is no longer feasible or practical to continue supporting.
+
+It is possible for build and CI infrastructure updates to cause failures in existing *Supported* platforms. This can happen, for instance, when an updated dependency forces the build to use an updated toolchain that is not yet (or no longer) supported on a given platform. In such cases, Collaborators should be notified  in advance that such changes are expected so that appropriate fixes on affected platforms can be planned and landed. Effort should be made to ensure that the build and CI infrastructure continues to work on all currently *Supported* platforms. Prior to the next release, however, if it becomes clear that the build cannot be fixed on a particular platform, it can be moved to *Deprecated* status and landing the changes would require a *semver-major* version increase.
+
+Support for *Deprecated* Platforms may be removed entirely after the next *semver-major* version increase.
+
+Note that the option to deprecate an existing supported platform should not be taken lightly. Given that deprecation of the platform would require a *semver-major* version increase, such changes must be reviewed and approved by the TSC.
+
+### Dependency Stability
+
+#### JavaScript Support (V8)
+
+Node.js will adopt new V8 releases as quickly as practically feasible. For Releases, the version of V8 shipped must be fully functional with no regressions on all *Supported* platforms.
+
+When V8 ships a breaking change to their C++ API that can be handled by the binary abstraction layer there will be a *semver-minor* version increase.
+
+When V8 ships a breaking change to their C++ API that cannot be handled by the binary abstract layer there will be a *semver-major* version increase.
+
+When new features in the JavaScript language are introduced by V8, there will be a *semver-minor* version increase. TC39 has stated clearly that no backwards incompatible changes will be made to the language so it is appropriate to increase the *minor* rather than the *major*.
+
+With a few notable exceptions, the Node.js Core Library API is largely built around ES5 Language features. While there are currently no plans to do so, it is possible for post-ES5 JavaScript language features to be introduced into the Core Library API in the future. If such changes can be introduced in a manner that is transparent to module and application developers and will not cause existing applications to break, the changes can be landed after sufficient review with either a *semver-patch* or *semver-minor* version increase (depending on whether the change introduces new APIs). However, if the changes cause a backwards incompatible change to the existing API or could cause existing modules and applications to break the change must be reviewed and approved by the TSC and must result in a *semver-major* version increase.
+
+#### Other dependencies
+
+Other dependencies such as OpenSSL, libuv and http-parser are handled similarly.
+
+Node.js will continue to adopt new dependency releases as often as practically feasible.
+
+When a dependency ships a breaking change to their API, if that change can be abstracted by the Node.js Application Binary Interface such that module and application developers can be isolated from the change without breaking existing applications, there will be a *semver-minor* version increase.
+
+When a dependency ships a breaking change to their API that cannot be abstracted by the Node.js Application Binary Interface, there will be a *semver-major* version increase.
+
+When dependencies introduce additional functionality that does not break backwards compatibility in any way, there will be a *semver-minor* version increase.
+
+#### npm
+
+While the `npm` utility is shipped as part of Node.js, it is not a functional dependency in the same way as V8, OpenSSL or libuv. Specifically, `npm` is not considered part of the Node.js API. As a general rule, *semver-patch* and *semver-minor* updates in `npm` may be introduced into Node.js with only a *semver-patch* version increase. If there is a *semver-major* update in `npm`, such as when `npm` rolls over to version 3.0.0, then a *semver-major* version increase should occur in Node.js. However, the TSC may alter this policy in the future depending on the nature and scope of changes expected in newer versions of `npm`.
+
+## Working Groups
+
+Working Groups are autonomous groups of Collaborators chartered by the TSC to oversee specific aspects of the Project. Working groups can be formed at any time but must be ratified by the TSC.
+
+Every Working Group has a charter that details its area of responsibility. Once approved by the TSC, the Working Group becomes solely responsible for items detailed in that charter.
+
+When applicable, the charter should indicate the conditions under which the Working Group's activity can be considered to be complete and the WG can be dissolved. A Working Group can, at any time, request that the TSC dissolve the Working Group by opening an issue requesting dissolution with the *tsc-agenda* tag.
+
+The TSC may revoke the Working Groups charter at any time following the decision making process defined in the TSC Charter.
+
+Proposals to create a new Working Group should be made either by opening an issue or submitting a PR with the draft charter for the new Working Group, then putting that on the TSC agenda using the *tsc-agenda* tag.
+
+<a id="developers-certificate-of-origin"></a>
+## Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+* (a) The contribution was created in whole or in part by me and I
+  have the right to submit it under the open source license
+  indicated in the file; or
+
+* (b) The contribution is based upon previous work that, to the best
+  of my knowledge, is covered under an appropriate open source
+  license and I have the right under that license to submit that
+  work with modifications, whether created in whole or in part
+  by me, under the same open source license (unless I am
+  permitted to submit under a different license), as indicated
+  in the file; or
+
+* (c) The contribution was provided directly to me by some other
+  person who certified (a), (b) or (c) and I have not modified
+  it.
+
+* (d) I understand and agree that this project and the contribution
+  are public and that a record of the contribution (including all
+  personal information I submit with it, including my sign-off) is
+  maintained indefinitely and may be redistributed consistent with
+  this project or the open source license(s) involved.
+
+## A Few Open Questions
+
+1. What about things like http_parser and libuv? Does it make sense to see about bringing each into the foundation as their own projects?
+2. What about all the other repos under iojs/* and joyent/*, which of those will move over to the foundation?
+
+## Notes
+
+1. The existing Node.js Workflow requires that all PR's can only be landed using a specific Jenkin's "node-accept-pull-request" job. This document requires that all PR's must be tested to ensure that all tests pass but it does not go into specific detail on the CI process. It is expected that the TSC will establish the specific step-by-step process by which Pull Requests must be landed.
+
+2. The existing Node.js Workflow recently introduced the notion of "Priority" and "Status" tags for Issues. For instance, the *P-0* tag can be used to label issues that break node on at least one supported platform and need to be resolved as quickly as possible. The intent of the Priority tags is to assist in the triage of issues and help Collaborators determine which issues to work on first. The io.js project currently does not have a similar mechanism and feedback from io.js participants has been that such a Priority tagging system may not be of use (and could be actively harmful) given the way they've chosen to handle issues.
diff --git a/locale/uk/get-involved/events.md b/locale/uk/get-involved/events.md
new file mode 100755
index 0000000000000..53007816808dc
--- /dev/null
+++ b/locale/uk/get-involved/events.md
@@ -0,0 +1,12679 @@
+---
+title: Події
+layout: events.hbs
+regions:
+  - region: Африка
+    meetups:
+      - country: ZA
+        city: Cape Town
+        link: 'http://www.meetup.com/Code-Craftsmanship/'
+        name: Code Craftsmanship
+        description: 'Exploring the art of code craftsmanship. A collective that meets to discuss, challenge and explore opportunities in building progressive software. From front-end design and development through to NoSQL databases. Discussing tools, processes and learnings from realworld implementations. Design, UX, front-end, back-end and beyond all discussed.'
+        lon: 18.459999084472656
+        lat: -33.93000030517578
+      - country: ZA
+        city: Johannesburg
+        link: 'http://www.meetup.com/Jozi-Node-JS/'
+        name: Jozi.Node.JS
+        description: Come and find out about Node.js the awesome server side development environment. All welcome.
+        lon: 28.040000915527344
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/7/6/600_358623702.jpeg'
+        lat: -26.190000534057617
+      - country: ZA
+        city: Cape Town
+        link: 'http://www.meetup.com/nodecpt/'
+        name: NodeJS Cape Town
+        description: |-
+          <p>Thanks to the brilliant work of Ryan Dahl, we have node.js, a beautiful and elegant server-side framework built on top of Google's V8 Javascript engine. This opens up a whole new world of possibility for developing web apps, APIs, and lightweight HTTP servers.</p>
+          <p>We try to meet each month on the third week. Each month we'll have a group discussion on a particular aspect of NodeJS, using it to build apps and any tools or workflows based on it.</p>
+          <p>If you'd like to present, please send a note with your topic. If you have a suggestion for a topic, feel free to submit it.</p>
+          <p>We are always looking for spaces to use for the meetups. If you'd like to offer a space for us to use, please reach out to us.</p>
+        lon: 18.459999084472656
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/3/8/c/600_298438252.jpeg'
+        lat: -33.93000030517578
+      - country: ZA
+        city: Cape Town
+        link: 'http://www.meetup.com/Cape-Town-Nodebots/'
+        name: Cape Town Nodebots
+        description: "Calling all Cape Town (aspiring) hardware hackers! We use Javascript to move more than just DIVs. For those interested in hacking hardware using Javascript. If you want to built a robot, but don't know where to start, this is for you. Or maybe you are an old Arduino hand trying something new or want to teach others a few ticks. Alternatively you can just come to show off your latest bot..."
+        lon: 18.459999084472656
+        lat: -33.93000030517578
+      - country: KE
+        city: Nairobi
+        link: 'http://www.meetup.com/Nairobi-node-js-Meetup/'
+        name: Nairobi node.js Meetup
+        description: 'Node Js is fast growing, lets learn and share'
+        lon: 36.81999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/3/d/0/600_437469168.jpeg'
+        lat: -1.2899999618530273
+      - country: EG
+        city: Cairo
+        link: 'http://www.meetup.com/Meteor-Egypt/'
+        name: Meteor Egypt
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 31.25
+        lat: 30.059999465942383
+      - country: MA
+        city: Casablanca
+        link: 'http://www.meetup.com/Meteor-Casablanca/'
+        name: Meteor Casablanca
+        description: "<p>a community gathering Meteor enthusiasts and passionate developpers to share knowledge in an inspiring way.</p>\n<p>Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>\n<br>\n\nBuilding web application is hard and time consuming and often an intimidating process , it was the right time to invent a new way to aproach building application by hiding irrelevant complexity and focus more on the core of the product. we believe this new aproach is championned by Meteor , and this deserves \_regular celebration \_meetings during which people can share their passion , in a human friendly way .<br>\n\nand also build things that can grow to be exciting !!\n<p><br>\n\n</p>"
+        lon: -7.579999923706055
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/3/b/0/600_432774192.jpeg'
+        lat: 33.529998779296875
+      - country: KE
+        city: Nairobi
+        link: 'http://www.meetup.com/nairobi-js/'
+        name: Nairobi JavaScript Community
+        description: |-
+          <p><span><b>Community/user group focused on HTML5, CSS3, JavaScript inclusive of Node.js&nbsp;and related web development topics. We meet regularly on the 1st Saturday each month at 2 pm at <a href="http://community.ihub.co.ke">iHub tech space</a>.</b></span></p>
+          <p><b>Other channels</b></p>
+          <p>We have a Slack and thriving <b>WhatsApp</b> channel/groups:</p>
+          <p><span><b>Slack:</b>&nbsp;<a href="http://bit.ly/slack-nbi-js">http://bit.ly/slack-nbi-js</a> (self-invite)</span></p>
+          <p><span><b>WhatsApp:</b> get in touch with me (email and twitter handle at the bottom)</span></p>
+          <p> <br><b>Introduction</b></p>
+          <p><b>First of all</b>, head over to&nbsp;<a href="http://trippa.firebaseapp.com">Trippa</a>, a speed typing testing application, and check/test it out. When satisfied with what you see, head over to it's repo --&nbsp;<a href="http://github.com/kn9ts/trippa">http://github.com/kn9ts/trippa</a>, study the files and file structure while at it. Then check out the project (link at the top of the repo).</p>
+          <p><span>It was done in </span><b>3 days</b><span>. Is this possible? </span><b>Yes. How?</b><span>Using:</span></p>
+          <p><b>- JavaScript Framework</b></p>
+          <p><b>- LESS, a CSS preprocessor</b></p>
+          <p><b>- JADE, a HTML5/Node.js templating engine</b></p>
+          <p><b>- Bower &amp; NPM for efficient package management</b></p>
+          <p><b>- Firebase, a cloud push service, database and static server deployment</b></p>
+          <p><b>- Gulp.js, a task automation tool</b></p>
+          <p><b>- Git &amp; Github for version control and repo hosting respectively</b></p>
+          <p><b>- Jshint, a linting tool that automates syntax errors detection and reporting</b></p>
+          <p><b>- Static file handling</b></p>
+          <p>Now it's harder to believe it was done in 3 days. Since it just seems I've cooked up all the above.</p>
+          <p><span>If all the mentioned above were like <b>"何とか何とか何とか..."</b> to you, then you have all the reasons to join this community and be present in all meet-ups and understand how we are able to build complex applications MVPs in mere days or hours. And find out what the "fudge" all the above are.</span> <br></p>
+          <p>We look forward to hearing from you, and to seeing you at an upcoming event. Get in touch at <b>eugenemutai@gmail.com</b>&nbsp;or holla at me on <b>twitter: @kn9ts</b> <br></p>
+        lon: 36.81999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/9/e/a/600_441871210.jpeg'
+        lat: -1.2899999618530273
+      - country: ZA
+        city: Johannesburg
+        link: 'http://www.meetup.com/Johannesburg-ReactJS-Meetup/'
+        name: Johannesburg ReactJS Meetup
+        description: 'This group is for anyone looking to learn and use ReactJS in production. We will be covering the FLUX architecture, Functional Reactive Programming, and React Native. We also cover how to test React components properly. Finally we will learn Relay and the GraphQL once they have been released to the public.'
+        lon: 28.040000915527344
+        lat: -26.190000534057617
+      - country: MU
+        city: Port Louis
+        link: 'http://www.meetup.com/frontend-mauritius/'
+        name: Front-end Mauritius
+        description: "<p>Front-end Mauritius is a free evening meetup that's dedicated to all aspects of front-end development.</p>"
+        lon: 57.5099983215332
+        lat: -20.170000076293945
+      - country: ZA
+        city: Johannesburg
+        link: 'http://www.meetup.com/Johannesburg-Ember-JS-Drinkup/'
+        name: Johannesburg Ember JS Drinkup
+        description: "<p>A meetup group to meet ambitious Ember.js developers! Let's get together periodically to talk about code, eat, drink, and generally geek out. We welcome people ranging from EmberJs/JavaScript/HTML/CSS apprentices to card-holding category theorists. &nbsp;In other words: if front end development, anything from the Ember technology stack, or JavaScript excite you -- check us out!</p>"
+        lon: 28.040000915527344
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/c/f/d/600_439176093.jpeg'
+        lat: -26.190000534057617
+      - country: MA
+        city: Casablanca
+        link: 'http://www.meetup.com/Casablanca-js/'
+        name: Casablanca.js
+        description: '<p>&nbsp;Javascript has become prominent in the Technology ecosystem. so many great implementations of frameworks out there that unfold endless possibilities for futur systems and that also bring many challenges along the way, to step up in that ever growing worldwide competition and have what it takes to not only ensure survival but to achieve a top level of coding skills, full awareness of past/present and futur of Javascript and evolving in an inspiring local ecosystem,we are urged to build a solid community.<br><br>We think Casablanca /Morocco is challenged to produce highly skilled developers and that is only achievable through community involvement and knowledge sharing , this meetup has the ambition to be a rich platform committed to drive Javascript knowledge through organizing regular events during which we will talk about different themes related to Javascript ,Hack together ,share little stories,dream big and of course EAT :D .<br><br>stay tunned for the upcoming event :)</p>'
+        lon: -7.579999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/1/e/5/600_446344581.jpeg'
+        lat: 33.529998779296875
+      - country: MA
+        city: Rabat
+        link: 'http://www.meetup.com/ngMorocco/'
+        name: ngMorocco - Moroccan AngularJS community
+        description: '<p>The Moroccan AngularJS Developer Community The main goal of ngMorocco is to share AngularJS knowledge and best-practices, to gather people who are passionate about AngularJS and enable them to talk, socialize and learn from the best, with delicious food and a friendly atmosphere no matter your gender, age, physical appearance, body size, race, or religion.</p>'
+        lon: -6.829999923706055
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/8/8/5/600_447250373.jpeg'
+        lat: 34.02000045776367
+    nodeschools:
+      - name: NodeSchool Algiers
+        location: 'Algiers, DZ'
+        organizers:
+          - ismnoiet
+        website: 'http://nodeschool.io/algiers'
+        repo: 'http://github.com/nodeschool/algiers'
+        lat: 36.7537703
+        lon: 3.0587927
+      - name: NodeSchool Cairo
+        location: 'Cairo, EG'
+        organizers:
+          - ahmdrefat
+          - Azzurrio
+        website: 'http://nodeschool.io/cairo'
+        repo: 'http://github.com/nodeschool/cairo'
+        lat: 30.0444196
+        lon: 31.2357116
+      - name: NodeSchool Hermanus
+        location: 'Hermanus, ZA'
+        organizers:
+          - andrenventer
+          - elsjelemmer
+        website: 'http://nodeschool.io/hermanus'
+        twitter: '@nodehermanus'
+        repo: 'http://github.com/nodeschool/hermanus'
+        lat: -34.4092004
+        lon: 19.2504436
+      - name: Johannesburg NodeSchool
+        location: 'Johannesburg, ZA'
+        organizers:
+          - StevenMcD
+          - johannds
+        website: 'http://nodeschool.io/johannesburg'
+        repo: 'http://github.com/nodeschool/johannesburg'
+        lat: -26.2041028
+        lon: 28.0473051
+      - name: Lagos NodeSchool
+        location: 'Lagos, NG'
+        organizers:
+          - dipolediamond
+          - 0101coding
+        website: 'http://nodeschool.io/lagos'
+        repo: 'http://github.com/nodeschool/lagos'
+        lat: 6.5243793
+        lon: 3.3792057
+      - name: Mombasa NodeSchool
+        location: 'Mombasa, KE'
+        organizers:
+          - huzeifa
+        repo: 'http://github.com/nodeschool/mombasa'
+        lat: -4.0434771
+        lon: 39.6682065
+  - region: Азія
+    conferences:
+      - name: NodeFest (東京Node学園祭)
+        desc: NodeFest is a yearly conference in Tokyo organized by the Node.js Japan user group.
+        link: 'http://nodefest.jp/2015/'
+        twitter: nodefest
+        lat: 35.6580415
+        lon: 139.6960736
+        location: 〒150-0043 東京都渋谷区道玄坂1丁目12番1号 渋谷マークシティ ウエスト13階
+      - name: JSConf.asia
+        location: 'reddot design museum, Singapore, Singapore'
+        link: 'http://jsconf.asia'
+        desc: "JSConf.Asia brings Southeast Asia's open web developer community together to exchange, to learn and entertain."
+        lat: 1.2782037
+        lon: 103.843435
+        twitter: jsconfasia
+      - name: JSConf.cn
+        location: China
+        link: 'http://jsconf.cn/'
+        desc: Yearly JavaScript community conference.
+        lat: 22.5341176
+        lon: 113.9064642
+    meetups:
+      - country: HK
+        city: Hong Kong
+        link: 'http://www.meetup.com/MobAppInnovation/'
+        name: Mobile Application Innovation
+        description: |-
+          <p><span>Experienced developers, novices, those keen to learn and people with ideas (especially original ones) are all welcome.&nbsp;</span> <br></p>
+          <p>We will be arranging presentations from app developers , investors, designers and innovators.</p>
+          <p> <br></p>
+        lon: 114.13999938964844
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/7/4/d/600_439514157.jpeg'
+        lat: 22.270000457763672
+      - country: IN
+        city: Pune
+        link: 'http://www.meetup.com/PuneJS/'
+        name: PuneJS
+        description: "<p>This meetup was started to get the Javascript buzz going in Pune. Let's meet up and join hacking!</p>"
+        lon: 73.83999633789062
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/c/5/8/600_374632312.jpeg'
+        lat: 18.530000686645508
+      - country: IN
+        city: Pune
+        link: 'http://www.meetup.com/expertalks/'
+        name: EXPERTALKS
+        description: |-
+          <p><span><span>Launched and run by</span> <a href="http://equalexperts.com/"><strong>Equal Experts</strong></a><span>, <strong>EXPERTALKS</strong></span> <span>is a</span> <strong>community of software enthusiasts</strong> <span>that meets up frequently to share knowledge.</span></span></p>
+          <p><span>With a keen focus on emerging practices, trends &amp; technologies in software development, EXPERTALKS meetups feature</span> <strong>hands-on workshops</strong> <span>in which participants <strong>code</strong> together to learn new concepts.</span></p>
+          <p><span>Needless to say, this hands-on approach has gained EXPERTALKS a lot of popularity with technologists.</span></p>
+          <p><span>With relevant, and diverse workshops on Agile practices, Big Data frameworks, evolving programming practices, JavaScript libraries, Single Page Applications and so on... EXPERTALKS is fast emerging as one of the most exciting meetups in Pune.</span> <br> <br> </p>
+        lon: 73.83999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/e/f/7/600_441824791.jpeg'
+        lat: 18.530000686645508
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/Node-js-Dilli/'
+        name: Node.js Dilli
+        description: "<p>Community for Node.js hackers and enthusiasts in and around New Delhi, Gurgaon, Noida and the greater NCR.</p>\n<p>Who should join?</p>\n<p>* Node.js and JavaScript programmers, enthusiasts and hackers<br>\n\n * Technologists interested in event based I/O<br>\n\n * Start-ups / organisations evaluating Node.js and related technologies</p>\n<p>What to expect?</p>\n<p>Monthly\_meet-ups, hackathons, demos, sessions, beer.</p>"
+        lon: 77.20999908447266
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/e/9/6/600_113656022.jpeg'
+        lat: 28.670000076293945
+      - country: CN
+        city: Beijing
+        link: 'http://www.meetup.com/developers/'
+        name: 'Web Design & Development'
+        description: "<p>A community passionate about collaborative web development. Come learn about current technologies or just get some help with whatever you're building. Focusing on User Experience Design, Web Standards, XHTML, CSS, Javascript, PHP, Ruby on Rails, Node.js, Browser Support and anything else that's just as awesome.</p>"
+        lon: 116.4000015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/3/3/8/600_140154072.jpeg'
+        lat: 39.93000030517578
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/hyderabad-javascript/'
+        name: Hyderabad Javascript Group
+        description: |-
+          <p>A meetup focused on JavaScript everywhere, including client side, server side, browser, non-browser, etc.. Goals for the group are to spread ideas about node.js, jQuery (including various open source jQuery plugins), Jade, Express, Async.js, Less.js, Chai, Mocha, RequireJS/AMD, EcmaScript 6, etc.</p>
+          <p>Learn and Share.</p>
+        lon: 78.4800033569336
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/1/9/c/600_441397276.jpeg'
+        lat: 17.399999618530273
+      - country: IL
+        city: Herzeliyya
+        link: 'http://www.meetup.com/NodeJS-Israel/'
+        name: NodeJS Israel
+        description: '<p>A group to discuss Node.js, its frameworks, and best practices.</p>'
+        lon: 34.84000015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/f/c/8/600_192272712.jpeg'
+        lat: 32.16999816894531
+      - country: VN
+        city: Thanh Pho Ho Chi Minh
+        link: 'http://www.meetup.com/JavaScript-Ho-Chi-Minh-City/'
+        name: JavaScript Ho Chi Minh City
+        description: |-
+          <p><span style="color : #0000ff">You like Javascript, Ember.js, Angular.js, Node.js, Vert.x, etc.?</span></p>
+          <p><span style="color : #0000ff">You like cutting-edge web technologies?</span></p>
+          <p><span style="color : #0000ff">You want to learn, share and become a master in Javascript and front-end development?</span></p>
+          <p><span style="color : #0000ff"><strong>Why don't you join us - JavaScript Meetup Community to share your great ideas, learn from the others, and widen your network?</strong></span></p>
+          <p><span>------------------------------------------------------</span></p>
+          <p><span>Facebook:</span> <a href="https://www.facebook.com/JavaScriptHCMC">https://www.facebook.com/JavaScriptHCMC</a></p>
+          <p><span>G+:</span> <a href="https://plus.google.com/u/0/communities/116105314977285194967">https://plus.google.com/u/0/communities/116105314977285194967</a></p>
+          <p>------------------------------------------------------</p>
+          <p><strong><em>Fee:</em></strong> <em>To cover the venue cost, the organizer would like to call for 50,000 VND/a person when attending each meetup.</em></p>
+          <p><em>Please register to Nicolas and do payment on the onsite day.</em></p>
+        lon: 106.69000244140625
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/7/d/4/600_196174772.jpeg'
+        lat: 10.779999732971191
+      - country: CN
+        city: Beijing
+        link: 'http://www.meetup.com/HTML5Rocks-Beijing/'
+        name: HTML5Rocks@Beijing
+        description: "<p style=\"text-align : center\"><strong>OUR MISSION:</strong><br>\n\n Our intent is to:. gather developers,idea generators, project manager or any aspiring entrepreneur into a community upon which each one would find support,<br>\n\n . spread the words on HTML5,<br>\n\n . offer a space where one can learn &amp; train himself or herself from a beginner perspective to an advanced level,<br>\n\n<br>\n\n<br>\n\n<br>\n\n<br>\n\n <strong>************************* IMPORTANT *************************</strong><br>\n\n Please note that for now the community is still being nurture .<br>\n\n What does it means exactly ?\_<br>\n\n In order to be able to organize a meet-up, we NEED :\_<br>\n\n . <strong>local co-organizer</strong>: that would represent the community, assure that the meet-up can take place into a venue in Beijing &amp; coordinate with speakers\_<br>\n\n . <strong>speakers</strong>: you are a front-end developer, student, self-taught developer or expert with knowledge / experience on \_HTML5 \_ ?\_<br>\n\n Share your knowledge &amp; experience and help us grow the community &amp; spread the word!<br>\n\n<br>\n\n<br>\n\n Until then , please note that the meet-up will be broadcasted from Singapore via google+ hangout :\_<br>\n\n <strong>HOW TO CONNECT ?</strong><br>\n\n <strong>Subscribe to the HTML5Rocks@SG YouTube channel to follow-up the live streaming.</strong><br>\n\n<br>\n\n<br>\n\n In the meantime, please be considerate to us for the technica issues that can occur with the google+ hangout &amp; help us build the commnity by stepping-up to set-up a strong local presence.</p>\n<p style=\"text-align : center\">\_</p>\n<p style=\"text-align : center\"><span><em>Facebook:</em> <a href=\"https://www.facebook.com/pages/HTML5RocksBeijing/361989453898466\"><span><em>https://www.facebook.com/pages/HTML5RocksBeijing/361989453898466</em></span></a><em><br>\n\n Twitter:</em> <a href=\"https://twitter.com/HTML5RocksBeiji\"><span><em>https://twitter.com/HTML5RocksBeiji</em></span></a><em><br>\n\n Google+:</em></span></p>\n<p style=\"text-align : center\"><span><em>https://plus.google.com/u/3/communities/115636832423784196952<br>\n\n</em></span></p>"
+        lon: 116.4000015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/8/c/a/600_198450922.jpeg'
+        lat: 39.93000030517578
+      - country: RU
+        city: Moscow
+        link: 'http://www.meetup.com/Meteor-Moscow/'
+        name: Meteor Moscow
+        description: "<p>Meet other developers using <a href=\"http://meteor.com\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 37.619998931884766
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/2/1/e/600_422021502.jpeg'
+        lat: 55.75
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/JavaScript-Ninjas-Bangalore/'
+        name: JavaScript Ninjas @ Bangalore
+        description: '<p>A meetup focused on JavaScript everywhere, including client side, server side, browser, non-browser, etc.. Goals for the group are to spread ideas about node.js, jQuery (including various open source jQuery plugins), Jade, Express, Async.js, Less.js, Chai, Mocha, RequireJS/AMD, EcmaScript 6, etc., to socialize projects, and discuss the technology, frameworks and best practices and have Javascript nirvana.........</p>'
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/d/9/c/600_250215772.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Node-js-Explorers/'
+        name: Node.js Explorers
+        description: '<p>Calling all software developers who are interested in exploring JavaScript libraries, tools and frameworks for building rich internet applications in general and Node.js in particular.</p>'
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/b/a/4/600_218231172.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/JSChannel-NCR/'
+        name: JSChannel NCR
+        description: '<p>This is a group for those who like to explore the javascript world, brainstorm different ideas with other js enthusiasts. We will sit together after office hours at coffee shop, in someones office or even it could be on a park bench :) and discuss trends, brainstorm ideas or collectively solve problems.</p>'
+        lon: 77.20999908447266
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/4/a/8/600_281982152.jpeg'
+        lat: 28.670000076293945
+      - country: IL
+        city: Petakh Tiqwa
+        link: 'http://www.meetup.com/HTML-5-JavaScript-Development/'
+        name: 'HTML 5 & JavaScript Development'
+        description: '<p>קבוצה מיועדת לכל מפתחי הווב שמאמינים שאפשר לפתח בווב כל מה שמפתחים ב-Native App ואפילו יותר :-) העתיד שייך לפיתוח אפלקציות בווב...</p>'
+        lon: 34.880001068115234
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/8/6/600_347762182.jpeg'
+        lat: 32.09000015258789
+      - country: TW
+        city: Taipei
+        link: 'http://www.meetup.com/javascript-enthusiasts/'
+        name: Taipei Javascript Enthusiasts
+        description: |-
+          <p><span>This is a group for all things Javascript, front-end and back-end. We invite Javascript newbies, enthusiasts and gurus to come together to share their knowledge. Join this group to learn more about Javascript and to meet other people interested in it.</span></p>
+          <p>Youtube: <a href="https://www.youtube.com/channel/UC9nknJ_fT2iu0a3nQJ_WRRA/videos">Taipei Javascript Enthusiasts</a></p>
+        lon: 121.44999694824219
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/9/7/c/600_446311100.jpeg'
+        lat: 25.020000457763672
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/JavaScript-Explorers/'
+        name: JavaScript Explorers
+        description: '<p>This group is for anyone interested in exploring the world of JavaScript and related frameworks and libraries for building Rich Internet Applications (RIA).</p>'
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/5/a/6/600_223066502.jpeg'
+        lat: 12.970000267028809
+      - country: TH
+        city: Bangkok
+        link: 'http://www.meetup.com/BKK-Developers-and-Tech-lovers/'
+        name: Dev Meetups hosted by HotelQuickly Engineers
+        description: |-
+          <p>A group for anyone interested in Development. It can be System Development, Web Development, Mobile Development or System Administration.&nbsp;</p>
+          <p>Also CTOs, product owners and project managers involved in IT are very welcomed to join us.</p>
+          <p>The goal of the group is to exchange best practices, meet new people and share ideas.</p>
+          <p><b>HotelQuickly's Product &amp; Engineering</b></p>
+          <p>See more about our <a href="http://www.slideshare.net/juhasm/hotelquickly-product-engineering">best practices on Slideshare</a>.</p>
+          <p><b>Topics covered include</b></p>
+          <p>•&nbsp;How to build an Apple Watch app?</p>
+          <p><span>•&nbsp;Build your own scalable infrastructure on Deis</span></p>
+          <p>•&nbsp;<span>What is Docker and how to use it?</span></p>
+          <p>•&nbsp;Building scalable APIs with Nodejs</p>
+          <p>•&nbsp;How to keep track of all the new cool &amp; hot stuff?</p>
+          <p>•&nbsp;Android development best practices</p>
+          <p>•&nbsp;Agile software development</p>
+          <p>•&nbsp;How do we do continuous integration?</p>
+          <p>•&nbsp;How to organise a remote development team?</p>
+          <p>Sexy PHP frameworks</p>
+          <p>•&nbsp;Software design patterns and when to use them?</p>
+          <p>•&nbsp;Best practices from application deployments <br></p>
+          <p> <br></p>
+        lon: 100.5
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/f/8/6/600_436816262.jpeg'
+        lat: 13.729999542236328
+      - country: TH
+        city: Bangkok
+        link: 'http://www.meetup.com/Bangkok-Node-js/'
+        name: Bangkok Node.js
+        description: |-
+          <p>This group is for people interested in learning and using Node.js, the fastest-growing Internet and Web application framework.</p>
+          <p><span>Node.js is similar Python, Java, or Ruby. It is a server-side ("backend") software environment, using JavaScript as its language and architecture (event-driven, callback-based programming). If you have ever written JavaScript for a web browser, now you can write JavaScript as a web server.</span></p>
+          <p><span>Topics of discussion include open source projects, architecture, development and maintenance, deployment, and Node.js trends. If you use Node.js, or if you want to learn more about Node.js, join us to learn all about it.</span></p>
+        lon: 100.5
+        lat: 13.729999542236328
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Women-Who-Code-Bangalore/'
+        name: Women Who Code Bangalore
+        description: |-
+          <p>Mission:</p>
+          <p>Women Who Code is a global nonprofit organization dedicated to inspiring women to excel in technology careers by creating a global, connected community of women in technology. The organization tripled in 2013 and has grown to be one of the largest communities of women engineers in the world.</p>
+          <p>Empowerment:</p>
+          <p>Women Who code is a&nbsp;professional community for women in tech.&nbsp;We provide an avenue for women to pursue a career in technology, help them gain new skills and hone existing skills for professional advancement, and foster environments where networking and mentorship are valued.</p>
+          <p>Key Initiatives:</p>
+          <p>Free technical study groups</p>
+          <p>Events featuring influential tech industry experts and investors</p>
+          <p>Hack events</p>
+          <p>Career and leadership development</p>
+          <p>Current and aspiring coders are welcome.&nbsp;</p>
+          <p>Bring your laptop and a friend!&nbsp;</p>
+          <p>Support Women Who Code:</p>
+          <p><a href="http://womenwhocode.com/donate">Donating to Women Who Code</a>, Inc.&nbsp;(#46-4218859) directly impacts our ability to efficiently run this growing organization, helps us produce new programs that will increase our reach, and enables us to expand into new cities around the world ensuring that women and girls everywhere have the opportunity to pursue a career in technology.</p>
+          <p>Women Who Code (WWCode) is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/womenwhocode">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a></p>
+          <p><a href="http://fb.com/womenwhocode"></a></p>
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/7/5/1/600_431686929.jpeg'
+        lat: 12.970000267028809
+      - country: LK
+        city: Colombo
+        link: 'http://www.meetup.com/Colombo-JS-Meetup/'
+        name: Colombo JS Meetup
+        description: '<p>This group consist of enthusiastic JavaScript developers , we would talk about front end developments , tools, libraries , frameworks, front end testing , node js , meteor and many more. As we know JS is the future so why not learn about it. We hope to have interactive, fun and educational meetups.</p>'
+        lon: 79.8499984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/6/0/0/6/600_434484582.jpeg'
+        lat: 6.929999828338623
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/JSChannel-Bengaluru/'
+        name: JSChannel Bengaluru
+        description: |-
+          <p><span>This is a group of passionate Javascripters. We will get together at a coffee shop, someone's office or any other interesting place. The idea is to get excited by others experiences and excite others with our learning. Our motto could be - 'enough with the presentations... show me some code' :)</span></p>
+          <p>You can join us and discuss on our Slack,&nbsp;https://jschannel.slack.com/</p>
+          <p>For invite, visit<a href="http://jschannel-slack.herokuapp.com/">http://jschannel-slack.herokuapp.com/</a></p>
+          <p>For job related (looking for a job or looking for a candidate) purpose, you can directly send a mail to the group. We are working with couple of guys in the community to solve this recruitment demand &amp; supply. <br></p>
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/7/e/a/600_446890218.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/mean-geeks/'
+        name: 'Jnaapti- MEAN Stack (MongoDB, ExpressJS, AngularJS, NodeJS)'
+        description: "<p>You love technologies? Then this is the place you must be in!</p>\n<p>We love to discuss about</p>\n<ul> \n <p><span>MongoDB</span></p> \n <p><span>AngularJS</span></p> \n <p><span>NodeJs</span></p> \n <p><span>ExpressJS</span></p> \n</ul>\n<p>We can also discuss on Docker, Cloud, Virtualization and various open source technologies!</p>\n<p><br></p>\n<p>Disclaimer: This is an existing meetup group later acquired by jnaapti. All meetups happening here are organized and managed by jnaapti. Any Meetup announced before Feb 28th 2015 was not the responsibility of jnaapti and jnaapti doesn't vouch for any of the past meetups happened through this group. &nbsp;</p>"
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/5/c/8/600_414729672.jpeg'
+        lat: 12.970000267028809
+      - country: RU
+        city: Moscow
+        link: 'http://www.meetup.com/MoscowJS-Meetup/'
+        name: MoscowJS Meetup
+        description: |-
+          <p>Group for people who interested in Javascript Web Development.</p>
+          <p>Official Site: <a href="http://www.moscowjs.ru/">www.moscowjs.ru</a></p>
+        lon: 37.619998931884766
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/e/8/a/600_373503722.jpeg'
+        lat: 55.75
+      - country: TH
+        city: Bangkok
+        link: 'http://www.meetup.com/Bangkok-Javascript/'
+        name: Bangkok Javascript
+        description: '<p>Community who live and fall in love with Javascript. Want to share what and why Javascript is awesome not just for fun but for long time relationship :)</p>'
+        lon: 100.5
+        lat: 13.729999542236328
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/JSChannel-Mumbai/'
+        name: JSChannel Mumbai
+        description: "<p>This is a group of passionate Javascripters. We will get together at a coffee shop, someone's office or any other interesting place. The idea is to share and learn together. Our motto could be - 'enough with the presentations... show me some code' :)</p>"
+        lon: 72.81999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/7/f/7/600_446890231.jpeg'
+        lat: 18.959999084472656
+      - country: PH
+        city: Manila
+        link: 'http://www.meetup.com/Manila-AngularJS-Group/'
+        name: Manila AngularJS Developers (ngManila)
+        description: '<p>This is a group for anyone interested (experienced or new) in developing in AngularJS. Meet ups will be held with the primary goal of sharing knowledge and furthering the science of single-page app development using AngularJS. Expect speakers, networking, and fun!</p>'
+        lon: 120.97000122070312
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/5/5/6/600_440030518.jpeg'
+        lat: 14.619999885559082
+      - country: ID
+        city: Jakarta
+        link: 'http://www.meetup.com/JakartaJS/'
+        name: Jakarta Javascript User Group
+        description: |-
+          <p>Come and meet other developers interested in the JavaScript and it's library in the Greater Jakarta area.</p>
+          <p><span>Twitter:&nbsp;@JakartaJS and we use the hashtag&nbsp;#jakartajs</span></p>
+        lon: 106.83000183105469
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/0/4/f/600_444672367.jpeg'
+        lat: -6.179999828338623
+      - country: PH
+        city: Manila
+        link: 'http://www.meetup.com/Node-js-Philippines/'
+        name: Node.js Philippines
+        description: Meetup group for Node.js Philippines
+        lon: 120.97000122070312
+        lat: 14.619999885559082
+      - country: IL
+        city: Tel Aviv-Yafo
+        link: 'http://www.meetup.com/Hackademy/'
+        name: Hackademy
+        description: '<p>Learning advanced Web and Mobile development frameworks and tools</p>'
+        lon: 34.77000045776367
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/4/e/4/600_316341732.jpeg'
+        lat: 32.06999969482422
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/framework-architects/'
+        name: Framework Architects
+        description: |-
+          <p>Instead of simply USING an existing app framework like Backbone, Durandal, express, etc, this is a meetup group for people interested in MAKING application frameworks.</p>
+          <p>So if you're developing a new application framework of your own then this is the place to come discuss it, present it, and generally ideate on it with other people genuinely interested in application architecture.</p>
+          <p>We discuss, collaborate on, and generally thrash about frameworks both our own as well as the popular ones out there in the open. And we intend to open up the members to each other's styles and strengths and come out with multiple frameworks implemented in open collaboration.</p>
+          <p>See you here some time with your thinking hat on :)</p>
+        lon: 77.20999908447266
+        lat: 28.670000076293945
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/AngularJS-Bangalore/'
+        name: AngularJS Bangalore
+        description: |-
+          <p>Group for AngularJS Enthusiasts... who would love to meet / talk / demo on AngularJS framework. Yes, the framework is vast / big enough &amp; deserves a community for itself!</p>
+          <p>Join the fellow Anglars to meet up next time.</p>
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/2/f/2/600_326634002.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Web-Developers-India/'
+        name: Web Developers India
+        description: '<p>Web Developers India is a group covering all forms of Web Development and JS, Functional Programming, Scalability, Cloud Computing, Mobile and more for developers from India and Sri Lanka. We will host local meet ups, hackatons and opportunities to connect with successful international startups.</p>'
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/7/4/600_332822932.jpeg'
+        lat: 12.970000267028809
+      - country: JP
+        city: Tokyo
+        link: 'http://www.meetup.com/i-teach-you-programming-so-you-teach-me-english/'
+        name: 'I Teach You Programming, So You Teach Me English!'
+        description: "<p>〜 In return for learning programming, please teach me English 〜\_</p>\n<p><br>\n\n</p>\n<p><b>I think it would be good if we could form a group of these people\_</b></p>\n<p>• People interested in learning programming or design that can also speak English.\_</p>\n<p>•\_<span>Designers or Programmers that want to learn English\_</span><br>\n\n</p>\n<p><br>\n\n<br>\n\n <b>Things that I can teach</b></p>\n<p><span>my specialty is web based programming:\_</span></p>\n<p><span>Front-end(HTML/CSS,JavaScript,Flash)\_</span></p>\n<p><span>Back-end(Node.js,PHP,[Ruby, Python])\_</span></p>\n<p><span>I also have some skills in animation and 3D\_</span></p>\n<p><span>Also I'm writing a book on jQuery,\_</span></p>\n<p>and think I would be able to do a reasonable job teaching that.\_</p>\n<p>If our programmer and designer members increase\_</p>\n<p>we can also increase what we are able to teach\_<br>\n\n<br>\n\n</p>\n<p>translate by\_Lochran Huck</p>\n<p><br>\n\n</p>\n<p>〜 プログラミング教えるので、英語教えてください 〜</p>\n<p><br>\n\n</p>\n<p><b>こんな人たちがあつまるといいなぁ</b></p>\n<p>•\_プログラムやデザインを勉強したい英語ができる人</p>\n<p><span>•\_英語を勉強したいプログラマや</span><span>デザイナ</span></p>\n<p><br>\n\n</p>\n<p><b>教えられる事</b></p>\n<p>自分が得意としているのはｗeb系のプログラムで、</p>\n<p>Front-end(HTML/CSS,JavaScript,Flash)も、</p>\n<p>Back-end(Node.js,PHP,[Ruby, Python])もできます。</p>\n<p>アニメーションや3Dなんかもできます。</p>\n<p><span>なにげにjQueryの本とか執筆しているので、</span></p>\n<p><span>そこそこ教えることができると思います。</span></p>\n<p><span>プログラマやデザイナのメンバーが増えたら、</span></p>\n<p><span>教えられる事の項目は増やしていきます。</span></p>\n<p><span><br>\n\n</span></p>\n<p>Lochran Huckさんが翻訳してくれました。<br>\n\n</p>\n<p>ありがとうございます。</p>"
+        lon: 139.77000427246094
+        lat: 35.66999816894531
+      - country: HK
+        city: Hong Kong
+        link: 'http://www.meetup.com/hongkongjs/'
+        name: Hong Kong JavaScript and Node.js
+        description: "<p>Welcome to Hong Kong JavaScript and Node.js! Join us to share ideas, discuss trends, and assess the future of the ever ubiquitous language. Upcoming topics include Introduction to Node.js, Meteor, Client-Side Frameworks, and\_ECMAScript 6.</p>"
+        lon: 114.13999938964844
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/a/8/2/600_413710882.jpeg'
+        lat: 22.270000457763672
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/Mumbai-Technology-Meetup/'
+        name: Mumbai Technology Meetup
+        description: 'Bunch of technology enthusiasts who have been organizing various User Group Meetups for Linux, JavaScript and Python. We decided to collate our efforts and start Mumbai Technology Meetup. We have been having regular offline meetups since the past 1 year for all the above and now look forward to making it more exciting by having a mixed crowd sharing and creating new learning experiences.'
+        lon: 72.81999969482422
+        lat: 18.959999084472656
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/Hyderabad-Couchbase-Community/'
+        name: Hyderabad Couchbase Community
+        description: '<p>Community for Couchbase &amp; opensource technology in and around Hyderabad, India...</p>'
+        lon: 78.4800033569336
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/5/8/600_344761112.jpeg'
+        lat: 17.399999618530273
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/Shanghai-JavaScript-Meetup/'
+        name: Shanghai JavaScript Meetup
+        description: '<p>The Shanghai JavaScript Meetup provides a space for JavaScript enthusiasts to share and develop their skills within the JavaScript community. We welcome contributors of all levels to share their recent work with the community through presentations or shorter lightning talks at each talk/networking event. This community is open to everyone interested in developing the JavaScript community in Shanghai.&nbsp;</p>'
+        lon: 121.47000122070312
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/8/9/a/600_420763162.jpeg'
+        lat: 31.229999542236328
+      - country: IN
+        city: Chandigarh
+        link: 'http://www.meetup.com/Nodejs_chandigarh/'
+        name: Chandigarh Nodejs Javascripters
+        description: '<p>This group is about nodejs and various JavaScript frameworks for front end with some mongodb. New technologies that are changing the web as we consume and produce content, the opportunity is presents for start ups and platforms that can help nurture developers careers.</p>'
+        lon: 76.77999877929688
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/9/e/2/600_413170722.jpeg'
+        lat: 30.75
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/Hyderabad-JavaScript-Meetup/'
+        name: Hyderabad JavaScript Meetup
+        description: 'This group is about JavaScript and related technologies. All skill levels are welcome. I am starting this group to exchanging the ideas, views on JavaScript and related technologies.'
+        lon: 78.4800033569336
+        lat: 17.399999618530273
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/free-software-promoters-network/'
+        name: Free Software Promoters Network - Jnaapti
+        description: "<p>Jnaapti is a technical firm which provides training, but also is a free software promoter.\_</p>\n<p>•\_This meetup group is for all free and open source evangelists who promote open source software.\_</p>\n<p>•\_<span>For people willing to attend sessions on using free software and open source software.\_</span><br>\n\n</p>\n<p>•\_For all like minded people who wish to be the technological change in the community.</p>\n<p>PS: This community is managed by \"<a href=\"http://jnaapti.com/\" class=\"linkified\">http://jnaapti.com/</a>\"</p>"
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/8/b/e/600_369179582.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/Mumbai-Node-js-Meetup/'
+        name: Mumbai Node.js Meetup
+        description: "Let's meet and share our experiences and help each other learn the spectacular Node.js and make it fun to work with!"
+        lon: 72.81999969482422
+        lat: 18.959999084472656
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/www-gmail-com/'
+        name: Bangalore AngularJS Meetup
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: IL
+        city: Tel Aviv-Yafo
+        link: 'http://www.meetup.com/BigPanda-Israel/'
+        name: BigPanda Israel
+        description: "At <a href=\"http://www.bigpanda.io\">BigPanda</a> we work with cutting edge technologies to build our product and infrastructure. We think it's time we share our knowledge with the world through workshops, lectures and hackathons. So if you're looking for coding adventures, you're in the right place!"
+        lon: 34.77000045776367
+        lat: 32.06999969482422
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/docpad-mumbai/'
+        name: docpad-mumbai
+        description: Docpad sets you free. DocPad removes limitations and closes the gap between experts and beginners. Designers and developers can create websites faster than ever before.
+        lon: 72.81999969482422
+        lat: 18.959999084472656
+      - country: IL
+        city: Tel Aviv-Yafo
+        link: 'http://www.meetup.com/Supersonic-developers/'
+        name: Supersonic developers
+        description: "<p>Once in a while we'll meet to share knowledge of the latest cutting edge open source web &amp; mobile technologies. Come to learn new tricks and meet other enthusiastic developers like you at the SupersonicAds office.</p>"
+        lon: 34.77000045776367
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/4/9/e/600_394581662.jpeg'
+        lat: 32.06999969482422
+      - country: IN
+        city: Ahmedabad
+        link: 'http://www.meetup.com/Ahmedabad-AngularJS/'
+        name: Ahmedabad AngularJS
+        description: 'This group is created to spread awareness about AnuglarJS, educating UI/UX developers, Web Developers to leverage the power of AngularJS in building marvellous web applications. Any one interested in this platform can join the group.'
+        lon: 72.58000183105469
+        lat: 23.030000686645508
+      - country: TW
+        city: Taipei
+        link: 'http://www.meetup.com/tech-design/'
+        name: 'Startup Code Camp - connects Idea, Technology and Investor'
+        description: |-
+          <p><b>Startup Code Camp &nbsp;is &nbsp;free &nbsp;</b><span><span>startup and code education with prototyping solution and&nbsp;</span>investment<span>&nbsp;network. </span></span><span>No matter you are interested in learning code &nbsp;startup, or if you are engineer, designer , investors interested in partner with us. Feel free to join our</span> <br></p>
+          <p><span>免費學習軟體開發與新創，提供快速開發服務與投資合作。</span><span>無論你是想學習程式或新創，或是工程師，設計師，投資人希望參與專案合作，都會有一起參與我們的startup Code Camp。</span> <br></p>
+          <p> <br></p>
+          <p><b>Startup Code Camp Event Schedule 活動內容:</b></p>
+          <p><b>1. One- minute</b>&nbsp;<b>Pitch Time</b>&nbsp;(30 min):</p>
+          <p>•&nbsp;Intro about you, idea or business&nbsp;</p>
+          <p>• Your current problem or what you need&nbsp;</p>
+          <p><b><br></b></p>
+          <p><b>2. Trending Topic of the week </b>(optional 30 min)</p>
+          <p><b>3. Free Network or Code Discussion Time</b></p>
+          <p> <br></p>
+          <p><b>Location 地點 ：</b></p>
+          <p>Taipei Bridge Mrt 3F Innosquare , Bar area</p>
+          <p>台北橋捷運站 3F，新北創立坊，吧檯區</p>
+          <p> <br></p>
+          <p> <br><b>Code &amp; Startup Learning Material :</b></p>
+          <p><a href="https://hackpad.com/Startup-Code-Camp-Workshop-51fDlZLdbyo">https://hackpad.com/Startup-Code-Camp-Workshop-51fDlZLdbyo</a>&nbsp;</p>
+          <p>Code Beginner please start with Codecademy angular Part 1:&nbsp;</p>
+          <p><a href="https://www.codecademy.com/learn/learn-angularjs">https://www.codecademy.com/learn/learn-angularjs</a></p>
+          <br>
+          <br>
+          <p> <br></p>
+        lon: 121.44999694824219
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/6/6/a/600_444322122.jpeg'
+        lat: 25.020000457763672
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/NodeJS-Hyderabad/'
+        name: NodeJS Hyderabad
+        description: '<p>Calling all NodeJS Developers in Hyderabad to brain storm how NodeJS is changing the world and breaking the principles.</p>'
+        lon: 78.4800033569336
+        lat: 17.399999618530273
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/Web-Development-Meetup-Delhi-Chapter/'
+        name: Web Development Meetup - Delhi Chapter
+        description: 'Calling all Web developers, calling all innovators, calling all who want to make internet a beautiful place making it the most dynamic platform for one and for all. Discuss your innovative ideas and let it be guided by industry experts and let it flourish. Discuss your problems, discuss new ideas. Let it all flow..'
+        lon: 77.20999908447266
+        lat: 28.670000076293945
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/efjsday/'
+        name: '#EFJS'
+        description: |-
+          <p><span>An incredible JavaScript community built by EF Education First and friends. We're the group of people behind the world's biggest online English school built with JavaScript, we aim to connect more developers around Shanghai <b>speaking both English and JavaScript</b>, attending :</span></p>
+          <p>• Meet new friends</p>
+          <p>• Great JavaScript topics <br></p>
+          <p>• Oral English Practice and improve presentation skills</p>
+          <p>• Get entertained ;) <br></p>
+          <p>Think of this meet-up as an <b>open events stream</b>, we don't really impose a fixed schedule, you subscribe to our calendar and pick the event that suits you time and your taste , we will raise per event as soon as we have a speech/session/workshop topic, so it doesn't have to be a hundred ppls on the same track.&nbsp;</p>
+          <p><span>Our place offers spaces with different size, depending on how many RSVPed in each event, you will be either sitting in small room with tv, &nbsp;or to stay in the&nbsp;</span><span>stadium steps in front of a projection wall. We offer <b>free coffee and WIFI</b> for everybody.</span> <br></p>
+          <p> <br></p>
+        lon: 121.47000122070312
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/a/c/3/600_439763235.jpeg'
+        lat: 31.229999542236328
+      - country: IN
+        city: Kochi
+        link: 'http://www.meetup.com/kochi-javascript/'
+        name: Kochi Javascript Ninjas
+        description: '<p>People who loves to learn and explore Javascript!</p>'
+        lon: 76.22000122070312
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/4/3/6/600_381598422.jpeg'
+        lat: 10.020000457763672
+      - country: IN
+        city: Kochi
+        link: 'http://www.meetup.com/Kochi-Noders/'
+        name: Kochi Noders
+        description: |-
+          <p>You want to learn or share anything regarding modern opensource technologies&nbsp;Node.js, Angular.js, React.js , Kochi Noders is the place!</p>
+          <p>Kochi Noders conducts seminars, workshops, discussions in and around Kochi on monthly basis.&nbsp;</p>
+        lon: 76.22000122070312
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/3/a/6/600_382614182.jpeg'
+        lat: 10.020000457763672
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Node-js-and-BlueMix-Meetup/'
+        name: Node.js and Bluemix Meetup
+        description: |-
+          <p>IBM® Bluemix™ provides a SDK for Node.js starter application that you can use as a template. You can add your code to the starter application, and then push the changes back to Bluemix.<br>
+
+          </p>
+          <p><b>What is IBM Bluemix?</b><br>
+
+           Bluemix is an open-standard, cloud-based platform for building, managing and running applications of all types (web, mobile, Big Data Analytics, new smart devices, and so on). Capabilities include Java, mobile back end development, application monitoring, as well as capabilities from ecosystem partners and open source software all through an as-a-service model in the cloud.With Bluemix, you can code in your choice of language, such as Java, Python, Ruby, or Node, focus on running your apps and not have to worry about getting servers or installing software.</p>
+          <p>This group is for those who are excited about connecting disparate devices to one another via the IBM Bluemix. Subject Matter Experts, Developers, Researchers, IT Consultants &amp; Beginners who want to learn what this is all about.....</p>
+          <p>All are welcome!</p>
+          <p>we learn about Bluemix hands on with fellow developers and Bluemix product architects(from IBM). <b>Our meetups are free.</b></p>
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/0/2/2/600_392372802.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/AngularJS-Mumbai/'
+        name: AngularJS Mumbai
+        description: 'This group is for people interesting in AngularJs. All skill levels are welcome. Motive of this group is to create a local community which can act a knowledge base and a great discussion group for all the angularjs things. be it a small application or a huge enterprise app built using angularjs , some one looking for a job or someone want to hire the talent. Welcome to AngularJs Mumbai.'
+        lon: 72.81999969482422
+        lat: 18.959999084472656
+      - country: IN
+        city: Kolkata
+        link: 'http://www.meetup.com/Kolkata-AngularJS-Meetup/'
+        name: Kolkata AngularJS Meetup
+        description: This is a group for anyone interested in learning about AngularJS. It is also the first step in making a vibrant tech startup culture in Kolkata. Open to everyone without any bar of age or experience it is a place where we can all grow together and build great things.
+        lon: 88.36000061035156
+        lat: 22.56999969482422
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/JavaExperts/'
+        name: Java Meetup
+        description: This is a group for developers  interested in Spring Hibernate Javascript Angular Js Ext Js.
+        lon: 78.4800033569336
+        lat: 17.399999618530273
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Bangalore-Node-MongoDB-Meetup/'
+        name: Bangalore Node+MongoDB Meetup
+        description: '“This is a group for anyone interested in NodeJs ,MongoDb. I started this group because to meet other NodeJs and MongoDB developer and we will learn from each other."'
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: IN
+        city: Chennai
+        link: 'http://www.meetup.com/Meteor-Chennai/'
+        name: Meteor Chennai
+        description: '<p>This is a group for web developers who works on Meteor framework. Meteor is a complete web stack built on top of Node.js for building real time web applications.</p>'
+        lon: 80.2699966430664
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/f/1/2/600_428080722.jpeg'
+        lat: 13.09000015258789
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/Mumbai-JS/'
+        name: Mumbai JS Meetup
+        description: '<p>This is for anyone who knows and wants to digg more in JS. <br></p>'
+        lon: 72.81999969482422
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/1/e/2/600_435252770.jpeg'
+        lat: 18.959999084472656
+      - country: IN
+        city: Pune
+        link: 'http://www.meetup.com/Pune-Node-js-User-Group/'
+        name: Pune Node.js User Group
+        description: 'This meetup is focused on spreading knowledge and best practices for the use of Node.js. Topics of discussion include OSS projects, architectures, testing, devops, code management, deployment strategies, the future of Node and emerging trends.'
+        lon: 73.83999633789062
+        lat: 18.530000686645508
+      - country: IN
+        city: Ahmedabad
+        link: 'http://www.meetup.com/meetup-group-iAIoTVuS/'
+        name: Ahmedabad NodeJS
+        description: A group to create awareness about NodeJS and educating developers in Node.js
+        lon: 72.58000183105469
+        lat: 23.030000686645508
+      - country: TW
+        city: Taipei
+        link: 'http://www.meetup.com/Meteor-Taipei/'
+        name: Meteor Taipei
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 121.44999694824219
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/0/a/c/600_435796556.jpeg'
+        lat: 25.020000457763672
+      - country: IN
+        city: Bhubaneswar
+        link: 'http://www.meetup.com/Bhubaneswar-nodeJS-and-javascript-developers/'
+        name: Bhubaneswar nodeJS and javascript developers
+        description: "<p><img src=\"http://photos4.meetupstatic.com/photos/event/5/2/8/c/600_430281132.jpeg\" style=\"margin : 5px ; max-width : 700px ; max-height : 700px\"></p>\n<p>This is a group for web developers who love opensource technologies particularly javascript in writing down both server side and client side code and \_developing hybrid mobile apps using web technologies.</p>"
+        lon: 85.83999633789062
+        lat: 20.270000457763672
+      - country: IL
+        city: Rishon LeZiyyon
+        link: 'http://www.meetup.com/GDG-Rashlatz/'
+        name: GDG Rashlatz
+        description: |-
+          <p>Google Developer Group - Rishon Le Zion</p>
+          <p>In these meetups we'll talk about current and future web &amp; mobile technologies, entrepreneurship and other geeky stuff</p>
+          <p>Finally, there is a group for all of the Rishon, Bat Yam, Holon, Nes Ziona, Rehovot and the Sviva to meet without the traffic jams of Tel Aviv :)</p>
+          <p><br>
+
+          </p>
+          <p>Also join our <a href="https://plus.google.com/116818838111714845459">Google+ Page</a></p>
+        lon: 34.79999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/3/b/2/600_410125522.jpeg'
+        lat: 31.959999084472656
+      - country: AE
+        city: Dubai
+        link: 'http://www.meetup.com/JS-Dubai/'
+        name: JS Dubai
+        description: '<p>Lectures and panels on topics concerning the JavaScript programming language.</p>'
+        lon: 55.33000183105469
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/0/8/c/600_400748332.jpeg'
+        lat: 25.270000457763672
+      - country: PH
+        city: Cebu
+        link: 'http://www.meetup.com/Cebu-JavaScript-Meetup/'
+        name: Cebu JavaScript Meetup
+        description: "Calling all JavaScript enthusiasts, from beginner to ninja! Let's get together to talk all about JS."
+        lon: 123.9000015258789
+        lat: 10.319999694824219
+      - country: ID
+        city: Jakarta
+        link: 'http://www.meetup.com/Jakarta-node-js-Meetup/'
+        name: Jakarta node.js Meetup
+        description: |-
+          <p><br>
+
+          </p>
+          <p>This is a group for anyone interested in nodejs</p>
+        lon: 106.83000183105469
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/a/a/600_403020682.jpeg'
+        lat: -6.179999828338623
+      - country: ID
+        city: Jakarta
+        link: 'http://www.meetup.com/Node-js-Workshop/'
+        name: Node.js Jakarta
+        description: '<p>Apa itu node js?, Platform yang mengunakan Chrome engine v8 , dalam perkembanganya node.js tidak hanya server side namun client side dan dapan berjalan di semua OS dan platform , distribusi nya dapat di deploy ke semua device (IOS, Android, Windows phone, Windows, Mac OS, Linux, etc), menggunakan bahasa javascript yang sama seperti implementasi dalam development web. Di Workshop ini kita akan belajar bagaimana mengembangkan applikasi menggunakan node.js dari awal sampe mahir. dengan konsep belajar berbagi ide dan sharing knowledge</p>'
+        lon: 106.83000183105469
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/7/7/3/600_432098771.jpeg'
+        lat: -6.179999828338623
+      - country: IN
+        city: Ni Dilli
+        link: 'http://www.meetup.com/Ni-Dilli-AngularJS-Meetup/'
+        name: Ni Dilli AngularJS Meetup
+        description: 'This group is to discuss Angular JS and stuff. How to proceed learning Angular, best methods, working on some project together.'
+        lon: 77.22000122070312
+        lat: 28.600000381469727
+      - country: PH
+        city: Cebu
+        link: 'http://www.meetup.com/javascript-cebu/'
+        name: Javascript Cebu
+        description: '<p>Promote Javascript and other cutting edge web application development technology to Cebu</p>'
+        lon: 123.9000015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/8/c/c/600_439094540.jpeg'
+        lat: 10.319999694824219
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/Web-Mobile-Full-Stack-AngularJS-NodeJS-NoSQL-Meetup/'
+        name: Web/Mobile - Full Stack (AngularJS + NodeJS + NoSQL) Meetup
+        description: 'This is a group for anyone interested to know about latest web / mobile technologies, either front-end, middleware or backend DBs. Its for full-stack engineers / architects, focused on developing apps using JavaScript (JSEverywhere). We will discuss about AngularJS, NodeJS and NoSQL DBs.'
+        lon: 78.4800033569336
+        lat: 17.399999618530273
+      - country: TW
+        city: Taipei
+        link: 'http://www.meetup.com/Taipei-D3-js-Meetup/'
+        name: Taipei D3.js
+        description: "<p>D3.js 是目前被廣泛使用的前端可視化 Library，</p>\n<p>Taipei D3.js 期盼聚齊更多數據可視的愛好者，藉由難得相聚的機會，</p>\n<p>一起研究、學習與交流D3.js的應用與技術，並推廣與分享D3應用方法與繪圖模組。</p>\n<p><b>視覺化的目的想讓使用者更容易解讀數據後背後真正的意圖，讓數據更具體且靈活地呈現。</b></p>\n<p>先有 \"<b>看得懂的數據</b>\"，才能解析 \"<b>有價值的洞察</b>\" ，最後才會產出 \"<b>合理的決策行動</b>\"</p>\n<p>-----<br>\n\n</p>\n<p>未來規劃在每個月月中，將定期舉辦交流聚會，</p>\n<p>期盼在學習與分享的過程中互相交流，加速大家的創新過程。</p>\n<p><i>[誠徵講者中...]</i><br>\n\n</p>\n<p>邀請D3同好、先進一起分享自己的學習經驗或應用模組\_</p>\n<p>Taipei D3.js Meetup 分享日程表\_ <a href=\"http://goo.gl/466UiS\">http://goo.gl/466UiS</a><br>\n\n</p>\n<p><i>歡迎來信分享 .. d3.meetup@gmail.com</i><br>\n\n</p>"
+        lon: 121.44999694824219
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/5/4/e/600_410618222.jpeg'
+        lat: 25.020000457763672
+      - country: IN
+        city: Chandigarh
+        link: 'http://www.meetup.com/AngularJS-presentation/'
+        name: AngularJS presentation
+        description: AngularJs is nex big thing. I have made an power point presentation of angular Basics. Hope this will useful for angyualrJs developer.
+        lon: 76.77999877929688
+        lat: 30.75
+      - country: IN
+        city: Ahmedabad
+        link: 'http://www.meetup.com/Ahmedabad-JavaScript-Enthusiasts/'
+        name: Ahmedabad JavaScript Enthusiasts
+        description: 'This is a group for people interested in Javascript, JQuery, AngularJS, EmberJS, ReactJS, NodeJS, GruntJS, MeteorJS. Meetups will be focused on new cutting edge Javascript frameworks that are redefining web app development of this times. Aim is to leverage collaborative wisdom in context of Javascript technologies.'
+        lon: 72.58000183105469
+        lat: 23.030000686645508
+      - country: JP
+        city: Tokyo
+        link: 'http://www.meetup.com/tokyojs/'
+        name: TokyoJS
+        description: |-
+          <p>This is a group for anyone interested in JavaScript, its good and bad parts. Let's awe together in the beauty and quirkiness of this language, that has stuck with us for almost two decades. Let's gather to share, explore and learn about everything-JavaScript.&nbsp;</p>
+          <p>これはJavaScriptに興味をお持ちの方の新グループです。 特有なところも美しいところも、いずれにせよ唯一無二のJavaScriptを一緒に楽しみましょう。 JavaScriptの全てを探検しながら、勉強したい方も、教えたい方も、皆さんどうぞをご参加ください。</p>
+          <p><img src="http://photos4.meetupstatic.com/photos/event/d/2/8/e/600_428033902.jpeg"></p>
+          <p> <br></p>
+        lon: 139.77000427246094
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/6/6/2/b/600_444746155.jpeg'
+        lat: 35.66999816894531
+      - country: IL
+        city: Tel Aviv-Yafo
+        link: 'http://www.meetup.com/Joola-data-analytics-meetup/'
+        name: Joola data analytics meetup
+        description: "<p>Joola is the easiest way to build data analytics applications. This group is for anyone interested in deploying data analytics &amp;amp; visualization apps using Joola's <a href=\"https://github.com/joola/joola\">opensource framework</a>, or <a href=\"https://joo.la\">our PaaS solution</a>.</p>"
+        lon: 34.77000045776367
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/3/7/0/600_431433648.jpeg'
+        lat: 32.06999969482422
+      - country: IL
+        city: Rishon LeZiyyon
+        link: 'http://www.meetup.com/Techome/'
+        name: Techome
+        description: '<p>TECHOME was established for the benefit of encouraging entrepreneurship, and strengthening the culture of cooperation and knowledge sharing, and exposing the thelatest technologies to the people of Rishon Lezion ( Israel) and surrounding.</p>'
+        lon: 34.79999923706055
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/7/9/2/600_418518322.jpeg'
+        lat: 31.959999084472656
+      - country: HK
+        city: Hong Kong
+        link: 'http://www.meetup.com/Hong-Kong-MEAN-Full-Stack-Developers/'
+        name: Hong Kong MEAN Javascript Full Stack Development
+        description: "<p>For <b>Developers, Entrepreneurs and Designers</b> who are interested in learning \_how</p>\n<p><b>MEAN</b> (Mongo, Express, Angular, Node)\_stack and\_</p>\n<p><b>MISO</b> (Micro Interoperable Services Oriented) architecture\_</p>\n<p>can help you work together to rapidly develop world class scalable <b>web/mobile apps</b>.\_</p>\n<p><span>Join to meet and learn from each other how to make the most out of MEAN and MISO.\_</span></p>\n<p><span>The group aims to provide <b>talks, trainings, hackathons</b> to bring up the MEAN and MISO community! If you are new to web development, this is a good starting point to learn a great development framework!</span><br>\n\n</p>"
+        lon: 114.13999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/d/c/8/600_421819912.jpeg'
+        lat: 22.270000457763672
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/Shanghai-Web-Dev-and-Design-Club/'
+        name: Shanghai Web Dev and Design Club
+        description: "<p>The Shanghai Web Dev &amp; Design club is for anyone interested in learning and exchanging industry tips and trends in JavaScript, CSS, PHP, python, HTML5, responsive design, servers, node.js, APIs, or anything else people want to discuss. Let's make some sexy websites! Such code, much fun, Wow! All levels welcome.</p>"
+        lon: 121.47000122070312
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/f/6/8/600_421996232.jpeg'
+        lat: 31.229999542236328
+      - country: IN
+        city: Thiruvananthapuram
+        link: 'http://www.meetup.com/tvm-js/'
+        name: tvmJs
+        description: '<p>Meet the other JavaScript developers in Trivandrum. Share your knowledge, apps and get feedback. No more presentations - "show me the code".</p>'
+        lon: 76.94999694824219
+        lat: 8.510000228881836
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/Shanghai-JSer-Reunion/'
+        name: Shanghai JSer Reunion
+        description: '<p>Either you have any interesting JS trick to share, or you want to have your tech stack updated, SIGN UP NOW! We are going to provide foods and drinks for free from 6:00pm. The Session would be officially launched from 6:30pm. After session, we will also enjoy music/game together.</p>'
+        lon: 121.47000122070312
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/8/3/4/600_427011252.jpeg'
+        lat: 31.229999542236328
+      - country: IN
+        city: Chennai
+        link: 'http://www.meetup.com/Chennai-Angular-JS-Front-End-Meetup-by-Sciflare/'
+        name: Chennai Angular JS / Front End Meetup by Sciflare
+        description: 'We welcome ALL, who are interested in learning or mastering Full Stack JavaScript Application development using Angular JS, Backbone JS, Node JS, HTML5, CSS3, React JS, Ember JS, Express, Mongo DB, NoSQL. All skills levels are welcome. We (Sciflare Technologies) started this group because to meet other Tech enthusiasts to share our expertise &amp; exchange ideas in solving real world problems in the Enterprise &amp; User driven applications where best is just not enough :) Excited to meet you all at the Meetup !'
+        lon: 80.2699966430664
+        lat: 13.09000015258789
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/MEAN-stack-Developers/'
+        name: MEAN stack Developers
+        description: 'MEAN stack is an open source stack which allows developers to build awesome and dynamic web applications!'
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: IN
+        city: Chennai
+        link: 'http://www.meetup.com/Javascript-G/'
+        name: Javascript-G
+        description: This group is for anyone who what to share and learn best practices of javascript and related technologies
+        lon: 80.2699966430664
+        lat: 13.09000015258789
+      - country: PH
+        city: Pasig City
+        link: 'http://www.meetup.com/Pasig-City-node-js-Meetup/'
+        name: Pasig City node.js Meetup
+        description: All about programming and cloud computing with Node.JS
+        lon: 121.08999633789062
+        lat: 14.579999923706055
+      - country: ID
+        city: Semarang
+        link: 'http://www.meetup.com/Semarang-node-js-Meetup/'
+        name: node.js Semarang
+        description: '<p>member of node.js indonesia nantikan workshop kami di semarang</p>'
+        lon: 110.41999816894531
+        lat: -6.96999979019165
+      - country: BD
+        city: Dhaka
+        link: 'http://www.meetup.com/Dhaka-JS/'
+        name: DhakaJS
+        description: |-
+          <p>Developers interested in sharing knowledge and growing their skills around JavaScript and modern web technology: e.g. ES6, AltJS, NodeJS, Angular, Ember, Browserify, Web Components,&nbsp;HTML5 APIs,&nbsp;LevelDB, etc.</p>
+          <p><br></p>
+          <p>If you want to help out, sponsor, or have any suggestions or feedback, just get in touch!</p>
+        lon: 90.38999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/c/2/e/600_434895406.jpeg'
+        lat: 23.700000762939453
+      - country: IL
+        city: "Ra'anana"
+        link: 'http://www.meetup.com/Web-Developers-Community/'
+        name: Web Developers Community
+        description: "The Web Developer Community is a group of developers that are interested in web technologies. We meet at Microsoft office at Ra'anana and discuss the latest web technologies like NodeJS, AngularJS and ASP.NET vNext."
+        lon: 34.880001068115234
+        lat: 32.189998626708984
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/jslovers/'
+        name: Lets decode the Javascript
+        description: |-
+          <p><b>Hello JavaScript Lovers,</b></p>
+          <p>Are you passionate about <b><i>Web Development, Javascript, HTML5, CSS, JS Libraries &amp; Frameworks</i></b>? Do you love spending hours talking about its&nbsp;fundamentals and functions? If yes, then welcome to <b><i>JSLovers- a community for the&nbsp;</i></b><b><i>JavaScript and Front-end technologists</i></b> like you and me.</p>
+          <p>We at JSLovers believe on - "Talk Less and Code More" approach.</p>
+          <p>Follow us @<b>jslovers_del </b>on twiiter&nbsp;</p>
+          <p>Love to be speaker or sponsor or want to post your project requirement/job requirement contact :</p>
+          <p>hello@jslovers.com</p>
+          <p><b> <br></b></p>
+          <p><b>What is JSLovers?</b> <br></p>
+          <p><b>At JSLovers we follow the approach of "Talk Less and Code More" approach.&nbsp;</b></p>
+          <p><span>It is a platform where you can attend sessions,meet and interact with JavaScript fanatics like&nbsp;</span><span>you and share your knowledge with them. It also gives you a chance to share your&nbsp;</span><span>enthusiasm of front end developers in Front-end field and apprise yourself of latest&nbsp;</span><span>developments in the field.</span></p>
+          <p><b> <br></b></p>
+          <p><b>Who are the face of JSLovers?</b></p>
+          <p>Currently, there are two of us &nbsp;running the show and give our best. We are looking&nbsp;<span>for people who want to come forward and share knowledge with the community.</span></p>
+          <br>
+          <p><b>What we have done so far?</b></p>
+          <p><span>We have a strong community of <b>500+</b> JSLovers on meetup</span></p>
+          <p><span>On <a href="https://www.facebook.com/javascriptlovers">Facebook</a>&nbsp;we have <b>400+</b></span></p>
+          <p><span>On <a href="http://jslovers.com">our site</a> we have <b>9000 sessions</b> so far.</span></p>
+          <p>On our Facebook page - <a href="https://www.facebook.com/javascriptlovers">https://www.facebook.com/javascriptlovers</a> on we keep posting&nbsp;<span>and sharing valuable information about the technologies, meetups, Sessions and also&nbsp;</span><span><span>post questions related to the&nbsp;</span>JavaScript<span>/Angular/Node/HTML, etc.</span></span></p>
+          <br>
+          <p>We also have our website <a href="http://Jslovers.com">Jslovers.com</a> , which we try to update on regular basis.</p>
+          <p><span> <br></span></p>
+          <p><span><b>Are these are paid or free?</b></span> <br></p>
+          <p>We know people LOVE FREE things, but in this world there is nothing like "Free Lunches".</p>
+          <p><span><b>Depends</b>. Few are free and few are paid. If you are serious learner you won't mind&nbsp;</span><span>paying for the knowledgeable sessions.</span></p>
+          <br>
+          <p><b>What is in future?</b></p>
+          <p><span>Our community is evolving and adapting to latest innovations in technology and market&nbsp;</span><span>demands. Join our Meetup Group and FB page to know the latest of the industry and&nbsp;</span><span>sessions.</span></p>
+          <p><span><br></span></p>
+          <p><span>CODE OF CONDUCT</span></p>
+          <p>If we find someone abusing or disrespecting the organizers, speakers or audience. We hold the right to ask that person to leave the workshop &amp; community. We won't think once before blocking that person.&nbsp;</p>
+          <p><span> <br></span></p>
+          <p><span>Happy learning!!</span></p>
+          <p> <br></p>
+          <p> <br></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: 77.20999908447266
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/0/4/8/600_433592840.jpeg'
+        lat: 28.670000076293945
+      - country: HK
+        city: Hong Kong
+        link: 'http://www.meetup.com/Hong-Kong-JavaScripter-Meetup/'
+        name: Hong Kong JavaScripter Meetup
+        description: 'Javascripters in HK assemble! We love to rant about how hideous JQuery is and our glorious self-made homebrew framework is superior to React.js. We had heated discussion of FP vs OOP in Javascript and how AngularJS is destroying the only place where Java is not ruining a generation of programmers. All those are tea and coffee fueled. Hope everyone can achieve the "Tao" of Javascript!'
+        lon: 114.13999938964844
+        lat: 22.270000457763672
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Bangalore-WebRTC-Meetup/'
+        name: Bangalore WebRTC Meetup
+        description: This group is being created to find out all the people who are really excited about WebRTC and related real time communication techniques and imagine to change the world through such a technology. We strongly believe that WebRTC has the potential to change the world. We invite everyone to explore the fascinating world of real time communication technologies and to find out how everyone can build game changer products with the help of these.
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: VN
+        city: Ha Noi
+        link: 'http://www.meetup.com/Ha-Noi-JavaScript-Application-Meetup/'
+        name: Ha Noi JavaScript Meetup
+        description: '<p>For local people who are interested in new developments of JavaScript in web application, desktop application, different front-end frameworks and tech startups. We have a Facebook group here&nbsp;https://www.facebook.com/groups/hanoiJS/</p>'
+        lon: 105.83999633789062
+        lat: 21.030000686645508
+      - country: IN
+        city: Mumbai
+        link: 'http://www.meetup.com/Mumbai-JavaScript-Meetup/'
+        name: Mumbai JavaScript Meetup
+        description: "Do you develop in AngularJS, Backbone, EmberJS, NodeJS, io.js or anything in JavaScript? If yes, then this meetup is for you. We'll be targeting talks on pure JavaScripts talks, Functional programming and latest trends in the community. Join us to keep yourself up to date. "
+        lon: 72.81999969482422
+        lat: 18.959999084472656
+      - country: NP
+        city: Kathmandu
+        link: 'http://www.meetup.com/KathmanduJS/'
+        name: KTMJS
+        description: '<p>Javascript is increasing in popularity but there are very few people writing frontend-heavy apps in javascript in Nepal. Let us meet and promote Javascript development.</p>'
+        lon: 85.30999755859375
+        lat: 27.709999084472656
+      - country: TW
+        city: Taipei
+        link: 'http://www.meetup.com/Code-Coffee-Conquer/'
+        name: Code. Coffee. Conquer.
+        description: "Let's meet at a coffee shop, grab coffee, write some code and conquer the world! In a positive way! :-)\n\nThe meetings will be very informal. Come share your experiences in technology, make a friend, find a mentor, coach a colleague and drink coffee! "
+        lon: 121.44999694824219
+        lat: 25.020000457763672
+      - country: IL
+        city: Tel Aviv-Yafo
+        link: 'http://www.meetup.com/ReactJS-Israel/'
+        name: 'React & Redux Israel'
+        description: '<p>Come and learn about the new disruptive technology from&nbsp;Facebook. Create Components and make your&nbsp;frontend&nbsp;blazing fast. We will focus on&nbsp;ReactJS&nbsp;and the supplemental infrastructure like Flux.</p>'
+        lon: 34.77000045776367
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/d/4/2/600_440492066.jpeg'
+        lat: 32.06999969482422
+      - country: IL
+        city: Herzeliyya
+        link: 'http://www.meetup.com/IsraeliAzureDevelopers/'
+        name: Israeli Azure Developer Community
+        description: |-
+          <p>The Israeli Azure Developer Community meets approximately once every two months at the Microsoft offices at Ra'anana to discuss all things related to Azure... Everything goes!</p>
+          <p><a href="http://www.meetup.com/IsraeliAzureDevelopers/about/">Learn More</a></p>
+        lon: 34.84000015258789
+        lat: 32.16999816894531
+      - country: IN
+        city: Pune
+        link: 'http://www.meetup.com/JavaScripters/'
+        name: JavaScripters
+        description: "<p>Let's get together for affordable activities on javascript knowledge sharing, training, discussions , job referrals network.</p>"
+        lon: 73.83999633789062
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/7/8/7/600_443710119.jpeg'
+        lat: 18.530000686645508
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/ionic-meetup/'
+        name: Ionic Meetup
+        description: 'A meetup for all the AngularJS lovers to share their experiences, skill-sets and application ideas.'
+        lon: 77.20999908447266
+        lat: 28.670000076293945
+      - country: IL
+        city: "Modi'in"
+        link: 'http://www.meetup.com/Modiin-Tech-Talks/'
+        name: Modiin Tech Talks
+        description: |-
+          <p>Modiin Tech Talks is a meeting place for people interested in all areas for development. We give presentations, run Hackathons, and discuss r<span>elevant topics.</span></p>
+          <p> <br></p>
+          <p>The group had a few meetings in 2014, but we started to use Meetup only in May 2015.</p>
+          <p><span>Our primary location for meetings is going to be at <a href="http://modiinhub.com/">MESH in Modiin</a>.&nbsp;</span> <br></p>
+        lon: 35.0099983215332
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/8/1/600_438961921.jpeg'
+        lat: 31.899999618530273
+      - country: RU
+        city: St. Petersburg
+        link: 'http://www.meetup.com/meteorspb/'
+        name: METEOR St. Petersburg
+        description: |-
+          <p><a href="https://www.meteor.com/">Meteor</a> - платформа для создания так называемых real-time web apps – современных веб-приложений.&nbsp;<span> <br></span></p>
+          <p><span>Мы обсуждаем аспекты при работе с платформой, делимся опытом и активно объединяемся в группу для проведения постоянных встреч-обсуждений.</span> <br></p>
+          <p>МитАпы проходят в центре Петербурга. Участие бесплатное.</p>
+          <p>Наша группа Вконтакте -&nbsp;<a href="http://vk.com/meteormeetup">http://vk.com/meteormeetup</a></p>
+          <p>Присоединяйтесь! <br> <br>--- --- --- --- --- --- --- --- --- ---&nbsp;</p>
+          <p><a href="https://www.meteor.com/">Meteor </a>is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>
+          <p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. <br> <br>MeetUps are held in Saint-Petersburg and are Free of charge. <br> <br>Don't hesitate to Join us!&nbsp;</p>
+        lon: 30.31999969482422
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/6/0/d/600_439029741.jpeg'
+        lat: 59.93000030517578
+      - country: RU
+        city: Tomsk
+        link: 'http://www.meetup.com/tomsk-front-end-meetup/'
+        name: Tomsk Front-end Development Meetup
+        description: |-
+          <p>Группа для организации встреч томских front-end разработчиков.</p>
+          <p> <br></p>
+          <p>Приглашаем всех желающих развивать свои профессиональные навыки.</p>
+          <p> <br></p>
+          <p>Планируется проведение:</p>
+          <p>•&nbsp;лекций,</p>
+          <p>•&nbsp;мастер-классов,</p>
+          <p>•&nbsp;воркшопов,</p>
+          <p>• прочих встреч всевозможных видов.</p>
+          <p>&nbsp; <br></p>
+          <p>О новых мероприятиях будут рассылаться уведомления. <br></p>
+        lon: 84.9800033569336
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/0/0/e/600_445305070.jpeg'
+        lat: 56.47999954223633
+      - country: LK
+        city: Colombo
+        link: 'http://www.meetup.com/React-js-Colombo/'
+        name: React.js Colombo
+        description: "This is a group for anyone interested in React.js and it's ecosystem of things. But really, it's for anyone who wants to amp up their Web-Dev skills, or looking at react to improve their productivity in building web and mobile apps. If you don't know anything about react, this might help: http://facebook.github.io/react/ In a gist, it's \"a javascript library for building user interfaces\" - originally developed and maintained by Facebook, and 100% open-source. It allows you to build fast, maintainable user interfaces for all your web, and event native mobile apps. (See: react-native) There's a ton of things you can do with it, both in the client and the server, and really fun to use and learn."
+        lon: 79.8499984741211
+        lat: 6.929999828338623
+      - country: IN
+        city: Chennai
+        link: 'http://www.meetup.com/meetup-group-zZPQtwTs/'
+        name: Chennai JavaScript Meetup
+        description: "<p>yeah pretty straight forward guys it all about web development, front end, back end, full stack and more coffee's</p>"
+        lon: 80.2699966430664
+        lat: 13.09000015258789
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/meetup-group-riqevIqL/'
+        name: Hyderabad Open Source Meetup
+        description: '<p>We are specialized in User Interface Design / Development and we would like to share / interact with others in same technologies, so we all can gain more knowledge from each other. Technologies we cover are - HTML, CSS, PhotoShop, LESS, CoffeeScript, SASS, SCSS, MongoDB, PHP, SEO, Javascript frameworks like jQuery, Backbone, Angular, NodeJS and KnockOutJS</p>'
+        lon: 78.4800033569336
+        lat: 17.399999618530273
+      - country: RU
+        city: Moscow
+        link: 'http://www.meetup.com/BeerJS-Moscow/'
+        name: BeerJS Moscow
+        description: '<p>JavaScript holy wars over craft beer. Random discussions, sharing experience, etc.<br><br>GitHub repo:&nbsp;<a href="https://github.com/beerjs/moscow">https://github.com/beerjs/moscow</a><br>Gitter room:&nbsp;<a href="https://gitter.im/beerjs/moscow">https://gitter.im/beerjs/moscow</a></p>'
+        lon: 37.619998931884766
+        lat: 55.75
+      - country: IN
+        city: Ludhiana
+        link: 'http://www.meetup.com/ludhianajs/'
+        name: ludhianajs
+        description: 'ludhianajs is a meetup group to discuss, share and learn about all things javascript. Share your JS work, a new framework, a test suite, an sdk. Whatever that is built with javascript.'
+        lon: 75.83999633789062
+        lat: 30.90999984741211
+      - country: IN
+        city: Chennai
+        link: 'http://www.meetup.com/hackerbots/'
+        name: HackerBOTs
+        description: "<p>HackerBOT is a BOT VFX sponsored group that loves to play at the intersection of web and mobile development tech (jQuery, jQuery Mobile, HTML5, CSS, Django), &nbsp;design philosophy and a handful of other technologies such as python, WebGL and OpenGL. &nbsp;<span>We enjoy many topics but more importantly we like to connect with interesting people. &nbsp;Joinees should have at least reasonable experience in web dev and be enthu. &nbsp;We'll have&nbsp;occasional&nbsp;get-togethers at BOT VFX to explore various topics. &nbsp;</span></p>"
+        lon: 80.2699966430664
+        lat: 13.09000015258789
+      - country: CN
+        city: Beijing
+        link: 'http://www.meetup.com/Frontend-Meetup-Beijing/'
+        name: Frontend Meetup Beijing
+        description: |-
+          We want to talk about all kinds of Frontend topics.
+          From CSS to Sass, from JavaScript to Nodejs, from Ionic to Cordova and everything related and in between.
+        lon: 116.4000015258789
+        lat: 39.93000030517578
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Bangalore-Full-Stack-Programmers/'
+        name: Bangalore Full Stack Programmers
+        description: '<p>This is a group for anyone interested in becoming a great full stack programmer. It is about programming at scale, about engineering discipline and productivity in development. About newer models of programming, languages, rapidly changing tech and the complete digital space.</p>'
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: CN
+        city: Beijing
+        link: 'http://www.meetup.com/Beijing-ReactJS-Meetup/'
+        name: Beijing ReactJS Meetup
+        description: '<p>Small group of people(5-10), sitting down to share anything about ReactJS. ReactJS兴趣小组分享会。</p>'
+        lon: 116.4000015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/9/a/c/600_442111148.jpeg'
+        lat: 39.93000030517578
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/Bluemix-Girls-Night-Meetups/'
+        name: "IBM Bluemix Girls' Night Meetups"
+        description: |-
+          <p>IBM Bluemix Girl's Night is a great opportunity to mix and mingle with smart women who understand technology. Join us for a one-of-a-kind event that brings together women developers in traditional IT and startup businesses. <br></p>
+          <p><b>NOTE:&nbsp; We encourage all genders to participate, if there are men who are interested in IBM Bluemix also.</b> <br></p>
+          <p>You'll have the chance to network like-minded people, gain career development and learn more about IBM PaaS Platform – Bluemix. Even you can start to build an APP of your own within a few minutes!</p>
+          <p>上海Bluemix研发团队的资深架构师 分享 Bluemix云平台 的绝佳机会， 来吧！！<br></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: 121.47000122070312
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/4/c/600_443040588.jpeg'
+        lat: 31.229999542236328
+      - country: PH
+        city: Manila
+        link: 'http://www.meetup.com/ManilaJavaScript/'
+        name: Manila JavaScript
+        description: |-
+          <p>Welcome to Manila JavaScript! Join us to share ideas, discuss trends, and assess the future of the most exciting programming language. Upcoming topics include introductory seminars, workshops, and demo days for Node.js, Meteor.js, React.js/React Native, Angular.js, D3.js, Client-Side Frameworks, ES6, etc.</p>
+          <p>Join our Facebook group at:&nbsp;<a href="https://www.facebook.com/groups/manilajs/" class="linkified">https://www.facebook.com/groups/manilajs/</a></p>
+        lon: 120.97000122070312
+        lat: 14.619999885559082
+      - country: RU
+        city: Moscow
+        link: 'http://www.meetup.com/Moscow-NodeJS-Meetup/'
+        name: Moscow NodeJS Meetup
+        description: 'We will meet time to time to discuss news, problems and share experience in NodeJS. Frontenders/backenders, russian speaking/english speaking are all welcome. Preferably it will be some quiet lounge place, where there is no need to shout loud. If you want more trash, consider going to BeerJS.'
+        lon: 37.619998931884766
+        lat: 55.75
+      - country: KR
+        city: Seoul
+        link: 'http://www.meetup.com/electron-kr/'
+        name: Electron Korea
+        description: |-
+          <p>Github 의 오픈소스인 Electron 을 사용한 소프트웨어 개발에 관심있는 개발자를 위한 미트업입니다. 저희는 <a href="http://electronkr.slack.com">Slack</a>&nbsp;을 이용해서 커뮤니케이션 하고 있스며 <a href="https://www.facebook.com/groups/808628819214318/">페이스북</a>에도 그룹이 있습니다. 저희 채널에 가입을 원하시면 <a href="https://electron-kr.herokuapp.com/">자동 초대 페이지</a>&nbsp;를 통해서 들어오시면 됩니다.&nbsp;</p>
+          <p> <br></p>
+        lon: 126.98999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/7/6/b/600_443622859.jpeg'
+        lat: 37.560001373291016
+      - country: ID
+        city: Denpasar
+        link: 'http://www.meetup.com/Mean-Stack-Bali-Meetup/'
+        name: Mean Stack Bali Meetup
+        description: This is a group for front-end and back-end web application developers and database administrators. Bali is a very conducive place to conduct workshops by the beach or rice fields. our aim is to develop our knowledge through pier-to-pier exchange. we plan to invite guest-stars at the initiative of breakthrough developments.
+        lon: 115.22000122070312
+        lat: -8.649999618530273
+      - country: HK
+        city: Hong Kong
+        link: 'http://www.meetup.com/Hong-Kong-ReactJS-Meetup/'
+        name: Hong Kong ReactJS Meetup
+        description: This is a group for anyone interested in React.js. All skills levels are welcome. I started this group because to meet other React enthusiasts. Looking forward to exploring React.js with everybody
+        lon: 114.13999938964844
+        lat: 22.270000457763672
+      - country: IL
+        city: Jerusalem
+        link: 'http://www.meetup.com/Jerusalem-Node-js-Meetup/'
+        name: Jerusalem Node.js Meetup
+        description: 'Do you want to learn about node.js? Or do you already use node.js and like to discuss it; teach it? Come join our meetup group. Node.js is event-driven JavaScript on the server: perfect for real-time web application, for IoT (Internet of things) and for any program that needs to communicate with many other programs.'
+        lon: 35.220001220703125
+        lat: 31.780000686645508
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/Shanghai-Digital-Hub/'
+        name: Shanghai Digital Hub
+        description: |-
+          <p>Shanghai Digital Hub is a Shanghai extension of Hong Kong's super popular digital meetup - <a href="http://www.meetup.com/HK-Web-Developers/" class="linkified">http://www.meetup.com/HK-Web-Developers/</a></p>
+          <p>If your passion is to learn, live, breathe experience modern web and non-web technology - let's change the shape of it in Shanghai and take on the rest of the world!</p>
+          <p>Each month, we get together over some small bites and drinks and talk about up-and coming trends and technologies. Some topics of interest are:</p>
+          <p>Scripting Trends: <br>- Angular.js <br>- React.js <br>- Coffeescript</p>
+          <p>CSS3 Animations and Filters / Shaders <br>- SASS <br>- WebGL including Three.js <br>- Tools and Approaches</p>
+          <p>Working with Yeoman (Yo, Grunt and Bower) <br>- BDD with Jasmine <br>- TDD with Mocha <br>- Getting the most of Require.js <br>- NOSQL Technologies including:</p>
+          <p>- Mongo <br>- Redis <br>- CouchDB <br>- The Freshest HTML5</p>
+          <p>- Playing with Polymer <br>- Web Sockets <br>- Web Workers <br>- Pushing boundaries of the web:</p>
+          <p>- Chrome NACL <br>- Chrome Packaged Apps <br>- Chromium and Native Web Extensions</p>
+          <p>We're always on the lookout for fellow geeks who are passionate about new tech and who'd love to share their knowledge with fellow developers.</p>
+        lon: 121.47000122070312
+        lat: 31.229999542236328
+      - country: IL
+        city: Tel Aviv-Yafo
+        link: 'http://www.meetup.com/Analytics-at-Scale/'
+        name: Analytics at Scale
+        description: 'This meetup objective is to learn about the technologies in the / needed for analytics, collection of data, analyze the data, algorithms in big data scale, monitoring and production (dev-ops) and presenting the data: Hadoop, Spark, MLlib, Hadoop with R, node.js, tableau. Including use cases, new features, case studies and best practices for deployment and tuning production environment.'
+        lon: 34.77000045776367
+        lat: 32.06999969482422
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/N8-Coders/'
+        name: N8 Coders
+        description: 'A group with members are passionate about new technologies. We are dedicated to sharing knowledge to exploring crazy-sounding ideas, new projects. There will be camps, sessions, talks, workshops from the NB coders in Shanghai. Join us if you are not afraid of challenges and changes. We covers enterprise software development including frameworks, languages, methodology and experiences such as react, react native, node, go and others.'
+        lon: 121.47000122070312
+        lat: 31.229999542236328
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/JavaScript-Meetup-Bangalore/'
+        name: JavaScript Meetup - Bangalore
+        description: 'Programming is fun! JavaScript is a popular and widely used language that we love to program in. This meetup is for passionate developers for learning and sharing tips & tricks and hacks & best practices in JavaScript. Our special focus is on new and upcoming topics in JavaScript (e.g., how to use ECMAScript 6 features). Come, let us learn and explore the amazing world of JavaScript.'
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/a/a/7/600_445475495.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/Hyderabad-nodeJS-hands-on-Boot-camp/'
+        name: Hyderabad nodeJS hands-on Boot camp
+        description: |
+          This is a group for anyone interested in learning node.js development. The meetups will be organized in a hands-on boot camp style. We will learn node.js by building real applications during the meetup.
+
+          This meetup is ideal for any one looking to learn node.js development. Experienced node.js devs are welcome to attend as well and help the boot camp participants.
+
+          Bring your own laptop to the meetup so you can get started coding node.js applications
+        lon: 78.4800033569336
+        lat: 17.399999618530273
+      - country: IN
+        city: Noida
+        link: 'http://www.meetup.com/Noida-Technology-Startups-Meetup/'
+        name: Noida Technology Startups Meetup
+        description: '<p>This is a group for anyone interested in web technologies and their applications in Start-up. All skills levels are welcome. I started this group to meet other like-minded enthusiasts. Looking forward to meet &amp;amp; learn together.</p>'
+        lon: 77.33000183105469
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/c/1/0/600_446804048.jpeg'
+        lat: 28.579999923706055
+      - country: IN
+        city: Ahmedabad
+        link: 'http://www.meetup.com/Soluble-Saturdays/'
+        name: Soluble Saturdays
+        description: 'Soluble Saturdays is an initiative by http://www.solutelabs.com to bring about an awareness in open source, knowledge sharing, new tech and ideas, startups and more!'
+        lon: 72.58000183105469
+        lat: 23.030000686645508
+      - country: IN
+        city: Noida
+        link: 'http://www.meetup.com/NCR-Just-JS/'
+        name: NCR- Just JS
+        description: This is a group for JS lovers. The primarily focus should be on knowledge sharing and sharing ideas to build a large product. Technology should be mainly concentrate on JS.
+        lon: 77.33000183105469
+        lat: 28.579999923706055
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Bangalore-Wakanda/'
+        name: Bangalore Wakanda Open Source JS Fullstack
+        description: |-
+          <p><span>This meetup is dedicated to promoting Wakanda&nbsp;Open Source JavaScript FullStack platform (<a href="https://wakanda.github.io/" class="linkified">https://wakanda.github.io/</a>). We will launch a monthly online JS development challenge. The best application developed with Wakanda Platform will receive at least $1,000 USD prize and will be showcased on Wakanda websites.</span> <br></p>
+          <p>This group is also for anyone interested in learning how to build mobile applications in 3 weeks using Javascript for both frontend and backend sides.</p>
+        lon: 77.55999755859375
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/9/c/0/600_447711648.jpeg'
+        lat: 12.970000267028809
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Rapid-Mobile-Dev-MEAN-Stack-ionic-cordova-more/'
+        name: 'Rapid Mobile Dev - MEAN Stack, ionic, cordova & more'
+        description: 'This is a group for anyone interested in rapid mobile development using cutting edge technologies like MEAN stack, ionic, Cordova and many more.'
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: LB
+        city: Beirut
+        link: 'http://www.meetup.com/Meteor-Beirut/'
+        name: Meteor Beirut
+        description: "Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started."
+        lon: 35.5
+        lat: 33.880001068115234
+      - country: IN
+        city: Chennai
+        link: 'http://www.meetup.com/nodejs-Chennai/'
+        name: Chennai Node.js
+        description: |-
+          <p>This meetup group is for Node School and Node.js events.</p>
+          <p>We would discuss about the following</p>
+          <blockquote>
+           <p>•&nbsp;Basics of Node.js</p>
+          </blockquote>
+          <blockquote>
+           <p>•&nbsp;Internals of Node.js</p>
+           <p>•&nbsp;JavaScript Language features</p>
+           <p>•&nbsp;Node.js ecosystem</p>
+           <p>•&nbsp;Node.js news</p>
+           <p>•&nbsp;Best practices</p>
+           <p>•&nbsp;Pain points</p>
+           <p>•&nbsp;Improvements to Node.js</p>
+           <p>•&nbsp;Encouraging people to contribute</p>
+          </blockquote>
+          <p>discussions may not be just limited to just these topics :)</p>
+        lon: 80.2699966430664
+        lat: 13.09000015258789
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/tech4all/'
+        name: Technology for Everybody
+        description: '<p>“This is a group for anyone interested in programming, IOT, robotics, hacking, mobility, etc. All skills levels are welcome. I started this group primarily to meet and impart knowledge to other technology enthusiasts. Looking forward to exploring the tech with everybody.”</p>'
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: IN
+        city: Panaji
+        link: 'http://www.meetup.com/goaCode/'
+        name: Goa Code
+        description: |-
+          <p>This is the perfect group for people serious about learning how to code through self-study using resources on the web.&nbsp;</p>
+          <p>This is a Javascript focused group and we will be learning how to build full stack web applications. We will progress through the following technologies:&nbsp;</p>
+          <p>•&nbsp;HTML5&nbsp;</p>
+          <p>•&nbsp;CSS3&nbsp;</p>
+          <p>•&nbsp;JavaScript&nbsp;</p>
+          <p>•&nbsp;Databases&nbsp;</p>
+          <p>•&nbsp;Git &amp;amp; GitHub&nbsp;</p>
+          <p>•&nbsp;Node.js&nbsp;</p>
+          <p>•&nbsp;React.js D3.js&nbsp;</p>
+          <p>For the complete curriculum please have a look [here]( <a href="http://www.freecodecamp.com/map" class="linkified">http://www.freecodecamp.com/map</a>).&nbsp;</p>
+          <p><span>The group is great for complete beginners. We will be learning by pair programming with someone of a similar experience level.&nbsp;</span></p>
+          <p><span>We do not provide formal instruction as you'd find in a classroom -- rather we introduce you to other beginners who are on the same path and give you the chance to work together with them on the projects laid out in our curriculum.&nbsp;</span></p>
+        lon: 73.80999755859375
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/a/e/7/600_447550983.jpeg'
+        lat: 15.5
+      - country: IN
+        city: Pune
+        link: 'http://www.meetup.com/Pune-Developers-Community/'
+        name: "Pune Developer's Community"
+        description: "Pune Developers Platform for learning and sharing technical knowledge, driven by passionate volunteers. \n­\nPune Guys, Lets collaborate together, network, learn and knowledge exchange."
+        lon: 73.83999633789062
+        lat: 18.530000686645508
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/Open-Source-Enthusiast/'
+        name: Open Source Enthusiast - Delhi
+        description: |-
+          <p>Hi everyone,</p>
+          <p>This group is all about open source technologies and methodologies, our aim is to build and nurture a community that openly communicates and help each other grow. We majorly hold meet-ups on Drupal, some of the other technologies we are interested in are NodeJS, AngularJS, PHP (various platforms), RoR, Python, and various database systems.</p>
+          <p>We have venues available for meet-ups in Delhi, Gurgaon and Goa. We are happy to help serious and relevant meet-up groups.</p>
+          <p>Cheers <br>See you at our next meet-up.</p>
+        lon: 77.20999908447266
+        lat: 28.670000076293945
+      - country: SA
+        city: Jiddah
+        link: 'http://www.meetup.com/Jeddah-Developers/'
+        name: Jeddah Developers
+        description: "<p>This is a group for anyone in Saudi Arabia who is interested in web development, apps development, web technologies, web design, e-Commerce, e-publishing, social media, etc. All skills levels are welcome. I started this group because to meet other amazing developers. Looking forward to see you join in and let's share and improve web in Arab world.</p>"
+        lon: 39.16999816894531
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/7/1/f/600_447185919.jpeg'
+        lat: 21.5
+      - country: IN
+        city: Goa Velha
+        link: 'http://www.meetup.com/Open-Source-Enthusiast-Goa/'
+        name: Open Source Enthusiast - Goa
+        description: |-
+          <p>Hi everyone,</p>
+          <p>This group is all about open source technologies and methodologies, our aim is to build and nurture a community that openly communicates and help each other grow. We majorly hold meet-ups on Drupal, some of the other technologies we are interested in are NodeJS, AngularJS, PHP (various platforms), RoR, Python, various database systems. We are also big on agile methodology (<a href="https://www.linkedin.com/groups/8460551">https://www.linkedin.com/groups/8460551</a>) irrespective of the technology you work on.</p>
+          <p>We have venues available for meet-ups in Goa, Delhi, Gurgoan and Bangalore. We are happy to help serious and relevant meet-up groups.</p>
+          <p>Cheers <br>See you at our next meet-up.</p>
+        lon: 73.87000274658203
+        lat: 15.430000305175781
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/Open-Source-Enthusiast-Bangalore/'
+        name: Open Source Enthusiast - Bangalore
+        description: "Hi everyone,\n\nThis group is all about open source technologies and methodologies, our aim is to build and nurture a community that openly communicates and help each other grow. We majorly hold meet-ups on Drupal, some of the other technologies we are interested in are NodeJS, AngularJS, PHP (various platforms), RoR, Python, and various database systems.\n\nWe have venues available for meet-ups in Bangalore, Delhi, Gurgaon and Goa. We are happy to help serious and relevant meet-up groups.\n\nCheers \nSee you at our next meet-up."
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/hyderabad-wakanda/'
+        name: Hyderabad Wakanda Open Source JavaScript FullStack
+        description: |-
+          <p>This meetup is dedicated to promoting Wakanda&nbsp;Open Source JavaScript FullStack platform (<a href="https://wakanda.github.io/" class="linkified">https://wakanda.github.io/</a>). We will launch a monthly online JS development challenge. The best application developed with Wakanda Platform will receive at least $1,000 USD prize and will be showcased on Wakanda websites.</p>
+          <p>This group is also for anyone interested in learning how to build mobile applications in 3 weeks using Javascript for both frontend and backend sides.</p>
+        lon: 78.4800033569336
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/4/4/1/600_446673857.jpeg'
+        lat: 17.399999618530273
+      - country: TH
+        city: Bangkok
+        link: 'http://www.meetup.com/Serverless-Bangkok/'
+        name: Serverless Bangkok
+        description: "<p>A group for anyone interested in building web, mobile and Internet-of-Things applications with serverless architectures using the Serverless Framework and more! We'll focus heavily on Amazon Web Services and discuss AWS Lambda as the focal point of AWS.</p>"
+        lon: 100.5
+        lat: 13.729999542236328
+      - country: IN
+        city: Bangalore
+        link: 'http://www.meetup.com/React-Native-Developers-Bengaluru/'
+        name: React Native Developers Bengaluru
+        description: "React Native is an open source Javascript framework from Facebook for building iOS or Android mobile apps. This is a community group for developers interested in React Native talks, discussions, and hack sessions. Let's Meetup"
+        lon: 77.55999755859375
+        lat: 12.970000267028809
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/Full-Stack-Mean-Ninajs/'
+        name: 'Full Stack Mean Ninajs!'
+        description: 'Group for people who want to come together with the aim of helping other beginners get a start in the MEAN stack and introducing them and mentoring them. '
+        lon: 77.20999908447266
+        lat: 28.670000076293945
+      - country: IN
+        city: Hyderabad
+        link: 'http://www.meetup.com/Hyderabad-Strongloop-MEAN-Meetup/'
+        name: 'Hyderabad MEAN Stack & Loopback Developers'
+        description: 'This a group for Engineers &amp; hustlers interested in learning MEAN Stack (Mongo, Express, Angular, Node) and build applications using enterprise frameworks like StrongLoop. This is a focussed group which meets 2nd Saturday of every month in Hyderabad. Please suggest topics for discussion, problems to solve and other innovative ideas. In every meetup we will also have a small hackathon to solve an interesting problem.'
+        lon: 78.4800033569336
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/e/2/a/5/600_447778021.jpeg'
+        lat: 17.399999618530273
+      - country: HK
+        city: Hong Kong
+        link: 'http://www.meetup.com/Sanuker-Academy/'
+        name: Sanuker Academy
+        description: "Wondering how to take the first step into the programming world? Come join our interesting coding class and explore everything about programming, mobile app and web development. Class levels ranging from beginner to intermediate and expert, with customized syllabus and cozy learning environment. Let's expand the hacker community together!"
+        lon: 114.13999938964844
+        lat: 22.270000457763672
+      - country: IN
+        city: Delhi
+        link: 'http://www.meetup.com/Geeky-Girls/'
+        name: Geeky Girls
+        description: 'Geeky girls is a group for the females who love technology. We will be learning, sharing, mentoring in technology  with each other.'
+        lon: 77.20999908447266
+        lat: 28.670000076293945
+      - country: IN
+        city: Indore
+        link: 'http://www.meetup.com/Free-Code-Camp-Indore/'
+        name: Free Code Camp Indore
+        description: "Whether you are a total beginner or well experienced, we welcome you to join us if you are interested in code pairing,enhancing your technical skills in JavaScript, JQuery, HTML, CSS, Angular.js, Node.js. and much more. This is also for anyone currently taking the Free Code Camp courses online (at www.freecodecamp.com) hoping to connect with a local campers in Indore\n\nIf you would like to host an event or have a venue in mind, feel free to reach out! "
+        lon: 75.86000061035156
+        lat: 22.719999313354492
+      - country: CN
+        city: Shanghai
+        link: 'http://www.meetup.com/Shanghai-Meteor-with-IoT-Meetup/'
+        name: Shanghai Meteor with IoT  Meetup
+        description: 'This is a team for anyone interesting in Meteor, Nodejs, IoT, Device Communction and UI , etc. All skills levels are welcome, I started this team becaues I like Javascript and any nice module，Handsome UI，and want to meet other same lovers .'
+        lon: 121.47000122070312
+        lat: 31.229999542236328
+    nodeschools:
+      - name: Amman NodeSchool
+        location: 'Amman, JO'
+        organizers:
+          - samuraik
+          - rashad612
+        repo: 'http://github.com/nodeschool/amman'
+        lat: 31.9565783
+        lon: 35.9456951
+      - name: NodeSchool Bali
+        location: 'Bali, ID'
+        organizers:
+          - LaughingSun
+        website: 'http://nodeschool.io/bali'
+        repo: 'http://github.com/nodeschool/bali'
+        lat: -8.4095178
+        lon: 115.188916
+      - name: Bangalore NodeSchool
+        location: 'Bangalore, IN'
+        organizers:
+          - abyv
+          - somesh123
+          - somsharan
+        repo: 'http://github.com/nodeschool/bangalore'
+        lat: 12.9715987
+        lon: 77.5945627
+      - name: NodeSchool Bangkok
+        location: 'Bangkok, TH'
+        organizers:
+          - jjmax75
+        website: 'http://nodeschool.io/bangkok'
+        repo: 'http://github.com/nodeschool/bangkok'
+        gitter: 'https://gitter.im/nodeschool/bangkok'
+        facebook: 'https://www.facebook.com/groups/NodeSchoolBangkok/'
+        lat: 13.7563309
+        lon: 100.5017651
+      - name: NodeSchool Cebu
+        location: 'Cebu City, PH'
+        organizers:
+          - levint
+          - keithics
+          - rollyn
+        website: 'http://nodeschool.io/cebu'
+        repo: 'http://github.com/nodeschool/cebu'
+        lat: 10.3156992
+        lon: 123.8854366
+      - name: NodeSchool Chandigarh
+        location: 'Chandigarh, IN'
+        organizers:
+          - nsena
+        website: 'http://nodeschool.io/chandigarh'
+        twitter: nodeschoolchd
+        repo: 'http://github.com/nodeschool/chandigarh'
+        lat: 30.7333148
+        lon: 76.7794179
+      - name: Chennai NodeSchool
+        location: 'Chennai, IN'
+        organizers:
+          - vikene
+        website: 'http://nodeschool.io/chennai'
+        twitter: chn_nodeschool
+        repo: 'http://github.com/nodeschool/chennai'
+        lat: 13.0826802
+        lon: 80.2707184
+      - name: NodeSchool Chiang Mai
+        location: 'Chiang Mai, Thailand'
+        organizers:
+          - RichardLitt
+        website: 'http://nodeschool.io/chiang-mai'
+        repo: 'http://github.com/nodeschool/chiang-mai'
+        lat: 18.787747
+        lon: 98.99312839999999
+      - name: 'NodeSchool Delhi-NCR '
+        location: 'Delhi-NCR, IN'
+        organizers:
+          - avin45h
+          - VibhorKukreja
+          - manoj-nama
+          - kashishgupta1990
+          - kushal-likhi
+        website: 'http://nodeschool.io/Delhi-NCR'
+        repo: 'http://github.com/nodeschool/delhi-ncr'
+        lat: 28.4179583
+        lon: 76.9104653
+      - name: Dhaka NodeSchool
+        location: 'Dhaka, BD'
+        organizers:
+          - az7arul
+          - zhdzmn
+          - riyadhalnur
+          - ishtiaque23
+        website: 'http://nodeschool.io/dhaka'
+        repo: 'http://github.com/nodeschool/dhaka'
+        lat: 23.810332
+        lon: 90.4125181
+      - name: Fukui NodeSchool
+        location: 'Fukui, JP'
+        organizers:
+          - fossamagna
+        website: 'http://nodeschool.io/fukui'
+        repo: 'http://github.com/nodeschool/fukui'
+        lat: 36.0640669
+        lon: 136.2194938
+      - name: NodeSchool Hanoi
+        location: 'Hanoi, VN'
+        organizers:
+          - hainh
+          - dominhhai
+        website: 'http://nodeschool.io/hanoi'
+        repo: 'https://github.com/nodeschool/hanoi'
+        lat: 21.0277644
+        lon: 105.8341598
+      - name: NodeSchool Ho Chi Minh - Vietnam
+        location: 'Ho Chi Minh, VN'
+        organizers:
+          - okaiji
+          - fw1065
+        website: 'http://nodeschool.io/hcmc-vietnam'
+        twitter:
+          - '@InnovQ'
+          - '@invisible_info'
+        repo: 'https://github.com/nodeschool/hcmc-saigon'
+        lat: 10.8230989
+        lon: 106.6296638
+      - name: NodeSchool Hong Kong
+        location: 'Hong Kong, HK'
+        organizers:
+          - neilnand
+          - rowlandwatkins
+          - hitchcott
+        website: 'http://www.meetup.com/HK-Web-Developers/'
+        repo: 'https://github.com/nodeschool/hong-kong'
+        lat: 22.2783151
+        lon: 114.174695
+      - name: NodeSchool Hyderabad
+        location: 'Hyderabad, IN'
+        organizers:
+          - gmkr
+        website: 'http://nodeschool.io/hyderabad/'
+        repo: 'http://github.com/nodeschool/hyderabad'
+        lat: 17.385044
+        lon: 78.486671
+      - name: IEM Kolkata NodeSchool
+        location: 'IEM, Kolkata, IN'
+        organizers:
+          - koustuvsinha
+        repo: 'http://github.com/nodeschool/iem-kolkata'
+        lat: 22.5698662
+        lon: 88.4295595
+      - name: IRN NodeSchool
+        location: 'Babol / Mazandaran, IR'
+        organizers:
+          - NIT
+        repo: 'http://github.com/nodeschool/iran'
+        lat: 36.5386629
+        lon: 52.6764543
+      - name: Isfahan NodeSchool
+        location: 'Isfahan,Isfahan, Iran'
+        organizers:
+          - ArianSotoudehMehr
+        website: 'http://nodeschools.ir'
+        repo: 'http://github.com/nodeschool/isfahan'
+        lat: 32.6546275
+        lon: 51.66798259999999
+      - name: Jakarta NodeSchool
+        location: 'Jakarta, ID'
+        organizers:
+          - aredo
+          - giosakti
+          - hafizbadrie
+          - rbudiharso
+        website: 'http://nodeschool.io/jakarta'
+        twitter: 'https://twitter.com/jakartajs'
+        repo: 'http://github.com/nodeschool/jakarta'
+        lat: -6.2087634
+        lon: 106.845599
+      - name: NodeSchool Kanpur
+        location: 'Kanpur, IN'
+        organizers:
+          - abdulqabiz
+        website: 'http://nodeschool.io/kanpur'
+        repo: 'http://github.com/nodeschool/kanpur'
+        lat: 26.449923
+        lon: 80.3318736
+      - name: Karaj NodeSchool
+        location: 'Karaj,Alborz, Iran'
+        organizers:
+          - ArianSotoudehMehr
+        website: 'http://nodeschools.ir'
+        repo: 'http://github.com/nodeschool/karaj'
+        lat: 35.8400188
+        lon: 50.9390906
+      - name: NodeSchool Lahore
+        location: 'Lahore, PK'
+        organizers:
+          - usmantahirr
+          - sheharyarn
+        website: 'http://nodeschool.io/Lahore'
+        repo: 'http://github.com/nodeschool/lahore'
+        lat: 31.55460609999999
+        lon: 74.3571581
+      - name: Malang NodeSchool
+        location: 'Malang, ID'
+        organizers:
+          - krahman
+        website: 'http://nodeschool.io/malang'
+        twitter: mlgnodeschool
+        repo: 'http://github.com/nodeschool/malang'
+        lat: -7.9666204
+        lon: 112.6326321
+      - name: Osaka NodeSchool
+        location: 'Osaka, JP'
+        organizers:
+          - martinheidegger
+          - vanx2
+          - kumatch
+          - kamiyam
+          - atuyl
+        website: 'http://nodeschool.io/osaka'
+        repo: 'http://github.com/nodeschool/osaka'
+        lat: 34.6937378
+        lon: 135.5021651
+      - name: Pune Nodeschool
+        location: 'Pune, IN'
+        organizers:
+          - adroittech
+        website: 'http://github.com/nodeschool/pune'
+        twitter: niravfaldu
+        repo: 'http://github.com/nodeschool/pune'
+        lat: 18.5204303
+        lon: 73.8567437
+      - name: NodeSchool Seoul
+        location: 'Seoul, KR'
+        organizers:
+          - xarus01
+        website: 'http://nodeschool.io/seoul/'
+        repo: 'https://github.com/nodeschool/seoul'
+        gitter: 'https://gitter.im/nodeschool/nodeschool/seoul'
+        lat: 37.566535
+        lon: 126.9779692
+      - name: Shiraz NodeSchool
+        location: 'Shiraz,Fars, Iran'
+        organizers:
+          - ArianSotoudehMehr
+        website: 'http://nodeschools.ir'
+        repo: 'http://github.com/nodeschool/shiraz'
+        lat: 29.5917677
+        lon: 52.5836982
+      - name: Singapore NodeSchool
+        location: 'Singapore, SG'
+        organizers:
+          - timoxley
+          - weilu
+          - renettarenula
+          - hongkheng
+          - soareschen
+          - vissree
+          - apraditya
+          - shioju
+          - danielmahadi
+          - eihan
+          - yzdong
+          - andrewabogado
+          - sayanee
+        website: 'http://nodeschool.io/singapore'
+        repo: 'http://github.com/nodeschool/singapore'
+        lat: 1.3553794
+        lon: 103.8677444
+      - name: Surat NodeSchool
+        location: 'Surat, GJ, IN'
+        organizers:
+          - harshjv
+          - Akshay-Jain01
+        repo: 'https://github.com/nodeschool/surat'
+        lat: 21.1702401
+        lon: 72.83106070000001
+      - name: Tabriz NodeSchool
+        location: 'Tabriz,Azarbaijan, Iran'
+        organizers:
+          - ArianSotoudehMehr
+        website: 'http://nodeschools.ir'
+        repo: 'http://github.com/nodeschool/tabriz'
+        lat: 38.094313
+        lon: 46.2614617
+      - name: Taiwan Nodeschool
+        location: Taiwan
+        organizers:
+          - leonlin14
+          - cfsghost
+          - poying
+        website: 'http://nodeschool.io/taiwan'
+        repo: 'https://github.com/nodeschool/taiwan'
+        lat: 23.69781
+        lon: 120.960515
+      - name: Tehran NodeSchool
+        location: 'Tehran,Tehran, Iran'
+        organizers:
+          - ArianSotoudehMehr
+        website: 'http://nodeschools.ir'
+        repo: 'http://github.com/nodeschool/tehran'
+        lat: 35.6891975
+        lon: 51.3889736
+      - name: NodeSchool Tokyo
+        location: 'Tokyo, JP'
+        organizers:
+          - sota0805
+          - tgfjt
+          - martinheidegger
+        website: 'http://nodeschool.io/tokyo/'
+        repo: 'https://github.com/nodeschool/tokyo'
+        gitter: 'https://gitter.im/nodeschool/nodeschool-japan'
+        lat: 35.6894875
+        lon: 139.6917064
+      - name: Vellore NodeSchool
+        location: 'Vellore, IN'
+        organizers:
+          - nikhil-kasukurthi
+        repo: 'http://github.com/nodeschool/vellore'
+        lat: 12.9165167
+        lon: 79.13249859999999
+      - name: "Xi'an NodeSchool"
+        location: "Xi'an, Shaanxi, CN"
+        organizers:
+          - howiehu
+        website: 'http://nodeschool.io/xian'
+        repo: 'https://github.com/nodeschool/xian'
+        lat: 34.341575
+        lon: 108.93977
+      - name: Yazd NodeSchool
+        location: 'Yazd,Yazd, Iran'
+        organizers:
+          - ArianSotoudehMehr
+        website: 'http://nodeschools.ir'
+        repo: 'http://github.com/nodeschool/yazd'
+        lat: 31.8974232
+        lon: 54.3568562
+  - region: Європа
+    conferences:
+      - name: NodeConf.eu
+        desc: 'Yearly NodeConf in Waterford, Ireland.'
+        link: 'http://nodeconf.eu'
+        lat: 52.2533703
+        lon: -7.0593531
+      - name: NodeConf Barcelona
+        desc: 'Yearly NodeConf in Bercelona, Spain.'
+        link: 'http://barcelona.nodeconf.com/'
+        lat: 41.3870295
+        lon: 2.1693952
+        location: 'Mobile World Centre, Barcelona, Spain'
+      - name: NodeConf Oslo
+        link: 'http://oslo.nodeconf.com/'
+        desc: Yearly Norwegian NodeConf.
+        lat: 59.8937806
+        lon: 10.6450355
+      - name: nodejsconf.it
+        link: 'http://nodejsconf.it/'
+        desc: Yearly Italian conference.
+        lat: 45.4639833
+        lon: 10.534382
+      - name: JSConf.eu
+        link: 'http://jsconf.eu'
+        desc: 'Yearly JavaScript conference in Berlin, Germany.'
+        location: 'Radial System V, Berlin, Germany.'
+        lat: 52.5102922
+        lon: 13.4286193
+    meetups:
+      - country: IT
+        city: Roma
+        link: 'http://www.meetup.com/codeinvaders/'
+        name: Codeinvaders
+        description: |-
+          <p>Meetup composto da persone&nbsp;interessate allo sviluppo software per il mondo mobile. Il gruppo si riunisce periodicamente per discutere wearables, mobile, VR, JavaScript, TDD, DevOps, ecc. ed offre talks di 25 minuti intervallati da musica, buon cibo e bevande.</p>
+          <p>Meetup with other local people who are interested in software development focusing on mobile app, rich internet applications and open source. Gather and discuss the designing and coding of web-based applications using next generation standards and frameworks like Sencha, jQuery, HTML5, CSS3, AIR, Flex, Flash Player, etc.</p>
+        lon: 12.479999542236328
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/2/4/e/600_447709742.jpeg'
+        lat: 41.900001525878906
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/londondigital/'
+        name: London Digital Design and Technology User Group
+        description: "<p>The London Design and technology user group is here to offer varied content for both designer and developers who live breath and work in the digital development space.</p>\n<p>This group is for the people who 'make' web experiences apps and games. Mainly it will be\_focussed\_on design and technology but we will also host any talks that are presented from a perspective that will be interesting to the members, so whether it be business related or strategic it will always be relevent.</p>\n<p>\_</p>"
+        lon: -0.10000000149011612
+        lat: 51.52000045776367
+      - country: GB
+        city: Cambridge
+        link: 'http://www.meetup.com/CAMDUG/'
+        name: "CAMDUG - Cambridge Developer's User Group"
+        description: |-
+          <p><strong><span>CAMDUG developer's User Group</span></strong></p>
+          <p>Camdug is a Cambridge Based community developer group who's primary goal is to connect great developers and great people (sometimes both ;-D )! Sometimes we organise some tech events, but mostly chilling out relaxed sessions where folk can meet and get to make new friends and meet with old ones.</p>
+          <p><img src="http://photos4.meetupstatic.com/photos/event/d/9/e/6/event_97555782.jpeg"></p>
+          <p> <br></p>
+          <p>Please also checkout some of the other techie meetup groups in Cambridge; I won't list them here, because each week there's a new group. Glad you've picked Cambridge as the place to hang out for a bit, and we look forward to meeting you some time, <br> <br>cheers, <br> <br>the dev guys in Cambridge.<span>&nbsp;</span></p>
+          <p>p.s. if you're looking to start your own meetup group in Cambridge, we'll help you get the message out.</p>
+        lon: 0.12999999523162842
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/3/8/e/600_433825486.jpeg'
+        lat: 52.209999084472656
+      - country: HU
+        city: Budapest
+        link: 'http://www.meetup.com/budapest-js/'
+        name: BudapestJS
+        description: "<p><strong><span>The Budapest JavaScript Meetup aka budapest.js is a</span> local community of JavaScript developers and\_enquirers living in or visiting Budapest</strong><span><strong>.</strong></span></p>\n<p><span>We're focusing on JavaScript—both server and client side technologies. If you are interested in</span> <strong>DOM scripting</strong><span>, you already wrote a bunch of plugins for</span> <strong>jQuery</strong> <span>or installed a module for</span> <strong>node.js</strong><span>, interested in large scale application development</span><span>, join us, and feel free to bring your talk as well.</span></p>\n<p><strong>Who should join the meetup?</strong></p>\n<ul>\n<li>Software engineers, developers, testers who develop with applications written in or used JavaScript</li>\n<li><span>Product managers, project managers who work with applications written in JavaScript</span></li>\n<li><span>People who would like to know why is JavaScript different from Java</span></li>\n<li>And everyone else who's interested in what's happenning in the web browser beyond Facebook</li>\n</ul>\n<p>Events are English speaking.\_<span>Food and drinks provided at meetups.</span></p>\n<p><strong>Code of Conduct</strong></p>\n<p><em>We stand for a welcoming community</em></p>\n<p>At our meetups we encourage respectful smart conversations that help improvement and inspire innovation. Sexism, racism, and being an asshole in general is not appreciated. If you do so, get prepared to be challenged by meetup members, who will probably ask what's wrong with you.</p>"
+        lon: 19.079999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/e/2/b/600_432560011.jpeg'
+        lat: 47.5099983215332
+      - country: AT
+        city: Vienna
+        link: 'http://www.meetup.com/viennajs/'
+        name: vienna.js Vienna JavaScript User Group
+        description: "<p><a href=\"http://www.viennaJS.org\">viennaJS.org</a> is all about JavaScript and sharing your experience! We love client- and server-side JavaScript of all flavors! Whether you use Prototype, jQuery, script.aculo.us, Dojo, Ext.js, Node.js, CommonJS, YUI, or just your own magic creation– feel welcome.</p>\n<p>We've a monthly meetup (every last Wednesday of the month) where we have short presentations on JavaScript topics in English– everyone is welcome to join in and do talks and show us new stuff.</p>\n<p>Whether you yet need to code your first line of JavaScript, or a world-renown ninja — join us!</p>\n<p>For announcements also follow us on Twitter at\_<a href=\"http://twitter.com/viennajs\" target=\"_blank\">http://twitter.com/viennajs</a></p>"
+        lon: 16.3700008392334
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/c/c/0/600_200076032.jpeg'
+        lat: 48.220001220703125
+      - country: 'NO'
+        city: Oslo
+        link: 'http://www.meetup.com/NodeJSOslo/'
+        name: Node.js Oslo
+        description: |-
+          <p><span>A meetup group for people interested in</span> <a href="http://www.nodejs.org">node.js</a>&nbsp;in Oslo.</p>
+          <p><span>Keep up with all our activities on <a href="http://nodejsoslo.github.io/">http://nodejsoslo.github.io/</a></span></p>
+        lon: 10.75
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/0/2/6/600_448044614.jpeg'
+        lat: 59.90999984741211
+      - country: DE
+        city: Hamburg
+        link: 'http://www.meetup.com/hamburg-js/'
+        name: HH.js
+        description: |-
+          <p>Welcome to Hamburg.js – the JavaScript Meetup in Hamburg.</p>
+          <p>We try to meet monthly to talk about all things JavaScript. Presentations wanted. Get in touch on here or via <a href="http://twitter.com/hhjs">@hhjs</a>.</p>
+          <p><a href="https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Number"><img src="http://photos1.meetupstatic.com/photos/event/a/7/a/9/event_19302921.jpeg" style="max-height : 700px ; max-width : 700px ; margin : 5px ; float : left"></a></p>
+        lon: 10
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/3/8/2/600_111917282.jpeg'
+        lat: 53.54999923706055
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/The-Digital-Pond/'
+        name: The Digital Pond
+        description: '<p>The world is going digital and so is business! The Digital Pond is an event series and meetup community welcoming all those from a digital discipline and those wanting to learn more or build networks with those within the industry. So whether you are an entrepreneur, business owner, website designer, UX (user-experience) designer, online marketer, web developer or social media guru, enter the pond and meet like-minded professionals.</p>'
+        lon: -0.10000000149011612
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/3/c/8/600_71737832.jpeg'
+        lat: 51.52000045776367
+      - country: SE
+        city: Stockholm
+        link: 'http://www.meetup.com/sthlm-js/'
+        name: sthlm.js
+        description: |-
+          <p>Hi! Great that you found us! We're all about discussing where JavaScript is heading. Even if its the latest browser tech, hard core node.js programming or why not a cool Emscripten project?</p>
+          <p>Do you want to host a meetup? Please fill in the <a href="https://docs.google.com/forms/d/1_kS4ilvSDQTO5OGp6f6J0teLLVhjVCpDpu5X9esSadc">hosting form</a>!</p>
+          <p>Would you like to speak at a meetup? We aim for everyone who wants to speak to get the chance as soon as possible! Fill in this <a href="https://docs.google.com/forms/d/1c-BvVhWn75HpIDrsN-rXPztkphDEL2mJLCb5SEAdtfI">speaking interest form</a>.</p>
+          <p>Do you have a great idea for a speaker? We have a form for <a href="https://docs.google.com/forms/d/14cGOarfPwmiKPEoyJte-Moj7c3jnDcNlYW2-crKHjOA">speaker ideas</a>!</p>
+          <p>Do you have this awesome idea we don't have a form for? Contact the organizers!</p>
+        lon: 18.06999969482422
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/d/9/600_446762009.jpeg'
+        lat: 59.33000183105469
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/London-CoffeeScript/'
+        name: "London CoffeeScript Users' Group"
+        description: '<p>This is a group for all software developers who are currently using, or who want to become more involved with, CoffeeScript.</p>'
+        lon: -0.07999999821186066
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/d/e/600_85082782.jpeg'
+        lat: 51.52000045776367
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/amsnode/'
+        name: The Amsterdam Node Meetup Group
+        description: "<p>For anyone interested in Node.js we like to get you all together and share each other's experiences. We plan to have 1 or 2 short presentations every meetup, which will range from introductions to Node, to the philosophy of/behind Node, and actual companies/startups that use Node.js. Feel free to come, whether you're a Node.js veteran with decades of javascript experience or just have an interest to see what happens in Node.js land. And yes, beers will be available.</p>"
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/4/1/c/600_106221532.jpeg'
+        lat: 52.369998931884766
+      - country: GB
+        city: Bristol
+        link: 'http://www.meetup.com/BristolJS/'
+        name: Bristol JS
+        description: |-
+          <p>document.write("Hello World".blink())</p>
+          <p> <br></p>
+          <p>&lt;a href="<a href="http://www.bristoljs.org" class="linkified">http://www.bristoljs.org</a>"&gt;www.bristoljs.org&lt;/a&gt;</p>
+        lon: -2.609999895095825
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/1/1/b/600_440884379.jpeg'
+        lat: 51.439998626708984
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/XMPP-UK-Meetup/'
+        name: XMPP UK Meetup
+        description: '<p>This group has been set up to bring together the XMPP/realtime community in London.</p>'
+        lon: -0.09000000357627869
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/4/0/2/600_214085122.jpeg'
+        lat: 51.52000045776367
+      - country: DE
+        city: Münster
+        link: 'http://www.meetup.com/monster-tech-tales-software-engineering-user-group-muenster/'
+        name: Monster Tech Tales
+        description: |-
+          <p>"Monster Tech Tales" was originally founded as a Ruby on Rails user group called "Monster on Rails". Over time, the focus changed towards a technology- and development-centered user group that offers a broad variety of different topics, such as (Web-)Technologies, (Web-)Frameworks, Software Architecture, Design Patterns, (No)-SQL DBMS, Programming Paradigms, Agile Development and many more&nbsp;. Usually we meet monthly at the Zweitag office.</p>
+          <p> <br></p>
+        lon: 7.619999885559082
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/1/4/0/600_148528992.jpeg'
+        lat: 51.959999084472656
+      - country: DE
+        city: Mannheim
+        link: 'http://www.meetup.com/node-js-Mannheim/'
+        name: node.js Mannheim
+        description: "<p>Is anyone else using node.js in Mannheim, Frankfurt, Karlsruhe or the Rhein-{Neckar,Main}-Area in general? If so, let's have a beer, talk about projects and share knowledge about this awesome piece of technology! Benutzt noch jemand node.js in Mannheim, Frankfurt, Karlsruhe oder dem Großraum Rhein-Neckar/Rhein-Main? Dann lasst uns ein Bier trinken, über die Projekte sprechen und Wissen zu diesem außerordentlichen Stück Software austauschen!</p>"
+        lon: 8.470000267028809
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/2/e/c/600_151237612.jpeg'
+        lat: 49.5
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/AmsterdamJS/'
+        name: AmsterdamJS
+        description: "<p>Calling all JavaScript developers in Amsterdam!</p>\n<p>AmsterdamJS is back and more alive than ever. We are hoping to create a big JavaScript community in Amsterdam that reflects the vibrant tech scene of the city.</p>\n<p>Every month we organize a meetup with amazing talks, great developers and snacks and drinks to go with it. If you want to give a talk about your project, or whatever interests you that is related to JavaScript, just give us a shout!</p>\n<p>\_</p>\n<p><strong>Do you want to speak at AmsterdamJS?</strong></p>\n<p>We'd love to know what you are passionate about! Speaking at AmsterdamJS is easy, just fill up the following form and we'll take a look at it:</p>\n<p>https://docs.google.com/forms/d/1JqfozjbITrOMN0Eq1886nS8gjgGmZg5ZQBFSflQ7NBU/viewform</p>"
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/a/0/0/600_158110752.jpeg'
+        lat: 52.369998931884766
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/Belgian-node-js-User-Group/'
+        name: Belgian node.js User Group
+        description: '<p>This node.js user group gathers the belgian node.js developers so we can improve our skill set and build kick-ass amazing apps.</p>'
+        lon: 4.329999923706055
+        lat: 50.83000183105469
+      - country: FR
+        city: Bordeaux
+        link: 'http://www.meetup.com/BordeauxJS/'
+        name: BordeauxJS
+        description: '<p>User group JavaScript à Bordeaux : réunions, discussions et live coding entre gens en asynchrone.</p>'
+        lon: -0.5799999833106995
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/e/b/2/600_170804722.jpeg'
+        lat: 44.84000015258789
+      - country: GB
+        city: Cambridge
+        link: 'http://www.meetup.com/JavaScript-Cambridge/'
+        name: 'JavaScript & NodeJS Cambridge'
+        description: |-
+          <p>It's time Cambridge woke up to the power of JavaScript &amp; NodeJS!</p>
+          <p>We are a friendly group who meet monthly to discuss the JavaScript and NodeJS ecosystem. &nbsp;Each month we have one or two talks by guest speakers or our own members.</p>
+          <p>All skill levels very welcome!</p>
+        lon: 0.14000000059604645
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/c/1/b/600_432579963.jpeg'
+        lat: 52.20000076293945
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Couchbase-France/'
+        name: Couchbase France
+        description: '<p>Un groupe pour se retrouver entre passionnés de Couchbase et NosQL en général...</p>'
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/7/a/f/600_438186063.jpeg'
+        lat: 48.86000061035156
+      - country: SE
+        city: Stockholm
+        link: 'http://www.meetup.com/Instrumenthack/'
+        name: 'Instrumenthack!'
+        description: "<p>A group dedicated to some of the best things in life: art, code, audio and hardware. We will have meetupsmet at Plan8's studios in the old fire station on södermalm. We will have some hardware and a lot of instruments to hack available.</p>\n<p>The idea of this group is to come up with prototypes using instruments and maybe also some of the exciting audio API out there, such as Web Audio, Echonest, Spotify, Last FM etc.\_Basically everything related to interactive audio. That and of course to meet other interested in the same thing.</p>\n<p>Sounds like fun, right?!</p>"
+        lon: 18.06999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/0/4/c/600_209604652.jpeg'
+        lat: 59.33000183105469
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/backend/'
+        name: Backend Web Berlin
+        description: "<p>Calling all Developers who works hard on amazing features that stays behind the visible face of various web projects. If you want to share your huge experience or just learn some new stuff, you are welcomed to participate.</p> \n<p>The idea is not to rely on one certain programming language or technology, since in most projects we are using many different languages, technologies and solutions.</p> \n<ul> \n <li><span>What to become a sponsor? </span><a href=\"http://www.meetup.com/backend/pages/Sponsors_request/\">Read more here</a><span>.</span></li> \n <li><span>Tweet about us with hashtag </span><span>#BackendWebBerlin</span></li> \n <li><span>Follow us on </span><a href=\"https://plus.google.com/u/0/b/109431419613697854313/109431419613697854313/posts\">Google+</a></li> \n</ul>"
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/1/1/2/600_196092562.jpeg'
+        lat: 52.52000045776367
+      - country: EE
+        city: Tallinn
+        link: 'http://www.meetup.com/Node-js-Tallinn/'
+        name: Node.js Tallinn
+        description: "<p>// node.js developers and hackers Tallinn meetup group</p>\n<p><span>Goal of the group is to engage Node.js developers community and spread the word about Node.js in Estonia.</span> Explore what Node.js technology can do and <span>network with fellow Node.js developers, discuss about Node.js projects, experience, hacks and tools.</span></p>\n<p>Who should join?</p>\n<p>Node.js and JavaScript programmers, enthusiasts and hackers; Technologists interested in event based I/O; \_Start-ups / organisations evaluating Node.js and related technologies.\_<br>\n\n<br>\n\n What to expect?<br>\n\n regular meet-ups, networking, hackathons, demos, sessions, snacks &amp; drinks.</p>"
+        lon: 24.739999771118164
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/4/7/0/600_196505232.jpeg'
+        lat: 59.439998626708984
+      - country: TR
+        city: Istanbul
+        link: 'http://www.meetup.com/Istanbul-Hackers/'
+        name: Istanbul Coders
+        description: "<p><span>If you believe in Software Craftsmanship, Agile movement, DevOps movement, Continuous Delivery, and turning your ideas into steady startups, this is the right group for you. I'll try to organize at least one meetup, potentially more meetups every week starting February '13. There will be plenty of activities in the future from live-coding sessions to one-day conferences, from various tutorials sessions to heated community discussions.</span></p>\n<p>Please find more info on <a href=\"http://istanbulcoders.org\">http://istanbulcoders.org</a> or <a href=\"http://github.com/istanbul-coders\">http://github.com/istanbul-coders</a></p>\n<p>If you believe in these values and you think you can also contribute, please come and support our group.</p>\n<p>-----------------</p>\n<p><span>Bu grup, bunlari baslatmanin ve ileride daha bir cok grubun kurulmasina vesile olacak cabalarin bir baslangici olmasini hedefleyerek baslattigim bir calisma. Eger siz de Yazilim Sanatkarligina, Cevik Yazilim Gelistirmeye, Gelistirici Operasyon hareketine, Durmaksizin Dagitima, ve fikirlerinizi kendi kendine yeten kobilere donusturmeye inaniyorsaniz, dogru yerdesiniz. Ben gucum yettigince Subat '13 ten sonra her hafta en az bir organizasyon yapmaya calisacagim. Su an icin planladigim bir suru temel aktivite var, canli kodlamalar dan, bir gunluk konferanslara, egitimlerden uretken tartismalara kadar bir cok aktivite.</span></p>\n<p>Lutfen daha fazla bilgi icin\_<a href=\"http://istanbulcoders.org/\">http://istanbulcoders.org</a> <span>veya</span> <a href=\"http://github.com/istanbul-coders\">http://github.com/istanbul-coders</a> sitesini ziyaret edin.</p>\n<p>Siz de eger bu degerlere inaniyorsaniz, iciniz kipir kipir oluyorsa, lutfen siz de katilin ve grubumuza destek verin.</p>\n<p>Sincerely / Saygilarimla,</p>\n<p>-Isa</p>"
+        lon: 28.959999084472656
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/a/1/a/600_309347642.jpeg'
+        lat: 41.0099983215332
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/Ember-js-Munich/'
+        name: Ember.js Munich
+        description: '<p>The Munich <a href="http://emberjs.com">Ember.js</a> Meetup. We meet roughly every 2 months.</p>'
+        lon: 11.579999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/1/0/6/600_441256646.jpeg'
+        lat: 48.13999938964844
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/Munich-Node-js-User-Group/'
+        name: Munich Node.js User Group
+        description: |-
+          <p>MNUG is a user group of server-side JavaScript users (amateurs, journeymen and hackers). We meet every 2nd month to discuss topics on NodeJS, server-side JavaScript and related technologies like MongoDB and CouchDB. Meetings take place (almost) on each first Thursday at 19:00 on different locations. We established in October 2011 in Munich.</p>
+          <p>Follow us on <a href="https://twitter.com/munichnug">Twitter</a></p>
+        lon: 11.579999923706055
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/6/d/7/6/600_201268022.jpeg'
+        lat: 48.13999938964844
+      - country: SE
+        city: Stockholm
+        link: 'http://www.meetup.com/Stockholm-Node-js/'
+        name: Stockholm Node.js
+        description: "<p>This group is for anyone interested in Node.js. We will share experiences on using or developing npm libraries and best practices. Let us know if you have something Node.js related you'd like to share or come with suggestions on topics that you want to learn about.</p>"
+        lon: 18.06999969482422
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/d/3/a/600_200448442.jpeg'
+        lat: 59.33000183105469
+      - country: DE
+        city: Hamburg
+        link: 'http://www.meetup.com/Riak-Hamburg/'
+        name: 'Riak Hamburg!'
+        description: '<p>A Hamburg based meet-Up for those interested in Riak, distributed systems, NoSQL, and app development.</p>'
+        lon: 10
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/2/2/600_200643362.jpeg'
+        lat: 53.54999923706055
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/Meteor-Berlin/'
+        name: Meteor Berlin
+        description: "<p>Meet other developers using <a href=\"http://meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/c/9/8/600_398355512.jpeg'
+        lat: 52.52000045776367
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/Meteor-Munich/'
+        name: Meteor Munich
+        description: |-
+          <p>&lt;p&gt;Meet other developers using &lt;a href="</p>
+          <p><a href="http://meteor.com/">http://meteor.com</a></p>
+          <p>"&gt;Meteor&lt;/a&gt;. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.&lt;/p&gt;</p>
+        lon: 11.579999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/5/9/1/600_438294673.jpeg'
+        lat: 48.13999938964844
+      - country: ES
+        city: Madrid
+        link: 'http://www.meetup.com/AngularJS_Madrid/'
+        name: AngularJS Madrid
+        description: '<p>Grupo de interés sobre AngularJS localizado en Madrid</p>'
+        lon: -3.7100000381469727
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/7/4/9/600_436590537.jpeg'
+        lat: 40.41999816894531
+      - country: IT
+        city: Torino
+        link: 'http://www.meetup.com/Meteor-Italia/'
+        name: Meteor Italia
+        description: '<p><span style="font-size : medium">Un luogo di incontro, di confronto e di studio per web developer interessati al framework Meteor.js, ma in generale per tutti gli appassionati di sviluppo applicazioni web HTML5 e Javascript client-side e server-side.</span></p>'
+        lon: 7.670000076293945
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/4/2/2/600_424897922.jpeg'
+        lat: 45.04999923706055
+      - country: IT
+        city: Torino
+        link: 'http://www.meetup.com/Torino-JS/'
+        name: Torino JS
+        description: '<p>Javascript, the most misunderstood language of all time ;-)</p>'
+        lon: 7.670000076293945
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/1/6/2/600_209532642.jpeg'
+        lat: 45.04999923706055
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Stripe-London/'
+        name: 'The Stripe Meetup Group: London'
+        description: '<p>Meet the Stripe team and members of the Stripe community in London.</p>'
+        lon: -0.12999999523162842
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/6/9/e/600_218494462.jpeg'
+        lat: 51.5099983215332
+      - country: SI
+        city: Ljubljana
+        link: 'http://www.meetup.com/Ljubljana-JavaScript-User-Group/'
+        name: Ljubljana JavaScript User Group
+        description: '<p>So many JavaScript programmers in Ljubljana, so few events dedicated to this lovely thing many people love to hate ... We should fix that.</p>'
+        lon: 14.510000228881836
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/1/e/a/600_343849642.jpeg'
+        lat: 46.060001373291016
+      - country: IT
+        city: Napoli
+        link: 'http://www.meetup.com/GDGCampania/'
+        name: GDG Campania
+        description: "<p><span>Il Google Developer Group Campania è la community ufficiale di Google più attiva d'Italia e lavora costantemente con le tecnologie Google, con l'obiettivo di creare un club d'eccellenza in cui sviluppatori, aziende, studenti e tutti gli appassionati di queste tecnologie possano ritrovarsi per condividere discussioni, raccogliere esperienze, organizzare eventi.</span></p>"
+        lon: 14.25
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/5/f/7/600_442290199.jpeg'
+        lat: 40.84000015258789
+      - country: GB
+        city: Leeds
+        link: 'http://www.meetup.com/LeedsJS/'
+        name: Leeds JS
+        description: "<p>Leeds JS is a user group in that meets in Leeds on the last Wednesday of every month. Join us for free food, a beer, prizes and to meet a great bunch of people.</p> \n<p>The goal of this user group is to form a community for Javascript in Leeds. Most technical companies now have to use javascript in some way and the demand is growing with every new framework and NodeJS release. We want to be a place were any developer can come for advice, to show off what they're working on or to just talk about the news (and drama) in the wider Javascript community.</p> \n<p>This user group is for the community! If you ever want to pitch in or have an idea just get in touch via twitter https://twitter.com/leedsjs</p> \n<p>Things to expect from this meet up:</p> \n<ul> \n <li>Interactive demos for attendees - make sure to charge your smartphone!</li> \n <li>Noobs, Intermediates, Experts, Gurus...everyone is welcome.</li> \n <li><span>Splendid prizes up for grabs each meet.</span></li> \n <li>A say in the direction of the group and what talks we put on.</li> \n <li>Conference discounts available.</li> \n</ul> \n<p><span>Good stuff, we hope to see you at the next meet =)</span></p> \n<p><span><span>We also now have a website and blog running on the NodeJS blogging engine Ghost. Check it out at leedsjs.com</span><br> </span></p> \n<p><strong>Please note the group is intended for developers looking to expand their knowledge in a recruiter free zone only so whilst interest from recruitment consultants is nice we have a no recruiters policy.</strong></p>"
+        lon: -1.5399999618530273
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/c/5/9/600_433591833.jpeg'
+        lat: 53.790000915527344
+      - country: 'NO'
+        city: Bergen
+        link: 'http://www.meetup.com/BergenJS/'
+        name: BergenJS
+        description: '<p>BergenJS exists to build a stronger developer community in Bergen, specifically in the areas of modern web technologies.</p>'
+        lon: 5.340000152587891
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/f/3/f/600_438212575.jpeg'
+        lat: 60.380001068115234
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/JavaScript-MVC-Meetup-Amsterdam/'
+        name: JavaScript MVC Meetup Amsterdam
+        description: |-
+          <p>We are a group of <strong>JavaScript enthusiast</strong> specifically interested in JavaScript <strong>MVC frameworks</strong>. Every JS developer has more or less the same questions when setting up a new web application.</p>
+          <ul>
+          <li><span>Which framework to choose?</span></li>
+          <li><span>What problems did other people have to tackle?</span></li>
+          <li><span>When not to choose a particular framework or tool?</span></li>
+          <li><span>etc.</span></li>
+          </ul>
+          <p><span>With this group we want to organize a nice evening every month, to discuss the pros and cons of various front-end JS frameworks and share some real life experience with the community.</span></p>
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/d/a/600_227101242.jpeg'
+        lat: 52.369998931884766
+      - country: NL
+        city: Groningen
+        link: 'http://www.meetup.com/Functional-Groningen/'
+        name: Functional Groningen
+        description: |-
+          <p>Functional Groningen focuses on the creation of a functional programming community in the northern of the Netherlands.</p>
+          <p><a href="http://functional-groningen.nl/">http://functional-groningen.nl/</a></p>
+        lon: 6.570000171661377
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/5/e/e/600_226637902.jpeg'
+        lat: 53.22999954223633
+      - country: SE
+        city: Göteborg
+        link: 'http://www.meetup.com/gbgnodejs/'
+        name: 'Göteborg, Node.js'
+        description: |-
+          <p><span>We are about spreading the knowledge and best practices of Node.js.</span></p>
+          <p><span>There are &gt;29k npm modules at time of writing, the node community is thriving!</span></p>
+          <p><span>If you use Node.js or even have a beginner's interest, come join us and be a part of the latest and greatest from Node.</span></p>
+          <p><span style="font-size : medium">;</span></p>
+        lon: 12.010000228881836
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/6/b/8/600_376190872.jpeg'
+        lat: 57.720001220703125
+      - country: SE
+        city: Stockholm
+        link: 'http://www.meetup.com/Sthlm-Viaplay-Tech-Group/'
+        name: Viaplay Tech Group
+        description: '<p>The Sthlm Viaplay Tech Group brings people together to talk about web development, online video streaming and other interesting stuff.</p>'
+        lon: 18.06999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/4/a/d/600_440601677.jpeg'
+        lat: 59.33000183105469
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/AngularJS-Paris/'
+        name: AngularJS Paris
+        description: "<p>If you love AngularJS and live in or around Paris, join us!</p>\n<p>Proposez vos sujets :\_<a href=\"http://goo.gl/JQyNWi\">h<span>ttp://goo.gl/JQyNWi</span></a></p>"
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/7/8/8/600_424158312.jpeg'
+        lat: 48.86000061035156
+      - country: DK
+        city: Copenhagen
+        link: 'http://www.meetup.com/Copenhagen-Node-js-Hackathon/'
+        name: Copenhagen Node.js Hackathon
+        description: "<p>Do you want to meet, share knowledge and work with other node.js hackers in Copenhagen? We are a group of node developers from Copenhagen who want to collaborate on cool projects. It doesn't matter if you are new to node or a pro. Our goal is that everybody should be able to get something out of the hackathons. You are free to work on your own projects or team up with others - just show up and have fun!</p>"
+        lon: 12.569999694824219
+        lat: 55.68000030517578
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Nodejs-Paris/'
+        name: Node.js Paris
+        description: |-
+          <p>Node.js + Javascript + Paris = ♥</p>
+          <p>Nous sommes un groupe de développeurs enthousiastes, spécialisés en Javascript et plus précisément avec Node.js.</p>
+          <p>Les nouvelles technologies web et mobiles nous passionnent (du stockage et de l'exploitation de données côté serveur jusqu'au rendu final visualisé par l'utilisateur).</p>
+          <p>Nous nous réunissons régulièrement pour échanger nos découvertes (bibliothèques npm, outils de dev, frameworks alternatifs…), nos compétences, les meilleurs pratiques du milieu (méthodes agiles, tests…), mais aussi à propos de l'écosystème du développeur (emploi, entrepreneuriat…).</p>
+          <p>Site web : <a href="http://nodejsparis.fr/" class="linkified">http://nodejsparis.fr/</a></p>
+          <p>Hashtag twitter : #nodejsparis</p>
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/e/3/f/600_446064127.jpeg'
+        lat: 48.86000061035156
+      - country: PL
+        city: Kraków
+        link: 'http://www.meetup.com/Escape-from-dev-null-Poland/'
+        name: Escape from /dev/null Poland
+        description: Escape from /dev/null is a series of different and inspiring programming competitions. Teams of up to three people navigate a web-based science-fiction or fantasy board-game to race the other teams and win prizes by solving thematic programming challenges.
+        lon: 19.959999084472656
+        lat: 50.060001373291016
+      - country: FR
+        city: Marseille
+        link: 'http://www.meetup.com/Disruptive-technologies-in-Planet-Marseille/'
+        name: 'Disruptive technologies in Planet Marseille !'
+        description: |-
+          <p>Nous sommes un groupe de hacker/maker enthousiastes.</p>
+          <p>Les nouvelles technologies informatiques et leurs impacts sur notre monde nous passionnent :</p>
+          <ul>
+          <li><span>le cloud - amazon, heroku, ... cloud9, nitrous.io, coderio,...</span></li>
+          <li><span>le bigdata - hadoop &amp; storm</span></li>
+          <li><span>les nouvelles architectures web&amp; mobile - javascript (node.js), temps réel, NoSQL (redis, mongo, neo4j), webrtc</span></li>
+          <li><span>le monde merveilleux de l'électronique via les IoT - arduino &amp; Raspberry</span></li>
+          </ul>
+          <p><span>Nous nous réunissons régulièrement (1 fois par mois) pour échanger nos découvertes (bibliothèques, outils de dev, frameworks alternatifs, cloud paas node.js, …), nos compétences, les meilleurs pratiques du milieu (méthodes agiles, tests…), mais aussi pour discuter de l'écosystème sur la région (emploi, entrepreneuriat, social, action citoyenne, open data, etc…).</span></p>
+          <p>twitter : @<span style="font-size : small">Marseilledisrup</span></p>
+        lon: 5.369999885559082
+        lat: 43.310001373291016
+      - country: GB
+        city: Edinburgh
+        link: 'http://www.meetup.com/AngularJS-Edinburgh/'
+        name: AngularJS - Edinburgh
+        description: 'AngularJS meets are the third Thursday of every month at Silicon Walk in Edinburgh - 25 Greenside Place, Edinburgh.  Come along and talk all things Angular.  Talk about what your building and chat with likeminded developers over a beer or two.'
+        lon: -3.190000057220459
+        lat: 55.959999084472656
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/geek2geek/'
+        name: Geek2Geek - Berlin Tech Talk
+        description: |-
+          <p>Geek2Geek is a monthly Berlin Tech Talk. Our goal is to bring software developers with a diverse background together. We noticed that the coding community is often isolated, meaning that PHP devs. are only going to PHP UG's and Java devs. solely to Java UG's</p>
+          <p>However, we believe that we could achieve great things if we connect. If you're a open source developer, start-up, techie, or geek using Java, Ruby, Python, Node.JS, PHP, JavaScript, R or Clojure, this group is for you!<br>
+
+          <br>
+
+           Join us to be one step ahead and think outside the box. We're looking forward to meet you!<br>
+
+          <br>
+
+          </p>
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/d/6/0/600_258255712.jpeg'
+        lat: 52.52000045776367
+      - country: PT
+        city: Lisbon
+        link: 'http://www.meetup.com/require-lx/'
+        name: "require('lx')"
+        description: '<p>A meetup group for JavaScript developers, lovers, enthusiasts and explorers in Lisbon. Server-side and client-side. Talks and code shows, some day even hackathons.</p>'
+        lon: -9.140000343322754
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/a/0/e/600_323635822.jpeg'
+        lat: 38.720001220703125
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/AngularJS-Belgium/'
+        name: AngularJS Belgium
+        description: "<p>Let's meet together for some discussions about the awesome AngularJS framework! I started this group to meet the belgian AngularJS community and share together our experience. Propose a talk here:&nbsp;<a href=\"http://goo.gl/forms/U1UBFxFYni\">http://goo.gl/forms/U1UBFxFYni</a></p>"
+        lon: 4.329999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/3/e/c/600_266274252.jpeg'
+        lat: 50.83000183105469
+      - country: ES
+        city: Madrid
+        link: 'http://www.meetup.com/Node-js-Madrid/'
+        name: Node.js Madrid
+        description: |-
+          <p>En este grupo hablamos de Node.js y sus aplicaciones, siempre con un enfoque práctico. Nos reunimos una vez al mes para vernos las caras, y para escuchar charlas de alguien de la comunidad... por ejemplo tú. Actualmente estamos enlazando una charla introductoria y otra avanzada, para llegar a todos los públicos.</p>
+          <p>Node.js es una plataforma robusta y escalable para servir aplicaciones web, basada en JavaScript. Grandes empresas como Walmart, PayPal o LinkedIn se han lanzado a la piscina y están migrando sus webs; y muchas otras empresas (extranjeras y españolas) usan Node.js en producción.</p>
+          <p>¿Tienes algo que contar? ¡Estamos interesados! Aceptamos propuestas en GitHub: <a href="https://github.com/NodeJsMadrid/talks" class="linkified">https://github.com/NodeJsMadrid/talks</a>. Nos regimos por este <a href="https://github.com/NodeJsMadrid/talks/blob/master/codigo-conducta.md">código de conducta</a>.<br></p>
+          <p>Síguenos en Twitter: <a href="https://twitter.com/NodeJsMadrid" class="linkified">https://twitter.com/NodeJsMadrid</a></p>
+        lon: -3.7100000381469727
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/4/7/0/600_377645232.jpeg'
+        lat: 40.41999816894531
+      - country: PL
+        city: Rzeszów
+        link: 'http://www.meetup.com/Rzeszow-JavaScript-Developers/'
+        name: Rzeszów JavaScript Developers
+        description: "<p>This is a group for <strong>anyone</strong> interested in <strong>JavaScript</strong>, <strong>SSJS</strong>, <strong>HTML5</strong> and mind blow <strong>startups</strong>. All skills levels are welcome. I started this group for everyone who wants to meet other enthusiasts, share experience and views, find out what's new out there, create a starup or just to have a beer with other geeks. <strong>Feel free to propose an event, presentation or</strong> <span><strong>codefest</strong>.</span></p>\n<p><span>Cheers!\_Follow us on twitter <a href=\"https://twitter.com/rz_js\">@rz_js</a></span></p>"
+        lon: 22
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/3/5/2/600_270170002.jpeg'
+        lat: 50.04999923706055
+      - country: 'NO'
+        city: Oslo
+        link: 'http://www.meetup.com/TechShock/'
+        name: TechShock
+        description: '<p>TechShock is a usergroup for web and mobile developers. While our group is broad and covers a lot of technologies, our individual meetups will be narrowed down to more specific areas of interest. Our meetups will be held in English, and there will be social events after each meetup for those interested in continuing the discussion over a beer or two.</p>'
+        lon: 10.75
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/5/2/c/600_305754572.jpeg'
+        lat: 59.90999984741211
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/NodeBots-of-London/'
+        name: NodeBots of London
+        description: |-
+          <p>We'll meet up in London and hack on Arduinos, Rasberry Pis, quadcopters, robots, and any other gizmos that need more input.</p>
+          <p>Continuing in the spirit of the international NodeBots Day event, this is not a hackathon, there will be no prizes. It's about spending a day in an amazing workshop with good people and tinkering, hacking and generally putting tools where hardware would rather you didn't. Please remember to bring your laptop, Arduino, a grab bag of components and ideas. Broken toys, Raspberry Pis, and circuit bent synths also encouraged.</p>
+        lon: -0.07999999821186066
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/8/d/c/600_278538652.jpeg'
+        lat: 51.470001220703125
+      - country: 'NO'
+        city: Oslo
+        link: 'http://www.meetup.com/Ember-js-Oslo/'
+        name: Ember.js Oslo
+        description: This group is intended to serve the Norwegian Ember.js community with meetings and activities related to Ember.js development and technologies.
+        lon: 10.75
+        lat: 59.90999984741211
+      - country: AT
+        city: Linz
+        link: 'http://www.meetup.com/stahlstadt-js/'
+        name: stahlstadt.js
+        description: "<p>Let's talk JS. In se Stahlstadt.</p>"
+        lon: 14.289999961853027
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/6/b/6/600_279599062.jpeg'
+        lat: 48.310001373291016
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/AngularJS-Barcelona/'
+        name: AngularJS Barcelona
+        description: '<p>We love AngularJS, we love the way it helps us build better web applications with less effort and we would love to meet other AngularJS developers in the Barcelona area so that we can discuss our approaches, ways, etc. with them.</p>'
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/f/a/a/600_335273162.jpeg'
+        lat: 41.400001525878906
+      - country: ES
+        city: Málaga
+        link: 'http://www.meetup.com/techmalaga/'
+        name: TechMalaga
+        description: "<p>Node Sol nacio con la mision de conectar apasionados del Node en Málaga. Hemos hecho varias charlas y workshops y constantemente planificamos nuevos eventos alrededor de las tendencias más innovadoras en la web: Node.js, Angular, Python, API's, Ruby on Rails, JavaScript, Erlang, Swift, socket.io, MongoDb, Redis, Cassandra, AWS y herramientas para desarrolladores.</p>"
+        lon: -4.420000076293945
+        lat: 36.720001220703125
+      - country: HR
+        city: Zagreb
+        link: 'http://www.meetup.com/JavaScript-Zagreb/'
+        name: JavaScript Zagreb
+        description: '<p>A monthly meetup of JavaScript developer enthusiasts from Zagreb and region.</p>'
+        lon: 15.970000267028809
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/c/2/e/600_284839502.jpeg'
+        lat: 45.79999923706055
+      - country: HU
+        city: Budapest
+        link: 'http://www.meetup.com/nodebp/'
+        name: Node.js Budapest
+        description: "<p>A meetup Node.js-ről fog szólni kezdőknek, haladóknak és bárkinek aki szereti javascriptet.</p>\n<p>A esemény szól mind a frontendeseknek, a backendeseknek és devopsoknak is.<br>\n\n No és persze nem maradhat el a fun rész, mint a nodebot- és quadrocopter építés.</p>\n<p><span>JIFASNIF - JavaScript is fun, and so Node is fun. \_(c) isaacs</span></p>\n<p>----------------<span>----------------</span></p>\n<p>We are about Node.js for beginners, experts and everyone who loves javascript. It's about using Node.js as frontend dev, backend dev or even devops. And last but not least node.js for fun like nodebots or building quadrocopters.</p>\n<p>JIFASNIF - JavaScript is fun, and so Node is fun. \_(c) isaacs</p>"
+        lon: 19.079999923706055
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/0/c/c/600_306452972.jpeg'
+        lat: 47.5099983215332
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/JSChannel-London/'
+        name: JSChannel-London
+        description: |-
+          <p>Whether you're a hands on software engineer, or a person just interested in advanced JS technologies, JSChannel London is the place for you in London.</p>
+          <p><span>This is a group for those who would like to explore the world of JavaScript, from: brainstorming ideas with other developers; listening to talks from leaders in their field; or participating in workshops and hackathons.</span></p>
+          <p><span>We will organise meetings and hold talks in Central London, bringing together the leaders in their fields from companies with</span> household <span>names. JavaScript is an ever expanding technology, whose pace of change is unequalled, and JSChannel hopes to help you stay up to date.</span></p>
+          <p><span>We'll focus on all manner of topics, including: JS testing and automation / engineering productivity (e.g. automated testing, building testing frameworks, etc); exploring new frameworks and practices; looking a the future of JavaScript, in ES6; and many many others.</span></p>
+          <p><span>If you have recommendations for future topics, feedback for the events team or are interested in future events, please fill out our interest form. Past meet-ups are generally recorded - enjoy!</span></p>
+        lon: -0.12999999523162842
+        lat: 51.5099983215332
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Front-Endgineers-London/'
+        name: Front Endgineers London
+        description: "<p>The Front Endgineers is a group for Software Engineers with an interest in Front End technologies. Through our forum and regular meetings you can keep in touch with the latest industry developments, learn new technologies, meet other developers, discuss technical/non technical issues and network further throughout the community.<br>\n\n<br>\n\n<strong>FAQ<br>\n\n</strong><br>\n\n<strong>What is the Front Endgineers group?</strong><br>\n\n<strong>What goes on in the Front Endgineers?</strong><br>\n\n<strong>Who can join?</strong><br>\n\n<strong>Is there a fee to Join, is there a fee for the events?</strong><br>\n\n<strong>How do I join?</strong><br>\n\n<strong>Do you have to go to every presentation/event?</strong><br>\n\n<br>\n\n<br>\n\n<strong>What is the Front Endgineers group?</strong><br>\n\n<br>\n\nThe Front Endgineers is a technical user group for software engineers based in London. It was founded in October 2013.<br>\n\n<br>\n\n<strong>What goes on in the Front Endgineers?</strong><br>\n\n<br>\n\nWe are hoping to run a variety of regular events ranging from social events to technical presentations. On top of the events we aim to run prize draws and develop an active mailing list/forum. We will support the Graduate Development Community in London and promote London based Open Source Software projects where possible.<br>\n\n<br>\n\n<strong>Who can join?</strong><br>\n\n<br>\n\nMembership is restricted to Software Engineers with an interest in Front End technologies working in or around London (or those hoping to train into these technologies, or relocate to London).\_<br>\n\n<br>\n\n<strong>Is there a fee to join, is there a fee for the events?<br>\n\n</strong><br>\n\nIt’s completely free to join and our events will be completely free.<br>\n\n<br>\n\n<strong>How do I join?</strong><br>\n\n<br>\n\nJust click on the link on this page to sign up to the mailing list, you'll hear of all of our latest news and events and can take part in the monthly prize draws.<br>\n\n<br>\n\n<strong>Do you have to go to every presentation?</strong><br>\n\n<br>\n\nAbsolutely not - it’s completely up to you which events you attend and which you don’t. Every event attracts a different crowd.<br>\n\n<br>\n\n<br>\n\nBarry Cranford<br>\n\nFounder of Front Endgineers</p>"
+        lon: -0.12999999523162842
+        lat: 51.5099983215332
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/Ember-js-Belgium/'
+        name: Ember.js Belgium
+        description: "<p>This is a group for anyone interested in developing web applications in Ember.js. I created this group because it's nice to have a local community for sharing knowledge, ideas and inspiration about this awesome web framework. The learning curve for Ember.js is not the lightest so it will also be a place to share your frustrations! Beginner or expert, everyone is welcome.</p>"
+        lon: 4.329999923706055
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/d/c/4/600_397176292.jpeg'
+        lat: 50.83000183105469
+      - country: GB
+        city: Liverpool
+        link: 'http://www.meetup.com/Liverpool-Javascript-user-group-client-server-side-JS/'
+        name: Liverpool JavaScript User Group
+        description: |-
+          <p>Hosted by DoESLiverpool.com</p>
+          <p>At Liverpool JavaScript User Group we cover JS frameworks like Backbone, Angular, Ember etc, libraries like jQuery, extJS and server side options like Node.js and Rhino all washed down with some beer and pizza.</p>
+          <p>We welcome all developers of all skill levels, we're a friendly bunch ranging from newbies to experts.</p>
+          <p>Follow us on twitter @liverpooljsug</p>
+          <p>Join us on linked in <a href="http://www.linkedin.com/groups?gid=6530802" class="linkified">http://www.linkedin.com/groups?gid=6530802</a></p>
+        lon: -2.990000009536743
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/b/d/b/600_442627131.jpeg'
+        lat: 53.400001525878906
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Nodebots-Paris/'
+        name: Les NodeBots de Paris
+        description: "<p>ce groupe est dédié au culte des nodebots et marque le début de leur invasion parisienne !</p>\n<p><span>qu'est ce que les nodebots, me direz vous ? ce sont de petits robots qui on abandoné le C et se sont mis a javascript plus d'informations</span> <a href=\"http://nodebots.io/\">ici</a><span>.</span></p>\n<p>Nous avons un programme d'échange de gadjets éléctronique ici :\_<a href=\"https://github.com/tableflip/nodebots-library\">the nodebots library</a></p>\n<p>suivez le compte\_<a href=\"https://twitter.com/lesNodebots\">@LesNodebots</a> sur twitter pour des infos flash</p>\n<p>Pour le moment ce groupe est assez informel et est crée pour voir combien d'entre nous seraient disponible pour établie une tête de pont a Paris. l'idée serais de faire dans un premier temps des petit workshops autour d'arduino et de ses jonctions avec node.js, et si on est vraiment beaucoup, pourquoi pas des conférences ?</p>\n<p>2 tracks seront proposés a partir de la rentrée</p>\n<ul>\n<li><span>1 track le soir 18h30 - 22h + social time : petit talk, initiation (installation / test framework), social time, demo time</span></li>\n<li><span>1 track le samedi, all day 10h - 18h, ouvert , ou on a deja un peut les mains dedans et on viens hacker ensembles + demo a la fin</span></li>\n</ul>"
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/5/3/c/600_294369532.jpeg'
+        lat: 48.86000061035156
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/PHPConference/'
+        name: International PHP Conference
+        description: |-
+          <p>The International PHP Conference is a famous industry event for PHP developers, webworkers, IT managers, and anyone else who has a burning interest in web technology! <br> <br> The conference focuses on the core topics for developers, as well as on the key technologies for IT executives.</p>
+          <p>&nbsp;</p>
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/1/d/1/600_437164561.jpeg'
+        lat: 52.52000045776367
+      - country: GB
+        city: Liverpool
+        link: 'http://www.meetup.com/LiverpoolClojure/'
+        name: Liverpool Clojure
+        description: 'Meet other local programmers interested in Clojure (and other Lisps and Schemes), functional programming, concurrent programming and anything else we can think of that might be related!'
+        lon: -2.9600000381469727
+        lat: 53.400001525878906
+      - country: CZ
+        city: Prague
+        link: 'http://www.meetup.com/Prague-Meteor-Meetup-Group/'
+        name: Prague Meteor Meetup Group
+        description: '<p>Group for anyone interested in Meteor framework, JavaScript and web development generally. Demoing apps is welcome.</p>'
+        lon: 14.430000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/d/b/8/600_422024472.jpeg'
+        lat: 50.08000183105469
+      - country: HR
+        city: Zagreb
+        link: 'http://www.meetup.com/Meteor-Zagreb/'
+        name: Meteor Zagreb
+        description: |-
+          <p>Meet other developers using <a href="http://meteor.com">Meteor</a>. Share your knowledge, apps, and get feedback from others.</p>
+          <p>Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>
+        lon: 15.970000267028809
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/9/0/600_424682192.jpeg'
+        lat: 45.79999923706055
+      - country: 'NO'
+        city: Kristiansand
+        link: 'http://www.meetup.com/Kristiansand-JavaScript/'
+        name: Kristiansand.js
+        description: |-
+          <p>Bilingual JavaScript meetup group based in Kristiansand, Norway. Information in English upon request (click "Contact Organizer").</p>
+          <p>Kristiansand.js er ei faggruppe for du som jobber eller vil jobbe med JavaScript og relaterte teknologier.</p>
+          <p>Har du noensinne tenkt, «Fins det webutviklere på Sørlandet?»</p>
+          <p>Jeg og. Jeg har vansekelig å tro at vi er et så sjeldne her.</p>
+          <p>Bli med i denne gruppa hvis du vil vise din interesse. Hovedtemaa blir JavaScript og relaterte rammeverk som Meteor, AngularJS, PhoneGap/Cordova osv.</p>
+          <p>Tiden er inne. La oss bygge ei kul gruppe for webutviklere uansett bakstykketeknologi.</p>
+        lon: 7.989999771118164
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/b/8/e/600_304299822.jpeg'
+        lat: 58.150001525878906
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/Node-js-Meetup-Berlin/'
+        name: Node.js Meetup Berlin
+        description: "<blockquote>\n NOTICE: If you're looking for a new job or you're a company looking to hire from among our members, please use \n <a href=\"http://www.upandfront.com\" class=\"linkified\">http://www.upandfront.com</a>. We want to keep the meetups about code only.\n</blockquote>\n<blockquote>\n <p><span>JavaScript is quickly becoming the language that drives your website, your server and your database. It can also run your operating system, your nintendo emulator and the new EPIC game engine.&nbsp;</span> <br></p>\n <p>In this group we focus on the server side - Node.js. Thanks to v8, it runs many times faster than PHP, Ruby or Python, and thanks to the event-based design, it is the ultimate back-end for mobile and web applications. It is fast to code and needs less CPU &amp; RAM - speeding up your development and saving you server costs.&nbsp;</p>\n <p>The group is open to anyone interested. Whether you're wondering why in the world you would want to put JavaScript on a server or want to discuss how async/await is the best thing since sliced bread, let's meet up!</p>\n</blockquote>"
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/6/e/8/4/600_308188292.jpeg'
+        lat: 52.52000045776367
+      - country: DE
+        city: Essen
+        link: 'http://www.meetup.com/Meteor-Ruhrpott/'
+        name: Meteor Ruhrpott
+        description: "<p>MeteorJS Meetup in the Ruhrgebiet, Germany.</p>\n<p>Meteor is an open-source platform for building\_top-quality web apps\_in a fraction of the time using JavaScript all the way and leveraging the power of full stack reactivity.<br>\n\n</p>\n<p>If you are interested in developing web applications and are in the Ruhr area you should join us. It doesn't matter whether you are a beginner or an expert.</p>"
+        lon: 7
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/0/f/8/600_410116632.jpeg'
+        lat: 51.470001220703125
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/jsdevices/'
+        name: 'JS on Devices: Web Programming for the Internet of Things'
+        description: "<p>This is a group for coders, entrepreneurs, and hardware hackers, interested in the huge potential of running JavaScript on embedded devices like the Raspberry Pi and the BeagleBone. Let's get together, share the tools we use, help each other, show off our projects, and inspire each other to build more and better!</p>"
+        lon: -0.10000000149011612
+        lat: 51.5099983215332
+      - country: CZ
+        city: Brno
+        link: 'http://www.meetup.com/BrnoJS/'
+        name: BrnoJS
+        description: |-
+          <p>Monthly gathering of people passionate about JavaScript in Brno, CZ.</p>
+          <p><b>Format</b></p>
+          <p>All talks (except for the introduction) follows the following schedule (borrowed from the cool guys at ViennaJS):</p>
+          <p>• Talk lasts 15 minutes max.</p>
+          <p>• Followed by a 10 minute Q&amp;A session.</p>
+          <p>• Followed by a 5 minute "beer retrieval" round (during which there is time for shootouts).</p>
+        lon: 16.610000610351562
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/7/4/2/600_311298242.jpeg'
+        lat: 49.20000076293945
+      - country: 'NO'
+        city: Bergen
+        link: 'http://www.meetup.com/Bergen-NoSQL/'
+        name: Bergen NoSQL User Group
+        description: |-
+          <p><span>Bergen NoSQL User Group is a place for developers to learn more and share their experiences about all the new and shiny NoSQL databases. </span><span>We discuss databases such as&nbsp;</span><b>MongoDB </b><span>and </span><b>CouchDB&nbsp;</b><span>document stores;&nbsp;</span><b>Neo4J</b><span> and </span><b>Giraph</b><span>&nbsp;graph stores;&nbsp;</span><b>Riak</b><span>, </span><b>Berkeley DB</b><span> and </span><b>Redis</b><span> key-value stores, and&nbsp;</span><b>Cassandra</b><span> and </span><b>HBase</b><span>&nbsp;wide-column stores; and many many more!</span><br></p>
+          <p>If you are facing challenges with MySQL or Postgres or Oracle and want to explore a more flexible, scalable alternative, please join us at one of our meetups.</p>
+        lon: 5.340000152587891
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/a/f/d/600_445155101.jpeg'
+        lat: 60.380001068115234
+      - country: 'NO'
+        city: Trondheim
+        link: 'http://www.meetup.com/BartJS/'
+        name: BartJS
+        description: "<p>En ny-oppstartet Meetup i Trondheim som konsentrerer seg om all-things Javascript. Fra programmering på serveren til koding i klienten, informasjon om det nyeste MV*-rammeverk til programmering av hardware. I denne meetupen kan vi kjøre introduksjoner til nye paradigmer og teknikker, diskusjoner om \"compile-to-javascript\"-språk eller innføring i UI-bibliotek.</p>\n<p>Se Github-repo på\_<a href=\"https://github.com/bartjs\">https://github.com/bartjs</a> og gruppens nettside på <a href=\"http://bartjs.github.io\">http://bartjs.github.io</a>.</p>"
+        lon: 10.399999618530273
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/f/8/6/600_314577222.jpeg'
+        lat: 63.439998626708984
+      - country: DE
+        city: Köln
+        link: 'http://www.meetup.com/WebWorker-Cologne/'
+        name: WebWorker Cologne
+        description: 'WebWorker Cologne ist Deine Community rund um die Themen Web-Enwicklung, Web-Programmierung, Web-Design für Desktop- und Mobile-Browser. Wir treffen uns jeden dritten Mittwoch im Monat zu einem lockeren Zusammensein und Informations- und Gedankenaustausch. Wir freuen uns über Mitgestalter und Mitmacher. Sei dabei!'
+        lon: 6.96999979019165
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/a/3/6/600_424514902.jpeg'
+        lat: 50.95000076293945
+      - country: CZ
+        city: Prague
+        link: 'http://www.meetup.com/prague-developers/'
+        name: Prague developers
+        description: |-
+          <p>Calling all developers in Prague! Prague is an awesome city, right? Many of us expats come here to work and enjoy the city's wonders. However there was one thing bugging me since I came here. How the heck do I meet other skilled professionals in the field of development? So how 'bout you join the group, we go out for some beers from time to time, have some interesting talks, share our knowledge and expertise.</p>
+          <p><span>Looking forward to meeting you!</span><br></p>
+        lon: 14.430000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/0/1/2/600_315736402.jpeg'
+        lat: 50.08000183105469
+      - country: 'NO'
+        city: Oslo
+        link: 'http://www.meetup.com/Meteor-Oslo/'
+        name: Meteor Oslo
+        description: "<p>Group for everyone who interested in Meteor - A Full Stack Framework For Building Pure JavaScript Apps. All skills levels are welcome. Main goal of this group to share knowledge of framework and do some creasy things together. Let's build together new Meteorites community in Oslo.</p>"
+        lon: 10.75
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/2/b/c/600_409069852.jpeg'
+        lat: 59.90999984741211
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/FranceJS/'
+        name: FranceJS
+        description: |-
+          <p>FranceJS, c'est l'ensemble des communautés francophones autour de <b>JavaScript</b>.</p>
+          <p>Ce groupe "meetup" permet de proposer une solution gratuite aux différents meetups français afin qu'ils puissent organiser plus facilement leurs évènements. Chaque évènement ajouté ici est aussi disponible en première page sur <a href="http://francejs.org">francejs.org</a>.</p>
+          <p>Si vous souhaitez découvrir JavaScript et les technologies associées, inscrivez-vous à ce groupe et vous aurez la possibilité de participer aux événements associés et ainsi que rencontrer la communauté.<br>
+
+          </p>
+          <p><br>
+
+          </p>
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/6/c/2/600_320450882.jpeg'
+        lat: 48.86000061035156
+      - country: NL
+        city: Nijmegen
+        link: 'http://www.meetup.com/NijmegenJS/'
+        name: NijmegenJS
+        description: "<p>Developers interested in sharing knowledge and growing their skills around JavaScript and modern web technology: e.g. ES6, NodeJS, Angular, Ember, Web Components, HTML5 APIs, etc.</p>\n<p>Goals:</p>\n<p>•\_A monthly meetup with one or more (short) talks</p>\n<p>• A\_post meal/drinks for socialising.</p>\n<p>•\_Focus on cutting-edge technologies and development techniques.<span>\_</span></p>\n<p>If you want to help out, have any suggestions or feedback, just get in touch!</p>"
+        lon: 5.849999904632568
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/0/0/c/600_320680972.jpeg'
+        lat: 51.84000015258789
+      - country: IS
+        city: Reykjavík
+        link: 'http://www.meetup.com/Javascript-Iceland/'
+        name: Javascript - Iceland
+        description: '<p>This is a group for anyone interested in Javascript. All skill levels are welcome. The reason why this group was started is because the Node.js community in Iceland has grown a lot and we feel like we could make some meet ups on the more general topic of javascript.</p>'
+        lon: -21.920000076293945
+        lat: 64.13999938964844
+      - country: RO
+        city: Bucharest
+        link: 'http://www.meetup.com/Meteor-Romania/'
+        name: Meteor Romania
+        description: "<p>Meet other developers using <a href=\"http://www.meteor.com\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 26.100000381469727
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/1/3/0/600_395633552.jpeg'
+        lat: 44.439998626708984
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/Meteor-Brussels/'
+        name: Meteor Brussels
+        description: "<p>Meet other developers using <a href=\"http://www.meteor.com\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 4.329999923706055
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/1/c/6/600_395633702.jpeg'
+        lat: 50.83000183105469
+      - country: SE
+        city: Göteborg
+        link: 'http://www.meetup.com/Meteor-Goteborg/'
+        name: Meteor Göteborg
+        description: "<p>Meet other developers using <a href=\"http://www.meteor.com\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 12.010000228881836
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/1/4/a/600_422009002.jpeg'
+        lat: 57.720001220703125
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/JS-everywhere/'
+        name: JS.everywhere() Conferences
+        description: "<p>The JS.everywhere() conference are organized in US and Europe</p>\n<p>They are here to demonstrate how strong is JavaScript to build and deploy B2B and B2C professional business application using widely supported Web Standards. JavaScript technologies are shown everywhere in any technologies like databases, servers, proxies, desktops, mobiles, televisions, objects, drones... and in any business / real life domains like commerce, art, sport, ecology, health, industry...</p>\n<br>\n\n<p>The Enterprise world is more and more looking at Cloud platforms and mobile devices for either internal, external usages. We choose for mission to help finding some of the best solutions to enhance portability &amp; interoperability while preserving maintainability &amp; security.</p>\n<br>\n\n<p>Facts</p>\n<p>•\_\_4 previous editions (first in 2011 at Boston)</p>\n<p><span>•\_Endorsed by the W3C (since the first edition)</span></p>\n<p>•\_<span>200-300 attendees</span></p>\n<p><span>•\_Public: Developers, Web Architects, CTOs, Entrepreneurs</span></p>\n<p>•\_<span>European: international attendees, all sessions are in english</span></p>\n<p><span>•\_No financial profit</span></p>\n<p>•\_<span>all tickets and sponsors money is directly invested in the event to get the best speakers/attendees experience\_</span></p>\n<br>\n\n<br>\n\n<p>Former Sponsors:\_</p>\n<p>Amazon, Mozilla, Yahoo, RedHat, O’Reilly, eBay, Atlassian, Pubnub, MongoLabs...</p>\n<br>\n\n<br>\n\n<p>Former Media Sponsors:\_</p>\n<p>InfoQ, The Rude Baguette, Programmez, AccessiWeb, NoSQL matters, Human Coders, Moonbar</p>\n<br>\n\n<br>\n\n<p>Former Speakers:</p>\n<p>Tristan Nitot, Bill Walker (Mozilla), Philippe Le Hegaret (W3C), Douglas Crockford (PayPal), Manuel Deschamps (Twitter), Julian Aubourg (jQuery), Doris Chen (Microsoft), Pamela Fox (Khan Academy), Steve Gill (Adobe), Kyle Simpson (getify),\_Mark Percival (Yahoo!),\_Estelle Weyl (Author, Trainer &amp; Consultant - ex Apple, Yahoo), Aaron Heckmann (10Gen),\_Stephen Blum (PubNub), Dave Freeman (HP), Steve Citron-Pousty (RedHat),\_Dio Synodinos (InfoQ)...</p>\n<p><br>\n\n</p>\n<p>Find the list and coverages of previous and upcoming editions on Lanyrd:</p>\n<p><a href=\"http://lanyrd.com/series/jseverywhere/\">http://lanyrd.com/series/jseverywhere/</a></p>\n<p><br>\n\n</p>\n<p>Feel free to contact us for more informations</p>"
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/f/e/4/600_335440932.jpeg'
+        lat: 48.86000061035156
+      - country: SE
+        city: Göteborg
+        link: 'http://www.meetup.com/gbg-js/'
+        name: gbg.js
+        description: '<p>This is a group for them who wants to be amongst others that have a interest in Web Development and JavaScript , who would like to be a part of techtalks, meetups, hackathons, and after-works. You should be a person who see other peoples lack of knowledge as a opportunity for you to share your own experiences.</p>'
+        lon: 12.010000228881836
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/9/2/600_328502962.jpeg'
+        lat: 57.720001220703125
+      - country: AT
+        city: Vienna
+        link: 'http://www.meetup.com/nodejs-vienna/'
+        name: Node.js Vienna
+        description: "<p>Hang out and discuss node.js tips, tricks, hacks, and frameworks with node.js enthusiasts, newbies and pros.\_</p>\n<p>Show cool stuff you've done and keep in touch about what else is going on in the node.js community.</p>"
+        lon: 16.3700008392334
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/c/a/0/600_359744192.jpeg'
+        lat: 48.220001220703125
+      - country: PL
+        city: Kraków
+        link: 'http://www.meetup.com/KrakowJS/'
+        name: KrakowJS
+        description: 'We want to bring all JS pros from Krakow together - learning, networking, chilling out.'
+        lon: 19.959999084472656
+        lat: 50.060001373291016
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/MEAN-Stack/'
+        name: MEAN Stack
+        description: |-
+          <p>This group is for anyone interested in learning more about the MEAN Stack (MongoDB, ExpressJS, AngularJS and Node.js) which is the latest stack around allowing developers to do rapid application development and application scaffolding.</p>
+          <p><span>Join us if you're interested in this new development stack or if you're simply interested in full stack web development, especially JavaScript as a programming language.</span></p>
+          <p><span>All skill levels are welcome as we do have presentations that are for absolute beginners and we also bring in experts to deliver in detail presentations about particular technologies.</span></p>
+        lon: -0.09000000357627869
+        lat: 51.52000045776367
+      - country: PL
+        city: Warsaw
+        link: 'http://www.meetup.com/Web-Hackers-Poland/'
+        name: Web Hackers Poland
+        description: '<p>Web Hackers Poland is a group covering all forms of Web Development and JS, Functional Programming, Scalability, Cloud Computing, Mobile and more for developers from Poland and Eastern Europe. We will host local meet ups, hackatons and opportunities to connect with successful international startups.</p>'
+        lon: 21.020000457763672
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/f/3/6/600_332817142.jpeg'
+        lat: 52.2599983215332
+      - country: PT
+        city: Porto
+        link: 'http://www.meetup.com/opo-js/'
+        name: opoJS
+        description: Meetup dedicated to all JavaScript aficionados in Porto (OPO) area.
+        lon: -8.619999885559082
+        lat: 41.150001525878906
+      - country: AT
+        city: Graz
+        link: 'http://www.meetup.com/grazjs/'
+        name: grazjs - Graz JavaScript Meetup
+        description: '<p>Eine Gruppe für alle JavaScript Fans in und um Graz. Hauptthemen der Gruppe sollte JavaScript, Web/Mobile/Desktop Development mit JS, Server-Side JS (Node.JS, Ringojs, Vert.x) und JS-getriebene Datenbanken (MongoDB, CouchDB) sein.</p>'
+        lon: 15.420000076293945
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/c/4/8/600_352695432.jpeg'
+        lat: 47.08000183105469
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Paris-js/'
+        name: Paris.js
+        description: "<p>Event-driven community about Javascript.</p>\n<p>Paris.js est un user group centré sur Javascript et les sujets associés, hébergé dans les bureaux d'une entreprise parisienne différente chaque mois; les bierres et les pizzas sont souvent offertes ! Si vous voulez héberger un meetup Paris.js, contactez-nous !</p>\n<p>Paris.js c'est aussi :</p>\n<p>• Un site web qui archive les meetups et les slides/repos des talks :\_<a href=\"http://parisjs.org/\"><b>parisjs.org</b></a>, et son code source open sur Github :\_<a href=\"https://github.com/parisjs/parisjs-website\">https://github.com/parisjs/parisjs-website</a></p>\n<p>• Une mailing list pour toutes les discussions annexes (orga, questions, etc.) :\_<a href=\"https://groups.google.com/forum/#!forum/parisjs\">https://groups.google.com/forum/#!forum/parisjs</a></p>\n<p>• Un compte Twitter (sans pollution) pour annoncer les meetups et passer des messages à la communauté :\_<a href=\"https://twitter.com/parisjs\">@parisjs</a></p>\n<p>• Et enfin, pour les recruteurs et annonces de job en tout genre : ne faîtes rien dans ce groupe sous peine de voir votre message supprimé, mais postez plutôt votre annonce sur la page LinkedIn dédiée :\_<a href=\"http://www.linkedin.com/groups/Parisjs-3852602\">http://www.linkedin.com/groups/Parisjs-3852...</a></p>\n<p>Vous ou votre entreprise désirez nous sponsoriser ? \"<b>Be a ParisJS host</b>\"</p>\n<p>•\_<span><a href=\"https://github.com/parisjs/parisjs-website/wiki/Be-a-ParisJS-Host\">https://github.com/parisjs/parisjs-website/wiki/Be-a-ParisJS-Host</a>\_</span></p>"
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/c/3/a/600_366232282.jpeg'
+        lat: 48.86000061035156
+      - country: FR
+        city: Rennes
+        link: 'http://www.meetup.com/RennesJS/'
+        name: RennesJS
+        description: '<p>Communauté des développeurs #JavaScript passionnés à #Rennes</p>'
+        lon: -1.6799999475479126
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/a/4/0/600_338015392.jpeg'
+        lat: 48.11000061035156
+      - country: NL
+        city: Utrecht
+        link: 'http://www.meetup.com/Utrecht-JavaScript-Meetup/'
+        name: Utrecht JavaScript Meetup
+        description: "<p>This is a group for all things JavaScript in Utrecht (city and Province, that means you Amersfoort, Veenendaal). We are not quite sure how many people would show up for this. So we'll do a mixed JavaScript thing. Think MVC (e.g. AngularJS, Ember, BladerunnerJS etc) but also Node.js (e.g. server side JS, REST, ElasticSearch integration etc), but even GameDevs who dabble with JavaScript or Data Scientists/people/journalists who do D3.js or Leaflet.</p>"
+        lon: 5.110000133514404
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/5/d/6/600_376134742.jpeg'
+        lat: 52.099998474121094
+      - country: PL
+        city: Studzionka
+        link: 'http://www.meetup.com/Meteor-Studzionka/'
+        name: Meteor Studzionka
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 18.770000457763672
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/4/e/2/600_350369922.jpeg'
+        lat: 49.959999084472656
+      - country: SE
+        city: Malmö
+        link: 'http://www.meetup.com/Oresund-Functional/'
+        name: Øresund Functional Programmers
+        description: |-
+          <p>Meetups to share experiences with regards of the use of functional programming languages ​​in software projects.&nbsp;</p>
+          <p>Functional programming languages ​​like Clojure, Scala, Erlang,&nbsp;Lisp,&nbsp;Haskell and&nbsp;Elixir.</p> As the group grows we will hold events in the Øresund region: Helsingborg, Lund, Malmö, Helsingør and Copenhagen.
+        lon: 13.020000457763672
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/9/2/2/600_348959682.jpeg'
+        lat: 55.61000061035156
+      - country: UA
+        city: Kyiv
+        link: 'http://www.meetup.com/KievNodeJS/'
+        name: Kiev node.js Group
+        description: '<p>Four time a year meetup group for Node.js professionals to discuss technology, exchange experience, find solutions and share case studies.</p>'
+        lon: 30.520000457763672
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/b/2/4/600_434431524.jpeg'
+        lat: 50.439998626708984
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/MunichJS-User-Group/'
+        name: MunichJS – JavaScript User Group
+        description: '<p>MunichJS is a user group in Munich for developers (ranging from interested onlookers to beginners to experts) that meets regularly to discuss topics related to JavaScript. Meetings take place in various locations. The group was established in October 2010 at the BarCamp in Munich.</p>'
+        lon: 11.579999923706055
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/e/1/6/600_443775894.jpeg'
+        lat: 48.13999938964844
+      - country: SE
+        city: Malmö
+        link: 'http://www.meetup.com/NodeSkane/'
+        name: Node.js Skåne
+        description: |-
+          <p>Do you want to meet, share knowledge and work with other node.js developers in Skåne? We are a group of passionate&nbsp;entrepreneurs&nbsp;and freelancers who love to collaborate on cool projects. You are free to work on your own projects or team up with others - just show up and have fun!</p>
+          <p>We will host MeetUps in Malmö,&nbsp;Lund and&nbsp;Helsingborg&nbsp;in Southern Sweden (Skåne) during 2016 when we reach 40 members. <br></p>
+        lon: 13.020000457763672
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/8/f/c/600_446435068.jpeg'
+        lat: 55.61000061035156
+      - country: PL
+        city: Łódź
+        link: 'http://www.meetup.com/meet-js-lodz/'
+        name: meet.js Łódź
+        description: |-
+          <p>Niekomercyjne spotkania front-endowe typu meetup, organizowane przez społeczność dla społeczności w w Poznaniu, Warszawie, Krakowie, Wrocławiu, Gdańsku, Katowicach, Łodzi i Szczecinie.</p>
+          <p>Na każdym meet.js można liczyć na kilka prelekcji na tematy webowo-front-endowe (JS, CSS, HTML etc.). Każda z nich trwa 30-40 minut. Duży nacisk kładziemy na Q&amp;A po danym speechu. Spikerami jesteśmy my sami - developerzy. Tylko od specjalistów można dowiedzieć się najwięcej. Każdy może przemawiać na meet.js - wystarczy się zgłosić! Zabawa i cenne doświadczenie gwarantowane!</p>
+        lon: 19.459999084472656
+        lat: 51.77000045776367
+      - country: FI
+        city: Helsinki
+        link: 'http://www.meetup.com/Helsinki-Node-js/'
+        name: Helsinki Node.js
+        description: |-
+          <p>Hello there! This is node.js developers and hackers Helsinki meetup group. In addition to this meetup group, we have a Slack channel (get invited here: https://helnode.typeform.com/to/q6tHHI)</p>
+          <p>This groups is for all who are using or considering to use Node.js or similar JavaScript/V8 based platforms as their server side technology. We'll discuss Node's use as a platform for both front-end and backend servers, use as application platform and even special use cases e.g. in embedded world. For example, how to develop Web apps, APIs and background workers; how to integrate into various databases (NoSQL, RDBs); how to run Node servers smoothly in production environment, e.g. in Amazon cloud.</p>
+        lon: 24.940000534057617
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/5/a/a/600_432346506.jpeg'
+        lat: 60.16999816894531
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/Dublin-Microservices-User-Group/'
+        name: Dublin μServices (Microservices) User Group
+        description: |-
+          <p>The Architectural Monolith’s days are numbered. As companies are becoming more and more agile, and see how they can now adapt in order to innovate and compete faster than their competition, software development teams are being forced to maintain and evolve large, monolithic applications at a pace of change that those architectures were never meant to withstand, let alone embrace!</p>
+          <p>Microservices are a new approach to architecting applications. They are simple, single-purpose, lightweight architectural components that enable you to deliver software faster. The microservice architectural approach also aims to lead to software that thrives on change while at the same time being secure, performant, and stable.</p>
+          <p>This meet up is for people interested in architecting, designing, deploying and maintaining micro service based software architectures.</p>
+        lon: -6.25
+        lat: 53.33000183105469
+      - country: GR
+        city: Thessaloníki
+        link: 'http://www.meetup.com/Thessaloniki-Node-js-Meetup/'
+        name: Thessaloníki Node.js Meetup
+        description: |-
+          <p>Do you love Node? We love it TOO!</p>
+          <p>Thessaloniki Node.js Meetup is an initiative to connect "Noders" across Thessaloniki in order to exchange ideas, knowledge and experience. We are a rapidly growing community that is welcoming individuals from diverse backgrounds and we are happy to assist fellow developers, designers, managers to understand Node.js, learn how to use it and build great things with it!</p>
+          <p>Come and meet us if you want to hear how others are using Node.js to solve real life problems.</p>
+          <p>P.S Because we are aware of the power of video, take a look of what being a Noder means! (in-house produced)</p>
+          <p><a href="https://vimeo.com/112690053">Node.js December 2014</a>,&nbsp;<a href="https://vimeo.com/117608325">Node.js Jan. 2015</a>,&nbsp;<a href="https://vimeo.com/126114980">Node.js April 2015</a>,&nbsp;<a href="https://vimeo.com/128472240">Node.js May 2015</a>,&nbsp;<a href="https://vimeo.com/138629583">Node.js Sept. 2015</a>,&nbsp;<a href="https://vimeo.com/146544394">Node.js November 2015</a>,&nbsp;<a href="https://vimeo.com/151296842">Node.js January 2016</a>,&nbsp;<a href="https://vimeo.com/156186908">Node.js February 2016</a></p>
+          <p> <br></p>
+          <br>
+        lon: 22.940000534057617
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/c/8/e/600_359075982.jpeg'
+        lat: 40.63999938964844
+      - country: IT
+        city: Venezia
+        link: 'http://www.meetup.com/larus-community/'
+        name: 'OpenSource & Agile Venice Group'
+        description: |-
+          <p>Hi All,</p>
+          <p>we are LARUS Business Automation, a company based in Mestre (Venezia) specialised in building web applications based on the Spring Framework, following principles behind the Agile Manifesto.</p>
+          <p>We organise not only training courses, but also free talks and meet ups, aiming to help sharing and learning skills to write better software.</p>
+          <p>In our free-events we are used to talking about these topics:</p>
+          <p>1) OpenSource: JAVA, LINUX, ANDROID<br>
+
+           2) Agile Software Development, Agile &amp; Lean Software Management<br>
+
+           3) Architectures: SOA (without ESB), REST<br>
+
+           4) Mobile: Android, iOS<br>
+
+           5) WEB: HTML5, JQuery, Javascript Frameworks, WebSockets<br>
+
+           6) NOSQL: Neo4J Graph Database and other non-relational databases</p>
+          <p>You can find out more informations about LARUS on our web site: <a href="http://www.larus-ba.it" target="_blank" class="linkified">http://www.larus-ba.it</a></p>
+          <p>If you share our same interests we really love you would join this group: we love to learn from you too!</p>
+          <p>Cheers,<br>
+
+           Lorenzo Speranzoni - LARUS Business Automation srl</p>
+        lon: 12.329999923706055
+        lat: 45.439998626708984
+      - country: SE
+        city: Uppsala
+        link: 'http://www.meetup.com/Uppsalajs/'
+        name: Uppsala.js
+        description: '<p>Welcome to the JavaScript user group in Uppsala! Whether you are an experienced programmer or a just starting to learn – this group is for you. Meet other JavaScript developers and share thoughts and ideas.</p>'
+        lon: 17.639999389648438
+        lat: 59.86000061035156
+      - country: TR
+        city: Istanbul
+        link: 'http://www.meetup.com/jstanbul/'
+        name: 'Jstanbul: Istanbul JavaScript User Group'
+        description: '<p>This is a group for people who interested in JavaScript and connected technologies.</p>'
+        lon: 28.959999084472656
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/1/b/4/600_364905492.jpeg'
+        lat: 41.0099983215332
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/front-end-brussels/'
+        name: Front-end in Brussels
+        description: |-
+          <p><span>This is a group for anyone interested in front-end. All skills levels are welcome. I started this group because I'd like to meet other outdoor enthusiasts. Looking forward to explore the outdoors with everybody.</span><br>
+
+          </p>
+        lon: 4.329999923706055
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/6/9/a/600_371450842.jpeg'
+        lat: 50.83000183105469
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/Bluemix-Barcelona/'
+        name: Bluemix Barcelona
+        description: |-
+          <p><span>¿Quieres conocer el entorno de ejecución de aplicaciones Cloud de IBM? Si eres un creador de aplicaciones o un emprendedor con ideas, este es tu grupo. Bluemix es una plataforma Cloud, con una entrada gratuita, en la que puedes desplegar tus aplicaciones. Además está basado en CloudFoundry, así que soporta casi todos los lenguajes de programación.</span> <br> </p>
+          <p><span>Vamos a darle a la tecla... pero con estilo</span></p>
+          <p><img src="http://photos1.meetupstatic.com/photos/event/b/a/0/6/600_369167622.jpeg"></p>
+          <p><span> <br> </span></p>
+          <p><span>¿Quieres saber qué es Bluemix ya? Aquí tenemos una comunidad de IBM DeveloperWorks con información y tutoriales en castellano:</span></p>
+          <p><a href="https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=e4b149c1-b695-4de1-9671-538da8d1fb5f">Comunidad DeveloperWorks de Bluemix España (dentro está la Wiki, y materiales del workshop que damos)</a></p>
+          <p><a href="http://www.ibm.biz/BluemixES">Página de acceso a Bluemix</a> <br></p>
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/8/a/8/600_369167272.jpeg'
+        lat: 41.400001525878906
+      - country: NL
+        city: Groningen
+        link: 'http://www.meetup.com/GrunnJS/'
+        name: GrunnJS
+        description: '<p>GrunnJS is a meetup for everything JavaScript. The goal is to provide a social meetup for people near Groningen (or anyone interested) that do something with JS. Want to present your latest hack, you can do it here. Anyone that does something or is interested in JS is welcome. Libraries, applications, neat features, client or server side can be presented and discussed. The meetup will have one or two short talks and some beer, drinks and snacks afterwards. You can extend your network and meet people with similar interests.</p>'
+        lon: 6.570000171661377
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/0/3/6/600_402372342.jpeg'
+        lat: 53.22999954223633
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/Dutch-OpenShift-User-Group/'
+        name: Dutch OpenShift User Group
+        description: '<p>This group is a place for developers to learn more about the Platform as a Service solution by Red Hat called "OpenShift". OpenShift is the leading Platform as a Service solution to DEVELOP, HOST, AND SCALE YOUR APPS IN THE CLOUD. So if you want to explore OpenShift, please join us!</p>'
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/5/d/6/600_374694742.jpeg'
+        lat: 52.369998931884766
+      - country: PL
+        city: Warsaw
+        link: 'http://www.meetup.com/WarsawJS/'
+        name: WarsawJS
+        description: "<p>We talk about JavaScript. Every month in Warsaw, Poland.</p>\n<p><br>\n\n</p>\n<p>WarsawJS is a local community of JavaScript professionals and enthusiasts. We meet every month to talk and debate about our favorite programming language. This community is focused on sharing experience from different fields on which JS is used, from web browsers, to servers, dev tools, mobiles, smart tvs, micro controllers,\_ databases, video games and so on. We increase our collective knowledge, by building integrated network of skilled individuals and local companies. Join Us Today!<br>\n\n</p>"
+        lon: 21.020000457763672
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/3/f/c/600_400649692.jpeg'
+        lat: 52.2599983215332
+      - country: DE
+        city: Ravensburg
+        link: 'http://www.meetup.com/Ravensburg-Programming-Meetup/'
+        name: Ravensburg Programming Meetup
+        description: "<p>Wir organisieren ein zweiwöchentliches Meetup um Leute aus der Gegend kennenzulernen,<span>\_die sich für modernes Programmieren im Bereich Web, Mobile und Enterprise interessieren. Dazu zählen z.B. JavaScript, Nodejs, Angular, Ruby, Python, Socket.io, Objective-C, Cocoa, Java und Ähnliches. Die Atmosphäre ist locker bis fröhlich, Anzüge sind verboten.</span></p>"
+        lon: 9.600000381469727
+        lat: 47.790000915527344
+      - country: NL
+        city: Nijmegen
+        link: 'http://www.meetup.com/Nijmegen-Developers-Meetup/'
+        name: Nijmegen Developers Meetup
+        description: |-
+          <p>Kom naar deze meetup om mede-developers uit Nijmegen en omgeving te ontmoeten en kennis en ervaringen uit te wisselen. Er is elke keer een presentatie of een workshop over een aan development gerelateerd onderwerp.&nbsp;</p>
+          <p>Ook bieden we elke keer de gelegenheid aan drie leden om een 10 minuten pitch te houden over een development gerelateerd onderwerp dat je tof vindt. Een project, een bepaalde techniek, nieuwe hardware/software, zoiets.</p>
+          <p>Na afloop is er altijd tijd voor een biertje of drankje. Relaxt, interessant en gezellig! Om de maand op de vierde donderdag van de maand.</p>
+          <p>Ben je op zoek naar developers maar ben je zelf geen developer, dan kan je best contact met ons opnemen, maar de meetups zijn echt alleen voor developers.</p>
+        lon: 5.849999904632568
+        lat: 51.84000015258789
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/Berlin-Grill-JS-Meetup/'
+        name: Berlin Grill.JS Meetup
+        description: "<p>Summer is here, so let's get together around the grill, have a few beers and wursts, and enjoy a lush evening on the summer terrace. The Grill.JS Meetup is strictly informal. There won't be official tech presentations, it's all about friendly discussions over a beer and a grillwurst. We do welcome lightning talks, and we're sure attendees would love to listen to \"my dumbest JS idea this year \". Just keep it short and entertaining. We'll provide for drinks (beer, mate, non-alcoholic) and grillwurst and some vegetarion options, and some salad. If you have special requirements, please bring your own food or drinks.</p>"
+        lon: 13.380000114440918
+        lat: 52.52000045776367
+      - country: GB
+        city: Leeds
+        link: 'http://www.meetup.com/Leeds-Code-Dojo/'
+        name: Leeds Code Dojo
+        description: "<p>Leeds Code Dojo is a group dedicated to programming. \_We focus on practical coding sessions , where you can learn by doing.</p>\n<p><span>Want to have some fun coding in a relaxed and friendly environment? Interested in self-improvement through deliberate practice? Want to see what you can learn from fellow programmers, and teach them what you know? Then Leeds Code Dojo is for you!</span></p>\n<p><span>All languages and levels of experience welcome.</span><br>\n\n</p>"
+        lon: -1.559999942779541
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/e/4/a/e/600_385018542.jpeg'
+        lat: 53.79999923706055
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Fullstack-js-London/'
+        name: Fullstack.js London
+        description: "<p><span>This group aims to explore the wonderful world of </span>fullstack<span> javascript. There are no limits on what libraries or technologies apart from heavy usage of javascript on the front and backend. Anyone wishing to learn or show off some </span>fullstack<span> js projects is more than welcome. It's our time Ninja's.</span><br></p>"
+        lon: -0.10000000149011612
+        lat: 51.4900016784668
+      - country: DE
+        city: Hamburg
+        link: 'http://www.meetup.com/node-HH/'
+        name: node.HH - Node.js User Group
+        description: |-
+          <p>This is a group for <b>anyone</b> interested in <b>Node.js</b>. We will meet to <b>talk</b>, <b>hack</b> and <b>learn</b> with and from each other. This is an open group, everyone is invited to <b>propose</b> talks and hands-on ideas. We all are learners in some way, don't be shy. To give you a hint, you could talk about:</p>
+          <p>• this one library, that changed your life or just helped you out. <br> </p>
+          <p>• how do you use Node? <br> </p>
+          <p>• best practices in development and operations <br> </p>
+          <p>• integration of Node.js in existing setups <br> </p>
+          <p>• interesting hacks or benchmarks <br> </p>
+          <p>•&nbsp;name your topic <br> </p>
+          <p>The talks can be in english or german, depending on the attenders. However english is preferred in case of conflicts. Usually there should be 1-3 Talks plus enough time for socializing. If <b>you know about someone</b> who definitely should talk at our meetup, <b>put a message</b> and i try to make contact. Or do it yourself.</p>
+          <p> <br> </p>
+          <p>Also we want to <b>mix the formats</b>, and will do open spaces, panel discussions and other stuff. <br> </p>
+          <p> <br> </p>
+          <p>We consider this group as an affiliate of the <a href="http://www.meetup.com/hamburg-js/">HH.js</a> group. If you have some general talks on JavaScript or front-end specific stuff, please <b>consider to talk there</b> (most of us attend there anyway :) ). This being said, if you have a strong argument to talk here instead, we are happy to have you here. <br> </p>
+          <p><b>Feedback Channel</b></p>
+          <p>we have a <a href="https://trello.com/b/lmbd9rpc">(new) Trello Board</a>, where you can put any kind of feedback, your ideas, wishes and proposals. We have a voting option there as well. Please use this! <br> </p>
+          <p><b>Important Note</b> <br> </p>
+          <p>We are trying to be an <b>inclusive</b> meetup and happily <b>conform</b> to <a href="http://confcodeofconduct.com/">the Code of Conduct.</a></p>
+          <p>Don't forget to follow us on Twitter: <a href="https://twitter.com/NodeHamburg">@NodeHamburg</a> <br> </p>
+        lon: 10
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/1/1/0/600_382301232.jpeg'
+        lat: 53.54999923706055
+      - country: FR
+        city: Montpellier
+        link: 'http://www.meetup.com/MontpellierJS/'
+        name: MontpellierJS
+        description: "Il s'agit d'un groupe visant à rassembler les utilisateurs et développeurs javascript sur la région de Montpellier."
+        lon: 3.869999885559082
+        lat: 43.61000061035156
+      - country: FR
+        city: Grenoble
+        link: 'http://www.meetup.com/AngularJS-Meetup-Grenoble/'
+        name: 'Angular & more'
+        description: '<p>This group is to exchange experiences with Angular and to be aware of new technologies for the Frontend developer.&nbsp;</p>'
+        lon: 5.71999979019165
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/5/3/f/600_442217727.jpeg'
+        lat: 45.189998626708984
+      - country: IS
+        city: Reykjavík
+        link: 'http://www.meetup.com/Meteor-Reykjavik/'
+        name: Meteor Reykjavík
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -21.920000076293945
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/2/b/8/600_382465272.jpeg'
+        lat: 64.13999938964844
+      - country: DE
+        city: Saarbrücken
+        link: 'http://www.meetup.com/SaarJS/'
+        name: SaarJS User Group
+        description: SaarJS is a user group in Saarbrücken for developers (ranging from interested onlookers to beginners to experts) that meets regularly to discuss topics related to JavaScript. Meetings take place in various locations.
+        lon: 6.96999979019165
+        lat: 49.25
+      - country: DE
+        city: Darmstadt
+        link: 'http://www.meetup.com/Darmstadt-node-js-Meetup/'
+        name: Darmstadt node.js Meetup
+        description: "<p>node.js ist in der Vergangenheit immer interessanter zur Entwicklung von Next Level Anwendungen geworden. Gibt es im Rhein-Main Gebiet Interessierte die ihr wissen an andere weitergeben wollen? Oder gibt es Interessierte die mehr über node.js und das Ökosystem dahinter erfahren wollen?\_</p>\n<p><b>Agenda</b>\_</p>\n<p>Da dies das erste node.js Darmstadt Meetup wäre, gibt es bisher nur eine kleine Agenda:\_</p>\n<p>•\_Wenn gewünscht, kurze Einführung in node.js\_</p>\n<p>•\_Eine kleine Q&amp;amp;A Runde mit den Teilnehmern: Wer benutzt bereits node.js? Professionell/Beruflich oder als Hobby? Welche Erfahrungen (Probleme, Vorteile) wurden mit node.js gemacht?\_</p>\n<p>•\_Ideen sammeln für das nächste Meetup ;-)</p>\n<p>--\_</p>\n<p>node.js has become more and more intersting for developing next level web applications. Are there people in the Rhein-Main region who want to give their knowledge to other interested people? Or... are there people who want to use node.js in future and want to know more about it?\_</p>\n<p><b>Agenda</b>\_</p>\n<p><span>Because this would be the first Meetup there is no real agenda yet.\_</span></p>\n<p>• I<span>ntroduction to node.js (if requested)\_</span></p>\n<p>•\_<span>A personal Q&amp;amp;A round with the participants: Who's using node.js already? Professonal or Hobby? What where the pains, gains and experiences with using node.js?\_</span></p>\n<p>•\_<span>Collecting ideas for next Meetup ;-)</span><br>\n\n</p>"
+        lon: 8.640000343322754
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/5/5/0/600_385970512.jpeg'
+        lat: 49.869998931884766
+      - country: SK
+        city: Bratislava
+        link: 'http://www.meetup.com/nodeba/'
+        name: Node.js Bratislava
+        description: "<p>We are about Node.js for beginners, experts and everyone who loves javascript. It's about using Node.js as frontend dev, backend dev or even devops. And last but not least node.js for fun like nodebots or building quadrocopters.</p> \n<p>JIFASNIF - JavaScript is fun, and so Node is fun. (c) isaacs</p> \n<p>Meet us online&nbsp;<a href=\"https://gitter.im/nodeba/nodeba\">https://gitter.im/nodeba/nodeba</a> <br> </p> \n<p>Here are talks&nbsp;<a href=\"https://github.com/nodeba/\">https://github.com/nodeba</a></p>"
+        lon: 17.1299991607666
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/e/c/8/600_444644744.jpeg'
+        lat: 48.15999984741211
+      - country: ES
+        city: Palma
+        link: 'http://www.meetup.com/MallorcaJS/'
+        name: MallorcaJS
+        description: "<p>This is a group for people doing stuff with JavaScript. <br> If you are building rich Internet applications, working with libraries or crafting cool code, you'll find people to share your experiences with. <br> If you are just starting out, come and meet others who have been there. This is a place to share knowledge, ask questions, teach and meet new faces. <br> Everyone is welcome!</p>"
+        lon: 2.6500000953674316
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/d/b/0/600_408536752.jpeg'
+        lat: 39.56999969482422
+      - country: FR
+        city: Saint-Étienne
+        link: 'http://www.meetup.com/Meteor-Sainte/'
+        name: Meteor Sainté
+        description: "Meetup dédié à la plateforme Meteor, framework web basé sur nodejs, réactif et simple d'accès. Tout le monde est le bienvenu. Simplement curieux, débutant, expérimenté.. Démonstrations, workshops et initiations. https://www.meteor.com/"
+        lon: 4.389999866485596
+        lat: 45.43000030517578
+      - country: SE
+        city: Uppsala
+        link: 'http://www.meetup.com/meteor-uppsala/'
+        name: Meteor Uppsala
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 17.639999389648438
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/a/e/5/600_437483269.jpeg'
+        lat: 59.86000061035156
+      - country: DE
+        city: Ulm
+        link: 'http://www.meetup.com/webmontag/'
+        name: Web Montag Ulm
+        description: "<p>Ein Web Montag ist ein informelles Treffen rund um aktuelle Themen aus dem Bereich Internet und neue Medien, das Entwickler, Designer, Unternehmer, Blogger und sonstige beruflich oder privat Interessierten zusammenbringt.</p>\n<p><span>Wir treffen uns jeden ersten Montag im Monat im <a href=\"https://de.wikipedia.org/wiki/Coworking\">Coworking</a> Space\_<a href=\"http://workraum.de/\">wørkraum</a>, um über aktuelle Trends und Themen aus den Bereichen Internet und Neue Medien zu diskutieren. Einleitend finden dazu oft kurze Vorträge und Präsentationen einiger Teilnehmer statt.<br>\n\n</span></p>\n<p><span>Ein Web Montag findet üblicherweise in einem lockeren, offenen Rahmen statt. Nach Möglichkeit mit Getränken, Snacks, Wi-Fi, interaktiven Präsentationen, Demos zu aktuellen Projekten und Produkten, Vorstellung und Austausch neuer Ideen, Brainstorming, Networking…\_<br>\n\n</span></p>\n<p><span>Der Web Montag steht allen offen, die sich für Themen rund um die Zukunft des Internets interessieren, egal ob Experte oder Anfänger. Einzige Grundvoraussetzung ist Offenheit für neue Ideen sowie die Bereitschaft, zu lernen und Wissen zu teilen.</span></p>"
+        lon: 9.970000267028809
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/d/c/600_415502012.jpeg'
+        lat: 48.400001525878906
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/London-dev/'
+        name: London.dev
+        description: |-
+          <p>Welcome to London.dev Meetup.&nbsp;</p>
+          <p><span>London.dev is aimed at professionals within the web industry who have an interest in Software development, and/or Computer science. &nbsp;It happens usually the last Tuesday of every Month.</span></p>
+          <p>We are looking for volunteers, speakers, partners, sponsors and nice places to host the event. We like to work with other meetups and conferences too. If you are interested in or have some idea about, please contact us.</p>
+          <p><span>Thanks to our partners&nbsp;</span><a href="http://www.meetup.com/London-IT-Contractors-Group/">London IT Contractors Group</a><span>&nbsp;and </span><a href="http://progscon.co.uk">ProgSCon Conference</a><span> to help us to organise this meetup.</span> <br></p>
+          <p> <br></p>
+          <p>Thanks for reading, and see you at our next meetup.</p>
+          <p>Follow us on twitter:&nbsp;<a href="https://twitter.com/londondev_mtp">@londondev_mtp</a></p>
+          <p> <br></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: -0.09000000357627869
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/2/6/e/600_444964718.jpeg'
+        lat: 51.52000045776367
+      - country: FR
+        city: Strasbourg
+        link: 'http://www.meetup.com/StrasbourgJS/'
+        name: StrasbourgJS
+        description: '<p>StrasbourgJS is a meetup to talk about all sides of Javascript, for client-side and server side usage. We might also talk about the rising frameworks like angular, ember and backbone or even meteor. Beginners are welcome as well as the most experimented programmers.</p>'
+        lon: 7.75
+        lat: 48.58000183105469
+      - country: DE
+        city: Düsseldorf
+        link: 'http://www.meetup.com/Meteor-Dusseldorf/'
+        name: Meteor Düsseldorf
+        description: "Meteor is an open-source platform for building top-quality web apps in a fraction of the time using JavaScript all the way and leveraging the power of full stack reactivity. If you are interested in developing web applications and are in or around Düsseldorf you should join us. It doesn't matter whether you are a beginner or an expert. Share your knowledge, apps, and get feedback from others."
+        lon: 6.789999961853027
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/9/8/2/600_408314722.jpeg'
+        lat: 51.2400016784668
+      - country: DE
+        city: Nürnberg
+        link: 'http://www.meetup.com/FrankenJS/'
+        name: FrankenJS
+        description: |-
+          <p>JavaScript, Pattern, Frameworks, Schäuferla, Web, Bier, Angular, Ember, Nämberch, Backbone, Promises...</p>
+          <p>Franken ist reich an Entwicklern, guten Ideen, weltklasse Software und Kreativität. Wir sind uns sicher, dass sich hinter all diesen Talenten auch einige JavaScript-Developer verbergen.</p>
+          <p>Viele Großstädte und Metropolregionen organisieren seit einigen Jahren JavaScript Usergroups und Meet-Ups. Franken, insbesondere die Großstädte Nürnberg, Erlangen und Fürth, sollten dem in nichts nachstehen. Daher haben wir es uns zur Aufgabe gemacht, das JavaScript KnowHow der Region zu bündeln und zu verbreiten. Wir möchten uns mit dieser Usergroup aktiv dafür einsetzen, dieses Wissen in der Region zu teilen und andere Entwickler dafür zu begeistern.</p>
+          <p>Da eine Usergroup nur mit ihren Mitgliedern wachsen kann, sind wir auf&nbsp;euch&nbsp;angewiesen. Was erwartet ihr von einem JavaScript / Web-Meetup? Welche Themen interessieren euch besonders? Womit wollt/könnt ihr bei der Usergroup beitragen? In welcher Region Frankens würdet ihr das erste Treffen bevorzugen? Erwartet ihr neben entspannter Atmosphäre professionelle Talks?</p>
+          <p>Ihr erreicht uns ebenfalls auf Twitter unter <a href="http://twitter.com/FrankenJS">@FrankenJS</a>, per E-Mail:&nbsp;<a href="mailto:servus@frankenjs.org">servus@frankenjs.org</a>, oder über unsere Website&nbsp;<a href="http://frankenjs.org">http://frankenjs.org</a></p>
+          <p>Ein erstes Event ist noch für Herbst 2014 geplant. <br> </p>
+        lon: 11.050000190734863
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/0/5/e/600_411053342.jpeg'
+        lat: 49.45000076293945
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/keystonejs-london/'
+        name: London KeystoneJS Meetup
+        description: "<p>Meet other developers using <a href=\"https://github.com/JedWatson/keystone\">KeystoneJS</a>. Share your knowledge, projects and get feedback from others. KeystoneJS is an open-source content management platform built on top of MongoDB &amp; NodeJS for creating robust scalable websites within few minutes.\_</p>"
+        lon: -0.12999999523162842
+        lat: 51.52000045776367
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/WebPlatform-London/'
+        name: Web Platform London
+        description: '<p>Web Platform London was born to promote openness in the Web Platform and support developers in learning new stuff / contribute to <a href="http://www.webplatform.org">webplatform.org</a>.</p>'
+        lon: -0.12999999523162842
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/6/4/9/600_446362089.jpeg'
+        lat: 51.47999954223633
+      - country: LT
+        city: Vilnius
+        link: 'http://www.meetup.com/Vilnius-js/'
+        name: Vilnius.js
+        description: |-
+          <p><b>A group for JavaScript developers, lovers, enthusiasts and explorers in Vilnius.</b> <br></p>
+          <p><span>Let's meet to talk about JavaScript! Client-side, server-side, any side! VilniusJS is a meetup to share the knowledge about the newest technologies, best practices, the greatest patterns and everything that is united by JavaScript.</span></p>
+          <p><span>Feel free to suggest topics and speakers (you?), or even step in and organise the next event yourself! This is an open platform for the community.</span></p>
+          <p>Oh and of course require('beer');</p>
+          <p>Join us at #vilniusjs channel <a href="https://uglt.herokuapp.com/">at Slack</a>.</p>
+          <p>•&nbsp;<a href="http://vilniusjs.lt">vilniusjs.lt</a></p>
+          <p>•&nbsp;<a href="https://github.com/vilniusjs">github.com/vilniusjs</a>&nbsp;</p>
+          <p><span>•&nbsp;<a href="https://twitter.com/vilniusjs">twitter.com/vilniusjs</a></span></p>
+        lon: 25.270000457763672
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/5/2/0/600_410661792.jpeg'
+        lat: 54.70000076293945
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/beerjs-amsterdam/'
+        name: Beer.js Amsterdam
+        description: "Events involving the two of mankind's greatest inventions; Beer and JavaScript."
+        lon: 4.889999866485596
+        lat: 52.369998931884766
+      - country: DE
+        city: Essen
+        link: 'http://www.meetup.com/PottJS/'
+        name: PottJS
+        description: "The \"Ruhrpott\" is not only Germany's biggest metropolitan area, it has also become an important part of Germany's role in information technology. What's missing is a central user group for JavaScript developers. Here it is. Let's talk, let's get to know each other. Let's get together and create cool stuff, maybe. Let's do PottJS. Glück auf."
+        lon: 7
+        lat: 51.470001220703125
+      - country: PL
+        city: Warsaw
+        link: 'http://www.meetup.com/MeetjsWarsaw/'
+        name: Meet.js Warsaw
+        description: '<p>Meet.js Warsaw is a part of Meet.js community – Polish JavaScript meetups which are organized every month in 8 biggest cities of Poland. Attending our meetup is free of charge. We usually talk about JavaScript, however we aim to have talks on CSS and HTML5 as well. Become a part of our community at http://meetjs.pl.</p>'
+        lon: 21.020000457763672
+        lat: 52.2599983215332
+      - country: DE
+        city: Rheda-Wiedenbrück
+        link: 'http://www.meetup.com/OWL-JS/'
+        name: JavaScript User Group OWL
+        description: "<p>Die JavaScript User Group OWL\_bietet ab November ein regelmäßiges Treffen rund um das Thema JavaScript und verwandte Technologien. Du arbeitest mit JavaScript oder interessierst dich für moderne Web-Technologien? Du willst Neues entdecken oder dich einfach mit anderen Entwicklern über Praxis-Themen austauschen? Ob blutiger Anfänger oder graubärtiger ECMAScript-Veteran, bei uns ist jeder willkommen!</p>"
+        lon: 8.279999732971191
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/e/e/0/600_411400672.jpeg'
+        lat: 51.849998474121094
+      - country: CH
+        city: Zürich
+        link: 'http://www.meetup.com/Zurich-Node-js/'
+        name: Zurich Node.js
+        description: |-
+          <p>This is a group dedicated to learning, spreading the knowledge of, and improving Node.js - the evented, server side javascript platform harnessing the underlying power of Google's V8 JS engine.<br>
+
+           You should join us if you want to learn about, share experiences with, or work with Node.js and it's modules.</p>
+          <p><span>Regardless of whether you work in web development or on some Internet of things application. As long as it contains some Node.js code, it's something to present and discuss at a meetup of this group.</span></p>
+          <p>I'd like to have a first meetup somewhen between mid to end of October. As soon as some people join the group, we can have a discussion about some topics for a first talk. Surely we can also organise something earlier if there's a demand.<br>
+
+           I assume in the beginning I'll give a short intro to Node.js for people that don't know the ecosystem yet.<br>
+
+          <br>
+
+           I'm looking forward to learning and hacking with you.</p>
+          <p>Marc Bachmann</p>
+          <p><a href="http://twitter.com/mrbrookman" class="linkified">http://twitter.com/mrbrookman</a><br>
+
+          </p>
+        lon: 8.539999961853027
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/2/d/e/600_412313982.jpeg'
+        lat: 47.380001068115234
+      - country: PL
+        city: Kraków
+        link: 'http://www.meetup.com/DevMeetings-Frontend-Development-Katowice/'
+        name: DevMeetings Frontend Development Katowice
+        description: Grupa uczestników DevMeetingów w Krakowie o tematyce Frontend Development.
+        lon: 19.959999084472656
+        lat: 50.060001373291016
+      - country: PL
+        city: Wroclaw
+        link: 'http://www.meetup.com/DevMeetings-Frontend-Development-Wro/'
+        name: DevMeetings Frontend Development Wroclaw
+        description: Grupa dla uczestników DevMeetingów we Wrocławiu poświęconych tematyce Webdevelopment.
+        lon: 17.030000686645508
+        lat: 51.11000061035156
+      - country: PL
+        city: Wroclaw
+        link: 'http://www.meetup.com/Meteor-Wroclaw/'
+        name: Meteor Wroclaw
+        description: |-
+          <p>Wrocławska grupa sympatyków <a href="http://meteor.com">Meteor</a>a. Spotykamy się aby wspólnie dzielić się doświadczeniami i pomagać sobie w budowaniu lepszych aplikacji.</p>
+          <p>Meteor jest platformą open-source napisaną w JavaScript, umożliwiającą łatwe i przyjemne budowanie wysokiej jakości aplikacji webowych.<br>
+
+          </p>
+        lon: 17.030000686645508
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/d/a/6/600_416715782.jpeg'
+        lat: 51.11000061035156
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/Frontend-Developer-Meetup-Amsterdam/'
+        name: Frontend Developer Meetup Amsterdam
+        description: |-
+          <p>We are the largest Frontend Developer Meetup Group in the Netherlands. Hosted over 10 Meetups in total over the last 12 months including our other group&nbsp;<a href="http://www.meetup.com/AngularJS-Amsterdam-Meetup/">http://www.meetup.com/AngularJS-Amsterdam-Meetup/</a>. <span>Calling all frontend developers in Amsterdam (and the Netherlands). With the creation of this group we are offering frontend developers advice on how to promote yourself in the modern world.&nbsp;</span></p>
+          <p><span>Give presentations on the latest tools, techniques, frameworks and libraries that companies are looking for. Information on companies that are hiring in Amsterdam (and the Netherlands) and what they can offer you. You will be supplied with beer and pizza as you mingle with other Frontend Developers in Amsterdam.&nbsp;</span></p>
+          <p><span>We will be welcoming ideas on what you would like to hear from future Meetups.</span></p>
+        lon: 4.889999866485596
+        lat: 52.369998931884766
+      - country: PL
+        city: Szczecin
+        link: 'http://www.meetup.com/meetjs-szczecin/'
+        name: Meet.js Szczecin
+        description: '<p>Meet.js to regularne spotkania dla front-end developerów, na których pojawia się kilka 20 minutowych prelekcji o HTML5, CSS3 i JavaScript. Są one darmowe, a na scenie występują jedynie chętne osoby, gotowe podzielić się swoimi spostrzeżeniami, pomysłami i technikami tworzenia stron internetowych.&nbsp;<span>Obecnie meet.js jest obecny w 8 miastach Polski – Poznaniu, Warszawie, Krakowie, Wrocławiu, Gdańsku, Katowicach, Łodzi i Szczecinie. Średnio na jedno spotkanie meet.js przychodzi około 70 ludzi, choć rekordowe są Gdańsk i Kraków, które potrafią regularnie zbierać ponad 120 uczestników.&nbsp;</span></p>'
+        lon: 14.529999732971191
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/9/8/0/600_417442912.jpeg'
+        lat: 53.43000030517578
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/fullstack-js-berlin/'
+        name: Fullstack.js
+        description: "<p>This user group is about anything related to JavaScript and web development with a focus to modularity and scalability. We're also open for topics on infrasturcture.</p>"
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/a/0/6/600_421566662.jpeg'
+        lat: 52.52000045776367
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/AngularJS-London-BYOP/'
+        name: 'AngularJS London : Bring Your Own Project'
+        description: |-
+          <p>Join other web developers for a monthly AngularJS - Bring Your Own Project - Meetup at SapientNitro, London from 6:30PM as we all work on group member's AngularJS projects.&nbsp;</p>
+          <p>Bring your questions, your code, and your desire to help. The sessions are informal, friendly, and organised with a loose agenda. Mix with your fellow Angularians and get hacking!</p>
+        lon: -0.07999999821186066
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/f/b/c/600_437008604.jpeg'
+        lat: 51.52000045776367
+      - country: PL
+        city: Katowice
+        link: 'http://www.meetup.com/meet-js-Katowice/'
+        name: meet.js Katowice
+        description: |-
+          <p>Niekomercyjne spotkania front-endowe typu meetup, organizowane przez społeczność dla społeczności. Zero komercji, czysta wiedza.</p>
+          <p>Na każdym meet.js można liczyć na kilka prelekcji na tematy webowo-front-endowe (JS, CSS, HTML etc.). Każda z nich trwa 10-15 minut. Duży nacisk kładziemy na Q&amp;A po danym speechu. Spikerami jesteśmy my sami - developerzy. Tylko od specjalistów można dowiedzieć się najwięcej. Każdy może przemawiać na meet.js - wystarczy się zgłosić! Zabawa i cenne doświadczenie gwarantowane!</p>
+        lon: 19.020000457763672
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/c/7/3/600_432892339.jpeg'
+        lat: 50.2599983215332
+      - country: PL
+        city: Szczecin
+        link: 'http://www.meetup.com/FixFusion/'
+        name: FixFusion
+        description: "<p>Here's an idea. Let's gather a group of open source software enthusiasts willing to invest few weekend hours to help some open source projects available on GitHub platform. Then, have a great time fixing bugs, adding features, editing docs, refactoring, testing, and even open sourcing your own software! All this while interacting with like-minded people, sharing knowledge and learning new things.</p>"
+        lon: 14.529999732971191
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/b/e/0/600_420751712.jpeg'
+        lat: 53.43000030517578
+      - country: FR
+        city: Lyon
+        link: 'http://www.meetup.com/Meteor-Lyon/'
+        name: Meteor Lyon
+        description: "Meteor est une nouvelle plateforme web. Son intérêt se trouve dans ses différents concepts : partage de code frontEnd/backEnd, compensation de latence, temps réel... Venez découvrir cette plateforme, venez partager votre expérience sur Meteor. Ce meetup n'est pas réservé aux seuls techniciens car Meteor se veut facile d'accès. Si vous avez une îdée, venez nous rencontrer pour que l'on puisse concrétiser celle-ci ensemble."
+        lon: 4.829999923706055
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/5/e/600_424442142.jpeg'
+        lat: 45.7599983215332
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/ShoreditchJS/'
+        name: ShoreditchJS
+        description: '<p>Because other tech meet-ups are too mainstream.</p>'
+        lon: -0.09000000357627869
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/3/9/f/600_431729599.jpeg'
+        lat: 51.529998779296875
+      - country: 'NO'
+        city: Stavanger
+        link: 'http://www.meetup.com/Stavanger-JavaScript/'
+        name: Stavanger.js
+        description: "<p>Bilingual Meteor (real-time JavaScript framework) user group based in Stavanger, Norway. Information is provided in English by default, we choose the language based on the participants when each event starts (if everyone understands Norwegian, then we go with that).\_</p>\n<p><b>ENGLISH</b></p>\n<p>Stavanger.js is a JavaScript-focused group for people who work with or want to work with JavaScript (on both the server and client) and related technologies. I started it because there weren't yet any other groups in the region with JavaScript as a focus. But it's constantly becoming a larger player in the development industry.</p>\n<p>If you want to meet like-minded people and talk about what's new with JavaScript frameworks and related topics, this group is for you.</p>\n<p>I expect the main topics to be JavaScript and related frameworks like Meteor, AngularJS, PhoneGap/Cordova, etc. I'll probably only be presenting on Meteor and AngularJS, but presentations from others on other frameworks are welcome!</p>\n<p>Events from Meteor Stavanger will be cross-posted here. There's also a good explanation on what Meteor is on Meteor Stavanger's group intro.</p>\n<p><br>\n\n</p>\n<p><b>NORSK</b></p>\n<p>Stavanger.js er ei faggruppe for du som jobber eller vil jobbe med JavaScript (på både serveren og klienten) og relaterte teknologier. Jeg hadde lyst til å starte ei gruppe i regionen der JavaScript stod i sentrum. Men det blir hele tida mer og mer tungvektig som utviklerverktøy.</p>\n<p>Har du lyst til å møte likesinnede og diskutere utviklinga i JavaScript-rammeverka og øvrige tema, er denne gruppa noe for deg.</p>\n<p>Hovedtemaa blir JavaScript og relaterte rammeverk som Meteor, AngularJS, PhoneGap/Cordova osv. I utgangspunktet er Meteor og AngularJS rammeverka som blir presentert, men foredrag om andre rammeverk er velkomne.</p>\n<p>Arrangementa i Meteor Stavanger (<a href=\"http://meetup.com/Meteor-Stavanger\" target=\"_blank\" class=\"linkified\">http://meetup.com/Meteor-Stavanger</a>) blir også posta her. Det er også ei grei forklaring på hva Meteor er på introduksjonssida til gruppa.</p>\n<p><br>\n\n</p>\n<p><i>Group photo from Wikimedia Commons. User:\_en:User:Godztian (Wikipedia English). License: GFDL (<a href=\"http://www.gnu.org/copyleft/fdl.html\" class=\"linkified\">http://www.gnu.org/copyleft/fdl.html</a>) or CC-BY-SA-3.0 (<a href=\"http://creativecommons.org/licenses/by-sa/3.0/\" class=\"linkified\">http://creativecommons.org/licenses/by-sa/3...</a>)</i></p>"
+        lon: 5.710000038146973
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/3/7/e/600_422973662.jpeg'
+        lat: 58.970001220703125
+      - country: RO
+        city: Iasi
+        link: 'http://www.meetup.com/Meteor-Iasi/'
+        name: Meteor Iasi
+        description: |-
+          <p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others.</p>
+          <p>Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>
+        lon: 27.56999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/b/6/4/600_427087012.jpeg'
+        lat: 47.16999816894531
+      - country: LU
+        city: Luxembourg
+        link: 'http://www.meetup.com/Meteor-Luxembourg/'
+        name: Meteor Luxembourg
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 6.119999885559082
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/6/6/8/600_424490792.jpeg'
+        lat: 49.619998931884766
+      - country: GB
+        city: Oxford
+        link: 'http://www.meetup.com/JSOxford/'
+        name: JSOxford
+        description: "We're mostly a meet up, sometimes a hack day, sometimes a party with the python and ruby people. If you do anything with JavaScript, or are interested in learning about it - come along to hang out with friendly/nice/welcoming/like-minded group of people. JSOxford has been going quite a while, though have just switched to meetup. Find out more about our past events at http://jsoxford.com."
+        lon: -1.2400000095367432
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/1/3/5/600_440673077.jpeg'
+        lat: 51.75
+      - country: IT
+        city: Roma
+        link: 'http://www.meetup.com/Meteor-Rome/'
+        name: Meteor Rome
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 12.479999542236328
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/7/8/6/600_424826502.jpeg'
+        lat: 41.900001525878906
+      - country: NL
+        city: Rotterdam
+        link: 'http://www.meetup.com/Meteor-Rotterdam/'
+        name: '[MOVED] Meteor Rotterdam'
+        description: |-
+          <p>This group is now a part of Meteor NL, which you can find at&nbsp;<a href="http://www.meetup.com/Meteor-NL/.">http://www.meetup.com/Meteor-NL/.</a>&nbsp;</p>
+          <p><br></p>
+          <p><br></p>
+        lon: 4.480000019073486
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/4/7/4/600_424829812.jpeg'
+        lat: 51.93000030517578
+      - country: DE
+        city: Frankfurt
+        link: 'http://www.meetup.com/FrankfurtJS/'
+        name: 'FrankfurtJS – JavaScript, HTML5 and NodeJS Meetup'
+        description: '<p>FrankfurtJS is a JavaScript, HTML5 and NodeJS user group in Frankfurt currently organized by Kahlil Lechelt, Jo Meenen and Eugene Terehov.</p>'
+        lon: 8.680000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/5/e/b/600_444298859.jpeg'
+        lat: 50.119998931884766
+      - country: NL
+        city: Zwolle
+        link: 'http://www.meetup.com/HackerDojoNL/'
+        name: Dutch Hacker Dojo
+        description: "<p>We are a group of hackers (programmers) located in Zwolle. The Hacker Dojo is a place where hackers come together to peer program and share knowledge on new technology, web frameworks and open source libraries.\_</p>\n<p><span>We love to hack the web and we have great interest in new technology and prototyping stuff. Our interests include</span><span>, but are most certainly not limited to</span><span>: controlling Arduino’s using Node, building responsive websites using Bootstrap and AngularJS, creating Chromecast apps, hacking the Pebble smartwatch, exploring Polymer and Web Components, create mobile apps using PhoneGap, discover Leap Motion and more.\_</span></p>\n<p><span>Every first friday of the month we host a new meetup. We simply pick a shared topic of interest and we spend our time prototyping and hacking something great. The goal of the meetup is a shared learning experience and above all to have fun.\_</span></p>\n<p><span>Come join us and let’s build our first autonomous Drone together!</span><br>\n\n</p>"
+        lon: 6.090000152587891
+        lat: 52.52000045776367
+      - country: UA
+        city: "Dnipropetrovs'k"
+        link: 'http://www.meetup.com/ScriptnCode/'
+        name: "Script'n'Code"
+        description: "Script'n'Code is an open meet-up, which unites like-minded people and give you a possibilitiy to dive into the script and functional languages world. You will get a chance to listen not only to Ukrainian geeks, but also find out the experience of IT-gurus from all over the world! Come and tell us about your ideas, get to know with IT-party, ask tricky questions to international fellows and just have a pleasant time around your old and new geek-friends :)"
+        lon: 35.040000915527344
+        lat: 48.45000076293945
+      - country: PT
+        city: Braga
+        link: 'http://www.meetup.com/bragajs/'
+        name: Braga.JS
+        description: |-
+          <p>Common ground for JS ehnthusiastics and Web aficionados in general.</p>
+          <p>Follow us on Twitter:&nbsp;https://twitter.com/braga__js</p>
+        lon: -8.430000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/b/0/e/600_448146926.jpeg'
+        lat: 41.54999923706055
+      - country: IT
+        city: Milano
+        link: 'http://www.meetup.com/MM-MeanMilan/'
+        name: 'M&M-Mean Milan'
+        description: "<p>M&amp;M Mean Milan, è una community nata dal volere di un gruppo di sviluppatori che dopo aver studiato lo stack MEAN e lavorato con questo hanno deciso di condividere le loro esperienze con tutti coloro che lo stanno utilizzando. La nostra community si propone di approfondire questa tecnologia, lo scopo è quello di conoscere meglio l’argomento, relazionarsi con altre persone che sviluppano in Mean e magari avere l’opportunità di trovare nuove collaborazion.</p> \n<p>MEAN è uno stack composto da quattro elementi: MongoDB , Node.js , Express , e AngularJS. È stato progettato per sviluppare applicazioni che necessitano di alte performance in operazioni di I/O.</p>"
+        lon: 9.1899995803833
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/a/a/3/600_433127779.jpeg'
+        lat: 45.459999084472656
+      - country: ES
+        city: Madrid
+        link: 'http://www.meetup.com/Redradix-Weekends/'
+        name: Redradix Weekends
+        description: '<p>Los weekends de Redradix son charlas cortas y eminentemente prácticas, talleres o conferencias donde se habla de temas interesantes en el mundo de la tecnología web. Es un evento abierto y gratis, reuniéndonos en las oficinas de Redradix. Solemos hacer uno al mes.</p>'
+        lon: -3.7100000381469727
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/b/600_448320059.jpeg'
+        lat: 40.41999816894531
+      - country: IS
+        city: Reykjavík
+        link: 'http://www.meetup.com/Reykjavik-Nodecopter/'
+        name: Reykjavík Nodecopter
+        description: |-
+          It's finally time!
+          And when I say finally time, I mean it's finally time to mess around with robots and node.js!
+
+          Oz Inc. would like to invite you to a amazing event that involves hacking on drones and has already been held in different cities around the world.
+
+          January 10th 2015 we will gather in Reykjavík University to do the following:
+
+          Listen to short talks about node.js.
+          Hack on drones in node.js.
+          Eat food and drink beers and sodas.
+          Have a kickass time.
+          Check out nodecopter.com for more info about nodecopter events and check out our github for more info about nodecopter Reykjavík.
+
+          Things you need:
+
+          5000ISK for registration.
+          Your own laptop.
+          Some programming experience.
+          We'll provide:
+
+          A single AR Drone 2.0 to mess around with (one per team).
+          Beer and pizzas.
+          Wifi!
+          Did we mention we'll let you mess around with a f'ing drone???
+          Afterwards we'll all meet up at Oz HQ to have beers, mingle and be merry.
+        lon: -21.920000076293945
+        lat: 64.13999938964844
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Azureoss/'
+        name: UK OSS on Windows Azure Platform Meetup
+        description: '<p>This group is open to anyone interested in discussing running Linux and OpenSource Software (OSS) on the Azure platform. "Microsoft ♥ Linux"</p>'
+        lon: -0.14000000059604645
+        lat: 51.5
+      - country: AT
+        city: Vienna
+        link: 'http://www.meetup.com/Vienna-AngularJS-Master-Class-Meetup/'
+        name: Vienna AngularJS Master Class Meetup
+        description: |-
+          <p>Vienna Tech Training Series is about learning the trending technologies and topics that will take your career to the next level. Because the&nbsp;training&nbsp;program is a&nbsp;whole package, it includes learning “how to code” and “how to market” your apps and websites.</p>
+          <p><br></p>
+          <p>The training series are focused on:</p>
+          <p>-&nbsp; Teaching and ”workshopping” trending topics</p>
+          <p>-&nbsp; Learning to code</p>
+          <p>-&nbsp; Marketing your webs and application</p>
+          <p>-&nbsp; Networking. This is how companies capture the best talent </p>
+          <p>-&nbsp; Providing a platform to expose your ideas</p>
+          <p><br></p>
+          <p>What can you expect from these trainings?</p>
+          <p>-&nbsp; VTTS is sponsored and supported by big tech companies</p>
+          <p>-&nbsp; The series will be filmed so you can watch the videos later on at home (included in the cost of the ticket)</p>
+          <p>-&nbsp; Lots of freebies and goodies for the “most active” participants</p>
+          <p>-&nbsp; Discounts for the next events</p>
+          <p><br></p>
+          <p>About the organiser: <br> Alejandro Rangel (<a href="https://www.linkedin.com/in/arangelp" class="linkified">https://www.linkedin.com/in/arangelp</a>) <br> </p>
+          <blockquote>
+           <p><span>A mobile frontend developer with more than 9 years working as a employee/freelance all around Europe and currently as Lead Game Developer in Greentube. I had worked with many clients in London, Vienna, Berlin and Barcelona. I had published more than 20 mobile applications in the last years.</span></p>
+          </blockquote>
+          <p><span><br></span></p>
+          <p><span>Jordi Rodriguez (<a href="https://www.linkedin.com/in/jrodriguez">https://www.linkedin.com/in/jrodriguezhttps://www.linkedin.com/in/jrodriguez</a>)</span></p>
+          <blockquote>
+           <p><span>A Digital Marketing Specialist with more than 8 years working in sales and Marketing, currently working as a freelance for small companies, startups and new projects. A jack of all trades but with the tech skills that anyone needs to become an entrepreneur.</span></p>
+          </blockquote>
+          <p> <br></p>
+        lon: 16.3700008392334
+        lat: 48.220001220703125
+      - country: PT
+        city: Lisbon
+        link: 'http://www.meetup.com/whatsyourstack-Lisbon/'
+        name: Whats Your Stack Lisbon
+        description: '<p>Startups explain their technology stack over drinks. Learn about the choices they made over databases, servers, programming languages, CDNs and frameworks - as well as what their favorite pizza joints are.</p>'
+        lon: -9.140000343322754
+        lat: 38.720001220703125
+      - country: DK
+        city: Copenhagen
+        link: 'http://www.meetup.com/Opbeat/'
+        name: Opbeat
+        description: This is a group for developers operating web applications on cloud infrastructure
+        lon: 12.569999694824219
+        lat: 55.68000030517578
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/BarcelonaJS/'
+        name: BarcelonaJS
+        description: '<p>Barcelona.JS is a usergroup focused on JavaScript and related topics. We meet regularly at the Mobile World Centre, C/ de Fontanella, 2 in Barcelona.</p>'
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/c/b/1/600_432151921.jpeg'
+        lat: 41.400001525878906
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/Meteor-Barcelona/'
+        name: Meteor Barcelona
+        description: |-
+          <p>Conoce a otros desarrolladores que utilizan <a href="http://meteor.com">Meteor</a>. Comparte tus conocimientos, aplicaciones, y aprende de ellos. Meteor es una plataforma de código abierto para la creación de aplicaciones web de alta calidad en una fracción del tiempo, tanto si eres un desarrollador experto o acabas de empezar.</p>
+          <p>Meet other developers using <a href="http://meteor.com">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.<br>
+
+          </p>
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/c/9/e/600_432220094.jpeg'
+        lat: 41.400001525878906
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/founderscoders/'
+        name: 'Founders & Coders'
+        description: '<p>Founders &amp; Coders runs a full-time no-fee coding bootcamp. We also run a number of meetups for people who are interested in our course, who want to learn more about programming, or who want help with their startup projects.&nbsp;</p>'
+        lon: -0.03999999910593033
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/5/6/b/600_442186443.jpeg'
+        lat: 51.529998779296875
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/ecomhackBerlin/'
+        name: ecomhack Berlin
+        description: |-
+          <p>There was a time when someone walked into store, had a chat with the store-owner and asked him which products he would recommend. The store-owner, knowing this person for years, would pull the right thing out of a shelf and turn the visitor into a happy customer. If the store-owner knew his trade really well, he would even anticipate his customers’ wishes and actively suggest something they did not know they needed - yet.&nbsp;</p>
+          <p>In this sense, personalization has always been a core principle of retail. And in this digital day and age, technical developments such data analysis and specialized APIs can make individualization and proactive personalization even more effective and provide interesting opportunities to merchants. With mobile devices and wearables learning more about their customers’ tastes and preferences, they can build better and more targeted applications and get a headstart against their competition.</p>
+          <p>New developments in hard- and software make it possible to reach online customers <br>far beyond their desktop computers and blur the boundaries between online and <br>“real” life. Emerging devices enable new forms of human-machine interaction and <br>redefine the way in which online retail is done. ecomhack.io 2015 is all about <br>mobile technology, emerging devices, keyboard-free interaction, a natural <br>shopping experience as an integral part of our everyday lives and the role of APIs in <br>shaping the future of e-commerce.</p>
+          <p>This weekend in Berlin is all about projects with an interesting approach to personalization and fresh ideas that make buying things more individual, more effective - and more fun. </p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/c/4/e/600_435584110.jpeg'
+        lat: 52.52000045776367
+      - country: RO
+        city: Iasi
+        link: 'http://www.meetup.com/Iasi-JS/'
+        name: Iasi JS
+        description: |-
+          <p>Iasi JS is the JavaScript User Group in Iasi. We're looking forward to locally build the community of JS enthusiasts.</p>
+          <p> </p>
+          <p>Stay tuned for our news and presentations at&nbsp;</p>
+          <p> </p>
+          <p><a href="https://www.facebook.com/iasiJS">https://www.facebook.com/iasiJS</a>&nbsp; <br> </p>
+          <p> </p>
+          <p>and</p>
+          <p> </p>
+          <p>www.iasijs.com</p>
+        lon: 27.56999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/1/2/8/600_432604392.jpeg'
+        lat: 47.16999816894531
+      - country: RS
+        city: Belgrade
+        link: 'http://www.meetup.com/JS-Belgrade-Meetup/'
+        name: JS Belgrade Meetup
+        description: |-
+          <p>JS Belgrade is JavaScript User Group from Belgrade. Our goal is to connect Belgrade's JavaScript community through monthly meetups.</p>
+          <p>More info on our website: <a>www.jsbelgrade.org</a>.</p>
+          <p>If you want to talk on JS Belgrade Meetup you can submit talk proposal here:&nbsp;<a>www.jsbelgrade.org/teme/</a></p>
+        lon: 20.5
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/7/d/3/600_436702483.jpeg'
+        lat: 44.83000183105469
+      - country: FR
+        city: Lyon
+        link: 'http://www.meetup.com/LyonJS/'
+        name: LyonJS
+        description: |-
+          <p>Le meetup LyonJS a pour but de rassembler les utilisateurs JavaScript de la ville de Lyon et de ses alentours. Ainsi nous organisons des réunions d'informations mensuelles ouvertes à tous et gratuites.</p>
+          <p>Le but est de se retrouver afin d'assister à des conférences dont le thème porte sur les technologies web et JavaScript en particulier.</p>
+          <p><span>Nous nous retrouvons ensuite autour d'un buffet en vue d'échanger nos impressions et de poursuivre la discussion.</span><br>
+
+          </p>
+        lon: 4.829999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/e/b/9/600_433108345.jpeg'
+        lat: 45.7599983215332
+      - country: RO
+        city: Cluj-Napoca
+        link: 'http://www.meetup.com/JavaScript-Cluj/'
+        name: JavaScript Cluj
+        description: |-
+          <p>Let's create a community for JavaScript in Cluj-Napoca, a place where you can learn tips, tricks, hacks, and frameworks with some of the best scripters around.<br><br>We host regular workshops and tech talks on a variety of different JavaScript topics. Show off cool stuff you've done and learn about what else is going on in the JS community.<br><br>We meet at ClujHUB (Pitesti 19). No matter what your level of experience is, we'd love to have you join us! No pressure, no mandatory presentations. Come, hang out, and hear great people talk about cutting edge scripting.<br></p>
+          <p><img src="http://photos2.meetupstatic.com/photos/event/d/4/5/0/600_436554352.jpeg"></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: 23.59000015258789
+        lat: 46.779998779296875
+      - country: IT
+        city: Milano
+        link: 'http://www.meetup.com/Meteor-Milano/'
+        name: Meteor Milano
+        description: "<p>Meet other developers using <a href=\"http://meteor.com\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 9.1899995803833
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/b/0/f/600_433347407.jpeg'
+        lat: 45.459999084472656
+      - country: LU
+        city: Luxembourg
+        link: 'http://www.meetup.com/JSLuxembourg/'
+        name: JSLuxembourg Meetup
+        description: "<p>JSLuxembourg is Luxembourg's JavaScript User Group. We organize monthly meetups that takes place at changing locations (Amazon Offices in Clausen, Technoport, theImpactory,..just to mention a few). This group is aimed at people that have an interest in JavaScript, either professionally or simply just for fun. For a meetup usually there is one main speaker presenting a topic for 30min and then we propose that people join in to give short (5-7 min) lightning talks. We will put our presentations and other documents on our github organization.(<a href=\"https://github.com/luxembourgjs\" target=\"_blank\" class=\"linkified\">https://github.com/luxembourgjs</a>)</p>"
+        lon: 6.119999885559082
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/f/5/2/600_433352594.jpeg'
+        lat: 49.619998931884766
+      - country: CH
+        city: Schaffhausen
+        link: 'http://www.meetup.com/node-js-meetup-schaffhausen/'
+        name: Node.js Meetup Schaffhausen
+        description: |-
+          <p>Bist du interessiert an Web Entwicklung? node.js, javascript, html, css etc. sind dein Leben, oder möchten es gerne werden? Teilst du dein Wissen gerne mit Anderen und möchtest neues lernen?&nbsp;</p>
+          <p>In dieser Gruppe möchten wir node.js Open Source Projekte vorstellen, diskutieren und über unsere Erfahrungen mit node.js austauschen.</p>
+          <p>Mich interessiert, ob es in der Region Schaffhausen begeisterte node.js Entwickler gibt. Für das erste Meeting würde ich eine Einführung in node.js machen.</p>
+        lon: 8.619999885559082
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/5/c/b/600_433573771.jpeg'
+        lat: 47.709999084472656
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/AzureDublin/'
+        name: Azure Dublin Meetup
+        description: "<p>This is Dublin's Azure Meetup. Here we will discuss anything Azure related. For developers, architects, DevOps, data scientists&nbsp;and IT professionals of all types. And yes it is open to Linux lovers and PhP, Java, Node.JS etc developers</p>"
+        lon: -6.25
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/a/5/a/600_433591322.jpeg'
+        lat: 53.33000183105469
+      - country: TR
+        city: Ankara
+        link: 'http://www.meetup.com/Javascript-Ankara/'
+        name: Javascript Ankara
+        description: "<p>Son yılların en yaygın dili JavaScript'in istemci ve sunucu tarafında kullanımlarını konuşacağımız, Ankara'daki JavaScript programcılarını kaynaştırmayı amaçlayan kullanıcı grubu</p>"
+        lon: 32.849998474121094
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/2/c/2/600_444569378.jpeg'
+        lat: 39.93000030517578
+      - country: RO
+        city: Bucharest
+        link: 'http://www.meetup.com/Bucharest-Angular-JS-Meetup/'
+        name: Bucharest Angular JS Meetup
+        description: |-
+          <p><span>This meet-up group has the purpose of creating a community around the AngularJS framework and related technologies.</span><br></p>
+          <p>Join us on Facebook:&nbsp;<span>https://www.facebook.com/groups/angularjs.bucharest/</span></p>
+        lon: 26.100000381469727
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/d/f/e/600_436879966.jpeg'
+        lat: 44.439998626708984
+      - country: BY
+        city: Minsk
+        link: 'http://www.meetup.com/Meteor-Minsk/'
+        name: Meteor Minsk
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started. <br> <br>Meteor Minsk community web: <a href=\"http://minsk.meteor.com\">minsk.meteor.com</a></p>"
+        lon: 27.549999237060547
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/c/5/6/600_434396406.jpeg'
+        lat: 53.90999984741211
+      - country: NL
+        city: Enschede
+        link: 'http://www.meetup.com/twentejs/'
+        name: Twente.js
+        description: |-
+          <p>Javascript user group for the east of The Netherlands.<br></p>
+          <p><br></p>
+          <p><a class="embedded" href="https://vimeo.com/121474814?portrait=0&amp;color=f6e629">https://vimeo.com/121474814?portrait=0&amp;color=f6e629</a></p>
+          <br>
+        lon: 6.889999866485596
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/7/5/e/600_434202846.jpeg'
+        lat: 52.220001220703125
+      - country: RO
+        city: Bucharest
+        link: 'http://www.meetup.com/BucharestJS/'
+        name: BucharestJS
+        description: |-
+          <p>BucharestJS is a developer group for anyone interested in Javascript. All skill levels are welcome. Stay tuned for details of BucharestJS meetups and get in touch if you want to get involved! We're also on Facebook (<a href="https://www.facebook.com/groups/1544555832466208/">https://www.facebook.com/groups/1544555832466208/</a>) and Twitter (<a href="https://twitter.com/bucharestjs">https://twitter.com/bucharestjs</a>)</p>
+          <p><br></p>
+          <p>PS: While HR people are more than welcome, HR spammy messages/posts/e-mails are NOT. These are the terms, take it or leave it!</p>
+        lon: 26.100000381469727
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/5/1/b/600_434349499.jpeg'
+        lat: 44.439998626708984
+      - country: CH
+        city: Lausanne
+        link: 'http://www.meetup.com/Frontend-Meetup-Romandie/'
+        name: Frontend Meetup - Romandie
+        description: '<p>Un meetup traitant de sujets comme les bonnes pratiques du développement Frontend, les dernières technologies et les retours sur expériences. Donc si tu veux partager un bout de code et une bière, rejoins-nous !</p>'
+        lon: 6.619999885559082
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/c/a/7/600_434264199.jpeg'
+        lat: 46.52000045776367
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Js-Star/'
+        name: Js-Star .Paris
+        description: "<p><span>JS-Star est un groupe de développeurs qui adorent échanger, c'est dans cet esprit que nous organisons ces meetups ! Le but est de partager nos expériences, questions, projets, problèmes entre nous, tout en passant une agréable soirée. <br>Chaque soirée sera découpée en deux grandes parties. En premier un thème sera abordé par des experts du sujet, puis en fin de soirée nous pourrons networker et échanger dans une ambiance détendue. <br>Nous vous attendons nombreux lors de ces soirées conviviales où nous pourrons discuter, apprendre et manger des pizzas !</span> <br></p>"
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/5/6/d/600_434717773.jpeg'
+        lat: 48.86000061035156
+      - country: DE
+        city: Köln
+        link: 'http://www.meetup.com/DevHouseFriday-Chillout/'
+        name: DevHouseFriday Chillout
+        description: '<p>DevHouseFriday is an event intended for creative and curious people interested in technology inspired by SuperHappyDevHouse.</p>'
+        lon: 6.96999979019165
+        lat: 50.95000076293945
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/MarkLogic-User-Group-NoSQL-Database-Technology/'
+        name: MarkLogic User Group Germany
+        description: "<p>Diese Gruppe ist für alle, die sich für NoSQL Technologie, für XML, XQeuery &nbsp;oder ähnliche Themen interessieren – für Einsteiger und Fortgeschrittene. Die NoSQL Datenbank Technologie kommt immer dann zum Einsatz, wenn relationale Datenbanken an ihre Grenzen stoßen. Bei unseren Treffen geben wir Tipps und Tricks, stellen Anwendungsbeisiele von Kunden vor oder geben einen Ausblick auf neue Entwicklungen. Wir freuen uns auf jeden Teilnehmer und den Austausch mit unseren Gruppenmitgliedern.</p>\n<p>The MarkLogic User Group (MLUG) &nbsp;is for users and/or fans of MarkLogic and those who are interested in learning more about MarkLogic, XML, XQuery and related technologies. MUGL meetups are free and open to anyone that wishes to attend. There is no formal membership for the group. Our meetings are held quarterly in different regions in Germany. <br></p>\n<p><i>Want to know more about MarkLogic?&nbsp; Read on&nbsp;<b>&gt;&gt;</b></i></p> \n<p>MarkLogic®&nbsp;is a new generation database platform that enables organisations to get more value from more data than ever before. Global enterprises and governments rely on MarkLogic to power intelligent, high performance applications aimed at analysing data for better insights and also running crucial day-to-day business operations. With MarkLogic, organisations achieve faster time-to-value than was possible with legacy databases, while minimising risk and improving data quality.</p> \n<p>MarkLogic is the only Enterprise NoSQL database—a powerful, agile, trusted database that has the speed and scale of NoSQL coupled with the enterprise features required.</p> \n<p>·&nbsp; Develop stronger applications faster with a flexible data model&nbsp;using Full-Stack JavaScript, JSON and Node.JS</p> \n<p>·&nbsp; Find relevant information easier with lightning fast, built-in search</p> \n<p>·&nbsp; Gain more intelligence in the data layer using semantics and bitemporal</p> \n<p>·&nbsp; Maintain data resiliency and consistency with ACID transactions, scalability and elasticity, certified security, &nbsp; and high availability and disaster recovery</p>\n<br>"
+        lon: 11.579999923706055
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/8/d/e/600_440246846.jpeg'
+        lat: 48.13999938964844
+      - country: DE
+        city: Siegen
+        link: 'http://www.meetup.com/Webentwicklung-in-Siegen-und-Umgebung/'
+        name: Webentwicklung in Siegen und Umgebung
+        description: '<p>Dies ist eine Gruppe für (Web)-Entwickler aus Siegen und Umgebung. Sie soll eine lockere Kooperation verschiedener Webentwickler ermöglichen, die sich regelmäßig zum Austausch über die neusten Webtechnologien treffen und sich gegenseitig bei der Webentwicklung unterstützen. Egal ob Du gerade auf Schienen, einer Insel, einem Elefanten und/oder auf Kaffee bist oder Du noch gar keine Ahnung davon hast, was damit gemeint ist: Du bist herzlich eingeladen beizutreten und mit zu machen!</p>'
+        lon: 8.010000228881836
+        lat: 50.869998931884766
+      - country: FR
+        city: Digne-les-Bains
+        link: 'http://www.meetup.com/Digne-les-Bains-JavaScript-Meetup/'
+        name: Digne-les-Bains JavaScript Meetup
+        description: 'Pour ceux qui veulent apprendre à coder et ceux qui veulent améliorer leur pratique du code. Javascript côté client et Javascript côté serveur. Mobile, Applications, Sites web : on peut tout faire avec Javascript. Réunissons-nous à Digne-les-Bains pour échanger!'
+        lon: 6.230000019073486
+        lat: 44.099998474121094
+      - country: IT
+        city: Milano
+        link: 'http://www.meetup.com/Intel-Developers-Milan/'
+        name: Intel Developers Milan
+        description: "Oltre a progettare processori, la Intel ha una divisione sviluppatori (conosciuta come Intel Developer Zone) che si occupa di creare strumenti in grado di far progredire il mondo dei computer e l'industria dei videogiochi. Lo scopo di questo Meetup è quello di riunire sviluppatori HTML5, Android e Windows 8 interessati a questi nuovi strumenti e innovazioni.\n\nIn questa serie di incontri ti invitiamo a presentare una demo del tuo codice e a interagire con un'audience di persone come te, con una forte enfasi sul problem-solving e sulle buone prassi. Tutti gli sviluppatori sono i benvenuti, sia per HTML5 cross platform che per lo sviluppo nativo sotto Android / Win 8, con una discussione interattiva che non dovrebbe superare i 25-30 minuti. \n\nLe presentazioni saranno in \"ottica sviluppatore\", con alcuni professionisti del settore ed oratori invitati a presentare le demo fianco a fianco con i partecipanti all'incontro. Non è necessario che tu sia uno sviluppatore esperto, portaci solo i tuoi hack ed altri progetti ai quali stai lavorando ed unisciti a noi per una serie di meetup Ultracode a base di pizza e birra."
+        lon: 9.1899995803833
+        lat: 45.459999084472656
+      - country: GB
+        city: Leigh-on-Sea
+        link: 'http://www.meetup.com/Southend-on-Sea-Web-Development-Meetup/'
+        name: Southend on Sea Web Meetup
+        description: "<p>I'm a web developer. I loving going to meetups in London, so I've decided to set one up locally. Whether you're a developer or designer, freelancer or employee, front end or back end, if you live in or around Southend and you do stuff on the web, I want to say \"hi\".</p>"
+        lon: 0.6700000166893005
+        lat: 51.54999923706055
+      - country: DE
+        city: Karlsruhe
+        link: 'http://www.meetup.com/Meteor-Karlsruhe/'
+        name: Meteor Karlsruhe
+        description: 'Austausch rund ums zukunftsweisendste Web-Framework Meteor. Ideen finden, Wissen teilen, gemeinsame Projekte initiieren.'
+        lon: 8.399999618530273
+        lat: 49
+      - country: ES
+        city: Valencia
+        link: 'http://www.meetup.com/ValenciaJS/'
+        name: ValenciaJS
+        description: '<p>A meetup in Valencia for people that hack JavaScript, <a href="https://github.com/Valencia-JS/talks">previous talks</a>. <a href="http://valenciajs.herokuapp.com/">Join to our Slack channel</a>.</p>'
+        lon: -0.38999998569488525
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/8/a/9/600_435626793.jpeg'
+        lat: 39.47999954223633
+      - country: NL
+        city: Boxmeer
+        link: 'http://www.meetup.com/Tech-Boxmeer/'
+        name: Boxmeer Tech Meetup
+        description: |-
+          <p>This is a group for developers. Would be nice to meet each other and have some knowledge sharing.</p>
+          <p>Idea is to meet monthly and have some speakers.</p>
+        lon: 5.940000057220459
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/7/5/1/600_443819217.jpeg'
+        lat: 51.65999984741211
+      - country: PT
+        city: Lisbon
+        link: 'http://www.meetup.com/JSLisbon/'
+        name: 'JS Lisbon (Frontend & Backend)'
+        description: |-
+          <p>Node.js, ReactJS, ExpressJS, Hapi.js, JavaScript, Neo4j, MongoDB...</p>
+          <p><span>MeetUps, Hackatons and Casual Coding sessions for all JS Ninjas in the Lisbon Area!</span>&nbsp;</p>
+          <p><span>[MeetUps during the summer will be held in primarily in Cascais/Estoril]</span> <br></p>
+        lon: -9.140000343322754
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/2/6/8/600_435664712.jpeg'
+        lat: 38.720001220703125
+      - country: SE
+        city: Stockholm
+        link: 'http://www.meetup.com/ReactJS-Stockholm/'
+        name: ReactJS Stockholm
+        description: |-
+          <p>ReactJs is a fun, easy to use Javascript library built at Facebook.</p>
+          <p><a href="http://facebook.github.io/react/" class="linkified">http://facebook.github.io/react/</a></p>
+          <p>We've found it to be incredibly easy to ramp up and fun, so we will start hosting react meetups and hackathons to experiment with the library and build on top of it.</p>
+          <p>Join us if you'd like to learn more or if you have your own ReactJs experience to share that others can benefit from.&nbsp;</p>
+        lon: 18.06999969482422
+        lat: 59.33000183105469
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/Belgian-Open-Badges-Meetup/'
+        name: Belgian Open Badges Meetup
+        description: |-
+          <p>The Belgian Open Badges group meets around the topic of Mozilla Open Badges</p>
+          <p>Badges: the open digital credentials for online learning &amp; getting recognition for skills and achievements that happen outside of school: <a href="http://openbadges.org" class="linkified">http://openbadges.org</a>&nbsp;</p>
+          <p>Main Git repository: <a href="https://github.com/mozilla/openbadges-backpack" class="linkified">https://github.com/mozilla/openbadges-backpack</a>&nbsp;</p>
+          <p>This group is for earners, issuers, ecosystem developers, or anyone interested in helping to spread Mozilla's great Open Badge standard to Belgium!</p>
+        lon: 4.329999923706055
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/1/8/2/600_446753634.jpeg'
+        lat: 50.83000183105469
+      - country: NL
+        city: Tilburg
+        link: 'http://www.meetup.com/Tilburg-Dev/'
+        name: Tilburg Dev
+        description: |-
+          <p>Quarterly meetup on dev related topics in Tilburg. Every meetup will have different topics, e.g. a new web dev framework or a talk about a dev startup launch.</p>
+          <p>Location and first meetup tba.</p>
+        lon: 5.070000171661377
+        lat: 51.56999969482422
+      - country: PT
+        city: Lisbon
+        link: 'http://www.meetup.com/Lisboa-WebRTC-TADHack-Meetup/'
+        name: 'Lisboa TADSummit & WebRTC & TADHack Meetup'
+        description: |-
+          <p><b>WebRTC</b> and <b>API</b>'s are disrupting (tele)communications and software ! We're building an <b>European community</b> of those who believe that this technology is more than some nice features to build alternative solutions to Skype. If you believe like us that WebRTC is a movement for the next years, then please join us to build this community, share ideas, projects and some nice food and drinks. <br></p>
+          <p>This Meetup is associated with:&nbsp;</p>
+          <p><b>TADSummit</b> (<a href="http://tadsummit.com/">http://tadsummit.com/</a>).&nbsp;<span>The Telecom Application Developer Summit (TADS) is a grass roots initiative to build an open ecosystem focused on helping businesses use telecom capabilities in their applications, services and business processes.&nbsp;</span><span>We bring together the leaders in the industry – across service providers, technology providers, developers, and enterprises – to work on getting new services to market and making business success in new services an everyday reality. On 17th and 18th November TADSummit will be held at&nbsp;CORINTHIA HOTEL LISBON,&nbsp;</span><span>Av. Columbano Bordalo&nbsp;</span><span>Pinheiro&nbsp;105, Lisbon</span></p>
+          <p><b>TADHack</b> (<a href="http://tadhack.com/2015/tadhack-global/" class="linkified">http://tadhack.com/2015/tadhack-global/</a>). TADHack is the international community of telecom app developers! This is the <b>ONLY GLOBAL MEETING</b> place for developers who want to learn, share, code and create using the tools and technologies available in telecommunications. On <b>13 &amp; 14th</b> June, the <b>worldwide TADHack hub was in @Instituto Superior Técnico</b>/Campus Taguspark.</p>
+        lon: -9.140000343322754
+        lat: 38.720001220703125
+      - country: NL
+        city: Utrecht
+        link: 'http://www.meetup.com/purescript-nl/'
+        name: Dutch PureScript Enthusiasts
+        description: "<p>Dutch Purescript programmers and enthusiasts unite! Let's meet to discuss, learn and teach PureScript together.</p>"
+        lon: 5.110000133514404
+        lat: 52.099998474121094
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/London-JavaScript-Community/'
+        name: London JavaScript Community
+        description: |-
+          <p><img src="https://lucamezzalira.files.wordpress.com/2015/04/bannermeetuppage-e1428103811502.png"></p>
+          <p> <br></p>
+          <p>This is a group for all the JavaScript developers that are interested to learn more about JavaScript, share development experiences or techniques and why not, find new friends to share our passion!</p>
+          <p>I started the group in order to discuss the latest JS libraries and/or frameworks, sharing open source projects, discuss about best practices, exploring new possible techniques to apply inside our projects or talking about tools we are using in our projects pipeline.</p>
+          <p>If you are passionate about these things or if you are just curious to meet new people passionate about JavaScript feel free to join this community!</p>
+          <p>Remember to follow us on <a href="https://www.linkedin.com/groups?mostRecent=&amp;gid=8282921">Linkedin</a>,&nbsp;<a href="https://twitter.com/london_JS">Twitter</a>&nbsp;and <a href="http://www.facebook.com/londonJSCommunity">Facebook</a> too!</p>
+        lon: -0.10000000149011612
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/8/4/5/600_435914405.jpeg'
+        lat: 51.52000045776367
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/AngularJS-Beers/'
+        name: 'AngularJS & Beers'
+        description: |-
+          <p><img src="http://photos2.meetupstatic.com/photos/event/7/8/e/8/600_444510952.jpeg"></p>
+          <p><a href="http://lameva.barcelona.cat/barcelonacultura/en/descobreix/bcn-innovacio-angular-beers-eng#.Vl4b4N-rRE4">AngularJS &amp; Beers. Informal event to socialise with AngularJS people.</a>&nbsp; <br>Express your motivations, share your ideas and play together creating awesome things in team.</p>
+          <p>We like to hack, learn, share and&nbsp;having fun in group while we are using AngularJS.&nbsp;<span>All experience levels and backgrounds are welcome. We love get action doing things. Join us!</span></p>
+          <p><span> <br></span></p>
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/2/4/b/600_447577451.jpeg'
+        lat: 41.400001525878906
+      - country: GR
+        city: Athens
+        link: 'http://www.meetup.com/Athens-AngularJS-Meetup/'
+        name: Athens AngularJS Meetup
+        description: '<p>A group focused on the goodies javascript brings to applications development. Of course AngularJS is the leader to create and structure responsive applications, SPA and realtime interfaces no matter which language we use for the backend (php5, nodeJS, ruby etc). Many other players try to make some impression like ReactJS, EmberJS so a modern developer has to keep learning and modernising his/her skills. This group is created for guys who really want to follow latest web development techniques and love javascript. Come join us and just share your experience with us because learning is a never ending process!!</p>'
+        lon: 23.729999542236328
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/6/d/c/600_436114524.jpeg'
+        lat: 37.97999954223633
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/Dublin-Node-js-Meetup/'
+        name: Dublin Node.js Meetup
+        description: |-
+          <p>Hello all Noders! Node.js Dublin is a monthly meetup for all things Node.js, we have been running this meetup for two years now, and are still going strong. If you interested in Node.js, and want to hear top quality talks, join our Node family! (There will also be free beer and pizza every month!)</p>
+          <p>We are currently looking for a new venue, our next meetup will be at the end of May, so stay tunned!</p>
+        lon: -6.25
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/3/d/e/600_436134238.jpeg'
+        lat: 53.33000183105469
+      - country: DE
+        city: Düsseldorf
+        link: 'http://www.meetup.com/Phone-API-Hackathon-Dusseldorf/'
+        name: Phone API Hackathon Düsseldorf
+        description: 'Gemeinsam wollen wir coole neue Ideen im Telefonnetz umsetzen und endlich mal wieder zeigen, dass Telefonie noch viele spannende Möglichkeiten bietet. Jeder kann mitmachen und mit dem eigenen Projekt teilnehmen. Für das leibliche Wohl sorgt die großartige sipgate Küche und am Ende werden die besten Projekte mit einem tollen Preis belohnt.'
+        lon: 6.789999961853027
+        lat: 51.2400016784668
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Mean-Mongo-Express-Angular-Node/'
+        name: Mean - Mongo Express Angular Node
+        description: '<p>the comunity around the Mean stack Mongo Express Angular Node</p>'
+        lon: -0.10000000149011612
+        lat: 51.52000045776367
+      - country: CH
+        city: Mels
+        link: 'http://www.meetup.com/SuedostCH-Softwareentwickler-Meetup/'
+        name: 'Sarganserland, FL, GR Softwareentwickler Meetup'
+        description: '<p>Aufruf an alle Softwareentwickler aus dem Raum Sarganserland, Fürstentum Liechtenstein und Graubünden sich regelmässig zum Know-How Austausch zu treffen. Es sollen alle Themen rund um die Softwareentwicklung, Architektur, DevOps, Requirements Engineering, etc. behandelt werden. Dabei geht es nicht primär um die eingesetzte Technologie. Es sollen jedoch trotzdem technologie bezogene Themen behandelt werden. Es wäre schön, wenn sich Entwickler aus allen Programmiersprachen, sei es Java, C#, C, C++, F#, Delphi, Pearl, Pascal, Cobol oder bekannte Web Script Sprachen wie AngularJS, NodeJS, etc. treffen, um gemeinsam Erfahrungen auszutauschen.</p>'
+        lon: 8.40999984741211
+        lat: 47.04999923706055
+      - country: ES
+        city: Sevilla
+        link: 'http://www.meetup.com/Bitnami-Sevilla/'
+        name: Bitnami Sevilla
+        description: '<p>Desde Bitnami queremos contribuir al conocimiento de las nuevas tecnologías en Sevilla, organizando encuentros y talleres relacionados con las tecnologías del desarrollo software y de Cloud Computing.</p>'
+        lon: -5.980000019073486
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/7/3/7/600_437006423.jpeg'
+        lat: 37.400001525878906
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/Women-Who-Code-Berlin-Germany/'
+        name: Women Who Code Berlin
+        description: |-
+          <p>Mission:</p>
+          <p>Women Who Code is a global nonprofit organization dedicated to inspiring women to excel in technology careers by creating a global, connected community of women in technology. The organization tripled in 2013 and has grown to be one of the largest communities of women engineers in the world.</p>
+          <p>Empowerment:</p>
+          <p>Women Who code is a&nbsp;professional community for women in tech.&nbsp;We provide an avenue for women to pursue a career in technology, help them gain new skills and hone existing skills for professional advancement, and foster environments where networking and mentorship are valued.</p>
+          <p>Key Initiatives:</p>
+          <p>Free technical study groups</p>
+          <p>Events featuring influential tech industry experts and investors</p>
+          <p>Hack events</p>
+          <p>Career and leadership development</p>
+          <p>Current and aspiring coders are welcome.&nbsp;</p>
+          <p>Bring your laptop and a friend!&nbsp;</p>
+          <p>Support Women Who Code:</p>
+          <p><a href="http://womenwhocode.com/donate">Donating to Women Who Code</a>, Inc.&nbsp;(#46-4218859) directly impacts our ability to efficiently run this growing organization, helps us produce new programs that will increase our reach, and enables us to expand into new cities around the world ensuring that women and girls everywhere have the opportunity to pursue a career in technology.</p>
+          <p>Women Who Code (WWCode) is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/womenwhocode">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a></p>
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/5/7/9/600_437105497.jpeg'
+        lat: 52.52000045776367
+      - country: RO
+        city: Cluj-Napoca
+        link: 'http://www.meetup.com/hello-js/'
+        name: hello.js
+        description: hello.js - a series of tech events for the JavaScript Community of Cluj
+        lon: 23.59000015258789
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/e/c/e/600_445720654.jpeg'
+        lat: 46.779998779296875
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Full-Stack-Software-Development-London/'
+        name: Full Stack Development London
+        description: '<p>This group is for anyone interested in meeting up to share and learn about different areas of the stack, from frontend to DevOps.</p>'
+        lon: -0.10000000149011612
+        lat: 51.52000045776367
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Formation-Baliz/'
+        name: Formation baliz.org
+        description: "<p>Des formations pensées pour les artisans du web. Votre niveau importe peu. Pendant nos séances, vous apprendrez les rudiments du web actuel, en découvrant avec un expert les meilleurs techniques javascript. Des bases à la création d'une application mobile, vous apprendrez à coder et améliorer vos connaissances.</p>"
+        lon: 2.3399999141693115
+        lat: 48.86000061035156
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/ReactJS-Barcelona/'
+        name: ReactJS Barcelona
+        description: '<p>We are the first meetup group in Barcelona about Facebook React.Js. We aim to organize regular events talking about React.js, Flux and all other libraries related to it. We also want to participate to React and Javascript conferences together. Starting with ReactEurope on July 2-3, 2015 in Paris.</p>'
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/c/6/8/600_437628232.jpeg'
+        lat: 41.400001525878906
+      - country: FR
+        city: Strasbourg
+        link: 'http://www.meetup.com/Strasbourg-Nodejs/'
+        name: Strasbourg Node.js
+        description: |-
+          <p>En permettant de créer des applications performantes qui encouragent la productivité,l’usage de Node.js, le Javascript côté serveur, a littéralement explosé en quelques années : de nombreuses sociétés font confiance à ce langage de programmation et la communauté grossit de jour en jour.</p>
+          <p><br>Le rôle de la communauté Node.js Strasbourg est de regrouper les développeurs de tous&nbsp;<span>niveaux s’intéressant à cette technologie au travers de soirées techniques de différents types : conférence, live coding et coding dojos.&nbsp;</span></p>
+          <p>Rejoignez-nous vite !</p>
+        lon: 7.75
+        lat: 48.58000183105469
+      - country: ES
+        city: Palma
+        link: 'http://www.meetup.com/Mallorca-Cassandra-Users/'
+        name: Mallorca Cassandra Users  - by DataStax -
+        description: "<p>The Apache Cassandra Project develops a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. This Apache Cassandra User Group is a highly awesome meetup group, bringing together cool people to talk about our favorite NoSQL implementation, Apache Cassandra.</p>"
+        lon: 2.6500000953674316
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/6/6/9/600_437682601.jpeg'
+        lat: 39.56999969482422
+      - country: ME
+        city: Podgorica
+        link: 'http://www.meetup.com/wavedevs/'
+        name: Wave Devs Meetup
+        description: |-
+          <p>It's group of passionate geeks who live near the sea. We like create useful thinks, cool websites, mobile apps, robots and many other things. And finally organise events, where we share our knowledge. If you like technology, like create new things and share your experience please join us. We always open for new members. We meet once a month at the one of town of Montenegro usually it's Kotor or Budva, but can be Herceg Novi and any other on a sea shore like Podgorica, Bar, Tivat and etc.</p>
+          <p>Official website:&nbsp;<a href="http://wave-developers.github.io/">http://wave-developers.github.io/</a></p>
+        lon: 19.280000686645508
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/9/8/600_447180920.jpeg'
+        lat: 42.470001220703125
+      - country: GR
+        city: Athens
+        link: 'http://www.meetup.com/GreeceJS/'
+        name: GreeceJS
+        description: |-
+          <p>Welcome to GreeceJS!&nbsp;</p>
+          <p>A bi-monthly celebration and exploration of the JavaScript programming language. This is a place to share knowledge, ask questions, learn and grumble. If you are interested in speaking or sponsoring please contact one of the organizers.&nbsp;</p>
+          <p><span>Sign up and join us!</span> <br></p>
+        lon: 23.729999542236328
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/4/6/0/600_438733408.jpeg'
+        lat: 37.97999954223633
+      - country: DE
+        city: Saarbrücken
+        link: 'http://www.meetup.com/AngularJS-Saarbrucken/'
+        name: AngularJS Saarbrücken
+        description: "<p>AngularJS Saarbrücken is a group around the AngularJS framework and related technologies. We're open to anyone interested in the topic. Whether you're a beginner or expert, come along and have a seat.</p>"
+        lon: 6.96999979019165
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/7/3/4/600_438539188.jpeg'
+        lat: 49.25
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/Dublin-TypeScript-Meetup/'
+        name: Dublin TypeScript Meetup
+        description: "TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. In this Meetup, we teach and learn effective ways to use Typescript, share cool projects we've built using the language, and do hands-on practice projects together."
+        lon: -6.25
+        lat: 53.33000183105469
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/nodeday/'
+        name: nodeday
+        description: |-
+          <p>nodeday is a Node.js conference by the enterprise, for the enterprise. This one-day industry conference brings together people from companies that have adopted or are planning to adopt Node.js, and focuses on the issues that these companies face. It gives participants a forum to discuss and share their experiences with Node.js, share advice, tips and tricks, and drive forward both the technology and the community.&nbsp;</p>
+          <p> <br></p>
+          <br>
+          <p> <br></p>
+          <p> <br></p>
+        lon: -6.25
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/6/e/0/600_446105856.jpeg'
+        lat: 53.33000183105469
+      - country: DE
+        city: Karlsruhe
+        link: 'http://www.meetup.com/KarlsruheJS/'
+        name: 'KarlsruheJS – JavaScript, HTML5 and NodeJS Meetup'
+        description: '<p>KarlsruheJS ist ein regelmäßiges Treffen von JavaScript-Entwicklern in Karlsruhe. <br>Organisiert wird die Gruppe von Evgenij Terehov und Kahlil Lechelt.</p>'
+        lon: 8.399999618530273
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/f/0/c/600_444247948.jpeg'
+        lat: 49
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Aurelia-Paris/'
+        name: Aurelia Paris
+        description: |-
+          <p>Aurelia + JavaScript (ES201x) + Paris = ♥</p>
+          <p>Nous sommes un groupe de développeurs enthousiastes, spécialisés en Javascript et curieux à propos du framework Aurelia.</p>
+          <p>Aurelia c'est quoi ? Probablement Angular 2 en propre. Le futur, quoi ! <br></p>
+          <p>Site web : <a href="http://aurelia.paris" class="linkified">http://aurelia.paris</a> (pas encore prêt !) <br></p>
+          <p>Hashtag twitter : #aureliaparis</p>
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/e/0/f/600_439076847.jpeg'
+        lat: 48.86000061035156
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Meetup-des-utilisateurs-de-Cozy-Cloud-en-France/'
+        name: Meetup des utilisateurs de Cozy Cloud en France
+        description: "<p>Venez rencontrer les développeurs de Cozy Cloud et les utilisateurs. On discute de l'évolution du produit, de ce qu'on pourrait y rajouter, des inévitables bogues qu'il faut résoudre en priorité ou des fonctionnalités pas faciles à comprendre. L'ambiance y est très détendue, la bonne humeur est de mise et on finit presque toujours par goûter à diverses boissons fermentées, sous prétexte que les problèmes rencontrés dans le logiciel libre sont presque tous solubles dans le houblon !</p>"
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/d/0/600_443043792.jpeg'
+        lat: 48.86000061035156
+      - country: DE
+        city: Frankfurt
+        link: 'http://www.meetup.com/Frankfurt-Google-Polymer-Webcomponents-Meetup/'
+        name: 'Frankfurt Google Polymer & Webcomponents Meetup'
+        description: "This is a group for those interested in the web components philosophy for the development of modern web and mobile applications. With web components you can basically create custom reusable HTML tags including styling und functionality. Discuss concepts like shadow DOM, the new declarative vs. imperative coding approach. Let's share our experience with the Google Polymer Framework."
+        lon: 8.680000305175781
+        lat: 50.119998931884766
+      - country: NL
+        city: Rotterdam
+        link: 'http://www.meetup.com/Lets-connect-now/'
+        name: "Let's connect (entrepreneurs, designers and developers)"
+        description: |-
+          <p>Hi meetup'ers!&nbsp;</p>
+          <p><span>This group is all about bringing entrepreneur/founders, developers and designers together. Now a days there are plenty of meetup groups. But this group is different, this group is not just for the designers.. or the developer.. No, it's a group to bring all these different kind of people with different kind of knowledge and specialties together.&nbsp;</span><br></p>
+          <p><span><b>This group is for:</b>&nbsp;</span></p>
+          <p><span>- The guy with the fantastic idea, aka "The entrepreneur, the founder"&nbsp;</span></p>
+          <p><span>- Back-end/Web app developers with knowledge of the newest frameworks like AngularJS, NodeJS etc.&nbsp;</span></p>
+          <p><span>- Frontenders/designers with knowledge to design for web / web-apps.&nbsp;</span></p>
+          <p><span><br></span></p>
+          <p><span><b><i>Why this group?&nbsp;</i></b></span></p>
+          <p><span>I'm Remi Hammerstein and I've an idea. I'm looking for one or more co-founders who see business in my idea and wanna help me build a web app and be part of this startup/company.</span><br></p>
+          <p>I can't be the only one who is looking for a partners/co-founders to work with, so entrepreneurs/starters you're very welcome to join this group! My vision is to bring people together with the right knowledge to start and build new web-apps and companies together.</p>
+          <p><br></p>
+          <p><i>&nbsp;"Nobody have the knowledge to start or run a company all by himself."</i></p>
+        lon: 4.480000019073486
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/b/1/3/600_439039219.jpeg'
+        lat: 51.93000030517578
+      - country: GB
+        city: Dartford
+        link: 'http://www.meetup.com/North-Kent-Web-Development-Meetup/'
+        name: North Kent Web Development Meetup
+        description: |-
+          <p>This meetup group is open to all with an interest in web development and design to discuss tools and techniques useful to both developers and designers.&nbsp;</p>
+          <p>The meetup will include at least one presentation followed by Q&amp;A and general discussion. Snacks and drinks will be provided!!!&nbsp;</p>
+          <p>We will schedule the meetup as regular as interest and participation allows.</p>
+        lon: 0.2800000011920929
+        lat: 51.40999984741211
+      - country: ES
+        city: Las Palmas
+        link: 'http://www.meetup.com/Gran-Canaria-JavaScript-Community/'
+        name: Canarias JavaScript Community
+        description: '<p>Grupo para los amantes de este lenguaje de programación que quieran compartir sus experiencias, reunirse, debatir y también aprender de otros compañeros o todos juntos ha hacer un mejor JavaScript.</p>'
+        lon: -15.430000305175781
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/c/3/d/600_439779997.jpeg'
+        lat: 28.100000381469727
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/JS-Coding-Nights-Munich/'
+        name: JavaScript Coding Nights Munich
+        description: |-
+          <p>Come together to improve your JavaScript skills, learn new technologies and meet other javascripters.</p>
+          <br>
+          <p>Meetup format:</p>
+          <p>•&nbsp;30 minutes food, drinks and friendly banter</p>
+          <p>•&nbsp;15 minute presentation on the topic of the day&nbsp;</p>
+          <p>•&nbsp;2h coding <br></p>
+          <p>•&nbsp;15 minute wrap up of the day</p>
+          <p> <br></p>
+          <p>You can work on:</p>
+          <p>•&nbsp;topic of the day&nbsp;</p>
+          <p>•&nbsp;javascript basics&nbsp;</p>
+          <p>•&nbsp;own projects&nbsp;</p>
+          <p>•&nbsp;<span>other people's projects</span></p>
+          <br>
+          <p>All experience levels are welcome.</p>
+        lon: 11.579999923706055
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/1/4/6/600_440081286.jpeg'
+        lat: 48.13999938964844
+      - country: DE
+        city: Mannheim
+        link: 'http://www.meetup.com/Hackschool/'
+        name: Hackschool
+        description: |-
+          <p> <br><b>GERMAN - DEUTSCH</b></p>
+          <p>Technik und Code gemeinsam erleben und verstehen.</p>Bei der Hackschool steht die Atmosphäre und das freie Lernen im Vordergrund. Dabei bietet Hackerstolz Hilfe zur Selbsthilfe.
+          <p>Mitmachen kann Jede und Jeder; die Gruppe fokussiert sich auf Kinder und Erwachsene ab 10 Jahren. Bitte bringt all eure Neugierde und Fragen mit! Vorkenntnisse sind nicht erforderlich, da mit individueller Betreuung auf die einzelnen Fähigkeiten eingegangen wird.</p>
+          <p>Ein eigenes Laptop wäre von Vorteil, es gibt aber auch Geräte vor Ort, die jeder mitverwenden kann. <br> <br> <br><b>ENGLISH - ENGLISCH</b></p>
+          <p>Let's both experience and understand tech and code together.</p>
+          <p>The hackschool empowers open learning with an atmosphere that helps you help yourself and others.</p>
+          <p>Everyone is invited to take part; the group is focussing on kids and grown-ups aged 10+. Please bring all your curiosity and questions with you! No experience required beforehand, as we offer an individual mentor-based training for each skillset.</p>
+          <p>An own Laptop would be awesome, but isn't required - we have some available that everyone can use. <br></p>
+        lon: 8.470000267028809
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/a/2/c/600_443867660.jpeg'
+        lat: 49.5
+      - country: PL
+        city: Warsaw
+        link: 'http://www.meetup.com/React-Warsaw/'
+        name: React Warsaw
+        description: |-
+          <p><a href="http://facebook.github.io/react/">React</a> is a fun, easy to use Javascript library built at Facebook for web and mobile. It has changed the way we think about client-side applications through concepts such as the virtual dom, one-way data flow, immutable data structures and isomorphism.</p>
+          <p>This is a group for anyone who has experience working with the React library or would like to learn more about it.</p>
+          <p>We meet once a month, generally have 2 speakers and loads of Q&amp;A, pizzas and beer.</p>
+          <p>Join us if you'd like to learn more or if you have your own React experience to share that others can benefit from. If you're interested in giving a talk, write us here.</p>
+          <p>See you soon!</p>
+          <p><a href="http://facebook.github.io/react/" class="linkified"></a></p>
+        lon: 21.020000457763672
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/0/6/3/600_445853347.jpeg'
+        lat: 52.2599983215332
+      - country: GB
+        city: Temple Meads
+        link: 'http://www.meetup.com/Bristol-MEAN-School/'
+        name: Bristol MEAN School
+        description: '<p>Single page web apps and technologies such as MongoDB, Express, AngularJS and NodeJS are hot right now; however not many of us get to use these technologies in our day jobs. This meetup group is aimed at beginners through to pros and aims to produce an environment where we all can learn something new!</p>'
+        lon: -2.5799999237060547
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/f/e/4/600_439876356.jpeg'
+        lat: 51.45000076293945
+      - country: DE
+        city: Darmstadt
+        link: 'http://www.meetup.com/DarmstadtJS/'
+        name: 'DarmstadtJS - JavaScript, AngularJS, React, Node.js  Meetup'
+        description: '<p>Diese Gruppe ist für begeisterte JavaScript Entwickler aber auch für interessierte Leute die sich von JavaScript begeistern lassen wollen :-)</p>'
+        lon: 8.640000343322754
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/5/1/3/600_439929491.jpeg'
+        lat: 49.869998931884766
+      - country: CZ
+        city: Prague
+        link: 'http://www.meetup.com/ngParty/'
+        name: ngParty
+        description: '<p>This meetup is for all interested in modern apps development, currently we are mainly focusing on Angular framework, but we are open to all nexgen technologies.</p>'
+        lon: 14.430000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/1/7/2/600_447488562.jpeg'
+        lat: 50.08000183105469
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Paris-Full-Stack-JavaScript-Meetup/'
+        name: Paris Full Stack JavaScript Meetup
+        description: '<p>Groupe destiné aux développeurs JavaScript, experts ou curieux, qui souhaitent échanger autour du concept <a href="http://www.meetup.com/Paris-Full-Stack-JavaScript-Meetup/pages/Full_Stack_JavaScript/">Full Stack JavaScript</a>.</p>'
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/5/1/5/600_440082261.jpeg'
+        lat: 48.86000061035156
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/Munich-Fullstack-Dojo-AngularJS-Node-js/'
+        name: Munich Full-Stack Dojo (AngularJS + Node.js)
+        description: '<p>- Code Linting/Sharing coding best practices <br>- Dojos in small groups (solve problems &amp; discuss solutions) <br>- Hackathons</p>'
+        lon: 11.579999923706055
+        lat: 48.13999938964844
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/javascript-lab-adam/'
+        name: JavaScript Lab Amsterdam
+        description: |-
+          <p>We love JavaScript and we thought it would be a great idea to put together a place where people can talk, meet and share their knowledge to bring their skills to the next level. <br>So join us and let's get better at doing this, together.</p>
+          <p> <br></p>
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/7/b/e/600_440858846.jpeg'
+        lat: 52.369998931884766
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/HackTrain-Innovating-at-200km-h/'
+        name: HackTrain - Innovating at 200km/h
+        description: "HackTrain is a network of innovators and technologists that are ready to evangelise the railway industry. An initiative to bring innovation to the railway industry through a series of immersive and unique meetups, hackathons and accelerators. What makes the HackTrain hackathon unique is our thorough focus on impact in the industry. The HackTrain brings together the world's most driven, skilled, and bold developers, designers and entrepreneurs, and provides them with an immersive environment to build high-impact solutions to solve burning problems in the industry. This, together with the help of our industry partners, ignites creativity, and allows our Trainhackers to conceive, build and launch scalable startups that provide scalable long-term solutions that have the potential to grow and truly have an impact on the world. Crazy? Definitely! Impossible? Not even close! HackTrain alumni have managed to build prototypes at the hackathon that reached headlines in high profile news headlines, exited by selling to railway companies, obtained access as advisors to boards in railway companies, and continued growing their projects forward. Nothing can stop innovation when travelling at 200km/h."
+        lon: -0.10000000149011612
+        lat: 51.540000915527344
+      - country: DE
+        city: München
+        link: 'http://www.meetup.com/ReactJS-Meetup-Munich/'
+        name: ReactJS Meetup Munich
+        description: 'Are you new to ReactJS and want to learn more? Or feeling ready to share your experience and show us what you built? Join us for The ReactJS Meetup in Munich!'
+        lon: 11.579999923706055
+        lat: 48.13999938964844
+      - country: DE
+        city: Dresden
+        link: 'http://www.meetup.com/DresdenJS-io-JavaScript-User-Group/'
+        name: DresdenJS.io JavaScript User Group
+        description: 'Wir wollen JavaScript in Dresden und Umgebung weiter voran bringen. Von Entwicklern für Entwickler wollen wir uns einmal im Monat treffen, um in gelockerter Atmosphäre mit kurzen Vorträgen interessante Neuigkeiten zu erfahren und danach noch uns austauschen. Wir sind offen für jeden, der mitmachen will! Vorträge, Ideen, Wünsche und Co. sind gern gesehen!'
+        lon: 13.739999771118164
+        lat: 51.04999923706055
+      - country: GB
+        city: Richmond
+        link: 'http://www.meetup.com/West-London-JavaScript-Meetup/'
+        name: West London JavaScript Meetup
+        description: "<p>We're focusing on JavaScript both on server and client side technologies.<br>Please come and join us, if you are a software engineer, developer, tester who develop applications written in or used JavaScript. We also happy to welcome product managers, project managers who work with applications written in JavaScript.</p>"
+        lon: -0.30000001192092896
+        lat: 51.459999084472656
+      - country: RO
+        city: Cluj-Napoca
+        link: 'http://www.meetup.com/Cluj-Javascripters/'
+        name: Cluj JavaScripters
+        description: |-
+          <p>If you believe that JavaScript is going to change our world, join this this group and DO IT! :)</p>
+          <p>Our site:&nbsp;<a href="http://clujjs.ghost.io/" class="linkified">https://cluj-javascripters.github.io/</a></p>
+          <p>Join our Facebook group:&nbsp;<a href="https://www.facebook.com/groups/412304825640095/">https://www.facebook.com/groups/412304825640095/</a></p>
+        lon: 23.59000015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/d/5/6/600_448087510.jpeg'
+        lat: 46.779998779296875
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/BackendDevelopers/'
+        name: Backend Developer Meetup Group
+        description: '<p>After successfully creating The Frontend Developer Meetup and Angularjs Meetup its time to build up the Backend Developer community. This will eventually grow into individual Backend Developer Language groups or there will be specific Meetups for those programming languages. Lets have fun together, gro and share knowledge</p>'
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/2/2/9/600_447496937.jpeg'
+        lat: 52.369998931884766
+      - country: FR
+        city: Antibes
+        link: 'http://www.meetup.com/Sophia-Antipolis-Early-morning-software-discussions/'
+        name: Sophia Antipolis - Early morning software discussions
+        description: "Rejoignons-nous de bonne heure à Sophia dans un petit café sympa et profitons-en pour prendre le petit déj et discuter des stacks technologiques que l'on aime utiliser au quotidien. L'idée est que chacun puisse présenter ses technos favorites (AngularJS, Node.js, Go, Docker, AWS, GKE, MongoDB, Cassandra, Hadoop, Ansible, …), en découvrir de nouvelles, et peut-être réaliser ensemble des projets les utilisant."
+        lon: 7.119999885559082
+        lat: 43.599998474121094
+      - country: SE
+        city: Göteborg
+        link: 'http://www.meetup.com/ReactJS-Goteborg/'
+        name: ReactJS Göteborg
+        description: |-
+          <p>The groups focus is ReactJS, Flux, best practices and why ReactJS brings sanity to the chaos of frontend architecture!</p>
+          <p>You can join our slack group here :</p>
+          <p><a href="https://reactjsgoteborg.herokuapp.com/">https://reactjsgoteborg.herokuapp.com/</a><br></p>
+          <p>/Stephen</p>
+        lon: 12.010000228881836
+        lat: 57.720001220703125
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/More-Micro-Modules/'
+        name: More Micro Modules
+        description: '<p>At MMM we build new tiny libraries that solve problems.</p>'
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/7/d/1/600_441599345.jpeg'
+        lat: 52.52000045776367
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/Dun-Laoghaire-node-Meetup/'
+        name: Dun Laoghaire Node/Angular/Meteor/React meetup
+        description: |-
+          <p>We are going to experiment with this meetup, We started with nodeJS and nodeschool, we are now thinking we can do more than just nodeJS, members drive what this group does so feel free to reach out and tell us what you would like to do, so far we have</p>
+          <p>• AngularJS <br></p>
+          <p>• ReactJS <br></p>
+          <p>• AWS Lambdas and AWS API gateway <br></p>
+          <p>• NodeJS <br></p>
+          <p>• SailsJS</p>
+          <p>Our guideline is that we write code or build products at the meet-up.</p>
+        lon: -6.25
+        lat: 53.33000183105469
+      - country: CH
+        city: Lugano
+        link: 'http://www.meetup.com/Ticino-Javascript-Meetup/'
+        name: Ticino Javascript Meetup
+        description: Questo gruppo è per tutti gli interessati alla programmazione in javascript
+        lon: 8.9399995803833
+        lat: 46.0099983215332
+      - country: IT
+        city: Milano
+        link: 'http://www.meetup.com/milano-front-end/'
+        name: Milano Front End
+        description: |-
+          <p>Questo è un gruppo per chiunque sia interessato allo sviluppo web front-end. CSS, Javascript , jQuery , frameworks, performance, etc. Incontriamoci per discuterne!&nbsp;</p>
+          <p>This is a group for anyone interested in front-end web development. CSS, Javascript, jQuery, Frameworks, performances, etc. Let's meet to discuss about it! English-speaking participants are welcome!</p>
+          <p>Join us on Slack, send us a message requesting to be added!</p>
+          <p>su Twitter: <a href="https://twitter.com/milanofrontend">@milanofrontend</a></p>
+        lon: 9.1899995803833
+        lat: 45.459999084472656
+      - country: DE
+        city: Hannover
+        link: 'http://www.meetup.com/HannoverJS/'
+        name: HannoverJS
+        description: |-
+          <p><span>HannoverJS is a usergroup focused on JavaScript and related stuff.&nbsp;The idea has gained great interest around lower saxonys JavaScript folks.&nbsp;We meet regularly on the 4th Thursday every month at 7pm.</span></p>
+          <p>•&nbsp;<b>Website:</b> <a href="http://www.hannoverjs.de">www.hannoverjs.de</a></p>
+          <p>•&nbsp;<span><b>Twitter:</b> </span><a href="http://www.twitter.com/hannoverjs">www.twitter.com/hannoverjs</a></p>
+          <p>•&nbsp;<b>Facebook:</b> <a href="http://www.facebook.com/hannoverjs">www.facebook.com/hannoverjs</a></p>
+          <p>•&nbsp;<b>Slack:</b> <a href="http://www.slack.hannoverjs.de">slack.hannoverjs.de</a></p>
+        lon: 9.729999542236328
+        lat: 52.400001525878906
+      - country: HU
+        city: Budapest
+        link: 'http://www.meetup.com/Web-Monday-Budapest/'
+        name: Web Monday Budapest
+        description: |-
+          <p>We're bringing Web Monday to Budapest!</p>
+          <p>Web Monday is an informal, non-commercial, and completely community-driven event that aims to connect the people who are shaping the future of the internet. Inspired by the culture of Silicon Valley, it started out in Cologne, Germany in late 2005 in an effort to help spread those sunny California vibes. Anyone involved in web 2.0 or neighboring fields who is interested in learning and sharing with others is most welcome to join. Whether you are a thinker, builder, designer, founder or funder – Web Monday is your chance to present your OSS, your product, your service, your startup, or your next big idea to a growing audience of web aficionados and aficionadas.</p>
+          <p>(Text partly taken from webmontag.de)</p>
+        lon: 19.079999923706055
+        lat: 47.5099983215332
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/The-Berlin-Web-App-Builders-Meetup/'
+        name: The Berlin Web App Builders Meetup
+        description: "<p>Learn how to build web apps, share your experiences, discuss your challenges and network with like-minded app builders.&nbsp;</p>\n<p><span>Free Beer &amp; Pizza (thank you, sponsors!). Web Apps. In English. Enough Said \\o/&nbsp;</span></p>\n<p><span>If the TL;DR; is not enough for you, here is a few more info:&nbsp;</span></p>\n<p><span><b>Who is the group for?</b>&nbsp;</span></p>\n<p><span>Berlin Web App Builders (BWAP) is a group for tech people who are working or want to work on web apps.&nbsp;</span></p>\n<p><span>We have an amazing tech community in Berlin with a great diversity of backgrounds, tools and experiences.</span></p>\n<p><span>This is a chance to get together, share, learn and improve from that. If you have any interest in building web apps or if you are already working on any kind of web app, join us and let us know about it!&nbsp;</span></p>\n<p><span><b>Where are we going to meet?&nbsp;</b></span></p>\n<p><span>We have possible locations in mitte, Ku-damm and Prenzlauer Berg. We will always make sure to keep the location next to a train station (S-Bahn or U-Bahn).&nbsp;</span></p>\n<p><span><b>What are we going to do?&nbsp;</b></span></p>\n<p><span>Every evening will have one or two speakers, a small networking session (if you come alone, just let us know and we can introduce you around - only if you want :)!) and why not, we can have some coding as well. Of course, let's not forget beer and food from our sponsors.&nbsp;</span></p>\n<p><span><b>When?</b>&nbsp;</span></p>\n<p><span>The first meetup will be in November, starting at 7.30pm. If you believe it is too late or too early, please drop us a note. If we have enough requests, we are happy to move it.</span></p>"
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/b/b/600_442920955.jpeg'
+        lat: 52.52000045776367
+      - country: GB
+        city: Egham
+        link: 'http://www.meetup.com/Egham-JavaScript-Meetup/'
+        name: Egham JavaScript Meetup
+        description: "This is a group for people doing serious stuff with JavaScript and NodeJS. If you are building rich applications, providing open-source contributions, looking forward to ES7, or crafting cool code, you'll find people to share your experiences with. If you are just starting out, come and meet others who have been there. This is a place to share knowledge, ask questions, learn and grumble; and an opportunity to prove that the best developers aren’t just in London. We meet monthly in Egham, Surrey for some informal talks, live coding, show-and-tell, questions and of course beer. Sign up and join us!"
+        lon: -0.5699999928474426
+        lat: 51.43000030517578
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Paris-vert-x-Meetup/'
+        name: Paris Vert.x Meetup
+        description: '<p>Vert.x user community in Paris, sharing Vert.x best practices, discuss architecture problems, contribute to vert.x, launch regular meetup and spread Vert.x.</p>'
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/1/8/9/600_443888585.jpeg'
+        lat: 48.86000061035156
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/Berlin-Realtime-Web-Meetup/'
+        name: Berlin Realtime Web Meetup
+        description: '<p>A group for everyone that feels the web should do more than just request-response. Let’s meet for talks and workshops to share experiences working with data-sync, websockets and pub-sub messaging, but also focus on realtime servers, databases, message buses and all the other bits and pieces necessary for building awesome realtime web applications.</p>'
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/6/2/f/600_444493871.jpeg'
+        lat: 52.52000045776367
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/NodeWorkshops/'
+        name: Node Workshops
+        description: |-
+          <p>This group will get together and go through various Node.js related topics.&nbsp;</p>
+          <p><span>Amongst other topics, we intend to work though these workshops - </span><a href="http://nodeschool.io/#workshopper-list" class="linkified">http://nodeschool.io/#workshopper-list</a> <br></p>
+          <p><span>Please get in touch if you can help out with a venue...</span> <br></p>
+        lon: -0.10000000149011612
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/0/9/8/600_447177496.jpeg'
+        lat: 51.52000045776367
+      - country: MT
+        city: Mellieha
+        link: 'http://www.meetup.com/nodejsmalta/'
+        name: NodeJS Malta
+        description: |-
+          <p>A dedicated meetup for people with NodeJS skills, or an interest in NodeJS, in Malta</p>
+          <p><br></p>
+          <p>On twitter: @nodejsmalta</p>
+          <p>And Facebook: &nbsp;https://www.facebook.com/nodejsmalta</p>
+        lon: 14.359999656677246
+        lat: 35.959999084472656
+      - country: DE
+        city: Mannheim
+        link: 'http://www.meetup.com/fulljsma/'
+        name: 'Full.js Mannheim - Meteor,  React & AngularJS'
+        description: '<p>Explorers of Javascript with Fullstack capabilities wanted. Interested in the concept of JSEntanglement? Join our local meeting group for Isomorphic JS enthusiasts and clever web app builders. From beginner to professional, everybody welcome.</p>'
+        lon: 8.470000267028809
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/f/5/a/600_443356218.jpeg'
+        lat: 49.5
+      - country: RO
+        city: Timisoara
+        link: 'http://www.meetup.com/Node-js-Timisoara/'
+        name: Node.js Timisoara
+        description: "<p>An open community for Node.js passionates. Let's share our experience.</p>"
+        lon: 21.229999542236328
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/e/6/9/600_443564649.jpeg'
+        lat: 45.7599983215332
+      - country: DK
+        city: Copenhagen
+        link: 'http://www.meetup.com/make-my-website/'
+        name: How to Make a Website
+        description: |-
+          <p>Anyone who wants a website soon discovers that the many different options can be confusing.&nbsp;<span>This meetup will clear things up by covering the different tools and techniques to get yourself online. Things we will cover include:</span></p>
+          <p><span> <br></span></p>
+          <p><span>- How to get a domain name such as MyWebsite.com</span></p>
+          <p>- Using HTML and CSS to build a website</p>
+          <p>- Building websites with Javas<span>cript</span></p>
+          <p>- Using tools such as Wix, Weebly, SimpleSite, One.com, Adobe Muse, Weld.io, and others to build a site</p>
+          <p>- Building interactive websites with Meteor.js, Angular, and Node.js</p>
+          <p>- Building interactive websites with Java</p>
+          <p> <br></p>
+          <p>If you come to the location but you can't find us then call 3141 0514 <br></p>
+        lon: 12.569999694824219
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/4/7/600_444300583.jpeg'
+        lat: 55.68000030517578
+      - country: PL
+        city: Katowice
+        link: 'http://www.meetup.com/ReactJS-Katowice/'
+        name: ReactJS Katowice
+        description: '<p>ReactJS + ecosystem community based in Katowice. React is a JavaScript library for creating user interfaces by Facebook and Instagram.</p>'
+        lon: 19.020000457763672
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/e/d/7/600_443564759.jpeg'
+        lat: 50.2599983215332
+      - country: GB
+        city: Milton Keynes
+        link: 'http://www.meetup.com/mkjscript/'
+        name: MK.js.
+        description: |-
+          <p>Oxford has a JavaScript meetup, London does, I thought MK needed one. I don't have any firm plans as to what the meetup should be. Initially I think that it would be good to just get some interested people together and meet up somewhere and discuss what people are interested in, what's new and what's exciting. When we build up a bit of momentum, we can try organise a bit more formally and get people to give talks and give people a platform to speak if they'd like. If anyone has other ideas they think would be good, please get in touch, it'd be great to get this meetup going. Hope to see some of you soon! (Sorry about the extra full stop at the end of the group name. It had to be six characters...)</p>
+          <p> <br></p>
+          <p>We now have a github where you can submit talks and give feedback: <a href="http://www.github.com/mkjs">www.github.com/mkjs</a></p>
+          <p>We're aiming for talks of around 20 minutes per slot, with up to 3 slots at an event. We're also going to have some time for shorter "Lightning Talks" of about 5 minutes each, so feel free to submit a shorter talk if you'd like.</p>
+          <p>For anyone who uses slack, we now have our very own channel, sign up here:&nbsp;https://mkjs.herokuapp.com/</p>
+        lon: -0.75
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/f/8/6/600_444508550.jpeg'
+        lat: 52.02000045776367
+      - country: BE
+        city: Brussels
+        link: 'http://www.meetup.com/jsbe-io/'
+        name: jsbe.io
+        description: |-
+          <p>New Belgium Front-end user group.</p>
+          <p>When looking at the current landscape there are a lot of awesome Frontend user groups already. However, they are either very localized (Brussels, Antwerp) or very specialized (Angular, Ember, NodeJs).</p>
+          <p>Jsbe.io aims to setup a user group where all sorts of frontend topics will be discussed. <br>We foresee to hold meetups at various locations all over the country.&nbsp;</p>
+          <p><span>Who is welcome?&nbsp; <br></span><span>Well everyone!&nbsp;</span></p>
+          <p><b>Still looking for steering committee members, speakers and locations! </b> <br></p>
+          <p>Contact:&nbsp;</p>
+          <p><span><a>jan.jsbe@gmail.com</a> <br></span><span><a>dennis.jsbe@gmail.com</a></span></p>
+          <p><span>Find us on github:&nbsp; <br></span><span><a href="https://github.com/jsbe">https://github.com/jsbe</a></span> <br></p>
+        lon: 4.329999923706055
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/9/8/9/600_443615209.jpeg'
+        lat: 50.83000183105469
+      - country: IT
+        city: Roma
+        link: 'http://www.meetup.com/RomaJS/'
+        name: RomaJS
+        description: |-
+          <p>This is a JavaScript User Group based in the city of Roma, Italia.</p>
+          <p>Follow us on&nbsp;<a href="https://www.facebook.com/RomaJS-1594098737474547/?fref=ts">Facebbok</a><span>!<br></span><span>And on </span><a href="https://twitter.com/roma_js">Twitter</a><span>!<br></span><span>This is our&nbsp;</span><a href="https://www.youtube.com/channel/UCFm8OPi5USbFybw9SaTLxeA">Youtube</a><span>.</span></p>
+        lon: 12.479999542236328
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/5/b/6/600_443818806.jpeg'
+        lat: 41.900001525878906
+      - country: FI
+        city: Helsinki
+        link: 'http://www.meetup.com/Futurice-WWWeeklies/'
+        name: Futurice WWWeeklies
+        description: '<p>Every week on Friday, Futurice frontend and backend developers meet to share latest web development news, show some new tools, interesting workflows, or show their code to their peers. This has been traditional an internal meetup only for Futurice, but we are now gladly welcoming some guests. Come and be one of our guests. ;) <br> <br>If you work at Futurice, <b>please do not RSVP</b> to this event. <br></p>'
+        lon: 24.940000534057617
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/8/d/600_444241677.jpeg'
+        lat: 60.16999816894531
+      - country: DE
+        city: Köln
+        link: 'http://www.meetup.com/Cologne-js/'
+        name: Cologne.js
+        description: 'Cologne’s JavaScript user group. We meet bi-monthly on the second Tuesday. Our goal is to have an awesome, inclusive and safe community meetup where people meet, hang out together, chat, listen to talks, exchange ideas and make new friends. Any harmful or discriminating behaviour will not be tolerated and results in the offending person being expelled from the meetup.'
+        lon: 6.96999979019165
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/4/1/6/600_444513814.jpeg'
+        lat: 50.95000076293945
+      - country: DE
+        city: Ludwigsburg
+        link: 'http://www.meetup.com/lubunode/'
+        name: Ludwigsburg Node.js Meetup
+        description: |-
+          <p>Let's discuss all things node! Whether it be ES6 features for JavaScript, npm packages, continous integration or anything else. The complete node ecosystem is ready to be explored :)</p>
+          <p><span>We'll start off with monthly meetups at selected pubs in Ludwigsburg until we get a decent group of regulars to organize bigger events with dedicated locations and speakers. Everyone interested in programming is welcome to join us!</span></p>
+        lon: 9.1899995803833
+        lat: 48.900001525878906
+      - country: HR
+        city: Split
+        link: 'http://www.meetup.com/Level-Up-Development/'
+        name: Level Up Development
+        description: '<p>Interested in discovering the newest technology trends? Excited about meeting people that share your passion? Join a group of prospective international developers at the monthly Level Up Development meetup. Learn more about the latest web technologies and how your community is using them. This meetup is open to anyone that has a curiosity and drive to explore what is offered, from experienced developers to students. Everybody knows that nothing works well on an empty stomach so, beside expanding your cognitions about technology and meeting new people, join us for free beer and pizza!</p>'
+        lon: 16.450000762939453
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/5/b/6/600_447646518.jpeg'
+        lat: 43.5099983215332
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/fullstack-berlin/'
+        name: Fullstack.JS Berlin
+        description: |-
+          <p>This group aims to explore the wonderful world of full-stack JavaScript. There are no limits on what libraries or technologies apart from heavy usage of JavaScript on the front and backend. Anyone wishing to learn or show off some full-stack JS projects is more than welcome. It's our time, ninjas.</p>
+          <p>This is a bi-monthly meet-up extension of our already popular FullstackJS London meetup (<a href="http://www.meetup.com/Fullstack-js-London/" class="linkified">http://www.meetup.com/Fullstack-js-London/</a>)</p>
+        lon: 13.380000114440918
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/4/7/6/600_444342102.jpeg'
+        lat: 52.52000045776367
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/Berlin-Cloud/'
+        name: Berlin Cloud Computing
+        description: |-
+          <p>Diese Gruppe ist genau das richtige für alle cloud-begeisterten Technologieenthusiasten in und um Berlin.</p>
+          <p>Einmal im Monat sprechen wir über aktuelle Themen und neue Technologien in der Cloud. Dafür haben wir regelmäßig wechselnde Experten zu Gast, welche uns mit ihrem Fachwissen helfen noch mehr aus der Cloud heraus zu holen.</p>
+          <p>Du willst wissen, was die Cloud ist, oder&nbsp;welche&nbsp;Möglichkeiten sie dir bietet? - Dann komm zu unseren Meetups und erfahre mehr!</p>
+          <p>Du arbeitest täglich mit der Cloud und möchtest dich mit anderen Profis austauschen? - Dann bist du bei uns genau richtig!</p>
+          <p>Oder bist du selbst Cloud-Experte? - Dann melde dich bei uns und teile deine Erfahrungen und&nbsp;Best Practices mit der Gruppe!</p>
+          <p>Wir freuen uns auf dich!</p>
+          <p><br></p>
+        lon: 13.380000114440918
+        lat: 52.52000045776367
+      - country: GR
+        city: Athens
+        link: 'http://www.meetup.com/nodejsathens/'
+        name: NodeJS Athens Meetup
+        description: '<p>This meetup is focused on spreading knowledge and best practices for the use of Node.js. Topics of discussion include open source projects, architectures, testing, code management, the future of Node.js and emerging trends.</p>'
+        lon: 23.729999542236328
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/3/f/7/600_444321495.jpeg'
+        lat: 37.97999954223633
+      - country: ES
+        city: Las Palmas
+        link: 'http://www.meetup.com/lpamean/'
+        name: 'LPA MEAN (MongoDB, Express, AngularJS, Node.js) & Phonegap'
+        description: |-
+          <p>Aprende, participa y asiste a eventos relacionados con MEAN Framework: MongoDB, ExpressJS, AngularJS y NodeJS. Además Phonegap y desarrollo móvil.</p>
+          <p><b>=== NodeJS ===</b></p>
+          <p>Javascript en el lado del servidor. Aprende a crear aplicaciones en tiempo real con Socket.io. Crea juegos multijuador y chats. Backends Flexibles en 5 minutos. Descubre la tecnología mejor pagada de Silicon Valley. <b>=== AngularJS ===</b></p>
+          <p><span>El mejor Framework JavaScript para desarrollar aplicaciones Móviles y Web. Desarrollado por Google.&nbsp;</span></p>
+          <p><span><b>=== MongoDB ===</b></span></p>
+          <p><span>La mejor Base de Datos NoSQL por excelencia. Con Mongo veremos como construir aplicaciones y backends flexibles, para pivotar las funcionalidades de nuestra aplicación adaptándolas a nuestros clientes. Además veremos cómo utilizar Mongo para analizar BIGDATA.</span></p>
+          <p><span><b>=== PhoneGap ===&nbsp;</b></span></p>
+          <p><span>PhoneGap o mejor dicho Cordova nos permite empaquetar código Web en aplicaciones nativas para iOS, Android, WindowsPhone, FirefoxOS, etc. Discutiremos qué frameworks y cómo desarrollar aplicaciones móviles híbridas de aspecto y performance nativo.</span></p>
+          <p><span><b>=== En general ===&nbsp;</b></span></p>
+          <p><span>Las últimas tecnologías para el desarrollo Web y Móvil, siguiendo las filosofías Lean Startup, Mobile First, NoSQL, NoBackend, Agile Development, Gamification.</span></p>
+          <p><span>Si eres Entrepreneur / Emprendeodor, entonces necesitas conocer los mejores entornos de desarrollo, y estar al día. Aprende, Crece, Comparte</span></p>
+          <p>Recursos:&nbsp; <br><a href="http://www.mongodb.org/">MongoDB</a>&nbsp;(<a href="http://mongoosejs.com/">Mongoose</a>) <br><a href="http://expressjs.com/"></a><a href="http://www.mean.io/#!/">mean.io</a>&nbsp; <br><a href="http://angularjs.org/">AngularJS</a>&nbsp; <br><a href="http://nodejs.org/">Node.js</a>&nbsp;(<a href="http://expressjs.com/">Express</a>&nbsp;)</p>
+          <p><a href="http://www.ibm.com/developerworks/library/wa-nodejs-polling-app/">Build a Real-time Polls Application with Node.js, Express, AngularJS and MongoDB</a>&nbsp;(IBM Tutorial)</p>
+        lon: -15.430000305175781
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/7/3/6/600_444326422.jpeg'
+        lat: 28.100000381469727
+      - country: ES
+        city: La Rioja
+        link: 'http://www.meetup.com/Angular-Hispano/'
+        name: Angular Hispano
+        description: '<p><span>Tú comunidad AngularJS en castellano.&nbsp;</span><span>Tanto si has oído hablar de AngularJS pero aún no has tenido tiempo de probarlo, como si eres un usuario avanzado, este es el sitio para seguir aprendiendo.</span></p>'
+        lon: -2.440000057220459
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/6/d/e/600_444326334.jpeg'
+        lat: 42.470001220703125
+      - country: 'NO'
+        city: Oslo
+        link: 'http://www.meetup.com/ReactJS-Oslo-Meetup/'
+        name: ReactJS Oslo Meetup
+        description: |-
+          <p>ReactJs is crazy easy to get started and fun once you get going. It is a library developed by Facebook!<span><br></span></p>
+          <p><span>Join us if you'd like to learn more or if you have your own ReactJs experience to share that others can benefit from.</span></p>
+          <p><span>We care about functional programming, bleeding-edge UIs, new ways of thinking about modular UI implementations on web and mobile!</span></p>
+          <p><br></p>
+          <p>Read more about React and React Native:</p>
+          <p><a href="http://facebook.github.io/react/">More info on ReactJS</a><br></p>
+          <p><a href="https://facebook.github.io/react-native/">More info on React Native</a></p>
+          <p><br></p>
+          <p>Join us :)</p>
+        lon: 10.75
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/1/9/4/600_444488596.jpeg'
+        lat: 59.90999984741211
+      - country: ES
+        city: Madrid
+        link: 'http://www.meetup.com/Tecnologias-para-la-Transformacion-Digital/'
+        name: Tecnologías para la Transformación Digital
+        description: 'El grupo de usuarios de Tecnologías para la Transformación Digital pretende ser un punto de encuentro e intercambio de ideas acerca de tecnologías y metodologías que ayudan a los equipos IT a enfrentarse a los retos de la transformación digital, es decir, a desarrollar productos digitales con más foco en el usuario, más flexibilidad, mejor time to market, más escalabilidad, más disponibilidad y menos coste. Hablaremos por tanto de arquitecturas avanzadas con bajo acoplamiento, infraestructuras elásticas con escalado horizontal, tolerancia a fallos a nivel software, modelos de almacenamiento NoSQL, y de mejoras en el ciclo de vida del desarrollo software vía automatización de pruebas y continuous delivery.'
+        lon: -3.7100000381469727
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/0/f/b/600_447641211.jpeg'
+        lat: 40.41999816894531
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/React-Barcelona/'
+        name: React Barcelona
+        description: |-
+          <p><b>React Barcelona </b><span>nace con la intención de agrupar la comunidad de desarrolladores de React en Barcelona, organizando eventos del tipo Meetup y Workshops con la filosofía open source: libre y gratuito para todo el mundo.&nbsp;</span> <br></p>
+          <p>Próximamente en <a href="http://react.barcelona">react.barcelona</a></p>
+        lon: 2.1700000762939453
+        lat: 41.400001525878906
+      - country: PT
+        city: Lisbon
+        link: 'http://www.meetup.com/por-uma-causa/'
+        name: '<porumacausa/>'
+        description: |-
+          <p>Tens ideias para projetos sem fins lucrativos que gostarias de ver concretizados?</p>
+          <p>Queres aprender novas tecnologias e ao mesmo tempo contribuir para melhorar a comunidade?</p>
+          <p>Estas meetups têm como objectivo melhorar a qualidade de vida de uma comunidade fazendo uso de meios tecnológicos, nomeadamente através da programação de aplicações informáticas.</p>
+        lon: -9.140000343322754
+        lat: 38.720001220703125
+      - country: FR
+        city: Pamiers
+        link: 'http://www.meetup.com/Meetup-JavaScript-NodeJS-Pamiers/'
+        name: Meetup JavaScript/NodeJS Pamiers
+        description: 'Parlons de développement, nouvelles techno, javascript, nos projets open-source ;)'
+        lon: 1.6200000047683716
+        lat: 43.119998931884766
+      - country: ES
+        city: Barcelona
+        link: 'http://www.meetup.com/AulaW3/'
+        name: AulaW3
+        description: |-
+          <p>Un grupo para ponernos al día con talleres, seminarios y charlas gratuitas en Barcelona para descubrir las últimas tendencias en desarrollo web y mobile. <br></p>
+          <p>Únete a nosotros, comparte tus conocimientos y encuentra otros en nuestra comunidad!</p>
+        lon: 2.1700000762939453
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/a/b/5/600_445639125.jpeg'
+        lat: 41.400001525878906
+      - country: NL
+        city: Den Haag
+        link: 'http://www.meetup.com/Part-up-Hackathon/'
+        name: Part-up Hackathons and Developer meetups
+        description: |-
+          <p>Part-up is a platform for matching people to temporary teams. We will help you find and build the best team for your project, startup, community or organization.&nbsp;<span>Organizations can get their own tribe on part-up.com to become a decentralized collaborative organizations (DCO) and allow for bottom-up collaboration within, on the edge or outside of the current organizational boundaries.</span></p>
+          <p>Part-up can be used by everyone, is developed by anyone and is going to be owned by the community that builds the platform and its use. We believe in building Part-up as a decentralized collaborative organization and therefore opensourced the&nbsp;Part-up codebase and Part-up development process.&nbsp;<br><br></p>
+          <p>So, are you a coder, designer, or creative, …? Interested in Part-up, wanting to learn more about open source development and crowd(re)sourced projects? Then you don’t want to miss the hackathons and Developer meetups we organize!</p>
+          <p>Great to have you in the community.&nbsp;</p>
+          <p>Cheers, Ralph (founder and product manager)</p>
+        lon: 4.28000020980835
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/8/4/f/600_445667183.jpeg'
+        lat: 52.08000183105469
+      - country: AT
+        city: Vienna
+        link: 'http://www.meetup.com/Commit-Vienna-Hackathons/'
+        name: Commit Vienna Hackathons
+        description: 'We are passionate about Open-Source Software and love to code. We organize and host hackathons and hackergartens on a regularly basis, to commit to Open-Source, code for competitions and enjoy hacking together.'
+        lon: 16.3700008392334
+        lat: 48.220001220703125
+      - country: DE
+        city: Karlsruhe
+        link: 'http://www.meetup.com/MEAN-Stack-Karlsruhe/'
+        name: MEAN Stack Karlsruhe
+        description: |-
+          Verwendest du den MEAN Stack oder möchtest du ihn verwenden? Link: http://mean.io/#!/
+
+
+          MEAN steht für Mongo-ExpressJS-AngularJS-NodeJS
+        lon: 8.399999618530273
+        lat: 49
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/Dublin-Coder-Forge/'
+        name: Dublin - Coder Forge
+        description: 'A place to learn how to forge out code, to smyth out patterns and designs. Complete beginners welcome, bring your own laptop.'
+        lon: -6.25
+        lat: 53.33000183105469
+      - country: PT
+        city: Abrantes
+        link: 'http://www.meetup.com/tagusjs/'
+        name: TagusJS
+        description: '<p>Vem conhecer outros utilizadores, entusiastas ou interessados em Javascript na zona centro de Portugal.</p>'
+        lon: -8.1899995803833
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/f/0/4/600_446277092.jpeg'
+        lat: 39.470001220703125
+      - country: UA
+        city: Chernihiv
+        link: 'http://www.meetup.com/chernihivjs/'
+        name: Chernihiv JavaScript Meetup Group
+        description: '<p>Meetup group for JavaScript professionals to discuss technology, share experience and find solutions.</p>'
+        lon: 31.290000915527344
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/c/1/1/600_445883569.jpeg'
+        lat: 51.5
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Node-js-Meetup-London/'
+        name: Node.js Meetup London
+        description: |-
+          <p>JavaScript is quickly becoming the language that drives your website, your server and your database. It can also run your operating system, your nintendo emulator and the new EPIC game engine.&nbsp; </p>
+          <p>In this group we focus on the server side - Node.js. Thanks to v8, it runs many times faster than PHP, Ruby or Python, and thanks to the event-based design, it is the ultimate back-end for mobile and web applications. It is fast to code and needs less CPU &amp; RAM - speeding up your development and saving you server costs.&nbsp;</p>
+          <p>The group is open to anyone interested. Whether you're wondering why in the world you would want to put JavaScript on a server or want to discuss how async/await is the best thing since sliced bread, let's meet up!</p>
+        lon: -0.10000000149011612
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/e/7/5/600_445935989.jpeg'
+        lat: 51.52000045776367
+      - country: RO
+        city: Bucharest
+        link: 'http://www.meetup.com/Bucharest-Full-Stack-Devs-Meetup/'
+        name: Bucharest Full Stack Devs Meetup
+        description: '<p>Devs who care about javascript from the front-end to the services in the back-end can meet other devs with similar interests. We speak javascript, node js, angular, elastic, you name it. Full vertical.</p>'
+        lon: 26.100000381469727
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/3/5/600_446460821.jpeg'
+        lat: 44.439998626708984
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/Startup-Kerkstraat/'
+        name: Startup Kerkstraat
+        description: |-
+          <p>This group for people involved or interested in startups in or around the Kerkstraat in Amsterdam.</p>
+          <p><span>We want to create a monthly gathering for people of startup companies located in the Kerkstraat area. Are you a founder, hacker, freelancer or startup enthousiast living or working in the area of the Kerkstraat, this group is for you!</span><br></p>
+          <p><br></p>
+        lon: 4.889999866485596
+        lat: 52.369998931884766
+      - country: FR
+        city: Lille
+        link: 'http://www.meetup.com/altima-front-end/'
+        name: altima front-end
+        description: |-
+          <p><b>Tous les 3 mois</b>, l’équipe front-end altima vous propose d’<b>échanger</b> autour de <b>sujets front-end</b>.</p>
+          <p>2 à 3 talks d’experts pour partager sur ce métier qui évolue sans cesse.</p>
+          <p> <br></p>
+          <p><span>Nous abordons tous les sujets front-end, HTML, CSS ou JS.</span> <br></p>
+          <p><span> <br></span></p>
+          <p><span>Les talks sont ouverts à tout public, que vous soyez débutant ou expert, geek ou nerd !</span> <br></p>
+        lon: 3.069999933242798
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/6/9/3/600_446314451.jpeg'
+        lat: 50.63999938964844
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Vuejs-Paris/'
+        name: Vuejs Paris
+        description: |-
+          <p>Vue.js community in Paris</p>
+          <p>Groupe de talks, discussions, ateliers, etc. Autour de Vue.js</p>
+          <p>Nous Sommes à la recherche <b>d'hébergeurs</b> pour nos prochains Meetups ainsi que de <b>sponsors</b> et de <b>speakers</b> ! Si tu es intéressé, envoie un mail a vue@posva.net pour se mettre en contact !</p>
+          <p>We are actively looking for hosts, sponsors and speakers&nbsp;(and not just francophones, so don't be shy!). Get in touch by sending an email to vue@posva.net</p>
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/c/8/4/600_446336452.jpeg'
+        lat: 48.86000061035156
+      - country: BE
+        city: Gent
+        link: 'http://www.meetup.com/JSValley/'
+        name: JSValley
+        description: |-
+          <p>We share valuable content related to the engineering of modern JavaScript applications. <br></p>
+          <p>We intend to fill each meetup with one larger content session and two shorter inspirational talks. Topic suggestions are more than welcome and we love to welcome you on stage. <br></p>
+          <p>Quality of content is key!</p>
+          <p><a href="https://twitter.com/JSValley_be" class="linkified">https://twitter.com/JSValley_be</a> <br></p>
+          <p><a href="https://www.facebook.com/JSValleyBe" class="linkified">https://www.facebook.com/JSValleyBe</a> <br></p>
+        lon: 3.7200000286102295
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/6/2/0/600_447553856.jpeg'
+        lat: 51.04999923706055
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Loopback-Paris/'
+        name: Loopback Paris
+        description: '<p>Un groupe pour échanger autour de ce framework NodeJS, et des modules associés (différents SDK, Arc, ...). Ouvert aux gens débutants curieux de découvrir, tout comme aux personnes souhaitant partager leur expérience sur le sujet</p>'
+        lon: 2.3399999141693115
+        lat: 48.86000061035156
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/WebDevelopment-Nederland/'
+        name: WebDevelopment Nederland
+        description: |-
+          <p>WebDevelopment Nederland organiseert MeetUps over de nieuwste technologieën en ontwikkelingen binnen webdevelopment. Deze groep richt zich uitsluitend op: PHP, Javascript, Python, Ruby on Rails en front-end development. Per kwartaal wordt er een lezing gegeven in hartje Amsterdam door een toonaangevende specialist binnen de markt.</p>
+          <p>Wil je je graag aanmelden als spreker of als attendee, laat het ons weten!<br></p>
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/1/9/4/600_446532692.jpeg'
+        lat: 52.369998931884766
+      - country: DE
+        city: Bonn
+        link: 'http://www.meetup.com/BonnJS/'
+        name: BonnJS
+        description: 'User group for JavaScript developers in Bonn to learn and discuss about JavaScript. All JavaScript levels are welcome. You can meet people, talk about JavaScript related technologies, find a mentor or someone to do pair programming with, or just work on your own tutorials, books, or projects. No matter if you are into Angular, React, jQuery, Backbone, Ember, Meteor, whatever... Everybody is welcome!'
+        lon: 7.099999904632568
+        lat: 50.72999954223633
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/Spilberg-IT-Development-Meetup/'
+        name: Spilberg IT Development Meetup
+        description: "<p>This is a meetup group for all IT development professionals; from HTML/CSS to JAVA and from Swift to .NET. All skill levels are welcome. At each meetup, a speaker on a trending topic starts with sharing the latest insights, after which the floor is yours for discussion. All with the purpose to keep each other up to date on the latest development trends. We'll organise the meet up every month at venues in or around Amsterdam. Location, speakers, food and drinks will be arranged by Spilberg IT Development. The topic and the quality of discussion is up to you! Is there any specific topic or a speaker you would like to see at the next Meetup? Do you want to share your insights on a(trending) topic yourself? Let us know!</p>"
+        lon: 4.889999866485596
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/3/2/a/600_448405386.jpeg'
+        lat: 52.369998931884766
+      - country: SE
+        city: Luleå
+        link: 'http://www.meetup.com/Lulea-Web-Application-Developers-Meetup/'
+        name: Luleå Web Application Developers Meetup
+        description: |-
+          <p><span>Startat denna grupp för utbyte av kunskaper och kontakter rörande utveckling av webbapplikationer.&nbsp;</span> <br></p>
+          <p>Vi på Context Sales Sweden etablerar vårt huvudkontor och utvecklingsteam i Luleå under första kvartalet 2016 och vill därför gärna bygga ett nätverk med likasinnade i och runt om Luleå. Vill träffa lokala förmågor för utbyte av erfarenheter, men också för möjligheter till framtida samarbeten.&nbsp;</p>
+          <p>(CSS letar just nu både erfarna seniora- och talangfulla juniora utvecklare Att utöka teamet med.)</p>
+          <p>-----------</p>
+          <p><b>English:</b></p>
+          <p>Have started this group for exchange of knowledge and contacts regarding development of web applications.&nbsp;</p>
+          <p>We at Context Sales Sweden are establishing our main office and development team in Luleå during the first quarter of 2016 and are therefore interested in building a network of likeminded in Luleå. Want to meet local talents for exchange of experiences, but also for the possibility of working together in the future.</p>
+          <p>(CSS are at this time looking for both experienced senior and talented junior developers to expand the team.)</p>
+        lon: 22.15999984741211
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/e/d/3/600_446976563.jpeg'
+        lat: 65.5999984741211
+      - country: IT
+        city: Salerno
+        link: 'http://www.meetup.com/JS-Salerno/'
+        name: 'JavaScript & NodeJS community Salerno'
+        description: "<p>JavaScript è qui da trent'anni ma è più vivo che mai! JS è passato da essere un semplice script di controllo dell'input nei browser a un linguaggio vero e proprio, con un ecosistema di framework e librerie da far impallidire linguaggi più blasonati. E' l'unico vero linguaggio universale, gira ovunque vi sia un browser (anche nel vostro telefonino) e anche su server! E' la porta d'accesso alle WebApp moderne. In questo gruppi saranno accettati i neofiti ed esperti. Organizzeremo incontri mensili (o bi-mensili) come conferenze, inviteremo esperti che soddisferanno le nostre curiosità e faremo rete.</p>"
+        lon: 14.779999732971191
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/d/4/3/600_447640259.jpeg'
+        lat: 40.68000030517578
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/Web-Up-Tech/'
+        name: Web Up Tech
+        description: "Ce Meetup est destiné à toute la communauté de développement Open Source Web/Cloud/DevOps. Les Thèmes abordés couvrent tous les aspects développement Web (Spring Boot, Angulars JS, Node JS, Mean Stack, HTML5,...) ainsi que les nouvelles architectures Cloud (Micro services, Containers, Ansible, Docker,...) dans un contexte DevOps/Agile. Les sessions organisées se déroulent généralement en soirée et sont animées par des experts dans leur domaine ou des développeurs de tout horizon. Normasys SA (SSII en pleine expansion) sponsorise et gère l'organisation de ces événements avec des partenaires de la place. Votre contribution est la bienvenue pour partager avec les acteurs et développeurs parisiens, votre savoir faire et vos retours sur expériences très précieux. Big Up, Come Up, Web Up ;)"
+        lon: 2.3399999141693115
+        lat: 48.86000061035156
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/React-London-Bring-Your-Own-Project/'
+        name: 'React London : Bring Your Own Project'
+        description: "Join other JS and Node developers for a monthly React - Bring Your Own Project - Meetup at SapientNitro, London as we all work on group member's React projects. \n\nBring your questions, your code, and your desire to help. The sessions are informal, friendly, and organised with a loose agenda. Mix with fellow React developers and get learning."
+        lon: -0.07999999821186066
+        lat: 51.52000045776367
+      - country: SE
+        city: Göteborg
+        link: 'http://www.meetup.com/DevBar/'
+        name: DevBar
+        description: '<p>DevBar är mötesplatsen för alla Open Source-kunniga webbutvecklare i Göteborgsområdet som vill sia ny teknik och prata trender inom Open Source-utveckling. Vi står för maten, de kalla dryckerna och diskussionsämnena. Allt du behöver ta med dig är idéer, spaningar och ditt kunnande. Tillsammans skapar vi en härlig stämning i Open Source-utvecklingens tecken.</p>'
+        lon: 12.010000228881836
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/7/e/600_447000894.jpeg'
+        lat: 57.720001220703125
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Serverless-London/'
+        name: Serverless London
+        description: "A group for anyone interested in building web, mobile and Internet-of-Things applications with serverless architectures using the Serverless Framework and more! We'll focus heavily on Amazon Web Services and discuss AWS Lambda as the focal point of AWS."
+        lon: -0.10000000149011612
+        lat: 51.52000045776367
+      - country: HU
+        city: Budapest
+        link: 'http://www.meetup.com/Corporate-JavaScript-Meetup-Budapest/'
+        name: Corporate JavaScript Meetup Budapest
+        description: '<p>A csoport célja a JavaScript technológia evangelizálása a hazai corporate fejlesztők körében. Szeretnénk megmutatni, hogy milyen bevált toolok és praktikák vannak a vállalati környezetben.</p>'
+        lon: 19.079999923706055
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/e/c/5/600_447216549.jpeg'
+        lat: 47.5099983215332
+      - country: DE
+        city: Hamburg
+        link: 'http://www.meetup.com/Node-RED-Hamburg/'
+        name: Node-RED Hamburg
+        description: "<p>Let's connect – machines, apps, people, everything... If you like cyberphysical data-plumbing, then you gotta love Node-RED! We are looking for passionate Geeks (f/m) within the IoT sphere to hang out and share our latest hacks, technologies and ideas with. Regarding to one of the most impactful IoT-tools out there right now, we invite you to join us and show off your favorite Node-RED nodes and get inspiration from the community. Beginners, Makers, Scientists, Professionals – feel free to contribute!</p>"
+        lon: 10
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/d/8/3/600_448608515.jpeg'
+        lat: 53.54999923706055
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Coding-Hour-London-After-work-drinks-for-developers/'
+        name: Coding Hour London - After work drinks for developers
+        description: |-
+          <p>This meetup group is gathering code enthusiasts in a chilled and fun atmosphere: while drinking beers, attendees will be invited to solve algorithm challenges in a limited time.</p>
+          <p>Coding Hour is the occasion for developers to get together and to improve their skills on a specific technology.</p>
+        lon: -0.10000000149011612
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/8/a/600_447240394.jpeg'
+        lat: 51.52000045776367
+      - country: DE
+        city: Heidelberg
+        link: 'http://www.meetup.com/RheinNeckarJS/'
+        name: RheinNeckarJS
+        description: |-
+          <p>RheinNeckarJS is a JavaScript, HTML5 and NodeJS user group in Heidelberg, Mannheim and the whole region Rhein-Neckar organized by Martina Kraus and Christoph Martens.</p>
+          <p><br></p>
+          <p>Website:&nbsp;<a href="http://rheinneckarjs.github.io/">http://rheinneckarjs.github.io/</a></p>
+          <p>Twitter:&nbsp;https://twitter.com/RheinNeckarJS</p>
+        lon: 8.6899995803833
+        lat: 49.41999816894531
+      - country: GB
+        city: London
+        link: 'http://www.meetup.com/Corporate-JavaScript-Meetup-London/'
+        name: Corporate JavaScript Meetup London
+        description: '<p>Our main goal is to evangelise&nbsp;JavaScript among corporate&nbsp;developers. We want to share the proven tools and the tips in corporate environment. <br>This is a place to share your knowledge, participate in Q &amp; A and widen your sphere of knowledge. <br>Free admission! <br>Join us to participate in this professional forum where everyone is invited!</p>'
+        lon: -0.10000000149011612
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/4/9/d/600_447373469.jpeg'
+        lat: 51.52000045776367
+      - country: NL
+        city: Amsterdam
+        link: 'http://www.meetup.com/Coding-Hour-Amsterdam-After-work-drinks-for-developers/'
+        name: Coding Hour Amsterdam - After work drinks for developers
+        description: 'This meetup group is gathering code enthusiasts in a chilled and fun atmosphere: while drinking beers, attendees will be invited to solve algorithm challenges in a limited time. Coding Hour is the occasion for developers to get together and to improve their skills on a specific technology.'
+        lon: 4.889999866485596
+        lat: 52.369998931884766
+      - country: FR
+        city: Toulouse
+        link: 'http://www.meetup.com/Toulouse-AngularJS-Meetup/'
+        name: AngularJS Toulouse
+        description: |-
+          <p>Bienvenue,</p>
+          <br>
+          <p>Nous recherchons continuellement des speekers et Sponsors. Les sujets peuvent&nbsp;être&nbsp;de&nbsp;tous&nbsp;niveaux, sur Angular ou Ionic 1 &amp; 2.</p>
+          <br>
+          <p>Si vous&nbsp;êtes&nbsp;intéressé&nbsp;merci de me contacter directement: &nbsp;<a href="https://twitter.com/julienrenaux">https://twitter.com/julienrenaux</a></p>
+          <br>
+          <p>PS: Un Slack de la communauté sera disponible&nbsp;en&nbsp;Avril.</p>
+        lon: 1.4500000476837158
+        lat: 43.619998931884766
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/JavaScript-Lab-Paris/'
+        name: JavaScript Lab Paris
+        description: |-
+          <p>Coder. Echanger. S'améliorer.</p>
+          <p>Nous sommes fans de JavaScript et nous nous sommes dit que ça serait vraiment bien d'avoir une communauté de passionnés où les gens peuvent échanger, se rencontrer et apprendre les uns des autres. <br> <br>Rejoignez-nous et devenons de meilleurs programmeurs, ensemble.</p>
+        lon: 2.3399999141693115
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/2/3/2/600_447689234.jpeg'
+        lat: 48.86000061035156
+      - country: CH
+        city: Bern
+        link: 'http://www.meetup.com/MarkLogic-User-Group-Switzerland/'
+        name: MarkLogic User Group Switzerland
+        description: 'Diese Gruppe ist für alle, die an Enterprise Data Stores für den Einsatz im Digital Business interessiert sind – für Neugierige und Experten. Enterprise Data Stores kommen immer dann zum Einsatz, wenn relationale Datenbanken an ihre Grenzen stossen. Bei unseren Treffen geben wir Tipps und Tricks, stellen Anwendungsbeispiele von Kunden vor und stellen neue Entwicklungen vor. Wir freuen uns auf jeden Teilnehmer und den Austausch mit unseren Gruppenmitgliedern. The MarkLogic User Group (MLUG) is for users and/or fans of MarkLogic and those who are interested in learning more about MarkLogic, XML, XQuery and related technologies. MUGL meetups are free and open to anyone that wishes to attend. There is no formal membership for the group. Our meetings are held quarterly in different regions in Germany. Want to know more about MarkLogic? Read on &gt;&gt; MarkLogic® is a new generation database platform that enables organisations to get more value from more data than ever before. Global enterprises and governments rely on MarkLogic to power intelligent, high performance applications aimed at analysing data for better insights and also running crucial day-to-day business operations. With MarkLogic, organisations achieve faster time-to-value than was possible with legacy databases, while minimising risk and improving data quality. MarkLogic is the only Enterprise NoSQL database—a powerful, agile, trusted database that has the speed and scale of NoSQL coupled with the enterprise features required. · Develop stronger applications faster with a flexible data model using Full-Stack JavaScript, JSON and Node.JS · Find relevant information easier with lightning fast, built-in search · Gain more intelligence in the data layer using semantics and bitemporal · Maintain data resiliency and consistency with ACID transactions, scalability and elasticity, certified security, and high availability and disaster recovery'
+        lon: 7.440000057220459
+        lat: 46.95000076293945
+      - country: FR
+        city: Paris
+        link: 'http://www.meetup.com/ParseServerParisianLovers/'
+        name: Parse Server Parisian Lovers
+        description: "Suite à leur récente annonce de la fin de Parse.com, Facebook a pris la décision de livrer en Open Source leur solution révolutionnaire de Back End As A Service : Parse Server. La quasi totalité de la suite et des SDKs est désormais open source. Pour que cette belle initiative perdure, il faut fédérer la communauté des développeurs Parse (600 000 à travers le monde) et quoi de mieux qu'un meet up ? Ce groupe s'adresse donc à tous ceux qui : - souhaitent contribuer au projet open source Parse Server - aiment/adorent la solution de Parse et l'utilisent dans leur développement - sont curieux de découvrir cette nouvelle opportunité"
+        lon: 2.3399999141693115
+        lat: 48.86000061035156
+      - country: IT
+        city: Ferrara
+        link: 'http://www.meetup.com/ferrarajs/'
+        name: Ferrara JavaScript Group - Mobile and cloud app developers
+        description: "<p>L'UserGroup di Ferrara e dintorni dedicato al JavaScript e al WebDevelopment! Lo scopo è quello di creare un gruppo di developer appassionati e ritrovi per discutere sulle nuove tecnologie e riscoperte nell'ambito dei nuovi frameworks e librerie, soprattutto nell'ambito dello sviluppo di app mobile, cloud, desktop e multipiattaforma!</p>"
+        lon: 11.619999885559082
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/0/3/c/600_447936924.jpeg'
+        lat: 44.84000015258789
+      - country: FR
+        city: Neuilly-sur-Seine
+        link: 'http://www.meetup.com/Meetup-AngularJS-Neuilly-sur-Seine/'
+        name: 'Meetup AngularJS & JavaScript'
+        description: "<p>Rejoignons-nous pour apprendre le code dans la bonne humeur ! Si vous avez envie d'apprendre AngularJS et le live coding, ainsi que l'évolution du JavaScript, mais pensez que cette activité est réservée aux scientifiques en herbe, révisez votre jugement et venez nous retrouver dans notre espace de co-working. Nous vous montrerons que coder n'est pas sorcier !</p>"
+        lon: 2.2699999809265137
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/a/3/9/600_447970809.jpeg'
+        lat: 48.88999938964844
+      - country: PL
+        city: Bydgoszcz
+        link: 'http://www.meetup.com/meet-js-Bydgoszcz/'
+        name: meet.js Bydgoszcz
+        description: '<p>Luźne, cykliczne spotkania dla osób zainteresowanych technologiami związanymi z JavaScript. Prezentacje prowadzone przez developerów dla developerów w luźnej formule barcampu. Poziom prelekcji jest zróżnicowany tak, że zarówno początkujący jak i JS Ninja znajdą coś dla siebie.</p>'
+        lon: 18.010000228881836
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/f/4/a/600_448216202.jpeg'
+        lat: 53.119998931884766
+      - country: AT
+        city: Graz
+        link: 'http://www.meetup.com/Angular-Meetup-Graz/'
+        name: Angular Meetup Graz
+        description: Wir treffen uns regelmäßig um über Angular zu sprechen.
+        lon: 15.420000076293945
+        lat: 47.08000183105469
+      - country: IE
+        city: Dublin
+        link: 'http://www.meetup.com/fullstackjsdublin/'
+        name: FullstackJS Dublin
+        description: |-
+          <p><span>JavaScript's taking over the web development stack - if the idea of using one programming language for the front-end AND the back-end tickles your programming fancy, then <a href="https://secure.meetup.com/register/?urlkey=&amp;eventId=&amp;a=&amp;number=&amp;gj=&amp;c=19782015&amp;newReg=1&amp;returnUri=http%3A%2F%2Fwww.meetup.com%2Ffullstackjsdublin%2Fjoin%2F%3FeventId%3D%26a%3D%26gj%3D%26newReg%3D1"><b>join us</b></a>!</span> <br></p>
+          <p><span>We are a vibrant community of developers interested in learning, sharing our knowledge of Javascript and helping each other.</span> <br></p>
+          <p>Have you got a coding problem? Or any question related to Javascript? Great! <br>Write your question <a href="http://www.meetup.com/FullstackJS-Dublin/messages/boards/thread/49732038"><b>in our message board</b></a>. Our code mentors will be happy to help you at our next live coding tutorial or workshop session! :)</p>
+          <p>We meet once a month. All levels are welcome. Bring your laptop, have fun coding and meet cool people! ;)</p>
+          <p>So if you want to practice Javascript, jQuery, AngularJS, BackboneJS, ReactJS, Meteor, etc together with other enthusiastic members, <a href="https://secure.meetup.com/register/?urlkey=&amp;eventId=&amp;a=&amp;number=&amp;gj=&amp;c=19782015&amp;newReg=1&amp;returnUri=http%3A%2F%2Fwww.meetup.com%2Ffullstackjsdublin%2Fjoin%2F%3FeventId%3D%26a%3D%26gj%3D%26newReg%3D1"><b>join us now</b></a>!</p>
+          <p><img src="http://photos3.meetupstatic.com/photos/event/c/7/7/e/600_448431070.jpeg"></p>
+          <p><span>You can follow us on </span><a href="https://twitter.com/fullstackjsdb"><b>Twitter</b></a><span>&nbsp;and </span><b><a href="https://www.facebook.com/Fullstack-JS-Dublin-1724120897872082/">Facebook</a>&nbsp;</b>and use our hashtag <b><a href="https://twitter.com/hashtag/fullstackjsdublin?src=hash">#fullstackjsdublin</a>&nbsp;</b><span>:) <br> <br>See you very soon! <br> <br>Sébastien <br><i>Your Gentle Organizer :)</i></span></p>
+        lon: -6.25
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/8/0/a/600_448514346.jpeg'
+        lat: 53.33000183105469
+      - country: NL
+        city: Almere
+        link: 'http://www.meetup.com/Silicon-Polder-Almere/'
+        name: Silicon Polder (Almere)
+        description: "We bespreken de laatste ontwikkelingen in ons vakgebied. We kijken naar ontwikkelingen op het gebied van PHP Frameworks, REST API's, Angular, maar er wordt ook gesproken over zaken als continuous integration, software deployment, e.d."
+        lon: 5.170000076293945
+        lat: 52.36000061035156
+      - country: DE
+        city: Berlin
+        link: 'http://www.meetup.com/MariaDB-Developers-Berlin-Meetup/'
+        name: MariaDB Berlin Meetup
+        description: "<p>This is a MariaDB Developers meetup group. This group is for everyone interested in the development of MariaDB, MySQL and any other forks of MySQL. You don't necessarily have to be a database developer to join the meetups. The focus is not purely on development of MariaDB. There are a lot of other aspects as well including everything from all the tools around MariaDB to community related aspects to documentation and infrastructure. Simply, if you're interested in becoming involved in making MariaDB better, please join!</p>"
+        lon: 13.380000114440918
+        lat: 52.52000045776367
+      - country: DE
+        city: Karlsruhe
+        link: 'http://www.meetup.com/Hackschool-KA/'
+        name: Hackschool - Karlsruhe
+        description: |-
+          <p><b>GERMAN - DEUTSCH&nbsp;</b></p>
+          <p>Technik und Code gemeinsam erleben und verstehen. Bei der Hackschool steht die Atmosphäre und das freie Lernen im Vordergrund. Dabei bietet <a href="https://hackerstolz.de">Hackerstolz e.V.</a>&nbsp;Hilfe zur Selbsthilfe. Mitmachen kann Jede und Jeder! Bitte bringt all eure Neugierde und Fragen mit! Vorkenntnisse sind nicht erforderlich, da mit individueller Betreuung auf die einzelnen Fähigkeiten eingegangen wird. Ein eigenes Laptop wäre von Vorteil, es gibt aber auch Geräte vor Ort, die jeder mitverwenden kann.&nbsp;</p>
+          <p><span><br></span></p>
+          <p><span><b>ENGLISH - ENGLISCH</b>&nbsp;</span></p>
+          <p><span>Let's both experience and understand tech and code together. The <a href="https://hackerstolz.de">Hackerstolz e.V.</a>&nbsp;Hackschool empowers open learning with an atmosphere that helps you help yourself and others. Everyone is invited to take part! Bring all your curiosity and questions with you! No experience required beforehand, as we offer an individual mentor-based training for each skillset. An own Laptop would be awesome, but isn't required - we have some available that everyone can use.</span><br></p>
+          <p><img src="http://photos2.meetupstatic.com/photos/event/b/b/0/7/600_448607879.jpeg"></p>
+          <p><span><i>An event made with love by <a href="https://hackerstolz.de">Hackerstolz e.V.</a></i></span></p>
+        lon: 8.399999618530273
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/b/1/9/600_448607897.jpeg'
+        lat: 49
+    nodeschools:
+      - name: NodeSchool Amsterdam
+        location: 'Amsterdam, NL'
+        organizers:
+          - jpwesselink
+          - rickheere
+          - stefanmirck
+          - codeflyer
+        website: 'http://github.com/nodeschool/amsterdam'
+        twitter: NodeSchoolAMS
+        repo: 'http://github.com/nodeschool/amsterdam'
+        lat: 52.3702157
+        lon: 4.895167900000001
+      - name: NodeSchool Ankara / Turkey
+        location: 'Ankara, TR'
+        organizers:
+          - trkozd
+          - skaan07
+        website: 'http://nodeschool.io/ankara'
+        repo: 'http://github.com/nodeschool/ankara'
+        lat: 39.9333635
+        lon: 32.8597419
+      - name: Augsburg NodeSchool
+        location: 'Augsburg, DE'
+        organizers:
+          - meaku
+          - jhnns
+          - sbat
+          - flootr
+          - matthaias
+          - topa
+        website: 'http://nodeschool.io/augsburg'
+        twitter: NodeschoolAugs
+        repo: 'http://github.com/nodeschool/augsburg'
+        lat: 48.3705449
+        lon: 10.89779
+      - name: Barcelona NodeSchool
+        location: 'Barcelona, ES'
+        organizers:
+          - patrickheneise
+        website: 'http://nodeschool.io/barcelona/'
+        repo: 'http://github.com/nodeschool/barcelona'
+        lat: 41.3850639
+        lon: 2.1734035
+      - name: Belfast NodeSchool
+        location: 'Belfast, UK'
+        organizers:
+          - gangleri
+          - lanazwart
+          - ablair08
+          - chrisfowler
+        website: 'http://nodeschool.io/belfast'
+        twitter: '@nodeschoolbel'
+        repo: 'http://github.com/nodeschool/belfast'
+        lat: 54.59728500000001
+        lon: -5.93012
+      - name: NodeSchool Belgrade
+        location: 'Belgrade, RS'
+        organizers:
+          - stojanovic
+          - aysbg
+          - simalexan
+        website: 'http://nodeschool.io/belgrade'
+        repo: 'http://github.com/nodeschool/belgrade'
+        lat: 44.786568
+        lon: 20.4489216
+      - name: NodeSchool Berlin
+        location: 'Berlin, DE'
+        organizers:
+          - finnp
+          - stryju
+          - johannhof
+        website: 'http://nodeschool.io/berlin'
+        repo: 'http://github.com/nodeschool/berlin'
+        lat: 52.52000659999999
+        lon: 13.404954
+      - name: NodeSchool Bratislava
+        location: 'Bratislava, SK'
+        organizers:
+          - yangwao
+        website: 'http://nodeschool.io/bratislava'
+        repo: 'http://github.com/nodeschool/bratislava'
+        lat: 48.1485965
+        lon: 17.1077477
+      - name: Bristol NodeSchool
+        location: 'Bristol, UK'
+        organizers:
+          - permadesign
+          - fiznool
+          - katjad
+        website: 'http://nodeschool.io/bristol'
+        gitter: 'https://gitter.im/nodeschool/bristol'
+        repo: 'http://github.com/nodeschool/bristol'
+        lat: 51.454513
+        lon: -2.58791
+      - name: Chernivtsi NodeSchool
+        location: 'Chernivtsi, UA'
+        organizers:
+          - denysdovhan
+        twitter: denysdovhan
+        repo: 'http://github.com/nodeschool/chernivtsi'
+        lat: 48.2920787
+        lon: 25.9358367
+      - name: Dublin NodeSchool
+        location: 'Dublin, IE'
+        organizers:
+          - no9
+          - johnbrett
+          - jasonmarah
+          - johnbrett
+          - akohli
+          - davecocoa
+          - lorcanmcdonald
+          - gangleri
+        website: 'http://nodeschool.io/dublin'
+        twitter: '@nodeschooldub'
+        repo: 'http://github.com/nodeschool/dublin'
+        lat: 53.3498053
+        lon: -6.2603097
+      - name: Faro NodeSchool
+        location: 'Faro, PT'
+        organizers:
+          - mcoquet
+          - nneves
+          - rsoares
+        repo: 'http://github.com/nodeschool/faro'
+        lat: 37.0193548
+        lon: -7.9304397
+      - name: Foyle NodeSchool
+        location: 'Derry/Londonderry, UK'
+        organizers:
+          - sjmerrigan
+          - kieranheg
+          - vquigley
+          - CahalKearney
+          - gangleri
+          - diarmaidm
+        website: 'http://nodeschool.io/foyle-valley'
+        repo: 'http://github.com/nodeschool/foyle-valley'
+        lat: 54.9966124
+        lon: -7.3085748
+      - name: NodeSchool Haarlem
+        location: 'Haarlem, NL'
+        organizers:
+          - rickheere
+          - jpwesselink
+          - codeflyer
+          - stefanmirck
+        website: 'http://nodeschool.io/haarlem'
+        repo: 'https://github.com/nodeschool/haarlem'
+        lat: 52.3873878
+        lon: 4.6462194
+      - name: NodeSchool Hamburg
+        location: 'Hamburg, DE'
+        organizers:
+          - greelgorke
+        website: 'http://nodeschool.io/hamburg'
+        repo: 'http://github.com/nodeschool/hamburg'
+        lat: 53.5510846
+        lon: 9.9936818
+      - name: NodeSchool Heidelberg
+        location: 'Heidelberg, DE'
+        organizers:
+          - martensms
+          - iUsemws
+        website: 'http://nodeschool.io/heidelberg'
+        twitter: 'https://twitter.com/nodeschoolhd'
+        repo: 'http://github.com/nodeschool/heidelberg'
+        lat: 49.3987524
+        lon: 8.6724335
+      - name: Helsinki NodeSchool
+        location: 'Helsinki, FI'
+        organizers:
+          - laurisvan
+          - jubilem
+        website: 'http://nodeschool.io/helsinki/'
+        twitter: helnode
+        repo: 'https://github.com/nodeschool/helsinki'
+        lat: 60.16985569999999
+        lon: 24.938379
+      - name: NodeSchool Hradec Králové
+        location: 'Hradec Králové, CZ'
+        organizers:
+          - bajtos
+        repo: 'http://github.com/nodeschool/hradec-kralove'
+        lat: 50.2103605
+        lon: 15.825211
+      - name: NodeSchool Istanbul
+        location: 'Istanbul, TR'
+        organizers:
+          - arifcakiroglu
+          - yasinaydin
+          - huseyinbabal
+        website: 'http://nodeschool.io/istanbul'
+        twitter: 'https://twitter.com/NodeSchool_Ist'
+        repo: 'http://github.com/nodeschool/istanbul'
+        lat: 41.0082376
+        lon: 28.9783589
+      - name: NodeSchool Italy
+        location: Italy
+        organizers:
+          - matteocollina
+          - MarcoPiraccini
+        website: 'http://nodeschool.io/italy'
+        repo: 'http://github.com/nodeschool/italy'
+        lat: 41.87194
+        lon: 12.56738
+      - name: NodeSchool Kyiv
+        location: 'Kyiv, UA'
+        organizers:
+          - sudodoki
+        repo: 'http://github.com/nodeschool/kyiv'
+        lat: 50.4501
+        lon: 30.5234
+      - name: Kirovohrad NodeSchool
+        location: 'Kirovohrad, UA'
+        organizers:
+          - ghaiklor
+        website: 'http://nodeschool.io/kirovohrad'
+        twitter: ghaiklor
+        repo: 'http://github.com/nodeschool/kirovohrad'
+        lat: 48.50793300000001
+        lon: 32.262317
+      - name: Lisbon NodeSchool
+        location: 'Lisbon, PT'
+        organizers:
+          - diasdavid
+        repo: 'http://github.com/nodeschool/lisbon'
+        lat: 38.7222524
+        lon: -9.1393366
+      - name: NodeSchool Lodz
+        location: 'Lodz, PL'
+        organizers:
+          - adamniedzielski
+          - lipkap
+        website: 'http://nodeschool.io/lodz'
+        twitter: nodeschool_lodz
+        gitter: 'https://gitter.im/nodeschool/lodz'
+        repo: 'https://github.com/nodeschool/lodz'
+        lat: 51.7592485
+        lon: 19.4559833
+      - name: London NodeSchool
+        location: 'London, UK'
+        organizers:
+          - iancrowther
+          - olizilla
+          - alanshaw
+          - orliesaurus
+          - ezodude
+        website: 'http://nodeschool.io/london'
+        repo: 'http://github.com/nodeschool/london'
+        lat: 51.5073509
+        lon: -0.1277583
+      - name: Lyon NodeSchool
+        location: 'Lyon, FR'
+        organizers:
+          - maxlath
+        website: 'http://nodeschool.io/lyon'
+        repo: 'http://github.com/nodeschool/lyon'
+        lat: 45.764043
+        lon: 4.835659
+      - name: NodeSchool Madrid
+        location: 'Madrid, ES'
+        organizers:
+          - alexfernandez
+          - gootyfer
+          - javiervelezreyes
+        website: 'http://nodeschool.io/madrid'
+        twitter: '@NodeJsMadrid'
+        repo: 'http://github.com/nodeschool/madrid'
+        lat: 40.4167754
+        lon: -3.7037902
+      - name: NodeSchool Moscow
+        location: 'Moscow, RU'
+        organizers:
+          - AVVS
+          - freele
+        repo: 'http://github.com/nodeschool/moscow'
+        lat: 55.755826
+        lon: 37.6173
+      - name: Munich NodeSchool
+        location: 'Munich, DE'
+        organizers:
+          - meaku
+          - jhnns
+          - sbat
+          - flootr
+          - matthaias
+          - topa
+        website: 'http://nodeschool.io/munich'
+        twitter: nodeschoolmuc
+        repo: 'http://github.com/nodeschool/munich'
+        lat: 48.1351253
+        lon: 11.5819806
+      - name: Oslo NodeSchool
+        location: 'Oslo, NO'
+        organizers:
+          - Andersos
+        website: 'http://nodeschool.io/oslo'
+        gitter: 'https://gitter.im/nodeschool/oslo'
+        repo: 'http://github.com/nodeschool/oslo'
+        lat: 59.9138688
+        lon: 10.7522454
+      - name: NodeSchool Oxford
+        location: 'Oxford, UK'
+        organizers:
+          - roylines
+          - benfoxall
+          - ivanbokii
+          - nileshkale
+          - peterjwest
+          - lazywithclass
+        website: 'http://jsoxford.com/'
+        twitter: 'https://twitter.com/JSOxford'
+        repo: 'http://github.com/nodeschool/oxford'
+        lat: 51.7520209
+        lon: -1.2577263
+      - name: NodeSchool Paris
+        location: 'Paris, FR'
+        organizers:
+          - tdd
+        website: 'http://nodeschool.io/paris/'
+        twitter: NodeSchoolParis
+        repo: 'http://github.com/nodeschool/paris'
+        lat: 48.856614
+        lon: 2.3522219
+      - name: NodeSchool Sevilla
+        location: 'Seville, ES'
+        organizers:
+          - beltran-rubo
+        repo: 'http://github.com/nodeschool/seville'
+        lat: 37.3890924
+        lon: -5.9844589
+      - name: NodeSchool Silesia
+        location: 'Silesia, PL'
+        organizers:
+          - afronski
+          - rspective
+        website: 'http://nodeschool.io/silesia'
+        twitter: nodeschoolpl
+        gitter: 'https://gitter.im/nodeschool/silesia'
+        repo: 'https://github.com/nodeschool/silesia'
+        lat: 50.5716595
+        lon: 19.3219768
+      - name: Saint Petersburg NodeSchool
+        location: 'Saint Petersburg, RU'
+        organizers:
+          - marinintim
+        website: 'http://nodeschool.io/spb'
+        repo: 'https://github.com/nodeschool/spb'
+        lat: 59.9342802
+        lon: 30.3350986
+      - name: Nodeschool Stavanger
+        location: 'Stavanger, NO'
+        organizers:
+          - asbjornenge
+          - megatrond
+          - olavgg
+          - olekjormo
+          - persille
+          - joargp
+          - resurge
+          - jmyrland
+          - frodeanonsen
+          - VirtueMe
+        website: 'http://nodeschool.io/stavanger'
+        repo: 'https://github.com/nodeschool/stavanger'
+        lat: 58.9699756
+        lon: 5.7331073
+      - name: NodeSchool Strasbourg
+        location: 'Strasbourg, FR'
+        organizers:
+          - jsebfranck
+        website: 'http://nodeschool.io/strasbourg/'
+        repo: 'http://github.com/nodeschool/strasbourg'
+        lat: 48.5734053
+        lon: 7.752111299999999
+      - name: NodeSchool Stuttgart
+        location: 'Stuttgart, DE'
+        organizers:
+          - kwakayama
+        website: 'http://nodeschool.io/stuttgart'
+        repo: 'http://github.com/nodeschool/stuttgart'
+        lat: 48.7758459
+        lon: 9.1829321
+      - name: Utrecht NodeSchool
+        location: 'Utrecht, NL'
+        organizers:
+          - fritzvd
+        website: 'http://nodeschool.io/utrecht/'
+        repo: 'http://github.com/nodeschool/utrecht'
+        lat: 52.09073739999999
+        lon: 5.1214201
+      - name: Vienna NodeSchool
+        location: 'Vienna, AT'
+        organizers:
+          - thomaspeklak
+          - shm
+          - saintedlama
+        website: 'http://nodeschool.io/vienna'
+        repo: 'http://github.com/nodeschool/vienna'
+        lat: 48.2081743
+        lon: 16.3738189
+      - name: Wroclaw NodeSchool
+        location: 'Wroclaw, Dolnoslaskie, PL'
+        organizers:
+          - grabbou
+          - explosivetitles
+        website: 'http://nodeschool.io/wroclaw'
+        twitter: nodeschool_wro
+        gitter: 'https://gitter.im/nodeschool/wroclaw'
+        repo: 'http://github.com/nodeschool/wroclaw'
+        lat: 51.1078852
+        lon: 17.0385376
+      - name: NodeSchool Zagreb
+        location: 'Zagreb, HR'
+        organizers:
+          - shime
+          - dinodsaurus
+        website: 'http://nodeschool.io/zagreb'
+        repo: 'http://github.com/nodeschool/zagreb'
+        lat: 45.8150108
+        lon: 15.981919
+  - region: Південна Америка
+    conferences:
+      - name: NodeConf Argentina
+        desc: 'NodeConf Argentina is among the first international Node.js conferences taking place in Latin American territory.'
+        dates:
+          - 2016-11-18T11:00:00.000Z
+          - 2016-11-19T11:00:00.000Z
+        link: 'https://2016.nodeconf.com.ar/'
+        lat: -34.6066339
+        lon: -58.4110953
+      - name: NodeConf Brazil
+        desc: 'This is the first edition of NodeConf in Latin America and is also the first major event focused exclusively on Node.js of Brazil.'
+        dates:
+          - 2016-07-04T11:00:00.000Z
+          - 2016-07-05T11:00:00.000Z
+        link: 'http://brazil.nodeconf.com/'
+        lat: -23.5539247
+        lon: -46.6550992
+    meetups:
+      - country: CL
+        city: Santiago
+        link: 'http://www.meetup.com/betazeta/'
+        name: Betazeta Tech Talks
+        description: '<p>Aqui nos juntamos los nerds y geeks a jugar con las tecnologias que nos gustan, tincan o simplemente las que nos dan curiosidad. Usamos la base de IT de Betazeta para disparar las tecnologias que nos gustaria que construyan la proxima internet o lo que es lo mimo, con las que todos la estamos construyendo :)</p>'
+        lon: -70.63999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/4/d/6/600_88277622.jpeg'
+        lat: -33.459999084472656
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/NodeJS-Argentina/'
+        name: Node.JS Argentina
+        description: "<p>Este <strong>grupo</strong> esta <strong>abierto</strong> para todo aquel interesado en conocer mas sobre <strong><a href=\"http://nodejs.org/\">Node.JS</a></strong>. La idea es generar un espacio donde podamos aprender unos de otros y adquirir o generar nuevo conocimientos.</p>\n<p>Los <strong>objetivos</strong> son:</p>\n<ol> \n <p>Servir de&nbsp;guía&nbsp;a nuevos usuarios para que puedan <strong>desarrollarse</strong></p> \n <p>Aportar <strong>buenas practicas y&nbsp;metodologías</strong></p> \n <p>Servir de <strong>laboratorio de testeo</strong> de nuevas funcionalidades y/o&nbsp;módulos</p> \n <p><span><strong>Difundir el conocimiento</strong> sobre Node.JS</span></p> \n <p><strong>Difundir Node.JS</strong> dentro de la comunidad&nbsp;informática&nbsp;de Argentina</p> \n</ol>\n<p><em>Nota: esta es una primera&nbsp;definición&nbsp;y puede sufrir cambios a partir de las&nbsp;discusiones&nbsp;del foro o votaciones.&nbsp;Así&nbsp;que por favor dense una vuelta por el foro y las encuestas.</em></p>\n<p><span><strong>Vínculos importantes para el grupo.</strong></span></p>\n<p><strong>No se permite SPAM</strong> de ningún tipo en la lista de correo electrónico, ni en los comentarios, ni en los canales de Slack.</p>\n<p>Para recruiters existe una <a href=\"http://www.meetup.com/NodeJS-Argentina/messages/boards/forum/5518472\">sección en el foro</a> para poner las ofertas laborales, tambien tenemos un canal en Slack.</p>\n<ul> \n <p><a href=\"http://www.meetup.com/NodeJS-Argentina/messages/archive/\">Lista de correo electronico</a> (archivo) </p> \n <ul> \n  <p><a href=\"http://www.meetup.com/NodeJS-Argentina/messages/archive/rss/NodeJS-Argentina-list+Meetup+Mailing+List/\">RSS</a></p> \n  <p><a href=\"http://www.meetup.com/NodeJS-Argentina/messages/archive/atom/NodeJS-Argentina-list+Meetup+Mailing+List/\">Atom</a></p> \n </ul> \n <p><a href=\"http://www.meetup.com/NodeJS-Argentina/messages/boards/\">Foro</a></p> \n</ul>\n<p><span><strong>Slack TeamSite</strong></span></p>\n<p>Slack es un sitio de chat similar a IRC. Tenemos un site de Slack en&nbsp;<a href=\"https://nodejsar.slack.com\">nodejsar.slack.com</a>. Esto es por invitación asi que envien la solicitud por <a href=\"http://www.meetup.com/NodeJS-Argentina/suggestion/\">esta pagina</a>.</p>\n<p><b>Google+</b> <br></p>\n<p>También tenemos una <a href=\"https://plus.google.com/u/0/communities/118395476615447392481\">Comunidad en G+</a></p>\n<p><b>Twitter</b></p>\n<p>Nuestro twitter es <a href=\"https://twitter.com/NodeJSArgentina\">@NodeJSArgentina</a></p>\n<p><strong>Dashboard de proyectos</strong></p>\n<p>Tenemos un <a href=\"http://nodejsar.hackdash.org/\">Dashboard</a> de proyectos. Pueden sumarse o agregar alguno.</p>\n<p><strong>Videos</strong></p>\n<p><a href=\"http://www.meetup.com/NodeJS-Argentina/pages/videos/\">Aqui</a> estan los videos de las meetups</p>\n<p><em>La marca Node.js y los logos son propiedad de Joyent.</em></p>\n<p><em>El presente grupo no tiene&nbsp;relación&nbsp;comercial alguna con la empresa Joyent.</em></p>"
+        lon: -58.369998931884766
+        lat: -34.61000061035156
+      - country: CO
+        city: Medellín
+        link: 'http://www.meetup.com/MedellinJS/'
+        name: MedellínJS
+        description: |-
+          <p>Hemos creado este grupo con el fin de reunir, compartir y aprender de los desarrolladores JavaScript de la ciudad de Medellín, Colombia.</p>
+          <p>Nuestra filosofía será siempre la de mantener un ambiente informal, nada estricto en ningún sentido. Así que cualquier colaboración, en cualquier sentido, será muy bien recibida.</p>
+          <p>¡Bienvenido!</p>
+        lon: -75.58999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/c/5/e/600_164568222.jpeg'
+        lat: 6.25
+      - country: UY
+        city: Montevideo
+        link: 'http://www.meetup.com/montevideojs/'
+        name: The Montevideo Javascript Meetup Group
+        description: |-
+          <p><span>This is a group for anyone interested in js, html, css and nodejs. Our&nbsp;</span><a href="https://github.com/mvdjs">GitHub</a><span>.</span> <br></p>
+          <p>Code of Conduct:&nbsp;<span><a href="http://confcodeofconduct.com/" class="linkified">http://confcodeofconduct.com/</a></span></p>
+        lon: -56.16999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/6/5/d/600_447618013.jpeg'
+        lat: -34.869998931884766
+      - country: BR
+        city: Belo Horizonte
+        link: 'http://www.meetup.com/Ember-BH/'
+        name: Ember.js Meetup - Belo Horizonte
+        description: '<p>Ember.js Belo Horizonte Meetup é o primeiro grupo de meetup de Ember.js no Brasil. Bora falar de JavaScript, web apps, frontend development e comer pizza!</p>'
+        lon: -43.939998626708984
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/2/2/c/600_238885132.jpeg'
+        lat: -19.920000076293945
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/AngularJS-Sao-Paulo/'
+        name: AngularSP
+        description: |-
+          <p>Grupo de meetups Angular em São Paulo, SP.</p>
+          <p><a href="https://groups.google.com/forum/#!forum/angularjs-sp">Lista de e-mails</a></p>
+        lon: -46.630001068115234
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/b/8/4/600_252879812.jpeg'
+        lat: -23.530000686645508
+      - country: CO
+        city: Cali
+        link: 'http://www.meetup.com/CaliJS/'
+        name: CaliJS
+        description: |-
+          <p>Hemos creado este grupo con el fin de reunir, compartir y aprender de los desarrolladores Javascript de la ciudad de Cali, Colombia.</p>
+          <p><span>Nuestra filosofía será siempre la de mantener un ambiente informal, nada estricto en ningún sentido. Así que cualquier colaboración, en cualquier sentido, será muy bien recibida.</span></p>
+          <p><span>¡Bienvenido!</span></p>
+        lon: -76.51000213623047
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/e/9/6/600_314816982.jpeg'
+        lat: 3.4200000762939453
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/Meteor-Sao-Paulo/'
+        name: Meteor São Paulo
+        description: '<p>Grupo criado para reunir pessoas interessadas em conhecer / aprender / ensinar / testar / desenvolver aplicações utilizando o framework Meteor.js. Meteor é uma plataforma open-source para desenvolvimento rápido de aplicações web de alta qualidade, indicada para quem está apenas começando ou para quem já é expert. Uma aplicação Meteor é um mix de Javascript que roda dentro de um web browser, Javascript que roda no no lado servidor Meteor dentro de um container Node.js, fragmentos HTML, regras CSS e conteúdos estáticos (imagens, vídeos, etc.).</p>'
+        lon: -46.630001068115234
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/c/e/600_429900462.jpeg'
+        lat: -23.530000686645508
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/Meetup-js/'
+        name: Meetup.js
+        description: '<p>Grupo para debatir y compartir ideas en torno a Javascript (client-side y server-side), distintos frameworks, librerías y tecnologías en general. Un meetup mensual con charlas preparadas por miembros de la propia comunidad</p>'
+        lon: -58.369998931884766
+        lat: -34.61000061035156
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/nodebr/'
+        name: NodeBR - São Paulo
+        description: |-
+          <p>A NodeBR é uma comunidade fundada por pessoas com interesse em aprender mais sobre Node.js assim como ajudar outras pessoas que possuem dúvidas nessa plataforma. No momento a comunidade é constituída por estes pontos de acesso principal</p>
+          <p>* <a href="https://groups.google.com/forum/?hl=pt#!forum/nodebr">A lista de e-mails</a> é um grupo no Google onde você pode cadastrar o seu endereço de e-mail para enviar e receber e-mails das outras pessoas cadastradas. Esta lista mostrou-se extremamente eficaz na resolução de dúvidas de pessoas iniciantes no Node.js, assim como também é o ponto de encontro de discussões proveitosas e notícias sobre a plataforma.</p>
+          <p>* <a href="https://webchat.freenode.net/?channels=#nodebr">Nosso canal #nodebr no IRC</a> é uma ferramenta de bate papo em tempo real, onde programadores trocam ideias e tiram dúvidas com outros membros que estão online, a ferramenta é nova e cresce junto com a comunidade. Para quem já possui instalado algum client IRC, nos achará facilmente no canal #nodebr na rede freenode.net, para aqueles que ainda não possuem um, podem acessar o link anterior para abrir o web chat e entrar diretamente no canal.</p>
+          <p>* <a href="http://www.meetup.com/Node-js-Sao-Paulo/">O grupo de Meetup de São Paulo</a> é onde organizamos nossos encontros e marcamos os eventos mensais que trazem informação e novidades sobre o mundo do Node.js.</p>
+          <p>* <a href="http://nodebr.org/">O site oficial da comunidade</a> está em fase de planejamento mas já é uma ferramenta extramente importante na nossa comunidade, visto que ela abrigará as principais ferramentas que a comunidade julga importante, como você pode ver no brainstorming.</p>
+          <p>* <a href="https://twitter.com/nodebr">@nodebr</a> no Twitter.</p>
+          <a href="https://github.com/nodebr/nodebr#contribua-para-o-projeto"></a>
+          <p><b>Contribua para o projeto</b></p>
+          <p>Para começar a contribuir você deve procurar por <a href="https://github.com/nodebr/nodebr/labels/help%20wanted">alguma issue em aberto</a>, veja aquela que você consiga resolver com facilidade. O próximo passo é fazer o fork do projeto e mandar uma pull request.</p>
+          <a href="https://github.com/nodebr/nodebr#links-importantes"></a>
+          <p><b>Links importantes</b></p>
+          <p>Lista de e-mail: <a href="https://groups.google.com/forum/?hl=pt#!forum/nodebr">https://groups.google.com/forum/?hl=pt#!forum/nodebr</a> <br> NodeBR no IRC: <a href="https://webchat.freenode.net/?channels=#nodebr">https://webchat.freenode.net/?channels=#nodebr</a> <br> Site da comunidade: <a href="http://nodebr.org/">http://nodebr.org</a> <br> Site do Meetup de São Paulo: <a href="http://www.meetup.com/Node-js-Sao-Paulo">http://www.meetup.com/Node-js-Sao-Paulo</a></p>
+        lon: -46.630001068115234
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/f/f/4/600_447632756.jpeg'
+        lat: -23.530000686645508
+      - country: BR
+        city: Belo Horizonte
+        link: 'http://www.meetup.com/AngularJS-BH/'
+        name: AngularBH
+        description: '<p>Grupo de meetups sobre o Angular de Belo Horizonte, MG.</p>'
+        lon: -43.939998626708984
+        lat: -19.920000076293945
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/OpenShift-Sao-Paulo/'
+        name: OpenShift São Paulo
+        description: '<p>Grupo de interesse sobre OpenShift, uma plataforma como serviço open-source. O objetivo do grupo é discutir a adoção de PaaS, trocar experiências de desenvolvimento dentro de plataformas. Gostaríamos de ver no grupo desenvolvedores, empresas, blogueiros, lojas de e-commerce e até mesmo pessoas que queiram implantar sua própria nuvem privada.</p>'
+        lon: -46.630001068115234
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/0/8/c/600_355648812.jpeg'
+        lat: -23.530000686645508
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/Sao-Paulo-AngularJS-Real-apps-Meetup/'
+        name: São Paulo AngularJS Real apps Meetup
+        description: "<p>Esse é um grupo para aqueles que já tem alguma experiência com Angular.js. Nossas palestras serão sobre usos reais do framework em produção. Também haverá palestras sobre a interação de Node.js com Angular.js.\_</p>"
+        lon: -46.630001068115234
+        lat: -23.530000686645508
+      - country: BR
+        city: Campina Grande
+        link: 'http://www.meetup.com/Women-Who-Code-Campina-Grande/'
+        name: Women Who Code Campina Grande
+        description: |-
+          <p>Women Who Code é uma organização global dedicada a educar e a inspirar as mulheres a buscarem conhecimento e se destacarem em carreiras tecnológicas. A organização triplicou em 2013, cresceu para 30000 membros em 18 países.</p>
+          <p>Somos conhecidos por nossos grupos de estudo semanais gratuitos e técnicos e eventos mensais maiores, incluindo palestras técnicas, noites de hackers, e treinamentos de carreira. Mais de 100 empresas de tecnologia , incluindo Square, Twitter, Etsy, Heroku, Yelp, e muitos outros têm promovido eventos para esta organização popular e que continua a crescer.</p>
+          <p>Programe em qualquer framework</p>
+          <p>qualquer nível de experiência</p>
+          <p>ou apenas programe para se divertir!</p>
+          <p>Programadoras e aspirantes a programadoras são bem vindas. Traga seu laptop e uma amiga!</p>
+          <p>Women Who Code (WWCode) is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p>Nosso Código de Conduta aplica-se a todos os eventos executados pela organização Women Who Code, Inc.<br></p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/womenwhocode">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a></p>
+          <p><br></p>
+        lon: -35.880001068115234
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/6/d/1/600_431686801.jpeg'
+        lat: -7.230000019073486
+      - country: BR
+        city: Fortaleza
+        link: 'http://www.meetup.com/nug-ce/'
+        name: NodeJS User Group Ceará
+        description: '<p>Grupo que visa fomentar e compartilhar conhecimentos sobre NodeJS e tecnologias relacionadas na comunidade cearense de desenvolvedores</p>'
+        lon: -38.59000015258789
+        lat: -3.7799999713897705
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/Aplicativos-Hibridos-Meetup/'
+        name: Aplicativos Híbridos Meetup
+        description: |-
+          <p>Espero conhecer pessoas interessadas em construir a Web do futuro - com ferramentas que entregam o resultado esperado para o usuário do mundo real - espero descobrir um caminho para provar que a simplicidade provoca escalabilidade - construindo soluções que funcionam, em respeito aos nossos usuários e em honra aos contratos com nossos investidores - soluções com experiências que mudam o dia-a-dia de quem usa - soluções que passam despercebidas pelo olhar crítico elitizado, pois são soluções que funcionam no mundo real.</p>
+          <p>Os encontros desse meetup irão sempre vir com um senso crítico, questionador das ferramentas adotadas - para que os dizeres acima se tornem realidade e para que todos tenha entendimento do todo que precisamos conhecer para levar uma carreira de Desenvolvedor Web comprometida do inicio ao fim com os resultados.</p>
+          <p>Minha opinião muda e gostaria que se você se sentiu interessado nessa abordagem, envie um e-mail de apresentação para oi@felquis.com e vamos juntos!</p>
+        lon: -46.630001068115234
+        lat: -23.530000686645508
+      - country: BR
+        city: Porto Alegre
+        link: 'http://www.meetup.com/MongoDBBrazil-Meetup/'
+        name: MongoDBBrazil Meetup
+        description: Grupo de Usuários que visam ajudar qualquer pessoa interessada aprender sobre MongoDB.
+        lon: -51.220001220703125
+        lat: -30.040000915527344
+      - country: BR
+        city: João Pessoa
+        link: 'http://www.meetup.com/paraibajs/'
+        name: paraiba.js
+        description: '<p>O Paraiba.js é um grupo de discussão da linguagem Javascript na paraíba que também organiza eventos para a disseminação de novidades da linguagem</p>'
+        lon: -34.86000061035156
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/9/4/600_443821940.jpeg'
+        lat: -7.119999885559082
+      - country: BR
+        city: Porto Alegre
+        link: 'http://www.meetup.com/AngularJS-Porto-Alegre/'
+        name: AngularJS Porto Alegre
+        description: '<p>Grupo de desenvolvedores apaixonados por tecnologias. O grupo tem enfoque na tecnologia AngularJS e em disseminar experiências e boas práticas dessa tecnologia.</p>'
+        lon: -51.220001220703125
+        lat: -30.040000915527344
+      - country: MX
+        city: México City
+        link: 'http://www.meetup.com/NodeBotsMX/'
+        name: NodeBots México
+        description: |-
+          <p>Así es... si tienes algo de experiencia en JavaScript, puedes usar tus poderes para controlar máquinas. Desde hacer parpadear un led hasta manejar un carrito, jugar con tu gato de manera remota, o torear multicóptero :-]</p>
+          <p>Queremos compartir lo poco que sabemos y aprender mucho de ti. Suscríbete a este grupo y mantente informado de las reuniones que llevaremos a cabo. Cualquier nivel de experiencia es bienvenido.</p>
+          <p>Si quieres compartir algo con la comunidad, favor de contactar a jurasec[at]gmail[.]com ó @_JuraseC</p>
+        lon: -99.13999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/5/2/2/600_405414562.jpeg'
+        lat: 19.43000030517578
+      - country: CO
+        city: Popayán
+        link: 'http://www.meetup.com/PopayanJS/'
+        name: PopayánJS
+        description: |-
+          <p><span>Este es un grupo para todos aquellos programadores y principiantes en programación que deseen aportar al desarrollo web con Javascript, HTML5 y todos los frameworks relacionados con estas tecnologias que sean tema de discusion en el grupo y generen contenido libre y de calidad</span><br>
+
+          </p>
+        lon: -76.61000061035156
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/b/2/a/600_427779722.jpeg'
+        lat: 2.4200000762939453
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/PCF-Sao-Paulo/'
+        name: Commerce Factory de São Paulo
+        description: "<p>Commerce Factory é um meetup gratuito apoiado \_pela PayPal. O foco do CF são palestras técnicas sobre tecnologias para comercio e pagamentos utilizando hacks com Arduino, sistemas com hardware com Bluetooth Low Energy, Wearbles, tecnologias para celulares, linguagens de programação server-side. Também discutiremos tópicos sobre Design, boas práticas e bibliotecas para desenvolvimento de plataformas de e-Commerce.</p>\n<p>E há Commerce Factory em outras partes do mundo. Dê uma olhada:</p>\n<p><a>meetup.com/pcf-mexico-ci­ty</a></p>\n<p><a href=\"http://www.meetup.com/pcf-miami/\">meetup.com/pcf-miami</a></p>\n<p><a href=\"http://www.meetup.com/pcf-london/\">meetup.com/pcf-london</a></p>\n<p><a href=\"http://www.meetup.com/pcf-berlin/\">meetup.com/pcf-berlin</a></p>\n<p><a href=\"http://www.meetup.com/pcf-sanjose/\">meetup.com/pcf-sanjose</a></p>\n<p><a href=\"http://meetup.com/pcf-sydney\">meetup.com/pcf-sydney</a></p>\n<p><a href=\"http://www.meetup.com/PCF-Singapore/\">meetup.com/PCF-Singapore</a><br>\n\n</p>"
+        lon: -46.630001068115234
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/3/0/2/600_389449922.jpeg'
+        lat: -23.530000686645508
+      - country: CL
+        city: Viña del Mar
+        link: 'http://www.meetup.com/javascript-vina-del-mar/'
+        name: Javascript y NodeJs Viña del Mar
+        description: 'A nosotros también nos interesa Javascript ¡Únetenos! Las aplicaciones web están dominando el mundo y el caballo de batalla es Javascript. Únete a nuestro grupo de peregrinos de este nuevo orden mundial ¡Y en Viña!'
+        lon: -71.55000305175781
+        lat: -33.0099983215332
+      - country: CO
+        city: Bogotá
+        link: 'http://www.meetup.com/Meteor-Colombia/'
+        name: Meteor Colombia
+        description: '<p>Conoce a otros desarrolladores usando&nbsp;<a href="https://www.meteor.com/">Meteor</a>.&nbsp;<span>Comparte tu conocimiento, apps y obtén retroalimentación de otros. Meteor es una plataforma de código abierto para construir web apps de alta calidad en fracción de tiempo, aun si eres un experto desarrollador o solo estas comenzando.</span></p>'
+        lon: -74.08999633789062
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/7/4/600_402902932.jpeg'
+        lat: 4.630000114440918
+      - country: MX
+        city: México City
+        link: 'http://www.meetup.com/javascriptmx/'
+        name: JavascriptMX
+        description: "<p>La comunidad de JavaScript de la Ciudad de México es una<span>&nbsp;organización sin fines de lucro con el objetivo de elevar la competitividad técnica de la ciudad con base en la colaboración y el compartir experiencias de carácter profesional.</span></p>\n<p><span>Nuestro interés se concentra en éstas tres áreas:</span></p>\n<blockquote>\n <p><b>Comunidad</b><span> — Eventos mensuales orientados a una herramienta tecnológica específica.</span></p>\n</blockquote>\n<blockquote>\n <p><b>Educación</b><span> — Talleres gratuitos para adquirir habilidades básicas e intermedias de código.</span></p>\n</blockquote>\n<blockquote>\n <p><b>Visibilidad</b><span> — Iniciativas para demostrar la viabilidad del país como un lugar creador de tecnología.</span></p>\n</blockquote> \n<p>La comunidad se rige por un <a href=\"https://github.com/javascriptmx/codigo-de-conducta\">código de conducta</a> con el que procuramos mantener un ambiente agradable para todas las personas que nos acompañan.&nbsp;</p>"
+        lon: -99.13999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/6/c/600_445142412.jpeg'
+        lat: 19.43000030517578
+      - country: MX
+        city: Matamoros
+        link: 'http://www.meetup.com/RGV-bots/'
+        name: RGV bots
+        description: 'This is a group for anyone interested in Hardware-Software Technologies Integration, mainly focused in OpenSource movment. All skills levels are welcome.'
+        lon: -97.5
+        lat: 25.8799991607666
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/Buenos-Aires-Node-js-Meetup/'
+        name: Buenos Aires Node.js Meetup
+        description: |-
+          <p>Curso de Node.js iniciando desde los conceptos básico de JavaScript hasta las técnicas de programación avanzada en Node.js y todo su ecosistema.</p>
+          <p><a href="http://www.educacionit.com/curso-de-nodejs-y-mongodb">Curso de Node.js en Buenos Aires</a><br>
+
+          </p>
+          <p><br>
+
+          </p>
+          <p><br>
+
+          </p>
+        lon: -58.369998931884766
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/f/a/c/600_405924492.jpeg'
+        lat: -34.61000061035156
+      - country: MX
+        city: Monterrey
+        link: 'http://www.meetup.com/nodejsmx/'
+        name: Node.js Comunidad Mexico
+        description: '<p>¡Bienvenid@s sean tod@s l@s programadoræs Javascript de cualquier parte que anden en México! Este grupo meetup fue creado para el beneficio de todos, podemos vernos nomás por cotorreo pero estoy seguro que por ahí hay gente como yo, tratando de sacar adelante un idea para un startup o también puede haber quien quiera simplemente mejorar como programador intercambiando ideas y trucos, e incluso habrá quienes estén buscando contactillos profesionales para agarrarse una mejor chamba. El caso es, que node.js está padre y la gente que lo usa suele caerme bien, ¡hay que vernos!.</p>'
+        lon: -100.31999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/a/8/0/600_405739072.jpeg'
+        lat: 25.670000076293945
+      - country: BR
+        city: Belo Horizonte
+        link: 'http://www.meetup.com/NodeBR-Minas-Gerais/'
+        name: NodeBR - Minas Gerais
+        description: |-
+          <p>A NodeBR é uma comunidade fundada por pessoas com interesse em aprender mais sobre Node.js assim como ajudar outras pessoas que possuem dúvidas nessa plataforma. No momento a comunidade é constituída por estes pontos de acesso principal</p>
+          <p>* A lista de e-mails é um grupo no Google onde você pode cadastrar o seu endereço de e-mail para enviar e receber e-mails das outras pessoas cadastradas. Esta lista mostrou-se extremamente eficaz na resolução de dúvidas de pessoas iniciantes no Node.js, assim como também é o ponto de encontro de discussões proveitosas e notícias sobre a plataforma.</p>
+          <p>* Nosso canal #nodebr no IRC é uma ferramenta de bate papo em tempo real, onde programadores trocam ideias e tiram dúvidas com outros membros que estão online, a ferramenta é nova e cresce junto com a comunidade. Para quem já possui instalado algum client IRC, nos achará facilmente no canal #nodebr na rede freenode.net, para aqueles que ainda não possuem um, podem acessar o link anterior para abrir o web chat e entrar diretamente no canal.</p>
+          <p>* O grupo de Meetup de São Paulo é onde organizamos nossos encontros e marcamos os eventos mensais que trazem informação e novidades sobre o mundo do Node.js.</p>
+          <p>* O site oficial da comunidade está em fase de planejamento mas já é uma ferramenta extramente importante na nossa comunidade, visto que ela abrigará as principais ferramentas que a comunidade julga importante, como você pode ver no brainstorming.</p>
+          <p>* @nodebr no Twitter.</p>
+          <p>Contribua para o projeto</p>
+          <p>Para começar a contribuir você deve procurar por alguma issue em aberto, veja aquela que você consiga resolver com facilidade. O próximo passo é fazer o fork do projeto e mandar uma pull request.</p>
+          <p>Links importantes</p>
+          <p>Lista de e-mail: <a href="https://groups.google.com/forum/?hl=pt#!forum/nodebr" target="_blank" class="linkified">https://groups.google.com/forum/?hl=pt#!forum/nodebr</a><br>
+
+           NodeBR no IRC: <a href="https://webchat.freenode.net/?channels=#nodebr" target="_blank" class="linkified">https://webchat.freenode.net/?channels=#nodebr</a><br>
+
+           Site da comunidade: <a href="http://nodebr.org" target="_blank" class="linkified">http://nodebr.org</a><br>
+
+           Site do Meetup de São Paulo: <a href="http://www.meetup.com/Node-js-Sao-Paulo" target="_blank" class="linkified">http://www.meetup.com/Node-js-Sao-Paulo</a><br>
+
+           Site do Meetup do Rio de Janeiro: <a href="http://www.meetup.com/Node-js-Rio-de-Janeiro" target="_blank" class="linkified">http://www.meetup.com/Node-js-Rio-de-Janeiro</a></p>
+        lon: -43.939998626708984
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/c/0/2/600_407735842.jpeg'
+        lat: -19.920000076293945
+      - country: BR
+        city: Sorocaba
+        link: 'http://www.meetup.com/HackLab-Sorocaba/'
+        name: HackLab Sorocaba
+        description: "<p>O\_<b>HackLab</b>\_é um hackerspace de Sorocaba, SP.<br>\n\n<br>\n\n Somos um grupo de (e para)\_entusiastas em tecnologia e nosso objetivo é projetar, testar, estudar e compartilhar conhecimentos sobre diversas tecnologias como programação, eletrônica, hardware, arduino, artes, música, RPG, jogos de tabuleiro e outros.</p>"
+        lon: -47.470001220703125
+        lat: -23.489999771118164
+      - country: MX
+        city: Monterrey
+        link: 'http://www.meetup.com/Javascript-Monterrey/'
+        name: Javascript Monterrey
+        description: 'Grupo para interesados y curiosos del lenguaje de programación Javascript. Buscamos difundir el lenguaje, promover el aprendizaje, conectar a la comunidad local y compartir experiencias laborales en torno al lenguaje.'
+        lon: -100.31999969482422
+        lat: 25.670000076293945
+      - country: CO
+        city: Cali
+        link: 'http://www.meetup.com/AngularJS-Cali/'
+        name: AngularJS Cali
+        description: 'Este grupo es para aquellos fascinados por el increible AngularJS. Tambien queremos oir que otras tecnologias web te interesan, y por que.'
+        lon: -76.51000213623047
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/d/8/600_410703032.jpeg'
+        lat: 3.4200000762939453
+      - country: MX
+        city: México City
+        link: 'http://www.meetup.com/Mexico-City-Angularjs-notes-Meetup/'
+        name: Mexico City Angularjs notes Meetup
+        description: This is a group for anyone interested in contribute to angularjs notes for beginners and for any beginner who wants to get started with the angularjs framework.
+        lon: -99.13999938964844
+        lat: 19.43000030517578
+      - country: MX
+        city: Pachuca
+        link: 'http://www.meetup.com/Pachupar-Develop/'
+        name: Pachupar Develop
+        description: |-
+          <p>Un meetup para personas interesadas en el aprendizaje de técnicas, herramientas, trucos, buenas prácticas y vicios del desarrollo de aplicaciones y sistemas, así como personas que deseen compartir el conocimiento adquirido a partir de su experiencia como programadores.</p>
+          <p>Conoce personas que lleven el mismo gusto al arte de codificar y materializar ideas a traves de los muchos lenguajes de programación.</p>
+          <p><img src="http://photos3.meetupstatic.com/photos/event/7/9/6/a/600_410971082.jpeg" style="max-height : 700px ; max-width : 700px ; margin : 5px"></p>
+          <p><br>
+
+          </p>
+        lon: -98.76000213623047
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/0/8/1/600_440689281.jpeg'
+        lat: 20.1200008392334
+      - country: BR
+        city: Rio de Janeiro
+        link: 'http://www.meetup.com/Meteor-Rio-de-Janeiro/'
+        name: Meteor Rio de Janeiro
+        description: |-
+          <p><span>Conheça outros desenvolvedores que usam Meteor. Compartilhe seus conhecimentos, apps, e receba </span><span>feedback&nbsp;</span><span>dos membros.</span><br></p>
+          <p><br>Meteor é uma plataforma open-source para a construção de aplicações web de alta qualidade em um curto período do tempo, não importa se você é um desenvolvedor especialista ou está apenas começando.<br></p>
+        lon: -43.20000076293945
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/1/a/8/600_415773192.jpeg'
+        lat: -22.90999984741211
+      - country: BR
+        city: Salvador
+        link: 'http://www.meetup.com/FrontendBa/'
+        name: Frontend Bahia
+        description: Grupo destinado à realizar encontros sobre Frontend na Bahia.
+        lon: -38.5
+        lat: -12.970000267028809
+      - country: MX
+        city: México City
+        link: 'http://www.meetup.com/nodersmx/'
+        name: NodersMX
+        description: "<p>Comunidad de Noders en México.</p>\n<p>Nos reunimos mensualmente no solo para compartir JavaScript entre el servidor y el navegador, también compartimos JavaScript con los desarrolladores... Y cerveza.</p>\n<p>Web: <a href=\"http://noders.mx\">http://noders.mx</a></p>\n<p>Twitter:\_<a href=\"https://twitter.com/nodersmx\">https://twitter.com/nodersmx</a><br>\n\n</p>\n<p>Facebook:\_<a href=\"https://www.facebook.com/Nodersmx\">https://www.facebook.com/Nodersmx</a></p>"
+        lon: -99.13999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/c/3/2/600_432095890.jpeg'
+        lat: 19.43000030517578
+      - country: CO
+        city: Bucaramanga
+        link: 'http://www.meetup.com/BucaraDev-Web-Developers/'
+        name: BucaraDev Web Developers
+        description: '<p>Un grupo para encontrar a los desarrolladores cerca a Bucaramanga, que sean apasionados con el desarrollo web y que les gusta estar al tanto de lo ultimo en tecnología de desarrollo. reunamos developers de front end y backend, mobile developers e interesados en traer la verdadera web a Bucaramanga.</p>'
+        lon: -73.13999938964844
+        lat: 7.130000114440918
+      - country: BR
+        city: Porto Alegre
+        link: 'http://www.meetup.com/Meteor-Porto-Alegre/'
+        name: Meteor Porto Alegre
+        description: |-
+          <p>Participe do nosso chat:&nbsp;<a href="https://demo.rocket.chat/channel/meetup-poa" class="linkified">https://demo.rocket.chat/channel/meetup-poa</a></p>
+          <p>Grupo criado para reunir pessoas interessadas em conhecer / aprender / ensinar / testar / desenvolver aplicações utilizando o framework Meteor.js. Meteor é uma plataforma open-source para desenvolvimento rápido de aplicações web de alta qualidade, indicada para quem está apenas começando ou para quem já é expert. Uma aplicação Meteor é um mix de Javascript que roda dentro de um web browser, Javascript que roda no no lado servidor Meteor dentro de um container Node.js, fragmentos HTML, regras CSS e conteúdos estáticos (imagens, vídeos, etc.).</p>
+        lon: -51.220001220703125
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/3/b/e/600_424457342.jpeg'
+        lat: -30.040000915527344
+      - country: MX
+        city: México City
+        link: 'http://www.meetup.com/Meteor-Mexico/'
+        name: Meteor México
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -99.13999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/1/b/a/600_426821402.jpeg'
+        lat: 19.43000030517578
+      - country: DO
+        city: Santo Domingo
+        link: 'http://www.meetup.com/Meteor-Dominican-Republic/'
+        name: Meteor Dominican Republic
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -69.91000366210938
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/b/f/0/600_425047152.jpeg'
+        lat: 18.479999542236328
+      - country: MX
+        city: Guadalajara
+        link: 'http://www.meetup.com/Meteor-GDL/'
+        name: Meteor GuadalajaraMX
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -103.3499984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/d/d/c/600_427480412.jpeg'
+        lat: 20.670000076293945
+      - country: MX
+        city: Culiacán
+        link: 'http://www.meetup.com/Culiacan-AngularJS-Meetup/'
+        name: Culiacán AngularJS Meetup
+        description: Intercambio de conocimientos y experiencias en programación web.
+        lon: -107.38999938964844
+        lat: 24.799999237060547
+      - country: VE
+        city: Ciudad Bolívar
+        link: 'http://www.meetup.com/Ciudad-Bolivar-Arduino-Node-Meetup/'
+        name: Ciudad Bolívar Arduino-Node Meetup
+        description: '"Arduino, Nodejs, tambien un poco de domotica y drones"'
+        lon: -63.599998474121094
+        lat: 8.100000381469727
+      - country: CO
+        city: Bogotá
+        link: 'http://www.meetup.com/Bogota-Startup-desde-0/'
+        name: Bogotá - Startup desde 0
+        description: '"La creación es un acto en grupo, es como desarrollamos autoestima &amp; confianza en nosotros mismos" (By @lorenaescandon) y "Que emprenda el que tenga la actitud, no el que tenga la urgencia de ganar dinero" (By @loogic)'
+        lon: -74.08999633789062
+        lat: 4.630000114440918
+      - country: BR
+        city: Rio de Janeiro
+        link: 'http://www.meetup.com/devbeers-Rio-de-Janeiro/'
+        name: devbeers Rio de Janeiro
+        description: |-
+          <p><span>devbeers é um evento focado em unir a comunidade de desenvolvedores! Levante da sua mesa e junte-se a nós para conversar sobre desenvolvimento e beber uma cerveja de graça. :)</span><br></p>
+          <p>O evento segue um código de conduta que vale para todas as partes (organizadores, participantes e patrocinadores), e queremos com a ajuda de vocês criar uma comunidade segura e receptiva para todos. Você pode encontrâ-lo nesse link:&nbsp;<a href="http://www.devbeers.io/codeofconduct/coc-portuguese.htm">http://www.devbeers.io/codeofconduct/coc-portuguese.htm</a></p>
+        lon: -43.20000076293945
+        lat: -22.90999984741211
+      - country: MX
+        city: Cancun
+        link: 'http://www.meetup.com/Cancun-JavaScript-Meetup/'
+        name: Cancun JavaScript Meetup
+        description: 'En este grupo aprenderemos a desarrollar aplicaciones y juegos para web y dispositivos móviles utilizando JavaScript. La idea es desarrollar nuestras habilidades, conocer nuevas tecnologías y relacionarte con otras personas. Si sabes programar en JavaScript, no importando si eres experto o principiante, y te interesa aprender y compartir tus conocimientos, únete a nuestro grupo.'
+        lon: -92.4800033569336
+        lat: 16.920000076293945
+      - country: CO
+        city: Montería
+        link: 'http://www.meetup.com/monteriajs/'
+        name: MonteríaJS
+        description: |-
+          <p>Hemos creado este grupo con el fin de reunir, compartir y aprender de los desarrolladores JavaScript de la ciudad de Montería, Colombia. Nuestra filosofía será siempre la de mantener un ambiente informal, nada estricto en ningún sentido. Así que cualquier colaboración, en cualquier sentido, será muy bien recibida. <br> <br></p>
+          <p>Es importante mantener el respeto hacia otras personas y por ello seguimos el código de conducta el cual pueden observar aquí --&gt;&nbsp;<a href="https://github.com/MonteriaJS/codigo-de-conducta/blob/master/README.md">Código de Conducta</a><br> <br></p>
+          <p>¡Bienvenido!</p>
+        lon: -75.88999938964844
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/5/9/8/600_433366488.jpeg'
+        lat: 8.75
+      - country: MX
+        city: Misantla
+        link: 'http://www.meetup.com/NodeBots-Misantla/'
+        name: NodeBots Misantla
+        description: 'Personas interesadas en experimentar nuevas tecnologias, la robotica, nodejs, android, desarrollo web.'
+        lon: -96.83000183105469
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/7/8/4/600_440306500.jpeg'
+        lat: 19.93000030517578
+      - country: CO
+        city: Pereira
+        link: 'http://pereirajs.org/'
+        name: PereiraJS
+        description: Comunidad de aprendizaje del lenguaje Javascript
+        lon: -75.68000030517578
+        lat: 4.809999942779541
+        source_of_truth: true
+      - country: MX
+        city: Zapopan
+        link: 'http://www.meetup.com/TequilaJS-Zapopan/'
+        name: TequilaJS Zapopan
+        description: 'Este es un grupo para aquellos interesados en el desarrollo de software basado principalmente en JavaScript, ya seas backend o frontend, ya seas un master de java o .net, ya seas un senesi de JavaScript o apenas estes comenzando en el desarrollo web, este meetup es para tí. This is a group for those interested on software development mainly based on JavaScript tecnologies, if you are a front or back end developer, if you are a java or .net master, if you are a JavaScript sensei or just starting on web development, this meetup is for you.'
+        lon: -103.4000015258789
+        lat: 20.719999313354492
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/beerjs-ba/'
+        name: Beer.js Buenos Aires
+        description: '<p>A meetup group for beer-drinkers and technology-oriented individuals looking to become closer with the JavaScript community in Buenos Aires. Join us for casual drinking and nerd experience-swapping!</p>'
+        lon: -58.369998931884766
+        lat: -34.61000061035156
+      - country: BR
+        city: Rio de Janeiro
+        link: 'http://www.meetup.com/ClickIT-Bitbucket-Meetup/'
+        name: ClickIT Bitbucket Meetup
+        description: Este grupo é para falar sobre as novas tecnologias que vão ser usadas na empresa ClickIT
+        lon: -43.20000076293945
+        lat: -22.90999984741211
+      - country: CL
+        city: Santiago
+        link: 'http://www.meetup.com/HackSantiago/'
+        name: HackSantiago
+        description: |-
+          <p>Welcome to HackSantiago! Join local like-minded developers, entrepreneurs and tech-enthusiasts for a night of pizza, beer, giveaways and learning a new thing or two. We will have thought leaders in the field speaking about hot topics in the startup and tech world. We'll be discussing software development, project management, programming languages and other tangential topics. Thanks for joining our community! I look forward to meeting you.&nbsp;</p>
+          <p>See you soon!&nbsp;</p>
+          <p>Daniela</p>
+          <p>¡Bienvenidos a HackSantiago! Únete desarrolladores, empresarios y entusiastas locales de la tecnología para una noche de pizza, cervezas, sorteos y aprender una o dos cosas nuevas. Tendremos expertos hablando de las temas de actualidad en el mundo de los startups y la tecnología. Discutiremos el desarrollo de software, project management, nuevas lenguajes de programación y otros temas afínes. ¡Gracias por unirte a nuestra comunidad!&nbsp;</p>
+          <p>¡Hasta pronto!&nbsp;</p>
+          <p>Daniela</p>
+          <p> <br></p>
+          <p><a href="http://www.hacksantiago.com">hacksantiago.com&nbsp;</a></p>
+        lon: -70.63999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/d/8/e/600_440111662.jpeg'
+        lat: -33.459999084472656
+      - country: PA
+        city: Panamá
+        link: 'http://www.meetup.com/Panamajs/'
+        name: PanamáJS
+        description: |-
+          <p>PanamáJS es la comunidad de usuarios de Javascript. Únete a la comunidad para aprender y compartir conocimiento sobre JavaScript. Realizamos diferentes eventos mensuales que ampliarán tus conocimientos sobre esta tecnología y otras tecnologías similares.</p>
+          <p>En PanamáJS nos regimos bajo un <a href="http://es.confcodeofconduct.com/">código de conducta</a>.</p>
+          <p>Entre nuestros eventos mensuales están los siguientes:</p>
+          <p>PanamaJS: un evento mensual gratuito donde desarrolladores se reúnen en un espacio y se comparten charlas y exposiciones acerca de Javascript.&nbsp;</p>
+          <p><b>PanamáJS</b>&nbsp;ayuda a crear espacios sociales que fortalezcan comunidades alrededor del <i>desarrollo de&nbsp;</i><i>software</i><span>. No es requerimiento alguno consumir alcohol para participar.</span></p>
+        lon: -79.52999877929688
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/0/c/4/600_441064292.jpeg'
+        lat: 8.970000267028809
+      - country: CO
+        city: Medellín
+        link: 'http://www.meetup.com/Robotica-Medellin/'
+        name: Robotica Medellín
+        description: '<p>Interesado en temas de electrónica, computación y mecánica? Te gusta trabajar con las nuevas tecnologias open source? quieres saber algo mas allá de un robot seguidor de línea? Tienes algún proyecto para mostrar pero no sabes donde hacerlo? Este espacio estará creado para fomentar una cultura, que no es propia de los asíaticos ni de los norteamericanos. En medellín se puede hablar de robótica!!!</p>'
+        lon: -75.58999633789062
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/0/d/6/600_442160694.jpeg'
+        lat: 6.25
+      - country: CO
+        city: Manizales
+        link: 'http://www.meetup.com/ManizalesJS/'
+        name: ManizalesJS
+        description: '<p>Este es un grupo con el objetivo de integrar desarrolladores en la ciudad de Manizales, alrededor de Javascript; tecnología cuyo uso está en auge y crecimiento. <br>El objetivo es encontrar personas que compartan estos intereses, para compartir, aprender y crecer juntos profesionalmente. <br>La idea, como en grupos similares en otras ciudades es mantener un ambiente informal, donde es bienvenida cualquier tipo de participación y colaboración que nos ayude a todos a crecer como desarrolladores.</p>'
+        lon: -75.5199966430664
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/f/b/c/600_433977276.jpeg'
+        lat: 5.059999942779541
+      - country: PE
+        city: Lima
+        link: 'http://www.meetup.com/ReactJS-Peru/'
+        name: ReactJS Lima
+        description: '<p>Come for drinks, share stories, and hack using ReactJS</p>'
+        lon: -77.05000305175781
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/3/b/2/600_433833714.jpeg'
+        lat: -12.069999694824219
+      - country: MX
+        city: Guanajuato
+        link: 'http://www.meetup.com/Meteor-Guanajuato/'
+        name: Meteor Guanajuato
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -101.27999877929688
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/f/e/4/600_433836836.jpeg'
+        lat: 21.020000457763672
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/banodejs/'
+        name: BA Node.js Meetup
+        description: '<p>La idea de BANode surgió desde la comunidad y para la comunidad. Desde proponer las charlas, el proceso de selección de los temas hasta la ubicación de los meetups son discutidos entre organizadores. ¿Quiénes son los organizadores? Cualquier persona que colabore es considerada parte de la organización.</p>'
+        lon: -58.369998931884766
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/e/d/a/600_438712954.jpeg'
+        lat: -34.61000061035156
+      - country: BR
+        city: Natal
+        link: 'http://www.meetup.com/FEMUG-RN/'
+        name: 'Natal.js -> FEMUG-RN'
+        description: |-
+          <p>Dedicado à comunidade de desenvolvimento Front-End do RN. <br></p>
+          <p>Qualquer pessoa que goste de compartilhar conhecimentos, trabalhe com a linguagem profissionalmente ou que seja apenas um "hobbista", é bem-vinda.&nbsp;</p>
+          <p><b>O que é o FEMUG:</b></p>
+          <p>O "Front-End Meet-Up Group" é um projeto que nasceu da necessidade de unir os desenvolvedores Front-End de São Paulo, e então tornou-se uma idéia coletiva, para que o acesso à informação seja feito em qualquer lugar que haja interesse do aprendizado.</p>
+          <p>O evento&nbsp;NÃO&nbsp;pode visar o lucro de um ou mais organizadores. É igualmente restritivo a prática de qualquer preconceito em relação a qualquer pessoa que tenha interesse de aprender ou qualquer tecnologia.</p>
+          <p>Trata-se de um evento para pessoas interessadas em aprender, evoluir e dividir conhecimentos relacionados ao front-end e tecnologias periféricas relacionadas.</p>https://github.com/braziljs/femug/
+          <br>
+        lon: -35.220001220703125
+        lat: -5.800000190734863
+      - country: AR
+        city: Resistencia
+        link: 'http://www.meetup.com/Resistencia-Corrientes-TechUpdate-Meetup/'
+        name: Resistencia - Corrientes TechUpdate Meetup
+        description: 'Si sos desarrollador frontEnd o BackEnd, si solamente te gusta investigar y aprender sobre nuevas tecnologías de desarrollo, si te gusta estar actualizado sobre herramientas que ayudan a mejorar el mundo sistémico, te invito a unirte a esta meetup donde el lenguaje, los conocimientos o la experiencia no es un límite.'
+        lon: -58.9900016784668
+        lat: -27.459999084472656
+      - country: CO
+        city: Villavicencio
+        link: 'http://www.meetup.com/Villavicencio-JS/'
+        name: VillavicencioJS
+        description: 'Esta es la primer comunidad Javascript de la ciudad e Villavicencio, ayúdanos a crear actividades que incentiven el uso de tecnologías innovadoras en los proyectos de software de la región y el país.'
+        lon: -73.63999938964844
+        lat: 4.150000095367432
+      - country: BR
+        city: Rio de Janeiro
+        link: 'http://www.meetup.com/tecnologia-e-cafe/'
+        name: 'Tecnologia & Café'
+        description: |-
+          <p>O Curto Café é um ambiente muito especial para conversar sobre tecnologia: uma cafeteria open source escondida no coração do Centro do Rio de Janeiro.</p>
+          <p><span>Junte-se a nós para beber um café especial e conversar sobre desenvolvimento web, café, sustentabilidade e como isso tudo se relaciona.</span> <br></p>
+        lon: -43.20000076293945
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/4/e/c/600_434669932.jpeg'
+        lat: -22.90999984741211
+      - country: PE
+        city: Lima
+        link: 'http://www.meetup.com/Lima-NodeJS-Meetup/'
+        name: Lima NodeJS Meetup
+        description: '<p>Llamando a todos los desarrolladores de software de Javascript. Reúnase con sus contemporáneos, aprender acerca de nuevas tecnologías y divertirse en nuestros eventos dedicados a NodeJS</p>'
+        lon: -77.05000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/1/7/8/600_434869528.jpeg'
+        lat: -12.069999694824219
+      - country: MX
+        city: Monterrey
+        link: 'http://www.meetup.com/Monterrey-AngularJS-Meetup/'
+        name: Monterrey AngularJS Meetup
+        description: '<p>Este es un grupo para promover buenas practicas y conocimiento fuerte sobre el desarrollo con la libreria Angularjs, así como para crear nuevo contenido de calidad. No es necesaria ninguna experiencia de desarrollo pero si muchas ganas de aprender y colaborar para crear grandes proyectos.</p>'
+        lon: -100.31999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/7/2/3/600_434862787.jpeg'
+        lat: 25.670000076293945
+      - country: CO
+        city: Barranquilla
+        link: 'http://www.meetup.com/BarranquillaJS/'
+        name: BarranquillaJS
+        description: |-
+          <p>Este es un grupo para todos los desarrolladores, entusiastas y apasionados por Javascript en Barranquilla y la costa atlantica.</p>
+          <p><a href="https://github.com/orgs/BAQJS">Github</a><br></p>
+          <p><a href="https://twitter.com/BAQ_JS">Twitter</a></p>
+          <p>Come and join us (we have cookies)!</p>
+        lon: -74.81999969482422
+        lat: 11
+      - country: AR
+        city: Córdoba
+        link: 'http://www.meetup.com/Meteor-Cordoba/'
+        name: Meteor Cordoba
+        description: '<p>Reunir otros desarrolladores que usen o quieran usar Meteor. Comparte tu conocimiento, aplicaciones y obtene recomendaciones de otros desarrolladores/programadores. Meteor es una plataforma de codigo abierto para construir rapidamente aplicaciones web y moviles de alta calidad para expertos o programadores novatos.</p>'
+        lon: -64.19000244140625
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/e/8/6/600_435392390.jpeg'
+        lat: -31.399999618530273
+      - country: BR
+        city: Rio de Janeiro
+        link: 'http://www.meetup.com/barrajs/'
+        name: Barra JS
+        description: '<p>Esse grupo é para os amantes do JavaScript. Outras linguagens são bem vindas. =)</p>'
+        lon: -43.20000076293945
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/8/6/6/600_435775398.jpeg'
+        lat: -22.90999984741211
+      - country: BR
+        city: Belo Horizonte
+        link: 'http://www.meetup.com/MEAN-BH/'
+        name: MEAN BH
+        description: 'Desenvolvedores Full-Stack JavaScript. Desenvolvimento de aplicações web com MongoDB, Express, Angular e Node.'
+        lon: -43.939998626708984
+        lat: -19.920000076293945
+      - country: BR
+        city: Ponta Grossa
+        link: 'http://www.meetup.com/PontaGrossaJS/'
+        name: PG.js
+        description: |-
+          <p>Grupo dedicado aos desenvolvedores JavaScript em Ponta Grossa e na região dos Campos Gerais.&nbsp;</p>
+          <p>Github: <a href="https://github.com/pgjs" class="linkified">https://github.com/pgjs</a>&nbsp;</p>
+          <p>Grupo no Facebook: <a href="https://www.facebook.com/groups/pontagrossajs" class="linkified">https://www.facebook.com/groups/pontagrossa...</a> <br></p>
+        lon: -50.15999984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/1/3/d/600_436096701.jpeg'
+        lat: -25.09000015258789
+      - country: BR
+        city: Fortaleza
+        link: 'http://www.meetup.com/Ionic-Fortaleza-Meetup/'
+        name: Ionic Fortaleza Meetup
+        description: Meetups para interessantes no Ionic Framework e Aplicativos Híbridos em geral e sua vasta gama de tecnologias.
+        lon: -38.59000015258789
+        lat: -3.7799999713897705
+      - country: MX
+        city: Guadalajara
+        link: 'http://www.meetup.com/Guadalajara-JS/'
+        name: Guadalajara JS
+        description: |-
+          <p>Este es un grupo para todos los interesado en el lenguaje JavaScript. Tanto en el Front-end como en el Back-end. La meta es tener reuniones mensuales, donde se hable sobre las capacidades del lenguaje y como lo usamos para resolver problemas, para invitar a más gente a usarlo y mejorar nuestras habilidades.</p>
+          <p>El segundo objetivo es hacer que el último martes de cada mes sea el mejor martes de cada mes :)</p>
+        lon: -103.3499984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/6/5/f/600_436298495.jpeg'
+        lat: 20.670000076293945
+      - country: CO
+        city: Medellín
+        link: 'http://www.meetup.com/Ember-Medellin/'
+        name: Ember Medellin
+        description: '<p>Ember.js Medellin Meetup para amantes de Ember.js, para mantenernos actualizados y en constante mejoramiento. Quienes deseen aprender son bienvenidos!</p>'
+        lon: -75.58999633789062
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/7/1/6/600_436102294.jpeg'
+        lat: 6.25
+      - country: AR
+        city: Córdoba
+        link: 'http://www.meetup.com/EmberJS-Cba/'
+        name: Ember.js Cba
+        description: '<p>Grupo de cordobeses embereños que comparten experiencias, novedades, curiosidades y alguna que otra demostración interesante del día a día con el framework Ember.js.</p>'
+        lon: -64.19000244140625
+        lat: -31.399999618530273
+      - country: AR
+        city: Rosario
+        link: 'http://www.meetup.com/JavaScript-Everywhere-in-Rosario/'
+        name: JavaScript Everywhere in Rosario
+        description: '<p>La idea es juntarnos a compartir ideas y experiencias sobre el pasado, presente y futuro de JavaScript, sin importar el nivel con el que cuente cada uno, o si conocen o no el lenguaje. Te invitamos a sumarte a esta página y también a nuestro grupo de facebook en donde llevamos el día a día de nuestra&nbsp;<span>comunidad:&nbsp;</span><a href="https://www.facebook.com/groups/js.everywhere/">https://www.facebook.com/groups/js.everywhere/</a></p>'
+        lon: -60.66999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/e/c/9/600_436888361.jpeg'
+        lat: -32.95000076293945
+      - country: BR
+        city: Salvador
+        link: 'http://www.meetup.com/Salvador-MeteorJS-Meetup/'
+        name: Salvador MeteorJS Meetup
+        description: 'Grupo de interessados na mágica do MeteorJS, aplicações real-time, mongodb em aplicações e desenvolvimento de novas ideias e do empreendedorismo inovador.'
+        lon: -38.5
+        lat: -12.970000267028809
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/Buenos-Aires-DEVS-have-the-power-Choose-your-next-work/'
+        name: Buenos Aires. DEVS have the power. Choose your next work.
+        description: 'We believe the best developers have the power and opportunity to choose their next work, their next company or a partner for a startup. Here is a space were we can meet and make that happen.'
+        lon: -58.369998931884766
+        lat: -34.61000061035156
+      - country: BR
+        city: São Carlos
+        link: 'http://www.meetup.com/opensanca/'
+        name: opensanca
+        description: |-
+          <p>Olá, se você veio até aqui, ficamos felizes! <br> <br></p>
+          <p>Esse é um dos canais para discutirmos sobre desenvolvimento Open Source, q<span>ueremos que esses encontros sejam além de tecnologias; esperamos que ele forneça apoio à todos em diversos segmentos e vertentes; s</span><span>eja parte disso e ajude a comunidade Open-Sanca para que este Meetup ganhe força, não importa se você é iniciante, ninja-samurai ou Goku das profundezas do Egeu.</span></p>
+          <p><span>Afinal, o que a comunidade espera de você desenvolvedor? Quando você ouve a palavra </span><b>contribua</b><span>, espera-se que possamos ir além de githubs, palestras, workshops e afins, por isto você é uma peça importante nessa engrenagem, </span><b>contribua</b><span>!</span></p>
+          <p><span>Queremos proporcionar um bate-papo(OpenTalks) no qual todos possam colaborar e &nbsp;fomentar um networking com empresas, desenvolvedores, comunidades acadêmicas, afinal hoje praticamente o que todos falam, respiram e exalam é sobre </span><b>tec</b><span><b>nologia .</b></span></p>
+          <p><span>Faça parte do OpenSanca, traga seus amigos, independente da carreira que segue, todos podem colaborar, abaixo enumeramos alguns assuntos que abordamos durante nossos encontros, mas fique a vontade para apontar tópicos que você julgar válido também, afinal estamos falando sobre ser <b>OPEN.</b></span></p>
+          <p>Tópicos:</p>
+          <p>- Oferecer Palestras (OpenTalks) &nbsp;<br>- Oferecer Workshops&nbsp;<br>- Oferecer Hangouts (Spin-Off)&nbsp;<br><br></p>
+          <p>E o que você vai ver nesse tópicos? Oras, será sobre desenvolvimento de software adotando as principais linguagens e tecnologias do mercado Open Source como Java, Python, Groovy, Ruby, Embarcados, JavaScript, Android, Swift, entre outras! ;)</p>
+          <p>Esperamos vocês! &nbsp;;)<br><br></p>
+          <p>Opensanca&nbsp;</p>
+          <p>&nbsp;<a href="http://www.opensanca.com.br">www.opensanca.com</a>&nbsp;| opensanca@gmail.com</p>
+        lon: -47.88999938964844
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/f/d/8/600_438773208.jpeg'
+        lat: -22.020000457763672
+      - country: MX
+        city: Cuernavaca
+        link: 'http://www.meetup.com/CuernavacaJS/'
+        name: CuernavacaJS
+        description: |-
+          <p><span>El objetivo principal es que la comunidad se conozca, intercambie experiencias y conocimientos, no importa si recién empiezas o si usas otro lenguaje por que sin importarlo todos convergemos en un mismo punto : <b>javascript</b>.</span> <br></p>
+          <p>Planeamos reunirnos al menos 1 vez al mes, con platicas de temas que la comunidad proponga y otras veces tendremos talleres para ir mejorando y afinando nuestras habilidades.</p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: -99.25
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/b/c/d/600_438975309.jpeg'
+        lat: 18.920000076293945
+      - country: GT
+        city: Guatemala
+        link: 'http://www.meetup.com/Guatemala-AngularJS-Meetup/'
+        name: Guatemala AngularJS Meetup
+        description: '<p>Este grupo es creado con la finalidad de dar a conocer la comunidad de AngularJS en Guatemala y reunirse para conocer más acerca del framework, transmitir todos nuestros conocimientos como aprender de ustedes, queremos ser mejores cada día y apuesto a que ustedes también, estamos en búsqueda de reunir a todos los amantes de la tecnología web, los invitamos a compartir con la comunidad de AngularJs.</p>'
+        lon: -90.55000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/3/b/c/600_446506012.jpeg'
+        lat: 14.630000114440918
+      - country: BR
+        city: Recife
+        link: 'http://www.meetup.com/NodeBotsRec/'
+        name: NodeBotsRec
+        description: |-
+          <p>Este é o primeiro ano do evento&nbsp;<a href="http://nodebots.io/">NodeBots Day</a>&nbsp;aqui Recife (<a href="http://nodebotsrec.github.io/">NodebotsRec</a>) e nós estamos extremamente agradecidos e honrados por puder contar com o apoio da&nbsp;<a href="http://www.robothink.org/#!arena/c3c5">Arena ROBOthink</a>&nbsp;do&nbsp;<a href="http://www.cesar.org.br/">CESAR</a>,&nbsp;<a href="http://robolivre.org/">Robô livre</a>&nbsp;e do&nbsp;<a href="http://csbc2015.cin.ufpe.br/">CSBC</a>, com o patrocínio deles o evento deste ano será totalmente grátis, não vamos precisar pagar nada para participar deste evento. Eles gentilmente cederam o espaço, kits de robótica e computadores, muito obrigado a todos vocês que estão apoioando e viabilizando este evento.</p>
+          <p>O foco do NodeBots day Recife é compartilhar e desfrutar do conhecimento e da companhia um do outro, vamos nos encontrar e construir robôs juntos.&nbsp;</p>
+          <p>Não haverá negociações e nem vendas de nada.&nbsp;Não haverá prêmios, para nós o maior prêmio é a satisfação de fazer algo incrível juntos.</p>
+          <p>Concordamos e seguimos o código de conduta do Nodebots Day Internacional.</p>
+        lon: -34.91999816894531
+        lat: -8.079999923706055
+      - country: CO
+        city: Medellín
+        link: 'http://www.meetup.com/Emergent-Software-Technologies-by-VP/'
+        name: Emergent Software Technologies by VP
+        description: '<p>We are a group of people who loves to adopt new technologies for software development. We share our knowledge and invite experts on different fields to talk about their experiences so that we can apply them in our own projects.</p>'
+        lon: -75.58999633789062
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/f/8/9/600_448408553.jpeg'
+        lat: 6.25
+      - country: BR
+        city: Florianópolis
+        link: 'http://www.meetup.com/meteor-floripa/'
+        name: Meteor Floripa
+        description: |-
+          <p>Grupo pra reunir a galera que já programa ou está aprendendo a mexer com o Meteor, uma plataforma para NodeJS (server side em JavaScript).</p>
+          <p>Também são bem vindos empreendedores que pensam ou estão pensando em abrir uma startup ou um novo negócio nesta plataforma.</p>
+          <p>A ideia é programarmos alguns encontros informais para trocarmos conhecimentos, ideias, processos, oportunidades... Colaboração!</p>
+          <p>Sugestões são bem vindas! =)</p>
+        lon: -48.540000915527344
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/f/a/5/600_440364485.jpeg'
+        lat: -27.600000381469727
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/Sencha-Buenos-Aires/'
+        name: Sencha Buenos Aires
+        description: '<p>Si desarrollas con algún producto Sencha, como Extjs, Touch, Architect, etc o planeas interiorizarte en este framework unite, estamos proponiendo juntarnos ni bien tengamos varios miembros inscriptos.</p>'
+        lon: -58.369998931884766
+        lat: -34.61000061035156
+      - country: MX
+        city: Pátzcuaro
+        link: 'http://www.meetup.com/Tardes-de-Hackers-Makers/'
+        name: 'Hackers & Makers Michoacán'
+        description: |-
+          <p>Es un grupo donde promovemos las culturas maker y hacker, las cuales actualmente están provocando un cambio en el mundo dando como resultado, Startups, PYMES y nuevos paradigmas en nuestra sociedad.</p>
+          <p><br></p>
+          <p><br></p>
+          <p><a class="embedded" href="https://youtu.be/tmmPlISETJg">https://youtu.be/tmmPlISETJg</a></p>
+          <br>
+          <p><a class="embedded" href="https://youtu.be/mklywR7TQxs">https://youtu.be/mklywR7TQxs</a></p>
+        lon: -101.62000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/7/4/7/600_440935111.jpeg'
+        lat: 19.520000457763672
+      - country: AR
+        city: Córdoba
+        link: 'http://www.meetup.com/DronCba/'
+        name: DronCba
+        description: '<p>Este grupo esta destinado a compartir código abierto y experiencias en el control de Drones.</p>'
+        lon: -64.19000244140625
+        lat: -31.399999618530273
+      - country: BR
+        city: Recife
+        link: 'http://www.meetup.com/NodeJS-Recife-Meetup/'
+        name: NodeJS Recife Meetup
+        description: 'Grupo sobre desenvolvimento voltado ao Node.js e todo seu ecossistema. Sejam todos bem vindos e "Always bet on JS"!'
+        lon: -34.91999816894531
+        lat: -8.079999923706055
+      - country: AR
+        city: Santa Fe
+        link: 'http://www.meetup.com/js-Litoral/'
+        name: JavaScript Litoral
+        description: |-
+          <p>Este es un grupo para los interesados en tecnologías JavaScript. También para juntarnos a tomar cerveza y hacer amigos. Sumate.</p>
+          <p> <br></p>
+          <p>tambien estamos en Slack!</p>
+          <p>http://jslitoral-slackin.herokuapp.com<br></p>
+        lon: -60.689998626708984
+        lat: -31.600000381469727
+      - country: BR
+        city: Belo Horizonte
+        link: 'http://www.meetup.com/MinasJS/'
+        name: MinasJS
+        description: 'Grupo de discussão sobre conceitos, ferramentas e/ou tecnologias que se relacionem com JavaScript,  seja no Client-Side, Server-Side ou qualquer outro meio que a linguagem esteja presente.'
+        lon: -43.939998626708984
+        lat: -19.920000076293945
+      - country: EC
+        city: Quito
+        link: 'http://www.meetup.com/Quito-js/'
+        name: Quito.js
+        description: 'Este es un grupo de programadores con la visión de que Javascript es el nuevo lenguage de máquina. Trataremos sobre todo el mundo de Javascript: nuevos tipos de bases de datos, aprendizaje automático de máquina, lenguajes de consulta de JSON, mapas geográficos, diseño 3D, frameworks, librerías, aplicaciones híbridas, y en general todas las nuevas tecnologías que tienen a Javascript como su centro. El cielo es el límite! (y el espacio en disco :)'
+        lon: -78.5
+        lat: -0.1899999976158142
+      - country: BR
+        city: Joinville
+        link: 'http://www.meetup.com/JS4Girls-Joinville/'
+        name: JS4Girls Joinville
+        description: 'Evangelizar Javascript para incentivar garotas a participarem mais de eventos, palestrarem em eventos, compartilhar conteúdo, aprender e conhecer outras pessoas :D'
+        lon: -48.84000015258789
+        lat: -26.31999969482422
+      - country: PE
+        city: Lima
+        link: 'http://www.meetup.com/Abakio-Javascript-Group/'
+        name: Abakio Javascript Group
+        description: '<p>Este es un grupo para todos los interesados en la tecnologia web basada en javascript.</p>'
+        lon: -77.05000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/4/1/0/600_442662000.jpeg'
+        lat: -12.069999694824219
+      - country: CO
+        city: Cali
+        link: 'http://www.meetup.com/Meteor-Cali/'
+        name: Meteor Cali
+        description: '<p>Conoce a otros desarrolladores usando Meteor. Comparte tu conocimiento, aplicaciones y obtén retroalimentación de otros. Meteor es una plataforma open-source que permite desarrollar aplicaciones de alta calidad en una fracción de tiempo, no importa si eres un desarrollador experimentado o tan solo estás empezando! Para más información puedes visitar la página oficial de Meteor <a href="http://meteor.com" class="linkified">http://meteor.com</a> y su repositorio oficial en Github <a href="https://github.com/meteor/meteor" class="linkified">https://github.com/meteor/meteor</a></p>'
+        lon: -76.51000213623047
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/6/9/5/4/600_443006964.jpeg'
+        lat: 3.4200000762939453
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/Free-Code-Camp-Sao-Paulo/'
+        name: Free Code Camp São Paulo
+        description: 'Esse é um grupo para interessados em se reunir, aprender, fazer os exercícios do Free Code Camp. Estudantes de todos os níveis de serão aceitos.'
+        lon: -46.630001068115234
+        lat: -23.530000686645508
+      - country: MX
+        city: Culiacán
+        link: 'http://www.meetup.com/Culiacan-front-end/'
+        name: Culiacán front-end
+        description: 'Imagina un Sinaloa sin frontends, que CAOS  :(, reunámonos y compartamos nuestras experiencias como desarrolladores.'
+        lon: -107.38999938964844
+        lat: 24.799999237060547
+      - country: CO
+        city: Bogotá
+        link: 'http://www.meetup.com/Meteor-Bogota/'
+        name: Meteor Bogotá
+        description: '<p>Este es un grupo para todos los interesados en aprender sobre METEOR. Son bienvenidos desde expertos desarrolladores, hasta principiantes que están creando su primera aplicación.</p>'
+        lon: -74.08999633789062
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/4/7/1/600_443289329.jpeg'
+        lat: 4.630000114440918
+      - country: CL
+        city: Santiago
+        link: 'http://www.meetup.com/Javascript-Chile/'
+        name: Javascript Chile
+        description: |-
+          <p>¡Llamando a todos los <b>JS Fans</b>! (Y los <b>JS Curious</b> también)&nbsp;</p>
+          <br>
+          <p>Javascript es el lenguaje más popular de la web, y ahora...¡fuera de ella! Este grupo está enfocado en armar y ser un espacio los diferentes meetups de Javascript, NodeJS, &nbsp;y todos sus sabores en Chile (Typescript, JSX, y el resto son todos bienvenidos) <br>:)&nbsp;</p>
+          <br>
+          <p>Nos juntamos a lo largo del país, una vez al mes, a aprender, compartir y conocer otros dudes and dudettes que les gusta este mítico personaje&nbsp;llamado "<b>El Javascripto</b>" en Latinoamérica (o JavaScript para los más amigos).&nbsp;</p>
+          <br>
+          <p>Un abrazo asíncrono, ¡y nos vemos en los meetups!</p>
+          <br>
+        lon: -70.63999938964844
+        lat: -33.459999084472656
+      - country: BR
+        city: Natal
+        link: 'http://www.meetup.com/Meetup-Microcontroladores-IoT-Natal/'
+        name: Microcontroladores IoT Natal
+        description: |-
+          <p>Pessoal entusiasta em microcontroladores (arduino, launchpad, pic ...) e que gosta de realizar projetos DIY aliando internet das coisas. Queremos conhecer pessoas que gostem de aprender e partilhar conhecimentos acerca desta temática. Revolucionadores, empreendedores, malucos por fazer acontecer e sonhadores são todos bem vindos!</p>
+          <p>Também temos um grupo no Facebook, <a href="https://www.facebook.com/groups/1523749987943402/?fref=nf">entre aqui</a>!</p>
+        lon: -35.220001220703125
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/9/f/f/600_444378943.jpeg'
+        lat: -5.800000190734863
+      - country: BR
+        city: Porto Alegre
+        link: 'http://www.meetup.com/Node-js-Porto-Alegre-Meetup/'
+        name: Node.js Porto Alegre Meetup
+        description: "<p>Meet other Node.js developers. Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient.</p>"
+        lon: -51.220001220703125
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/0/0/9/600_444676393.jpeg'
+        lat: -30.040000915527344
+      - country: MX
+        city: Monterrey
+        link: 'http://www.meetup.com/Tecnologia-Digital/'
+        name: Tecnología Digital
+        description: 'Grupo para interesados en IT, en programación, testing y metodología Ágil. Buscamos difundir diferentes pláticas técnicas donde los participantes puedan aprender las tecnologías digitales modernas como Angular, IOS, Devops, etc. Contaremos con al menos un evento por mes.'
+        lon: -100.31999969482422
+        lat: 25.670000076293945
+      - country: BR
+        city: Moji das Cruzes
+        link: 'http://www.meetup.com/Front-Back-Mogi/'
+        name: 'Front&Back Mogi'
+        description: |-
+          <p>O<b> Front&amp;Back</b> é um grupo de estudos gratuito para a região de Mogi das Cruzes e Alto Tietê.&nbsp;</p>
+          <p>O objetivo principal do grupo é promover o networking e disseminar o conhecimento FrontEnd e BackEnd. Abordamos diversos assuntos como HTML, CSS, JavaScript, MEAN(MongoDb, Express, AngularJS e NodeJS), JQuery, Arquitetura.&nbsp;</p>
+          <p><b>Sobre os Eventos</b></p>
+          <p>Os eventos (Mini Cursos e Palestras) são para qualquer pessoa que esteja interessada em participar(independente do nível de conhecimento).&nbsp;</p>
+          <p>A entrada para os eventos é 1 kg de alimento não perecível que será doado para alguma instituição de caridade (Você aprende e ainda ajuda quem precisa).&nbsp;</p>
+          <p>Sempre teremos eventos.</p>
+        lon: -46.209999084472656
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/2/a/e/600_444964782.jpeg'
+        lat: -23.520000457763672
+      - country: BR
+        city: Joinville
+        link: 'http://www.meetup.com/femug-jlle/'
+        name: FEMUG JLLE
+        description: |-
+          <p><span>O "Front-End Meet-Up Group" é um projeto que nasceu da necessidade de unir os desenvolvedores para que o acesso à informação seja feito em qualquer lugar que haja interesse do aprendizado. Trata-se de um evento para pessoas interessadas em aprender, evoluir e dividir conhecimentos.</span><br></p>
+          <p><a href="https://github.com/braziljs/femug/">github.com/braziljs/femug</a> <br> <br><a href="https://groups.google.com/forum/#!forum/femug-jlle" class="linkified">https://groups.google.com/forum/#!forum/fem...</a> <br></p>
+        lon: -48.84000015258789
+        lat: -26.31999969482422
+      - country: VE
+        city: Caracas
+        link: 'http://www.meetup.com/Meetup-de-JavaScript-en-Caracas/'
+        name: 'JavaScript en Caracas, FaceBook: "JavaScript Venezuela"'
+        description: |-
+          <p>Somos un sitio de encuentro para todas las personas relacionadas con javascript desde los que quieren estar informados en este nuevo paradigma de desarrollo, hasta por los clientes que estan buscando soluciones javascript para sus necesidades informáticas. Ven a compartir, ven a conocer, ver a instruir, ven a aprender, ven a construir una comunidad.</p>
+          <p>Estamos tambien en FaceBook, con el grupo "JavaScript Venezuela", agregate, aporta y construye. Para una mejor Venezuela.</p>
+        lon: -66.93000030517578
+        lat: 10.539999961853027
+      - country: DO
+        city: Santo Domingo
+        link: 'http://www.meetup.com/Azure-Open-Source-Santo-Domingo/'
+        name: 'Azure {Open Source}; Santo Domingo'
+        description: '<p>Este grupo es para todos los interesados en tratar y aprender temas relacionados a Open Source en Azure, esta última es la Nube Abierta de Microsoft… Lo cual nos deja mucho de qué hablar :) !! Conoce más sobre Open Source en Microsoft http://microsoft.com/openness <a href="http://openness.microsoft.com/es-latam/blog/" class="linkified">http://openness.microsoft.com/es-latam/blog/</a></p>'
+        lon: -69.91000366210938
+        lat: 18.479999542236328
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/Javascript-SP/'
+        name: Meetup Javascript São Paulo
+        description: '<p>Este é um grupo para os interessados ​​em javascript. Todos os níveis são bem-vindos. Eu comecamos este grupo para conhecer outros entusiastas de javascript.</p>'
+        lon: -46.630001068115234
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/2/2/2/600_445613794.jpeg'
+        lat: -23.530000686645508
+      - country: CO
+        city: Bogotá
+        link: 'http://www.meetup.com/Beer-JS-Bogota/'
+        name: BeerJS Bogotá
+        description: |-
+          <p>BeerJS es un encuentro de desarrolladores apasionados por crear código JavaScript y que disfrutan de una buena cerveza. Se realiza mundialmente por ciudades, y en Colombia no tenemos porque quedarnos atrás!</p>
+          <p>El repositorio y el resto de la organización está en&nbsp;<a href="https://github.com/beerjs/bogota">https://github.com/beerjs/bogota</a>, así que es mejor que estén pendientes de ese medio, al igual que por <a href="https://beerjsbog.herokuapp.com/">Slack</a>&nbsp;y por&nbsp;<a href="https://gitter.im/beerjs/bogota">Gitter</a>, gracias y salud!</p>
+          <p> <br></p>
+        lon: -74.08999633789062
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/f/d/f/600_446108159.jpeg'
+        lat: 4.630000114440918
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/React-js-en-Buenos-Aires/'
+        name: React.js en Buenos Aires
+        description: '<p>Un meetup para discutir, investigar, implementar los últimos avances sobre React.js/Flux, y cualquier derivado: Redux, react-bootstrap, material-ui, routing, isomorphic SPA, ...</p>'
+        lon: -58.369998931884766
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/6/a/b/600_447849899.jpeg'
+        lat: -34.61000061035156
+      - country: MX
+        city: Puebla
+        link: 'http://www.meetup.com/DevNightsMX/'
+        name: 'DevNights - Code Pizza & Beer'
+        description: '<p>Este es un grupo para todos los interesados en temas como OpenSource, Node.js, Javascript, Startups, Frameworks y demás… Sé que Puebla puede ser un hub muy interesante para el código en México ya que estamos cerca de todos lados. Ven, da una plática o escucha una, conoce gente haz networking habla sobre tu siguiente emprendimiento y encuentra a tu co-fundador. Pero principalmente: pizza &amp; beer :)</p>'
+        lon: -98.22000122070312
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/b/7/9/600_446711129.jpeg'
+        lat: 19.049999237060547
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/spember/'
+        name: Ember.sp
+        description: 'Vamos conhecer e nos aprofundar no framework do Hamster, e descobrir como podemos usar seus poderes para aplicações web ambiciosas, estáveis e que permitam visualizar o futuro dos padrões da web! Venha conversar, conhecer, chorar e desabafar sobre os percalços dessa jornada de aprendizado, e vamos sempre compartilhar nossas experiências para criar melhores projetos!'
+        lon: -46.630001068115234
+        lat: -23.530000686645508
+      - country: CO
+        city: Armenia
+        link: 'http://www.meetup.com/ArmeniaJS/'
+        name: ArmeniaJS
+        description: 'Entérate del desarrollo Web local, conoce otros desarrolladores para compartir el conocimiento, aprender tecnologias modernas, revisar el estado de nuestra comunidad o tener otra vision sobre el desarrollo local.'
+        lon: -75.69000244140625
+        lat: 4.53000020980835
+      - country: CO
+        city: Cúcuta
+        link: 'http://www.meetup.com/Cucuta-NodeJS-Meetup/'
+        name: Cúcuta NodeJS Meetup
+        description: 'Cansado de programar en viejos lenguajes o de no encontrar proyectos que no sean un gran reto? Unete a a este grupo creado para todos los curiosos de la programación que deseen explorar esta gran tecnología, crear proyectos openSource, mejorar habilidades en javascript y encontrar nuevas oportunidades laborales. Personas de todos los niveles son bienvenidas y entre todos nos ayudaremos a crecer.'
+        lon: -72.51000213623047
+        lat: 7.909999847412109
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/muleysba/'
+        name: MuleSoft Developers Argentina
+        description: '<p>Es un grupo para profesionales del área de desarrollo que estén interesados en tecnologías utilizadas en MuleSoft, como Mule ESB, Anypoint Studio, enterprise integration, web services, IoT, APIs REST, microservices y otros.</p>'
+        lon: -58.369998931884766
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/9/d/e/600_448403006.jpeg'
+        lat: -34.61000061035156
+      - country: BR
+        city: Belo Horizonte
+        link: 'http://www.meetup.com/Javascript-Dojo-Belo-Horizonte/'
+        name: Javascript Dojo - Belo Horizonte
+        description: '<p>Se você quer aprender/aprofundar mais sobre closures, es6, prototype inheritance, promise, js frameworks de forma prática inscreva-se.<br>O objetivo é promover dojos é aprender coletivamente sobre javascript metendo a mão na massa.</p>'
+        lon: -43.939998626708984
+        lat: -19.920000076293945
+      - country: BR
+        city: São Paulo
+        link: 'http://www.meetup.com/Free-Code-Camp-SP/'
+        name: Free Code Camp SP
+        description: 'Esse grupo tem como objetivo reunir estudantes do Free Code Camp residentes na cidade de São Paulo. Se você já está fazendo, em qualquer estágio do curso, ou tem interesse em aprender mais sobre desenvolvimento web full stack focado em Javascript, esse é o lugar! Entre os eventos desse Meetup teremos coffee &amp; codes, workshops, webcasts e qualquer outro tipo de encontro que possibilite a troca de experiências e um aprendizado com mais qualidade! Sintam-se livres para propor eventos! Por último, peço para que, por enquanto, só entrem no grupo se forem de São Paulo e realmente pretenderem ir nos encontros, pois estou fazendo uma conta free.'
+        lon: -46.630001068115234
+        lat: -23.530000686645508
+      - country: AR
+        city: Buenos Aires
+        link: 'http://www.meetup.com/Alquimistas-de-la-programacion/'
+        name: Alquimistas de la programación
+        description: 'Este es un grupo donde todos los amantes de: PHP, HTML5, IONIC, Phonegap y MySql se juntan de forma ONLINE y presencia charlas creadas por un grupo de desarrolladores que intenta crecer día a día profesionalmente.'
+        lon: -58.369998931884766
+        lat: -34.61000061035156
+    nodeschools:
+      - name: Belo Horizonte NodeSchool
+        location: 'Belo Horizonte, BR'
+        organizers:
+          - paulohp
+          - obetomuniz
+          - victorferraz
+          - erickbelfy
+        website: 'http://nodeschool.io/belo-horizonte'
+        repo: 'http://github.com/nodeschool/belo-horizonte'
+        lat: -19.9166813
+        lon: -43.9344931
+      - name: NodeSchool Bogotá
+        location: 'Bogotá, CO'
+        organizers:
+          - davsket
+          - agar3s
+          - kuryaki
+          - zaccaro
+          - buritica
+        repo: 'http://github.com/nodeschool/bogota'
+        lat: 4.710988599999999
+        lon: -74.072092
+      - name: Buenos Aires NodeSchool
+        location: 'Buenos Aires, AR'
+        organizers:
+          - a0viedo
+        website: 'http://nodeschool.io/buenosaires'
+        twitter: nodeschoolba
+        repo: 'http://github.com/nodeschool/buenosaires'
+        lat: -34.6036844
+        lon: -58.3815591
+      - name: Campinas NodeSchool
+        location: 'Campinas, SP, BR'
+        organizers:
+          - fmoliveira
+          - MiattoRocha
+          - edersonnascimento
+        website: 'http://nodeschool.io/campinas'
+        twitter: nodeschoolcps
+        repo: 'http://github.com/nodeschool/campinas'
+        lat: -22.9099384
+        lon: -47.0626332
+      - name: NodeSchool Cochabamba
+        location: 'Cochabamba, BO, BO'
+        organizers:
+          - chitopolo
+          - aquilardo
+        website: 'http://www.boliviajs.com'
+        twitter: 'https://www.twitter.com/BoliviaJS'
+        repo: 'http://github.com/nodeschool/Cochabamba'
+        lat: -17.4139766
+        lon: -66.1653224
+      - name: Córdoba NodeSchool
+        location: 'Córdoba, AR'
+        organizers:
+          - avilaton
+        website: 'http://nodeschool.io/cordoba'
+        repo: 'http://github.com/nodeschool/cordoba'
+        lat: -31.42008329999999
+        lon: -64.1887761
+      - name: 'NodeSchool Costa Rica '
+        location: 'San José, CRI'
+        organizers:
+          - gaboesquivel
+          - yeco
+          - laubits
+          - brolag
+          - stevenperez
+          - kevinblanco
+          - laurensortiz
+          - jarias
+          - rubenabix
+          - cayasso
+          - avenidanet
+        website: 'http://nodeschool.io/costarica/'
+        twitter: costaricajs
+        repo: 'http://github.com/nodeschool/costarica'
+        lat: 9.6257333
+        lon: -84.010995
+      - name: Florianópolis NodeSchool
+        location: 'Florianópolis, SC, BR'
+        organizers:
+          - conrado
+        website: 'http://nodeschool.io/florianopolis'
+        twitter: nodeschoolFLN
+        repo: 'http://github.com/nodeschool/florianopolis'
+        lat: -27.5953778
+        lon: -48.5480499
+      - name: Havana NodeSchool
+        location: 'Havana, CU'
+        organizers:
+          - phinfonet
+          - elMor3no
+          - olemis
+          - robertkowalski
+          - aurium
+        website: 'http://nodeschool.io/havana'
+        repo: 'http://github.com/nodeschool/havana'
+        lat: 23.1135925
+        lon: -82.3665956
+      - name: NodeSchool Hermosillo
+        location: 'Hermosillo, Son, MX'
+        organizers:
+          - dayrachiu
+          - jrsalgado
+          - keogh
+          - abrahamhinojo
+        website: 'http://nodeschool.io/hermosillo'
+        repo: 'http://github.com/nodeschool/hermosillo'
+        lat: 29.0729673
+        lon: -110.9559192
+      - name: NodeSchool Ibagué
+        location: 'Ibagué, CO'
+        organizers:
+          - gioyik
+          - yeisontapia
+          - pandres95
+          - zheref
+        repo: 'http://github.com/nodeschool/ibague'
+        lat: 4.444675999999999
+        lon: -75.24243799999999
+      - name: Manizales NodeSchool
+        location: 'Manizales, CO'
+        organizers:
+          - gmauricio
+        repo: 'http://github.com/nodeschool/manizales'
+        lat: 5.070275
+        lon: -75.5138166
+      - name: NodeSchool Medellín
+        location: 'Medellín, CO'
+        organizers:
+          - julianduque
+          - edsadr
+          - academo
+        repo: 'http://github.com/nodeschool/medellin'
+        lat: 6.253040800000001
+        lon: -75.5645737
+      - name: Mexico City NodeSchool
+        location: 'Mexico City, MX'
+        organizers:
+          - jeduan
+          - rogr
+          - siedrix
+        website: 'http://nodeschool.io/mexicocity'
+        repo: 'http://github.com/nodeschool/mexicocity'
+        lat: 19.4326077
+        lon: -99.133208
+      - name: Montevideo NodeSchool
+        location: 'Montevideo, UY'
+        organizers:
+          - pdjota
+          - pricco
+          - mprunell
+        repo: 'http://github.com/nodeschool/montevideo'
+        lat: -34.9011127
+        lon: -56.16453139999999
+      - name: NodeSchool Pereira
+        location: 'Pereira, CO'
+        organizers:
+          - cronopio
+          - pin3da
+          - jhonber
+        repo: 'http://github.com/nodeschool/pereira'
+        website: 'http://nodeschool.io/pereira'
+        twitter: PereiraJS_
+        lat: 4.8087174
+        lon: -75.690601
+      - name: Puerto Rico NodeSchool
+        location: 'Puerto Rico, PR'
+        organizers:
+          - gcollazo
+          - jpadilla
+          - elving
+          - jomajoma
+          - froi
+        website: 'http://nodeschool.io/puertorico/'
+        repo: 'http://github.com/nodeschool/puertorico'
+        lat: 18.220833
+        lon: -66.590149
+      - name: Rio de Janeiro NodeSchool
+        location: 'Rio de Janeiro, RJ, BR'
+        organizers:
+          - milesibastos
+        website: 'http://nodeschool.io/rio'
+        gitter: 'https://gitter.im/nodeschool/rio'
+        repo: 'http://github.com/nodeschool/rio'
+        lat: -22.9068467
+        lon: -43.1728965
+      - name: San Ignacio NodeSchool
+        location: 'San Ignacio, PY'
+        organizers:
+          - matiasinsaurralde
+          - luchobenitez
+          - carloscarvallo
+        website: 'http://nodeschool.io/sanignacio'
+        repo: 'http://github.com/nodeschool/sanignacio'
+        lat: -26.8433512
+        lon: -57.10131879999999
+      - name: NodeSchool Santa Marta
+        location: 'Santa Marta, CO'
+        organizers:
+          - pedroromn
+          - gengue
+        website: 'http://nodeschool.io/santamarta/'
+        repo: 'http://github.com/nodeschool/santamarta'
+        lat: 11.2403547
+        lon: -74.2110227
+      - name: Santiago NodeSchool
+        location: 'Santiago, CL'
+        organizers:
+          - forres
+          - xabadu
+        website: 'http://www.noders.cl'
+        twitter: nodeschoolstgo
+        repo: 'http://github.com/nodeschool/Santiago'
+        lat: -33.4488897
+        lon: -70.6692655
+      - name: USAC NodeSchool
+        location: 'USAC, Guatemala City, GT'
+        organizers:
+          - edwinallenz
+          - bladimir47
+          - ottogiron
+          - osukaa
+          - gepser
+          - jossemarGT
+          - viktorcoradov
+          - braestuart
+          - cruzperez
+          - hhgn32
+          - bvalenzuela
+          - louicruz
+          - Lucosenza2015
+        repo: 'https://github.com/nodeschool/usac.gt'
+        lat: 14.5881064
+        lon: -90.5477204
+  - region: Північна Америка
+    conferences:
+      - name: Node.js Interactive
+        dates:
+          - 2015-12-08T00:00:00.000Z
+          - 2015-12-09T00:00:00.000Z
+        link: 'http://events.linuxfoundation.org/events/node-interactive'
+        image: 'http://events.linuxfoundation.org/sites/events/files/nodeint15_400x400.png'
+        desc: Node.js Foundation lead conference.
+        location: 'Hilton Portland & Executive Tower, Portland, OR'
+        lat: 45.5167983
+        lon: -122.6815443
+      - name: NodeConf Adventure
+        link: 'http://nodeconf.com'
+        desc: Unconference for Node.js developers.
+        location: 'Walker Creek Ranch, Marin County, CA, USA'
+        lat: 38.1665953
+        lon: -122.8083025
+      - name: Empire Node
+        link: 'http://2015.empirenode.org/'
+        desc: Yearly Node.js conference in New York City.
+        lat: 40.704031
+        lon: -74.013747
+        location: 'National Museum of the American Indian, NYC, NY'
+      - name: EmpireJS
+        desc: Yearly JS Conference in New York City.
+        lat: 40.704031
+        lon: -74.013747
+        location: 'National Museum of the American Indian, NYC, NY'
+      - name: Node Community Convention
+        dates:
+          - 2016-01-26T00:00:00.000Z
+          - 2016-01-27T00:00:00.000Z
+          - 2016-01-28T00:00:00.000Z
+        link: 'http://nodecommunityconvention.com/?gclid=CK6y2d_-rMkCFQ8yaQod_mkBMQ'
+        desc: Real Time Innovation for the Node.js Community
+        lat: 37.788678
+        lon: -122.4126467
+        location: "Marine's Memorial Theatre, 609 Sutter Street, San Francisco, CA 94102"
+    meetups:
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Austin-MEAN-Stack-Development/'
+        name: Austin MEAN Stack Dev Meetup
+        lon: -97.740280
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/a/4/3/highres_449419011.jpeg'
+        lat: 30.275401
+      - country: US
+        city: Fort Lauderdale
+        link: 'http://www.meetup.com/web-development-frameworks/'
+        name: Web Frameworks Meetup
+        lon: -80.18000030517578
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/6/f/c/600_69980.jpeg'
+        lat: 26.18000030517578
+      - country: US
+        city: Fort Lauderdale
+        link: 'http://www.meetup.com/webdesign-27/'
+        name: The Broward County Web Design Meetup Group
+        description: '<p>This Meetup Group focuses on web related design issues. We privilege conceptual vs. technical. (i.e. how to do good design vs. what application to use) Tech sessions at the end, if requested. Business issues welcome too!</p>'
+        lon: -80.18000030517578
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/4/8/a/600_53781642.jpeg'
+        lat: 26.18000030517578
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Lakefront-Web-Developers/'
+        name: Lakefront Web Developers
+        description: '<p>Meet other web developers and continue your education in HTML, CSS, JavaScript, PHP, and other technologies. Industry trends are always changing and we cover what you need to stay up to date. Each meetup has an hour-long technical presentation with food, drinks, and good people. So come join us sometime near the beautiful Chicago lakefront.</p>'
+        lon: -87.62999725341797
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/8/0/c/600_448158444.jpeg'
+        lat: 41.88999938964844
+      - country: US
+        city: Lansing
+        link: 'http://www.meetup.com/lansingweb/'
+        name: Lansing Web Meetup Group
+        description: |-
+          <p>Come hang out with other local web developers and designers!</p>
+          <p>Lansing Web Meetups are agenda-free events where you can share your latest project, talk about tools you’re using, network, trade career advice, or just chat about the web.</p>
+          <p>We also host occasional talks, so if there’s a topic you’d like to learn more about or give a talk on, please let us know!</p>
+        lon: -84.55000305175781
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/e/e/0/600_438504288.jpeg'
+        lat: 42.72999954223633
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/jsmeetup/'
+        name: The SF JavaScript Meetup
+        description: |-
+          <p>Hang out and discuss JavaScript tips, tricks, hacks, and frameworks with some of the best scripters around. Show off cool stuff you've done and learn about what else is going on in the JS community. No pressure, no mandatory presentations. Come, hang out, and hear great people talk about cutting edge scripting.</p>
+          <p><em>The SF JavaScript Meetup is committed to maintaining an inclusive, harassment-free atmosphere. Attendees, speakers and sponsors must all abide by our <a href="http://confcodeofconduct.com/">Code of Conduct</a>. Please do not spam the group with job postings/contact info or bring collateral to the events.</em></p>
+        lon: -122.41000366210938
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/6/8/4/600_59778052.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/Hackers-and-Founders/'
+        name: Hackers and Founders
+        description: |-
+          <p><a href="http://hf.cx/">You should really go over there and learn more about us.</a></p>
+          <p><a href="http://hf.cx/coop">We have a founder's co-operative. &nbsp;Learn more here.</a></p>
+          <p>Hackers/Founders is the largest community of early tech founders in Silicon Valley ( that includes SF ).</p>
+          <p><span>Like reviewing startups? <a href="https://docs.google.com/a/hf.cx/forms/d/1ImzZHqHI1w8azBhTBeXBUn8lLzzdxTx0eq2FAnSdO-8/viewform">Sign up here!</a></span></p>
+          <p><span>We host networking events and meetups in </span>Silicon Valley<span>, San Francisco, Berkeley and San Jose.</span></p>
+          <p><a href="http://hf.cx">Subscribe to Hackers/Founders Newsletter</a></p>
+          <p>Looking to invest in startups? <a href="http://hf.cx/invest">Subscribe to our Investor Newsletter</a></p>
+        lon: -122.08000183105469
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/6/1/a/600_439817946.jpeg'
+        lat: 37.40999984741211
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/NY-JavaScript/'
+        name: NY JavaScript
+        description: |-
+          <p>Welcome to the NY JavaScript meetup group. We host regular workshops and tech talks on a variety of different JavaScript topics.</p>
+          <p>We look forward to hearing from you, and to seeing you at an upcoming event.</p>
+          <p>&nbsp;<span>Get in touch at jovena@nyjavascript.com if you'd like to be involved.</span></p>
+          <p>&nbsp;</p>
+        lon: -74
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/c/c/d/600_437171469.jpeg'
+        lat: 40.720001220703125
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/austincoders_hackers/'
+        name: 'Austin Coders & Hackers by The Tech^map'
+        description: "<p><span><span><br><strong>Welcome to Austin Coders &amp; Hackers Meetup group by The Tech^map!</strong></span></span></p> \n<p>If you are interested to attend hackethon, tech, or coding events or anything related to technology and partying you want to be part of this group.&nbsp;<span>Everyone is welcome to our group! Software developers, UX designers, hardware architects and students looking for a more exciting and challenging opportunity in Austin. Come on in, join us!</span></p> \n<p>Our meetups are always a great opportunity to meet engineering and creative talent from Austin, TX, to find out what is happening in the techie universe in Silicon Hills join us.</p> \n<p><span>To list your company, post jobs, connect with others or find events going on signup to www.thetechmap.com.&nbsp;It is FREE!</span></p> \n<p>Cheers,<br>Johan Borge<br>CEO &amp; Founder</p>"
+        lon: -97.76000213623047
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/8/1/5/8/600_396573112.jpeg'
+        lat: 30.290000915527344
+      - country: US
+        city: Baltimore
+        link: 'http://www.meetup.com/bmorejs/'
+        name: BmoreJS – The Baltimore JavaScript Users Group
+        description: |-
+          <p>Check out Charm City JS for meetups&nbsp;http://www.meetup.com/charmcityjs/</p>
+          <p><br></p>
+          <p>Meet other local JavaScripters to share knowledge, help each other out, review new technology and dream up new ways to use and make JavaScript the most loved language around. We encourage knowledge sharing and a comfortable environment to be yourself.</p>
+          <p>Our meetings cover general Web Development topics focused on the programming side of things. We often cover popular JavaScript libraries and frameworks.</p>
+        lon: -76.62000274658203
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/8/d/4/600_96070452.jpeg'
+        lat: 39.290000915527344
+      - country: US
+        city: Tampa
+        link: 'http://www.meetup.com/florida-web-developers/'
+        name: Central Florida Web Developers
+        description: '<p>The Central Florida Web Developers user group’s mission is to&nbsp;provide environment for accelerated growth and development of our members by organizing monthly group meetings rich on discussions and exercises that advance technical skills, use best practices, teach methodologies and attract opportunities. <br> <br> <br></p>'
+        lon: -82.51000213623047
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/5/3/2/600_446301810.jpeg'
+        lat: 27.940000534057617
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/sfnodejs/'
+        name: SF Node.js
+        description: "<p><strong>Expand your Node.js knowledge!</strong></p>\n<p>If you are in San Francisco and interested in diving deeper into Node.js this is the group for you. Please provide your GitHub username when signing up. Forks or public repos containing Node.js code are required for membership.</p>\n<p>\_</p>\n<p>NO RECRUITERS ALLOWED!</p>"
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/7/c/c/600_107207052.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: Omaha
+        link: 'http://www.meetup.com/nebraskajs/'
+        name: NebraskaJS
+        description: |-
+          <p><span style="color : #000000">Formerly known as <em>Omaha jQuery Meetup</em> (2009) and <em>Omaha Front-End Web &amp; jQuery</em> (2011).</span></p>
+          <p><span style="color : #000000"><strong>NebraskaJS</strong></span> <span style="color : #000000 ; font-size : 13px">was founded in fall of 2009 by local front-end heros Jonathan Sharp, Andrew Wirick, and Eli Perelman. It was originally focused solely on jQuery, but later expanded to include other front end technologies.</span></p>
+          <p><span style="color : #000000">In 2012, group leadership duties were passed on to Zach Leatherman and the group decided to move away from a jQuery focus toward a more generic JavaScript focus. Nick Nisi</span> joined mid-2013 primarily to get more JavaScript developers to use Vim. In 2014, Blaine Kasten joined to bring NebraskaJS to Lincoln.</p>
+          <p><span style="color : #000000">Our goals:</span></p>
+          <ul>
+          <li><span style="color : #000000"><span>Encourage open source/community contributions by our members. A portion of every meeting is dedicated to small lightning talks on GitHub issues that members in the community have contributed to/closed out (no issue too small!).</span><br>
+
+          </span></li>
+          <li><span style="color : #000000"><span><span>Sharing workflow and useful tools. Small coding exercises dedicated to showing how others work can expose useful tips and tricks to separate the wheat from the chaff in development tooling.</span><br>
+
+          </span></span></li>
+          <li><span style="color : #000000"><span><span><span>All presentations are recorded and published online, in the hopes that it will improve the quality of presentations and offer nice exposure and incentive to present.</span><br>
+
+          </span></span></span></li>
+          </ul>
+          <p><span style="color : #000000 ; font-size : 13px">We seek to bring together the developer and designer community in and around Omaha and cover interesting topics relevant to front end web development. Come join us for an informative event and a great community!</span></p>
+        lon: -95.93000030517578
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/d/2/8/600_150379752.jpeg'
+        lat: 41.2599983215332
+      - country: US
+        city: Durham
+        link: 'http://www.meetup.com/Triangle-JavaScript/'
+        name: Triangle JavaScript
+        description: 'Welcome to Triangle JavaScript, a group for people in the Raleigh-Durham area interested in discussing all things JavaScript.'
+        lon: -78.91999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/d/c/9/600_437808585.jpeg'
+        lat: 35.91999816894531
+      - country: US
+        city: Las Vegas
+        link: 'http://www.meetup.com/VegasJS/'
+        name: VegasJS
+        description: '<p>To discuss, learn, teach, and play JavaScript!</p>'
+        lon: -115.12000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/7/5/2/600_269074642.jpeg'
+        lat: 36.16999816894531
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/torontojs/'
+        name: Toronto JavaScript
+        description: '<p>Toronto JavaScript is a meet up for those interested in all things JavaScript. Client side, server side, we love it all!</p>'
+        lon: -79.4000015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/8/c/4/600_430214532.jpeg'
+        lat: 43.65999984741211
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/nodejs/'
+        name: nodejs
+        description: "<p>Thanks to the brilliant work of Ryan Dahl, we have node.js, a beautiful and elegant server-side framework built on top of Google's V8 Javascript engine. This opens up a whole new world of possibility for developing web apps, APIs, and lightweight HTTP servers.</p>\n<p>\_</p>\n<p>We meet on Wednesday at 6:30pm. \_Each week we'll have a group discussion on a particular aspect of NodeJS, or a whackiest. \_Occasionally, we'll may have a more formal presentation.</p>\n<p>\_</p>\n<p>If you'd like to present, please send a note with your topic and when you'd like to give it to the leadership staff.</p>\n<p>\_</p>\n<p>If you have a suggestion for a topic, feel free to submit it.</p>\n<p>\_</p>\n<p>We are always looking for spaces to use for the meetups. \_If you'd like to offer a space for us to use, please reach out to the leadership team.</p>"
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/d/d/600_39301501.jpeg'
+        lat: 40.7599983215332
+      - country: US
+        city: Dallas
+        link: 'http://www.meetup.com/DallasNode/'
+        name: Dallas.node
+        description: |-
+          <p>Ever wish there was a world where people talked about nothing but node.js all day everyday even while they slept?</p>
+          <p>Well we did too! So we started Dallas.node to further this Utopian vision to it's breaking limit! Join us if you're a fellow async junkie.</p>
+        lon: -96.79000091552734
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/f/f/4/600_19377332.jpeg'
+        lat: 32.93000030517578
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Node-js-Serverside-Javascripters-Club-SF/'
+        name: Node.js Club SF
+        description: |-
+          <p>This meetup is focused on spreading knowledge and best practices for the use of Node.js. Node is exploding with a massive and dedicated developer community, and is moving into enterprise stacks. There is an incredible talent pool out there who can bring their experience back to the community, and our goal is to get them into the group to speak. Topics of discussion include OSS projects, architectures, testing, devops, <span>code management,</span> deployment strategies, the future of Node and emerging trends.</p>
+          <p>And of course we want to continue making the Node.js community a great atmosphere to be in. If you use Node.js or even have a beginner's interest, come join us and hear about the latest and greatest from Node.</p>
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/1/e/3/600_434453731.jpeg'
+        lat: 37.779998779296875
+      - country: US
+        city: Oakland
+        link: 'http://www.meetup.com/eastbayjavascript/'
+        name: JavaScript in the SF East Bay
+        description: |-
+          <p>A group for people in the SF East Bay who love/use/want to learn JavaScript, including libraries like jQuery, Angular, Ember, React and many more. We'll also cover plenty of Node.js related topics!</p>
+          <p><span>There is something for everyone to learn, from novices to experts alike.</span></p>
+        lon: -122.29000091552734
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/e/c/a/600_433768362.jpeg'
+        lat: 37.810001373291016
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Chicago-Nodejs/'
+        name: Chicago  Node.js
+        description: '<p>A group to discuss Node.js, its frameworks, and best practices. Email mike.hostetler@gmail.com with any questions.</p>'
+        lon: -87.63999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/9/c/1/600_47379361.jpeg'
+        lat: 41.880001068115234
+      - country: US
+        city: Boulder
+        link: 'http://www.meetup.com/Boulder-JS/'
+        name: Boulder JS
+        description: |-
+          <p>While there are some great groups in town that discuss a bunch of cool languages, there wasn't one that focused specifically on the language that you and I both love, JavaScript.</p>
+          <p>Until now.</p>
+          <p>These are fascinating times for JavaScript development, and this group will attempt to explore topics including, but by no means limited to:</p>
+          <p>* the power of raw JavaScript; <br>* Ajax; <br>* libraries like jQuery and Prototype; <br>* techniques for building your own library; <br>* server-side JavaScript with Node.js; <br>* optimization techniques; <br>* test-driven development; <br>* and so much more!</p>
+          <p>We're a friendly group and we welcome developers of all skill levels, beginner to expert. We want to foster an environment where it's okay to ask questions and it's okay not to know about certain aspects of the language. We're willing to share what we know, and are open to learning from others.</p>
+        lon: -105.20999908447266
+        lat: 40.04999923706055
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/noders/'
+        name: 'Node.JS User Group - Austin, TX'
+        description: '<p>Node.js is an event-driven I/O framework for the V8 JavaScript engine. It makes building scalable and elegant network applications easy. Praised for its brilliant design and simplicity it is quickly being adopted and extended by many developers, companies, and entusiasts around the world. Visit http://www.nodejs.org/ and http://npmjs.org/ to get started today!</p>'
+        lon: -97.73999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/5/9/6/600_22341910.jpeg'
+        lat: 30.290000915527344
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/Node-JS-Boston/'
+        name: Node.JS Boston
+        description: "<p>A group dedicated to Node.JS, the server side framework for Google's V8 JavaScript engine.</p>"
+        lon: -71.04000091552734
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/c/0/5/600_448119941.jpeg'
+        lat: 42.349998474121094
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/SoCal-Node-JS/'
+        name: SoCal Node.js
+        description: "<p>Los Angeles, Orange Country, San Diego meetup focused on Server Side Javascript, and in particular, Node.js. Goals for the group are to spread ideas about Server Side Javascript, Node.js in particular, socialize projects, and discuss the technology and best practices. We'd like to keep the group informal but focused on technology and interesting projects. I think the ideal group would be made up of developers on OSS projects, site/app builders, systems integrators, architects, designers, freelancers/consultants, and even a few engineering managers who manage projects using node.js.</p>"
+        lon: -118.30999755859375
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/8/c/7/600_45618631.jpeg'
+        lat: 34.060001373291016
+      - country: US
+        city: Fort Lauderdale
+        link: 'http://www.meetup.com/NodeJS-Enthusiasts-SE-Florida/'
+        name: NodeJS Enthusiasts SE Florida
+        description: "<p>NodeJS is emerging as a powerful platform for building Internet applications. As an emergent technology, NodeJS does not yet have the ensemble of tools and infrastructural parts that mature language systems have. The NodeJS community is relatively small, and we all need to learn from each other's efforts to work with it. The NodeJS Enthusiasts SE Florida group exists to foster interaction among NodeJS developers. The goals for this group are to build our local NodeJS developer community, encourage adoption of NodeJS by businesses in the area, and help people better understand and use NodeJS in applications, both for personal and business uses.</p>"
+        lon: -80.12999725341797
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/b/b/600_41883771.jpeg'
+        lat: 26.1200008392334
+      - country: US
+        city: Saint Louis
+        link: 'http://www.meetup.com/STL-JS-meetup/'
+        name: STLJS
+        description: "<p>Hang out and discuss JavaScript tips, tricks, hacks, and frameworks with fellow scripters in the Saint Louis area. Show off cool stuff you've done and discuss developments in the greater JS community:\_<a href=\"http://stljs.org/\">stljs.org</a> | <a href=\"http://nodemeatspace.com\">node.js meatspace</a> | <a href=\"http://www.youtube.com/channel/UCRSFZt0URpegRPg-xoe0o9Q\">youtube</a> |\_<a href=\"https://github.com/STLJS\">github</a> | <a href=\"https://twitter.com/STLJS\">twitter</a> | <a href=\"http://facebook.com/STLJS\">facebook</a> | <a href=\"http://www.linkedin.com/groups/Saint-Louis-JavaScript-Meetup-4353680\">linkedin</a> | <a href=\"https://plus.google.com/+StljsOrg/posts\">google+</a> | <a href=\"https://groups.google.com/forum/#!forum/stljs\">google groups</a> | <a href=\"http://webchat.freenode.net?channels=%23stljs&amp;uio=d4\">irc://irc.freenode.net/stljs</a></p>\n<iframe src=\"http://www.youtube.com/embed/videoseries?list=PLo001zCveVlPiN27lGGBpymcqyqLc9_0N\" width=\"470\" height=\"264\" style=\"margin : 5px ; max-width : 700px ; max-height : 700px\"></iframe>"
+        lon: -90.20999908447266
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/f/8/e/600_105684462.jpeg'
+        lat: 38.630001068115234
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/BayNode/'
+        name: BayNode - The Bay Area Node.js Meetup
+        description: "<p>BayNode was started because we were sick of waiting for someone else to start start a node.js group! Come out if you want to sharpen your Javascript skills and find out why node.js rocks! The great thing about node.js is it's so new none of us are experts... yet... So all are welcome!</p>"
+        lon: -122.08000183105469
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/5/2/d/600_33605421.jpeg'
+        lat: 37.380001068115234
+      - country: US
+        city: Cleveland
+        link: 'http://www.meetup.com/NodejsCleveland/'
+        name: Cleveland Node.js User Group
+        description: '<p>Node.js is hot and heavy. Come meet with other Node.js enthusiasts and see how server-side JavaScript is not only new but a very powerful way to develop. We will also aim to cover topics regarding jQuery, JavaScript performance and other popular front-end development. We hope to share and develop with all who are welcome to join us here in Northeast Ohio.</p>'
+        lon: -81.68000030517578
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/c/b/7/600_45547351.jpeg'
+        lat: 41.5099983215332
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/sandiegojs/'
+        name: sandiego.js (Javascript User Group)
+        description: |-
+          <p>The premier San Diego user group based around the web platform. Join us to hear about the state of the art in web development around JavaScript, hack on open source projects, or learn from some of the best in the community.</p>
+          <p>Visit our site at <a href="http://sandiegojs.org/">sandiegojs.org</a> for information on upcoming meetups or to write an article. &nbsp;<a href="https://groups.google.com/d/forum/sandiegojs">Join our mailing list</a> for javascript related discussions. Follow <a href="http://twitter.com/sandiegojs">@sandiegojs on twitter</a>, and post in the <a href="http://www.meetup.com/sandiegojs/messages/boards/">meetup message board</a>!</p>
+        lon: -117.19999694824219
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/c/6/a/600_81100042.jpeg'
+        lat: 32.88999938964844
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/talesofjavascript/'
+        name: T.O.J. - Tales Of JavaScript
+        description: "<p>Expanding content to handle a wealth of overflow from the <a href=\"http://html5devconf.com/\">HTML5DevConf</a>. Meetup content now covers general JavaScript, HTML5, CSS3, WebGL, node.js, and Apps and Games using those technologies. In addition we look forward to a great year for WebGL, HTML5, and JavaScript Games from the traditional Games.js content which we will continue to bring.</p>\n<p>Meetings will be held in both SF and Mountain View.</p>\n<p>\_</p>\n<p>\_</p>"
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/4/3/6/600_323917942.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/DeveloperAdvocates/'
+        name: SF Developer Advocates
+        description: |-
+          <p><span style="font-size : medium">This group is focused on helping Developer Advocates and Evangelists to share best practices, value-based insights on building communities around API's and cloud based products plus any humorous examples of nerd shepherding.</span></p>
+          <p><span style="font-size : medium">This group isn't for: Marketing or recruiters to spam with annoying messages.</span></p>
+          <p><span style="font-size : medium">This group is for: Those who work/live/play in the developer relations space and live in the Bay Area (we cannot accept members who live elsewhere more than 75% of the time).</span></p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/4/9/1/600_43689361.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: Downey
+        link: 'http://www.meetup.com/oclajs/'
+        name: OC/LA JavaScript -- Downey
+        description: "<p>Let's learn and share what we know about JavaScript, its frameworks and libraries.</p>"
+        lon: -118.12999725341797
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/2/9/0/600_441372944.jpeg'
+        lat: 33.939998626708984
+      - country: US
+        city: Herriman
+        link: 'http://www.meetup.com/Big-Data-Salt-Lake/'
+        name: Big Data Salt Lake
+        description: 'Present and discuss issues, use cases, related to Big Data. Cassandra, Hadoop, etc.'
+        lon: -111.97000122070312
+        lat: 40.56999969482422
+      - country: US
+        city: Madison
+        link: 'http://www.meetup.com/MadisonJS/'
+        name: MadJS
+        description: |-
+          <p>Madison professionals, enthusiasts, and hobbyists who share a passion for great JavaScript, and making JavaScript work for them and their users through terrific, engaging, and intuitive apps.</p>
+          <p>&nbsp;</p>
+          <p>Google Group:&nbsp;<a href="http://groups.google.com/group/madjs?hl=en">http://groups.google.com/group/madjs</a></p>
+        lon: -89.37999725341797
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/4/8/e/600_84245262.jpeg'
+        lat: 43.08000183105469
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/javascript-austin/'
+        name: The JavaScript Austin Meetup Group
+        description: '<p>This group is for anyone who wants to learn about JavaScript and related frameworks and tools. Hopefully we can discuss development with the latest and greatest JavaScript stuff, so bring your computer and get ready for some hands-on Meetups!</p>'
+        lon: -97.73999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/e/b/a/600_63272442.jpeg'
+        lat: 30.5
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/toronto-node-js/'
+        name: Toronto Node.js
+        description: "<p>If you're interested in developing apps in Node.js, keeping up to date on the latest Node frameworks and packages, then join us for our monthly gathering in Toronto. Each meetup will feature at least one presentation, and the opportunity to meet other Toronto Node enthusiasts.</p>"
+        lon: -79.41000366210938
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/5/b/0/600_387826512.jpeg'
+        lat: 43.66999816894531
+      - country: US
+        city: Huntington
+        link: 'http://www.meetup.com/Code-Strong-Island/'
+        name: Code Strong Island
+        description: |-
+          <p>Yes there are developers on Long Island. We're a group of Long Island developers who share an interest in code craftsmanship and new technology.</p>
+          <p>Professionally we work in Node.js, Ruby, Clojure, Hadoop (EMR), Mongodb, and a long list of related technologies. We organize, and contribute to, open source projects on github. We work hard and love to have fun in the process.</p>
+        lon: -73.41000366210938
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/8/a/c/600_63490412.jpeg'
+        lat: 40.869998931884766
+      - country: US
+        city: Minneapolis
+        link: 'http://www.meetup.com/JavaScriptMN/'
+        name: JavaScriptMN
+        description: '<p>This is a group of Minnesotans getting together to discuss programming JavaScript in the browser, on the server, on mobile devices, and everything in between. JavaScript veterans and newbies alike are welcomed and encouraged to attend! Meets the last Wednesday of the month at CoCo in Uptown Minneapolis.</p>'
+        lon: -93.26000213623047
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/7/0/2/600_172934082.jpeg'
+        lat: 44.97999954223633
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Stripe/'
+        name: The Stripe Meetup Group
+        description: '<p>Meet the Stripe team and members of the Stripe community.</p>'
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/9/8/c/600_421694732.jpeg'
+        lat: 37.75
+      - country: US
+        city: Palo Alto
+        link: 'http://www.meetup.com/SVHack/'
+        name: Silicon Valley Hackathons
+        description: 'Attend Hackathons in Silicon Valley!'
+        lon: -122.1500015258789
+        lat: 37.439998626708984
+      - country: US
+        city: Atlanta
+        link: 'http://www.meetup.com/Atlanta-Nodejs-Developers/'
+        name: Atlanta Nodejs Developers
+        description: "<p>The focus of this group will be to learn node js through a practical approach. We will have speakers followed by \"open spaces\" discussions.</p> \n<p>Members may be developers of all skill levels, designers looking to leverave javascript skill sets, architects looking for faster ways to build scalable systems, and engineering managers who want to understand how this technology can be utilized in their company.</p> \n<p>And of course anyone interested in changing the world.</p> \n<p>We will have a heavy focus on mobile computing devices and other smart devices like TVs with less focus on plain desktop pc.</p>"
+        lon: -84.37999725341797
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/e/7/2/600_91340082.jpeg'
+        lat: 33.77000045776367
+      - country: US
+        city: Detroit
+        link: 'http://www.meetup.com/DetNode/'
+        name: 'DetNode: The Detroit Node.js User Group'
+        description: "<p>Detroit Node aims to bring together developers interested in this up and coming technology. &nbsp;We're looking to have open hack sessions and are open to facilitating presentations in the future. &nbsp;Come be a part of the Technology Revolution in Detroit!</p>"
+        lon: -83.05000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/8/9/2/600_73315442.jpeg'
+        lat: 42.33000183105469
+      - country: CA
+        city: Calgary
+        link: 'http://www.meetup.com/yyc-js/'
+        name: YYCjs
+        description: "<p>YYC.js is comprised of a group of Calgary web developers and JavaScript aficionados with a passion for open source software. &nbsp;Our passion for software written in JavaScript stems from the ability to be extremely creative due to JavaScript's flexible nature. &nbsp;NodeJS allows us to bring this creativity to the server side while also affording the ability to create large-scale performant systems. &nbsp;Our group meets regularly to perform demos, provide tutorials, collaborate on open source software, and generally discuss the world of JS.</p>"
+        lon: -114.08999633789062
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/0/7/2/600_440869266.jpeg'
+        lat: 51.04999923706055
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Chicago-Heroku-Meetup-Group/'
+        name: Chicago Heroku User Group
+        description: '<p>Heroku User Groups (HUGS) are a casual gatherings of developers who are interested in learning about Heroku technologies. It provides developers an opportunity to explore Heroku (a polygot platform), as well learn how to run and scale any type of app, written in Java, Ruby, Node.js, Clojure, Python or Scala. This is a great place to meet Heroku experts and network with peer.</p>'
+        lon: -87.66999816894531
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/6/8/e/600_125219022.jpeg'
+        lat: 41.900001525878906
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/node-dc/'
+        name: node.dc
+        description: '<p><span>NodeDC brings</span> <a href="http://nodejs.org/">node.js</a> <span>developers together to share ideas and solutions in Washington, DC</span><span>.</span> For updates, join the group at <a href="http://www.meetup.com/node-dc">http://www.meetup.com/node-dc</a> and/or follow us at <a href="https://twitter.com/#!/nodedc">@NodeDC</a>.</p>'
+        lon: -77.04000091552734
+        lat: 38.91999816894531
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Joyent-Cloud-User-Group/'
+        name: Joyent
+        description: '<p>This is a group for developers and other technical types interested in Joyent technology. Any technical professional is welcome to join. We regularly announce meetups and events featuring interesting and innovative technologies like Node.js, OS virtualization, best practices on improving performance and new innovations like the Manta storage service with in situ compute.</p>'
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/2/5/4/600_202365652.jpeg'
+        lat: 37.79999923706055
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/Seattle-Node-js/'
+        name: Seattle Node.js
+        description: |-
+          <p>This is a group dedicated to learning, spreading the knowledge of, and improving Node.js - the evented, server side javascript platform harnessing the underlying power of Google's V8 JS engine.</p>
+          <p>You should join us if you want to learn about, share experiences with, or work to improve Node.js and its modules.</p>
+        lon: -122.33999633789062
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/8/5/0/600_331158512.jpeg'
+        lat: 47.630001068115234
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/gamedevjs/'
+        name: Seattle JavaScript Game Development
+        description: '<p>Our focus is on the expanding HTML5 field and javascript game development. This is a place to learn or teach, to share tips on programming, game engines, sdks, tools for development on the web and cross platform solutions. Meetings will be held in the greater Seattle area.</p>'
+        lon: -122.33999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/5/2/6/600_88538182.jpeg'
+        lat: 47.61000061035156
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/seattle-software-craftsmanship/'
+        name: Seattle Software Craftsmanship Community
+        description: '<p>We are a community of software professionals who are passionate about our craft and are committed to learning better ways of doing what we do, sharing with others, and growing as professionals in the process.</p>'
+        lon: -122.33000183105469
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/2/2/e/600_103156942.jpeg'
+        lat: 47.599998474121094
+      - country: US
+        city: Pittsburgh
+        link: 'http://www.meetup.com/Pittsburgh-Node-js/'
+        name: node.pgh
+        description: |-
+          <p><strong>Welcome to the Pittsburgh Node.js community Meetup!</strong></p>
+          <p>This is a meetup to discuss Node.js, popular npm modules, general web development and JavaScript running on the server. If you're interested in Node personally or professionally, we'd love to hear from you. Stop by to hear about something cool or, even better, stop by to tell others about something cool! This group is intended for beginners all the way up to veteran Node and JavaScript developers.&nbsp;</p>
+        lon: -79.97000122070312
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/d/3/c/600_276679772.jpeg'
+        lat: 40.400001525878906
+      - country: US
+        city: Arlington
+        link: 'http://www.meetup.com/Nova-Node/'
+        name: Nova Node
+        description: '<p>Learn about Node.js and related technologies, meet other Javscript developers, and discover new tools and tricks to make your next project with Node.js a success.</p>'
+        lon: -77.06999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/7/5/a/600_92262842.jpeg'
+        lat: 38.88999938964844
+      - country: US
+        city: Bangor
+        link: 'http://www.meetup.com/Hacker-Club/'
+        name: Hacker Club
+        description: "<p>Have a hankering for hacking? Been pounding away at a programming project? It's time to come out of the woodwork and pool our hacker minds for our mutual benefit. Bring your ideas, projects, and laptops to this shared hacking experience.</p>"
+        lon: -68.77999877929688
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/6/9/0/600_220869872.jpeg'
+        lat: 44.810001373291016
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/Los-Angeles-Hack-Night/'
+        name: Los Angeles Hack Night
+        description: "<p style=\"text-align : left\"><span style=\"font-size : x-large\"><strong>Prerequisites</strong></span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\">Hackers only. Bring your laptop and a project or tutorial to work on. Recruiters, spectators, etc. are not allowed.</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\"><br>\n\n</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : x-large\"><strong>What to expect</strong></span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\">Expect to find people sitting around tables talking about and working on their own projects and tutorials. We don't have presentations or structure so bring your own project, tutorial, etc., introduce yourself, ask people \"what are you working on\", find a seat and get yourself set up, hack away on your project, and have fun.</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\">We frequently see people learning and hacking on software projects using Java, Scala, Ruby, Python, Node, JavaScript, CoffeeScript, among other languages and hardware projects using Arduino.</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\">Our members include beginners working through the <a href=\"http://learncodethehardway.org/\" style=\"font-size : small\">Learn Code the Hard Way</a>,\_<a href=\"http://www.codecademy.com/\">Code Academy</a>, <a href=\"https://onemonthrails.com/\">One Month Rails</a>, etc. as well as experienced developers working on side projects.</span></p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\"><span style=\"font-size : x-large\"><strong>Sponsors</strong></span></p>\n<p style=\"text-align : left\"><span style=\"font-size : x-large\"><strong><img src=\"http://photos2.meetupstatic.com/photos/event/e/b/2/event_342783762.jpeg\" style=\"max-height : 700px ; max-width : 700px ; margin : 5px ; float : left\"></strong></span></p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\"><a href=\"http://www.pandastrike.com/\" style=\"font-size : small\">Panda Strike</a> <span style=\"font-size : small\">sponsors hack night regularly. Panda Strike is\_a consultancy focused on rich client, high-performance Web and mobile experiences and lightweight solutions for big data, primarily using CoffeeScript, Node.js, Elaticsearch, and a stack of innovative open source technologies. <a href=\"http://www.pandastrike.com/pages/hiring\">Panda Strike is hiring talented engineers</a>.</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\"><br>\n\n</span></p>\n<p style=\"text-align : left\"><strong><span style=\"font-size : x-large\">Sponsoring</span></strong></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\">If you're interested in hosting hack night or sponsoring food or drinks then send me an email.</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\"><br>\n\n</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : x-large\"><strong>Contact</strong></span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\">You can email me through meetup.com<br>\n\n Follow us on Twitter: @lahacknight</span></p>\n<p style=\"text-align : left\"><span style=\"font-size : small\"><br>\n\n</span></p>"
+        lon: -118.3499984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/9/3/8/600_93910552.jpeg'
+        lat: 34.06999969482422
+      - country: US
+        city: Redwood City
+        link: 'http://www.meetup.com/MindfulQS/'
+        name: 'Compassion Technology: Mindful QS'
+        description: |-
+          <p>Compassion Technology is Self-discovery, Self-development, and Service via logical and technological extensions of mindfulness!</p>
+          <p>We welcome developers, designers, and all other Good People who are trying to become even better through daily practice, deeply honest self-appraisal, and/or dedicated inspired study.</p>
+          <p>In particular, tech folks with a fondness for prayer, meditation, or other forms of mind/body awareness are especially likely to find a home here amongst like-minded souls.</p>
+        lon: -122.2699966430664
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/1/5/a/600_100125402.jpeg'
+        lat: 37.45000076293945
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/DC-Web-Design-Development-Tech-and-Media-Authority/'
+        name: 'DC Web Design, Development, Tech, and Media Authority'
+        description: |-
+          <p>If you are interested in learning or sharing anything about designing, developing and supporting a great <strong>web</strong> site, service, app or online social network community, this group will not just explore, but we will discuss and possibly build, <strong>together</strong>. &nbsp;This includes Javascript, HTML5, Ruby on Rails, MongoDB, mobile web support, CakePHP, WordPress and other content management systems. &nbsp;But it does not stop there.&nbsp;</p>
+          <p>This group will identify and explore the use of <strong>technologies</strong>, <strong>content</strong>, <strong>media</strong> and <strong>social</strong> elements that goes into supporting a <strong>Web 2.0/3.0</strong>&nbsp;environment. &nbsp;<strong>We won't just talk about these elements, we will use them to help each other build something.</strong>&nbsp; In-depth exploration, discussion, experimentation and implementation of <strong>HTML5</strong>, <strong>Javascript</strong>, <strong>CSS</strong>, <strong>PHP</strong>, <strong>Ruby on Rails</strong>, any and all <strong>elements</strong> that support today's web environment and services will be executed. &nbsp;</p>
+          <p>&nbsp;</p>
+          <p><strong>Meet our new organizers for&nbsp;<a href="http://www.meetup.com/DC-Web-Design-Development-Tech-and-Media-Authority/" target="_blank">DC Web Design Development Tech and Media Authority</a></strong>&nbsp;</p>
+          <p><img src="http://tacticaltechs.com/web-developer-organizers-team.jpg" style="max-height : 700px ; max-width : 700px ; margin : 5px"></p>
+          <p>&nbsp;</p>
+          <p>There's more to a web site than just the front end and various types of engines that do the work, you have to have somewhere to store the data itself right? &nbsp;We will explore and discuss the different database models such as <strong>MySQL</strong>, <strong>MongoDB</strong>, <strong>CouchDB</strong> and many others that can be used, depending on the <strong>requirements</strong> of the web project. &nbsp;While we we are at it, let's explore <strong>Cassandra</strong>.</p>
+          <p>So we will cover the web tech, content, media and the social elements of a website/service, but there is still more to it. &nbsp;So <strong>web hosting services</strong>, types and features will be identified. &nbsp;Everything from the use of shared hosting plans all the way up to <strong>Amazon Web Service (AWS)</strong> will be explored. &nbsp;Members will be able to make better more informed decisions on hosting service selections based on what we experience together.</p>
+          <p>There is a lot involved in developing a website, a service platform, social network or other online environment. &nbsp;You have the content, media, front and back ends of the solution that may leverage many pieces of technology fused together to make everything look great and function well. &nbsp;Some of us don't have the skills, time and/or resources to design, develop and maintain a website. For those members we will identify the best content management system (CMS that meets their needs such s <strong>WordPress</strong> and other popular CMS solutions. &nbsp;We will also explore emerging CMS solutions based on Ruby on Rails such as Locomotive, Radiant and Browser CMS to determine if they are worth the attention and time to implement.</p>
+          <p>Big ambitions right, well this is going to be a big group.</p>
+          <p>Using methods pioneered by&nbsp;<strong>JumpstartLab</strong>&nbsp;and<strong>&nbsp;Hungry Academy</strong>, we want to grow our own developers, including Ruby on Rails.</p>
+          <p>Folks, presentations are great, but this group is about more than that. &nbsp;We are actually going to build developers, build web sites and new types of online services.</p>
+          <p>How will we accomplish all of this?</p>
+          <ul>
+          <li><strong>Presentations</strong>&nbsp;from Ruby on Rails Pros, Javascript, HTML5, WordPress, CakePHP and other evangelists.</li>
+          <li><strong>Workshops</strong>&nbsp;(Hands On) introductions to new development tools, coding techniques, plugins, advance features and more</li>
+          <li><strong>Study Groups</strong>&nbsp;weekly smaller sessions at different locations to&nbsp;continue using web development toolkits on real world projects or just for fun</li>
+          <li><strong>Plugin</strong>&nbsp;development to extend the capabilities &nbsp;of WordPress and other CMS solutions</li>
+          <li><strong>Hackathons</strong>&nbsp;&nbsp;small and large, including conference size events hosted by our&nbsp;<strong>partners</strong>.</li>
+          </ul>
+          <p>Talking about web design and development tech and&nbsp;<strong>not</strong>&nbsp;doing anything useful with it is not what this group is about. &nbsp;We expect more and want to turn this into a&nbsp;<strong>real community</strong>&nbsp;of developers of all levels to&nbsp;<strong>learn</strong>,<strong>share</strong>&nbsp;and possibly&nbsp;<strong>collaborate</strong>&nbsp;on&nbsp;<strong>real world projects</strong>.</p>
+          <p>If this sound like something interesting that you want to be a part of, join us. &nbsp;If you want to contribute to meetups, become an organizer or even be a moderator at our study halls, just let us know.</p>
+          <p>&nbsp;</p>
+          <p><span>DC Web Design Development Tech and Media Authority is a part of Just Dev It (One) Network</span></p>
+          <p>&nbsp;</p>
+        lon: -77.0199966430664
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/2/2/a/600_101013322.jpeg'
+        lat: 38.90999984741211
+      - country: US
+        city: Oakland
+        link: 'http://www.meetup.com/EBJavaScript/'
+        name: East Bay JavaScript Meetup Group
+        description: "<p>Come discuss Javascript with some of the most talented programmers in the East Bay. Show off some of the cool projects you've been working on and talk about everything happening in the JS community. Let's share tips, tricks, hacks and frameworks! We don't have a JavaScript group in the East Bay so I thought I'd start one. Our first topic is an intro to Node. Come check it out!</p>\n<p>\_</p>\n<p>Logo provided by Oakland's Where It's AT-AT.\_<a href=\"http://www.oaklandiswhereitsatat.com/\">http://www.oaklandiswhereitsatat.com/</a></p>"
+        lon: -122.26000213623047
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/7/f/2/600_113954322.jpeg'
+        lat: 37.83000183105469
+      - country: US
+        city: Kansas City
+        link: 'http://www.meetup.com/JavaScriptKC/'
+        name: JavaScript KC
+        description: |-
+          <p>JavaScript KC is for those who use Node.js and JavaScript in general.&nbsp;<span>Come join us to talk and code in JavaScript!</span></p>
+          <p><span><a href="http://www.JavaScriptKC.com">http://www.JavaScriptKC.com</a></span></p>
+        lon: -94.56999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/6/f/2/600_448430930.jpeg'
+        lat: 39.099998474121094
+      - country: US
+        city: Philadelphia
+        link: 'http://www.meetup.com/nodejs-philly/'
+        name: Node.js Philly
+        description: For those working with or interested in Node.js.
+        lon: -75.16000366210938
+        lat: 39.95000076293945
+      - country: CA
+        city: Vancouver
+        link: 'http://www.meetup.com/node-brigade-vancouver/'
+        name: Node Brigade Vancouver
+        description: '<p>All about NodeJS.</p>'
+        lon: -123.0999984741211
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/c/f/8/600_123031992.jpeg'
+        lat: 49.279998779296875
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/bbdevla/'
+        name: Enterprise Developer Group
+        description: "<p><strong>The Enterprise Developer Group is sponsored by BlackBerry. We focus on business productivity services and solutions spanning mobility, server, wearable and embedded computing aka IoT.</strong></p>\n<p>We welcome a healthy discourse in an objective and collegial setting dedicated to everyone's success.</p>\n<p>\_</p>"
+        lon: -118.33000183105469
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/1/2/600_203341042.jpeg'
+        lat: 34.099998474121094
+      - country: CA
+        city: Ottawa
+        link: 'http://www.meetup.com/Ottawa-JavaScript/'
+        name: Ottawa JavaScript
+        description: '<p><span>Ottawa JavaScript is a friendly and fast-growing community of local developers exploring new, innovative technologies related to JavaScript. We cover everything from node, noSQL, HTML5, mobile apps, big data, and hardware hacking... to flying robots! Our monthly meetups feature interesting talks and demos by members at all levels.</span></p>'
+        lon: -75.66999816894531
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/1/9/6/600_332884502.jpeg'
+        lat: 45.400001525878906
+      - country: US
+        city: Westlake
+        link: 'http://www.meetup.com/Cleveland-JavaScript-Meetup/'
+        name: Cleveland JavaScript Meetup
+        description: "<p>It's time that Cleveland pulled together all the tech gurus playing around with JavaScript, ECMAScript, jQuery, Dojo, YUI, Sencha, CoffeeScript and much more, no matter whether on the server-side or in the browser. JavaScript is an extremely versatile (nicely put) language with some fantastic innovations happening. Backbone, Ember, NodeJS and many other new technologies are paving the way for very exciting things to come. Let's get together and teach each other about what is hip and happening!</p>"
+        lon: -81.93000030517578
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/b/a/6/600_138463942.jpeg'
+        lat: 41.45000076293945
+      - country: US
+        city: Palo Alto
+        link: 'http://www.meetup.com/NodeSummit/'
+        name: Node Summit
+        description: '<p>Meet ups organized to talk about Node.js and related technologies, learn about new projects using Node.js and connect with cutting edge geeks.</p>'
+        lon: -122.12999725341797
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/2/e/0/600_129304832.jpeg'
+        lat: 37.45000076293945
+      - country: US
+        city: Jacksonville Beach
+        link: 'http://www.meetup.com/Jax-js/'
+        name: Jax.js
+        description: "<p>We're a local group of Web workers with an interest in front-end technologies, including HTML/HAML, CSS/SASS, Javascript/CoffeeScript, and all things related to these languages.</p>"
+        lon: -81.41999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/6/9/e/600_175333982.jpeg'
+        lat: 30.280000686645508
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/Node-js-in-the-wild/'
+        name: Node.js in the wild
+        description: '<p>Node.js in the wild was started to discuss Node.js and its application in real live application...both large and small. Come out if you want to hear how others are using Node.js to solve real problems.</p>'
+        lon: -71.04000091552734
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/5/d/a/600_263278842.jpeg'
+        lat: 42.349998474121094
+      - country: US
+        city: Cincinnati
+        link: 'http://www.meetup.com/Node-cincy/'
+        name: 'Node.cincy : Cincinnati Node.js Meetup'
+        description: "<p>Are you interested in learning more about Node.js? Well then Node.cincy is the meetup for you. We'll be helping people get a handle on what Node.js is, how you can use it, and the best ways to build awesome stuff.</p>\n<p><br></p>\n<p>We have a Code of Conduct for all of our events that we adhere to. This makes it so we all have a good time &amp; feel comfortable \uD83D\uDE03<br><br><b>Code of Conduct</b></p>\n<p>We, the organizers of&nbsp;Node.cincy, are dedicated to providing a harassment-free community for everyone, regardless of sex, gender identity or expression, sexual orientation, disability, physical appearance, age, body size, race, nationality, or religious beliefs. We do not tolerate harassment of community members in any form. Participants violating these rules may be sanctioned or expelled from the community at the discretion of the organizers of Node.cincy.</p>\n<p>Harassment includes offensive verbal or written comments related to sex, gender identity or expression, sexual orientation, disability, physical appearance, age, body size, race, nationality, or religious beliefs, deliberate intimidation, threats, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Sexual language and imagery is not appropriate for any events at&nbsp;Nodeschool Cincinnatimeetups or in any related communication channels. Community members asked to stop any harassing behavior are expected to comply immediately. Sponsors and presenters are also subject to the anti-harassment policy.</p>\n<p>If a community member engages in harassing behavior, the organizers of&nbsp;Node.cincy may take any action they deem appropriate, including warning the offender or expulsion from the community. If you are being harassed, notice that someone else is being harassed, or have any concerns, please contact an organizer immediately.</p>"
+        lon: -84.5
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/1/b/0/600_143021392.jpeg'
+        lat: 39.11000061035156
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/nodela/'
+        name: Socal Software Developers
+        description: '<p>Anyone interested in or using Node.js, Javascript, CoffeeScript, and other related frameworks/technologies in the Los Angeles / Southern California Area</p>'
+        lon: -118.33999633789062
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/5/a/c/600_145182412.jpeg'
+        lat: 34.09000015258789
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Chicago-Ember-js/'
+        name: Chicago Ember.js
+        description: "<p>Chicago's Ember.js group is\_committed\_to creating a robust community built around the\_philosophy\_of building\_beautifully\_crafted web applications with the help of Ember.js.</p>\n<p>Meetups should be fun and\_engaging\_to\_promote\_a wealth of knowledge among your peers. We will always keep this as a core concept.</p>"
+        lon: -87.6500015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/d/9/a/600_284384442.jpeg'
+        lat: 41.91999816894531
+      - country: US
+        city: Minneapolis
+        link: 'http://www.meetup.com/NodeSummitMN/'
+        name: Node Summit Minnesota
+        description: '<p>Meet ups organized to talk about Node.js and related technologies, learn about new projects using Node.js and connect with cutting edge geeks.</p>'
+        lon: -93.2699966430664
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/600_151980002.jpeg'
+        lat: 44.97999954223633
+      - country: US
+        city: Phoenix
+        link: 'http://www.meetup.com/Phoenix-JavaScript/'
+        name: Phoenix JavaScript
+        description: "<p><span>Phoenix JavaScript hosts monthly events that allows members to network and hear technology presentations. Meetings are generally held on Wednesdays and we usually have stuff from sponsors to provide to members such as pizza and a t-shirt drawing. Membership is free, I only ask that you use Meetup's RSVP system to let us know you're coming. Our goal is to provide a regular event that allows our community to come together and learn from each other. We will always try to appeal to both experienced and inexperienced developers.</span></p>"
+        lon: -112.02999877929688
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/f/e/4/600_221080932.jpeg'
+        lat: 33.380001068115234
+      - country: US
+        city: Indianapolis
+        link: 'http://www.meetup.com/Node-indy/'
+        name: 'Node.indy : Indianapolis Node.js Meetup'
+        description: "<p>Are you interested in learning more about Node.js? Well then Node.indy is the meetup for you. We'll be helping people get a handle on what Node.js is, how you can use it, and the best ways to build awesome stuff.</p>"
+        lon: -86.11000061035156
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/e/8/4/6/600_158639462.jpeg'
+        lat: 39.869998931884766
+      - country: US
+        city: Brooklyn
+        link: 'http://www.meetup.com/Brooklyn-Node-JS-Meetup/'
+        name: Brooklyn Node JS Meetup
+        description: '<p>Node JS has gained a lot of attention in the press citing all the wonderful things being done with it. Rather than hearing about it, our meetup group is about doing things with Node JS (and related technologies like Socket.IO) that pushes the envelope. If you want to learn from others or show others what you can do, this is the community to join.</p>'
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/5/5/a/600_161229562.jpeg'
+        lat: 40.70000076293945
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/fullstackers/'
+        name: Bay Area Full Stack Developers
+        description: '<p>This meetup is for bringing together full stack developers. Talk Talks, tutorials related to full stack development and pitching events with participation from leading VCs and investors. Send email to organizer if you would like to propose any event topics.</p>'
+        lon: -122.06999969482422
+        lat: 37.38999938964844
+      - country: US
+        city: Milwaukee
+        link: 'http://www.meetup.com/milwaukeejs/'
+        name: MilwaukeeJS
+        description: |-
+          <p>A group for JavaScript enthusiasts and those looking to learn JavaScript in the Milwaukee area. &nbsp;We meet monthly to talk about different JavaScript and topics and are open to anyone from beginners and those who have been using JavaScript for years. &nbsp;Also be sure to join us in #JavaScript channel on the Milwaukee developer slack. Get an invite at&nbsp;http://mke-slack.herokuapp.com/</p>
+          <p><a href="http://files.meetup.com/5484242/Code%20of%20Conduct.pdf">Code of Conduct</a></p>
+        lon: -87.91000366210938
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/3/0/a/600_171457642.jpeg'
+        lat: 43.06999969482422
+      - country: US
+        city: Cambridge
+        link: 'http://www.meetup.com/Full-Stack-Boston/'
+        name: Full Stack Boston
+        description: |-
+          <p><span>Keep up with the latest you need to know in making your Internet based apps sing on a wide range of mobile and less-mobile platforms such as Android, Arduino, iOS, Mac, Raspberry PI, &amp; Windows.</span></p>
+          <p><span>We evaluate technologies and methodologies applicable anywhere within the software stack, but always in the context of multi-platform development and architectural impact. Preference is given to standards-oriented browser/web technologies, such as HTML/HTML5, CSS/CSS3, Javascript, etc. and cross-platform tools from Adobe and others. Discussions evaluate the technical merits of a subject and how it plays with other elements in the bigger picture, such as integration, workflow, maintenance and market/marketing considerations.</span></p>
+          <p><span>Our hope is to help each developer find their own answer to the never ending question: Is there a core skill set that can enable me to efficiently create elegant solutions that have the desired reach.</span></p>
+          <p>Please sign up for free &amp; join us on the journey.</p>
+          <p>Best regards, <br> <span>Douglas McCarroll &amp; Ira Hochman <br> Co-Organizers, Full Stack Boston</span></p>
+        lon: -71.08999633789062
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/0/7/2/600_442536978.jpeg'
+        lat: 42.369998931884766
+      - country: US
+        city: Redwood City
+        link: 'http://www.meetup.com/PersonalCapital/'
+        name: Personal Capital Engineering
+        description: |-
+          <p>Personal Capital Engineering is a group about how we can use technology to bring order to the chaos of finance.</p>
+          <p>It's a group for mobile, web and back-end developers and designers to learn and share their knowledge of building large, multi-client cloud-based systems.</p>
+          <p>Things like architecting single page apps, advanced charting for mobile and Amazon's simple notification service are par for the course, which will typically be a two part talk complemented by food and drink.</p>
+          <p>At Personal Capital we have developed clients for web, iOS and Android supported by a lean Java stack and cloud based back-end in Redwood City and want to jumpstart a more collaborative tech community here. Our engineering blog is here: http://techblog.personalcapital.com/</p>
+          <p>&lt;/Personal Capital Engineers&gt;</p>
+        lon: -122.19999694824219
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/2/0/e/600_176145582.jpeg'
+        lat: 37.4900016784668
+      - country: US
+        city: Tempe
+        link: 'http://www.meetup.com/NodeAZ/'
+        name: NodeAZ
+        description: '<p>@NodeAZ - Phoenix developer group for server-side JavaScript/CoffeeScript using Node.js. Real-time web, websockets, HTML5 and much more. 7PM 3rd Mon at UAT, rm 201</p>'
+        lon: -111.93000030517578
+        lat: 33.369998931884766
+      - country: US
+        city: Saint Petersburg
+        link: 'http://www.meetup.com/suncoast-js/'
+        name: Suncoast.js
+        description: |-
+          <p>A group for Tampa bay area JavaScript developers.</p>
+          <p>Code of Conduct:&nbsp;<a href="https://github.com/suncoast-devs/code-of-conduct/blob/master/code-of-conduct.md" class="linkified">https://github.com/suncoast-devs/code-of-co...</a></p>
+        lon: -82.7300033569336
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/8/e/2/600_185755522.jpeg'
+        lat: 27.790000915527344
+      - country: US
+        city: Philadelphia
+        link: 'http://www.meetup.com/Philly-Startup-Hackers/'
+        name: Philly Startup Hackers
+        description: |-
+          <p>We have monthly hackathons in the Philly area for people working on or interested in startups (primarily Internet related). A hackathon is an event with no specific agenda--everyone comes and "hacks" on their projects. It is a great place to meet other local hackers and get feedback/help on your projects.</p>
+          <p>Every month we have the meetup at a local Philly company where cool hacking is going on. We have pizza for dinner, hang out and talk about our startup experiences, and hack on our projects together.</p>
+        lon: -75.13999938964844
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/b/0/8/600_183776072.jpeg'
+        lat: 39.95000076293945
+      - country: US
+        city: Lexington
+        link: 'http://www.meetup.com/Kentucky-JavaScript-Users-Group/'
+        name: Kentucky JavaScript Users Group
+        description: "<p>Its the Kentucky JavaScript Users Group. Doesn't that just say it all?</p>"
+        lon: -84.4800033569336
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/9/6/e/600_184994702.jpeg'
+        lat: 38
+      - country: US
+        city: Charlottesville
+        link: 'http://www.meetup.com/Central-Virginia-Javascript-Enthusiasts-CVJSE/'
+        name: Central Virginia Javascript Enthusiasts (CVJS)
+        description: "<p>Javascript has good parts, bad parts, and parts you're most likely to only discover from the JS genius next door. Join the Central Virginia Javascript Enthusiasts if you want to tap the rich brain trust of web, node, and mobile developers using \"the worlds most popular language\" in Charlottesville, VA and surrounding areas. We meet every 4th Wednesday of the month in Charlottesville (exact location TBD) to share presos, code, tools, techniques and tall tales of Javascript (and Coffeescript) wonders. See also:\_<a href=\"http://cvjs.net\">http://cvjs.net</a></p>"
+        lon: -78.5199966430664
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/9/9/6/600_188695702.jpeg'
+        lat: 38.040000915527344
+      - country: US
+        city: Buffalo
+        link: 'http://www.meetup.com/Buffalojs/'
+        name: BuffaloJS
+        description: |-
+          <p><span>JavaScript Manifest Destiny: Whatever program can be written in JavaScript eventually WILL be written in JavaScript. - <em>Isaac Schlueter</em></span></p>
+          <p><span>Javascript is kicking ass and taking names right now. It is THE language that enables you to be a full-stack engineer and lets you to write once run anywhere. Let us show you the world of JS and remind you that not everything in Buffalo misses wide right.</span></p>
+        lon: -78.80000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/6/0/3/600_447489731.jpeg'
+        lat: 42.970001220703125
+      - country: US
+        city: Philadelphia
+        link: 'http://www.meetup.com/EmberJS-Philly/'
+        name: Ember.js Philly
+        description: |-
+          <p>This is a group for people interested in Ember.js, whether developing Ember.js for your day job, or just interested in learning more about it. We'll meet monthly or quarterly in Center City Philadelphia.</p>
+          <p>Join us on the<span>&nbsp;<a href="http://phillydev.org">http://phillydev.org</a>&nbsp;Slack group in the</span><span>&nbsp;#emberjsphilly channel.</span></p>
+        lon: -75.1500015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/a/7/f/600_435614975.jpeg'
+        lat: 39.939998626708984
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Austin-Backbone-js-Ninjas/'
+        name: Austin Backbone.js Ninjas
+        description: "<p>Rich User Experiences are moving to the web browser. This means jQuery spaghetti if you aren't already modularlizing your code. Make your Apps easier to maintain, improve, and test with Backbone.js and a suite of other hot technologies. Require.js (Dynamic Code/CSS Loading) Jasmine.js (Unit and Functional Test Framework) Node.js (Event Based Server Side Framework) Backbone-Marionette (Improved Event Handling, View Management)</p>"
+        lon: -97.73999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/0/c/e/600_440093454.jpeg'
+        lat: 30.270000457763672
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/NYC-Titanium-Users-Group/'
+        name: NYC Titanium Users Group
+        description: "<p>The purpose of the group is to support developers, designers, and other Titanium platform users with product knowledge, development skills and networking opportunities. Titanium is an open source development toolset and SDK that accelerates the development of native mobile applications for iOS, Android, BlackBerry 10, Tizen, and Windows Phone 8 (1Q13) devices. Appcelerator is the company that makes the Titanium platform and offers support, training and one of the best cloud service back-ends called Appcelerator Cloud Service (ACS).</p>\n<p>\_</p>\n<p><a href=\"http://www.meetup.com/NYC-Titanium-Users-Group/pages/NYC_Area_Titanium_Consultants_and_Professionals/\">Looking for a NYC Area Titanium Consultant/Professional?</a> <a href=\"http://www.meetup.com/NYC-Titanium-Users-Group/pages/Request_addition_as_Consultant_or_Professional/\">Want to be added to the list?</a></p>\n<p><a href=\"http://www.meetup.com/NYC-Titanium-Users-Group/pages/Titanium_Help_Wanted/\">Titanium Help Wanted Postings.</a> <a href=\"http://www.meetup.com/NYC-Titanium-Users-Group/pages/Request_addition_of_Help_Wanted/\">Want to add a posting?</a></p>"
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/a/e/0/600_194075552.jpeg'
+        lat: 40.72999954223633
+      - country: US
+        city: Raleigh
+        link: 'http://www.meetup.com/triangle-nodejs/'
+        name: Triangle Node.js
+        description: '<p>A group for people in the Raleigh-Durham-Chapel Hill area working with (or interested in) Node.js.</p>'
+        lon: -78.63999938964844
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/c/1/e/600_194303582.jpeg'
+        lat: 35.77000045776367
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/pdxnode/'
+        name: PDXnode
+        description: "<p>Our group is open and geared to engage all levels of programmer. We seek to build a community of developers who enjoy each other's company while being excited about developing JavaScript. \_Whether you're wondering why in the world you would want to put JavaScript on a server or want to discuss the different implementations of the promises/A+ standard and the eternal struggle with callbacks, we're here to help!</p>\n<p>We've hosted\_<a href=\"https://tito.io/pdxnode/nodebotsday\">PDX International NodeBots day</a>,\_<a href=\"http://2013.cascadiajs.com/#train\">Hacker Train</a>, and host a\_<a href=\"http://www.meetup.com/nodepdx/\">monthly presentation night and Code &amp; Learn night</a> as well. Look forward to workshops and many great talks to come!</p>\n<p><span>We support our\_<a href=\"https://github.com/PDXNode/pdxnode/blob/master/code-of-conduct.md#code-of-conduct\">Code of Conduct</a> and welcome input to improve upon it via issues submission and pull requests--long story short: \"Don't be a jerk.\"</span></p>\n<p>To contribute please look at our\_https://github.com/PDXNode/pdxnode</p>"
+        lon: -122.68000030517578
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/e/4/4/600_335364132.jpeg'
+        lat: 45.529998779296875
+      - country: US
+        city: Philadelphia
+        link: 'http://www.meetup.com/Philadelphia-JavaScript-Developers/'
+        name: Philadelphia JavaScript Developers
+        description: |-
+          <p>This is a group for developers to meet up and exchange knowledge about the latest trends in JavaScript Development in Philadelphia. We have longer talks on the odd months, lightning talks/project night on the even months. Come meet your fellow JavaScripters, whether you've been writing it since 1997 or since last week. Welcome!</p>
+          <p>If you'd like to speak, drop us a line at&nbsp;<a href="http://bit.ly/1tkLzGD">http://bit.ly/1tkLzGD</a>. And follow us on Twitter at <a href="https://twitter.com/phillyjsdev">@phillyjsdev</a>.</p>
+        lon: -75.16000366210938
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/6/0/a/600_343745642.jpeg'
+        lat: 39.95000076293945
+      - country: US
+        city: Santa Cruz
+        link: 'http://www.meetup.com/node-sc/'
+        name: node.sc
+        description: |-
+          <p>Node.SC aims to bring together Santa Cruz developers and technologists who use node.js or want to learn about node.</p>
+          <p>I'd like to build a community of experts and newcomers in an atmosphere where people feel comfortable teaching, learning, collaborating, and just nerding-out!</p>
+          <p>I picture our typical meetup running something like:</p>
+          <ol>
+          <li><span>Meet and greet</span></li>
+          <li><span>A couple 'lightning talks' (5 mins) on topics such as 'Quick Tips', 'Hot Modules', 'Node.JS Core Update', etc.</span></li>
+          <li><span>One or two longer talks (20 mins) on topics such as 'How To .....', 'Module Review', 'Case Study', 'Project Pitch', etc. I'd like to encourage these longer talks to include 'live coding' and actual execution of sample code. In my experience, showing people how stuff really works is both more engaging and more impressive :)</span></li>
+          <li><span>Keep the conversation going over drinks and snacks.</span></li>
+          <li><span>Wifi and seating to encourage hacking after the talks are over.</span></li>
+          </ol>
+          <p>I'm excited to get this group going but I'll be looking for your help and look forward to building something exciting and long-lasting!</p>
+          <p>What is node.js? - Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. http://nodejs.org/</p>
+        lon: -122.05999755859375
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/6/d/a/600_202675002.jpeg'
+        lat: 36.9900016784668
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Escape-from-dev-null-CA/'
+        name: Escape from /dev/null CA
+        description: "<p>Escape from /dev/null (or just /dev/null for short) is series of unique and engaging programming competitions.</p>\n<p>Actually, they differ from traditional programming competitions in that they are not boring, not about boring things, mostly shy away from abstract algorithmic brain-twisters and instead focus on practicality and having fun.</p>\n<p>The 'outer game' is played by logging int to a web-based interface. It could theoretically be played online entirely, but it's always done in a ballroom setting where all players as teams and the judges meet in person during the game.</p>\n<p>The 'inner game' is revealed one challenge at a time where teams create their own way of interacting with it.</p>\n<p>\_</p>"
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/c/1/a/600_202759482.jpeg'
+        lat: 37.779998779296875
+      - country: US
+        city: New Orleans
+        link: 'http://www.meetup.com/FrontEndParty/'
+        name: '#FrontEndParty'
+        description: "<p>Are you a developer on the front-end side of things, looking to learn the latest HTML5 / CSS3 / Javascript tricks and best practices? Are you a designer who would love a second set of eyes on their latest work, or to talk about the newest design trends and styles? If this sounds like you, then come join us at FrontEndParty and throw your ideas into the mix. We’ll host three 15 minute presentations from developers and designers around New Orleans on the last Thursday of every month.</p>\n<p>Looking for more details? \_Check out\_<span>http://www.frontendparty.com for the latest info!</span></p>\n<p>Want to present at FrontEndParty? <a href=\"https://docs.google.com/a/joeellis.la/spreadsheet/viewform?formkey=dC1SQlBHdU5yS2xKODR0bjR5QTFENHc6MQ\">Apply to present</a></p>"
+        lon: -90.08000183105469
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/8/e/6/600_204798662.jpeg'
+        lat: 29.959999084472656
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/TwilioSF/'
+        name: Twilio San Francisco Meetup Group
+        description: '<p>Join our meetup group for events centered around building with Twilio cloud communications, design and development, APIs, and more.</p>'
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/f/b/2/600_204940882.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/apidiscovery/'
+        name: API Discovery
+        description: |-
+          <p>This group is designed for developers looking to discover APIs and services that can help speed up and modularize their development and so time is not wasted re-inventing wheels. We will meet and learn the ins and outs of a new API every week, and why that API is relevant to development. Every API demo will be fun and engaging, and the goal of this meetup is not only to learn, but to also have a great time and make friends!</p>
+          <p>SPONSOR MESSAGE<br>Lyft is currently offering members of our Meetup free ride credit to try the service! Visit <a href="https://www.lyft.com/invited/DEV">https://www.lyft.com/invited/DEV</a> to get your free credit.&nbsp;<br></p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/e/3/8/600_392651832.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/hackreactor/'
+        name: 'Hack Reactor: Learn to Code'
+        description: |-
+          <p>Hack Reactor is a 12-week immersive coding school offering classes onsite in San Francisco and online through Hack Reactor Remote Beta. &nbsp;Our Meetup group exists to help both aspiring &amp; established coders level up.&nbsp;</p>
+          <p><span><a href="http://hackreactor.com">http://hackreactor.com</a> <br> Twitter:</span> <a href="https://twitter.com/hackreactor">@HackReactor</a></p>
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/c/4/6/600_231404102.jpeg'
+        lat: 37.779998779296875
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/DC-Hack-and-Tell/'
+        name: DC Hack and Tell
+        description: "<p>It's Hack and Tell, in DC! There's a web site with descriptions of past events! <a href=\"http://dc.hackandtell.org/\" class=\"linkified\">http://dc.hackandtell.org/</a> See the meetup event descriptions for more!</p>"
+        lon: -77.0199966430664
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/0/b/0/600_388245232.jpeg'
+        lat: 38.90999984741211
+      - country: US
+        city: Birmingham
+        link: 'http://www.meetup.com/bhm-js/'
+        name: Birmingham Javascript Meetup
+        description: '<p>Birmingham JavaScript meetup. #bhmjs on social media.</p>'
+        lon: -86.80999755859375
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/b/d/2/600_233487602.jpeg'
+        lat: 33.459999084472656
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Sails-js-Austin/'
+        name: Sails.js Austin
+        description: '<p>This has always been a group for developing ideas and apps with Sails.js, the MVC framework for Node.js...now find us over on the Austin Node.js Meetup page~&nbsp;http://www.meetup.com/noders/</p>'
+        lon: -97.7699966430664
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/e/1/2/a/600_214197642.jpeg'
+        lat: 30.350000381469727
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/js-read/'
+        name: JavaScript Reading Group
+        description: "<p>If your growing list of JavaScript books, articles, and tutorials to read through is as long as your list of projects to experiment with--and you know you're never going to finish all of them alone--this group is for you. Considering the pace of evolution in the JavaScript world, trying to stay on top of all that's happening is at best optimistic, and at worst a fool's game. But don't surrender! Enjoy the support and encouragement of a community of like-minded JavaScript coders and enthusiasts. We agree on what we most want to read, commit to a timeframe, and then get together to discuss what we've learned. Together we are building an environment where we can exchange informed opinions and insights with peers, while reading a curated selection of expert writings about JavaScript and its various flavors, libraries, and implementations.</p>"
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/4/e/a/600_213418602.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: Santa Monica
+        link: 'http://www.meetup.com/Los-Angeles-CoffeeScript/'
+        name: Los Angeles CoffeeScript
+        description: "<p><span style=\"font-size : x-large\"><strong>What is CoffeeScript?</strong></span></p>\n<p><a href=\"http://coffeescript.org/\">CoffeeScript</a> is a little language that compiles into JavaScript. Underneath that awkward Java-esque patina, JavaScript has always had a gorgeous heart. CoffeeScript is an attempt to expose the good parts of JavaScript in a simple way.</p>\n<p><span>For a quick introduction to CoffeeScript check out Panda Strike's</span> <a href=\"http://www.pandastrike.com/pages/intro-to-coffeescript\">Introduction to CoffeeScript</a></p>\n<p>\_</p>\n<p><span style=\"font-size : x-large\"><strong>Who We Are</strong></span></p>\n<p>We're a group of professionals so in love with CoffeeScript we've developed our own tutorials. We're starting this meetup to show others why we enjoy developing in CoffeeScript and to interact with others who are also using CoffeeScript.</p>\n<p>\_</p>\n<p><span style=\"font-size : x-large\"><strong>What To Expect</strong></span></p>\n<p>Some programming experience is assumed.\_<span>For people who are new to CoffeeScript we'll provide self-paced tutorials. For people who are further advanced we'll have projects to work on and talk about, people to <a href=\"http://www.youtube.com/watch?v=kQFKtI6gn9Y\">argue</a> with.</span></p>\n<p>\_</p>\n<p style=\"text-align : left\"><span style=\"font-size : x-large\"><strong>Sponsors</strong></span></p>\n<p style=\"text-align : left\"><img src=\"http://photos2.meetupstatic.com/photos/event/e/b/2/event_342783762.jpeg\" style=\"max-height : 700px ; max-width : 700px ; margin : 5px ; float : left\"></p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\">\_</p>\n<p style=\"text-align : left\"><span><a href=\"http://www.pandastrike.com/\">Panda Strike</a> is\_a consultancy focused on rich client, high-performance Web and mobile experiences and lightweight solutions for big data, primarily using CoffeeScript, Node.js, Elaticsearch, and a stack of innovative open source technologies.</span> <a href=\"http://www.pandastrike.com/pages/hiring\">Panda Strike is hiring talented engineers</a><span>.</span></p>\n<p style=\"text-align : left\"><span><br>\n\n</span></p>\n<p style=\"text-align : left\"><strong><span style=\"font-size : x-large\">Sponsoring</span></strong></p>\n<p style=\"text-align : left\">If you're interested in hosting hack night or sponsoring food or drinks then send Lance Lakey an email through meetup.com</p>\n<p style=\"text-align : left\">\_</p>"
+        lon: -118.5
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/7/4/e/600_213990542.jpeg'
+        lat: 34.02000045776367
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/lever-open-source/'
+        name: Lever Open Source
+        description: '<p>Lever is the company behind the Derby JavaScript MVC Framework. Learn more at http://derbyjs.com/</p>'
+        lon: -122.41000366210938
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/9/4/c/600_303871052.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/nyfrontendcoders/'
+        name: New York Front End Coders
+        description: "<p>We're a group of New York based front end developers passionate about the technologies we work with on a daily basis. We are hoping to create a community of people to explore ideas, learn, teach and share information around user experience, design, and new emerging techniques and technologies. This group will host talks and workshops to discuss best practices, HTML5, CSS, cross-browser support and testing, mobile, optimization techniques and more. Get updates via @Shuttertech on Twitter.</p>"
+        lon: -74.01000213623047
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/7/2/a/600_226375082.jpeg'
+        lat: 40.70000076293945
+      - country: US
+        city: Santa Rosa
+        link: 'http://www.meetup.com/Norcal-Javascript-Hackers/'
+        name: Norcal Javascript Hackers
+        description: "<p><span>Mission</span>:</p>\n<p> </p>\n<p></p>\n<p></p>\n<ul> \n <p><span>Finding all the best engineers...</span></p> \n <p><span>Bring us together to expand our networks...</span></p> \n <p><span>Make people better at what they do!</span></p> \n</ul>\n<p></p>\n<p> </p>\n<p><span>At Meetups We Typically</span>:</p>\n<p> </p>\n<p></p>\n<p></p>\n<ul> \n <p>Bounce ideas off friends and peers</p> \n <p>Validate our assertions</p> \n <p>Lean on each others experience</p> \n <p>Give short talks on stuff we are leaning</p> \n <p>Drink Coke</p> \n <p>Drink Beer</p> \n <p>Win more</p> \n</ul>\n<p></p>\n<p> </p>\n<p>&nbsp;</p>"
+        lon: -122.69000244140625
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/9/2/f/600_436915599.jpeg'
+        lat: 38.459999084472656
+      - country: US
+        city: Salt Lake City
+        link: 'http://www.meetup.com/UtahJS/'
+        name: UtahJS
+        description: |-
+          <p>This group is all about JavaScript in Utah.</p>
+          <p>We meet the 1st Thursday of the month in Orem, the 3rd Tuesday of the month in SLC, and at least monthly in Logan. On the 4th Thursday of the month in Sandy is our Angular meetup.</p>
+          <p><span>See also utahjs.com</span></p>
+          <p><span>Join our mailing list at&nbsp;<a href="https://groups.google.com/forum/#!forum/utahjs" class="linkified">https://groups.google.com/forum/#!forum/uta...</a></span></p>
+          <p><span>Join us on Slack at http://slack.utahjavascript.com.</span></p>
+        lon: -111.88999938964844
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/9/a/8/600_226003432.jpeg'
+        lat: 40.709999084472656
+      - country: US
+        city: Lindon
+        link: 'http://www.meetup.com/UtahJS-Orem-Meetup/'
+        name: UtahJS Orem Meetup
+        description: "<p>This group is all about JavaScript in the Orem, Utah area.</p>\n<p>We meet every 1st Thursday of the month... each and every month. We also have other hackathons, lunches, etc... on other days.</p>\n<p>We are having our second UtahJS 2013 conference in SLC, Utah on May 17th, 2013.</p>\n<p>http://lanyrd.com/2013/utahjs/</p>\n<p>See utahjs.com for what we'll be talking about this month!</p>\n<p>\_</p>"
+        lon: -111.7300033569336
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/9/f/8/600_226003512.jpeg'
+        lat: 40.34000015258789
+      - country: US
+        city: York
+        link: 'http://www.meetup.com/york-js/'
+        name: york.js
+        description: york.js is a group for discussing all things JavaScript.
+        lon: -76.7699966430664
+        lat: 39.970001220703125
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Ember-ATX/'
+        name: Ember ATX
+        description: 'Ember ATX is a group for people of all skill levels to come together, learn, and help one another build ambitious web applications.'
+        lon: -97.7300033569336
+        lat: 30.290000915527344
+      - country: US
+        city: Santa Monica
+        link: 'http://www.meetup.com/socal-angular/'
+        name: SoCal AngularJS
+        description: |-
+          <p>If you love testable JavaScript, this group is for you!</p>
+          <p><span>If you want to getting into testing your code, jump in!</span></p>
+        lon: -118.5
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/5/4/0/600_228133632.jpeg'
+        lat: 34.02000045776367
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/Portland-JavaScript-Admirers/'
+        name: Portland JavaScript Admirers
+        description: |-
+          <p><span>We host monthly presentations and discussions on everything JavaScript-related - including client-side application frameworks, node.js, CoffeeScript, and whatever else comes up.</span><br>
+
+          <br>
+
+          <span>Join the conversation by subscribing to our</span> <a href="http://groups.google.com/group/pdxjs" target="_blank">mailing list</a> <span>on Google Groups.</span><br>
+
+          <br>
+
+          <span>Follow the Portland JavaScript Admirers on</span> <a href="https://twitter.com/pdxjs" target="_blank">Twitter</a> <span>or on</span> <a href="https://plus.google.com/102821302536334304550/posts" target="_blank">Google+</a><span>.</span><br>
+
+          <br>
+
+          <span>Find out about other groups and events in Portland on</span> <a href="http://calagator.org/" target="_blank">Calagator</a><span>.</span></p>
+        lon: -122.69000244140625
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/6/0/e/600_228590702.jpeg'
+        lat: 45.52000045776367
+      - country: US
+        city: Dallas
+        link: 'http://www.meetup.com/Club-AJAX/'
+        name: Club AJAX
+        description: '<p>Club AJAX is a site devoted to JavaScript and related technologies, such as CSS3 and HTML5, and strives to be the portal for the latest information, news and discussions surrounding front end development. The DFW Club AJAX User Group was founded by Bob Byron and Mike Wilcox in January 2009. The goal for the group is to gather a community of professionals with like-minded interests and everything involved in making great apps and websites.</p>'
+        lon: -96.80000305175781
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/7/2/2/600_337586402.jpeg'
+        lat: 32.970001220703125
+      - country: US
+        city: Dublin
+        link: 'http://www.meetup.com/Columbus-Nodejs-User-Group/'
+        name: Columbus Node.js User Group
+        description: |-
+          <p>With Columbus' Node.js community small but growing, it is time for an avenue to share knowledge and to meet like-minded people. This group hopes to do just that. We will meet to discuss favorite modules or testing libraries, share our experiences, and most of all to share the joy of Node.js with anyone interested.</p>
+          <p>Also join us on Google+.</p>
+          <p>https://plus.google.com/u/0/communities/107657401765720049052</p>
+        lon: -83.12000274658203
+        lat: 40.099998474121094
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/ngpdxers/'
+        name: Angular Portland Meetup
+        description: |-
+          <p>We are a community of javascript enthusiasts that share a love for Angular.&nbsp; Some of us have been using it for years and others are just hearing about it.&nbsp;&nbsp;</p>
+          <p>Each month we get together to hear about all the great things that make up the Angular framework and see what great things people are creating with it.</p>
+        lon: -122.69000244140625
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/f/c/b/600_435640907.jpeg'
+        lat: 45.5
+      - country: CA
+        city: Vancouver
+        link: 'http://www.meetup.com/CSS-Brigade-Vancouver/'
+        name: CSS Brigade Vancouver
+        description: "<p><span>It's been long overdue the need for a CSS meetup in Vancouver...</span></p>\n<p><span>T</span><span>he world of CSS is changing extremely fast and it's getting harder and harder to keep up.</span> <span>There are no shortage of challenges when it comes to writing and maintaining CSS for modern web applications.</span></p>\n<p><span>Let's solve that problem. Come to share and learn the latest CSS techniques at CSS Brigade.</span></p>\n<ul> \n <p><span>Responsive/</span>Adaptive Design</p> \n <p>Semantic Grids</p> \n <p>SMACSS, OOCSS and BEM</p> \n <p>CSS Frameworks</p> \n <p>Anything related to CSS...</p> \n</ul>"
+        lon: -123.0999984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/f/2/8/600_234332552.jpeg'
+        lat: 49.279998779296875
+      - country: US
+        city: Stevens Point
+        link: 'http://www.meetup.com/Central-WI-Developers-Group/'
+        name: Central WI Developers Group
+        description: '<p>This is a group for anyone who is interested in software development and/or related topics. All skill levels are welcome.</p>'
+        lon: -89.55999755859375
+        lat: 44.540000915527344
+      - country: US
+        city: Richmond
+        link: 'http://www.meetup.com/rva-js/'
+        name: RVA.js
+        description: "<p>Let's get together to talk about how to use JavaScript to build applications. Visit our site here: http://rvajs.com/</p>"
+        lon: -77.48999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/1/b/2/600_338873682.jpeg'
+        lat: 37.560001373291016
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/AngularJS-Toronto/'
+        name: 'AngularJS Toronto (#AngularJSTO)'
+        description: "<p>Welcome to the <strong>Toronto AngularJS</strong> meetup. We generally try to meet the 3rd Wednesday of every month. Join our group and follow us\_<span>on twitter for updates,</span> <a href=\"https://twitter.com/NGToronto\">@NGToronto</a>.</p>\n<p><span>AngularJS is the future of web development. It's so much better than everything else you'll shed tears of joy as you finally shed the trauma of out-of-control unobtrusive JavaScript (how on earth do you figure out what a page does?), jQuery (amazing but it doesn't scale), overloaded CSS (update at your own risk!) and the resulting expensive and unmaintainable web applications. AngularJS is to jQuery what jQuery is to non-library JavaScript. It's that good.</span></p>\n<p><strong>The 5 D's of AngularJS:</strong></p>\n<p>1. <strong>DRY</strong>. Don't repeat yourself, which means no boilerplate.</p>\n<p>2. <strong>Declarative</strong>. HTML is the template and markup with AngularJS directives is the templating language. This works perfectly thanks to the next two D's.</p>\n<p>3. <strong>Dependency injection</strong>. Now I'm crying. You can actually test AngularJS apps, but more importantly you have scoping kung-fu where everything is modular, decoupled, and has a clearly logical place to go. It's pretty, implicit, magical, and it fixes 90% of what's wrong with every other JavaScript framework.</p>\n<p>4. <strong>Data-binding</strong>. Now I'm openly weeping with joy. Data-binding in a dependency managed, magically scoped, declarative, and DRY language is beautiful, amazingly succinct and powerful. Data-binding isn't the start with Angular- it's result. And this is the essence of Angular- the magic is in how everything works together. Dry + Declarative + Dependency Injection + Data-binding ALL work together. Remove one of them and AngularJS isn't AngularJS.</p>\n<p>5. <strong>Designer-Friendly</strong>. Your CSS will no longer look like you wrote it while on crack, and you can see within the HTML the general outline of what those developers are doing. And with that, you are free to go to town on the markup so long as you don't delete the ng- magic tags. Yes, dear designer, you can change the markup and style the application without destroying the business logic. How cool is that.</p>\n<p>So there you have it.</p>\n<p>Tweet insights to <a href=\"https://twitter.com/NGToronto\">@NGToronto</a> using the <strong>#AngularJSTO</strong> hashtag.</p>\n<p><strong>PRESENTING:</strong></p>\n<p>We are always looking for speakers &amp; presenters for future meetups, so if you are using or teaching AngularJS, please submit to speak:</p>\n<p><span><a href=\"http://tinyurl.com/AJSTO-Speaker\">http://tinyurl.com/AJSTO-Speaker</a></span></p>\n<p>If you wish to recommend someone to speak or a topic you want covered, please submit to:</p>\n<p><a href=\"http://tinyurl.com/AJSTO-Recommend\">http://tinyurl.com/AJSTO-Recommend</a></p>\n<p>if you have an interest in sharing your work with the group.</p>\n<p><em>Watch these and other AngularJS-Toronto meetup talks at\_<a href=\"https://www.youtube.com/rangleio/\">youtube.com/rangleio</a></em></p>"
+        lon: -79.37999725341797
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/0/3/600_436380259.jpeg'
+        lat: 43.650001525878906
+      - country: US
+        city: Berkeley
+        link: 'http://www.meetup.com/Angular-js-Meetup/'
+        name: East Bay AngularJS +
+        description: |-
+          <p>East Bay AngularJS. We'll be talking about Angular 2, ES6, Typescript, and JavaScript in general.</p>
+          <p>If you would like to present about Angular 2 topics, please contact me through the link in the sidebar.</p>
+          <p>If you're interested in helping to organize events, or know of a good venue, send an email. Be sure to also join the <a href="http://www.meetup.com/codeselfstudy/">Code Self Study</a> group!</p>
+        lon: -122.26000213623047
+        lat: 37.869998931884766
+      - country: US
+        city: Berkeley
+        link: 'http://www.meetup.com/Javascript-from-Zero-to-Hero/'
+        name: Javascript from Zero to Hero
+        description: |-
+          <p>Often considered as not so serious in the recent past, Javascript has come a long way in becoming the most popular language used on all size projects. A handful of libraries such as jQuery brought it to the masses and unveiled the true potential of JS resulting in a widespread adoption of it. As you may find out it is very easy to get started with Javascript, almost instantly you can see your code being executed in the browser window and strike a superhero pose thinking out loud "I rock!!!." In reality as easy it is to write JS code it's even easier to write bad code or over engineered chunks to do simple or complex tasks.&nbsp;</p>
+          <p><br>This meetup is geared toward the beginner in programing in general with a focus on Javascript. We will take the baby steps to learn the core language first and slowly but surely look at libraries and frameworks. <br>If you are a print or web designer who has never coded before but want to add a new skill to your toolbox, a hobbyist who is enthusiastic about new languages and technologies in general, or want to unlock the true potential of HTML5 with the new APIs such as geolocation, File, websockets and more, this is definitely the meetup for you.&nbsp;</p>
+          <p><br>This will be run workshop style with a lot of hands on training and a small amount of lectures and presentations. So come and get ready to get your hands dirty.</p>
+        lon: -122.26000213623047
+        lat: 37.880001068115234
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/San-Diego-JavaScript-Study-Group/'
+        name: San Diego JavaScript Study Group
+        description: |-
+          <p>Trying to work through a JavaScript book or tutorial you found on the web? Have questions about a specific js concept? Bring it to the study group! This is your chance to make progress and ask questions in a non-intimidating environment. Our small group setting is perfect for in-depth discussions.</p>
+          <p>Suggest a book or article and we will work through the exercises together. We can also work through various JavaScript concepts to get a better understanding of the language.</p>
+        lon: -117.19999694824219
+        lat: 32.88999938964844
+      - country: US
+        city: Leesburg
+        link: 'http://www.meetup.com/Ruby-LoCo/'
+        name: Ruby LoCo
+        description: '<p>Rubyists of Loudoun County, VA. We meet the last Friday of every month for lunch. We also meet the second Monday of every month for a hack night. Please join us.</p>'
+        lon: -77.61000061035156
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/0/9/8/600_247241112.jpeg'
+        lat: 39.08000183105469
+      - country: US
+        city: Irvine
+        link: 'http://www.meetup.com/Node-JS-OC/'
+        name: Node.js OC
+        description: '<p>Lets Learn, Hack, Build with Javascript and Node JS. All skills welcome.</p>'
+        lon: -117.83000183105469
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/3/e/c/600_419193772.jpeg'
+        lat: 33.68000030517578
+      - country: US
+        city: Santa Barbara
+        link: 'http://www.meetup.com/Santa-Barbara-JavaScript-Meetup/'
+        name: Santa Barbara JavaScript
+        description: '<p>SB has Rails. SB has Python. SB has UX! But where is the JavaScript love? Want to escape your jQuery hammer? Want to learn the ins and outs of JavaScript the language? &nbsp;Interested in ES6 and 7? Interested in using sweet new frameworks like React, Angular, Aurelia, Ember. Or maybe Node is your thing? Want to know different styles of programming like imperative, object-oriented, functional, or even functional reactive? Maybe learn how to test and organize your code better? Want to hack on cool projects? This could be for you! Come and join us.</p>'
+        lon: -119.70999908447266
+        lat: 34.41999816894531
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/statsd/'
+        name: StatsD NY Meetup
+        description: '<p>This Meetup is about supporting the community and users that are using StatsD to measure their own custom application metrics. Meetups will go over how others are using StatsD, and connecting the community with each other to share war stories and best practices.</p>'
+        lon: -74
+        lat: 40.7400016784668
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/openhackatx/'
+        name: OpenHack Austin
+        description: "<p>OpenHack, as the name implies, is an open \"forum\" for all software engineers in the city to come together and work on any project they like in a setting conducive to meeting new people, getting work done, and/or learning new skills. It's a great chance to get out and pair with others (or work by yourself), bounce ideas off other people, and connect with other developers in the city. Any project, any programming language, any platform, any reason - everyone who's looking to write some code (or pair program) is welcome. Take some time to work on that side project, learn a new skill, and make some new friends by coming out to OpenHack Austin.</p>"
+        lon: -97.73999786376953
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/c/3/a/600_252311322.jpeg'
+        lat: 30.270000457763672
+      - country: US
+        city: Chandler
+        link: 'http://www.meetup.com/Phoenix-Angular-js/'
+        name: Phoenix Angular.js
+        description: '<p>Angular.js is on FIRE. Whether you are already working with angularJS or you are a front end developer working with javascript, ember, jquery, etc, we are bringing people together to grow and strengthen the community of people who use AngularJS.</p>'
+        lon: -111.91999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/7/c/c/600_258347052.jpeg'
+        lat: 33.310001373291016
+      - country: US
+        city: Minneapolis
+        link: 'http://www.meetup.com/NodeMN/'
+        name: NodeMN
+        description: '<p>A group for anyone interested in Node.js regardless of skill level or experience. Join us in discussing the latest frameworks, projects, conferences and hacks using anything node.</p>'
+        lon: -93.25
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/a/c/0/600_373703232.jpeg'
+        lat: 45
+      - country: US
+        city: San Jose
+        link: 'http://www.meetup.com/Samsung-Developers/'
+        name: Samsung Developer Connection
+        description: |-
+          <p>Samsung Developer Connection is a team dedicated to serving you by connecting people with BIG opportunities at Samsung—tools, workshops, networking events, introductions to Samsung business leaders. Access to our powerful smartphones, tablets, Samsung GALAXY Apps store, Smart tv’s, wearables, virtual reality—we are here to pave new roads to help you stand out above the crowd.</p>
+          <p> <br></p>
+        lon: -121.88999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/7/2/3/600_439294595.jpeg'
+        lat: 37.33000183105469
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/Meteor-South-Bay/'
+        name: Meteor South Bay
+        description: |-
+          <p>We're all about Meteor! Meteor is a complete open source platform&nbsp;for building web and mobile apps&nbsp;in pure JavaScript. Learn more about it at http://meteor.com.<br></p>
+          <p>We do various kinds of meetups all over the South Bay. Most of them focus on speakers and lightning talks, but we also like to get together for hands on working sessions and occasionally do more social events too! Our favourite hangout spots are tech companies in the area - we've been to Google, Mozilla, MongoDB, ShareThis, Nook, Elastic, Shape and more so far.</p>
+          <p>This is a meetup for newbies and advanced users alike. If you're looking to learn about Meteor, we'll be there to help you out! Just come to a hands on working session, generally organised by Laurie, and get to know other early Meteor developers. If you've built something with Meteor and you'd like to share, let us know and we can schedule a lightning talk for you at the next meetup!</p>
+          <p><br></p>
+        lon: -122.05000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/7/b/4/600_438270644.jpeg'
+        lat: 37.40999984741211
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/PDX-Web-Development/'
+        name: PDX Web Development
+        description: "<p><span style=\"font-size : medium\"><strong><span style=\"color : #666666\">This group will focus on anything about development and technologies that run on the browsers (i.e. JavaScript (JS), JS frameworks (AngularJs, Backbone), HTML5, CSS3, Web Performance, etc..). I started this group because I want to share what I know about web development with other people and learning from them at the same time. I hope this meetup will also be a place where people can network and enjoy good conversations.</span></strong></span></p>\n<p>\_</p>\n<p><span style=\"font-size : medium\"><strong><span style=\"color : #666666\">Best,</span></strong></span></p>\n<p><span style=\"font-size : medium\"><strong><span style=\"color : #666666\">Your Organizers<br>\n\n</span></strong></span></p>"
+        lon: -122.66999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/8/f/2/600_279831442.jpeg'
+        lat: 45.52000045776367
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/thestartersacademy/'
+        name: "The Starter's Academy"
+        description: "<p><span>Learn how to design, code, and deliver web applications. The Starter's Academy is creating a growing, vibrant community of people with the skills to build the web applications they envision. Our instructors tailor the workshop to your knowledge and goals. We will teach you how to imagine, build, and demo\_minimum viable products. using HTML, CSS, JavaScript, Backbone.js, and Node.js. Learning these skills can help you start a new career, launch a product, or create a company.</span></p>"
+        lon: -117.19999694824219
+        lat: 32.88999938964844
+      - country: US
+        city: San Antonio
+        link: 'http://www.meetup.com/San-Antonio-JavaScript-User-Group/'
+        name: Hill Country JavaScript
+        description: |-
+          <p><span>Hill Country JS is a monthly meetup in San Antonio, Texas. Come to listen to industry leaders, work with other JavaScript enthusiasts &nbsp;and nerd out to the latest in web development. We have members with all sorts of backgrounds and experiences, so no worries if you're new to JavaScript.</span></p>
+          <p>Follow us on <a href="https://twitter.com/hillcountryjs">Twitter</a> for the latest updates. <a href="https://gitter.im/hillcountryjs/contributors">Chat</a> with us.</p>
+          <p>Interested in speaking? <a href="http://goo.gl/forms/js2Y0LYMhj">Submit a proposal</a>!</p>
+        lon: -98.48999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/1/5/a/600_278445402.jpeg'
+        lat: 29.420000076293945
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/the-future-of-software-design-sf/'
+        name: The Future of Software Design - San Francisco Meetup
+        description: "<p><span>Like the tortoise and the hare, software and hardware race ahead at wildly different paces. \_Hardware leaps every 2 years, but the steps into the future of software happen maybe every 20 years.</span> <span>Join us on an adventure to find the little known shortcuts to the future of software design.</span></p>\n<p><span>This Meetup is for designers, developers and innovators who make digital things. \_Come expecting a gamut of the technical, inspirational and the wild.</span> <span>Come nerd-out with us!</span></p>"
+        lon: -122.44000244140625
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/6/4/6/600_269525702.jpeg'
+        lat: 37.779998779296875
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Chicago-Backbone/'
+        name: Chicago Backbone JS
+        description: "<p>A group based on furthering JavaScript and Backbone development in Chicago We focus on web technologies, but won't leave HTML-native mobile or NodeJS spheres out! Come share your experiences, opinions and questions with fellow JS superheroes :)</p>"
+        lon: -87.63999938964844
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/3/6/8/600_292061832.jpeg'
+        lat: 41.880001068115234
+      - country: US
+        city: Nashville
+        link: 'http://www.meetup.com/nashjs/'
+        name: NashJS
+        description: '<p>A group for people interested in software development using Javascript. <a href="http://nashjs.org">http://nashjs.org</a></p>'
+        lon: -86.77999877929688
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/d/9/6/600_277219862.jpeg'
+        lat: 36.16999816894531
+      - country: US
+        city: Atlanta
+        link: 'http://www.meetup.com/meansters/'
+        name: 'Atlanta MEAN (Mongo, Express, Angular, Node) Developers'
+        description: "<p>\_</p>\n<p><img src=\"http://photos4.meetupstatic.com/photos/event/2/e/4/2/event_289871842.jpeg\" style=\"max-height : 700px ; max-width : 700px ; margin : 5px ; float : left\"></p>\n<p>\_</p>\n<p>\_</p>\n<p>\_</p>\n<p>\_</p>\n<p>\_</p>\n<p>\_</p>\n<p>\_</p>\n<p><span>A group for software development professionals, who are interested to exchange ideas and share their experience on application development using MEAN Stack (Mongo, Express, Angular, Node).</span></p>\n<p>\_</p>\n<p>\_</p>"
+        lon: -84.38999938964844
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/1/e/4/600_289872772.jpeg'
+        lat: 33.75
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/nodebots/'
+        name: Nodebots NYC
+        description: |-
+          <p><strong>Nodebots NYC</strong> is a meetup for hardware and javascript enthusiasts and hackers of all skill levels.&nbsp;</p>
+          <p>We run monthly workshops where you can get advice, show off what you're working on, help others, and play with the latest and greatest hardware. Nodebots are by name robots powered by NodeJS and Javascript but often includes software in all languages. They're a great way to learn JavaScript and Hardware concepts.</p>
+          <p><a href="http://johnny-five.io">http://johnny-five.io</a> is a great place to get started if you want to get familiar before an event.&nbsp;</p>
+          <p><span>So come join us and s</span><span>olve a problem, play with hardware or learn something new!</span></p>
+        lon: -74
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/c/4/4/600_278771332.jpeg'
+        lat: 40.720001220703125
+      - country: US
+        city: East Troy
+        link: 'http://www.meetup.com/East-Troy-Computer-Club/'
+        name: East Troy Computer Club
+        description: "<p>The East Troy Computer Club is a community-driven group of all-age, all-skill level tinkerers interested in playing with technology. We meet every other week (or so) over a variety of topics at a cafe on the historic square of East Troy, WI.</p>\n<p>This club is about a year old now. Smaller meetups tend to take on a roudntable discussion format while larger turnouts/topics are more formal in presentation. Feel free to jump in on the conversation, show &amp; tell your latest project or challenge.</p>\n<p>Each meetup will have a theme and loose agenda to guide the group. Some will be geared towards kids, or helping grandparents out with getting their email to work. Others, and likely most consistently, we'll be a group of adults talking mostly about internet and hardware technologies. A little on the advanced side, but what better group of talented folks to serve as a backbone to a club such as this!</p>\n<p>Things we're open to meeting over:</p>\n<p>• Arts &amp; Craft projects utilizing technology.\_<br>\n\n<span>•</span> <span>Robotics. Ardiuno, Raspberry Pi, Tessel hardware projects.\_<br>\n\n•</span> <span>Web development, design, scaling and performance.\_<br>\n\n•</span> <span>Hands-on workshops. Such as 'intro to electronics' for children.\_<br>\n\n•</span> <span>Summer 'bootup camps'—Computer summer camp for kids.\_<br>\n\n•</span> <span>Programming, Unit tests, Development tools and tips.\_<br>\n\n•</span> <span>GNU/Linux, UNIX and general System Administration.\_<br>\n\n•</span> <span>Productivity, Workflow and staying focus.\_<br>\n\n•</span> <span>Collecting/Mining local (meta) data.<br>\n\n•</span> <span>Practicing your presentation skills with us.\_<br>\n\n•</span> <span>Sprints (work on projects together, right then and there).\_<br>\n\n•</span> <span>Tutorials / HOWTO's - An instructor walks the group through a particular topic.\_<br>\n\n•</span> <span>Helping Seniors stay connected.\_<br>\n\n•</span> <span>Sharing tips, tricks and software.</span></p>\n<p><span>As we grow, certain interests or projects may branch out of this club, such as working with the Public Library and other facilities. We also have a GitHub organization; http://github.com/etcc/</span></p>\n<p>We're a patient body of tinkerers invested in local community and set out to foster discovery and education of technology.</p>\n<p>You don't have to be from East Troy to participate. Come on over!</p>"
+        lon: -88.41999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/6/1/7/600_433298423.jpeg'
+        lat: 42.79999923706055
+      - country: US
+        city: Jacksonville
+        link: 'http://www.meetup.com/Jax-Node-js-UG/'
+        name: Jax Node.js UG
+        description: |-
+          <p>Want to learn more about Node.js, a great way of running non-blocking javascript on the server. Join our meetup!</p>
+          <p>Come to our <a href="http://www.jaxnode.com">web site</a>.</p>
+        lon: -81.51000213623047
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/6/b/c/600_287834012.jpeg'
+        lat: 30.309999465942383
+      - country: US
+        city: Denver
+        link: 'http://www.meetup.com/Meteor-Denver/'
+        name: Meteor Denver
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -104.98999786376953
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/c/3/1/600_445115889.jpeg'
+        lat: 39.75
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/causathon/'
+        name: Hack for a Cause
+        description: "<p>A technology enthusiast group comprised of talented product architects, designers and engineers looking to push product in the most efficient and effective way possible. If you enjoy collaborating with like minded individuals to get better and share what you do best, then you're going to find this to be very beneficial.</p> \n<p>Causathon is an event series around the country that brings together developers, designers and marketers for an intensive 24 hour collaboration to produce impactful technology solutions for non-profit organizations.</p>"
+        lon: -118.44999694824219
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/2/c/8/600_434025768.jpeg'
+        lat: 34.040000915527344
+      - country: US
+        city: Columbia
+        link: 'http://www.meetup.com/devcomo/'
+        name: devcomo
+        description: '<p>devcomo is a monthly user group Columbia, MO that is focused on development and design. Simply put, if it is interesting then it’ll be discussed!</p>'
+        lon: -92.31999969482422
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/d/3/0/600_292327472.jpeg'
+        lat: 39
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Real-Estate-Developer-Meetup-Group/'
+        name: Real Estate Developer Meetup Group
+        description: This group is for anyone interested in developing for the real estate field using property listing data. So if you love JS and NodeJS and are interested in creating and talking about open source components lets all connect.
+        lon: -122.41000366210938
+        lat: 37.77000045776367
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/cultivate/'
+        name: Cultivate
+        description: |-
+          <p>Cultivate is for people who love building software - not for software's sake, but for it's ability to create dramatic change in the world. We are designers and developers using our talents to create positive change that benefits our communities, our children and those who come after us.</p>
+          <p>In-person events cover a range of topics and formats. Learn the latest on building web applications with Angular and Node.js. Hack on tools to improve a farmer's productivity. Find a collaborator to work on your next big idea. Regardless of the topic or the format, we guarantee the food will always be great.</p>
+          <p><em><a href="http://www.goodeggs.com">Good Eggs</a> is the sponsor of Cultivate and is a new kind of grocery store where you buy online directly from farmers and foodmakers producing high quality food with integrity. If you believe in our mission to grow and sustain local food systems and think Good Eggs might be the right place for you, <a href="http://www.goodeggs.com/about/jobs">let us know</a>.</em></p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/9/4/2/600_304510562.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: Raleigh
+        link: 'http://www.meetup.com/Triangle-Titanium-Developers/'
+        name: Triangle Titanium Developers
+        description: "The Triangle Titanium Developers' group was created to bring together the Triangle's growing Titanium community. Our goal is to provide the latest information about Titanium and other mobile related technologies while creating opportunities for community members to network."
+        lon: -78.63999938964844
+        lat: 35.77000045776367
+      - country: US
+        city: Charlotte
+        link: 'http://www.meetup.com/Meteor-Charlotte/'
+        name: Meteor Charlotte
+        description: |-
+          <p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>
+          <p>Find us on irc.freenode.net at #meteor-clt</p>
+        lon: -80.79000091552734
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/7/c/2/600_425526082.jpeg'
+        lat: 35.16999816894531
+      - country: US
+        city: Norfolk
+        link: 'http://www.meetup.com/NorfolkJS/'
+        name: Norfolk.js
+        description: '<p>Join us in talking about, brainstorming, and building Javascript tools and applications. See more information at norfolkjs.org or github.com/norfolkjs.</p>'
+        lon: -76.30000305175781
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/5/d/3/600_434126067.jpeg'
+        lat: 36.86000061035156
+      - country: US
+        city: Tampa
+        link: 'http://www.meetup.com/AngularJS-Tampa/'
+        name: AngularJS-Tampa
+        description: |-
+          <p>AngularJS meetup group in Tampa, FL</p>
+          <p>Meetups are held the third Wednesday of every month; the goal is sharing AngularJS knowledge and best-practices; providing a place where people can meet with other AngularJS enthusiasts. We love Angular.</p>
+          <p>Resources:<br>
+
+           <a href="http://www.angularjs.org/" target="_blank" class="linkified">http://www.angularjs.org/</a><br>
+
+           <a href="http://www.youtube.com/angularjs" target="_blank" class="linkified">http://www.youtube.com/angularjs</a></p>
+        lon: -82.51000213623047
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/4/f/0/600_304633552.jpeg'
+        lat: 27.940000534057617
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/codecrewsf/'
+        name: Code Crew San Francisco
+        description: |-
+          <p>Hackers + Designers + Entrepreneurs = Code Crew!</p>
+          <p>Passionate about learning how to code, creating beautiful designs or building the prototype for your business idea and tired of doing it alone? Then this is the group for you!</p>
+          <p>This is the perfect group for people serious about learning how to code through self-study using resources on the web like Code School, Codecademy, Treehouse, P2PU, Coursera, edX, Udacity, programming books, screencasts or whatever else is out there on the internet. We also share a helpful suggested reading on our blog and issue occasional code challenges. If you're just starting out and want to get a head start then check out some cool resources here.</p>
+          <p>We are a group of software engineers, designers and entrepreneurs that enjoy building cool stuff with code at our collaborative coding/pair programming sessions. We currently have members building with HTML, CSS, Javascript, Ruby, Ruby on Rails, Python, Django, PHP, Objective C and more. So come join us and meet some cool and interesting people while picking up a new skill!</p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/9/a/600_337202202.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/CouchDB-Boston/'
+        name: CouchDB™ Boston
+        description: |-
+          <p>Relax, it's CouchDB! CouchDB Boston brings together developers, technologists, and anyone else passionate or curious about CouchDB to swap stories, share projects, code apps, and otherwise relax on the couch. All skill levels are welcome, whether you've got hundreds of nodes replicating petabytes around the world, or just heard about CouchDB when you found this page. Join us for good food, good folks, and good times :D</p>
+          <p>All events organized by this meetup group fall under the <a href="https://couchdb.apache.org/conduct.html">Apache CouchDB™ Code of Conduct and Diversity Statement</a>.<br></p>
+          <p><i>Apache CouchDB™, CouchDB™ and Apache are either registered trademarks or trademarks of the <a href="http://www.apache.org/">Apache Software Foundation</a> in the United States and/or other countries, and are <a href="https://www.apache.org/foundation/marks/events.html#attributions">used with permission</a>. The Apache Software Foundation has no affiliation with and does not endorse, or review the materials provided at this event, which is managed by <a href="http://www.cloudant.com">IBM Cloud Data Services</a>.</i> <br></p>
+        lon: -71.05000305175781
+        lat: 42.369998931884766
+      - country: CA
+        city: Montréal
+        link: 'http://www.meetup.com/js-montreal/'
+        name: "js-montreal - montreal's javascript user group"
+        description: "<p><b>New: Help us make the group better by filling up our <a href=\"https://docs.google.com/forms/d/183axsUpTwtD2sMSSM-QJqN27dmORezX27_Y6Gr36Kbw/viewform\">Yearly Survey</a></b></p>\n<p>Want to learn more about JavaScript? Meet other people who are passionate about writing software? Show off your latest project?<br>\n\n</p>\n<p>We meet on every second tuesday of the month. The details are always available on <a href=\"http://js-montreal.org\">js-montreal.org</a></p>\n<p>Front-end, backend with Node and other tools, other interesting uses for JavaScript: We got you covered.</p>\n<p>If you wish to sponsor one of our events, get in touch. We often do beer + pizza before the meetup and give you a chance to talk about your company and what you're looking for in terms of developers.</p>\n<p>Our goal is to bring the MTL JS development community together and promote the use and understanding of the language, inside and outside the browser. We've been doing this since 2010.\_</p>"
+        lon: -73.58000183105469
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/b/3/2/600_312887922.jpeg'
+        lat: 45.47999954223633
+      - country: US
+        city: Herndon
+        link: 'http://www.meetup.com/NOVA-MEAN/'
+        name: NOVA MEAN
+        description: "<p>Are you developing (or interested in developing) software using MongoDB, Express, AngularJS, and Node.js, but you don't really want to join 3-4 different Meetups to cover these architecture topics? Well that's what we were thinking, so we started a Meetup to cover all of these in one group. We'll have a few Meetups on each topic over the course of the year. \_Together we'll learn ways to develop better enterprise JavaScript solutions.</p>"
+        lon: -77.4000015258789
+        lat: 38.93000030517578
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Node-js-Beer/'
+        name: 'Node.js && Beer'
+        description: Talk about Node.js and drink beer. Or just talk about Node.js. Or just drink beer.
+        lon: -122.41000366210938
+        lat: 37.77000045776367
+      - country: US
+        city: Dallas
+        link: 'http://www.meetup.com/Women-Who-Code-Dallas/'
+        name: Women Who Code Dallas/Ft. Worth
+        description: |-
+          <p>Mission:</p>
+          <p>Women Who Code is a global nonprofit organization dedicated to inspiring women to excel in technology careers by creating a global, connected community of women in technology. The organization tripled in 2013 and has grown to be one of the largest communities of women engineers in the world.</p>
+          <p>Empowerment:</p>
+          <p>Women Who code is a&nbsp;professional community for women in tech.&nbsp;We provide an avenue for women to pursue a career in technology, help them gain new skills and hone existing skills for professional advancement, and foster environments where networking and mentorship are valued.</p>
+          <p>Key Initiatives:</p>
+          <p>Free technical study groups</p>
+          <p>Events featuring influential tech industry experts and investors</p>
+          <p>Hack events</p>
+          <p>Career and leadership development</p>
+          <p>Current and aspiring coders are welcome.&nbsp;</p>
+          <p>Bring your laptop and a friend!&nbsp;</p>
+          <p>Support Women Who Code:</p>
+          <p><a href="http://womenwhocode.com/donate">Donating to Women Who Code</a>, Inc.&nbsp;(#46-4218859) directly impacts our ability to efficiently run this growing organization, helps us produce new programs that will increase our reach, and enables us to expand into new cities around the world ensuring that women and girls everywhere have the opportunity to pursue a career in technology.</p>
+          <p>Women Who Code (WWCode) is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/womenwhocode">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a>&nbsp;|&nbsp;<a href="http://womenwhocode.com/blog">Blog</a></p>
+          <p><a href="https://www.facebook.com/WWCodeDallas"></a></p>
+          <p> <br> </p>
+        lon: -96.80000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/7/a/9/600_431687017.jpeg'
+        lat: 32.790000915527344
+      - country: US
+        city: Oklahoma City
+        link: 'http://www.meetup.com/OKC-js/'
+        name: OKC.js
+        description: '<p>Oklahoma City Javascript User Group The Legend of OKC.js <a href="http://okcjs.com/the-legend-of-okcjs/index.html" class="linkified">http://okcjs.com/the-legend-of-okcjs/index.html</a></p>'
+        lon: -97.5199966430664
+        lat: 35.470001220703125
+      - country: US
+        city: Bend
+        link: 'http://www.meetup.com/Meteor-Bend/'
+        name: Meteor Bend
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -121.29000091552734
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/0/a/600_317163082.jpeg'
+        lat: 44.099998474121094
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/Escape-from-dev-null-Washington/'
+        name: Escape from /dev/null Washington
+        description: "<p>Escape from /dev/null is a silly, creative and challenging series of developer games. Part board-game, part SF/Fantasy narrative, part laidback programming competition. You might like it.</p>\n<p><span>http://swdc.se/devnull</span><br>\n\n</p>\n<p>It's also a bit of a travelling circus with different sponsors each time, like a meetup. The focus is on having fun and solving always new challenges in a variety of live web-based API setups.\_</p>\n<p>OK, so it is of course at its roots a kind of sourcing event where you can show your skills for a sponsors if you care to, but the hat is on the other foot compared to other events of its kind. This is an option for you while you're having fun, nothing else.</p>"
+        lon: -122.33000183105469
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/f/9/0/600_324196272.jpeg'
+        lat: 47.61000061035156
+      - country: CA
+        city: Victoria
+        link: 'http://www.meetup.com/Victoria-NodeJS-Meetup/'
+        name: Victoria NodeJS Meetup
+        description: '<p>All things Node. Packages, patterns, problems, polyfills, prototypes, other things that start with P, including pints.</p>'
+        lon: -123.3499984741211
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/c/6/e/600_327704142.jpeg'
+        lat: 48.439998626708984
+      - country: US
+        city: Saint Louis
+        link: 'http://www.meetup.com/Saint-Louis-Node-js-Meetup/'
+        name: Saint Louis Node.js Meetup
+        description: 'This group is for anyone interesting in Node.js or that is already using it. I started this group to help build the Node.js and back-end JavaScript community. All skill levels are welcome, but bring a positive attitude.'
+        lon: -90.20999908447266
+        lat: 38.630001068115234
+      - country: US
+        city: Denver
+        link: 'http://www.meetup.com/Node-js-Denver-Boulder/'
+        name: Node.js Denver/Boulder/Ft. Collins
+        description: "<p>This is a group for anyone who is currently using or interested in knowing more about Node.js. A great place to meet, interact, and learn with other developers, designers, managers, and like-minded individuals. Come and share your knowledge, applications, roadblocks, and get feedback from others. We'll organize regularly scheduled meetings that will focus on Node.js and many of the associated technologies. About Node.js: Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.</p>"
+        lon: -104.98999786376953
+        lat: 39.75
+      - country: US
+        city: Bothell
+        link: 'http://www.meetup.com/Bothell-Web-Developers-Meetup/'
+        name: Bothell Web Developers Meetup
+        description: "<p>Apply your programming skills to personal projects you want to tackle, share ideas with fellow developers, and deepen your knowledge of web development programming. Whether you are new to the field or have years of experience, we welcome anyone who has a passion to become a better developer and tackle challenging problems. Use this time to focus on your own projects or talk with other developers.\_<span>Please do not use this group to self promote or recruit people for other projects.</span></p>"
+        lon: -122.22000122070312
+        lat: 47.790000915527344
+      - country: US
+        city: Troy
+        link: 'http://www.meetup.com/Node-js-Meetup-12180/'
+        name: 'Node.js Meetup: 12180'
+        description: "We're a group of web developers looking to mix and mingle with other folks leveraging Node.js for new and exciting solutions - all levels are welcome. We're prepared to meet, discuss, lecture, hack and code with this event driven, server-side platform built on V8 and see what we can learn, share & create. supporting technology like client-side JavaScript development & NoSQL data storage is fair game too. We're open to taking the group in any direction the membership wants to go... but yo, we're keeping our base in the 12180: Troy NY"
+        lon: -73.61000061035156
+        lat: 42.7400016784668
+      - country: US
+        city: Jackson
+        link: 'http://www.meetup.com/Jackson-Hole-Tech-Meetup/'
+        name: Jackson Hole Tech Meetup
+        description: "<p>Jackson Hole's first tech meetup. This is a group for programmers, designers, entrepreneurs and anyone interested in software development in beautiful Jackson Hole, Wy. This group will cover deep technical topics w/ guest speakers giving short presentations at each meetup. The group will meet at Jackson's newest coworking community, Spark Jackson Hole (sparkjh.com).</p>"
+        lon: -110.7699966430664
+        lat: 43.470001220703125
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/codefellows/'
+        name: Code Fellows Seattle Meetup
+        description: "<p>Code Fellows offers full-time and part-time programs to train software developers at every experience level. We strongly believe in the power of community and want to contribute in any way we can. Whether you're just starting out or have been a coding for years, come join us!</p>"
+        lon: -122.33999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/7/4/6/600_334882342.jpeg'
+        lat: 47.630001068115234
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/San-Francisco-JS-Breakfast/'
+        name: San Francisco JS Breakfast
+        description: 'Meet other JS developers and learn more about your favorite language, all before 10am.'
+        lon: -122.4000015258789
+        lat: 37.79999923706055
+      - country: CA
+        city: Kingston
+        link: 'http://www.meetup.com/Kingston-Developers/'
+        name: Kingston Developers
+        description: '<p>This is a group for anyone interested in developing for the web and web apps The main focus is on HTML, CSS and JavaScript but there is major cross over with many other domains such as PHP, R, Python, SQL etc. All skill levels are welcome. I started this group to meet other people who want to exchange ideas, tips, tricks, troubleshoot and work on solving problems through the web, and maybe start a business along the way. We hope to meet weekly or bi-weekly and sometimes for weekend hack-a-thons.</p>'
+        lon: -76.4800033569336
+        lat: 44.22999954223633
+      - country: US
+        city: Durham
+        link: 'http://www.meetup.com/Stacked/'
+        name: 'Stacked! Building Better Developers'
+        description: |-
+          <p>Stacked! is a Meetup group for anyone passionate about technology and dedicated to lifelong learning. And, while many of our talks lean towards advanced topics, we strongly encourage those newer to programming (as well as non-programmers with an interest in technology) to attend.&nbsp;</p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p>Our events typically begin with some time for networking and a bite to eat followed by back-to-back speakers or a series of lightening talks. We place a heavy emphasis on selecting speakers who are passionate and engaging as well as creating a&nbsp;<a href="http://www.meetup.com/Stacked/pages/Stacked%21_Code_of_Conduct/">warm and welcoming environment</a><span>&nbsp;for programmers and non-programmers alike.&nbsp;</span></p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p>At the end of the day, this group is about learning, meeting new people, discussing technology, and having a good time. Stacked! is powered by&nbsp;<a href="http://www.smashingboxes.com/">Smashing Boxes</a><span>.&nbsp;</span></p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p>P.S. We're planning Durham's first developer conference for Spring 2015!</p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p>Ideas? Suggestions? Whispers of endearment? Tweet us&nbsp;<a href="https://twitter.com/stackedtriangle">@StackedTriangle</a></p>
+        lon: -78.9000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/0/6/c/600_371097452.jpeg'
+        lat: 36
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Toronto-Ember-JS-Meetup/'
+        name: Toronto Ember.js Meetup
+        description: "<p>We're a merry, nomadic gang of Ember enthusiasts led by Unspace and Discourse that get together for presentations and socialize, typically on the first Thursday of every month.\_</p>\n<p>To stay abreast on all the updates and special goings-on in the Toronto Ember community, we suggest you sign up for our mailing list: <a href=\"http://torontoemberjs.com/\" target=\"_blank\" class=\"linkified\">http://torontoemberjs.com</a></p>\n<p><span>The format is pretty simple: we'll start with a short presentation about something Ember related (FYI, we welcome any talk submissions to line up for future events). Then people can ask questions, talk to each other and discuss all things Ember in a fun environment (usually Unspace or Pharmacy Bar) with lovely sponsors usually picking up the tab.</span></p>"
+        lon: -79.43000030517578
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/a/9/e/600_332859582.jpeg'
+        lat: 43.65999984741211
+      - country: US
+        city: Stanford
+        link: 'http://www.meetup.com/South-Bay-Hackathons/'
+        name: South Bay Hackathons
+        description: "<p>For anyone who loves to create.\_</p>\n<p>We will be hosting regular hackathons where you can come and meet other awesome developers and work on cool projects with them!</p>\n<p>South Bay Hackathons!</p>"
+        lon: -122.16000366210938
+        lat: 37.41999816894531
+      - country: US
+        city: Tallahassee
+        link: 'http://www.meetup.com/TallyJS/'
+        name: TallyJS
+        description: "TallyJS is a group focused on JavaScript and related topics. Let's meet up to discuss and learn about new JavaScript frameworks and best practices. Whether you use JS for your job or you're completely new to javascript, this meetup can help you build more dynamic and interesting things on the web. Come out and help build the javascript community in Tallahassee!"
+        lon: -84.31999969482422
+        lat: 30.479999542236328
+      - country: US
+        city: Princeton
+        link: 'http://www.meetup.com/javaScript-io/'
+        name: javaScript.io
+        description: '<p>Have you ever shut off your MacBook Pro at the end of the day only to encounter a world of family, friends, bartenders and manicurists who’s eyes glaze over when you attempt to share your passion for JavaScript? If so, despair no longer. javaScript.io is a place where you can come to meet like minded, savants who live or work near Princeton, NJ, and discuss frameworks, design patterns, and interesting applications of this delightfully versatile language. NOTE: If the phrase “prototypical inheritance” is something you feel should be discussed with an accountant or lawyer, this is probably not the meetup for you.</p>'
+        lon: -74.66999816894531
+        lat: 40.369998931884766
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/MEAN-Stack-NYC/'
+        name: 'MEAN (MongoDB, Express, AngularJS, Node.js) Stack NYC'
+        description: |-
+          <p><span>This group is for anyone interested in learning more about building web applications with the MEAN (MongoDB, Express, AngularJS, Node.js) Stack. Experts and the curious are welcome to join!</span> <br> </p>
+          <p><b>Resources:</b> <br> <a href="http://www.mean.io/#!/">mean.io</a> <br> <a href="http://www.mongodb.org/">MongoDB</a>&nbsp;| <a href="http://mongoosejs.com/">Mongoose</a> <br> <a href="http://expressjs.com/">Express</a> <br> <a href="http://angularjs.org/">AngularJS</a> <br> <a href="http://nodejs.org/">Node.js</a></p>
+          <p><a href="http://www.ibm.com/developerworks/library/wa-nodejs-polling-app/">Build a Real-time Polls Application with Node.js, Express, AngularJS and MongoDB</a> (IBM Tutorial)</p>
+          <p> <br> </p>
+        lon: -73.94000244140625
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/d/2/2/600_446324322.jpeg'
+        lat: 40.810001373291016
+      - country: US
+        city: Pittsburgh
+        link: 'http://www.meetup.com/Angular-js-Pittsburgh/'
+        name: ngPittsburgh
+        description: "<p>Angular is a superheroic JavaScript 'Model View Whatever' framework. If you're looking for an alternative to writing unmaintainable and buggy jQuery spaghetti code come on down and give Angular.js a try!</p>"
+        lon: -79.98999786376953
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/8/7/f/600_443238559.jpeg'
+        lat: 40.45000076293945
+      - country: US
+        city: Cambridge
+        link: 'http://www.meetup.com/Firebase-Cambridge/'
+        name: Firebase Cambridge Meetup
+        description: "<p>This group is to learn about using Firebase in web and mobile application development. The point of this group is to help each other progress in our projects, not to just sit back and listen to guest speakers.</p>\n<p>Firebase is a powerful API to store and sync data in realtime and has full-featured libraries\_for all major web and mobile platforms\_and bindings for the most popular frameworks.</p>\n<p>We will have speakers, demos, lightning talks, workshops and socializing to help connect our members and help each other.\_</p>\n<p>Come brainstorm ideas, share insights, and exchange feedback on your apps, and most of all, make progress.<br>\n\n</p>\n<p><br>\n\n</p>\n<p>@FirebaseCamb is our twitter handle.</p>"
+        lon: -71.12999725341797
+        lat: 42.380001068115234
+      - country: US
+        city: Colorado Springs
+        link: 'http://www.meetup.com/coloradospringsjs/'
+        name: coloradoSprings.js (JavaScript User Group)
+        description: |-
+          <p>This is a group for people who work with JavaScript on a professional level or hobbyists who hack in their spare time. We're looking for people who know JavaScript and want to learn and share their knowledge alike. Topics at meetups should be anything that is even remotely JavaScript related, from web development to hardware hacking.</p>
+          <p> <br> </p>
+          <p><span>Join us in&nbsp;</span><span>#coloradoSprings.js on <a>freenode</a>!&nbsp;</span></p>
+          <p><span>Wiki:&nbsp;<a href="https://hackpad.com/collection/E9kKDGDJ9Uu" class="linkified">https://hackpad.com/collection/E9kKDGDJ9Uu</a></span></p>
+          <p>Code:&nbsp;<a href="https://github.com/coloradoSpringsJS" class="linkified">https://github.com/coloradoSpringsJS</a></p>
+          <p>Website:&nbsp;<a href="http://coloradospringsjs.org">http://coloradospringsjs.org</a></p>
+        lon: -104.81999969482422
+        lat: 38.83000183105469
+      - country: US
+        city: Boulder
+        link: 'http://www.meetup.com/Full-Stack-Boulder/'
+        name: Full Stack Boulder
+        description: "<p>A group for web professionals and newbies. From rich client user interfaces to multi cluster server deployments. Let's explore together what the web technologies have to offer.</p>"
+        lon: -105.30999755859375
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/9/d/2/600_341395762.jpeg'
+        lat: 40.040000915527344
+      - country: US
+        city: San Luis Obispo
+        link: 'http://www.meetup.com/codeslo/'
+        name: CodeSLO
+        description: '<p>CodeSLO is a place for learning to code, and for helping others to learn. We offer free coding classes for anyone who wants to learn, and we meet multiple times per month. To learn more about what we do and why we do it, visit our website at www.codeslo.com.</p>'
+        lon: -120.6500015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/b/6/5/600_436196165.jpeg'
+        lat: 35.2599983215332
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/WomenWhoCodeNYC/'
+        name: Women Who Code NYC
+        description: |-
+          <p>Mission:</p>
+          <p>Women Who Code is a global nonprofit organization dedicated to inspiring women to excel in technology careers by creating a global, connected community of women in technology. The organization tripled in 2013 and has grown to be one of the largest communities of women engineers in the world.</p>
+          <p>Empowerment:</p>
+          <p>Women Who code is a&nbsp;professional community for women in tech.&nbsp;We provide an avenue for women to pursue a career in technology, help them gain new skills and hone existing skills for professional advancement, and foster environments where networking and mentorship are valued.</p>
+          <p>Key Initiatives:</p>
+          <p>Free technical study groups</p>
+          <p>Events featuring influential tech industry experts and investors</p>
+          <p>Hack events</p>
+          <p>Career and leadership development</p>
+          <p>Current and aspiring coders are welcome.&nbsp;</p>
+          <p>Bring your laptop and a friend!&nbsp;</p>
+          <p>Support Women Who Code:</p>
+          <p><a href="http://womenwhocode.com/donate">Donating to Women Who Code</a>, Inc.&nbsp;(#46-4218859) directly impacts our ability to efficiently run this growing organization, helps us produce new programs that will increase our reach, and enables us to expand into new cities around the world ensuring that women and girls everywhere have the opportunity to pursue a career in technology.</p>
+          <p>Women Who Code (WWCode) is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/womenwhocode">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a></p>
+        lon: -74
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/b/8/0/600_446191616.jpeg'
+        lat: 40.7400016784668
+      - country: US
+        city: Bismarck
+        link: 'http://www.meetup.com/DakotaJS/'
+        name: DakotaJS
+        description: "We're a group of JavaScript enthusiasts that get together to learn from each other and talk about the latest in the world of JavaScript."
+        lon: -100.77999877929688
+        lat: 46.81999969482422
+      - country: US
+        city: Manchester
+        link: 'http://www.meetup.com/Front-End-Rally/'
+        name: Front End Rally
+        description: 'The web is rapidly changing. New standards, technology and techniques are being created daily; making it difficult to stay on top of your game. The Front End Rally is a community of Professional Front End Developers and enthusiasts dedicated to meeting, talking and sharing ideas about the latest and greatest technology, techniques and workflows together.'
+        lon: -71.44999694824219
+        lat: 43
+      - country: US
+        city: Tampa
+        link: 'http://www.meetup.com/tampa-nodejs/'
+        name: Tampa NodeJS
+        description: "<p>The purpose of Tampa NodeJS is to bring together developers that are interested in learning more about Node.js and all things related. This group is open to anyone that's interested, no experience necessary, if you want to learn more about Node or you want to share your knowledge then please join us!</p>"
+        lon: -82.45999908447266
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/6/5/e/c/600_402806092.jpeg'
+        lat: 27.959999084472656
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Famo-us-Hacking-Meetup-in-San-Francisco/'
+        name: Famo.us Hacking Meetup in San Francisco
+        description: 'An unofficial hackers group for those interested in learning about and building apps with Famo.us, a JavaScript platform that enables engineers to build beautiful, cross-platform web apps that perform as well as the very best native apps.'
+        lon: -122.44000244140625
+        lat: 37.7599983215332
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/Silicon-Valley-EmberJS-Meetup/'
+        name: Silicon Valley Ember.js Meetup
+        lon: -122.08000183105469
+        lat: 37.40999984741211
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/Future-of-Technology-in-Education-at-Cengage-Learning/'
+        name: Future of Technology in Education at Cengage Learning
+        description: "Want to learn future of technology in Education Industry and learn how you could help? Cengage Learning would like to invite you on Monday, April 28th from 6:00pm - 8:30pm at 10 Channel Center, 3rd Floor South Boston. (10 Channel Center is on A Street in South Boston, 500 feet to the right of Barlow's Restaurant), to share how Education Industry is transforming in this age of data &amp; analytics. Cengage will share the vision of the future of technology in the Education industry, product &amp; technology roadmap over the next several years and corporate culture &amp; environment. This event will be a fast-track ride into the world of education as seen by Cengage. Come and join the discussion. The following agenda is planned for the evening: 6:00pm - 6:30pm: Registration &amp; Conversation 6:30pm - 6:50pm: George Moore, Chief Technology Officer - Mr. Moore will be providing his perspective on the trends in the Education Industry and how technology will play a significant role in defining and shaping the future of how students learning activities will be changing and how learning institutions will adapt over time 6:50pm - 7:10pm: Doug Mealing, Chief Architect - Mr. Mealing will be describing the current technology landscape at Cengage Learning and the challenges it faces and the direction of its enterprise architecture and frameworks 7:10pm - 7:30pm: Ryan Martin, Principal Architect/Designer - Mr. Martin will portray what it's like to be a technologist in Cengage's environment and the culture of the organization 7:30pm - 8:30pm: Q&amp;A Open Discussion Please RSVP, and looking forward to seeing you all at the event."
+        lon: -71.05000305175781
+        lat: 42.36000061035156
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/seattlejshackers/'
+        name: SeattleJS Hackers
+        description: |-
+          <p><b>Seattle JS Hackers</b> is an open and inclusive after-hours community of JavaScript hackers who learn and hack in JavaScript together.&nbsp;<span>We are entrepreneurs, creatives, professionals, tinkerers, computer scientists, educators,&nbsp;marketers, and more -- all working to ignite and amplify our personal productivity and collaboration.</span></p>
+          <p><b>How we do it:</b> We organize hacking sessions at WiFi-ready offices, cafes and&nbsp;bars around Seattle each week. Our hacking sessions encourage peer ideation and review, knowledge sharing, new champions for causes and projects, personal productivity, and a heightened sense of community.</p>
+          <p><span>If you want to to learn and hack with together, come join us!</span><br></p>
+        lon: -122.33000183105469
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/5/1/9/600_443266361.jpeg'
+        lat: 47.61000061035156
+      - country: US
+        city: Boise
+        link: 'http://www.meetup.com/frontend-devs/'
+        name: Frontend Development
+        description: |-
+          <p>Front end technologies, tools, processes and the way it interacts with other tiers.</p>
+          <p>We got great talent looking forward to share their expertise on AngularJS, React, Swift, ExtJS, etc</p>
+          <p>Come and make the difference!</p>
+        lon: -116.20999908447266
+        lat: 43.630001068115234
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/MEAN-SF-Developers/'
+        name: MEAN SF Developers
+        description: "We are MEAN (MongoDB, Express, AngularJS and Node.js) developers. We love the stack, love to share and learn together. We'll have social events, to-the-point-presentations and hacking nights. All levels welcome. ...to get started: http://meanjs.org"
+        lon: -122.41999816894531
+        lat: 37.75
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/RethinkDB-Bay-Area-Meetup-Group/'
+        name: RethinkDB Bay Area Group
+        description: "<p>Welcome to the official RethinkDB Bay Area meetup group!\_<span>RethinkDB is an open-source, distributed database, built to store JSON documents at scale.</span></p>\n<p>Come meet the RethinkDB team, learn how to build better apps with existing and upcoming features, and get one-on-one support from fellow RethinkDB users and makers at the office hours.</p>\n<p>Let's learn, teach, and build software together!</p>"
+        lon: -122.06999969482422
+        lat: 37.38999938964844
+      - country: US
+        city: Lakewood
+        link: 'http://www.meetup.com/Lakewood-Software-Developers/'
+        name: Lakewood Software Developers
+        description: '<p>This is a meetup for frum web developers from the Lakewood community interested in learning, discussing and showcasing the latest web related tools and technologies. All skill levels are welcome. We hope to meet once a month.</p>'
+        lon: -74.19999694824219
+        lat: 40.08000183105469
+      - country: US
+        city: Grand Rapids
+        link: 'http://www.meetup.com/GRNodeDev/'
+        name: GrNodeDev
+        description: |-
+          <p>We're a group of developers that are experimenting with and are using Node.js for web and app development.</p>
+          <p>Our goal is to explore the platform, to share what we're learning with others, and to meet others that are interested in Node.js.</p>
+          <p>Whether you're using Node.js in several projects or have just heard about it and want to learn more, we'd love to chat.</p>
+        lon: -85.52999877929688
+        lat: 42.93000030517578
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/Yahoo-Tech-Talks/'
+        name: Yahoo Tech Talks - NYC
+        description: |-
+          <p><i><b></b></i></p>
+          <p> </p>
+          <p><i><b>Looking for a Mobile Tech Talk series in NYC that covers, not only iOS and Android development, but mobile backends, performance at scale, quality engineering and mobile design?&nbsp;</b></i></p>
+          <p> </p>
+          <p>Whether you are a designer, mobile programmer, or backend engineer, or full-stack developer, we think you will want to attend this series of multi-platform NYC Tech Talks, sponsored by Yahoo.&nbsp;</p>
+          <p> </p>
+          <p>•&nbsp;Native development,&nbsp;•&nbsp;UI/UX,&nbsp;• Architecture,&nbsp;• Graphics,&nbsp;•&nbsp;Serving at scale,&nbsp;•&nbsp;Cross-platform technologies and more...</p>
+          <p> </p>
+          <p>Hope to see you soon! =)</p>
+          <p> </p>
+          <p> <br> </p>
+          <p> </p>
+          <p><img src="http://photos3.meetupstatic.com/photos/event/c/f/9/2/600_434273138.jpeg"></p>
+          <p> </p>
+          <p></p>
+        lon: -73.98999786376953
+        lat: 40.7599983215332
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/ReactJS-San-Francisco/'
+        name: ReactJS San Francisco Bay Area meetup
+        description: |-
+          <p>ReactJs is a fun, easy to use Javascript library started by Facebook and maintained by *you*.</p>
+          <p><a href="http://facebook.github.io/react/">http://facebook.github.io/react/</a></p>
+          <p>ReactJs is crazy easy to get started and so fun once you get going. &nbsp;</p>
+          <p>Join us if you'd like to learn more or if you have your own ReactJs experience to share that others can benefit from.</p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/d/8/a/600_361668522.jpeg'
+        lat: 37.79999923706055
+      - country: US
+        city: Sunnyvale
+        link: 'http://www.meetup.com/Women-Who-Code-Silicon-Valley/'
+        name: Women Who Code Silicon Valley
+        description: |-
+          <p>Mission:</p>
+          <p>Women Who Code is a global nonprofit organization dedicated to inspiring women to excel in technology careers by creating a global, connected community of women in technology. The organization tripled in 2013 and has grown to be one of the largest communities of women engineers in the world.</p>
+          <p>Empowerment:</p>
+          <p>Women Who code is a&nbsp;professional community for women in tech.&nbsp;We provide an avenue for women to pursue a career in technology, help them gain new skills and hone existing skills for professional advancement, and foster environments where networking and mentorship are valued.</p>
+          <p>Key Initiatives:</p>
+          <p>Free technical study groups</p>
+          <p>Events featuring influential tech industry experts and investors</p>
+          <p>Hack events</p>
+          <p>Career and leadership development</p>
+          <p>Current and aspiring coders are welcome.&nbsp;</p>
+          <p>Bring your laptop and a friend!&nbsp;</p>
+          <p>Support Women Who Code:</p>
+          <p><a href="http://womenwhocode.com/donate">Donating to Women Who Code</a>, Inc.&nbsp;(#46-4218859) directly impacts our ability to efficiently run this growing organization, helps us produce new programs that will increase our reach, and enables us to expand into new cities around the world ensuring that women and girls everywhere have the opportunity to pursue a career in technology.</p>
+          <p>Women Who Code (WWCode) is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/womenwhocode">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a></p>
+          <br>
+        lon: -122.01000213623047
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/9/1/3/600_431687379.jpeg'
+        lat: 37.400001525878906
+      - country: US
+        city: Johnson City
+        link: 'http://www.meetup.com/Tri-JS/'
+        name: TriJS
+        description: "<p>PHP, .NET, Java, Ruby/Rails, Node.JS, Python/Django. No matter what kind of web developer you are, you're using JavaScript. This group is dedicated to the language that brings us all together - the world's most popular language and the world's most horribly used. We'll talk JavaScript, Angular.JS, jQuery, Node.JS and more.</p>"
+        lon: -82.37999725341797
+        lat: 36.310001373291016
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/JS-Code-Club/'
+        name: JS Code Club
+        description: |-
+          <p><span>The JS Code Club is a group of people that come together to hack on anything with JavaScript. The group will help motivate you to start on your ideas, and help you along the way. Bring your ideas, pair with other developers, and start building!</span> <br> </p>
+          <p>JS Code Club is open to all. If you are a seasoned developer or just starting out, and have an interest in JavaScript, join the club!</p>
+          <p> <br> </p>
+        lon: -79.38999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/c/0/600_444300704.jpeg'
+        lat: 43.650001525878906
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/init-developer/'
+        name: init developer
+        description: |-
+          <p>We're a group dedicated to helping new software developers get started. We welcome mentors, educators, software developers of all skill levels, and companies interested in hiring new developers for internships, apprenticeships, first-hires, or junior roles.</p>
+          <p>As mentors, instructors and educators, how do we develop curricula that gets developers ready for software development? How do we test and iterate?</p>
+          <p>As software developers and architects, how do we write codebases that are straightforward and clean? How do we best optimize for productivity from newer developers?</p>
+          <p>As newer software developers, how do we filter out the noise? How do we find career coaching and mentorship? How do we move from a structured learning environment to a self-taught one?</p>
+          <p>There are a lot of people in the software community in NYC who want to help new developers succeed. That's our goal.</p>
+          <p>We'll be hosting roundtable discussions, planning sessions, and other, more tech-focused events.</p>
+        lon: -73.98999786376953
+        lat: 40.720001220703125
+      - country: US
+        city: Orlando
+        link: 'http://www.meetup.com/OrlandoJS/'
+        name: OrlandoJS
+        description: The Orlando JavaScript group is a place to talk about all things JavaScript.
+        lon: -81.37000274658203
+        lat: 28.540000915527344
+      - country: US
+        city: Nashville
+        link: 'http://www.meetup.com/Nashville-MEAN-Stack-Development-Meetup/'
+        name: Nashville MEAN Stack Development Meetup
+        description: '<p>A group for anyone interested in the MEAN stack, Javascript,&nbsp; Node.js, Javascript frameworks, AngularJS, Express and related tools. <br></p>'
+        lon: -86.95999908447266
+        lat: 36.060001373291016
+      - country: US
+        city: East Lansing
+        link: 'http://www.meetup.com/Lansing-Javascript-Meetup/'
+        name: Lansing Javascript Meetup
+        description: "<p>Calling all Lansing area Javascript enthusiasts (or those who might like to be)! The Lansing Javascript Meetup is a group dedicated to growing the Javascript and startup community in the Mid-Michigan area. Meetups try to include stuff for beginners, as well as more advanced topics for experienced developers. We're all learning (and we were all 'noobs' once!), so don't be shy about attending, regardless of your experience level. Just come, hang out, eat, drink, meet, and learn. It's free. It's fun. It's Javascript.</p>"
+        lon: -84.47000122070312
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/3/7/8/600_437661368.jpeg'
+        lat: 42.75
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Reactive-TO/'
+        name: Reactive Programming Toronto
+        description: "<p><b>Reactive</b> is an emerging paradigm to help define and create the next generation of applications.\_</p>\n<p><span><i>Reactive applications:\_</i></span></p>\n<p>•\_<span>React to events</span></p>\n<p><span>•\_React to load</span></p>\n<p>•\_<span>React to failure</span></p>\n<p><span>•\_React to users</span></p>\n<p><a href=\"http://www.reactivemanifesto.org\" target=\"_blank\" class=\"linkified\">http://www.reactivemanifesto.org</a></p>\n<p>Reactive is language agnostic. If you have suggestions please get in touch!</p>\n<p>Visit <a href=\"http://reactiveto.com\" class=\"linkified\">http://reactiveto.com</a> for more details.</p>"
+        lon: -79.4000015258789
+        lat: 43.63999938964844
+      - country: US
+        city: Las Vegas
+        link: 'http://www.meetup.com/Las-Vegas-Virtual-Reality-Meetup/'
+        name: Virtual Reality Las Vegas Meetup
+        description: '<p>Virtual Reality Las Vegas Meetup is building a local community of VR enthusiasts. The Oculus Rift is an easy to use new development platform that allows you to experience VR and create it as well. Everyone is welcome: Engineers, Designers, Game Developers, Entrepreneurs, and VR fans. We will have demos, presentations, speakers, and educational sessions. We will also conduct Hackathons with Oculus Dev Kits. Share, Learn, Experience the future... Today!</p>'
+        lon: -115.20999908447266
+        lat: 36.08000183105469
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/NodeDTLA/'
+        name: Node.DTLA
+        description: "<p>Node.DTLA is a community for dreamers, builders, and JavaScript programmers. \_Come explore projects, learnings, and the future of new technologies. \_We're based in Downtown LA and encourage anyone and everyone to join our events!</p>"
+        lon: -118.23999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/e/e/c/600_432076108.jpeg'
+        lat: 34.04999923706055
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/southbayjs/'
+        name: South Bay JavaScript Meetup
+        description: '<p>A group dedicated to sharing knowledge through promoting software development best practices. Sessions will cover a range of technologies and languages, primarily related to building software and systems on the web.</p>'
+        lon: -122.06999969482422
+        lat: 37.38999938964844
+      - country: US
+        city: Minneapolis
+        link: 'http://www.meetup.com/Skyway-Software-Symposium/'
+        name: Skyway Software Symposium
+        description: '<p>We are a group of software engineers that meet monthly (or so) to discuss new software platforms, trends and lessons learned in our respective professional settings.</p>'
+        lon: -93.27999877929688
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/e/a/2/600_371527842.jpeg'
+        lat: 44.970001220703125
+      - country: US
+        city: Miami
+        link: 'http://www.meetup.com/Miami-node-js-Meetup/'
+        name: Miami node.js Meetup
+        description: This is a group for software developers using node.js and Javascript in general. We plan to meet once a month around downtown Miami.
+        lon: -80.19000244140625
+        lat: 25.770000457763672
+      - country: US
+        city: Las Vegas
+        link: 'http://www.meetup.com/Meteor-Las-Vegas/'
+        name: Meteor Las Vegas
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -115.13999938964844
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/9/8/600_411602712.jpeg'
+        lat: 36.09000015258789
+      - country: US
+        city: Columbia
+        link: 'http://www.meetup.com/Maryland-Javascript-Meetup/'
+        name: Maryland Javascript Meetup
+        description: "<p>This is a group for Maryland Javascript developers. Whether it's AngularJS, NodeJS, or just plain vanilla Javascript, we'll discuss and present about best practices and the latest trends in Web Development. Join this group &amp; follow <a href=\"https://twitter.com/JsMaryland\" target=\"_blank\" class=\"linkified\">https://twitter.com/JsMaryland</a> for updates, and reach out if you have a great idea for a presentation topic!</p>"
+        lon: -76.83000183105469
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/1/9/0/600_373868592.jpeg'
+        lat: 39.20000076293945
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/Women-Who-Code-Portland/'
+        name: Women Who Code Portland
+        description: |-
+          <p><b>Mission:</b></p>
+          <p>Women Who Code is a global nonprofit organization dedicated to inspiring women to excel in technology careers by creating a global, connected community of women in technology. The organization tripled in 2013 and has grown to be one of the largest communities of women engineers in the world.</p>
+          <p><b>Empowerment:</b></p>
+          <p>Women Who code is a&nbsp;professional community for women in tech.&nbsp;We provide an avenue for women to pursue a career in technology, help them gain new skills and hone existing skills for professional advancement, and foster environments where networking and mentorship are valued.</p>
+          <p><b>Key Initiatives:</b></p>
+          <p>•&nbsp;Free technical study groups</p>
+          <p>•&nbsp;Events featuring influential tech industry experts and investors</p>
+          <p>•&nbsp;Hack events</p>
+          <p>•&nbsp;Career and leadership development</p>
+          <p><b>Current and aspiring coders are welcome.&nbsp;</b></p>
+          <p><span>Bring your laptop and a friend!&nbsp;</span></p>
+          <p><b>Support Women Who Code:</b></p>
+          <p><a href="http://womenwhocode.com/donate">Donating to Women Who Code</a>, Inc.&nbsp;(#46-4218859) directly impacts our ability to efficiently run this growing organization, helps us produce new programs that will increase our reach, and enables us to expand into new cities around the world ensuring that women and girls everywhere have the opportunity to pursue a career in technology.</p>
+          <p><b>Women Who Code (WWCode)</b> is dedicated to providing an empowering experience for everyone who participates in or supports our community, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, ethnicity, age, religion, or socioeconomic status. Because we value the safety and security of our members and strive to have an inclusive community, we do not tolerate harassment of members or event participants in any form. Our&nbsp;<a href="https://github.com/WomenWhoCode/guidelines-resources/blob/master/code_of_conduct.md">Code of Conduct</a>&nbsp;applies to all events run by Women Who Code, Inc. If you would like to report an incident or contact our leadership team, please submit an&nbsp;<a href="https://docs.google.com/forms/d/1NuBY_E2DcuJx2wtKFXyS5ZY5zZlql4jcZJqsf0sAs-0/viewform">incident report form</a>.</p>
+          <p><a href="http://womenwhocode.com/">WomenWhoCode.com</a></p>
+          <p><a href="http://twitter.com/wwcodeportland">Twitter</a>&nbsp;|&nbsp;<a href="http://fb.com/womenwhocode">Facebook</a>&nbsp;|&nbsp;<a href="http://womenwhocode.com/blog">Blog</a></p>
+          <br>
+          <p><a href="http://fb.com/womenwhocode"></a></p>
+        lon: -122.66999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/6/c/9/600_446262697.jpeg'
+        lat: 45.52000045776367
+      - country: US
+        city: Katy
+        link: 'http://www.meetup.com/LearnerJs/'
+        name: LearnerJs
+        description: A JavaScript fundamentals user group in Houston Tx. A Part of the HoustonJS group.
+        lon: -95.80999755859375
+        lat: 29.75
+      - country: US
+        city: Playa del Rey
+        link: 'http://www.meetup.com/LA-Front-End/'
+        name: 'LA Front-End Developers: Client-Side Sorcery'
+        description: "<p>LA Front-End Developers is a haven for front-end engineers, designers, and server-side gurus looking to expand into the client. If you go home at night and ember.js, angular.js, Swift, d3.js or backbone.js code haunts your dreams, you have come to the right place.\_We're focused on presentations, demos and groups of people collaborating to create the best possible UX engineering and data visualization design experiences. Let's do this!</p>"
+        lon: -118.45999908447266
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/e/4/4/600_377004132.jpeg'
+        lat: 33.9900016784668
+      - country: US
+        city: Chattanooga
+        link: 'http://www.meetup.com/Meteor-Chattanooga/'
+        name: Meteor Chattanooga
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -85.37000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/6/c/8/600_438218600.jpeg'
+        lat: 35.029998779296875
+      - country: US
+        city: Astoria
+        link: 'http://www.meetup.com/QueensJS/'
+        name: QueensJS
+        description: |-
+          <p>Do you have a love for JavaScript? Do you want to hear people talk about JavaScript? Do you want to converse with others who know or are learning… JavaScript? Then Queens JS is the place for you! On the first Wednesday of every month, programmers from all over New York City gather in New York’s largest borough to discuss the passions and pitfalls of the language that is everywhere, JavaScript.</p>
+          <p>Interested in being a sponsor? Want to give a talk? Email us at <b>organizers at queensjs dot com</b>!</p>
+          <p>Queens JS expects all speakers and attendees to follow the <a href="http://jsconf.com/codeofconduct.html">JSConf code of conduct</a>.</p>
+          <p> <br> </p>
+          <p><b>Admission:</b> $5. <i>All proceeds go towards charities that work to increase code literacy among NYC youth.</i></p>
+          <p><b>Meetup Structure:</b> <span>Three, 20 minute talks</span></p>
+        lon: -73.93000030517578
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/4/0/e/600_392597422.jpeg'
+        lat: 40.7599983215332
+      - country: US
+        city: Santa Cruz
+        link: 'http://www.meetup.com/santacruzjs/'
+        name: Santa Cruz JavaScript
+        description: "<blockquote> \n <p>We are an open group with meetups that can be presentations on a topic or informal hack/code/chat sessions.</p> \n <p>We accommodate all experience levels through a variety of events.</p> \n <p>For our hack/code/chat sessions: just show up, find an allocated table, sit with unfamiliar or familiar faces, introduce yourself, and do whatever you feel like in the JS-inspired environment. You most likely will learn something new with JS (framework, library, debugging strategies, etc.), meet cool people, get some stuff done, showcase some cool work you've done, or get help on some of your project.</p> \n</blockquote>"
+        lon: -122.05999755859375
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/f/0/e/600_403576142.jpeg'
+        lat: 36.9900016784668
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/NYC-Real-Time-Computing-NYCRTC/'
+        name: NYC Real-Time Computing (NYCRTC)
+        description: 'Web APIs such as MediaStream, DataChannel, and PeerConnection will change the way we build web applications. Come to share ideas, projects or learn about the upcoming real-time technologies that will revolutionize the web.'
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/8/e/2/600_380575522.jpeg'
+        lat: 40.7599983215332
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/nycgolang/'
+        name: NYC Golang
+        description: |-
+          <p>Our group is for true Go developers and enthusiasts. Join us every month to connect with the local NYC community of Go engineers. We will meet to share insight and listen to guest speakers on Go related topics.</p>
+          <p>New to Go? Ask questions and discuss technical topics with the rest of the community at the beginning of each meetup. Attending monthly meetups will help you get motivated and stay focused on your path to mastering Go!</p>
+        lon: -74
+        lat: 40.7400016784668
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/Meteor-San-Diego/'
+        name: Meteor San Diego
+        description: "<p>Meet other developers using <a href=\"http://meteor.com\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -117.19999694824219
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/9/6/c/600_398383372.jpeg'
+        lat: 32.88999938964844
+      - country: US
+        city: Venice
+        link: 'http://www.meetup.com/Los-Angeles-MEAN-Stack-Developers/'
+        name: Los Angeles MEAN Stack Developers
+        description: |-
+          <p>The term "MEAN stack" was coined to denote the all-JavaScript web application stack of MongoDB, ExpressJS, AngularJS, and NodeJS... but you already knew that, didn't you? We're a group of developers who are at varying levels of expertise with the stack, but who are continuously striving to improve our technical skills, our professional network, and our beat-boxing abilities. Our meetups range from basic how-tos, to best practice presentations, hackathons, bar crawls, and dance-offs. You never know what we'll schedule next, but you do know it'll make you smarter, better networked, or better looking.</p>
+          <p>Join up and get MEAN!</p>
+        lon: -118.47000122070312
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/e/f/2/600_379848882.jpeg'
+        lat: 33.9900016784668
+      - country: CA
+        city: Kitchener
+        link: 'http://www.meetup.com/Kitchener-node-js-Meetup/'
+        name: Kitchener node.js Meetup
+        description: "This meetup is for Javascript enthusiasts who want to improve their understanding of Node.js or share their knowledge and projects with the community. Kitchener-Waterloo is a great tech hub and there's lots of people using Node.js for projects or who want to learn more about the exciting technology. We'd like to make the discussions community driven so please suggest topics, but there will definitely be talks on architectures, testing strategies, code management, development tools, deployment strategies, the future of Node and emerging trends. See you there!"
+        lon: -80.5
+        lat: 43.45000076293945
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/SanDiegoCodeCamp/'
+        name: San Diego Code Camp
+        description: '<p>Please join the&nbsp;http://www.meetup.com/san-diego-code-school/ meetup group page. &nbsp;This group is being merged/migrated to that group. &nbsp;Thanks!</p>'
+        lon: -117.19999694824219
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/2/2/8/600_440309224.jpeg'
+        lat: 32.88999938964844
+      - country: US
+        city: Memphis
+        link: 'http://www.meetup.com/Meteor-Memphis/'
+        name: Meteor Memphis
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -89.94000244140625
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/c/1/8/600_382927192.jpeg'
+        lat: 35.119998931884766
+      - country: CA
+        city: Kitchener
+        link: 'http://www.meetup.com/porchJS/'
+        name: porchJS
+        description: 'Love JavaScript, nodeJS, development in general? Come join us on the bitHound.io porch for a casual meetup where we can chat about the language(s) we all love (or love to hate) over a nice cold beer, pop, or water.'
+        lon: -80.48999786376953
+        lat: 43.45000076293945
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Ionic-Toronto/'
+        name: Ionic Toronto
+        description: "<p>The beautiful, open source front-end framework for developing hybrid mobile apps with HTML5. This Toronto Meetup group is aimed to educate, demonstrate and collaborate using the Ionic Mobile Development Framework.</p>\n<p>We welcome attendees of all skill levels and would love to hear about projects and apps that you are working on.&nbsp;</p> \n<p><b>If you would like to present something related to Ionic at an upcoming event, please message me via the Ionic TO Meetup board.&nbsp;</b></p>\n<br>"
+        lon: -79.41999816894531
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/b/e/6/600_433163526.jpeg'
+        lat: 43.65999984741211
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Open-Source-Toronto/'
+        name: Open Source Toronto
+        description: '<p>A group to discuss and develop on open source technologies, with a focus on the promotion of their use in enterprise settings. Anyone who works on, or wants to work on open source technologies is welcome!</p>'
+        lon: -79.37000274658203
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/2/9/2/600_389617522.jpeg'
+        lat: 43.63999938964844
+      - country: US
+        city: Provo
+        link: 'http://www.meetup.com/Utah-Node-Ninjas/'
+        name: Utah Node.js Ninjas - Provo
+        description: |-
+          <p>NOTE: &nbsp;We are currently looking for an Organizer to manage Provo. &nbsp;There will be no meetups in provo until one is found. &nbsp;The UNN <a href="http://www.meetup.com/utahnodejs/">meetup in SLC</a> is still active.</p>
+          <p><br></p>
+          <p>Utah web developers exploring different areas of Node.js such as making RESTful APIs and exploring popular libraries and frameworks.</p>
+          <p><span>NodeJS is emerging as a powerful platform for building Internet applications. As an emergent technology, NodeJS does not yet have the ensemble of tools and infrastructural parts that mature language systems have. The NodeJS community is relatively small, and we all need to learn from each other's efforts to work with it. The Utah Node.js Ninjas exist to foster interaction among NodeJS developers. The goals for this group are to build our local NodeJS developer community, encourage adoption of NodeJS by businesses in the area, and help people better understand and use NodeJS in applications, both for personal and business uses.</span></p>
+          <p><span>We have weekly meetings, alternating between presentations and hack nights. Hack nights also double as a beginners course, partnering with Nodeschool.io. Anyone interested in learning Node from the ground up is welcome to attend and learn with us!</span></p>
+        lon: -111.62000274658203
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/6/6/1/4/600_405746132.jpeg'
+        lat: 40.2599983215332
+      - country: US
+        city: Tucson
+        link: 'http://www.meetup.com/TucsonJS/'
+        name: TucsonJS
+        description: |-
+          <p>JavaScript. It's everywhere on the web these days. Here we will discuss client-side JavaScript, server-side JavaScript...and everything in-between. So get your keyboards ready and join us for an adventure in everything JavaScript!</p>
+          <p>We want our meetup to be a safe place for everyone, so we have a&nbsp;<a href="http://coc.tucsonjs.org/">code of conduct</a>.</p>
+        lon: -110.98999786376953
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/a/5/a/600_435647706.jpeg'
+        lat: 32.33000183105469
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/hacker-table-tennis-players/'
+        name: HTTP // Hacker Table Tennis Players
+        description: "<p>The core idea of HTTP is to create a Table Tennis club for Boston-area developers, who are interested in a social meetup with other devs over a light-hearted (or maybe, just maybe, sometimes uber-competitive) game of ping pong!\_</p>\n<p>We'll be hosting events at Blazing Paddles - the table tennis club at Game On! in Fenway - and possibly other venues as the club grows.</p>\n<p>All play levels welcome!!!</p>"
+        lon: -71.06999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/a/e/2/600_394686882.jpeg'
+        lat: 42.36000061035156
+      - country: US
+        city: Spokane
+        link: 'http://www.meetup.com/Spokane-Frontend-Meetup/'
+        name: Spokane Frontend Developers Meetup
+        description: |-
+          <p>The Spokane Frontend Meetup connects front-end developers to learn and discuss topics related to frontend web development. We meet the 1st Tuesday of each month at Mckinstry&nbsp;Innovation Center.</p>
+          <p>Our discussions cover topics related to JavaScript, HTML5, CSS3, Frameworks, best practices, etc.&nbsp; <br><span> <br>If you'd like to share your event or product feel free to start a discussion or message the organizers.</span></p>
+        lon: -117.43000030517578
+        lat: 47.66999816894531
+      - country: US
+        city: Olympia
+        link: 'http://www.meetup.com/The-Percival/'
+        name: The Percival
+        description: "<p>A meetup group The Percival, a startup news organization in Olympia, Washington. The Percival will host a number of workshops, hackathons, and other events about journalism and civic engagement.</p>\n<p>The Percival is a startup news organization for Olympia, Washington.\_The Percival will host a number of events and workshops about journalism and civic engagement with a technology focus.\_<br>\n\n</p>\n<p>If you are interested in journalism and using technology to beef up civic engagement in Olympia, then you should join this group.</p>\n<p><b>Types of events:</b></p>\n<p>•\_<b>workshops -\_</b>3-hour introductions to a technology like javascript, ruby, or jquery.</p>\n<p>•\_<b>write-a-thons -\_</b><span>Edit OlyWiki.org to help build a locally-focused community guide to Olympia and Thurston County.</span></p>\n<p><br>\n\n</p>"
+        lon: -122.87000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/c/b/c/600_395411452.jpeg'
+        lat: 46.9900016784668
+      - country: US
+        city: Louisville
+        link: 'http://www.meetup.com/JSLouKY/'
+        name: "JSLou - Louisville's JavaScript Group"
+        description: "<p>Louisville's JavaScript Group. Meets twice every month.</p>\n<p><b>1st Wed - Hack night</b></p>\n<p>Work on projects alone or in a group. Get help, pair up or ask questions of other JavaScript developers.</p>\n<p><b>3rd Wed - Learn Night</b></p>\n<p>Come listen to a great local JavaScript developer about web technology - talks are usually 20-30 min with questions to follow. Time to chat and network after.</p>\n<p><b>Come talk at\_JSLou's Learn Night - What to expect of you are speaking:</b></p>\n<p>Here are some ideas if you think you might want to speak.Share your experience with the group - it's a great way to help build the thriving JavaScript community here in Louisville!<br>\n\n<br>\n\n Tips:</p>\n<p>Talk about what you know - it's safe to assume others can learn from it.<br>\n\n Don't worry about your skill level, the group has a wide range of experience, and beginners can gain a lot from what you know even if you are a beginner working through the basics yourself.Ideas:Talk about a tool or framework you use.<br>\n\n Provide a real-world scenario, discuss a project, or how you solved a problem in a project.<br>\n\n Show &amp; Tell - Show off a project you are working on or have completed.<br>\n\n Code Review/Ask for help - Talk about a project you are working on and get the group's feedback or help, we would love to do code review/ solve problems on the spot. The group has lots of really bright developers who would love to help.<br>\n\n<br>\n\n The format:<br>\n\nJSLou\_talks are around 20min, with a short Q&amp;A period to follow.JSLou's attendance is usually around 10-15 people on learn nights, and the style is very relaxed so\_expect\_comments/questions to pop up during your talk as well.Talks are recorded video/audio unless you specify otherwise.Speaking at the group looks great on your linkedin profile or resume.</p>\n<p><br>\n\n Thanks again and\_\_​remember to either signup and reply to this list: <a href=\"http://kyoss.org/mailman/listinfo/jslou\" class=\"linkified\">http://kyoss.org/mailman/listinfo/jslou</a>, or email\_<a href=\"mailto:jslouky@gmail.com\">jslouky@gmail.com</a>\_and let me know you would like to speak.<br>\n\n</p>"
+        lon: -85.76000213623047
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/d/7/4/600_395715732.jpeg'
+        lat: 38.25
+      - country: US
+        city: Nashville
+        link: 'http://www.meetup.com/Meteor-Nashville/'
+        name: Meteor Nashville
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -86.79000091552734
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/d/7/b/600_438220315.jpeg'
+        lat: 36.15999984741211
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/LA-RESTful-API-Working-Group/'
+        name: L.A. RESTful API Working Group
+        description: "<p>This is a language-agnostic group for developers, sysadmins and PMs to discuss the creation and consumption of RESTful web services. Let's get together and address the problems we all face regardless of the languages/frameworks we work in:</p>\n<p>•\_How to structure our services</p>\n<p>•\_What http status codes to use for various conditions</p>\n<p>•\_How to handle sessions / user-logins / user-logouts</p>\n<p>•\_Best practices for CORS and JSONP</p>\n<p>•\_To force https or not?</p>\n<p>•\_How to version an API and keep multiple versions running live</p>\n<p>•\_How to test an API with SuperAgent, Postman, Curl, Selenium and others</p>\n<p>•\_How to integrate Oauth</p>\n<p>•\_How to write and generate documentation.</p>\n<p>• How to deploy and/or integrate our API development into CI tools</p>\n<p>Maybe this working group can set a unifying-standard for the creation of web services! And while we're at it, let's explore the various open apis available like Twilio, Twitter, AWS, and others. Let's consume as much as we create, and focus the discussions on the similarities between our implementations, instead of the differences.</p>"
+        lon: -118.37000274658203
+        lat: 34.11000061035156
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/Los-Angeles-JavaScript-and-Node-js/'
+        name: Los Angeles JavaScript and Node.js
+        description: "<p>We are JS.LA, the oldest active JavaScript and Node.js meetup in Los Angeles.\_</p>\n<p><span>Find out more and see videos from our past meetups at</span> <a href=\"http://js.la\">JS.LA</a><br>\n\n</p>"
+        lon: -118.25
+        lat: 34.040000915527344
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/TechNext-Bay-Area/'
+        name: TechNext Bay Area
+        description: "<p>Single Place to meet and discuss around new and emerging software technologies. Cover more of Breadth than the Depth. See how these emerging technologies work together.\_</p>"
+        lon: -122.06999969482422
+        lat: 37.38999938964844
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/The-Blockchain-Garage/'
+        name: The Blockchain Garage
+        description: |-
+          <p>The Blockchain Garage is a monthly event for developers hosted by Block.io</p>
+          <p><span>The hardest challenge in building a crypto app is deciding how to handle security, in addition to hosting your own blockchain(s), and proper consulting. This hurdle can costs many startups weeks or months of precious time that can be crucial to getting off the ground in the early phase.</span></p>
+          <p><span>During the event, you can follow along as our featured presenter builds a Bitcoin, Dogecoin, or Litecoin application over the course of several hours (with more currencies coming soon). Ask questions, get personalized help, make connections and friends, let us help you move faster!</span></p>
+          <p><span>Come find us at Blockchaingarage.com and join in!</span><br>
+
+          </p>
+        lon: -122.44000244140625
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/2/2/4/4/600_403328772.jpeg'
+        lat: 37.79999923706055
+      - country: US
+        city: Gainesville
+        link: 'http://www.meetup.com/gainesvillejs/'
+        name: Gainesville JS
+        description: "<p>Are you a forward thinking, bleeding edge tech enthusiast? Wondering what full stack JavaScript can do? End to end testing. The most inspiring frameworks. We will explore JavaScript in all it's incarnations. Server, client, DB, native. Let's cover it all.</p>"
+        lon: -82.4000015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/d/d/6/600_445695830.jpeg'
+        lat: 29.600000381469727
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/seattle-react-js/'
+        name: Seattle React.js
+        description: |-
+          <p>React.js is a fun, easy to use Javascript library built at Facebook.</p>
+          <p><a href="http://facebook.github.io/react/">http://facebook.github.io/react/</a> <br> </p>
+          <p>You should join us if you want to learn about, share experiences with, or work with fellow js devs interested in React. &nbsp;</p>
+        lon: -122.31999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/3/0/600_414122352.jpeg'
+        lat: 47.630001068115234
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/sfnode/'
+        name: SFNode
+        description: |-
+          <p>SFNode is a community run Node.js meetup in San Francisco created by <a href="https://twitter.com/dshaw">dshaw</a>. We meet on the first Thursday of each month. <br> <br>Our location changes month to month. If you have an event space, we'd love to have you host. The event host typically provides food and drink, but if you're not able to we can usually find a sponsor for that.</p>
+          <p>Each month we feature 2-3 talks about Node.js, server-side JavaScript, npm and the surrounding ecosystem. We try to find a good balance between beginner and advanced topics.</p>
+          <p>If you want to help, <a href="https://github.com/sfnode/contribute">we are always looking for contributors</a>. Join us. <br> <br>Follow us on Twitter at&nbsp;<a href="https://twitter.com/sfnode" class="linkified">https://twitter.com/sfnode</a> .</p>
+        lon: -122.4000015258789
+        lat: 37.77000045776367
+      - country: US
+        city: Tampa
+        link: 'http://www.meetup.com/Tampa-Bay-JS-Meetup/'
+        name: Tampa Bay JS Meetup
+        description: |-
+          <p>This meetup is designed for individuals who wish to learn and engage in the latest in the world of JavaScript. The group's main focus is on OOP JS development using tools such as Backbone.js, Angular.js and Node.js. Anyone who has an interest in web development and JavaScript development is encouraged to attend!</p>
+          <p>Events will be hosted and sponsored by Mad Mobile.<br>
+
+          </p>
+          <p><br>
+
+          </p>
+        lon: -82.51000213623047
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/9/e/0/600_418199872.jpeg'
+        lat: 27.969999313354492
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/nodebotssf/'
+        name: NodeBotsSF
+        description: '<p>NodeBotsSF is a monthly meetup for NodeBot hackers to create, explore and share.</p>'
+        lon: -122.4000015258789
+        lat: 37.77000045776367
+      - country: US
+        city: Orlando
+        link: 'http://www.meetup.com/University-Tech/'
+        name: University Tech
+        description: |-
+          <p>This is our once a month Meetup about all things Tech related!&nbsp;</p>
+          <p>If you are a programmer, developer or Tech professional:</p>
+          <p>•&nbsp;&nbsp;Bring a Laptop or whatever gear you need&nbsp;</p>
+          <p>•&nbsp;&nbsp;Meet like minded people to collaborate with</p>
+          <p><span>• &nbsp;Engage in a discussion on the Tech topics you are passionate about</span></p>
+          <p>• &nbsp;<span>Lead a discussion or demo a project you are working on</span></p>
+          <p>Mingle, network, do something cool, and enjoy a beer!</p>
+        lon: -81.25
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/6/c/3/600_439294499.jpeg'
+        lat: 28.579999923706055
+      - country: US
+        city: Boca Raton
+        link: 'http://www.meetup.com/Boca-JS/'
+        name: Boca JS
+        description: |-
+          <p>The Boca Raton JavaScript group (Boca-JS) is here to demonstrate the power of this wonderful language to South Florida.</p>
+          <p>In addition to vanilla java script, we'll be looking at frameworks such as&nbsp;<span>Node,&nbsp;</span><span>AngularJS,&nbsp;</span><span>Ember.js,&nbsp;</span><span>jQuery</span><span>&nbsp;and&nbsp;</span><span>Ionic.</span></p>
+          <p><span>Founded in September 2014 by Adam and Hector, this group continues to grow and thrive.<br></span></p>
+          <p><span>IMPORTANT: This group has been created as a resource for developers. We do welcome meeting sponsors for an opportunity to reach out to members, please contact us for the details.</span> <br> </p>
+          <p><br> </p>
+        lon: -80.08999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/a/9/e/600_412879102.jpeg'
+        lat: 26.350000381469727
+      - country: US
+        city: Milan
+        link: 'http://www.meetup.com/Milan-Web-Development/'
+        name: Milan Web Development
+        description: This is a group for all those interested in web development. We are laid back and interested in expanding our web development knowledge and chatting about all the newest tech. All experience levels are welcome.
+        lon: -83.68000030517578
+        lat: 42.11000061035156
+      - country: US
+        city: Melbourne
+        link: 'http://www.meetup.com/GDGSpaceCoast/'
+        name: GDG Space Coast - Google Developers Group
+        description: |-
+          <p>Google Developer Group (GDG) Space Coast is a technology user group that meets to discuss the latest Google Technologies, Tools, SDKs, and APIs. We focus on learning about the broad spectrum of technologies provided by Google and finding ways that these technologies can be applied. This includes discussions of the technologies from a number of angles (startups, corporations, and individuals).</p>
+          <p> <br> <b>Here are a few of the topics that we have covered so far:</b> <br> <span>Android, AngularJS,&nbsp;Chrome, Chrome OS, Material Design, Google App Engine, Google Play Games Services, Google Cloud Platform, Google Maps, Dart, AngularDart, Polymer, Web Components, Ingress, Android Studio, GWT, JavaScript, Git, GitHub, NodeJS, TypeScript, Google Analytics,&nbsp;and more.</span></p>
+          <p> <br> In addition to regular speaker focused meetings, we also organize code labs, hackathons, social events, DevFests, and study jams. We also assist with local TrepHub and Startup Weekend events.</p>
+          <p> <br> The group is free to attend and open to all who are interested in&nbsp;discussing&nbsp;and learning more about software development with tools and technologies from Google or the open-source community.</p>
+          <p> <br> If you would like to stay up to date with events and activities of the group, please follow us on <a href="https://www.google.com/+GDGSpaceCoastOrg">Google+</a>&nbsp;and bookmark our <a href="http://gdgspacecoast.org/">website</a>. If you would like to take part in discussions about the group, future events, and future content, please join the <a href="https://plus.google.com/communities/102090770044888811148">GDG Space Coast community</a> linked from our About page on Google+.</p>
+          <p><b>Disclaimer</b>:&nbsp;<i>GDG Space Coast is an independent group; our activities and the opinions expressed here should in no way be linked to Google, the corporation.</i></p>
+        lon: -80.62999725341797
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/9/d/8/600_411591672.jpeg'
+        lat: 28.06999969482422
+      - country: US
+        city: Liberty Lake
+        link: 'http://www.meetup.com/dev-coop/'
+        name: Dev Coop
+        description: "<p>You're a developer, you love the web, you build web apps, you feel like the only one in town... You need to join us at the Dev Coop! We don't get together and talk, we get together and do. We're on the cutting edge of web tech and so freakin' excited to share our passion with our peers. Come with us and make something awesome. Get inspired, be challenged, show off, learn something, and love life.</p>"
+        lon: -117.08000183105469
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/7/7/f/600_435382399.jpeg'
+        lat: 47.650001525878906
+      - country: US
+        city: Framingham
+        link: 'http://www.meetup.com/MetroWest-JS/'
+        name: MetroWest JS
+        description: '<p>This group is for anyone in the Metrowest area interested in Javascript. From frontend technologies like jQuery, AngularJS, Ember and D3.js to backend technologies like NodeJS and Express to NodeBots and the IoT. Javascript all the things!</p>'
+        lon: -71.43000030517578
+        lat: 42.31999969482422
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Code-Cans-Developer-Meetup/'
+        name: 'Code & Cans Developer Meetup'
+        description: 'A meetup to share development stories, techniques and technology while enjoying cans of craft beer.'
+        lon: -87.75
+        lat: 41.939998626708984
+      - country: US
+        city: Tampa
+        link: 'http://www.meetup.com/Meteor-Tampa-Bay/'
+        name: Meteor Tampa Bay
+        description: |-
+          <p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others.<br>
+
+          Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>
+        lon: -82.45999908447266
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/c/7/0/600_419396432.jpeg'
+        lat: 27.959999084472656
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/TrackMaven-Monthly-Challenge/'
+        name: Monthly Challenge
+        description: "<p>TrackMaven's Monthly Challenge is a chance to experiment with new technologies and explore creative projects. Each month, we will name a general topic, a new technology, or something in between. We'll collect a few resources and examples to get you started, then it's up to you; make something interesting! At the end of the month, it's time to show off; we'll meet up to share rapid-fire presentations, as raw or as polished as you'd like.</p>"
+        lon: -77.04000091552734
+        lat: 38.90999984741211
+      - country: US
+        city: Norfolk
+        link: 'http://www.meetup.com/Meteor-Norfolk/'
+        name: Meteor Norfolk/Virginia Beach
+        description: "<p>This groups first event was\_<a href=\"http://www.meetup.com/Meteor-Norfolk/events/213228112/\">Worldwide Meteor Day 2014</a>.</p>\n<p>After that event, this group folded it's membership and energy into the awesome <a href=\"http://www.meetup.com/norfolkjs/\">NorfolkJS meetup</a>, and events are based out of that meetup. Go there to join Meteor meetups (as well as Node, Robots, and other JavaScript events).</p>\n<p><br>\n\n</p>"
+        lon: -76.29000091552734
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/4/c/0/600_422065792.jpeg'
+        lat: 36.849998474121094
+      - country: US
+        city: Phoenix
+        link: 'http://www.meetup.com/Meteor-Phoenix/'
+        name: Meteor Phoenix
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -112.06999969482422
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/3/a/8/600_421225512.jpeg'
+        lat: 33.45000076293945
+      - country: US
+        city: Sacramento
+        link: 'http://www.meetup.com/The-Sacramento-Javascript-Meetup/'
+        name: The Sacramento JavaScript Meetup
+        description: |-
+          <p>SacJS isn't just about teaching Javascript, jQuery, new APIs, NodeJS, or micro-controllers. Its about people. We want you to come hang out and meet new people, learn new things. That cool thing you just learned about or launched at work? Come teach us about it!</p>
+          <p> </p>
+          <p>Interested in being a sponsor? Want to give a talk? Tweet us a <a href="http://twitter.com/sac_js">@sac_js</a>&nbsp;or <a href="https://github.com/sacjs/sacjs.github.io">open a Pull Request on GitHub</a>.</p>
+          <p> </p>
+          <p>SacJS expects all speakers and attendees to follow the SacJS <a href="http://sacjs.com/code-of-conduct/">Code of Conduct</a></p>
+          <p> </p>
+          <br>
+        lon: -121.51000213623047
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/5/2/6/600_421838182.jpeg'
+        lat: 38.58000183105469
+      - country: US
+        city: Stamford
+        link: 'http://www.meetup.com/Meteor-Stamford/'
+        name: Meteor Stamford
+        description: "<p>Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started. Come\_Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others.</p>"
+        lon: -73.54000091552734
+        lat: 41.04999923706055
+      - country: US
+        city: Schaumburg
+        link: 'http://www.meetup.com/Chicago-Suburban-Mobile-and-Web-Technology-Meetup/'
+        name: Chicago Suburban Mobile and Web Technology Meetup
+        description: 'Chicago suburban focuses on connecting technology professionals and decision makers in the Chicago land suburbs. The idea is to discuss innovative and disruptive technology aspects like Mobile App Development, Web Technology frameworks, connected devices i.e. Internet of Things and going over the industry trends and implementation of the technologies in terms of solutions.'
+        lon: -88.08000183105469
+        lat: 42.040000915527344
+      - country: US
+        city: Santa Barbara
+        link: 'http://www.meetup.com/Santa-Barbara-AngularJS-Meetup/'
+        name: Santa Barbara AngularJS Meetup
+        description: 'AngularJS Meetup group in Santa Barbara, CA'
+        lon: -119.73999786376953
+        lat: 34.45000076293945
+      - country: CA
+        city: Ottawa
+        link: 'http://www.meetup.com/Meteor-Ottawa/'
+        name: Meteor Ottawa
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -75.69000244140625
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/c/f/c/a/600_441593194.jpeg'
+        lat: 45.41999816894531
+      - country: US
+        city: Glendale
+        link: 'http://www.meetup.com/WebApp-Builders/'
+        name: WebApp Builders - WEEKLY - Fullstack Projects (LA Eastside)
+        description: "<p><b>WebApp Builders</b></p>\n<p><b>Fullstack WebApp Development -- WEEKLY Meetup</b></p>\n<p><b>Projects &amp; Study Group.</b></p>\n<p>L.A Eastside (Glendale)</p>\n<p>We are a weekly study group, coming together to improve our skills as full-stack WebApp developers.\_ We study together to expand our skills, stay sharp, and stay abreast of the latest trends and technologies.\_ Our ultimate goal is to strengthen our skills to produce the finest, most intuitive, scalable, industrial strength web-applications.\_ Our group is primarily composed of Rails developers using an assortment of JavaScript frontends (Angular, Backbone, etc.), but want to include all developers using any/all stacks for their projects.</p>\n<p><i><b>We use Rails, but want to learn from others:</b></i></p>\n<p>Share best-practices with developers building WebApps using the latest backend MVC (MV*) frameworks, together with the latest front-end frameworks.\_ <b><i>Our environment is very welcoming, both to senior developers as well aspiring full-stack developers alike</i></b>.\_ Our group grew out of a beginner's Ruby on Rails study group (itself an outgrowth of Rails Girls LA) -- and we've picked up a number of professional developers along the way.</p>\n<p><i><b>WEEKLY SCHEDULE</b></i>:<br>\n\n \"WebApp Builders\" is a project-oriented study group.\_ We break up into project groups, work as teams, and learn together by discussing our projects as a group.</p>\n<p>A weekly meeting usually encompasses the following:</p>\n<p>(I.) Each project has time to:<br>\n\n - Present what you group did last week.<br>\n\n - Talk about design choices, options chosen and other ideas from the group.<br>\n\n - Discuss next weeks tasks and ask for group feedback.</p>\n<p>(II.) Layer in appropriate tutorials for the group:<br>\n\n - The emphasis is on \"full-stack\" development, so these will be tutorials emphasizing \"Using Rails with AngularJS.\" etc.<br>\n\n - We select a book, assign homework as a group, and discuss at the Meetup.</p>\n<p>(III.) A short weekly \"How To\" presentation:<br>\n\n - A \"How To\" presentation covering Rails fundamentals.<br>\n\n \_\_\_\_\_\_ For example: How to use \"rake routes.\"</p>\n<p><br>\n\n <b>Note on Experience Level</b>:<br>\n\n We are open to all developers -- please come join us! However, this group is intended as a intermediate (and up) group.\_ If you are a beginner, please feel free to join us, but we also have a \"Beginners Rails\" group that meets on Thursdays where we start from HTML &amp; CSS and work our way through tutorials such as Hartl's Rails Tutorial: (<a href=\"https://www.railstutorial.org\">https://www.railstutorial.org</a>).</p>\n<p>Our Beginners Rails Study Group: <a href=\"http://www.meetup.com/LA-Eastside-Ruby-Rails-Study-Group\">http://www.meetup.com/LA-Eastside-Ruby-Rails-Study-Group</a></p>\n<p>Please feel free to come to both!</p>\n<br>\n\n<p>If you've already done tutorials such as <b><i>Hartl's Rails Tutorial</i></b> or gone to one the \"<i><b>BootCamps</b></i>\" such as General Assembly, this is a <b>great group to maintain your skills</b>, keep you up-to-date with software industry best practices, and explore fresh technologies as they emerge.</p>\n<p><i><b>JavaScript in the Front, WebApp Framework in the Back:</b></i><br>\n\n Though we tend to have our conversations around a Rails/Angular implementations, we encourage participation of WebApp developer using any modern full application stacks. We can all learn from each other and are interested in learning from developers using any of the following:</p>\n<p><b>Web Application Frameworks</b>:<br>\n\n Rails4<br>\n\n Django<br>\n\n Drupal<br>\n\n Symfony2<br>\n\nFlask</p>\n<p><b>JavaScript Technologies</b>:<br>\n\n Angular<br>\n\n Backbone<br>\n\n Ember<br>\n\n JQuery<br>\n\nReact</p>\n<p>MEAN stack (Mongo, Express, Angular, Node)</p>\n<p>AND many more...</p>\n<p>Most of the discussion will be around Rails, but any and all are welcome.</p>\n<p>We also use this group as an opportunity to stay up on trends.\_ Not all trends are worth pursuing, but many are worthy of discussion.\_ For example, these days, \"decoupled WebApps,\" is the new thing.\_ As interested developers, the group will be exploring decoupled design pattern, to see how this architecture pattern may fit within our projects.</p>\n<p>*This group is meant for developers.\_ Beginners through professionals are welcome, but please come prepared to learn.\_ We love participation!</p>\n<p>**The is not a place to pitch your business ideas, nor for recruitment.</p>"
+        lon: -118.2699966430664
+        lat: 34.150001525878906
+      - country: US
+        city: Savannah
+        link: 'http://www.meetup.com/SavannahJS/'
+        name: SavannahJS
+        description: |-
+          <p>Meet and learn from other javascript developers with topics like NodeJS, Javascript Frameworks, Mobile and more. Show off things you have done and learn more about what is going on in the JS community in and around Savannah, Georgia.</p>
+          <p><br>
+
+          </p>
+          <p>Topics on our mind but not limited to!</p>
+          <p>- NodeJS</p>
+          <p>- Javascript</p>
+          <p>- Hardware hacking with Javascript</p>
+          <p>- Ghost (new blogging platform built on NodeJS)</p>
+          <p>- Building Mobile Apps using Javascript</p>
+          <p>- Drones using NodeJS</p>
+          <p><br>
+
+          </p>
+        lon: -81.11000061035156
+        lat: 32.06999969482422
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/Portland-ReactJS/'
+        name: Portland ReactJS
+        description: |-
+          <p>This is a group for anyone who has experience working with the Facebook React library or would like to learn more about it. We (usually) host meetings on a monthly basis. There is room for reagents to share their war stories, give lightning talks, share cool tricks/projects and more.</p>
+          <p>If you are interested in sharing or collaborating, please get in touch with us!</p>
+          <p><b>To submit a proposal to talk at one of our events, <a href="https://goo.gl/forms/TCzP1g6urI">please fill out this form</a>.</b></p>
+          <p> <br></p>
+          <p> <br> </p>
+        lon: -122.66999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/b/8/9/600_434023913.jpeg'
+        lat: 45.52000045776367
+      - country: US
+        city: Huntsville
+        link: 'http://www.meetup.com/Huntsville-js-JavaScript-Meetup/'
+        name: Huntsville.js JavaScript Meetup
+        description: 'Our group will be open to all developers from those just starting to those with ninja status. Javascript has become pervasive in the browser, on the server, and even embedded devices. Our mission - create a community in Huntsville that can share experience, knowledge, and opportunities and enhance our own skills and value. Oh - and one more thing - we will have FUN!'
+        lon: -86.55999755859375
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/1/f/c/4/600_428588132.jpeg'
+        lat: 34.66999816894531
+      - country: US
+        city: Laguna Niguel
+        link: 'http://www.meetup.com/SoCal-Application-Developers/'
+        name: SoCal Application Developers
+        description: |-
+          <p>This is a group for anyone interested in application development. We will meet to present and discuss the latest trends in web and mobile development. Our primary focus is the stack of technologies that developers are using to build the modern Internet, including but not limited to MVC/MV* frameworks, JavaScript, Ruby, Rails,&nbsp;Angular JS, Ember JS, Backbone JS, Meteor JS, Knockout JS, the MEAN Stack (MongoDB, Express JS, Angular JS, Node JS), &nbsp;REST, JSON, JSONP, RESTful APIs, CoffeeScript, the Yeoman workflow, Grunt, Gulp, npm, Bower, Jasmine, Karma, Mocha, NoSQL, CouchDB, HTML5, CSS, Bootstrap, LESS, SASS, PhoneGap, Ionic, Apache Cordova, and Firebase to name just a few.</p>
+          <p>We will focus on learning and best practices for integrating the every combination and permutation of technologies that make up the stack faced by developers in this fluid and dynamic ecosystem. We are technology evangelists and at the same time technology agnostic. Please use this as a place to freely share your knowledge and experiences as well as discuss and debate your opinions. This is more than just a Meetup... it is a marketplace for ideas and information.</p>
+          <p>Please feel free to suggest topics, events, presenters, and venues... we need your input.&nbsp;</p>
+          <p>Also, please feel free to use the forums to discuss technology, ask for help, and offer help. This is our community so let's make the most of it.</p>
+          <p> <br> </p>
+        lon: -117.70999908447266
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/b/5/d/600_431743869.jpeg'
+        lat: 33.529998779296875
+      - country: US
+        city: Provo
+        link: 'http://www.meetup.com/DevMountain-Alumni-Association/'
+        name: DevMountain Alumni Association
+        description: |-
+          <p>This group is exclusively for DevMountain Alumni.</p>
+          <p>Here is where DevMountain alumni will find networking opportunities, exclusive events, and a plugin to the tech &amp; developer communities. This meetup group aims to provide a continued education for all alumni.</p>
+          <p>L E A R N + L I V E + B U I L D + G I V E</p>
+        lon: -111.69000244140625
+        lat: 40.220001220703125
+      - country: US
+        city: Mandeville
+        link: 'http://www.meetup.com/Mandeville-Web-Development-Meetup/'
+        name: Mandeville - Web Development Meetup
+        description: 'Meet fellow web developers and designers near you! Come to a Web Development Meetup to compare tools, languages, and templates; trade advice on careers, rates, and freelancing; and share cool websites. Make valuable contacts as you mingle with new friends!'
+        lon: -90.01000213623047
+        lat: 30.420000076293945
+      - country: US
+        city: De Pere
+        link: 'http://www.meetup.com/devtrain-web-developer-community/'
+        name: DevTrain Web Developer Community
+        description: '<p>Interested in the latest open source technology? Want to find a career in web development? Maybe meet other developers who are passionate about the same technology as you? If you answered "yes" to any of those questions, you need to hop on the DevTrain.</p>'
+        lon: -88.06999969482422
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/4/7/2/600_431533426.jpeg'
+        lat: 44.43000030517578
+      - country: US
+        city: Pensacola
+        link: 'http://www.meetup.com/Pensacola-javascript/'
+        name: Pensacola.js The Premier Pensacola JavaScript Users Group
+        description: "<p>Let's get together and learn about JS topics. &nbsp;We are a group of hobbyists/enthusiasts, full time developers, sys admin, and students. &nbsp;Regardless of your familiarity with Javascript, if long as you want to learn more about it then come out to a meetup and ask some questions!</p>"
+        lon: -87.22000122070312
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/a/d/7/600_434491447.jpeg'
+        lat: 30.420000076293945
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/React-Chicago/'
+        name: React Chicago
+        description: |-
+          <p>Meetup focused on all things React.&nbsp;</p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p> </p>
+          <p><span>If you're interested in speaking, sign up&nbsp;</span><a href="https://docs.google.com/forms/d/1_Z1xkxsIwJpgKIfkRdRnVY2TuY375f17sxvKzrXPyvc/viewform?usp=send_form">here</a> <br> </p>
+        lon: -87.63999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/e/c/d/600_432564269.jpeg'
+        lat: 41.880001068115234
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/techDTLA/'
+        name: techDT.LA
+        description: "<p>Relax and enjoy a cozy atmosphere in the middle of DTLA's hustle, join informal presentations and group discussions with food, drinks and wifi. &nbsp;Hang out with local tech professionals, chat about your latest project, and maybe even pick up a thing or two. Looking forward to seeing you at the next meetup.</p>"
+        lon: -118.23999786376953
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/2/1/b/600_437220539.jpeg'
+        lat: 34.04999923706055
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Elasticsearch-Toronto/'
+        name: Elasticsearch Toronto
+        description: |-
+          <p>Welcome to the <b>Toronto</b> meetup group for <b>elasticsearch</b>!</p>
+          <p>I have recently moved from Amsterdam to Toronto. In Amsterdam I worked for the Netherlands Institute for Sound and Vision, the national audiovisual archive of the Netherlands and one of the largest archives in Europe. The institute was one of the early adopters of elasticsearch, using it to power the archive's search engine: <a href="http://www.elasticsearch.org/case-study/sound-and-vision" target="_blank" class="linkified">http://www.elasticsearch.org/case-study/sound-and-vision</a> (if you have a Dutch background or if you are into Dutch cultural heritage, you might enjoy this site: <a href="http://in.beeldengeluid.nl" target="_blank" class="linkified">http://in.beeldengeluid.nl</a>).<br>
+
+          </p>
+          <p>I have already moved on to another project, but since I could not find an elasticsearch meetup group here in Toronto, I thought that I should start one. I'm happy to share my experience with mappings, settings and bringing an elasticsearch cluster to production, and then let the community take it forward. You all use elasticsearch, don't you?<br>
+
+          </p>
+        lon: -79.37999725341797
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/4/c/e/600_431885326.jpeg'
+        lat: 43.63999938964844
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/SF-Front-End/'
+        name: 'SF Front-End Developers: Client-Side Sorcery'
+        description: "<p>SF Front-End Developers is a community for front-end engineers, UX/UI designers and server-side fiends looking to expand into the client. If you go home at night and Ember.js, Angular.js, Polymer, Swift, d3.js or Backbone.js code haunts your dreams, you have come to the right place. We're focused on providing: engaging presentations, bleeding-edge tech demos and gathering groups of people together to explore the best possible UX engineering and design experiences. Let's do this!</p>"
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/4/0/600_432002880.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/iojsnyc/'
+        name: New York io.js Meetup
+        description: "We're dedicated to exploring and furthering io.js, the new fork of the game-changing node.js platform. We're application developers, backend engineers, open source contributors, and local New York technologists!"
+        lon: -73.9800033569336
+        lat: 40.720001220703125
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/JS-Study-Group/'
+        name: Javascript Study Group
+        description: "<p>This group is primarily focused on hosting and fostering study sessions for specific Javascript-specific technologies (frameworks, libraries, standards, etc.). We want to build various \"mini-communities\" for a variety of these JS technologies so that all members can accelerate their learning of the respective subject -- whether it's Angular, Firebase, Underscore/Lodash, MomentJS, Appgyver, Phonegap, Node, etc. We hope to have members achieve this accelerated learning by leveraging each others' knowledge and expertise.</p>"
+        lon: -122.08000183105469
+        lat: 37.40999984741211
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/Dev-Games-2015/'
+        name: 'Dev Games!'
+        description: '<p>This is the Developer Olympics. Network with like-minded devs, make cool stuff, have a blast doing it. &nbsp;We will have a series of short, timed coding challenges and there will be an opportunity to share stories from the trenches - how did that design pattern or library work in a real-world situation, on the job? What new frameworks and libraries are you interested in learning about?</p>'
+        lon: -118.33000183105469
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/f/600_445320175.jpeg'
+        lat: 34.099998474121094
+      - country: US
+        city: Pawtucket
+        link: 'http://www.meetup.com/Kenzan-Providence-Hack-Nights/'
+        name: Kenzan Providence Hack Nights
+        description: |-
+          <p>This is a group for developers interested in sharing code, helping each other, learning new stuff, hanging out and having a few beers.&nbsp;</p>
+          <p>Kenzan has a great space with lots of hardware and interesting technology, stop by and let's work on something together or simply join us for a conversation.</p>
+        lon: -71.38999938964844
+        lat: 41.869998931884766
+      - country: US
+        city: Worcester
+        link: 'http://www.meetup.com/Lets-Learn-Programming-in-Worcester-MA/'
+        name: "Let's Learn Programming in Worcester, MA!"
+        description: "<p>I want to become a Front End Developer, but I believe this endeavour will be much easier to tackle with like minded people. so, please join in! My aim is to became proficient in the MEAN stack (MongoDB, ExpressJS, AngularJS and node.js), but by no means I want to limit the group, so if you want to learn PHP or Ruby, and you would like to become part of the group, feel free! The idea of this meetup is purely the collaboration between 2 or more people in a common goal, learning how to be a proficient developer. We all learn at different pace, some of us will be able to learn in couple of months, and some of us will take longer, but don't let that deter you! I would like to welcome to the group, complete newbies, intermediary level and experience programmers! we all can learn something and help each other. I would love to hear from you, if you would like to help me on this venture, I will answer all questions and I will gladly accept all collaboration in developing a study guide/curriculum.</p>"
+        lon: -71.80000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/6/b/5/600_432870389.jpeg'
+        lat: 42.290000915527344
+      - country: US
+        city: Morgan Hill
+        link: 'http://www.meetup.com/South-County-Web-Developers/'
+        name: South County Web Developers
+        description: |-
+          <p><b>South County Web Developers</b>&nbsp;is a study group for web designers and developers of all skill levels to get together, work on some cool websites, make friends, network, learn some of the hottest frameworks, and have fun!</p>
+          <p><b>Mission</b></p>
+          <p>This group aims to become a motivated and driven web design/development community within and near the Morgan Hill area. Some of our key initiatives are, but may not be limited to:</p>
+          <p>•&nbsp;To connect together web designers/developers within the Morgan Hill area&nbsp; <br><span>•&nbsp;To provide resources for designers/developers to learn and improve skills<br></span><span>•&nbsp;</span><span>To provide a friendly, learning and collaborative environment for designers/developers to jump-start and work on website projects alongside each other <br></span><span>•&nbsp;</span><span>To help aspiring designers/developers discover a passion in the technology field&nbsp; </span><br></p>
+          <p>All aspiring designers/developers are welcome!&nbsp;Bring your laptop to events, and tell your friends about our group!</p>
+          <p><span>Join our Facebook group here:</span> <a href="https://www.facebook.com/groups/GilroyMorganHillWebDevelopers/">https://www.facebook.com/groups/GilroyMorganHillWebDevelop...</a> <br> </p>
+        lon: -121.6500015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/e/b/7/600_433017015.jpeg'
+        lat: 37.119998931884766
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/codefellowspdx/'
+        name: Code Fellows Portland Meetup
+        description: "<p>Code Fellows offers full-time and part-time programs to train software developers at every experience level. We strongly believe in the power of community and want to contribute in any way we can. Whether you're just starting out or have been a coding for years, come join us!</p>"
+        lon: -122.69000244140625
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/e/2/8/600_433128680.jpeg'
+        lat: 45.5
+      - country: CA
+        city: Cambridge
+        link: 'http://www.meetup.com/Meteor-Tri-City-Code-Club/'
+        name: Meteor Tri-City Code Club
+        description: '<p>Hoping to gather a group of people to meetup either Cambridge/Kitchener/Waterloo for ongoing MeteorJS hackathons and meetups. If you love Javascript and you are interested in Meteor or you are already developing with the framework, this group is for you!</p>'
+        lon: -80.33000183105469
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/b/7/a/600_433151130.jpeg'
+        lat: 43.349998474121094
+      - country: US
+        city: Saint George
+        link: 'http://www.meetup.com/Saint-George-JavaScript-Meetup/'
+        name: Saint George JavaScript
+        description: '<p>A group for developers that want to be JavaScript masters. All are welcome: young, old, new, experienced. We get together once a month to discuss hot topics in JavaScript, the industry, and programming. We understand that JavaScript is in web, mobile, and desktop applications, so we will also learn and discuss HTML, CSS, Android, iOS, Windows, Mac, and Linux. You will learn, socialize, teach, and help in this group. Go team JS!</p>'
+        lon: -113.58000183105469
+        lat: 37.08000183105469
+      - country: US
+        city: Berkeley
+        link: 'http://www.meetup.com/BayArea-OpenROV-Users-Group/'
+        name: BayArea OpenROV Users Group
+        description: 'This group is for OpenROV users and enthusiasts in the Bay Area.  If you need help building your underwater robot, if you want to share with like minded individuals we are here to help.  Activities include build days, local expeditions to fly ROVs, and hack days.  All skill levels and ages welcome.'
+        lon: -122.30000305175781
+        lat: 37.869998931884766
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/javascript-dc/'
+        name: JavaScript DC
+        description: "<p>JavaScript is becoming ever more popular on the client, server and mobile. Let's get together to learn new skills and network with like-minded JavaScript developers.\_</p>\n<p><b>Why another JavaScript group?</b> Because with ES6 around the corner and with over 1 million JavaScript projects on GitHub, the Washington DC metro area can afford a new and different look at this fantastic language.</p>"
+        lon: -77.0199966430664
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/c/8/e/600_433192366.jpeg'
+        lat: 38.90999984741211
+      - country: US
+        city: Charlotte
+        link: 'http://www.meetup.com/Makerspace-Charlotte/'
+        name: Makerspace Charlotte
+        description: "<p>Makerspace Charlotte is for make euthusiasts of all ages; we're into rockets, microcontroller, robots, etc... especially nodebots, and other IoT platforms for connecting all the things. Come by if you're into STEM education, sustainable tech, or building your next Burning Man exhibit. We can make IT together.</p>"
+        lon: -80.83000183105469
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/1/3/600_435601811.jpeg'
+        lat: 35.189998626708984
+      - country: US
+        city: Minneapolis
+        link: 'http://www.meetup.com/JAVA-USER-GROUP-JUG/'
+        name: JAVA USER GROUP (JUG)
+        description: 'Do you like to learn new technologies? Want to meet with other Java/UI developers in the Twin Cities? Enjoy free food and beverages?! Then come check us out! This group is for anyone and everyone who is interested in learning about the new technology trends in the Twin Cities Market. Set-Up: An hour of social time (catch up with other developers and eat food!), then an hour of presentation from a local software developer and technical evangelist. Topics range from web development w/backbone.js to best practices for RESFFUL API design. We cater to what the group is interested in hearing about! ***PLEASE check back with us on the next topic!'
+        lon: -93.33999633789062
+        lat: 44.81999969482422
+      - country: US
+        city: Saint Louis
+        link: 'http://www.meetup.com/STL-AngularJS/'
+        name: STL AngularJS Meetup
+        description: |-
+          <p>Come to learn, discuss and get to know fellow AngularJS developers in the STL area. We love seeing new faces and most of the meetups end with some great discussion!</p>
+          <p>If you are interested in speaking please fill out the form here:&nbsp;http://goo.gl/forms/xlceG63Ukq and we will get you on the schedule as soon as possible.</p>
+        lon: -90.25
+        lat: 38.63999938964844
+      - country: US
+        city: Addison
+        link: 'http://www.meetup.com/DallasAngularJS/'
+        name: Dallas AngularJS SuperHeros
+        description: '<p>The Dallas AngularJS Super Heros DASH is a user group of front end AngularJS developers. We meet to broaden our knowledge on AngularJS and also other related front end technologies. The DASH meets on the fourth Tuesday of every month, with social / food at 6:30pm, and meeting content starting at 7:00pm. We meet at the Improving Enterprises office on the Dallas North Tollway.</p>'
+        lon: -96.83000183105469
+        lat: 32.959999084472656
+      - country: US
+        city: Houston
+        link: 'http://www.meetup.com/NodejsHouston/'
+        name: Node.js Houston
+        description: |-
+          <p>Node.js Houston was created to bring like minded software developers with an interest of Node.js together. This group plans to facilitate a learning environment for all those seeking to improve their understanding with full stack javascript web development. This group encourages and will be facilitating opportunities to expose and announce collaborative efforts, opensource and local projects. We are all looking forward to the future of web development with a full javascript stack!</p>
+          <p>For more information about Node.js Houston, please visit our website: <a href="http://www.nodejshouston.com">http://www.nodejshouston.com</a></p>
+          <p>Join us on slack at: http://chat.nodejshouston.com/</p>
+        lon: -95.41999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/6/d/d/600_433559101.jpeg'
+        lat: 29.799999237060547
+      - country: US
+        city: Jersey City
+        link: 'http://www.meetup.com/Hudson-County-JavaScript-Meetup/'
+        name: Hudson County JavaScript Meetup
+        description: |-
+          <p><img src="http://photos3.meetupstatic.com/photos/event/9/2/a/e/600_434137550.jpeg"></p>
+          <p> </p>
+          <p>This group is for anyone interested in any and all things JavaScript. Our meetups and presentations are intended for members to share and level-up their JS skills. All skill levels are welcome.</p>
+        lon: -74.05000305175781
+        lat: 40.72999954223633
+      - country: US
+        city: Chalfont
+        link: 'http://www.meetup.com/Bucks-Co-Js/'
+        name: Bucks County JS
+        description: '<p>Bucks County JS is a group of professionals that are interested in, and involved with development in the browser and beyond. Topics include JavaScript, HTML, CSS, Node.js, Build Tools and Automation, Popular/Upcoming frameworks and libraries, etc.</p>'
+        lon: -75.19999694824219
+        lat: 40.279998779296875
+      - country: US
+        city: Reno
+        link: 'http://www.meetup.com/RenoJS/'
+        name: Reno.js
+        description: |-
+          <p>This is a group for anyone interested in JavaScript development.&nbsp; We will cover a wide variety of topics both client-side and server-side (Node.js) as well as some embedded JS development.</p>
+          <p> <br></p>
+          <br>
+        lon: -119.80999755859375
+        lat: 39.529998779296875
+      - country: CA
+        city: Victoria
+        link: 'http://www.meetup.com/victoriajs/'
+        name: 'VicJS: Victoria JavaScript Developers'
+        description: "<p>VicJS is for JavaScript&nbsp;(including CoffeeScript!)&nbsp;developers based in Victoria, BC, Canada. The meetup format is a 30 to 60 minute presentation, followed by discussion at a nearby pub. We're planning to meet once every 2 months; contact us if you want to give a talk!</p>"
+        lon: -123.37000274658203
+        lat: 48.43000030517578
+      - country: US
+        city: Collingswood
+        link: 'http://www.meetup.com/Beer-js-South-New-Jersey-Talk-JavaScript-at-Local-Pubs/'
+        name: Beer.js South New Jersey - Talk JavaScript at Local Pubs
+        description: "<p>Beer and JavaScript - what could be better? The South New Jersey (central to Audubon) chapter of the Beer.js group. Let's meet at some of our fine local establishments and talk JavaScript while enjoying a beverage and maybe some food. Despite the name, Beer.js is about creating social spaces to strengthen software communities. There is no requirement to drink to participate.</p>"
+        lon: -75.06999969482422
+        lat: 39.90999984741211
+      - country: US
+        city: Denver
+        link: 'http://www.meetup.com/DenverScript/'
+        name: DenverScript
+        description: |-
+          <p>DenverScript is a community of developers focused on JavaScript in downtown Denver. We will be discussing best practices, features coming to ECMAScript, application development, what's going on in the JS community, and more. If you have any interest in upping your JavaScript knowledge, then please come check us out.</p>
+          <p>Follow our Twitter account at&nbsp;<a href="https://twitter.com/denverscript">@DenverScript</a>&nbsp;for JavaScript tweets and Meetup announcements, and join us at #denverscript on Freenode to chat!</p>
+          <p>We care about providing a safe harassment-free community, so read our <a href="http://www.meetup.com/DenverScript/pages/Code_of_Conduct/">Code of Conduct</a> and know who to contact if there are issues.</p>
+        lon: -104.98999786376953
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/1/c/7/600_434176839.jpeg'
+        lat: 39.75
+      - country: US
+        city: Irvine
+        link: 'http://www.meetup.com/Meteor-Irvine/'
+        name: Meteor Irvine
+        description: "<p>Meet other developers using <a href=\"https://www.meteor.com/\">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: -117.79000091552734
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/7/5/4/600_433954644.jpeg'
+        lat: 33.689998626708984
+      - country: US
+        city: Palo Alto
+        link: 'http://www.meetup.com/modernwebui/'
+        name: Modern Web UI
+        description: |-
+          <p>For meetups, please visit http://meetup.com/modernweb. For podcasts and videos, visit http://modern-web.org.</p>
+          <p>Topics: web components, ember, angular, react, polymer, async programming, libraries such as bacon.js, rxjs, scalability, native promises &amp; performance, es6/es7 iterators and generators, reactive extensions, object oriented design in es6, traits.js, design patterns and more.</p>
+        lon: -122.16000366210938
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/6/f/7/600_439950455.jpeg'
+        lat: 37.45000076293945
+      - country: US
+        city: Monterey Park
+        link: 'http://www.meetup.com/LA-Web-Dev-Design/'
+        name: 'LA Web Dev & UX Design community'
+        description: |-
+          <p>Introduction: Our meetup is for anyone interested in HTML5, CSS3, Javascript/JQuery, Dustjs/Templating Language, Less/Sass, Backbonejs/Angularjs and the <a>Nodejs/Expressjs Platform, Bootstrap, Wordpress, Shopify, Google Analytics, Heroku, </a>Parse, Twilio, also Responsive Design, Mobile First and Content First, or anything else people wants to learn and discuss.yeah! Our meetup is also to network and connect local talented and skilled web developers who like to work on side project or tutor(on nights and weekend from home) and make a few extra money, with companies and startups in need of talents that can get things done for and willing to work on their own hours for a slightly reduced rate.</p>
+          <p> <br> </p>
+          <p>so you are welcome to join if:</p>
+          <p>1, you are talent web Developer/ designer</p>
+          <p>2, you own or work for a startup company and have web development needs and looking for solutions or user feedback .</p>
+          <p>3, work on a project(or side project) and might need a helping hand with your project from time to time.</p>
+          <p> <br></p>
+        lon: -118.1500015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/b/4/7/600_434036135.jpeg'
+        lat: 34.04999923706055
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/sandiego-ember/'
+        name: San Diego Ember
+        description: '<p>San Diego Ember is dedicated to providing a fun and engaging environment promoting Ember.</p>'
+        lon: -117.23999786376953
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/c/f/c/600_434251996.jpeg'
+        lat: 32.790000915527344
+      - country: US
+        city: Plano
+        link: 'http://www.meetup.com/amRobotics/'
+        name: 'amRobotics - LittleBits, JavaScript, Python, IoT, and More!'
+        description: |-
+          <p><a href="http://www.meetup.com/nodebotsdfw/"></a>The focus of our community is on developing and hacking the latest technology using JavaScript, Python, IoT, and LittleBits in order to create and enjoy a better way of life through technology.</p>
+          <p><a href="http://www.meetup.com/nodebotsdfw/">AmRobotics</a>&nbsp;will share information on (and host) several local Maker Faire &amp; Hackathon events in 2016. Although group presentations and discussions are encouraged, our approach will be predominately ’hands on’.</p>
+          <p>We meet the last Monday of every other month starting March 2016.</p>
+          <p>Suggestions encouraged and&nbsp;<b>ALL SKILL LEVELS</b> welcome!</p>
+          <p> <br> <br></p>
+          <p><i>Check out the links below for more info on the international community and sponsors.</i></p>
+          <p><b>International Communities</b>:</p>
+          <p><a href="https://github.com/nodebots/nodebotsday">International NodeBots Day</a></p>
+          <p><a href="http://nodebots.io/">NodeBots</a></p>
+          <p> <a href="http://www.pycon.org/">PyCon</a></p>
+          <p><a href="https://day.arduino.cc/#/">Arduino Day 2016</a></p>
+          <p> <br></p>
+          <p><b>Sponsors</b>:</p>
+          <p><a href="https://www.facebook.com/amrobotics/">AmRobotics</a></p>
+          <p><a href="https://www.techbubble.info/">TechBubble Info</a></p>
+          <p><a href="https://www.zaniaclearning.com/southlake/">Zaniac Southlake</a></p>
+          <p><a href="http://nodebots.io/"></a></p>
+        lon: -96.80000305175781
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/c/c/6/600_446572422.jpeg'
+        lat: 33.08000183105469
+      - country: US
+        city: Indianapolis
+        link: 'http://www.meetup.com/meteor-indy/'
+        name: Meteor Indy
+        description: |-
+          <p>Join other area enthusiasts to share knowledge, apps and experience with Meteor.&nbsp;</p>
+          <p>Meteor is a full stack open source, reactive platform for building web and mobile apps in pure JavaScript. Meteor lets you build apps that are a delight to use, faster than you ever thought possible.&nbsp;</p>
+          <p>Everyone is welcome.</p>
+        lon: -86.11000061035156
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/7/c/f/8/600_434431992.jpeg'
+        lat: 39.869998931884766
+      - country: US
+        city: Glendale
+        link: 'http://www.meetup.com/West-Valley-OSS-Web-Development-Meetup/'
+        name: West Valley OSS Web Development Meetup
+        description: |-
+          <p>westvalleywebdev</p>
+          <p>The West Valley OSS Web Development Meetup group is a friendly learning-based meetup for people new to open-source web development. This meetup is ideal for high school (with parents in tow...members must be 18 but parents can join for their kids) and college students, Jr. developers, and people new to web development (career change, etc.). The goal of the meetup is to help foster the growth of professional web developers here in the West Valley. We welcome people of all skill levels but topics will be most beneficial to beginning and intermediate developers. More seasoned developers are certainly welcome to join as long as you are interested in guiding and helping other members who want to learn.</p>
+          <p>This meetup is a collaborative effort and thus members are expected to not only be interested in learning all aspects of web development but also willing to help their fellow developers when needed. Each meetup will have a speaker who will give a short 30-45min presentation followed by 30-60min of an open lab where members can work on the topics covered or just seek help and guidance on their own projects from other members. This group is about learning and problem solving as much as it is about making professional connections.</p>
+          <p>Because we are an OSS focused group, we will primarily cover OSS-related topics like popular web languages (JavaScript, PHP, Python, Ruby, etc.), databases (MySQL, MongoDB, etc.), Linux as a server, code management (Git/Mercurial, DVCS, etc.), APIs and cloud services (AWS, DigitalOcean, etc.), and a variety of other related topics! Ideas and suggestions are always welcome.</p>
+          <p>Meetups will be graciously hosted by the awesome START center at West-MEC (<a href="http://west-mec.org/start/" class="linkified">http://west-mec.org/start/</a>).</p>
+          <p>Check out our slack (<a href="https://slack.com/">https://slack.com/</a>) team at "westvalleywebdev" Instructions for joining are <a href="https://slack.zendesk.com/hc/en-us/articles/201405046-Joining-multiple-Slack-teams">here</a>. Ask development questions, connect with others, and make group-related announcements. Please no spam!</p>
+        lon: -112.25
+        lat: 33.529998779296875
+      - country: US
+        city: Bakersfield
+        link: 'http://www.meetup.com/Bakersfield-JavaScript/'
+        name: Bakersfield JavaScript
+        description: '<p>Javascript is everywhere! If you are a programmer you will eventually need to get your hands dirty in JS. We will talk about frameworks, libraries, common practices and everything javascript. If you are coming from the HTML 5 Meetup group, welcome, this is the new place for meetups.</p>'
+        lon: -118.93000030517578
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/a/3/8/600_434639960.jpeg'
+        lat: 35.38999938964844
+      - country: US
+        city: Carlsbad
+        link: 'http://www.meetup.com/San-Diego-Technology-Immersion-Group-SDTIG/'
+        name: San Diego Technology Immersion Group (SDTIG)
+        description: |-
+          <p>We are a technical book club. We read the same book on software development and then meet once a month to discuss it. It takes us between 3 - 5 months to read a book. We read three to four books a year. We've been doing this for about four years and have about 150 active members with about 40 people coming each month. Past books have covered T-SQL, JavaScript, Angular.JS, Entity Framework, WPF, C#, etc. Our next topic will be Python.</p>
+          <p><br></p>
+          <p>If you'd like to see past webcasts of our meetings, please visit the<a href="https://www.youtube.com/channel/UCM4g18nauWI2pAuaiC6bWgw"> CraftingBytes YouTube channel</a>.</p>
+          <p><br></p>
+          <p><br></p>
+        lon: -117.30999755859375
+        lat: 33.150001525878906
+      - country: US
+        city: West Palm Beach
+        link: 'http://www.meetup.com/Palm-Beach-Javascript/'
+        name: Palm Beach JavaScript
+        description: |-
+          <p><span>If you're interested in anything related to JavaScript, then this meetup is for you!</span><br></p>
+          <p><span>This group is for anyone interested in JavaScript, client side, server side, and everything in between. We'll share ideas, talk about projects, listen to speakers, have demonstrations, and anything else one can think of.&nbsp;<b>All skill levels welcome!</b></span></p>
+        lon: -80.05999755859375
+        lat: 26.709999084472656
+      - country: US
+        city: Melville
+        link: 'http://www.meetup.com/Long-Island-Programming-Meetup/'
+        name: Long Island Programming Meetup
+        description: '<p>Long Island Programming Meetup is a place for programmers to share ideas, challenges, and passion. &nbsp;All languages are welcome and all types of development (web, back-end, etc.). &nbsp;</p>'
+        lon: -73.4000015258789
+        lat: 40.79999923706055
+      - country: US
+        city: West Palm Beach
+        link: 'http://www.meetup.com/Angular-Bootstrap-MVC-of-West-Palm-Beach-Meetup/'
+        name: 'Angular & Bootstrap & MVC of West Palm Beach Meetup'
+        description: |-
+          <p>New to Angular? Finding yourself calling $scope.$apply for everything? Don’t worry, we got you covered!</p>
+          <p>I’m starting this group because I believe Angular is gaining popularity in Palm Beach County and there is a need to collaborate and exchange ideas.</p>
+          <p>The goal is to create a welcoming atmosphere where people of all levels can come together and expand their Angular awesomeness. Join us!</p>
+        lon: -80.05999755859375
+        lat: 26.709999084472656
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Code-Fellows-Chicago-Meetup/'
+        name: Code Fellows Chicago Meetup
+        description: "<p>Code Fellows offers full-time and part-time programs to train software developers at every experience level. We strongly believe in the power of community and want to contribute in any way we can. Whether you're just starting out or have been a coding for years, come join us!</p>"
+        lon: -87.63999938964844
+        lat: 41.88999938964844
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Rockstar-Developers-Designers-Meetup/'
+        name: Rockstar Developers
+        description: '<p>Are you a rockstar developer? or want to become one? This group is for you. Come and network with some of the brightest minds in the industry and elevate your career. Great opportunity to learn from developers who have been successful, not just in development but also in their lives. Opportunity to learn some productivity techniques and relaxation techniques from some world class yoga gurus too. Complete personality development group for technocrats. Worth joining. See you soon!</p>'
+        lon: -97.80999755859375
+        lat: 30.299999237060547
+      - country: US
+        city: Salt Lake City
+        link: 'http://www.meetup.com/utahnodejs/'
+        name: Utah Node.js - Salt Lake City
+        description: '<p>A meetup group dedicated to software development using <a href="https://nodejs.org/">Node.js</a>.</p>'
+        lon: -111.81999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/3/b/a/600_446973722.jpeg'
+        lat: 40.619998931884766
+      - country: US
+        city: Detroit
+        link: 'http://www.meetup.com/ng-detroit/'
+        name: ng-detroit
+        description: '<p>A group for AngularJS developers to network and share resources. <br></p>'
+        lon: -83.05000305175781
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/5/c/9/1/600_440783697.jpeg'
+        lat: 42.33000183105469
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Austin-Treeline/'
+        name: Austin Treeline
+        description: '<p>Treeline lets you develop scalable Node.JS backend apps in your web browser without needing to know a lick of node syntax. Our meetup will introduce Treeline, showcase Treeline projects, and discus the world of rapid development for enterprise.</p>'
+        lon: -97.70999908447266
+        lat: 30.270000457763672
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/CodeClass-io/'
+        name: CodeClass.io
+        description: 'CodeClass.io offer coding and technical workshops to help you get a jump start on your learning. We are a group of passionate developers, hackers, builders who love to learn and teach.'
+        lon: -122.44000244140625
+        lat: 37.77000045776367
+      - country: CA
+        city: Waterloo
+        link: 'http://www.meetup.com/Waterloo-Ember-js-Meetup/'
+        name: Kitchener-Waterloo Ember.js Meetup
+        description: '<p>If you think the ember way is the only way, or you think the ember way will eventually be the only way or if you are just curious about the ember way, then this is for you. This meet ups will focus around Ember.js existing and future features, its progress in the way of Ember 2.0 and overall common front-end challenges Ember.js devs face</p>'
+        lon: -80.51000213623047
+        lat: 43.470001220703125
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/makersquarela/'
+        name: MakerSquare Los Angeles
+        description: "<p>Ever thought about learning to code? If so, this meetup is for you! This meetup is run by MakerSquare, a 3 month immersive software engineering school part of the national Reactor Core Network. Our mission is to teach a driven community of students the latest in web development skills. We're educators first and software engineers second. We employ 21st century, rapid-iteration teaching principles to teach professionals the most in-demand skills in the most effective ways possible. Events we'll host will include coding workshops in HTML, CSS, JavaScript and Git, networking events for tech professionals in the Los Angeles area and community events to attract attention to the tech scene, just to name a few. Our goal is to provide the Los Angeles area with effective training that can support the lively tech ecosystem. Feel free to reach out if you're looking to get your hands dirty in some code!</p>"
+        lon: -118.23999786376953
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/4/d/d/e/600_448339934.jpeg'
+        lat: 33.970001220703125
+      - country: US
+        city: Baltimore
+        link: 'http://www.meetup.com/charmcityjs/'
+        name: charmCityJs
+        description: "<p>CharmCityJS brings the JS community of Baltimore together once a month for talks, hacking, and networking. We welcome newcomers of all experience levels. If you're new to web development and programming or if you're a CTO - we want to hang with you!</p>"
+        lon: -76.62000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/e/c/1/600_436060641.jpeg'
+        lat: 39.290000915527344
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/Seattle-Devmeetings/'
+        name: Seattle Devmeetings
+        description: '<p>We are looking forward to meet front-end engineers who would like to improve their skills in web technologies, share their knowledge and experience as well as software developers who are starting their adventure with web development and are eager to learn Javascript and related frameworks and tools. Devmeeting is a mix between hackaton, workshop and development training. We will code in teams with support from mentors and we will learn Javascript related tools, technologies and frameworks.</p>'
+        lon: -122.37999725341797
+        lat: 47.66999816894531
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/treelinesails/'
+        name: Sails.js + Treeline.io Raft.Up
+        description: |-
+          <p>Lets get together, learn and work with Sails.js &amp; Treeline.io&nbsp;</p>
+          <p> <br><a href="http://sailsjs.org">Sails.js</a> is a web framework that makes it easy to build custom, enterprise-grade Node.js apps. It is designed to resemble the MVC architecture, but with support for the more modern, data-oriented style of web app development. It's especially good for building realtime features like chat. <br></p>
+          <p><a href="https://treeline.io/">Treeline.io</a> allows you to build the back end of a web or mobile application by combining components (aka “<a href="http://node-machine.org/">node-machines</a>”) in a visual environment. Your app is then compiled into a Sails.js project that can be downloaded and deployed anywhere. In short, Treeline eliminates the need for specialized knowledge to create back-end apps.</p>
+          <p>Collaborative Coding provides the opportunity for coders to work on their own projects while sharing the company of other coders working with the same language or framework. Lets share tips, code, and experience with each other.</p>
+          <p><b>Learning Sails Videos <br></b></p>
+          <p><a href="http://irlnathan.github.io/sailscasts/">IRL Nathan Sailscast Blog</a>&nbsp;</p>
+          <p><a href="https://www.youtube.com/user/ponzicoder/videos">Sailscast on Youtube</a></p>
+          <p><a href="https://courses.platzi.com/courses/develop-apps-sails-js/">Platzi Free Course Develop Web Apps in Node &amp; Sails.js </a><b> <br></b></p>
+          <p><a href="https://www.youtube.com/watch?v=ZfPJEOwBP68">Modern Web Intro to Sails </a><b> <br></b></p>
+          <p><a href="https://www.youtube.com/watch?v=7YvPMeCgPew">Markus Padourek Sails and Ember </a><b> <br></b></p>
+          <p><b>Learning Sails Docs &amp; Tuts</b></p>
+          <p><a href="http://www.manning.com/mcneil/">In Progress "Sails.js in Action" Book</a></p>
+          <p><a href="http://sailsjs.org/#!/documentation/concepts">Sails.js Official Docs </a> <br></p>
+          <p><b>Learning Treeline Videos</b></p>
+          <p><a href="https://www.youtube.com/watch?v=84TXJ4CxeKw">Build a Contact Form in Treeline&nbsp;</a></p>
+          <p><a href="https://www.youtube.com/watch?v=KH5E2TL-_e8">Treeline Sneak Peek </a> <br></p>
+          <p><b>Learning Treeline Docs &amp; Tuts</b></p>
+          <p> <a href="https://treeline.io/documentation/faq">Treeline FAQ</a></p>
+          <p><a href="https://treeline.io/documentation">Treeline Beta Intro</a></p>
+          <p><a href="http://blog.treeline.io/">Super Secret Treeline blog</a><br></p>
+          <p><b>The Sails Treeline Node-Machine Universe </b><br></p>
+          <p><a href="https://www.youtube.com/watch?v=nZKG7hLhbRs">Mike McNeill What is Software? at Platzi Conference</a>&nbsp;</p>
+          <p><a href="https://www.youtube.com/watch?v=72jI0dQx7pw">"Pulling the Plug" Node-Machine Intro </a> <br></p>
+          <p> <a href="https://www.youtube.com/watch?v=MSkM4uqFsMI">Sails Rags to Open Source</a></p>
+          <p><br></p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/9/c/f/600_436334799.jpeg'
+        lat: 37.79999923706055
+      - country: US
+        city: Sunnyvale
+        link: 'http://www.meetup.com/GoLivelabs/'
+        name: 'GoLiveLabs.io - UI, UX & MEAN Stack Experts'
+        description: |-
+          <p>Go-Live Labs is a <b>UI/UX &amp; MEAN Stack</b> focused company, passionate about learning, educating, building great technology products.&nbsp;</p>
+          <p>This group is created to invite local hackers/ programmers/ developers/ designers to Learning Events @ Go-Live Labs.</p>
+          <p><b>Developers</b> will get to learn and practice emerging and popular JavaScript Frameworks like React, AngularJS, Node.js, etc.</p>
+          <p><b>Designers</b> will get to do lot of live product reviews for variety of bay area startups and interact with panel of UX experts.</p>
+          <p><b>Startup</b> <b>CEOs &amp; Product Owners</b> can present their products for UX Critique from a panel of UX experts.</p>
+          <p>We invite you all to join our small, focused and tightly knit community.</p>
+          <p>RA</p>
+          <p>CEO @ Go-Live Labs</p>
+          <p> <br></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: -122.0199966430664
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/8/f/4/600_440970964.jpeg'
+        lat: 37.380001068115234
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Firebase-Toronto/'
+        name: Firebase Toronto
+        description: "<p>This group is for anyone interested in Firebase, a relatively new database service from Google. Firebase can help you quickly build web and mobile applications, get rid of servers and dev-ops, build push-capable real-time applications, scale easily, and save time and money overall. Firebase has a lot of potential for developers and companies that develop their own software. Let's get together and learn about Firebase and all its awesomeness.</p>"
+        lon: -79.37000274658203
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/6/b/e/600_436674974.jpeg'
+        lat: 43.650001525878906
+      - country: US
+        city: Irvine
+        link: 'http://www.meetup.com/ReactJS-OC/'
+        name: ReactJS OC
+        description: '<p>We are an Orange County meetup focused on developing with ReactJS, React Native, and Flux architecture. Our community is open-minded and welcome other front-end MVC enthusiasts too. Interestingly, React Native gives JS developers a way to write native mobile applications so we will cover related topics as well.</p>'
+        lon: -117.75
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/6/c/5/600_436654501.jpeg'
+        lat: 33.7400016784668
+      - country: US
+        city: Miami
+        link: 'http://www.meetup.com/MiamiJS/'
+        name: MiamiJS
+        description: '<p>MiamiJS is a group for JavaScript developers to learn and share. Topics include both client and server side JS: ES6, frameworks and libraries, NodeJS, AngularJS, MeteorJS, mobile development, testing and more...</p>'
+        lon: -80.20999908447266
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/e/9/e/c/600_436799884.jpeg'
+        lat: 25.81999969482422
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/ContainerNode/'
+        name: ContainerNode
+        description: '<p><span>We &lt;3 Node and Docker developers, architects and enthusiasts! Join us for a series of meetups at Hacker Dojo and online dedicated to microservice architecture &amp; orchestration topics based on Node and Docker technology.</span> <br></p>'
+        lon: -122.06999969482422
+        lat: 37.38999938964844
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/React-Native-Los-Angeles/'
+        name: React Native Los Angeles
+        description: '<p>React Native Los Angeles is a meetup dedicated to people building mobile apps with React Native.</p>'
+        lon: -118.27999877929688
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/3/1/8/600_436849944.jpeg'
+        lat: 34.029998779296875
+      - country: US
+        city: Boulder
+        link: 'http://www.meetup.com/RefactorU-Education-Technology/'
+        name: 'RefactorU Education & Technology'
+        description: |-
+          Interested in learning about up-and-coming technology? Want to harness your technical knowledge to develop innovative apps? Looking to network with people across all technological platforms?
+          As a group of passionate people who love making things, solving problems, and spreading knowledge, we want to host and create events that will inspire the community to join us in our creative endeavors.
+        lon: -105.30999755859375
+        lat: 40.040000915527344
+      - country: US
+        city: Sacramento
+        link: 'http://www.meetup.com/Sacramento-ReactJS-Meetup/'
+        name: 'Reacto: The Sacramento ReactJS Meetup'
+        description: "<p>This is a meetup for anyone interested in programming applications with React and React Native. The React.js meetup will bring together the local React community to share ideas, tricks, and triumphs to help make working with the library even more fun. Since this group is new, we're excited to collaborate to make the group useful for everyone, so please don't hesitate to get in touch!</p>"
+        lon: -121.48999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/3/5/a/600_437053146.jpeg'
+        lat: 38.58000183105469
+      - country: US
+        city: Santa Monica
+        link: 'http://www.meetup.com/GirlHack-A-weekly-hack-for-the-ladies/'
+        name: GirlHack -  A weekly hack for the ladies.
+        description: |-
+          <p>Tired of always being the only chick at tech meetups? Tired of for-profit girl-only meetups that cite feminist empowerment as a motivation to program? We started a hack for the ladies who want to keep it real. We don't want to hear about the glass ceiling. We don't want to be asked if our dad/brother/boyfriend got us into programming. We just want to get our hack on. GirlHack is every Thursday. Bring your latest project, bring a friend, bring your A-Game.&nbsp;</p>
+          <p>We have 1weeks and 0weeks. 0weeks are are informal hacks: opportunities to pair, get feedback, or get help. 1weeks are hacks with a purpose, where we will be tackling specific topics, or hosting speakers. Occasionally, we'll host hikes, beach days, or even go rock climbing. And, tech conferences? Ooooh girl. Good times will be had by all. Location independent: We'll host in or around West LA / Santa Monica, until we find an optimal central location for our major patrons. (There's an algorithm for that!)&nbsp;</p>
+          <p>We prefer to keep it open source. Our talks will probably never encompass Microsoft or Oracle technologies, due to cost (just like our meetups, we like our software FREE). Unix based operating systems are assumed (Linux, Mac, BSD). Let us know if you are a Windows user, hoping to come to the dark side. We have distros of Mint or Ubuntu waiting! UEFI notwithstanding. We're interested in: anything .js, ruby, php, python, functional, or c-based. We'll focus on: algorithms, version control, agile, TDD and BDD, workflow, frameworks, security, cryptography, maths, scientific programming, best practices, and more.&nbsp;</p>
+          <p>It's all free, unless there are entry or venue fees. We want to keep this as free as possible. Girlhack has only one request: don't be a dick, and don't have one.</p>
+        lon: -118.5
+        lat: 34.02000045776367
+      - country: US
+        city: Redding
+        link: 'http://www.meetup.com/ReddingGDG/'
+        name: Redding Google Developers Group Meetup
+        description: "This group is for anyone interested in Google's developer technology; generally we focus on Android development with connectivity to Google API's. In addition we tend to enjoy everything from Android, Chrome, App Engine, HTML5, to product APIs like the YouTube and prediction engine."
+        lon: -122.41999816894531
+        lat: 40.560001373291016
+      - country: US
+        city: Houston
+        link: 'http://www.meetup.com/Connected-Car-Houston/'
+        name: Connected Car Houston
+        description: '<p>This group is all about the future of urban mobility, transportation and the connected car. If you love cars (connected ones, autonomous ones, electric ones or even shared ones) this is the group for you. We are a group of tech and car enthusiasts who come together to share the biggest and brightest ideas and companies in the space. We host monthly meetups with some of the most progressive startups, entrepreneurs and companies in Houston. We hope you will join us and look forward to meeting you.</p>'
+        lon: -95.22000122070312
+        lat: 29.719999313354492
+      - country: US
+        city: Fayetteville
+        link: 'http://www.meetup.com/fayettevillejs/'
+        name: '{ fayetteville.js };'
+        description: '{ fayetteville.js }; is a monthly group for anyone interested in the JavaScript programming language. All skill levels are welcome. The purpose of this group is to teach each other about new JavaScript technologies and meet other NWA area developers. For the majority of meetups, we will follow a conference-style approach, where someone in the community will volunteer to present for 20-40 minutes on a particular topic. The remainder of the time will be reserved for socializing (and eating).'
+        lon: -94.1500015258789
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/7/b/5/600_437399317.jpeg'
+        lat: 36.099998474121094
+      - country: CA
+        city: Québec
+        link: 'http://www.meetup.com/ProjectNight/'
+        name: Project Night Québec
+        description: "<p>Ce groupe s'adresse à tous ceux qui sont intéressés par le développement que ce soit pour le Web, mobile, ou logiciel. Que vous soyez débutants ou professionnel, ce groupe est pour tout le monde qui a envie de travailler sur un projet informatique seul ou avec d'autres personnes du groupe, pour but de s'améliorer en tant que programmeurs, ou même se lancer en affaire avec d'autres programmeurs passionnés. Je suis certain qu'il y à beaucoup de potentiel à Québec pour ce groupe. Oh, pour cette soirée, bières et pizza sont au rendez-vous :-)</p>"
+        lon: -71.20999908447266
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/f/9/2/600_437453138.jpeg'
+        lat: 46.810001373291016
+      - country: US
+        city: Fresno
+        link: 'http://www.meetup.com/fresno-node-js/'
+        name: Fresno Node.js Developer Community
+        description: "<p>This is a group for node.js developers located in California's Central Valley.</p>"
+        lon: -119.80000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/9/3/7/600_440199223.jpeg'
+        lat: 36.84000015258789
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/HelloMaker/'
+        name: 'HelloMaker: Coding & Design Workshops'
+        description: "<p>Start learning how to build websites and apps with HTML, CSS and JavaScript through hands-on workshops and mentoring. A lot of people learn programming and design on their own, and having someone to help out when you are stuck or just guide in the right direction is crucial. You can start with some basic projects or choose more advanced topics web development. Don't hesitate to use this time to work on your own project and get help from mentors. All backgrounds and skill levels are welcomed!</p>"
+        lon: -122.44000244140625
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/e/c/4/600_437697028.jpeg'
+        lat: 37.720001220703125
+      - country: US
+        city: Fort Wayne
+        link: 'http://www.meetup.com/Fort-Wayne-Ember-JS-Meetup/'
+        name: Fort Wayne Ember JS Meetup
+        description: This meetup is focused on learning and applying Ember.js to ambitious web apps.
+        lon: -85.12000274658203
+        lat: 41.15999984741211
+      - country: US
+        city: Franklin
+        link: 'http://www.meetup.com/franklin-developer-lunch/'
+        name: 'Franklin Developer Lunch & Learn'
+        description: "<p>Enjoy lunch? Like to learn? We've infused two of your favorite things with high quality talks about web and mobile development. Join us once a month to break bread with like-minded professionals and grow together.</p>"
+        lon: -86.88999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/f/f/9/600_447220953.jpeg'
+        lat: 35.91999816894531
+      - country: US
+        city: Lowell
+        link: 'http://www.meetup.com/modern-javascript/'
+        name: Modern JavaScript
+        description: '<p>Passionate about JavaScript, or want to learn why others are? Modern JavaScript is a regular meetup of technologists looking to improve their development skills and network with others. We have a flexible agenda. Sometimes we have presentations. Sometimes we get together to learn by hacking something together or using NodeSchool.</p>'
+        lon: -71.33999633789062
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/a/b/6/600_439043222.jpeg'
+        lat: 42.650001525878906
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/CodeOregon/'
+        name: Code Oregon
+        description: |-
+          <p>ABOUT:</p>
+          <p>Code Oregon is a free online training opportunity for Oregon residents 18+ to learn to build websites or apps on the Treehouse platform. Code Oregon is a partnership between WorkSystems, inc., Treehouse, and WorkSource Oregon. Code Oregon provides Oregonians 18+ access to coding, training, and job readiness recources.&nbsp;</p>
+          <p><br></p>
+          <p>OUR MEETUPS:</p>
+          <p>Our Meetups will support student learning and engagement by coordinating Meetups for Code Oregon Study Hall sessions, Mentor Sessions, Events, and More!<br></p>
+          <p><br></p>
+          <p>WHY JOIN THIS MEETUP GROUP?</p>
+          <p>Code Oregon Meetup Group Members will be able to RSVP for mentor sessions and other events with limited available space.<br></p>
+          <p><br></p>
+          <p>WHO SHOULD JOIN THIS MEETUP GROUP?</p>
+          <p><span>Those interested in learning to build websites or apps should join the group.&nbsp;Whether you want to become a career coder or just want to learn to code for fun, you're welcome to join!</span></p>
+          <p><span><br></span></p>
+          <p><span>HOW DO I JOIN CODE OREGON?</span></p>
+          <p><span>If you are and Oregon resident and 18+, you are welcome to sign up for free at CodeOregon.org! If you are under 18 or a non-resident, you can sign up as a regular Treehouse Customer.</span></p>
+        lon: -122.69000244140625
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/4/0/b/600_445337419.jpeg'
+        lat: 45.5
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/All-Things-Web-Tech/'
+        name: All Things Web Tech
+        description: |-
+          <p>Our Goals are:</p>
+          <p>- Learn new technologies and build applications/websites</p>
+          <p>- Learn from industry experts to understand different aspects of an application/website build.</p>
+          <p>- Learn the marketing aspects and technologies available to promote the newly built or existing application/website</p>
+          <p>- To make all things happen.</p>
+        lon: -87.66999816894531
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/2/d/c/600_448125788.jpeg'
+        lat: 41.849998474121094
+      - country: US
+        city: Huntington
+        link: 'http://www.meetup.com/Long-Island-js/'
+        name: Long Island JavaScript Group
+        description: |-
+          <p>This is a Meetup group for developers and programmers of all skill levels who are interested in learning and discussing JavaScript together. We cover all things JavaScript, including syntax, frameworks and libraries.&nbsp;</p>
+          <br>
+          <p>Members are encouraged to demonstrate and share their JavaScript projects to serve as a learning experience for the group.</p>
+        lon: -73.41000366210938
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/c/e/a/600_445840170.jpeg'
+        lat: 40.869998931884766
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/InRhythmU/'
+        name: InRhythm U
+        description: '<p>Calling all InRhythm-ers! We produce high quality Meetups which successfully bring all of our teams together. Join us once a month for a a combination of new technology education and some fun socializing.</p>'
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/3/e/7/600_440034247.jpeg'
+        lat: 40.75
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/Enterprise-3-0/'
+        name: 'Enterprise 3.0 (cloud, SaaS, open-source takeover of IT)'
+        description: |-
+          <p>This is a group for anyone interested in the new stack for Enterprise: generally Open Source, Cloud Computing, SaaS.&nbsp;</p>
+          <p>These amazing new tools allow fast, agile, and affordable development of new business apps that beat traditional products from Microsoft, IBM, Oracle, SAP and their ecosystems.&nbsp;</p>
+          <p>Let's meet like-minded people who want to build, invent, design, buy, and generally takeover traditional IT by storm during this momentous convergence of exciting new open source and cloud technology.&nbsp;</p>
+          <img src="http://photos4.meetupstatic.com/photos/event/a/6/f/0/600_438222736.jpeg">
+          <p><a href="http://www.google.com/trends/explore#q=cloud%2C%20ibm%2C%20sap%2C%20oracle&amp;cmpt=q&amp;tz=">http://www.google.com/trends/explore#q=cloud%2C%20ibm%2C%20sap%2C%20oracle&amp;cmpt=q&amp;tz=</a></p>
+          <p>Come join us if you get excited reading these words: Open Source, JavaScript, Web Technology, Mobile Technology, SaaS (Software as a Service), NoSQL, JavaScript Frameworks, mongoDB, node.js, Hadoop, DevOps, AWS , Agile Project Management, Scrum, Agile, User Centered Design, Cloud Computing.</p>
+          <p><img src="http://photos1.meetupstatic.com/photos/event/a/6/d/3/600_438222707.jpeg"></p>
+        lon: -122.69000244140625
+        lat: 45.5
+      - country: US
+        city: Cambridge
+        link: 'http://www.meetup.com/Boston-Code-Dojo-Competitive-Programming/'
+        name: Boston Code Dojo - Competitive Programming
+        description: |-
+          <p>This is a group for people that love programming and love competing. As often as possible, we'll get together and everyone will try to solve coding challenges that test your knowledge of any of the following:</p>
+          <p>- combinatorics<br>- number theory<br>- graph theory<br>- geometry<br>- string analysis<br>- data structures <br>- network security<br>- software explotation</p>
+          <p>We'll focus on moderate level challenges at first. Everyone will have time to attempt the challenge, and then we'll discuss our thoughts, approaches, and solutions as a group. We'll compare execution speed and memory usage, but conceptual elegance will also be heavily weighted. Over time, we'll figure out a belts system, or a judging mechanism, or something, to decide who "wins."</p>
+          <p>Perfect for someone who is prepping for a technical interview, someone who likes to compete, or just wants to improve their programming and reasoning abilities quickly.</p>
+        lon: -71.12999725341797
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/7/4/a/600_439034154.jpeg'
+        lat: 42.38999938964844
+      - country: US
+        city: Atlanta
+        link: 'http://www.meetup.com/DigitalCrafts-Learn-To-Code-Atlanta/'
+        name: 'DigitalCrafts | Learn to Code in Atlanta'
+        description: |-
+          <p>Learning to code? Our Immersive Bootcamp turns beginners into skilled engineers in 16 weeks and over 640 hours of instruction. &nbsp;<span>Look out for our "hack nights", workshops, get-togethers, information sessions, and other other code-generating events and RSVP to join in on the fun!</span></p>
+          <p>We're always looking to help creative and motivated builders breathe life into their ideas. &nbsp;If that's you, be sure to reach out to hello@digitalcrafts.com, give us a ring at 770-858-5806, or just visit <a href="http://digitalcrafts.com/">DigitalCrafts</a>&nbsp;on the web!</p>
+          <p><img src="http://photos1.meetupstatic.com/photos/event/d/0/a/e/600_438293422.jpeg"></p>
+          <p><b><a href="http://www.digitalcrafts.com/immersive-web.html">16 Week Immersive Coding Bootcamp</a></b></p>
+          <p>• Learn Front-end Web Development including HTML, CSS, JavaScript, and much more.&nbsp;</p>
+          <p>•&nbsp;Learn Full-stack Web Development: Javascript, Node.js &amp; the MEAN Stack, and PHP &amp; the LAMP Stack.</p>
+          <p>• Option to also enroll in the rotating elective program covering either User Experience (UX) Design, Native App Development, or Cross Platform Mobile App Development.<br></p>
+          <p><span>Thanks again for your interest, we look forward to chatting!&nbsp;</span><br></p>
+        lon: -84.38999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/c/8/4/600_447623684.jpeg'
+        lat: 33.83000183105469
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/build-with-code/'
+        name: Build With Code - Los Angeles
+        description: |-
+          <p><b>Build with Code hosts free weekly JavaScript and Software Engineering workshops, lectures and pair-programming sessions. Welcome!</b> <br></p>
+          <p>Learn and build with the hard parts of JavaScript every Thursday 6:30pm-8:00pm through intuitive lectures and pair-programming</p>
+          <p>The reason people who only watch programming videos don't become programmers is because they're not programming. Come join other aspiring engineers and start building!</p>
+          <p>In JavaScript the Hard Parts, we cover callbacks,&nbsp;higher-order functions (functional programming with JavaScript), object-oriented programming with JavaScript, closure, scope and execution context</p>
+          <p>Hosted at&nbsp;<a href="https://www.codesmith.io/">Codesmith</a>&nbsp;every week on Thursdays 6:30pm-8:00pm and taught by Codesmith CTO Will Sentance</p>
+          <p>Price: Always free</p>
+          <p>Codesmith&nbsp;(<a href="https://www.codesmith.io/">Codesmith</a>)&nbsp;</p>
+          <p>Codesmith teaches full stack software engineering in JavaScript through a 12 week immersive program.&nbsp;</p>
+          <p>We teach computer science, object-oriented JavaScript, React, Angular, Node, distributed systems and mobile development so our grads can secure mid-to-senior level software engineering positions or launch their own ventures</p>
+          <p>Apply to the program at&nbsp;<a href="http://codesmith.io/apply">codesmith.io/apply</a>. For further questions email&nbsp;<a href="mailto:admissions@codesmith.io">admissions@codesmith.io</a></p>
+          <p><img src="http://photos1.meetupstatic.com/photos/event/c/e/b/8/600_441832920.jpeg"></p>
+          <p> ---</p>
+          <p>JavaScript the Hard Parts is a free workshop series in Los Angeles designed to teach pair programming and essential programming in JavaScript - including callbacks, higher order functions (like how to understand map, reduce, filter and foreach), closure, object-oriented programming in JavaScript and other topics</p>
+          <p>In Codesmith Information sessions, attendees meet with current students and graduates to discuss what it's like to attend Codesmith, what characteristics create the best coding bootcamp in Los Angeles, how to get into Codesmith and how to succeed in the Codesmith interview</p>
+        lon: -118.43000030517578
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/4/d/7/600_440045335.jpeg'
+        lat: 33.9900016784668
+      - country: US
+        city: Tampa
+        link: 'http://www.meetup.com/Ybor-Tech/'
+        name: Ybor Tech
+        description: |-
+          <p>The Ybor Tech Association exists to grow, encourage and support the tech community in Ybor City. <br></p>
+          <p>OpenHack + Ybor City = OpenHack Ybor OpenHack is a meetup with a simple purpose: Code together, on anything. OpenHack works by hosting a meetup in your city that gets programmers of any experience level together to code. Find out more here: <a href="http://openhack.github.io/" class="linkified">http://openhack.github.io/</a> Why Ybor? There's lots of great meetups going on across the Tampa/St. Pete area. I love the relaxed feel and organized chaos of OpenHack and Ybor just feels like the perfect place for this kind of event.</p>
+        lon: -82.33999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/d/f/f/600_446216831.jpeg'
+        lat: 27.979999542236328
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/OpenTable-SF-Engineering/'
+        name: OpenTable Tech Talks
+        description: |-
+          <p>OpenTable hosts regular tech talks and meetups at our San Francisco HQ. &nbsp;With over 200 Engineers worldwide, OpenTable has a lot to offer to the community and we want to share. &nbsp;Topics will likely center on Web Development, Mobile Apps, Data Science and Continuous Delivery. &nbsp;Our tech stack is mostly centered on Node.js, Java and C# but we employ polyglots and you'll hear more and more about Scala, Go and Python to name a few. &nbsp;And we love tools like Mesos, Docker, Puppet and Chef (yes, we use both). &nbsp;So come, eat, drink, socialize and best of all, talk tech with others in the same field.</p>
+          <p><a href="http://blog.opentable.com/">Company Blog</a> |&nbsp;<a href="http://tech.opentable.com/">Tech Blog</a>&nbsp;| <a href="http://www.opentable.com/careers/technology/">Careers</a>&nbsp;|&nbsp;<a href="http://brand.opentable.com/">Brand</a> | <a href="http://pay.opentable.com/">Payments</a></p>
+        lon: -122.4000015258789
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/1/4/9/600_439229001.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/Microservices-Day-NYC-July-13-2015/'
+        name: 'Microservices Day NYC - July 13, 2015'
+        description: |-
+          What is Microservices Day?
+
+          Microservices Day is a conference by the enterprise, for the enterprise. It brings together people from organizations that have adopted (or are planning to adopt) a microservices approach to running their business and focuses on the issues that companies face. It gives participants a forum to discuss and share their experiences with microservices through advice, tips and tricks as well as driving forward both the technology and business community. Come join us at The Altman Building, 135 West 18th Street in New York on July 13th! The event will consist of a range of talks from industry leaders who have deep experience building and operating microservices systems at scale. Panel discussions and active audience participation will be a further part of the event, as the implications of enabling business to innovate at a faster pace than ever before will be a key discussion point. Come join the early adopters at the dawn of a new era in business computing!
+        lon: -73.98999786376953
+        lat: 40.75
+      - country: US
+        city: Atlanta
+        link: 'http://www.meetup.com/Atlanta-IBM-Bluemix-Meetup/'
+        name: Atlanta IBM Bluemix™ Meetup
+        description: '<p><span>IBM Bluemix™ is a new cloud platform as a service (PaaS) developed by IBM. It supports several programming languages and services as well as integrated DevOps to build, run, deploy and manage applications on the cloud. Bluemix™&nbsp;is based on Cloud Foundry open technology and runs on SoftLayer infrastructure. This group serves to help new developers and system operators understand IBM Bluemix™&nbsp;and exchange ideas on how to best implement these services.</span>&nbsp;[Not Affiliated with IBM]. <br></p>'
+        lon: -84.38999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/c/7/0/600_439604144.jpeg'
+        lat: 33.83000183105469
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/New-York-JavaScript-Study-Group/'
+        name: New York JavaScript Study Group
+        description: 'The NY Javascript Study Group, in close co-operation with the Python Study Group, is a peer-driven forum for Javascript users to learn, study, and interact as a community to solve their individual programming tasks. Users of all skill levels are welcome and encouraged to attend.'
+        lon: -74
+        lat: 40.720001220703125
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/JavaScript-Workshops-LA/'
+        name: JavaScript Workshops LA
+        description: '<p>This will be a series of JavaScript Workshops for all levels of developers from beginners to advanced developers. Our courses will offer a good introduction for front end developers to learn best practices for advanced dynamic web pages up to full scale JavaScript web applications.</p>'
+        lon: -118.25
+        lat: 34.040000915527344
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/free-code-camp-sea/'
+        name: Free Code Camp Seattle
+        description: '<p>A community of Seattle campers learning how to program at www.freecodecamp.com. All skill levels are welcome!&nbsp;</p>'
+        lon: -122.37999725341797
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/b/0/f/600_439823311.jpeg'
+        lat: 47.66999816894531
+      - country: CA
+        city: Burlington
+        link: 'http://www.meetup.com/haltonjs/'
+        name: HaltonJS
+        description: '<p>HaltonJS is a monthly event that will occur on the last Thursday @ 7:30pm - 9:30PM of every month starting in September. Location TBD. This is a meetup group for anybody that wants to enhance their knowledge in JavaScript and web technologies.</p>'
+        lon: -79.7699966430664
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/e/6/1/9/600_441058905.jpeg'
+        lat: 43.369998931884766
+      - country: US
+        city: Cambridge
+        link: 'http://www.meetup.com/Cambridge-Developer-Entrepreneur-Networking-Full-Stack/'
+        name: Cambridge Developer Entrepreneur Networking Full Stack
+        description: '<p>This is a developer focused networking group for people who are looking to join together and create a startup. <br>Developers with experience in Node.js, JavaScript Frameworks, mobile, web technology, Redis and overall knowledgable across the web stack should join.</p>'
+        lon: -71.12999725341797
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/b/e/9/600_440379913.jpeg'
+        lat: 42.38999938964844
+      - country: US
+        city: Newport Beach
+        link: 'http://www.meetup.com/IPAs-and-APIs/'
+        name: "IPA's and API's"
+        description: '<p>Craft Beer and Technology. <br>Learn about Applied Programming Interfaces, Javascript, and Nodejs... all while enjoying the best craft beer in Southern California</p>'
+        lon: -117.87000274658203
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/6/f/c/b/600_440668619.jpeg'
+        lat: 33.630001068115234
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Bay-Area-Electron-User-Group/'
+        name: Bay Area Electron User Group
+        description: '<p>Discussions about building cross platform native applications using JavaScript, CSS, and HTML with Electron.</p>'
+        lon: -122.41999816894531
+        lat: 37.779998779296875
+      - country: US
+        city: Denver
+        link: 'http://www.meetup.com/Denver-Cordova-Ionic-Meetup/'
+        name: Denver Cordova/Ionic Meetup
+        description: '<p>This meetup is for AngularJS developers who want to learn more about building hybrid mobile applications using HTML5, CSS, and JavaScript (Angular). We will be covering techniques for developing mobile applications including hands on sessions to get you started.</p>'
+        lon: -105.16000366210938
+        lat: 39.70000076293945
+      - country: US
+        city: Santa Monica
+        link: 'http://www.meetup.com/ReactLA-User-Group/'
+        name: ReactLA User Group
+        description: "<p>ReactJS is one of the many modern JS technology that has fundamentally changed the way we create front end application. Let's get together, share our best practices, and progress this technology forward. Most important of all, let's all help build a strong community of tech enthusiast in LA</p>"
+        lon: -118.5
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/d/9/1/1/600_442555569.jpeg'
+        lat: 34.02000045776367
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/NYC-Women-Who-Go/'
+        name: NYC Women Who Go
+        description: |-
+          <p>This is the New York City Chapter of Women Who Go:&nbsp;<a href="http://www.meetup.com/Women-Who-Go/">http://www.meetup.com/Women-Who-Go/</a>&nbsp;This group is for you if: 1. You identify as a woman, publicly or privately. 2. You have some interest in the Go programming language, or programming in general.</p>
+          <p><img src="http://photos2.meetupstatic.com/photos/event/4/1/0/e/600_440836654.jpeg"></p>
+          <p> <br></p>
+        lon: -73.98999786376953
+        lat: 40.75
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/SD-Women-Who-Go/'
+        name: SD Women Who Go
+        description: |-
+          <p>This is the San Diego County Chapter of Women Who Go: <a href="http://www.meetup.com/Women-Who-Go/" class="linkified">http://www.meetup.com/Women-Who-Go/</a> This group is for you if: 1. You identify as a woman, publicly or privately. 2. You have some interest in the Go programming language, or programming in general.</p>
+          <p><span>We tweet from <a href="http://twitter.com/womenwhogo_sd" class="linkified">http://twitter.com/womenwhogo_sd</a></span> <br></p>
+          <p>We also hangout on Slack, come chat with us over on the #general or #sandiego channel. Invite link: <a href="http://bit.ly/wwg-slack">http://bit.ly/wwg-slack</a> <br></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: -117.16999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/0/d/0/600_441469360.jpeg'
+        lat: 32.720001220703125
+      - country: US
+        city: Manchester
+        link: 'http://www.meetup.com/OpenSourceNH/'
+        name: Open Source NH
+        description: |-
+          <p>Open Source NH is a networking and learning resource for open source software developers in NH. This group is Programming Language, licence, OS, and text editor agnostic. Meaning the "what" is more important than the "how" in regards to joining the group. That is to say the group is generally open to those who develop code they release to the public. The group is also open to those who are new to programming and looking opportunities to learn.</p>
+          <p>Our Meetings are normally either social (find help, get help) or hands on (workshop or group project) maybe a mix of both.</p>
+          <p>The regular "Find help, get help" meeting format is a bit different but simple. Members suggest issues they are dealing with or impending interest on the meet-up event page. Depending on what is appropriate, the meeting may break out into separate groups for individual topics or just have a full group discussion. The main goal is having the opportunity to get new perspective, with the recognition that solutions or complete understanding may still be hard to come by. As a default in the absence of topics or being involved in one, the meeting is social/networking. Workshops or group projects may come about based on member interest.</p>
+        lon: -71.47000122070312
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/5/8/e/f/600_441262767.jpeg'
+        lat: 42.9900016784668
+      - country: US
+        city: Greenville
+        link: 'http://www.meetup.com/NodeGreenville/'
+        name: NodeGreenville
+        description: |-
+          <p>We are a group of developers in Greenville, SC who are excited about working with Node.js. &nbsp;We will meet weekly on Wednesdays. The second Wednesday of the month will feature three 20-minute presentations. &nbsp;All other meetups are "working groups," so bring your project and get help from other developers in the community.</p>
+          <p>If you'd like to know more about node core, running local build tools like bower, or hosting your production site on express, come join us.</p>
+        lon: -82.4000015258789
+        lat: 34.900001525878906
+      - country: US
+        city: Dallas
+        link: 'http://www.meetup.com/DFW-Front-end-development/'
+        name: DFW Front end development
+        description: '<p>Meet other front end developers to share your knowledge and discuss frameworks, such as AngularJS and front end ecosystems toolsets like Bower, npm, gulp and more. All skill-levels, platform backgrounds and languages welcome.</p>'
+        lon: -96.80000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/5/c/2/1/600_442823585.jpeg'
+        lat: 32.790000915527344
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Austin-ElectronJs-Meetup/'
+        name: Austin ElectronJs Meetup
+        description: |-
+          <p>All things ElectronJs and writing cross-platform, desktop apps using web dev technologies! Exciting times!</p>
+          <p>I'd like this meetup group to grow in terms of gradually digging deeper and deeper into developing cross-platform, desktop apps using ElectronJs--NodeJs, Chromium, and other web technologies. I expect great things from our community and hope I can provide the same for us all.</p>
+          <p>Not sure what ElectronJs is? Think&nbsp;web development&nbsp;in&nbsp;NodeJs, but for&nbsp;desktop&nbsp;apps. &nbsp;We'll get into the details here. &nbsp;So, please come join us! &nbsp;There are many production-grade, ElectronJs apps out there. &nbsp;Best example is&nbsp;<a href="https://atom.io/">Atom</a>, the text editor by GitHub that is now a competitor to&nbsp;<a href="http://www.sublimetext.com/">Sublime Text</a>.</p>
+          <br>
+        lon: -97.73999786376953
+        lat: 30.270000457763672
+      - country: US
+        city: Orlando
+        link: 'http://www.meetup.com/Free-Code-Camp-Orlando/'
+        name: 'Free Code Camp - Orlando, FL'
+        description: '<p>A community of Orlando Free Code Campers learning how to program at www.freecodecamp.com. All skill levels are welcome!</p>'
+        lon: -81.16999816894531
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/3/2/9/600_441377193.jpeg'
+        lat: 28.399999618530273
+      - country: US
+        city: Boulder
+        link: 'http://www.meetup.com/CodeCraftSchool/'
+        name: 'CodeCraft School & Web Development Community'
+        description: "<p>CodeCraft School is a new coding bootcamp in Boulder, Colorado that leverages Boulder Digital Arts' decade of experience training digital professionals. We offer a 10-week Full-Stack JavaScript Web Development bootcamp to get you started as a junior developer.\_</p>\n<p><span>CodeCraft School will be hosting open houses periodically throughout the year and we wanted to invite the meetup community to join us. We will be having interactive discussions on topics ranging from HTML, CSS, and advanced topics like Angular.js. Everyone is invited from professionals coders to those looking to learn more about programming and everyone in between.\_</span></p>\n<p><span>CodeCraft School's bootcamp is more than just learning to code. Our entire team is focused on empowering and transforming your future with world-class instruction, small class sizes, one-on-one attention, and industry connections that match your goals. As an extra benefit for our students, we offer free registration to all related workshops at Boulder Digital Arts that can help you prepare or fill in gaps in your new skills.</span> <br></p>"
+        lon: -105.20999908447266
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/4/7/4/8/600_441618248.jpeg'
+        lat: 40.04999923706055
+      - country: US
+        city: Bellevue
+        link: 'http://www.meetup.com/BellevueJS/'
+        name: BellevueJS
+        description: |-
+          BellevueJS provides an opportunity to meet other local JavaScripters, share knowledge, and learn about the latest in JavaScript on the Eastside.
+
+          How often would you like to meet? What would you like to learn? Would you like to sponsor a meetup in Bellevue? Join us and discuss!
+        lon: -122.20999908447266
+        lat: 47.619998931884766
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/Cloud-Native-New-York/'
+        name: Cloud Native New York
+        description: '<p>Discuss everything about building and utilizing cloud native application architectures and platforms. Topics on interest also include Micro Services, DevOps, Container technologies and platforms</p>'
+        lon: -74
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/9/8/4/600_444347492.jpeg'
+        lat: 40.7400016784668
+      - country: US
+        city: San Marcos
+        link: 'http://www.meetup.com/San-Marcos-Tech-Meetup/'
+        name: San Marcos Tech Meetup
+        description: "I can't believe that there isn't a tech meetup in San Marcos. This group is to bring together tech enthusiast for the so that we can share information about new technology. Find others in the community that we can collaborate with. Get information on the ins/outs of startups. Show off our latest iot device. And on and on."
+        lon: -97.94999694824219
+        lat: 29.8799991607666
+      - country: US
+        city: Mc Lean
+        link: 'http://www.meetup.com/tysons-js/'
+        name: tysons.js
+        description: '<p>"This group is for anyone who is interested in JavaScript and is in the Tysons, VA area. All skill levels are welcome. We get together, have hack nights, product demos, discuss new frameworks / libraries, eat, drink, and be merry."</p>'
+        lon: -77.18000030517578
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/1/6/9/8/600_444905784.jpeg'
+        lat: 38.93000030517578
+      - country: US
+        city: Santa Monica
+        link: 'http://www.meetup.com/LA-Software-Craftsmanship/'
+        name: LA Software Craftsmanship
+        description: |-
+          <p>This is a group for people interested in <b>high quality code</b>... doesn't really matter what language, what methodology, or what kind of environment you work in (big enterprise, startup, open source, etc.). All that matters is that you're interested in getting together now and then (in real life or virtually) to talk about great code and what makes it great.</p>
+          <p>BTW, I know there's a "thing" around software craftsmanship (not to mention a conference coming to LA in 2015) and we should talk about that movement. But the time we spend together in these Meetups should be much broader, focused only on high quality code and not centered around any manifestos.</p>
+          <p>Long term, the goal is to give members the tools (and inspire them) to write amazing code&nbsp;accomplish by learning from others, study, mentorship, hands on experience, and open discussion.&nbsp;</p>
+        lon: -118.5
+        lat: 34.02000045776367
+      - country: US
+        city: Palo Alto
+        link: 'http://www.meetup.com/Dans-Linux-JavaScript-Class/'
+        name: "Dan's Linux JavaScript Class"
+        description: 'Each Meetup starts with a 40 minute lecture related to running JavaScript apps on Linux servers. Also we cover serving JavaScript (and other assets) to browsers from Linux servers. After the lecture, we pair up and work on a code challenge related to the Lecture. This Meetup is aimed at developers who want to pitch interactive product ideas (usually mobile apps) to investors. Building an awesome prototype which behaves well in a mobile browser is more effective than a slide-deck and elevator pitch. All skill levels welcome. Bring your laptop.'
+        lon: -122.1500015258789
+        lat: 37.439998626708984
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/Crowdcoders-Coworking-Space/'
+        name: Crowdcoders Coworking Space
+        description: |-
+          <p>Crowdfunder is opening its doors to coders needing a place to work on their own development project. Coders of all experience levels are welcome.&nbsp;</p>
+          <p>Come ready to code!&nbsp;</p>
+          <p>Don't be shy and introduce yourself when you arrive.</p>
+          <p>Need tunes to help you code? Bring headphones to limit noise level and &nbsp;distractions for others who might be sensitive . This is a co-working space &nbsp;so remember to respect your fellow Crowdcoders. If you need to take or make a phone call longer than a few minutes, take it outside.&nbsp; <br></p>
+          <p> <br> <br></p>
+        lon: -118.43000030517578
+        lat: 33.9900016784668
+      - country: US
+        city: Ann Arbor
+        link: 'http://www.meetup.com/Free-Code-Camp-Ann-Arbor/'
+        name: Free Code Camp Ann Arbor
+        description: |-
+          <p>This is a group for anyone learning (or interested in learning) web development and coding through the free JavaScript based curriculum at&nbsp;<a href="http://www.freecodecamp.com">freecodecamp.com</a>.</p>
+          <p><span>This meetup will provide opportunities to meet other campers in the Ann Arbor area, get help, and find people to pair program with.</span></p>
+          <p>Check out our <span>local Facebook page at: &nbsp;</span><a href="https://www.facebook.com/groups/free.code.camp.ann.arbor/">https://www.facebook.com/groups/free.code.camp.ann.arbor/</a></p>
+        lon: -83.80999755859375
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/b/f/3/600_441855347.jpeg'
+        lat: 42.27000045776367
+      - country: CA
+        city: Vancouver
+        link: 'http://www.meetup.com/ReactJS-Vancouver-Meetup/'
+        name: ReactJS Vancouver Meetup
+        description: "<p>With an increasing number of Vancouver developers who work with React (<a href=\"http://facebook.github.io/react/\" class=\"linkified\">http://facebook.github.io/react/</a>), it's time to get together and share our experiences, projects, issues, tips, etc. &lt;br&gt;</p> \n<p>If you work with React, React Native, React Hot Loader, React Router, Flux, you name it or simply want to get an idea of what others do with these technologies, please join us at one of our next events.</p> \n<p>For speaker or hosting suggestions, please contact us so we can plan.</p>"
+        lon: -123.12000274658203
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/b/8/2/600_441888002.jpeg'
+        lat: 49.279998779296875
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/fullstack360/'
+        name: FS360 Development Workshops
+        description: '<p>Want to learn frontend development, backend development and iOS programming? In other words, want to be a full stack developer? This meetup is dedicated teaching students all areas of the "stack." Each week, we will demo a new concept live and explain the basics behind the implementation. Join us Mondays from 6:30pm to 9:00pm to learn something new, meet like-minded people, and begin your journey to becoming a full stack developer</p>'
+        lon: -73.9800033569336
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/5/b/1/600_447414705.jpeg'
+        lat: 40.75
+      - country: US
+        city: Burlington
+        link: 'http://www.meetup.com/Greater-Boston-Enterprise-UI/'
+        name: Greater Boston Enterprise UI
+        description: "Greater Boston Enterprise UI is a Meetup group for anyone who is interested in learning, understanding and sharing about topics surrounding developing User Interface in the enterprise context. We define UI as a large spectrum that spans across technology stacks and could include the various JavaScript frameworks, HTML, CSS, Node.js, tooling &amp; automation (Grunt &amp; gulp), and testing (Selenium and Webdriver). Basically anything that would face a UI developer on a daily basis. Our goal is to connect passionate individuals who care about making innovative and user-focused interfaces and experiences that have a big impact. If you're interested in speaking at our events, please reach out to us. We look forward to hearing from you!"
+        lon: -71.19999694824219
+        lat: 42.5099983215332
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/ave-B-Social-Javascript/'
+        name: (ave) B Social Javascript
+        description: '<p>This group is to serve NYC developers who want an alternative to coding in the office or at home by combining elements of co-working with the social component of a hackathon. If you like JavaScript, come join us for fast internet, coffee, and a couple talks in a cool coffeeshop / bar in the East Village, The Roost.</p>'
+        lon: -74
+        lat: 40.720001220703125
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/Seattle-MEAN-Stack-Developers/'
+        name: Seattle MEAN Stack Developers
+        description: "We're a group dedicated to all things MongoDB, Express, Angular, and Node. If you're using any part of the MEAN stack we want you to come code with us! All levels of experience are welcome, we aim to offer a welcoming environment for working, learning, and socializing with other MEAN devs."
+        lon: -122.31999969482422
+        lat: 47.630001068115234
+      - country: US
+        city: Cookeville
+        link: 'http://www.meetup.com/Friday-Night-Hacks-at-the-Biz-Foundry/'
+        name: Friday Night Hacks at the Biz Foundry
+        description: "Ever had the desire to code with other programmers? Want to learn from others just a bit ahead of you? Or maybe you'd like to show off your awesome workflow: Friday Night Hacks is the night for you! We are a community about programming and learning from each other while contributing back to the Cookeville community through projects and super cool software! Come out and be a part of an awesome community."
+        lon: -85.5199966430664
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/4/3/1/600_442546129.jpeg'
+        lat: 36.20000076293945
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Austin-ReactJS-Native-Meetup/'
+        name: 'Austin ReactJS & Native Meetup'
+        description: |-
+          <p>This group is for those who are curious about or are actively using ReactJS and React Native. We plan on hosting demos, instructional lectures, and social events for those interested in learning more about this Javascript framework.&nbsp;</p>
+          <p><br></p>
+          <p>For more information about ReactJS and React Native, check out these links: <a href="https://facebook.github.io/react/" class="linkified">https://facebook.github.io/react/</a>&nbsp;and&nbsp;<a href="https://facebook.github.io/react-native/" class="linkified">https://facebook.github.io/react-native/</a></p>
+        lon: -97.73999786376953
+        lat: 30.270000457763672
+      - country: US
+        city: Dublin
+        link: 'http://www.meetup.com/BayOne-Labs/'
+        name: BayOne Labs
+        description: BayOne Labs is extremely delighted to announce the workshop series for the IT professionals and enthusiasts. In this series we will take deep dive into the amazing world of technologies inspiring numerous individuals and companies in the domain of bigdata full-stack engineering and cloud computing. The intent is to share the practical wisdom for technologies and build a knowledge-sharing platform for the booming high-tech community in the bay area.
+        lon: -121.93000030517578
+        lat: 37.709999084472656
+      - country: US
+        city: Orem
+        link: 'http://www.meetup.com/CodeforOdin/'
+        name: Code for Odin
+        description: "<p>What better way to please Odin than to be c-Odin-g on Wednesday (Odin's day) ? Come to our weekly casual coding meetup! Everyone from beginners to experts are invited to come. The casual and relaxed setting makes it a great time to meet other coders, show off your project to your peers, get protips from experts, or to just relax and code with friends. We like to code together. Join us!</p>"
+        lon: -111.69999694824219
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/a/6/7/600_443555431.jpeg'
+        lat: 40.31999969482422
+      - country: US
+        city: Bayside
+        link: 'http://www.meetup.com/Queens-Bayside-Sofware-Development-and-Design/'
+        name: Queens Software Development and Design
+        description: '<p>Computer programmers, Web developers of queens unite. No more long commutes to the city to get and give help on your stalled projects. Why not create our own group here in queens where we can meet-up*, learn from each other, help each other and have a fun time doing it. This group is for anyone interested in software development/computer programming, specifically for those living in the queens area who like me have had to go to meet-ups in the city and are looking to stay closer to home.</p>'
+        lon: -73.77999877929688
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/3/8/2/3/600_444254371.jpeg'
+        lat: 40.790000915527344
+      - country: US
+        city: Provo
+        link: 'http://www.meetup.com/GUN-User-Group/'
+        name: GUN User Group
+        description: |-
+          <p>This group is for anyone interested in databases from start-up entrepreneurs to web developers. GUN is a database written entirely in JavaScript and super hackable (MIT/Apache2/ZLIB) with these cool features: <br></p>
+          <p>•&nbsp;Like Firebase? GUN is an Open Source Firebase, with all the realtime goodies included!</p>
+          <p>•&nbsp;Like Bitcoin? GUN is fully peer-to-peer, which means no DevOps or SysAdmin work is required!</p>
+          <p>•&nbsp;It is Offline-First so you never have to worry about writing ajax or scared if your app disconnects.</p>
+          <p>•&nbsp;Can't stand the NoSQL/SQL debate? GUN is both relational and document oriented, using graphs! <br></p>
+          <p>We're just going to have a chill get-together, eat food, talk about crazy mad science JavaScript, and learn about gun, get started using gun, and hack on gun! Until then, check out <a>http://gun.js.org</a> and <a href="https://github.com/amark/gun">https://github.com/amark/gun</a>, and feel free to contact us at <a href="https://gitter.im/amark/gun">https://gitter.im/amark/gun</a> or <a href="https://groups.google.com/forum/#!forum/g-u-n">https://groups.google.com/forum/#!forum/g-u-n</a>. <br></p>
+        lon: -111.62999725341797
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/c/e/a/f/600_446572911.jpeg'
+        lat: 40.220001220703125
+      - country: US
+        city: Denver
+        link: 'http://www.meetup.com/NodeBots-Colorado/'
+        name: NodeBots Colorado
+        description: "We are a group of JavaScript and hardware enthusiasts working to create an inclusive community for anyone to begin or continue learning about NodeBots. You don't need to know anything about hardware or programming to join. We can show you how to build a robot in under an hour and would love to have you join us!"
+        lon: -105.08000183105469
+        lat: 39.70000076293945
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/Los-Angeles-Amazon-Echo-Developer-Meetup/'
+        name: Los Angeles Amazon Echo Developer Meetup
+        description: '<p>This is a meetup for anyone interested in building apps for the Amazon Echo using the Alexa Skills Kit (ASK) and Amazon Voice Service (AVS).</p>'
+        lon: -118.23999786376953
+        lat: 33.970001220703125
+      - country: US
+        city: Cambridge
+        link: 'http://www.meetup.com/Electron-Atom/'
+        name: Electron/Atom
+        description: A place where developers and entrepreneurs can share knowledge on developing apps in Electron and on using or developing for the Atom IDE.
+        lon: -71.0999984741211
+        lat: 42.369998931884766
+      - country: US
+        city: San Antonio
+        link: 'http://www.meetup.com/San-Antonio-Meteor-Meetup/'
+        name: San Antonio Meteor Meetup
+        description: "This is a group for anyone interested in Meteor and its associated technologies, like Node.js, MongoDB, Angular.js, React.js, Jade, Spacebars, Famous-Views, JSON, etc. It's all about developing modern interactive web applications. All skill levels are welcome. If you are, or want to be, a Meteorite, then this group is for you!"
+        lon: -98.75
+        lat: 29.459999084472656
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Free-Code-Camp-Austin/'
+        name: Free Code Camp Austin
+        description: '<p>This is a study and networking group specifically for folks in the Austin, TX area who are learning web development through www.freecodecamp.com. This group is committed to creating opportunities for members to socialize, team up on projects, and keep one another accountable on our coding journey. Check out our local Facebook page at: <a href="https://www.facebook.com/groups/free.code.camp.austin/" class="linkified">https://www.facebook.com/groups/free.code.camp.austin/</a></p>'
+        lon: -97.73999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/8/6/e/600_443871310.jpeg'
+        lat: 30.270000457763672
+      - country: US
+        city: Indianapolis
+        link: 'http://www.meetup.com/High-Fives-Happy-Hour/'
+        name: High Fives Happy Hour
+        description: "<p>Join us for the High Fives Happy Hour at the High Alpha offices for free food, drinks, and awesome people. This is a casual event that will occur quarterly. We want it to be a fun get-together with Indy's Tech community to foster new relationships or catch up with old friends. People are free to come and go as they please. The event will start at 4:30 and run to 7:30.</p>"
+        lon: -86.18000030517578
+        lat: 39.88999938964844
+      - country: US
+        city: Gulf Breeze
+        link: 'http://www.meetup.com/Mobile-Home-Brew-Computer-Club/'
+        name: Homebrew Computer Club
+        description: '<p>Good folks interested in working towards developing startups in the area of mobile computing with an emphasis on social, AI, and machine learning technologies. Creative types from all disciplines, serious folks, with an eye on seeing computing targeted towards bettering the lives of all of humanity. Its more important to have motivation than knowledge. Come one, come all, but come with motivation. There is an emphasis on good here. You either are or your not and you already know it. <br></p>'
+        lon: -87.08999633789062
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/2/2/2/600_444008738.jpeg'
+        lat: 30.3799991607666
+      - country: CA
+        city: Vancouver
+        link: 'http://www.meetup.com/ionicvancouver/'
+        name: Ionic Vancouver
+        description: |-
+          <p>This is the official <b>Vancouver</b> meetup group for <b>Ionic Framework</b>. This Meetup is for anyone using or interested in using Ionic to build mobile hybrid apps using modern web technologies. We welcome attendees of all skill levels and would love to hear about projects and apps that you are working on. If you would like to present something related to Ionic at an upcoming event, please message admin via the Ionic Vancouver Meetup board.&nbsp;</p>
+          <p>---</p>
+          <p><span><b>Code of Conduct</b>:</span></p>
+          <p><span><i>Ionic Vancouver is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, or religion (or lack thereof). We do not tolerate harassment of event participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter and other online media. Event participants violating these rules may be sanctioned or expelled from the event and all future event at the discretion of the organisers. (adapted from confcodeofconduct.com)</i></span> <br></p>
+        lon: -123.04000091552734
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/3/6/9/e/600_444133982.jpeg'
+        lat: 49.279998779296875
+      - country: US
+        city: Dallas
+        link: 'http://www.meetup.com/DFW-Improving-Web-Mobile-App-Performance-w-New-Relic-APM/'
+        name: 'DFW Improving Web & Mobile App Performance w/New Relic APM'
+        description: 'A group for learning, sharing, collaborating, networking - and having fun sponsored by New Relic. This is for anyone developing critical applications / or responsible for running applications - a true DevOps oriented group. We focus on sharing, learning, events, and also fun-oriented events. If you are a Developer, Product Manager, Digital Innovation specialist, or you run Apps in Production this is the group for you! www.newrelic.com/apm'
+        lon: -96.80000305175781
+        lat: 32.790000915527344
+      - country: US
+        city: Phoenix
+        link: 'http://www.meetup.com/Learn-To-Code-PHX/'
+        name: Learn To Code Phoenix
+        description: 'Learn to code in a fun safe environment in vibrant downtown Phoenix! '
+        lon: -112.06999969482422
+        lat: 33.45000076293945
+      - country: CA
+        city: Montréal
+        link: 'http://www.meetup.com/decodemtl/'
+        name: 'DecodeMTL: Learn to Code'
+        description: |-
+          <p><a href="http://www.decodemtl.com">DecodeMTL</a> is the hub for digital education in Montreal. Join us for networking events, workshops, and industry talks with Montreal's top programmers. We are a community of creators, passionate about building beautiful and meaningful things with technology.&nbsp;</p>
+          <p>About DecodeMTL:&nbsp;</p>
+          <p>DecodeMTL is a full-stack javascript programming bootcamp located in Montreal, Canada. Accepted students run through an intensive 8 week program designed to turn them into job ready web developers.</p>
+        lon: -73.55000305175781
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/d/c/9/600_444284489.jpeg'
+        lat: 45.5099983215332
+      - country: US
+        city: Mountain View
+        link: 'http://www.meetup.com/World-Cappuccino-Meetup/'
+        name: Worldwide Cappuccino Meetup
+        description: '<p>This is a group for anyone interested in Cappuccino (<a href="http://www.cappuccino-project.org" class="linkified">http://www.cappuccino-project.org</a>). All skills levels are welcome. Cappuccino is an open source framework that makes it easy to build desktop-caliber applications that run in a web browser. Meetups are going to be organized around the world and hopefully regularly ! During the Meetups, different topics can be covered like : How a Companies are using it ? How to test a Cappuccino Application ? How do deal with large application ? Demo of libraries etc...</p>'
+        lon: -122.05000305175781
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/6/f/8/600_444346840.jpeg'
+        lat: 37.40999984741211
+      - country: US
+        city: Tallahassee
+        link: 'http://www.meetup.com/beerjs-tallahassee/'
+        name: Beer.js Tallahassee
+        description: |-
+          <p><span>A popular Silicon Valley Meetup, Beer.js, has come to Tallahassee!&nbsp;</span></p>
+          <p><span>Beer.js - Tallahassee hosts events involving the two of mankind's greatest inventions; Beer and JavaScript. Watch us at&nbsp;<a href="https://github.com/beerjs/tallahassee" class="linkified">https://github.com/beerjs/tallahassee</a></span>&nbsp;for more information. <br></p>
+        lon: -84.04000091552734
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/a/2/600_444302722.jpeg'
+        lat: 30.600000381469727
+      - country: US
+        city: Reston
+        link: 'http://www.meetup.com/Pragmatic-Innovators/'
+        name: Pragmatic Innovators
+        description: "This is a group for anyone interested in leading software development languages, technologies, and practices. All skill levels are welcome. Topics discussed will include ReactJS, ReactJS Native, Scala, Single-Page Application Technologies, Mobile Application Development, Web Design, and Data Analytics. In-Person meetups will be held at our sponsor's (Pragmatics) corporate office in Reston."
+        lon: -77.33999633789062
+        lat: 38.959999084472656
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/Mueller-Technology-Collablorative/'
+        name: Mueller Technology Collablorative
+        description: '<p>Come join us for socializing and learning. Our group is focused on technoogy and sharing. Whether you are a software developer working with Node.js or a graphic designer living in InDesign, you will find people who share your love of technology culture.</p>'
+        lon: -97.75
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/e/4/d/600_444340525.jpeg'
+        lat: 30.219999313354492
+      - country: US
+        city: Fresno
+        link: 'http://www.meetup.com/Free-Code-Camp-Fresno/'
+        name: Free Code Camp Fresno
+        description: 'This is the Fresno chapter of Free Code Camp. Share your knowledge, learn new stuff, support one another through tough times. We also offer opportunities to give/hear a talk, pair up on a project, hangout and talk about code, and so much more. '
+        lon: -119.80000305175781
+        lat: 36.84000015258789
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/Portland-New-Relic-User-Group/'
+        name: Portland New Relic User Group
+        description: "Calling all Portland New Relic Users! This user group is designed to foster the community and connect you with the resources & peers you need to get the most out of New Relic's software analytics suite.\n\nSome of topics we'll discuss:\n- Application Performance Monitoring\n- Understanding Apdex\n- Custom Dashboards & Alerts\n- New Relic Insights / NRQL\n- More!\n\nEach event features talks from New Relic users and pros alike, with ample time for food, drinks, networking, and discussion. This is a great opportunity to get to know and learn best practices from other New Relic users in the area. \n\nAll New Relic users or those interested are welcome!"
+        lon: -122.69000244140625
+        lat: 45.5
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Hire-Front-End-Developers/'
+        name: Hire Front End Developers
+        description: |-
+          <p>It's never been a better time to be a front end developer, or a more challenging time for companies to find an appropriate fit in the Bay Area. If you'd like to meet enthusiasts of technologies like angular.js, ember.js, meeteor, react, html5, css, UX, and other front end tools, join us!</p>
+          <p>We're excited to provide free opportunities for talent and companies to meet in the real world,&nbsp;and pair awesome front end devs with competitive and interesting companies. Typical evenings include interviews of top companies and pitches by startups that are looking for talent, followed by a mixer.</p>
+          <p>All companies in attendance offer competitive salaries. We're here to make real connections between equals. Top flight companies meeting top talent is what we're about.<br></p>
+          <p><span>Some presenting companies from past events include: HumbleBundle, Enjoytech, Adobe, Tapjoy, MatterMark, Razer, and many more.</span> <br></p>
+        lon: -122.41999816894531
+        lat: 37.779998779296875
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Hire-node-JS-developers/'
+        name: Hire Node Developers
+        description: |-
+          <p>It's never been a better time to be node developer, or a more challenging time for companies to find an appropriate fit in the Bay Area. We're excited to provide free opportunities for talent and companies to meet in the real world, and pair awesome server side devs with competitive and interesting companies.&nbsp;</p>
+          <p><span>We're excited to provide free opportunities for talent and companies to meet in the real world,&nbsp;and pair awesome front end devs with competitive and interesting companies. Typical evenings include interviews of top companies and pitches by startups that are looking for talent, followed by a mixer.<br></span></p>
+          <p><span>All companies in attendance offer competitive salaries. We're here to make real connections between equals. Top flight companies meeting top talent is what we're about.<br></span></p>
+          <p><span>Some presenting companies from past events include: HumbleBundle, Enjoytech, Adobe, Tapjoy, MatterMark, Razer, and many more.</span> <br></p>
+          <p><br></p>
+        lon: -122.41999816894531
+        lat: 37.779998779296875
+      - country: US
+        city: Milwaukee
+        link: 'http://www.meetup.com/ReactJS-Wisconsin/'
+        name: ReactJS Wisconsin Meetup
+        description: |-
+          <p><span>ReactJS is an incredible JavaScript library started by Facebook. &nbsp;Join us if you'd like to learn more or if you have your own ReactJs experience to share that others can benefit from.</span> <br></p>
+          <p>We're focused on all things ReactJS - on client or server, for html, canvas or other.</p>
+          <p><a href="http://facebook.github.io/react/" class="linkified">http://facebook.github.io/react/</a></p>
+          <p> <br></p>
+        lon: -87.9000015258789
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/a/0/b/600_447159435.jpeg'
+        lat: 43.04999923706055
+      - country: US
+        city: Saint Louis
+        link: 'http://www.meetup.com/node-jSTL/'
+        name: node.jSTL
+        description: '<p>Interested in building apps, orchestrating thousands of IoT devices, or building incredibly robust architecture? Want to learn about the language powering Netflix, Paypal, and dozens of other tech giants? Join us as we talk and learn about the incredibly popular Node.JS.</p>'
+        lon: -90.20999908447266
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/d/6/2/600_446088482.jpeg'
+        lat: 38.630001068115234
+      - country: US
+        city: Tempe
+        link: 'http://www.meetup.com/EmberJS-Phoenix/'
+        name: EmberJS-Phoenix
+        description: '<p>A meetup to discuss aspects of the Ember JS framework</p>'
+        lon: -111.93000030517578
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/c/5/c/600_445407740.jpeg'
+        lat: 33.369998931884766
+      - country: US
+        city: Orlando
+        link: 'http://www.meetup.com/Orlando-Slack-Developers-Meetup/'
+        name: Orlando Slack Developers Meetup
+        description: '<p>A place for programmers, product designers, and slack interested people to come get updated on what is happening inside the wonderful world of Slack Development.</p>'
+        lon: -81.37000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/8/f/d/600_447002301.jpeg'
+        lat: 28.540000915527344
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Serverless/'
+        name: Serverless
+        description: "A group for anyone interested in building web, mobile and Internet-of-Things applications with serverless architectures using the Serverless Framework and more! We'll focus heavily on Amazon Web Services and discuss AWS Lambda as the focal point of AWS."
+        lon: -122.41999816894531
+        lat: 37.779998779296875
+      - country: CA
+        city: Montréal
+        link: 'http://www.meetup.com/Oracle-Developers-Montreal/'
+        name: Oracle Developers Montréal
+        description: '<p>This is a group for technology enthusiasts and developers of all skill levels. The group is designed to bring you updates and innovations in technology from Oracle through meetings, events, workshops and hands-on experiences.</p>'
+        lon: -73.56999969482422
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/9/e/a/600_447198922.jpeg'
+        lat: 45.5
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/SF-JavaScript-Workshops/'
+        name: SF JavaScript Workshops
+        description: |-
+          <p>Welcome! Learning JavaScript in SF? Catching up on the latest framework?&nbsp;<span>We host workshops in React, Node, and Angular to help frontend developers get up to speed quickly.</span></p>
+          <p>Let us know if you want a workshop you don't see, and we will try and find one for you!</p>
+          <p>Best,</p>
+          <p>Frank Kotsianas</p>
+          <p>Organizer</p>
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/1/b/d/4/600_445807124.jpeg'
+        lat: 37.790000915527344
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/JavaScript-and-the-Internet-of-Things/'
+        name: JavaScript and the Internet of Things Meetup
+        description: |-
+          <p>Want to talk about Node.js on the Raspberry Pi or Tessel 2? How about JavaScript MicroControllers like the Espruino?</p>
+          <p>All meetup attendies, sponsors and speakers agree to abide by the <a href="http://berlincodeofconduct.org">code of conduct</a>.</p>
+        lon: -122.63999938964844
+        lat: 45.54999923706055
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Real-World-React/'
+        name: Real World React
+        description: 'Talks and workshops about using React in real-world, production applications.'
+        lon: -122.41000366210938
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/4/1/8/600_445906104.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: Pomona
+        link: 'http://www.meetup.com/Pomona_Free_Code_Camp/'
+        name: Pomona Free Code Camp
+        description: '<p>Learn code through free curriculum online @ <a href="http://www.freecodecamp.com/">freecodecamp.com</a>. Join this community for making new friends, gaining support, and participating in live pair programming sessions. <br></p>'
+        lon: -117.73999786376953
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/d/2/a/c/600_446753932.jpeg'
+        lat: 34.08000183105469
+      - country: US
+        city: Santa Monica
+        link: 'http://www.meetup.com/API-Craft-Los-Angeles/'
+        name: API Craft Los Angeles
+        description: |-
+          <p>A meetup group for people who design and build and test APIs - We &lt;3 APIs!</p>
+          <p>Topics for meetups include:</p>
+          <p>1. API Design - what makes a good API and what makes a bad API</p>
+          <p>2. The API development process - spec, dev, test and documentation</p>
+          <p>3. Future direction of APIs - new developments</p>
+          <p>4. The business of APIs - metrics and business models</p>
+          <p>5. API evangelism - internal and external</p>
+          <p>Learn and share knowledge about REST/Web APIs. Discover what other professionals in Los Angeles are using to build real-world APIs to drive their business. We are the LA chapter of the world wide&nbsp;<a href="https://groups.google.com/forum/#!forum/api-craft">API Craft Google Group.</a></p>
+        lon: -118.5
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/c/1/c/7/600_445909607.jpeg'
+        lat: 34.02000045776367
+      - country: US
+        city: Fresno
+        link: 'http://www.meetup.com/fresno-js/'
+        name: Fresno.js JavaScript User Group
+        description: "<p>Fresno.js is Fresno's premier JavaScript user group. Join us as we learn from some of the best in the community about the state of the art in web, mobile, database and server development . Every first Tuesday is our official meetup where we get together at Bitwise Industries for presentations on the hottest topics in JavaScript.</p>"
+        lon: -119.79000091552734
+        lat: 36.75
+      - country: US
+        city: Philadelphia
+        link: 'http://www.meetup.com/Philadelphia-Microservices-Meetup/'
+        name: Philadelphia Microservices Meetup
+        description: 'Breaking monoliths and spaghetti architectures into lightweight, decoupled components is a liberating experience. The microservices movement focuses on these small building blocks, enabling greater agility, simpler change, polyglot capability and the chance to really grok large systems. This meetup is for people interested in architecting, designing, deploying and maintaining microservice based architectures.'
+        lon: -75.01000213623047
+        lat: 40.119998931884766
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/Boston-FinTech-Solutions-Architectures/'
+        name: Boston FinTech Solutions Architectures
+        description: 'This group is about discussing various IT challenges in Financial Technology including Risk and Compliance, AML, KYC, Customer MDM, Product MDM, Knowledge-bases, Trading Systems, Portfolio Management Systems, etc.  We will discuss real world problems, how solutions were designed and implemented, the advantages and issues with different approaches and architectural patterns and anti-patterns.'
+        lon: -71.06999969482422
+        lat: 42.36000061035156
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/DC-Ionic-Framework-Meetup/'
+        name: DC Ionic Framework Meetup
+        description: |-
+          <p>Interested in a hybrid approach to Mobile Development using the Ionic Framework, Cordova, AngularJS, and many other open source JS frameworks? Then you've come to the right place :-) . Ionic DC will cover some of the latest and greatest topics related to the Ionic Framework ecosystem, including live coding demos, and discussion showcasing some of the great features and services Ionic has to offer! This is also a great opportunity to meet and network with other fellow Ionic developers in the DC area! A wise woman once told me "Your network is your net worth"&nbsp;</p>
+          <p>About the host: &nbsp;In the summer of 2014, after years of development using Cordova, I came across the Ionic framework and have never looked back. Since then my friend/colleague Stephen White and I have released a sports news application written in Ionic called SportScoop for Android and iOS (details below). &nbsp;I'm also very active in the Ionic Market and has released 3 popular Ionic plugins used for Ionic applications; Ionic Filter Bar, Ionic Scroll Sista, and Ionic Content Banner.&nbsp;</p>
+          <p>SportScoop</p>
+          <p>&nbsp;- Web Demo -&nbsp;<a href="http://www.sportscoopapp.com">www.sportscoopapp.com</a></p>
+          <p>- iOS - <a href="https://itunes.apple.com/us/app/sportscoop/id1035164619?mt=8" class="linkified">https://itunes.apple.com/us/app/sportscoop/id1035164619?mt...</a>&nbsp;</p>
+          <p>- Android - <a href="https://play.google.com/store/apps/details?id=com.coseur.sportscoop" class="linkified">https://play.google.com/store/apps/details?id=com.coseur.s...</a>&nbsp;</p>
+          <p>Ionic Plugins (Ionic Filter Bar, Ionic Scroll Sista, Ionic Content Banner</p>
+          <p>&nbsp;- Github - <a href="https://github.com/djett41" class="linkified">https://github.com/djett41</a></p>
+        lon: -76.98999786376953
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/8/5/f/5/600_446194293.jpeg'
+        lat: 38.880001068115234
+      - country: US
+        city: Louisville
+        link: 'http://www.meetup.com/DoneJS-Louisville/'
+        name: DoneJS Louisville
+        description: '<p>A group based on furthering JavaScript along with DoneJS, StealJS, CanJS and DocumentJS development in Louisville. Learn from people who developed the technology. Share your experiences, opinions and questions with fellow JS superheroes!</p>'
+        lon: -85.77999877929688
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/b/4/d/600_446499757.jpeg'
+        lat: 38.25
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/Javascript-Study-Toronto/'
+        name: Javascript Study Toronto
+        description: '<p>Javascript has been an essential part of the Web development industry. &nbsp;I started this meetup to make Javascript more accessible to anyone, including myself, who loves to learn more about the technology and build applications with it.</p>'
+        lon: -79.36000061035156
+        lat: 43.7400016784668
+      - country: CA
+        city: Toronto
+        link: 'http://www.meetup.com/devhub/'
+        name: Devhub
+        description: |-
+          <p>Launched in April 2016, Devhub is Canada’s first education space for developers of all levels. It is a platform where developers can grow together, whether they've been coding for two decades or 8 weeks.&nbsp;</p>
+          <p>Find out more information at <a href="http://www.devhub.ca">www.devhub.ca</a></p>
+          <p>Want to stay in touch? Join our <a href="http://eepurl.com/bW0qZ9">e-mail family</a></p>
+        lon: -79.38999938964844
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/e/5/7/c/600_446758748.jpeg'
+        lat: 43.63999938964844
+      - country: US
+        city: Petaluma
+        link: 'http://www.meetup.com/Basic-Web-Dev/'
+        name: Basic Web-Dev
+        description: |-
+          <p>This is a group for Curios/Beginning Front-End-Web-Devs, We will start from; Mark-up, HTML5, CSS, JavaScript, and GIT. We will work on pair programming, and communicating while building things on the web. A lecture for 30-60 minutes then get to pairing and programming.</p>
+          <p>We will starting from the very beginning; loading a text editor,Mark-up, HTML, CSS/Bootstrap, Git, JavaScript {arrays, objects, functional programming with underscore} &nbsp; All levels are welcome. If you are advanced and would like to grace us with your knowledge please do. If we have enough interest/people weekly will be okay for the location I have secured. Please bring your own Laptop, we will meeting from 6-8 pm and will keep a weekly meet-up as long as we have people wanting to learn. If you have any questions please feel free to contact me.</p>
+        lon: -122.66000366210938
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/8/1/a/600_446438938.jpeg'
+        lat: 38.2400016784668
+      - country: US
+        city: Chicago
+        link: 'http://www.meetup.com/Learn-to-Code-Chicago/'
+        name: Learn to Code Chicago
+        description: "<p>Ever thought about learning to code? Well this meetup is for you! This meetup is run by MakerSquare, a 3 month immersive software engineering school part of the national Reactor Core Network. Our mission is to teach a driven community of students the latest in web development skills. We're educators first and software engineers second. We employ 21st century, rapid-iteration teaching principles to teach professionals the most in-demand skills in the most effective ways possible. Events we'll host will include coding workshops in HTML, CSS, JS and Git, networking events for tech professionals in the Chicago area and community events to attract attention to the tech scene, just to name a few. Our goal is to provide the Chicago area with effective training that can support the lively tech ecosystem. Feel free to reach out if you're looking to get your hands dirty in some code!</p>"
+        lon: -87.62000274658203
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/a/4/9/600_448123593.jpeg'
+        lat: 41.880001068115234
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/pdx-sh/'
+        name: Portland Shell Hackers (pdx.sh)
+        description: |-
+          <p>&nbsp; "Can't you just do that with Bash and SSH?" - Famous Last Words&nbsp;</p>
+          <p><b>Portland Shell Hackers (pdx.sh)</b> is a monthly meetup for sweet Bash hacks, clever zsh macros, corny ksh scripts, fishy fish functions, and everything related. We'll cover the Unix Coreutils (and all their quirks and platformy weirdness), cURL, ssh, scp, Bash package management, DevOops, etc.&nbsp;<span>All skill levels welcome.&nbsp;</span></p>
+          <p><span>BYOSH (Bring Your Own Sweet Hacks).</span></p>
+        lon: -122.69000244140625
+        lat: 45.5
+      - country: US
+        city: Palo Alto
+        link: 'http://www.meetup.com/modernweb/'
+        name: Modern Web
+        description: |-
+          <p>This is an interactive meetup/variety show focused on exploring next generation frameworks, standards, tools, and techniques of the Modern Web.&nbsp;</p>
+          <p>Topics we cover range from JavaScript frameworks such as ReactJS, EmberJS, AngularJS, Angular2, React Native, TC39, ES2015, ES6, ES7, ES2016, RxJS, Web Components, PolymerJS, Docker, Containers, Progressive Web Apps, and more.</p>
+          <p>You may visit http://modern-web.org for podcasts, videos, and additional content.</p>
+        lon: -122.1500015258789
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/4/1/9/3/600_446416787.jpeg'
+        lat: 37.439998626708984
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/North-Austin-JavaScript-Meetup/'
+        name: North Austin JavaScript Meetup
+        description: We are a group of software developers exploring technologies and frameworks that leverage the javascript language. Come join us as we venture through the exciting field of javascript.
+        lon: -97.75
+        lat: 30.219999313354492
+      - country: US
+        city: Redwood City
+        link: 'http://www.meetup.com/SF-Bay-Area-Oracle-Developers/'
+        name: SF Bay Area Oracle Developers
+        description: '<p>This is a group for technology enthusiasts and developers of all skill levels. The group is designed to bring you updates and innovations in technology from Oracle through events, workshops, hackathons, and hands-on experiences.</p>'
+        lon: -122.25
+        lat: 37.529998779296875
+      - country: US
+        city: Austin
+        link: 'http://www.meetup.com/North-Austin-Full-Stack/'
+        name: North Austin Full Stack
+        description: 'North Austin Full Stack is a friendly group of people interested in developing (Front and Back End) in the North Austin/Cedar Park, Texas area. Whatever your skill level, we invite you to join us, share your experiences, and learn new tricks and tips. Meet other web developers/designers in your area! Come to our Meetup to compare tools, languages; trade career advice, best practices, rates, and freelancing. Expand your networking as you meet new friends!'
+        lon: -97.75
+        lat: 30.219999313354492
+      - country: US
+        city: Charlotte
+        link: 'http://www.meetup.com/Charlotte-NodeJS-User-Group/'
+        name: Charlotte NodeJS User Group
+        description: '<p>From desktop to IoT to Serverless execution to the universe of npm libraries, the world of NodeJS is becoming increasingly complex and harder to navigate. We want to come together to learn more about the JavaScript and Node.js and its uses in the world. Hopefully make human and computing connections to simplify both our computing and professional lives. Come check us out.</p>'
+        lon: -80.86000061035156
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/8/2/2/600_447006178.jpeg'
+        lat: 35.209999084472656
+      - country: US
+        city: Portland
+        link: 'http://www.meetup.com/Free-Code-Camp-Portland/'
+        name: Free Code Camp Portland
+        description: 'Hi Campers. Free Code Camp is a 100% free online curriculum teaching technologies like HTML, CSS, JavaScript, jQuery, ReactJS, node.js, and mongodb. Students or "campers" complete challenges and projects towards certificates and then are eligible to work on actual development projects for non-profits. This group is for campers looking to get together and share their current projects, work on any challenges, and socialize and collaborate with other campers and mentors. Bring your laptop and come learn some JavaScript!'
+        lon: -122.69000244140625
+        lat: 45.5
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/RiotJS-Bay-Area-Meetup/'
+        name: RiotJS Bay Area Meetup
+        description: "<p>Want React-like components in a blazing fast 20kb production-quality library using HTML, not JSX? Check out Riot (<a href=\"http://riotjs.com\" class=\"linkified\">http://riotjs.com</a>), a micro-framework for building UI components that just feels right. We're calling all Riot enthusiasts as well as folks who are interested in using this lightweight alternative to React for building scalable web apps. We want to build an inclusive, welcoming environment for web developers of all backgrounds to learn this amazing tech.</p>"
+        lon: -122.4000015258789
+        lat: 37.77000045776367
+      - country: US
+        city: Milwaukee
+        link: 'http://www.meetup.com/Wisconsin-AngularJS-Meetup/'
+        name: Wisconsin AngularJS Meetup
+        description: "Angular JS is an incredible JavaScript library. Join us if you'd like to learn more or if you have your own Angular JS experience to share that others can benefit from. "
+        lon: -87.9000015258789
+        lat: 43.04999923706055
+      - country: US
+        city: Houston
+        link: 'http://www.meetup.com/freecodecampHouston-Midtown/'
+        name: FreeCodeCamp - Houston
+        description: 'This group is for anyone who is interested in programming and is involved in FreeCodeCamp, the free online code academy. Check out www.freecodecamp.com. We are the Houston group. All levels are welcome. We meet to share ideas, network, and learn! We will meet twice a month in the midtown area. Bring your laptop. WiFi is available at our different venues.'
+        lon: -95.47000122070312
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/3/7/e/e/600_448094318.jpeg'
+        lat: 29.75
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/LearnToCodeNYC/'
+        name: Learn to Code NYC
+        description: "<p>Ever thought about learning to code? If so, this meetup is for you! This meetup is run by MakerSquare, a 3 month immersive software engineering school part of the national Reactor Core Network. Our mission is to teach a driven community of students the latest in web development skills. We're educators first and software engineers second. We employ 21st century, rapid-iteration teaching principles to teach professionals the most in-demand skills in the most effective ways possible. Events we'll host will include coding workshops in HTML, CSS, JavaScript and Git, networking events for tech professionals in the New York City area and community events to attract attention to the tech scene, just to name a few. Our goal is to provide the New York City area with effective training that can support the lively tech ecosystem. Feel free to reach out if you're looking to get your hands dirty in some code!</p>"
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/1/7/8/600_448100856.jpeg'
+        lat: 40.75
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/LearnProgrammingBoston/'
+        name: Learn Programming Boston
+        description: "<p>Ever thought about learning to code? Well this meetup is for you! This meetup is run by MakerSquare, a 3 month immersive software engineering school part of the national Reactor Core Network. Our mission is to teach a driven community of students the latest in web development skills. We're educators first and software engineers second. We employ 21st century, rapid-iteration teaching principles to teach professionals the most in-demand skills in the most effective ways possible. Events we'll host will include coding workshops in HTML, CSS, JS and Git, networking events for tech professionals in the Boston area and community events to attract attention to the tech scene, just to name a few. Our goal is to provide the Boston area with effective training that can support the lively tech ecosystem. Feel free to reach out if you're looking to get your hands dirty in some code!</p>"
+        lon: -71.05999755859375
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/a/4/e/600_448123598.jpeg'
+        lat: 42.36000061035156
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Veterans-Who-Code/'
+        name: Veterans Who Code SF
+        description: |-
+          <p>At this Meetup, you'll learn: <br>- JavaScript <br>- React JS <br>- Angular JS <br>- How to get into programming <br>- How to transition into a career in technology <br></p>
+          <p><b>The goal of this Meetup: </b> <br>Bring veterans together who want to learn to code, who want to transition into a career in technology, or want to share their programming knowledge with others. <br></p>
+          <p>This meetup is inclusive of all groups who wish to attend; the group is not limited only to veterans. We welcome all people who want to learn to code, who want to help others, or who want to share programming best practices.</p>
+        lon: -122.4000015258789
+        lat: 37.790000915527344
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/JS-Office-Hours/'
+        name: JS Office Hours
+        description: '<p><span>Have JavaScript questions? Want to discuss ES6, React, or Promises? Then why not bring your laptop over to the Haight to share a beer and some snacks. The Tonic team will be hosting a weekly JavaScript Office Hours.</span><br></p>'
+        lon: -122.44000244140625
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/e/5/2/c/600_447178668.jpeg'
+        lat: 37.77000045776367
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/Boston-FreeCodeCampers/'
+        name: Boston FreeCodeCampers
+        description: |-
+          <p>Free Code Camp (<a href="http://www.freecodecamp.com" class="linkified">http://www.freecodecamp.com</a>) is an open source community where you learn to code full stack JavaScript and help non-profits.&nbsp;</p>
+          <p><span>You need Free Code Camp because learning to code is hard.</span> <br></p>
+          <p>Most people who successfully learn to code: <br>Make friends with people who code <br>Code a little every day</p>
+          <p>Free Code Camp gives you the structure and the community you need so you can successfully learn to code. All skill levels are welcome. More on&nbsp;http://freecodecamp.github.io/wiki/en/Why-you-need-Free-Code-Camp/</p>
+        lon: -71.05999755859375
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/7/5/1/7/600_447209975.jpeg'
+        lat: 42.349998474121094
+      - country: US
+        city: Fayetteville
+        link: 'http://www.meetup.com/Fayetteville-Web-Developers/'
+        name: Fayetteville Web Developers
+        description: '<p>A group for those of us who love to write code and design user experiences here in Fayetteville, NC.</p>'
+        lon: -78.93000030517578
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/4/7/9/600_447222105.jpeg'
+        lat: 35.0099983215332
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/Build-With-Code-San-Francisco/'
+        name: Build With Code - San Francisco
+        description: |-
+          <p>Build with Code hosts free weekly JavaScript and Software Engineering workshops, lectures and pair-programming sessions.&nbsp;</p>
+          <p>Welcome! The reason people who only watch programming videos don't become programmers is because they're not programming. Come join other aspiring engineers and start building! In JavaScript the Hard Parts, we cover callbacks, higher-order functions (functional programming with JavaScript), object-oriented programming with JavaScript, closure, scope and execution context.</p>
+          <p><span>&nbsp;JavaScript the Hard Parts has been our most popular workshop in LA, and now Codesmith CEO Will Sentance is bringing it to San Francisco.&nbsp;</span></p>
+          <p><span>Price: Always free&nbsp;</span></p>
+          <p><span>About Codesmith: Codesmith teaches full stack software engineering in JavaScript through a 12 week immersive program. We teach computer science, object-oriented JavaScript, React, Angular, Node, distributed systems and mobile development so our grads can secure mid-to-senior level software engineering positions or launch their own ventures&nbsp;</span></p>
+          <p><span>Apply to the program at codesmith.io/apply. For further questions email admissions@codesmith.io</span> <br></p>
+          <p>---</p>
+          <p><span>JavaScript the Hard Parts is a free JavaScript class in San Francisco and Los Angeles designed to learn intermediate and advanced JavaScript - including callbacks, higher order functions (like how to understand map, reduce, filter and foreach), closure, object-oriented programming in JavaScript and other topics</span><br></p>
+          <p>In Codesmith Information sessions, attendees meet with current students and graduates to discuss what it's like to attend Codesmith, what characteristics create the best coding bootcamp in the US, how to get into Codesmith and how to succeed in the Codesmith interview</p>
+          <br>
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/7/9/8/600_447246040.jpeg'
+        lat: 37.779998779296875
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/LA-Node/'
+        name: LA Node.js
+        description: |-
+          <p>Welcome to the hub for Node.js, one of the fastest growing server side languages to date, in Southern California - from Los Angeles, to San Diego, from the Valley to Orange County</p>
+          <p><b>Join us for compelling talks, workshops with lead engineers building with Node and starter sessions for those who are new to React.</b></p>
+          <p>We're in the early stage with the meetup group so we're excited to hear your suggestions!&nbsp;</p>
+        lon: -118.43000030517578
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/a/7/1/600_447391345.jpeg'
+        lat: 33.9900016784668
+      - country: US
+        city: Nashville
+        link: 'http://www.meetup.com/Nashville-EmberJS/'
+        name: Nashville Ember JS Meetup
+        description: '<p>This meetup is focused on learning and working on Ember.js projects. All interest and levels are welcome.</p>'
+        lon: -86.77999877929688
+        lat: 36.11000061035156
+      - country: US
+        city: Richardson
+        link: 'http://www.meetup.com/Hack-My-Life/'
+        name: Hack My Life
+        description: '<p>We are a group committed to helping software developers vastly improve their lifestyle engineering skills. As developers, we work in some of the most in-demand fields on the planet, yet many of us feel stuck in our career paths. This need not, and should not be the case. Being in-demand should mean that you are able to work in a role that you find personally fulfilling, which simultaneously moves you closer to your personal goals. With the right set of tools and a community behind you, you can find ways to side-step obstacles to your career development, with far greater ease than you could on your own.</p>'
+        lon: -96.75
+        lat: 32.959999084472656
+      - country: US
+        city: Fairfax
+        link: 'http://www.meetup.com/Fairfax-Full-Stack-Developer-Meetup/'
+        name: Fairfax Full Stack Developer Meetup
+        description: |-
+          <p>Are you passionate about technology and constantly seeking innovative ways to solve problems? Fairfax Full Stack Developer Meetups is where developers can come to learn from and teach each other about emerging technologies. Our guest speakers will discuss the latest technologies, frameworks and solutions to everyday challenges. We will have fun and challenging events like Hackathons, workshops and networking.</p>
+          <p>“A problem well-defined is half-solved.”Einstein<br></p>
+        lon: -77.33999633789062
+        lat: 38.83000183105469
+      - country: US
+        city: Los Angeles
+        link: 'http://www.meetup.com/Los-Angeles-Oracle-Developers/'
+        name: Los Angeles Oracle Developers
+        description: 'This is a group for technology enthusiasts and developers of all skill levels. The group is designed to bring you updates and innovations in technology from Oracle through events, workshops, hackathons, and hands-on experiences.'
+        lon: -118.23999786376953
+        lat: 33.970001220703125
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/sfwakanda/'
+        name: San Francisco Wakanda Open Source JS FullStack
+        description: |-
+          <p>This meetup is dedicated to promoting Wakanda<span>&nbsp;Open Source JavaScript FullStack platform. We will launch a monthly online JS development challenge. The best application developed with Wakanda Platform will receive at least $1,000 USD prize and will be showcased on Wakanda websites.</span></p>
+          <p>This group is also for anyone interested in learning how to build mobile applications in 3 weeks using Javascript for both frontend and backend sides.</p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: -122.41999816894531
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/c/9/b/3/600_447711635.jpeg'
+        lat: 37.779998779296875
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/Seattle-Oracle-Developers/'
+        name: Seattle Oracle Developers
+        description: 'This is a group for technology enthusiasts and developers of all skill levels. The group is designed to bring you updates and innovations in technology from Oracle through events, workshops, hackathons, and hands-on experiences'
+        lon: -122.33000183105469
+        lat: 47.61000061035156
+      - country: US
+        city: Washington
+        link: 'http://www.meetup.com/ELECTRONDC/'
+        name: ELECTRONDC
+        description: "Building cross platform apps with web technologies using Github's Electron"
+        lon: -77.0199966430664
+        lat: 38.90999984741211
+      - country: US
+        city: Rocky Mount
+        link: 'http://www.meetup.com/Coders-Gather-And-Create/'
+        name: Coders Gather And Create
+        description: |-
+          <p>Calling ALL coders! &nbsp;This Meetup group is for <b>designers and developers</b> who share the same kind of passion for coding that I do no matter your skill level or programming background. I have been to Meetups before that center around programming, but I haven't found one that really pushes it's members to really create something throughout the course of the meetings. That is something I hope to change with this group.&nbsp;</p>
+          <p>LETS CREATE SOMETHING!</p>
+          <p>The purpose of this Meetup is to test out a new style of gathering where <b>everyone binds their skills with coding and design together</b> to create something... &nbsp;Who know's what that something will end up being, but we will create SOMETHING! Currently, there is no direction that is chiseled in stone, but the Idea is that whoever comes can contribute a component to a project using whatever language he/she is comfortable with even if it requires a little bit of learning. C++,&nbsp;.NET, AngularJS, BackboneJS, Ruby, Ruby on Rails, NodeJS, SQL, MONGO, Python, etc... Your language is your choice. The challenge is to figure out how to create something <b>larger than ourselves</b> that <b>anyone</b> new<b> (from beginners to professionals) can contribute</b> to <b>or</b> can learn the language that he/she is interested in and&nbsp;<b>learn how to contribute</b>. The great thing is that I think the power of project management with git can make this work. I am hoping for great things with this group.</p>
+          <p>At the very least, we will get to know and learn from fellow coders around the Nash county area. As far as a place to meet, details will be released once we get a few members interested.</p>
+        lon: -77.75
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/a/6/2/6/600_447822534.jpeg'
+        lat: 35.95000076293945
+      - country: US
+        city: Philadelphia
+        link: 'http://www.meetup.com/ServerlessPHL/'
+        name: Serverless PHL
+        description: '<p>Serverless PHL seeks to grow a community of developers interested in building "serverless" applications running on platforms such as AWS Lambda, Google Cloud Functions, OpenWhisk, and/or IOpipe. Topics will include dev, test, and deployment of applications, the operational challenges of running serverless apps, and the tools and services that empower such applications (Auth0, Firebase, etc).</p>'
+        lon: -75.01000213623047
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/2/6/4/2/600_447849794.jpeg'
+        lat: 40.119998931884766
+      - country: US
+        city: Ponte Vedra Beach
+        link: 'http://www.meetup.com/nativescript/'
+        name: NativeScript Jax
+        description: '<p>NativeScript Jax is a meetup dedicated to people building/learning to build native cross platform iOS and Android mobile apps with NativeScript in North Florida</p>'
+        lon: -81.37999725341797
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/4/2/1/a/600_447856922.jpeg'
+        lat: 30.239999771118164
+      - country: US
+        city: Brooklyn
+        link: 'http://www.meetup.com/Coders-Helping-Coders/'
+        name: Coders Helping Coders
+        description: |-
+          <p>This is a meetup dedicated to having coders helping coders. Each meetup will consist of more doing and less anything else. Bring your laptop, and be ready to ask questions (bugs, coding style, concepts, getting setup) or be ready to help. We'll meet at a common venue, and people will pair up or group up to help each other whatever is necessary. Feel free to buy whoever is helping you a beer or a muffin, but not necessary. Open to programmers of all skill sets, absolute beginners to pros.</p>
+          <p>No Recruiters or Recruiting allowed. You must have the desire to help others coding or to learn how to code.</p>
+          <p>We will be vetting people to make sure everyone has a quality time with this meetup!</p>
+        lon: -73.94999694824219
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/b/4/9/b/600_447886235.jpeg'
+        lat: 40.709999084472656
+      - country: US
+        city: Atlanta
+        link: 'http://www.meetup.com/The-Atlanta-Blockchain/'
+        name: The Atlanta Blockchain
+        description: "The Atlanta Blockchain (TAB). This group focuses on educating the community about decentralized crypto technologies. Many new and exciting things are happening in this space, things are changing quickly, don't be left behind. The future will be encrypted and decentralized and this is the time to learn what the heck is going on. We will focus on many things including: Bitcoin, Blockchain, Ethereum, decentralized storage, alt-coins, mining, programming, blockchain as a database, general education 101's, and more. Please come join us to be part of this technology revolution!"
+        lon: -84.38999938964844
+        lat: 33.93000030517578
+      - country: US
+        city: Boston
+        link: 'http://www.meetup.com/Boston-Redis/'
+        name: Boston Redis
+        description: '<p>This group meets monthly to discuss different ways to use Redis to scale your website</p>'
+        lon: -71.06999969482422
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/3/8/e/600_448140910.jpeg'
+        lat: 42.36000061035156
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/Learn-to-Code-New-York/'
+        name: Learn to Code New York
+        description: "Ready to learn to code? Start your programming journey by attending learn to code workshops and by collaborating with a supportive community. We'll be covering intro and intermediate topics every month."
+        lon: -73.94999694824219
+        lat: 40.810001373291016
+      - country: US
+        city: Boulder
+        link: 'http://www.meetup.com/bouldernode/'
+        name: Boulder Node.js
+        description: "<p>Attn Node.js afficionados: This is one technology group that will get you publishing NPM's, collaborate on open-source projects together, and discuss hosting needs among more novel uses of the technology. When solutions don't exist, we'll build them. Come to share your ideas and learn in interactive workshops. Mentor others and find mentees. If you don't know how to code, come with an attitude to learn.</p>"
+        lon: -105.27999877929688
+        lat: 40.040000915527344
+      - country: US
+        city: Seattle
+        link: 'http://www.meetup.com/Seattle-Joyent-Meetup/'
+        name: Joyent Seattle Meetup
+        description: '<p>This is the Seattle area meetup for developers, operations and other technical types interested in Joyent technology. Come join us for a technical meet up to discuss the advantages of using containers in production, and how to overcome common challenges with deployments. Anyone who is interested in using, deploying, or contributing to Triton or other Joyent open-source projects are welcome. We will discuss topics such as Docker, Node.js, Mesos, KVM, Kubernetes, OS virtualization and DevOps, as well as best practices for public, private and hybrid cloud architectures.</p>'
+        lon: -122.33000183105469
+        lat: 47.61000061035156
+      - country: US
+        city: Rancho Cucamonga
+        link: 'http://www.meetup.com/Inland-Empire-JavaScript-Meetup/'
+        name: Inland Empire JavaScript Meetup
+        description: "This group is for anyone interested in Javascript. I'd like to bring together the local JS community and create a welcoming environment for anyone interested in meeting local JS Developers. We'll start with coding exercises and talks on anything Javascript and long term goals include holding workshops and a mini Hack-A-Thon."
+        lon: -117.5199966430664
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/6/7/1/c/600_448346396.jpeg'
+        lat: 34.119998931884766
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/DevOps-for-Devs/'
+        name: DevOps for Devs
+        description: |-
+          <p><i>We've all been there.</i></p>
+          <p><span>You thought you were hired to write code, but the scope of your job has widened to include all things DevOps (CI/CD, deployment, configuration management, server administration, etc).</span></p>
+          <p><span><b>What's a developer to do?</b></span></p>
+          <p><span>This is a meetup for Software Engineers, by Software Engineers, with the goal of helping each other understand how to deploy our code safely and effectively, how to manage live servers (and databases) and how to embrace new technologies (like Docker, yay!) and incorporate them into our development process.&nbsp;</span></p>
+          <p><span>You're not alone anymore. We'll get through this whole DevOps thing together.</span></p>
+          <p><span>Stay tuned for speakers on all the topics you've been dying to learn about: AWS, Heroku, Docker, Kubernetes, Chef, Puppet, New Relic, Load Balancing, lions and tigers and bears, oh my!</span><br></p>
+        lon: -73.94999694824219
+        lat: 40.83000183105469
+      - country: US
+        city: Brooklyn
+        link: 'http://www.meetup.com/ThinkAcademy/'
+        name: 'Think Academy - Learn To Code!'
+        description: '<p>Passionate about learning how to code, love creating beautiful designs or building prototypes for your start up and tired of doing it alone?&nbsp;Then this is the group for you!&nbsp;</p>'
+        lon: -73.98999786376953
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/a/0/1/600_448435809.jpeg'
+        lat: 40.70000076293945
+      - country: US
+        city: Hawthorne
+        link: 'http://www.meetup.com/la-code-collective/'
+        name: 'LA Code Collective: Co-Op Group Programming'
+        description: |-
+          <p>This a small meet-up I am currently running out of my house. The point is to get career developers together in an intimate setting and discuss some of the things that we do literally every day. I'll try to include at least one presentation on technology at each group meeting, but then it is free-form discussion and coding. I'll have coffee and beer if you want it. <br> <br>I have to limit this to 10 - 15 spots at first. Please attend only if you are on the RSVP list. I know a lot of people don't show up, but if you really want to come by and hang with your fellow abused coders just message me personally.</p>
+          <p>This is not a group for recruiters or 'idea guys' trying to sell their ideas. This group is for people who have already made a commitment to coding whether that is personal or professional. This is a group for people who have figured out how to get the job done, whatever that means.</p>
+          <p>I am very laid back and casual and you are all welcome to come talk about your problems, personal and professional. We'll sort out the mess of tools and languages we're expected to know as well as the pressures that modern life puts on a person who is expected to literally know everything and never stop working.</p>
+          <p>If we share and help each other with our unique situation we can make our lives a little bit easier.</p>
+          <p>I can't wait to meet you!</p>
+          <p> <br></p>
+        lon: -118.3499984741211
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/f/7/8/600_448416728.jpeg'
+        lat: 33.91999816894531
+      - country: US
+        city: Monterey Park
+        link: 'http://www.meetup.com/Techbow-LA-Web-Technology-Meetup/'
+        name: Techbow LA Web Technology Meetup
+        description: '<p>To join us for a weekly meetup to share and discuss about the most up-to-date web technology. We are the most influential IT training provider in LA, which teaches a series of IT classes from fundamental to advanced level of web/mobile design and development, data analytics, digital media and online marketing classes.</p>'
+        lon: -118.1500015258789
+        lat: 34.04999923706055
+      - country: US
+        city: New York
+        link: 'http://www.meetup.com/Build-With-Code-New-York-City/'
+        name: Build With Code - New York City
+        description: "Build with Code hosts free weekly JavaScript and Software Engineering workshops, lectures and pair-programming sessions. \n\nWelcome! The reason people who only watch programming videos don't become programmers is because they're not programming. Come join other aspiring engineers and start building! In JavaScript the Hard Parts, we cover callbacks, higher-order functions (functional programming with JavaScript), object-oriented programming with JavaScript, closure, scope and execution context.\n\n JavaScript the Hard Parts has been our most popular workshop in LA, and now Codesmith CEO Will Sentance is bringing it to New York City. \n\nPrice: Always free \n\nAbout Codesmith: Codesmith teaches full stack software engineering in JavaScript through a 12 week immersive program. We teach computer science, object-oriented JavaScript, React, Angular, Node, distributed systems and mobile development so our grads can secure mid-to-senior level software engineering positions or launch their own ventures \n\nApply to the program at codesmith.io/apply. For further questions email admissions@codesmith.io \n\n---\n\nJavaScript the Hard Parts is a free JavaScript class in San Francisco, Los Angeles, and New York City designed to learn intermediate and advanced JavaScript - including callbacks, higher order functions (like how to understand map, reduce, filter and foreach), closure, object-oriented programming in JavaScript and other topics \n\nIn Codesmith Information sessions, attendees meet with current students and graduates to discuss what it's like to attend Codesmith, what characteristics create the best coding bootcamp in the US, how to get into Codesmith and how to succeed in the Codesmith interview"
+        lon: -73.98999786376953
+        lat: 40.75
+      - country: US
+        city: Dallas
+        link: 'http://www.meetup.com/ReactDallas/'
+        name: React Dallas
+        description: '<p>ReactJS and React Native meetup group. Learn and discuss React.</p>'
+        lon: -96.80000305175781
+        lat: 32.790000915527344
+      - country: US
+        city: San Diego
+        link: 'http://www.meetup.com/Build-With-Code-San-Diego/'
+        name: Build With Code - San Diego
+        description: "Build with Code hosts free weekly JavaScript and Software Engineering workshops, lectures and pair-programming sessions. Welcome! \n\nLearn and build with the hard parts of JavaScript every Thursday 6:30pm-8:00pm through intuitive lectures and pair-programming\n\nThe reason people who only watch programming videos don't become programmers is because they're not programming. Come join other aspiring engineers and start building!\n\nIn JavaScript the Hard Parts, we cover callbacks, higher-order functions (functional programming with JavaScript), object-oriented programming with JavaScript, closure, scope and execution context\n\nHosted at Codesmith every week on Thursdays 6:30pm-8:00pm and taught by Codesmith CTO Will Sentance\n\nPrice: Always free\n\nCodesmith (Codesmith) \n\nCodesmith teaches full stack software engineering in JavaScript through a 12 week immersive program. \n\nWe teach computer science, object-oriented JavaScript, React, Angular, Node, distributed systems and mobile development so our grads can secure mid-to-senior level software engineering positions or launch their own ventures\n\nApply to the program at codesmith.io/apply. For further questions email admissions@codesmith.io"
+        lon: -117.16999816894531
+        lat: 32.720001220703125
+      - country: US
+        city: San Jose
+        link: 'http://www.meetup.com/JSstance/'
+        name: JSstance
+        description: |+
+          import {js} from './ether'
+
+          <code>.replace(/(ruby|python|java)/g, js)
+
+          Learn. Discuss. Propagate.
+
+
+
+
+
+
+        lon: -121.9000015258789
+        lat: 37.38999938964844
+      - country: US
+        city: San Francisco
+        link: 'http://www.meetup.com/San-Francisco-Telephony-API-Users-Group/'
+        name: San Francisco Telephony API Users Group
+        description: "Come hangout and discuss what has changed and what's new in the world of TelecomAPIs. Tech including but not limited to WebRTC, Javascript, C#, REST API, XML, basically anything you can throw an HTTP request with."
+        lon: -122.41999816894531
+        lat: 37.779998779296875
+      - country: US
+        city: San Mateo
+        link: 'http://www.meetup.com/San-Mateo-JavaScript-Study-Group/'
+        name: San Mateo JavaScript Study Group
+        description: |-
+          <p><b>Who is this study group for? </b>- This is a place to learn, study, and practice JavaScript as a group. Items related to HTML/CSS/Javascript/various JavaScript libraries/etc. are welcome, but the focus should be on JavaScript. All JS levels are invited.You can meet people, talk about JavaScript related technologies, find a mentor, or someone to study with or do pair programming with. <br></p>
+          <p><b>RULES: -</b> Simple, just be respectful towards others. ANY/ALL SKILL LEVELS ARE WELCOME AND ENCOURAGED, so please be nice. - ASK/CONFIRM if someone wants critique/help before just jumping in and giving it. - Have fun; learn!! :) <br></p>
+          <p><b>Online coding environments:</b> <br></p>
+          <p>CodePen, JSFiddle <br></p>
+          <p><b>What is the study plan? -</b> We will decide between: <a href="https://github.com/getify/You-Dont-Know-JS" class="linkified">https://github.com/getify/You-Dont-Know-JS</a> or <a href="http://www.amazon.com/Beginning-JavaScript-Paul-Wilton/dp/0470525932" class="linkified">http://www.amazon.com/Beginning-JavaScript-Paul-Wilton/dp...</a> <br></p>
+          <p><b>When do we study together? - </b>We will meet on a weekly basis, on Sunday afternoons via Slack/Skype or based on interest in person, and do our best to read and practice, first individually, and in advance (before the weekly meeting), as much as possible of just one book chapter per week, so we can discuss that weekly book chapter, ask and answer questions during our weekly meetup's. <br></p>
+          <p><b>Note: </b>If you have extra time, you can also follow the "beginner's" weekly studying sequence recommended at: <a href="http://javascriptissexy.com/how-to-learn-javascript-properly/" class="linkified">http://javascriptissexy.com/how-to-learn-javascript-prope...</a> <br></p>
+          <p><b>Slack Channel:</b> peninsulajs.slack.com <br></p>
+          <p><b>Liability Waiver:</b> All participants agree to assume 100% responsibility for their own safety, conduct, and well-being and recognize that possible hazards exist while participating in outdoor (or any other) activities, and agree to participate solely at their own risk. If you join this group, and if you RSVP “Yes” and/or attend any of our events, it shall be conclusively presumed you understand and agree to this policy.</p>
+        lon: -122.2699966430664
+        lat: 37.54999923706055
+      - country: US
+        city: Saint Louis
+        link: 'http://www.meetup.com/FullStack-STL/'
+        name: FullStack / STL
+        description: FullStack is a network of monthly developer and digital designer-only meetups that cover open source web and mobile app development from front to back.
+        lon: -90.25
+        lat: 38.63999938964844
+      - country: US
+        city: Ferndale
+        link: 'http://www.meetup.com/Detroit-Javascript/'
+        name: Detroit Javascript
+        description: |-
+          <p>var javaScriptMeetup = "A place for people to discuss the pains and joys of JS. Also a place to learn more about javaScript";</p>
+          <p>We follow the <a href="http://jsconf.com/codeofconduct.html">JSConf Code of Conduct</a>. So please be respectful!</p>
+        lon: -83.13999938964844
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/9/3/9/e/600_448657790.jpeg'
+        lat: 42.459999084472656
+      - country: CA
+        city: Vancouver
+        link: 'http://www.meetup.com/Vancouver-Real-Estate-Technology-and-Data-Meetup/'
+        name: Vancouver Real Estate Technology and Data Meetup
+        description: |-
+          This is a group will discuss the latest and upcoming real-estate technologies for: Agents, Brokerages, MLS, Homeowners. We are passionate about applying data driven approach to the industry, and using the latest tools to help us make smarter decisions.
+          You can be someone who is experienced in the industry or simply someone who is interested in learning more about real-estate. You may be an innovator who is looking to do something amazing in the space. The sky's the limit.
+        lon: -123.04000091552734
+        lat: 49.279998779296875
+    nodeschools:
+      - name: Anchorage NodeSchool
+        location: 'Anchorage, AK, US'
+        organizers:
+          - thejones
+        website: 'http://nodeschool.io/anchorage'
+        repo: 'http://github.com/nodeschool/anchorage'
+        lat: 61.2180556
+        lon: -149.9002778
+      - name: NodeSchool ATL
+        location: 'Atlanta, GA, US'
+        organizers:
+          - airportyh
+        repo: 'http://github.com/nodeschool/atlanta'
+        lat: 33.7489954
+        lon: -84.3879824
+      - name: Austin NodeSchool
+        location: 'Austin, TX, US'
+        organizers:
+          - stefanmve
+        repo: 'http://github.com/nodeschool/austin'
+        lat: 30.267153
+        lon: -97.7430608
+      - name: Bainbridge Island NodeSchool
+        location: 'Bainbridge Island, WA, US'
+        organizers:
+          - awaterma
+          - crtr0
+          - twleung
+        repo: 'http://github.com/nodeschool/bainbridge'
+        lat: 47.6262081
+        lon: -122.5212448
+      - name: Baltimore NodeSchool
+        location: 'Baltimore, MD, US'
+        organizers:
+          - jasonrhodes
+        website: 'http://nodeschool.io/baltimore'
+        twitter: bmorenodeschool
+        repo: 'http://github.com/nodeschool/baltimore'
+        lat: 39.2903848
+        lon: -76.6121893
+      - name: BayNode
+        location: 'Mountain View, CA, US'
+        organizers:
+          - tonypujals
+          - rosskukulinski
+          - CrabDude
+        repo: 'http://github.com/nodeschool/baynode'
+        lat: 37.3860517
+        lon: -122.0838511
+      - name: Boston NodeSchool
+        location: 'Boston, MA, US'
+        organizers:
+          - jstreb
+          - twalling
+        website: 'https://github.com/nodeschool/boston'
+        repo: 'http://github.com/nodeschool/boston'
+        lat: 42.3600825
+        lon: -71.0588801
+      - name: Chicago NodeSchool
+        location: 'Chicago, IL, US'
+        organizers:
+          - azizali
+        website: 'http://nodeschool.io/chicago'
+        twitter: '@heyaziz'
+        repo: 'http://github.com/nodeschool/chicago'
+        lat: 41.8781136
+        lon: -87.6297982
+      - name: Cincinnati NodeSchool
+        location: 'Cincinnati, OH, US'
+        organizers:
+          - fiveisprime
+          - jackboberg
+          - Tzmanics
+        website: 'https://github.com/nodeschool/cincinnati'
+        twitter: CincyNodeSchool
+        repo: 'http://github.com/nodeschool/cincinnati'
+        lat: 39.1031182
+        lon: -84.5120196
+      - name: Cleveland NodeSchool
+        location: 'Cleveland, OH, US'
+        organizers:
+          - kmckee
+          - kwpeters
+        website: 'http://nodeschool.io/cleveland'
+        twitter: nodeSchoolCLE
+        repo: 'http://github.com/nodeschool/cleveland'
+        lat: 41.49932
+        lon: -81.6943605
+      - name: PairColumbus NodeSchool
+        location: 'Columbus, OH, US'
+        organizers:
+          - jbobo
+        website: 'http://nodeschool.io/columbus'
+        repo: 'http://github.com/nodeschool/columbus'
+        lat: 39.9611755
+        lon: -82.99879419999999
+      - name: NodeSchool Dallas
+        location: 'Dallas, TX, US'
+        organizers:
+          - prochafilho
+          - gangstead
+          - leongaban
+        website: 'http://nodeschool.io/dallas'
+        repo: 'http://github.com/nodeschool/dallas'
+        lat: 32.7766642
+        lon: -96.79698789999999
+      - name: Denver-Boulder-Ft. Collins NodeSchool
+        location: 'Denver, CO, US'
+        organizers:
+          - ralucas
+          - patrick-steele-idem
+          - legittalon
+          - mjhea0
+        twitter: '@nodejscolorado'
+        repo: 'http://github.com/nodeschool/denver-boulder'
+        lat: 39.7392358
+        lon: -104.990251
+      - name: Edmonton NodeSchool
+        location: 'Edmonton, AB, CA'
+        organizers:
+          - ryanramage
+        website: 'https://github.com/nodeschool/edmonton'
+        twitter: '@ryan_ramage_'
+        repo: 'http://github.com/nodeschool/edmonton'
+        lat: 53.544389
+        lon: -113.4909267
+      - name: NodeSchool Fort Lauderdale
+        location: 'Fort Lauderdale, FL, US'
+        organizers:
+          - khalifenizar
+          - dambalah
+          - onel0p3z
+        repo: 'http://github.com/nodeschool/fort-lauderdale'
+        lat: 26.1224386
+        lon: -80.13731740000001
+      - name: 'Gainesville, FL NodeSchool'
+        location: 'Gainesville, FL, US'
+        organizers:
+          - aaronbdixon
+        website: 'http://gnvjs.com'
+        twitter: gnvjs
+        repo: 'http://github.com/nodeschool/gainesville'
+        lat: 29.6516344
+        lon: -82.32482619999999
+      - name: NodeSchool - Glendora Javascript
+        location: 'Glendora, CA, US'
+        organizers:
+          - uptownhr
+        website: 'http://nodeschool.io/glendora'
+        repo: 'http://github.com/nodeschool/glendora'
+        lat: 34.1361187
+        lon: -117.865339
+      - name: NodeSchool Wisconsin
+        location: 'Green Bay, WI, US'
+        organizers:
+          - blakehall
+          - zo0o0ot
+        website: 'http://nodeschool.io/wisconsin'
+        twitter: '@greenbayjs'
+        repo: 'http://github.com/nodeschool/wisconsin'
+        lat: 44.51915899999999
+        lon: -88.019826
+      - name: Honolulu NodeSchool
+        location: 'Honolulu, HI, US'
+        organizers:
+          - keokilee
+          - taesup
+          - mrbarbasa
+          - jaywon
+          - thgaskell
+        website: 'http://nodeschool.io/honolulu'
+        repo: 'http://github.com/nodeschool/honolulu'
+        lat: 21.3069444
+        lon: -157.8583333
+      - name: NodeSchool Kamloops
+        location: 'Kamloops, BC, CA'
+        organizers:
+          - jonotron
+          - chadfawcett
+          - chrisfosterelli
+        repo: 'http://github.com/nodeschool/kamloops'
+        lat: 50.674522
+        lon: -120.3272674
+      - name: 'NodeSchool: LA Edition'
+        location: 'Los Angeles, CA, US'
+        organizers:
+          - jxson
+          - emkay
+        website: 'http://nodeschool.io/los-angeles'
+        repo: 'http://github.com/nodeschool/los-angeles'
+        lat: 34.0522342
+        lon: -118.2436849
+      - name: NodeSchool Madison
+        location: 'Madison, WI, US'
+        organizers:
+          - jthoms1
+        website: 'http://nodeschool.io/madison/'
+        twitter: nodeschoolmsn
+        repo: 'http://github.com/nodeschool/madison'
+        lat: 43.0730517
+        lon: -89.4012302
+      - name: NodeSchool Manchester
+        location: 'Manchester, NH, US'
+        organizers:
+          - AlabamaMike
+          - antishow
+          - swinter2
+        website: 'http://nodeschool.io/manchester'
+        twitter: nodemanchvegas
+        repo: 'http://github.com/nodeschool/manchester'
+        lat: 42.9956397
+        lon: -71.4547891
+      - name: NodeSchool Miami
+        location: 'Miami, FL, US'
+        organizers:
+          - khalifenizar
+          - dambalah
+          - onel0p3z
+        repo: 'http://github.com/nodeschool/miami'
+        lat: 25.7616798
+        lon: -80.1917902
+      - name: NodeSchool Minneapolis
+        location: 'Minneapolis, MN, US'
+        organizers:
+          - mikefrey
+        repo: 'http://github.com/nodeschool/minneapolis'
+        lat: 44.977753
+        lon: -93.2650108
+      - name: Modesto NodeSchool
+        location: 'Modesto, CA, US'
+        organizers:
+          - joshterrill
+          - nbunney
+        website: 'http://nodeschool.io/modesto'
+        repo: 'http://github.com/nodeschool/modesto'
+        lat: 37.63909719999999
+        lon: -120.9968782
+      - name: NodeSchool Normal
+        location: 'Normal, IL, US'
+        organizers:
+          - BrainBacon
+          - codysherman
+          - shwnstrmn
+        website: 'http://nodeschool.io/normal'
+        twitter: NodeNormal
+        repo: 'http://github.com/nodeschool/normal'
+        lat: 40.5142026
+        lon: -88.9906312
+      - name: NodeSchool NYC
+        location: 'New York, NY, US'
+        organizers:
+          - hackygolucky
+          - brianloveswords
+          - toolness
+          - hsin421
+          - acingraham
+          - gautamarora
+        website: 'http://nodeschool.io/nyc'
+        repo: 'http://github.com/nodeschool/nyc'
+        lat: 40.7127837
+        lon: -74.0059413
+      - name: Oakland NodeSchool
+        location: 'Oakland, CA, US'
+        organizers:
+          - fauntleroy
+        website: 'http://nodeschool.io/oakland/'
+        twitter: nodeschooloak
+        repo: 'http://github.com/nodeschool/oakland'
+        lat: 37.8043637
+        lon: -122.2711137
+      - name: NodeSchool OC
+        location: 'Orange County, CA, US'
+        organizers:
+          - markhuge
+        repo: 'http://github.com/nodeschool/oc'
+        lat: 33.7174708
+        lon: -117.8311428
+      - name: Orlando NodeSchool
+        location: 'Orlando, FL, US'
+        organizers:
+          - lancehudson
+          - bradplank
+          - calebrosario
+        repo: 'http://github.com/nodeschool/orlando'
+        lat: 28.5383355
+        lon: -81.3792365
+      - name: NodeSchool PDX
+        location: 'Portland, OR, US'
+        organizers:
+          - nrn
+          - dlmanning
+          - wraithan
+          - meandavejustice
+          - justinabrahms
+          - nvcexploder
+          - ngoldman
+        website: 'http://nodeschool.io/pdx/'
+        repo: 'http://github.com/nodeschool/pdx'
+        lat: 45.5230622
+        lon: -122.6764816
+      - name: NodeSchool Philadelphia
+        location: 'Philadelphia, PA, US'
+        organizers:
+          - adobley
+        website: 'http://nodeschool.io/philadelphia'
+        twitter: nodeschoolphl
+        repo: 'http://github.com/nodeschool/philadelphia'
+        lat: 39.9525839
+        lon: -75.1652215
+      - name: 'Nodeschool Portland, ME'
+        location: 'Portland, ME, US'
+        organizers:
+          - carlodicelico
+          - jaegerpicker
+        website: 'http://nodeschool.io/portland-me'
+        repo: 'http://github.com/nodeschool/portland-me'
+        other: 'http://www.meetup.com/Portland-Maine-Nodeschool'
+        lat: 43.66147100000001
+        lon: -70.2553259
+      - name: Raleigh-Durham NodeSchool
+        location: 'Raleigh-Durham, NC, US'
+        organizers:
+          - brianpmarks
+          - jbelmont
+        website: 'http://nodeschool.io/raleigh-durham'
+        twitter: rdunodeschool
+        repo: 'http://github.com/nodeschool/raleigh-durham'
+        lat: 35.8991678
+        lon: -78.86364019999999
+      - name: NodeSchool Reno
+        location: 'Reno, NV, US'
+        organizers:
+          - colinloretz
+          - hmudesign
+          - w1zeman1p
+        website: 'http://nodeschool.io/reno/'
+        repo: 'http://github.com/nodeschool/reno'
+        lat: 39.5296329
+        lon: -119.8138027
+      - name: NodeSchool SLO
+        location: 'San Luis Obispo, CA, US'
+        organizers:
+          - ecwyne
+        website: 'http://nodeschool.io/san-luis-obispo/'
+        repo: 'http://github.com/nodeschool/san-luis-obispo'
+        lat: 35.2827524
+        lon: -120.6596156
+      - name: NodeSchool SF
+        location: 'San Francisco, CA, US'
+        organizers:
+          - duquet
+          - llkats
+          - jedireza
+        website: 'http://nodeschool.io/sanfrancisco/'
+        twitter: nodeschoolsf
+        repo: 'http://github.com/nodeschool/sanfrancisco'
+        lat: 37.7749295
+        lon: -122.4194155
+      - name: Seattle NodeSchool
+        location: 'Seattle, WA, US'
+        organizers:
+          - sethvincent
+          - YonasBerhe
+          - blakmatrix
+        website: 'http://nodeschool.io/seattle'
+        repo: 'http://github.com/nodeschool/seattle'
+        lat: 47.6062095
+        lon: -122.3320708
+      - name: Stanford University NodeSchool
+        location: 'Stanford, CA, US'
+        organizers:
+          - feross
+          - jhiesey
+          - abi
+        repo: 'https://github.com/nodeschool/stanford'
+        lat: 37.42410599999999
+        lon: -122.1660756
+      - name: NodeSchool STL
+        location: 'St. Louis, MO, US'
+        organizers:
+          - robbennet
+        website: 'http://nodeschool.io/stlouis'
+        repo: 'http://github.com/nodeschool/stlouis'
+        lat: 38.6270025
+        lon: -90.19940419999999
+      - name: Tacoma NodeSchool
+        location: 'Tacoma, WA, US'
+        organizers:
+          - NorthDecoder
+        website: 'http://nodeschool.io/tacoma'
+        repo: 'http://github.com/nodeschool/tacoma'
+        lat: 47.2528768
+        lon: -122.4442906
+      - name: Tampa Nodeschool
+        location: 'Tampa, FL, US'
+        organizers:
+          - eliwheaton
+        repo: 'https://github.com/nodeschool/tampa'
+        lat: 27.950575
+        lon: -82.4571776
+      - name: NodeSchool Toronto
+        location: 'Toronto, CA'
+        organizers:
+          - rmillr
+          - darcyclarke
+          - richgilbank
+          - jeffjewiss
+          - brenna
+          - andrewdamelio
+          - tessalt
+        website: 'http://nodeschool.io/toronto'
+        twitter: 'https://twitter.com/nodeschoolto'
+        repo: 'http://github.com/nodeschool/toronto'
+        lat: 43.653226
+        lon: -79.3831843
+      - name: Utah Node Ninjas
+        location: 'Provo, UT, US'
+        organizers:
+          - therebelrobot
+        website: 'http://www.meetup.com/Node-Ninjas/'
+        repo: 'https://github.com/Utah-Node-Ninjas'
+        lat: 40.2338438
+        lon: -111.6585337
+      - name: NodeSchool Vancouver
+        location: 'Vancouver, BC, CA'
+        organizers:
+          - sintaxi
+          - notmatt
+          - afabbro
+          - lvivier
+          - gyaresu
+        website: 'http://nodeschool.io/vancouver/'
+        repo: 'http://github.com/nodeschool/vancouver'
+        lat: 49.2827291
+        lon: -123.1207375
+      - name: Western Massachusetts NodeSchool
+        location: 'Western Massachusetts, US'
+        organizers:
+          - Sequoia
+          - a-pasquale
+        website: 'http://nodeschool.io/western-mass/'
+        repo: 'https://github.com/nodeschool/western-mass'
+        lat: 42.5944125
+        lon: -70.68915439999999
+      - name: NodeSchoolDC
+        location: 'Washington, DC, US'
+        organizers:
+          - robbiethegeek
+          - joshfinnie
+          - JuanCaicedo
+          - danpaz
+        website: 'http://nodeschool.io/washingtondc/'
+        twitter: NodeSchoolDC
+        repo: 'http://github.com/nodeschool/washingtondc'
+        lat: 38.9071923
+        lon: -77.0368707
+  - region: Океанія
+    meetups:
+      - country: NZ
+        city: Auckland
+        link: 'http://www.meetup.com/AucklandJS/'
+        name: AkJS
+        description: '<p>A meetup for people in Auckland interested in JavaScript.</p>'
+        lon: 174.75999450683594
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/2/1/3/6/600_61388502.jpeg'
+        lat: -36.849998474121094
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/MelbNodeJS/'
+        name: The Melbourne Node.JS Meetup Group
+        description: |-
+          <p><span><strong>HTTP 302: &nbsp;<a href="http://groups.google.com/group/nodejsau">http://groups.google.com/group/nodejsau</a>. Join the Google Group. All discussions and event notices occur here.</strong></span></p>
+          <p>For Melbourne Noders wanting to chat about Node libraries or hack with others (on their stuff, on other's, on everyone's). Beginners and experts welcome alike.<br><br>Our Code of Conduct is located here:&nbsp;<a href="https://gist.github.com/louiscntr/84be3ead90ed77f8a5ba">https://gist.github.com/louiscntr/84be3ead90ed77f8a5ba</a></p>
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/2/e/6/600_88481702.jpeg'
+        lat: -37.810001373291016
+      - country: AU
+        city: Perth
+        link: 'http://www.meetup.com/perth-js/'
+        name: perth.js
+        description: "<p>A group for JavaScript developers - an opportunity to explore the growing JS ecosystem, exchange battle stories and generally shoot the breeze... Let us know if you have a topic / passion you'd like to discuss!</p>"
+        lon: 115.83999633789062
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/b/9/c/0/600_154247552.jpeg'
+        lat: -31.959999084472656
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/sydney-node-ninjas/'
+        name: Sydney Node.ninjas
+        description: "<p>We started as a small hack night in the ThoughtWorks Sydney office... but we think it's time to grow!</p>\n<p>Whether you've just heard about <strong>Node.js</strong>, used it for personal projects, or whether it already powers your commercial applications, <strong>join the Sydney community</strong> to share your experiences and learn about the fastest growing platform of 2012.</p>\n<p>We're aiming to get a mix of informal chats and presentations, and some opportunities for hacking. <strong>All skill levels are welcome</strong>!</p>\n<p>Head over to <a href=\"https://github.com/sydney-node-ninjas/meetup/wiki\">the wiki</a> for a list of past meetups, and session ideas.</p>\n<p>\_</p>"
+        lon: 151.2100067138672
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/8/6/b/c/600_172414492.jpeg'
+        lat: -33.869998931884766
+      - country: SG
+        city: Singapore
+        link: 'http://www.meetup.com/Singapore-JS/'
+        name: SingaporeJS
+        description: "<p>Developers interested in sharing knowledge and growing their skills around JavaScript and modern web technology: e.g. ES6, AltJS, NodeJS, Angular, Ember, Browserify, Web Components, <span>HTML5 APIs,</span> LevelDB, etc.</p>\n<p> <br> <strong>Goals</strong></p>\n<ul> \n <p>A monthly meetup</p> \n <p>Post-meetup meals/drinks for socialising.</p> \n <p>Prefer many short talks vs. few long talks.</p> \n <p>Focus on cutting-edge technologies and development techniques.</p> \n <p>Focus on open source over commercial products.</p> \n <p>Focus on clean code.</p> \n</ul>\n<p> <br> If you want to help out, sponsor, or have any suggestions or feedback, just get in touch!</p>"
+        lon: 103.8499984741211
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/b/4/4/1/600_436066145.jpeg'
+        lat: 1.2999999523162842
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/EmberJS-Melbourne/'
+        name: Melbourne Ember.js Meetup
+        description: "<p>The Ember.js Melbourne Meetup is for anyone who wants to learn Ember.js, is already using it heavily, or wants to stay up to date with the fast changing developments of Ember.js. Let's get together periodically to talk about code, eat, drink, and generally geek out. See you there!</p>"
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/2/4/0/600_233505632.jpeg'
+        lat: -37.810001373291016
+      - country: NZ
+        city: Auckland
+        link: 'http://www.meetup.com/AucklandNodeJs/'
+        name: Auckland Node.js Meetup
+        description: "<p>A group for Auckland-based developers who are interested in finding out more about this new fandangled technology called Node.js... You may be a front-end coder who is looking to apply your JavaScript skills to back-end development, or a full-stack developer who presently codes in Ruby / Python / PHP / insert preferred language here / etc., and is curious to see what asynchronous programming has to offer (and whether it really kicks your current preferred language's *ss). If you wish to become a competent practitioner of Nodejitsu, then enter the Node.nz dojo!</p>"
+        lon: 174.75999450683594
+        lat: -36.849998474121094
+      - country: NZ
+        city: Wellington
+        link: 'http://www.meetup.com/Node-js-Wellington/'
+        name: Node.js Wellington
+        description: "<p>A group for anyone interested in Node.js, JavaScript, frontend/backend and everywhere where JavaScript runs, whether it's the browser, the server, your database or under your kitchen sink and everything in between. We're a social group and whilst we don't (yet) do organised presentations, we're happy to swap ideas and chat about different techniques.</p>"
+        lon: 174.77999877929688
+        lat: -41.279998779296875
+      - country: AU
+        city: Gold Coast
+        link: 'http://www.meetup.com/goldcoastjs/'
+        name: 'GCJS: Gold Coast JavaScript'
+        description: "<p>Hey we all know that JavaScript is the new/old black, but there no denying it - there's a lot of people on the Gold Coast happily coding JavaScript, so if there's any programming group that's going to make it - this is it!</p>"
+        lon: 153.44000244140625
+        lat: -28.06999969482422
+      - country: NZ
+        city: Christchurch
+        link: 'http://www.meetup.com/CHCH-JS/'
+        name: CHCH.JS
+        description: |-
+          <p>For those in Christchurch interested in everything JavaScript. Node.js, frameworks, libraries and everything in between. Newbies, battle-hardened veterans, all welcome!</p>
+          <p><span>We meet once a month and</span> <span>alternate our monthly sessions between node.js and</span> <span>front-end</span> <span>JavaScript.</span></p>
+          <p>Join the group to find out when and where our next meetup is.</p>
+          <p>Tell us your talk ideas or submit a talk here: http://goo.gl/forms/v8lcHdrGJH<br></p>
+        lon: 172.63999938964844
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/1/0/b/e/600_440464286.jpeg'
+        lat: -43.529998779296875
+      - country: SG
+        city: Singapore
+        link: 'http://www.meetup.com/Meteor-Singapore/'
+        name: Meteor Singapore
+        description: "<p>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>"
+        lon: 103.8499984741211
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/5/8/7/2/600_421822642.jpeg'
+        lat: 1.2999999523162842
+      - country: NZ
+        city: Auckland
+        link: 'http://www.meetup.com/Auckland-d3-js/'
+        name: Auckland d3-js
+        description: |-
+          <p>For people interested in implementing svg graphics with <a href="http://d3js.org">d3.js</a><br>
+
+          </p>
+        lon: 174.75999450683594
+        lat: -36.849998474121094
+      - country: NZ
+        city: Wellington
+        link: 'http://www.meetup.com/hackpack/'
+        name: Hack Pack
+        description: "<p>You can think of Hack Pack like a social club for hackers.\_</p>\n<p>Rather than us focus on presentations and speakers (there are already lots of great meetups which do this) we're focusing on fulfilling the social needs of the community.</p>\n<p><span><b>Join us for:</b></span></p>\n<p>•\_<span>Waxing lyrical about node/ruby/next big thing.</span></p>\n<p>•\_<span>Playing video games</span><br>\n\n</p>\n<p>•\_<span>Trying your hand at table tennis</span></p>\n<p>•\_<span>Having the odd drink</span></p>\n<p>•\_Perhaps partaking in a slice of pizza</p>\n<p>•\_Starting side-projects</p>\n<p>•\_Making friends!</p>\n<p><br>\n\n</p>\n<p><br>\n\n</p>\n<p><br>\n\n</p>\n<p><br>\n\n</p>"
+        lon: 174.77999877929688
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/a/e/7/6/600_415424662.jpeg'
+        lat: -41.279998779296875
+      - country: SG
+        city: Singapore
+        link: 'http://www.meetup.com/NodeBotsSingapore/'
+        name: NodeBots Singapore
+        description: "<p>NodeBots Singapore is a meetup for robotics makers.\_</p>\n<p>•\_<span>NodeBots are robots that are controlled by node.js/javascript.</span> <a href=\"http://nodebots.io/\" target=\"_blank\" class=\"linkified\">http://nodebots.io/</a><span>\_</span></p>\n<p><span>• Examples of NodeBots:\_</span><a href=\"https://github.com/rwaldron/johnny-five\" target=\"_blank\" class=\"linkified\">https://github.com/rwaldron/johnny-five</a> <a href=\"http://nodecopter.com/\" target=\"_blank\" class=\"linkified\">http://nodecopter.com/</a><span>\_</span></p>\n<p>•\_<span>The group will meet quarterly.\_</span></p>\n<p><span>•\_</span><span>Let's get together to talk, hack, and demo robotics.\_</span></p>\n<p>•\_<span>Join a supportive and growing international community. Make your own R2D2.</span></p>"
+        lon: 103.8499984741211
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/7/8/a/c/600_318930892.jpeg'
+        lat: 1.2999999523162842
+      - country: AU
+        city: Adelaide
+        link: 'http://www.meetup.com/adelaidejs/'
+        name: Adelaide front-end JS frameworks
+        description: '<p>This meet-up is focused on learning and applying front-end JS frameworks like Ember.js, AngularJS and React etc to create and maintain ambitious web applications.</p>'
+        lon: 138.60000610351562
+        lat: -34.93000030517578
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/Meteor-Sydney/'
+        name: Meteor Sydney
+        description: |-
+          <p>Meet other developers using <a href="http://www.meteor.com">Meteor</a>. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started.</p>
+          <p>Join the community channel at:&nbsp;<a href="https://meteorsydney.herokuapp.com/">https://meteorsydney.herokuapp.com/</a></p>
+        lon: 151.2100067138672
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/6/2/0/600_424418432.jpeg'
+        lat: -33.869998931884766
+      - country: AU
+        city: Perth
+        link: 'http://www.meetup.com/meteor-perth/'
+        name: Meteor Perth
+        description: |-
+          <p><span>Meet other developers using Meteor. Share your knowledge, apps, and get feedback from others. Meteor is an open-source platform for building top-quality web apps in a fraction of the time, whether you're an expert developer or just getting started. Join in on live Devshop viewings, hackathons, inspirational classes and casual poolside catchups!</span><br>
+
+          </p>
+        lon: 115.83999633789062
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/d/4/a/600_424443402.jpeg'
+        lat: -31.959999084472656
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/Stripe-Australia/'
+        name: 'The Stripe Meetup Group: Australia'
+        description: '<p>Meet the Stripe team and members of the Stripe community in Australia.</p>'
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/7/0/b/e/600_332848862.jpeg'
+        lat: -37.810001373291016
+      - country: SG
+        city: Singapore
+        link: 'http://www.meetup.com/CreativeCoders/'
+        name: Creative Coders
+        description: |-
+          <p>Creative Coders is a Singapore user group for programmers to get together and discuss about how to use technologies creatively. Anyone who is interested in coding and/or creative coding is welcomed to join. The purpose of the group is to make programmers happy and excited about their job and to inspire non-programmers to pick up coding as a hobby. We will focus on trendy technologies which are also fun to work with, such as HTML5, Processing, Mobile development, OpenFrameworks and Node.js etc.</p>
+          <p>Join our Facebook group to get fresh updates,&nbsp;<a href="https://www.facebook.com/groups/ccmail/" class="linkified">https://www.facebook.com/groups/ccmail/</a></p>
+        lon: 103.8499984741211
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/9/b/0/2/600_447399682.jpeg'
+        lat: 1.2999999523162842
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/AngularJS-Melbourne/'
+        name: AngularJS Melbourne
+        description: "<p>This group is for web developers \_in Australia who want to learn more about AngularJS and applications built with this framework.</p>\n<p>Each meetup will host 2 speakers who have built amazing stuff with AngularJS and want to share it with others. After that and during the breaks - networking and sharing of experience.<br>\n\n</p>"
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/b/5/6/0/600_341146432.jpeg'
+        lat: -37.810001373291016
+      - country: SG
+        city: Singapore
+        link: 'http://www.meetup.com/Singapore-Node-Community/'
+        name: Singapore Node Community
+        description: |-
+          <p>A informal meetup group focused on bringing together developers that use Web frameworks built on top of Node.JS. Node.js is a modern web technology that is open source, cross-platform runtime environment for server-side and networking applications. The community is free and non profit effort to bring developers together that are interested in sharing their knowledge in a casual way after work.&nbsp;</p>
+          <br>
+          <p>Meetup Talks focused on :&nbsp;</p>
+          <p>•&nbsp;Web Frameworks built on top of NodeJS (Express etc)</p>
+          <p>•&nbsp;Best Practices- Security of Node.JS</p>
+          <p>•&nbsp;Popular Node Modules</p>
+          <p>•&nbsp;Production stories</p>
+          <p>•&nbsp;Short Talks</p>
+          <p>•&nbsp;Socialising after meetups</p>
+          <br>
+          <p>We are always looking for friends to help arrange the space and food. If you think you can help, get in touch!</p>
+          <br>
+        lon: 103.8499984741211
+        lat: 1.2999999523162842
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/Melbourne-Tessel-Enthusiasts/'
+        name: Melbourne Tessel Enthusiasts
+        description: 'This is a group for Tessel enthusiasts or anyone who is interested in finding out what you can do with one. Tessel is a Wifi enabled microcontroller board (and a set of add-on modules) that can be programmed with JavaScript and is compatible with Node.js. More information at: http://tessel.io/.'
+        lon: 144.9600067138672
+        lat: -37.810001373291016
+      - country: SG
+        city: Singapore
+        link: 'http://www.meetup.com/Singapore-Node-JS/'
+        name: Singapore Node.JS
+        description: Anything and everything Node.JS in Singapore
+        lon: 103.8499984741211
+        lat: 1.2999999523162842
+      - country: AU
+        city: Brisbane
+        link: 'http://www.meetup.com/Brisbane-AppDynamics/'
+        name: Brisbane AppDynamics User Group
+        description: "<p>AppDynamics! Where Application Perfomance meets DevOps. The hottest APM company on the planet. Find out what's new from the local AppDynamics team, discuss trends in APM technology, and share stories with other like-minded AppDynamos.</p>"
+        lon: 153.02000427246094
+        lat: -27.459999084472656
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/Melbourne-AppDynamics/'
+        name: AppDynamics Melbourne User Group
+        description: |-
+          <p>AppDynamics! Where Application Performance meets DevOps. The hottest APM company on the planet.</p>
+          <p><img src="http://photos3.meetupstatic.com/photos/event/d/0/c/e/600_437633454.jpeg"></p>
+          <p><span>Find out what's new from the local AppDynamics team, discuss trends in APM technology, and share stories with other like-minded AppDynamos.</span> <br></p>
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/0/9/0/600_447221104.jpeg'
+        lat: -37.810001373291016
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/Sydney-AppDynamics/'
+        name: AppDynamics Sydney User Group
+        description: "<p>AppDynamics! The hottest APM company on the planet. The home of the application performance super hero. Find out what's new from the local AppDynamics team, discuss trends in APM technology, and share stories with other like minded AppDynamos.</p>"
+        lon: 151.2100067138672
+        lat: -33.869998931884766
+      - country: AU
+        city: Brisbane
+        link: 'http://www.meetup.com/NodeBots-Brisbane/'
+        name: NodeBots Brisbane
+        description: "<p>Use JavaScript to manipulate machines. From blinking lights to Sumo Bot battles, Remote control cats, and Bull fighting with quadcopters...</p>\n<p><span style=\"font-size : 16px\">Anyone with an interest in JavaScript or Robots, or in\_designing or building web connected physical things\_should join this meetup.\_</span><span style=\"font-size : 16px\">You’ll learn about electronics, NodeJS and Arduino, meet new people and have loads of fun while building NodeBots.\_You’ll use JavaScript but also get to play with Arduinos, Servos, Sensors, Node.js, Johnny-Five, LEDs and maybe even a drone or two.</span></p>\n<p>You don't need to bring any robotics or electronics with you if you don't have any, as the group has kits you can borrow but please bring a laptop if you have one running NodeJS.\_<span style=\"font-size : 16px\">You can find all the setup instructions you'll need on our GitHub site, or ask one of the mentors for a hand getting your development environment set up:\_</span><a href=\"https://github.com/nodebotsau/nbdau\" style=\"font-size : 16px\">https://github.com/nodebotsau/nbdau</a></p>\n<p>This meetup group formed after the fun we had being part of International NodeBots day on July 26th 2014 and will meet monthly in the new Fabrication Lab at The Edge so that we can continue to develop our robots. Watch this space for details of the next meetup! See\_<a href=\"http://nodebotsau.github.io/\">http://nodebotsau.github.io/</a> for more about NodeBots in Australia or follow us on twitter @nodebotsau</p>"
+        lon: 153.02000427246094
+        group_photo:
+          photo_link: 'http://photos2.meetupstatic.com/photos/event/9/7/6/0/600_390998752.jpeg'
+        lat: -27.459999084472656
+      - country: NZ
+        city: Wellington
+        link: 'http://www.meetup.com/NewZealand-AppDynamics/'
+        name: AppDynamics New Zealand User Group
+        description: |-
+          <p><span>AppDynamics! Where Application Performance meets DevOps. The hottest APM company on the planet. </span> <br></p>
+          <p><span>Find out what's new from the local AppDynamics team, discuss trends in APM technology and share stories with other like-minded AppDynamos.</span> <br></p>
+        lon: 174.77999877929688
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/a/0/b/7/600_447221143.jpeg'
+        lat: -41.279998779296875
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/ng-sydney/'
+        name: ng-sydney
+        description: "<p>Trying to get everyone who is interesting in Angular and happens to be around Sydney. &lt;br&gt;</p> \n<p><b>A Few Things To Know:</b></p> \n<p>- This group was created in December 2014 as an earlier AngularJS group hasn't had any content meetups since November 2013.</p> \n<p>- Our meetings are usually held on the first Wednesday of every month. Make sure you get notifications as RSVPs usually run out in couple of days only.</p> \n<p>- To make sure this group doesn't just stop like the earlier one, we always welcome new people to come and speak about whatever they want. Send the organizer a message with a session title and short abstract (or any rambling incomplete idea, we'll help turn it into a proper talk), and we'll get you talking next month :)</p>"
+        lon: 151.2100067138672
+        lat: -33.869998931884766
+      - country: NZ
+        city: Auckland
+        link: 'http://www.meetup.com/ReactJS-Auckland/'
+        name: Auckland ReactJS Meetup
+        description: "<p>ReactJs is a fun, easy to use Javascript library built at Facebook. <a href=\"http://facebook.github.io/react/\" class=\"linkified\">http://facebook.github.io/react/</a> Join us if you'd like to learn more or if you have your own ReactJs experience to share that others can benefit from.</p>"
+        lon: 174.75999450683594
+        lat: -36.849998474121094
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/Sydney-Cloud-Foundry-Meetup/'
+        name: Sydney Cloud Foundry Meetup
+        description: |-
+          <p>We will talk about all things Cloud Foundry. Whether thats about buildpacks, service brokers, microservices, BOSH, high availability, Docker and container orchestration, Diego, Lattice, multi data centre design, continuous delivery or cloud native application design. We got you covered.</p>
+          <p><img src="http://photos1.meetupstatic.com/photos/event/a/5/7/9/600_435762361.jpeg"></p>
+          <p><br></p>
+          <p> <br></p>
+        lon: 151.2100067138672
+        group_photo:
+          photo_link: 'http://photos3.meetupstatic.com/photos/event/a/4/e/1/600_435762209.jpeg'
+        lat: -33.869998931884766
+      - country: AU
+        city: Canberra
+        link: 'http://www.meetup.com/CanberraJS/'
+        name: CanberraJS
+        description: Canberra Javascript is a bi-monthly meetup of Javascript Developers and people interested to learn more about web development using Javascript.
+        lon: 149.1300048828125
+        lat: -35.310001373291016
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/Sydney-Full-Stack-Development-Meetup/'
+        name: Sydney Full Stack Development Meetup
+        description: |-
+          <p><b>Sydney Full Stack Development Group&nbsp;</b></p>
+          <p><span>This is a monthly event, where Seasoned Full Stack Developers, Aspiring Programmers and Technology Entrepreneurs assemble, to learn, network and have fun.&nbsp;</span></p>
+          <p><span>Membership is free and open to anyone with an interest in Software Engineering!&nbsp;</span>&nbsp;</p>
+          <p><b>Why Attend?&nbsp;</b></p>
+          <p>• &nbsp;<span>We'll have guest speakers, workshops and presentations from Industry Leaders and Full Stack Brainiacs.&nbsp;</span></p>
+          <p>• &nbsp;<span>There will be&nbsp;</span><span>group discussions, debating the burning issues, latest trends and the&nbsp;</span><span>evolution of the Full Stack Developer. &nbsp;</span></p>
+          <p>• &nbsp;<span>Best of all, we'll&nbsp;</span><span>provide free Pizza &amp; Beer. &nbsp;</span></p>
+          <p> <br></p>
+          <p> <br></p>
+        lon: 151.2100067138672
+        lat: -33.869998931884766
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/front-end-developers-javascript/'
+        name: 'The Melbourne F-Enders: Building Front End Together'
+        description: |-
+          <p>This group is designed to share and build expert front end development knowledge and offer training and advancement to build on your current skill set.</p>
+          <p>Looking to master&nbsp;building quality web interfaces. You've got the basics down and don't want to learn from teachers who just offer you meaningless results, you want to learn from the masters!&nbsp;</p>
+          <p>Here, you get experienced professionals and people who&nbsp;are actively shaping the industry in front end technologies and who have a true passion for what they do. &lt;br&gt; &lt;br&gt;Join us and front-end professionals and master JavaScript, AngularJS, HTML5/CSS3 and UI frameworks etc.</p>
+          <p>We have monthly meetup and regular Frontend courses to offer and assist you with all the necessary tools you will need to become a great front end developer.</p>
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos4.meetupstatic.com/photos/event/d/0/8/5/600_446993381.jpeg'
+        lat: -37.810001373291016
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/Melbourne-Microservices-Meetup/'
+        name: Melbourne Microservices Meetup
+        description: |-
+          <p>This is a group interested in microservices, nodejs, react, flux, javascript where the members could help redifine a new architecure of javascript related solutions with microservices. Developers, business minded people, and solution architects all welcome. &nbsp;For anyone interested in learning more about me, I can be contacted at the following:</p>
+          <p><br></p>
+          <p><a href="https://au.linkedin.com/in/matthewlowery">LinkedIn Profile</a></p>
+          <p><a href="http://www.lowery.com/">My Blog</a></p>
+          <p><a href="http://www.meetup.com/Melbourne-Microservices-Meetup/">Melbourne Meetup</a></p>
+          <p>Skype: matthew.magicks</p>
+          <br>
+        lon: 144.9600067138672
+        lat: -37.810001373291016
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/Flow-based-Programming-Melbourne/'
+        name: Flow-based Programming Melbourne
+        description: |-
+          <p>This is a group for anyone interested in flow-based programming and/or Noflo. All skill levels are welcome. I started this group to meet tech enthusiasts who are interested in this promising development paradism.</p>
+          <p><a href="https://www.google.com.au/search?client=safari&amp;rls=en&amp;q=flow+based+programming&amp;ie=UTF-8&amp;oe=UTF-8&amp;gfe_rd=cr&amp;ei=sb5PVqj4OczN8Aem8aiQDg#q=flow+based+programming&amp;tbm=vid">More information about FBP</a> <br></p>
+        lon: 144.9600067138672
+        group_photo:
+          photo_link: 'http://photos1.meetupstatic.com/photos/event/9/e/5/0/600_444520528.jpeg'
+        lat: -37.810001373291016
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/MelbourneJS/'
+        name: JS Workshops
+        description: "<p>Where we meet to hack together on JavaScript. We intend to run workshop/hacking sessions to learn upcoming ES6/7 features, and how to put new ideas into practice.&nbsp; &lt;br&gt;</p> \n<p><b>Code of Conduct</b> &lt;br&gt; &lt;br&gt;MelbourneJS events are community events intended for networking and collaboration as well as learning. We value the participation of every member of the JS community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the event and in interactions online associated with this group. &lt;br&gt; &lt;br&gt;To make clear what is expected, everyone taking part in our events and discussions — instructors, helpers, organizers, and learners — is required to conform to the following Code of Conduct. Organizers will enforce this code throughout every meet-up, but you may also contact us directly the organizer directly <a href=\"http://www.meetup.com/Melbourne-JS/members/\" class=\"linkified\">http://www.meetup.com/Melbourne-JS/members/</a>.... All communication will be treated as confidential. &lt;br&gt;<b> &lt;br&gt;THE SHORT VERSION</b> &lt;br&gt; &lt;br&gt;&nbsp; The MelboureJS is dedicated to providing a harassment-free learning experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, religion, or choice of text editor. We do not tolerate harassment of participants in any form. &lt;br&gt; &lt;br&gt;&nbsp; All communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate for any event. &lt;br&gt; &lt;br&gt;&nbsp; Be kind to others. Do not insult or put down other attendees. &lt;br&gt; &lt;br&gt;&nbsp; Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate. &lt;br&gt; &lt;br&gt;&nbsp; Attendees violating these rules may be asked to leave the event at the sole discretion of the conference organizers without a refund of any charge that may have been levied. &lt;br&gt; &lt;br&gt;Thank you for helping make this a welcoming, friendly event for all. &lt;br&gt; &lt;br&gt;THE LONGER VERSION &lt;br&gt; &lt;br&gt;Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. &lt;br&gt; &lt;br&gt;Participants asked to stop any harassing behavior are expected to comply immediately. &lt;br&gt; &lt;br&gt;Be careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be offensive to those around you. &lt;br&gt; &lt;br&gt;If a participant engages in behavior that violates this code of conduct, the organizers may take any action they deem appropriate, including warning the offender or expulsion from the event with no refund of any fee that may have been levied. &lt;br&gt; &lt;br&gt;</p>"
+        lon: 144.9600067138672
+        lat: -37.810001373291016
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/Melbourne-Aurelia-Meetup/'
+        name: Melbourne Aurelia Meetup
+        description: "Finally, a group for conventional and unconventional people who love convention over configuration! If you want to find out more about this framework, or want to see one of the next big things in single-page application development, come and join us. \"Aurelia is a next generation JavaScript client framework that leverages simple conventions to empower your creativity.\" OK, so that was cut and pasted from the http://Aurelia.io website. What it's trying to say is that if you want to develop advanced front-ends without creating a spaghetti monster with fifty configuration options for factories, directives, providers, routers, and dozens of other configured objects, Aurelia might be more suited to your needs. Come and join us to find out if it does meet you needs, as we're a group of non-zealots who are open to any and all practical, useful, real-world applicable technologies. Oh, and we promise not to demonstrate To-do apps, Twitter clients, or weather displaying widgets."
+        lon: 144.9600067138672
+        lat: -37.810001373291016
+      - country: AU
+        city: Melbourne
+        link: 'http://www.meetup.com/1-Night-Daniel-Khan-Harald-Zeitlhofer-Klaus-Enzenhofer/'
+        name: '1 Night! Daniel Khan, Harald Zeitlhofer & Klaus Enzenhofer'
+        description: 'In town together for 1 night only, Daniel "Mr Node.js" Khan, Harald "PHP" Zeitlhofer, &amp; Klaus Enzenhofer - aka Mr Mobile, will be delivering presentations together. This is a one night only super meetup, and Dynatrace will be providing the refreshments. There is no entry fee, we only ask that you register before coming, and that you get in quick because we do have to cap numbers due to venue size.'
+        lon: 144.9600067138672
+        lat: -37.810001373291016
+      - country: AU
+        city: Sydney
+        link: 'http://www.meetup.com/Meet-The-Masters-1-Night-Only-Sydney/'
+        name: 'Meet The Masters 1 Night Only, Sydney'
+        description: |-
+          We've got Daniel Khan, Klaus Enzenhofer, and Harald Zeitlhofer visiting for just one night, so we thought it would be a grand idea to hold a massive meetup for them.
+
+          All three are experts in their respective fields, and they are all highly experienced conference presenters - so this promises to be an evening of Node.js, PHP, and Mobile Cloud learning from some great speakers.
+
+          This is a free event, with food and drink provided, but we need you to register as numbers are limited by the venue size.
+        lon: 151.2100067138672
+        lat: -33.869998931884766
+    nodeschools:
+      - name: Auckland NodeSchool
+        location: 'Auckland, NZ'
+        organizers:
+          - jladuval
+          - kevnz
+          - ram-manthry
+        website: 'http://nodeschool.io/auckland/'
+        repo: 'http://github.com/nodeschool/auckland'
+        lat: -36.8484597
+        lon: 174.7633315
+      - name: Brisbane NodeSchool
+        location: 'Brisbane, AU'
+        organizers:
+          - rvagg
+          - garrows
+        repo: 'http://github.com/nodeschool/brisbane'
+        lat: -27.4710107
+        lon: 153.0234489
+      - name: NodeSchool Christchurch
+        location: 'Christchurch, NZ'
+        organizers:
+          - digitalsadhu
+          - coder_stu
+          - gmwills
+          - gingermusketeer
+        website: 'http://nodeschool.io/christchurch/'
+        repo: 'http://github.com/nodeschool/christchurch'
+        lat: -43.5320544
+        lon: 172.6362254
+      - name: NodeSchool Hobart
+        location: 'Hobart, AU'
+        organizers:
+          - joshgillies
+          - jonnyscholes
+          - timheap
+          - MalucoMarinero
+        website: 'http://nodeschool.io/hobart'
+        repo: 'http://github.com/nodeschool/hobart'
+        lat: -42.8819032
+        lon: 147.3238148
+      - name: NodeSchool Perth
+        location: 'Perth, AU'
+        organizers:
+          - nii236
+          - miqid
+        website: 'http://nodeschool.io/perth'
+        repo: 'https://github.com/nodeschool/perth'
+        gitter: 'https://gitter.im/nodeschool/perth'
+        lat: -31.9535132
+        lon: 115.8570471
+      - name: Sydney NodeSchool
+        location: 'Sydney, AU'
+        organizers:
+          - rvagg
+          - DamonOehlman
+        website: 'http://nodeschool.io/sydney'
+        repo: 'https://github.com/nodeschool/sydney'
+        lat: -33.8674869
+        lon: 151.2069902
+      - name: NodeSchool Wellington
+        location: 'Wellington, NZ'
+        organizers:
+          - vimto
+          - chilts
+        repo: 'http://github.com/nodeschool/wellington'
+        lat: -41.2864603
+        lon: 174.776236
+
+---
diff --git a/locale/uk/get-involved/index.md b/locale/uk/get-involved/index.md
new file mode 100755
index 0000000000000..ae887f0763876
--- /dev/null
+++ b/locale/uk/get-involved/index.md
@@ -0,0 +1,59 @@
+---
+title: Приєднатись
+layout: contribute.hbs
+---
+
+# Ми заохочуємо будь–яку підтримку з боку спільноти.
+
+Спільнота Node.js — велика, цілісна і відкрита для багатьох користувачів, які підтримують нас. Якщо ви хочете [повідомити про помилку](https://github.com/nodejs/node/issues), [допомогти з документацією](/en/get-involved/contribute/) або [вдосконалити кодову базу](/en/get-involved/development/) проекту, ви прийшли за адресою. Перегляньте ресурси нашої спільноти, щоб зрозуміти, як ви можете допомогти:
+
+<hr>
+
+## Обговорення
+
+- [Список іш’ю на GitHub](https://github.com/nodejs/node/issues) — це місце, де обговорюють ключовий функціонал Node.js.
+
+- Для живого чату про розробку на Node перейдіть на `irc.freenode.net` у канал `#node.js` через [IRC клієнт](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) або підключіться до каналу через веб–браузер з допомогою [ WebChat від freenode](http://webchat.freenode.net/?channels=node.js).
+
+- Офіційний аккаунт Node.js у Twitter [nodejs](https://twitter.com/nodejs).
+
+- [Node Weekly](http://nodeweekly.com) це поштове розсилання, що збирає найсвіжіші події та новини довкола спільноти Node.js.
+
+- [Planet Node](http://planetnodejs.com) це агрегатор блогів розробників на Node.
+
+- [NodeUp](http://nodeup.com) подкаст в якому обговорюють найсвіжіші новини з Nod–спільноти.
+
+- [NodeJS Reactions](http://nodejsreactions.tumblr.com) відображає досвід роботи з Node.js через анімовані GIF.
+
+
+## Навчання
+
+- [Офіційна довідкова документація по API](/api) описує Node API.
+
+- [NodeSchool.io](http://nodeschool.io) навчить вас концепцій Node.js через інтерактивні консольні ігри.
+
+- [StackOverflow Node.js tag](http://stackoverflow.com/questions/tagged/node.js) щодня поповнюється новою інформацією.
+
+- [docs.nodejitsu.com](http://docs.nodejitsu.com/) відповіді на загальні питання, які виникають у людей.
+
+- [How To Node](http://howtonode.org/) має велику кількість корисних туторіалів.
+
+
+## Сайти міжнародних спільнот та проекти
+
+- [Australian Node.js blog &amp; developers listing](http://nodejs.org.au/)
+- [Brazilian community of Node.js](http://www.nodebr.com/)
+- [Chinese community](http://cnodejs.org)
+- [Cộng đồng Node.js Việt Nam](http://nodejs.vn)
+- [German Node.js community](http://nodecode.de)
+- [Google+ Community of Node.js French users](https://plus.google.com/communities/113346206415381691435)
+- [Hungarian (Magyar) community](http://nodehun.blogspot.com/)
+- [Iran group in Persian](http://nodejs.ir)
+- [Japan user group](http://nodejs.jp/)
+- [Node.js site for Kiwis](http://nodejs.geek.nz/)
+- [Russian website](http://node-center.ru/)
+- [Serbian Node.js community website](http://nodejs.rs/)
+- [Spanish language community](http://nodehispano.com)
+- [Taiwan community](http://nodejs.tw)
+- [Nicaragua Node.js community](http://nodenica.com/)
+- [Korean Node.js community](http://nodejs.github.io/nodejs-ko/)
diff --git a/locale/uk/index.md b/locale/uk/index.md
new file mode 100755
index 0000000000000..1e4c4e3d0334c
--- /dev/null
+++ b/locale/uk/index.md
@@ -0,0 +1,21 @@
+---
+layout: index.hbs
+labels:
+  current-version: Поточна версія
+  download: Завантажити
+  download-for: Завантажити для
+  other-downloads: Інші завантаження
+  other-lts-downloads: Інші LTS завантаження
+  other-current-downloads: Інші поточні завантаження
+  current: Поточна
+  lts: LTS
+  tagline-current: Найновіші можливості
+  tagline-lts: Рекомандовано для більшості
+  changelog: Список змін
+  api: Документація API
+  version-schedule-prompt: Або подивіться на
+  version-schedule-prompt-link-text: графік LTS
+---
+
+Node.js® — це JavaScript–оточення побудоване на JavaScript–рушієві [Chrome's V8](https://developers.google.com/v8/).
+Node.js використовує подієву, неблокуючу I/O модель, що робить його легким та ефективним. Пакетна екосистема Node.js, [npm](https://www.npmjs.com/), є найбільшою у світі екосистемою бібліотек з відкритим кодом.
diff --git a/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md b/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md
new file mode 100755
index 0000000000000..8b4b4a9b68610
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/clients/how-to-access-query-string-parameters.md
@@ -0,0 +1,26 @@
+---
+title: How to access query string parameters
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - http
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+In Node.js, functionality to aid in the accessing of URL query string parameters is built into the standard library. The built-in `url.parse` method takes care of most of the heavy lifting for us.  Here is an example script using this handy function and an explanation on how it works:
+
+    var fs = require('fs');
+    var http = require('http');
+    var url = require('url') ;
+
+    http.createServer(function (req, res) {
+      var queryObject = url.parse(req.url,true).query;
+      console.log(queryObject);
+
+      res.writeHead(200);
+      res.end('Feel free to add query parameters to the end of the url');
+    }).listen(8080);
+
+The key part of this whole script is this line: `var queryObject = url.parse(req.url,true).query;`. Let's take a look at things from the inside-out.  First off, `req.url` will look like `/app.js?foo=bad&baz=foo`. This is the part that is in the URL bar of the browser. Next, it gets passed to `url.parse` which parses out the various elements of the URL (NOTE: the second paramater is a boolean stating whether the method should parse the query string, so we set it to true). Finally, we access the `.query` property, which returns us a nice, friendly Javascript object with our query string data. 
+
+
diff --git a/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md b/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md
new file mode 100755
index 0000000000000..3f8539c1ee9e7
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md
@@ -0,0 +1,95 @@
+---
+title: How do I make a http request?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - http
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+
+Another extremely common programming task is making an HTTP request to a web server.  Node.js provides an extremely simple API for this functionality in the form of `http.request`.
+
+As an example, we are going to preform a GET request to [www.random.org/integers/?num=1&min=1&max=10&col=1&base=10&format=plain&rnd=new](www.random.org/integers/?num=1&min=1&max=10&col=1&base=10&format=plain&rnd=new) (which returns a random integer between 1 and 10) and print the result to the console.
+
+    var http = require('http');
+
+    //The url we want is: 'www.random.org/integers/?num=1&min=1&max=10&col=1&base=10&format=plain&rnd=new'
+    var options = {
+      host: 'www.random.org',
+      path: '/integers/?num=1&min=1&max=10&col=1&base=10&format=plain&rnd=new'
+    };
+
+    callback = function(response) {
+      var str = '';
+
+      //another chunk of data has been recieved, so append it to `str`
+      response.on('data', function (chunk) {
+        str += chunk;
+      });
+
+      //the whole response has been recieved, so we just print it out here
+      response.on('end', function () {
+        console.log(str);
+      });
+    }
+
+    http.request(options, callback).end();
+
+
+Making a POST request is just as easy. We will make a POST request to `www.nodejitsu.com:1337` which is running a server that will echo back what we post. The code for making a POST request is almost identical to making a GET request, just a few simple modifications:
+
+    var http = require('http');
+
+    //The url we want is `www.nodejitsu.com:1337/`
+    var options = {
+      host: 'www.nodejitsu.com',
+      path: '/',
+      //since we are listening on a custom port, we need to specify it by hand
+      port: '1337',
+      //This is what changes the request to a POST request
+      method: 'POST'
+    };
+
+    callback = function(response) {
+      var str = ''
+      response.on('data', function (chunk) {
+        str += chunk;
+      });
+
+      response.on('end', function () {
+        console.log(str);
+      });
+    }
+
+    var req = http.request(options, callback);
+    //This is the data we are posting, it needs to be a string or a buffer
+    req.write("hello world!");
+    req.end();
+
+Throwing in custom headers is just a tiny bit harder. On `www.nodejitsu.com:1338` we are running a server that will print out the `custom` header.  So we will just make a quick request to it:
+
+    var http = require('http');
+
+    var options = {
+      host: 'www.nodejitsu.com',
+      path: '/',
+      port: '1338',
+      //This is the only line that is new. `headers` is an object with the headers to request
+      headers: {'custom': 'Custom Header Demo works'}
+    };
+
+    callback = function(response) {
+      var str = ''
+      response.on('data', function (chunk) {
+        str += chunk;
+      });
+
+      response.on('end', function () {
+        console.log(str);
+      });
+    }
+
+    var req = http.request(options, callback);
+    req.end();
diff --git a/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md b/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md
new file mode 100755
index 0000000000000..b2e33c71a295b
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTP-server.md
@@ -0,0 +1,34 @@
+---
+title: How do I create a HTTP server?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - http
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+Making a simple HTTP server in Node.js has become the de facto 'hello world' for the platform.  On the one hand, Node.js provides extremely easy-to-use HTTP APIs; on the other hand, a simple web server also serves as an excellent demonstration of Node's asynchronous strengths.
+
+Let's take a look at a very simple example:
+
+    var http = require('http');
+    var requestListener = function (req, res) {
+      res.writeHead(200);
+      res.end('Hello, World!\n');
+    }
+
+    var server = http.createServer(requestListener);
+    server.listen(8080);
+
+Save this in a file called `server.js` - run `node server.js`, and your program will hang there... it's waiting for connections to respond to, so you'll have to give it one if you want to see it do anything.  Try opening up a browser, and typing `localhost:8080` into the location bar.  If everything has been set up correctly, you should see your server saying hello!
+
+Let's take a more in-depth look at what the above code is doing.  First, a function is defined called `requestListener` that takes a request object and a response object as parameters. 
+
+The request object contains things such as the requested URL, but in this example we ignore it and always return "Hello World". 
+
+The response object is how we send the headers and contents of the response back to the user making the request. Here we return a 200 response code (signaling a successful response) with the body "Hello World".  Other headers, such as `Content-type`, would also be set here.
+
+Next, the `http.createServer` method creates a server that calls `requestListener` whenever a request comes in. The next line, `server.listen(8080)`, calls the `listen` method, which causes the server to wait for incoming requests on the specified port - 8080, in this case. 
+
+There you have it - your most basic Node.js HTTP server.
diff --git a/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTPS-server.md b/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTPS-server.md
new file mode 100755
index 0000000000000..440e3095902b2
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/servers/how-to-create-a-HTTPS-server.md
@@ -0,0 +1,47 @@
+---
+title: How to create an https server?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - https
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+*If you're using [Nodejitsu](http://nodejitsu.com)*, we handle HTTPS for you. Free SSL on jit.su and nodejitsu.com subdomains, and SSL on custom domains for business customers.
+*It's never necessary to create an HTTPS server yourself.*
+
+- - -
+
+To create an HTTPS server, you need two things: an SSL certificate, and Node's built-in `https` module.
+
+We need to start out with a word about SSL certificates.  Speaking generally, there are two kinds of certificates: those signed by a 'Certificate Authority', or CA, and 'self-signed certificates'.  A Certificate Authority is a trusted source for an SSL certificate, and using a certificate from a CA allows your users to be trust the identity of your website. In most cases, you would want to use a CA-signed certificate in a production environment - for testing purposes, however, a self-signed certicate will do just fine.
+
+To generate a self-signed certificate, run the following in your shell:
+
+    openssl genrsa -out key.pem
+    openssl req -new -key key.pem -out csr.pem
+    openssl x509 -req -days 9999 -in csr.pem -signkey key.pem -out cert.pem
+    rm csr.pem
+
+This should leave you with two files, `cert.pem` (the certificate) and `key.pem` (the private key). This is all you need for a SSL connection. So now you set up a quick hello world example (the biggest difference between https and [http](/how-do-i-create-a-http-server) is the `options` parameter):
+
+    var https = require('https');
+    var fs = require('fs');
+
+    var options = {
+      key: fs.readFileSync('key.pem'),
+      cert: fs.readFileSync('cert.pem')
+    };
+
+    var a = https.createServer(options, function (req, res) {
+      res.writeHead(200);
+      res.end("hello world\n");
+    }).listen(8000);
+
+NODE PRO TIP: Note `fs.readFileSync` - unlike `fs.readFile`, `fs.readFileSync` will block the entire process until it completes.  In situations like this - loading vital configuration data - the `sync` functions are okay.  In a busy server, however, using a synchronous function during a request will force the server to deal with the requests one by one!
+
+Now that your server is set up and started, you should be able to get the file with curl:
+
+    curl -k https://localhost:8000
+
+or in your browser, by going to https://localhost:8000 . 
diff --git a/locale/uk/knowledge/HTTP/servers/how-to-handle-multipart-form-data.md b/locale/uk/knowledge/HTTP/servers/how-to-handle-multipart-form-data.md
new file mode 100755
index 0000000000000..9cf3d2e53f10a
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/servers/how-to-handle-multipart-form-data.md
@@ -0,0 +1,63 @@
+---
+title: How to handle multipart form data
+date: '2011-09-09T10:08:50.000Z'
+tags:
+  - http
+  - forms
+  - multipart
+  - uploads
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+Handling form data and file uploads properly is an important and complex problem in HTTP servers.  Doing it by hand would involve parsing streaming binary data, writing it to the file system, parsing out other form data, and several other complex concerns - luckily, only a very few people will need to worry about it on that deep level.  Felix Geisendorfer, one of the Node.js core committers, wrote a library called `node-formidable` that handles all the hard parts for you.  With its friendly API, you can be parsing forms and receiving file uploads in no time.
+
+This example is taken directly from the `node-formidable` GitHub page, with some additional explanation added.
+
+      var formidable = require('formidable'),
+          http = require('http'),
+          util = require('util');
+
+      http.createServer(function(req, res) {
+
+        // This if statement is here to catch form submissions, and initiate multipart form data parsing.
+        
+        if (req.url == '/upload' && req.method.toLowerCase() == 'post') {
+          
+          // Instantiate a new formidable form for processing.
+          
+          var form = new formidable.IncomingForm();
+          
+          // form.parse analyzes the incoming stream data, picking apart the different fields and files for you.
+          
+          form.parse(req, function(err, fields, files) {
+            if (err) {
+
+              // Check for and handle any errors here.
+
+              console.error(err.message);
+              return;
+            }
+            res.writeHead(200, {'content-type': 'text/plain'});
+            res.write('received upload:\n\n');
+            
+            // This last line responds to the form submission with a list of the parsed data and files.
+            
+            res.end(util.inspect({fields: fields, files: files}));
+          });
+          return;
+        }
+
+        // If this is a regular request, and not a form submission, then send the form.
+
+        res.writeHead(200, {'content-type': 'text/html'});
+        res.end(
+          '<form action="/upload" enctype="multipart/form-data" method="post">'+
+          '<input type="text" name="title"><br>'+
+          '<input type="file" name="upload" multiple="multiple"><br>'+
+          '<input type="submit" value="Upload">'+
+          '</form>'
+        );
+      }).listen(8080);
+
+Try it out for yourself - it's definitely the simpler solution, and `node-formidable` is a battle-hardened, production-ready library.  Let userland solve problems like this for you, so that you can get back to writing the rest of your code!
\ No newline at end of file
diff --git a/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md b/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md
new file mode 100755
index 0000000000000..46e1d0f956f77
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/servers/how-to-read-POST-data.md
@@ -0,0 +1,44 @@
+---
+title: How can I read POST data?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - http
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Reading the data from a POST request (i.e. a form submission) can be a little bit of a pitfall in Node.js, so we're going to go through an example of how to do it properly.  The first step, obviously, is to listen for incoming data - the trick is to wait for the data to finish, so that you can process all the form data without losing anything. 
+
+Here is a quick script that shows you how to do exactly that:
+
+    var http = require('http');
+    var postHTML = 
+      '<html><head><title>Post Example</title></head>' +
+      '<body>' +
+      '<form method="post">' +
+      'Input 1: <input name="input1"><br>' +
+      'Input 2: <input name="input2"><br>' +
+      '<input type="submit">' +
+      '</form>' +
+      '</body></html>';
+
+    http.createServer(function (req, res) {
+      var body = "";
+      req.on('data', function (chunk) {
+        body += chunk;
+      });
+      req.on('end', function () {
+        console.log('POSTed: ' + body);
+        res.writeHead(200);
+        res.end(postHTML);
+      });
+    }).listen(8080);
+
+The variable `postHTML` is a static string containing the HTML for two input boxes and a submit box - this HTML is provided so that you can `POST` example data. This is NOT the right way to serve static HTML - please see [How to Serve Static Files](link) for a more proper example.
+
+With the HTML out of the way, we [create a server](/how-do-i-create-a-http-server) to listen for requests. It is important to note, when listening for POST data, that the `req` object is also an [Event Emitter](/what-are-event-emitters).  `req`, therefore, will emit a `data` event whenever a 'chunk' of incoming data is received; when there is no more incoming data, the `end` event is emitted. So, in our case, we listen for `data` events. Once all the data is recieved, we log the data to the console and send the response. 
+
+Something important to note is that the event listeners are being added immediately after the request object is received. If you don't immediately set them, then there is a possibility of missing some of the events. If, for example, an event listener was attached from inside a callback, then the `data` and `end` events might be fired in the meantime with no listeners attached!
+
+You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occassionally you will see lines with no data, e.g. `POSTed: `. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently.
+
diff --git a/locale/uk/knowledge/HTTP/servers/how-to-serve-static-files.md b/locale/uk/knowledge/HTTP/servers/how-to-serve-static-files.md
new file mode 100755
index 0000000000000..840564e1ae751
--- /dev/null
+++ b/locale/uk/knowledge/HTTP/servers/how-to-serve-static-files.md
@@ -0,0 +1,42 @@
+---
+title: How to serve static files
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - http
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+A basic necessity for most [http servers](/how-do-i-create-a-https-server) is to be able to serve static files. Thankfully, it is not that hard to do in Node.js. First you [link]read the file, then you serve the file.  Here is an example of a script that will serve the files in the current directory:
+
+    var fs = require('fs'),
+        http = require('http');
+
+    http.createServer(function (req, res) {
+      fs.readFile(__dirname + req.url, function (err,data) {
+        if (err) {
+          res.writeHead(404);
+          res.end(JSON.stringify(err));
+          return;
+        }
+        res.writeHead(200);
+        res.end(data);
+      });
+    }).listen(8080);
+
+This example takes the path requested and it serves that path, relative to the local directory. This works fine as a quick solution; however, there are a few problems with this approach. First, this code does not correctly handle mime types. Additionally, a proper static file server should really be taking advantage of client side caching, and should send a "Not Modified" response if nothing has changed.  Furthermore, there are security bugs that can enable a malicious user to break out of the current directory. (for example, `GET /../../../`). 
+
+Each of these can be addressed invidually without much difficulty. You can send the proper mime type header. You can figure how to utilize the client caches. You can take advantage of `path.normalize` to make sure that requests don't break out of the current directory. But why write all that code when you can just use someone else's library? 
+
+There is a good static file server called [node-static](https://github.com/cloudhead/node-static) written by Alexis Sellier which you can leverage. Here is a script which functions similarly to the previous one:
+
+    var static = require('node-static');
+    var http = require('http');
+
+    var file = new(static.Server)();
+
+    http.createServer(function (req, res) {
+      file.serve(req, res);
+    }).listen(8080);
+
+This is a fully functional file server that doesn't have any of the bugs previously mentioned. This is just the most basic set up, there are more things you can do if you look at [the api](https://github.com/cloudhead/node-static). Also since it is an open source project, you can always modify it to your needs (and feel free to contribute back to the project!).
diff --git a/locale/uk/knowledge/REPL/how-to-create-a-custom-repl.md b/locale/uk/knowledge/REPL/how-to-create-a-custom-repl.md
new file mode 100755
index 0000000000000..1c14c9c50e3dd
--- /dev/null
+++ b/locale/uk/knowledge/REPL/how-to-create-a-custom-repl.md
@@ -0,0 +1,100 @@
+---
+title: How to create and use a custom REPL
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - repl
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+Node allows users to create their own REPLs with the [repl module](http://nodejs.org/docs/v0.4.10/api/repl.html). Its basic use looks like this:
+
+    repl.start(prompt, stream);
+
+`prompt` is a string that's used for the prompt of your REPL and defaults to "> ". `stream` is the stream that the repl listens on and defaults to `process.stdin`. When you run `node` from the command prompt, what it's doing in the background is running `repl.start()` to give you the standard REPL.
+
+However, the repl is pretty flexible. Here's an example that shows this off:
+
+    #!/usr/bin/env node
+
+    var net = require("net"),
+        repl = require("repl");
+
+    var mood = function () {
+        var m = [ "^__^", "-___-;", ">.<", "<_>" ];
+        return m[Math.floor(Math.random()*m.length)];
+    };
+
+    //A remote node repl that you can telnet to!
+    net.createServer(function (socket) {
+      var remote = repl.start("node::remote> ", socket);
+      //Adding "mood" and "bonus" to the remote REPL's context.
+      remote.context.mood = mood;
+      remote.context.bonus = "UNLOCKED";
+    }).listen(5001);
+
+    console.log("Remote REPL started on port 5001.");
+
+    //A "local" node repl with a custom prompt
+    var local = repl.start("node::local> ");
+
+    // Exposing the function "mood" to the local REPL's context.
+    local.context.mood = mood;
+
+This script creates *two* REPLs: One is normal excepting for its custom prompt, but the *other* is exposed via the net module so I can telnet to it! In addition, it uses the `context` property to expose the function "mood" to both REPLs, and the "bonus" string to the remote REPL only. As you will see, this approach of trying to expose objects to one REPL and not the other *doesn't really work*.
+
+In addition, all objects in the global scope will also be accessible to your REPLs.
+
+Here's what happens when I run the script:
+
+    $ node repl.js 
+    Remote REPL started on port 5001.
+    node::local> .exit
+    ^Cjosh@pidgey:/tmp/telnet$ node repl.js 
+    Remote REPL started on port 5001.
+    node::local> mood()
+    '^__^'
+    node::local> bonus
+    ReferenceError: bonus is not defined
+        at [object Context]:1:1
+        at Interface.<anonymous> (repl.js:171:22)
+        at Interface.emit (events.js:64:17)
+        at Interface._onLine (readline.js:153:10)
+        at Interface._line (readline.js:408:8)
+        at Interface._ttyWrite (readline.js:585:14)
+        at ReadStream.<anonymous> (readline.js:73:12)
+        at ReadStream.emit (events.js:81:20)
+        at ReadStream._emitKey (tty_posix.js:307:10)
+        at ReadStream.onData (tty_posix.js:70:12)
+
+As may be seen, the `mood` function is usable within the local REPL, but the
+`bonus` string is not. This is as expected.
+
+Now, here's what happens when I try to telnet to port 5001:
+
+    josh@pidgey:/tmp/telnet$ telnet localhost 5001
+    Trying ::1...
+    Trying 127.0.0.1...
+    Connected to localhost.
+    Escape character is '^]'.
+    node::remote> mood()
+    '>.<'
+    node::remote> bonus
+    'UNLOCKED'
+
+As you can see, the `mood` function is *also* available over telnet! In addition, so is "bonus".
+
+As an interesting consequence of my actions, bonus is now also defined on the local REPL:
+
+    node::local> bonus
+    'UNLOCKED'
+
+It seems we "unlocked" the `bonus` string on the local REPL as well. As it turns out, any variables created in one REPL are also available to the other:
+
+    node::local> var node = "AWESOME!"
+
+    node::remote> node
+    'AWESOME!'
+
+As you can see, the node REPL is powerful and flexible.
diff --git a/locale/uk/knowledge/REPL/how-to-use-nodejs-repl.md b/locale/uk/knowledge/REPL/how-to-use-nodejs-repl.md
new file mode 100755
index 0000000000000..041d8976c47f9
--- /dev/null
+++ b/locale/uk/knowledge/REPL/how-to-use-nodejs-repl.md
@@ -0,0 +1,60 @@
+---
+title: "How do I use node's REPL?"
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - cli
+  - repl
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+
+Node.js ships with a REPL, which is short for 'Read-Eval-Print Loop'.  It is the Node.js shell; any valid Javascript which can be written in a script can be passed to the REPL. It can be extremely useful for experimenting with node.js, debugging code, and figuring out some of Javascript's more eccentric behaviors.
+
+Running it is simple - just run node without a filename.
+
+     docs@nodejitsu:~/$ node
+
+It then drops you into a simple prompt ('>') where you can type any Javascript command you wish. As in most shells, you can press the up and down arrow keys to scroll through your command history and modify previous commands. The REPL also  `Tab` to make the REPL try to autocomplete the command.
+
+Whenever you type a command, it will print the return value of the command. If you want to reuse the previous return value, you can use the special `_` variable.
+
+For example:
+
+     node
+     > 1+1
+     2
+     > _+1
+     3
+
+One thing worth noting where REPL return values are concerned:
+
+     > x = 10
+     10
+     > var y = 5
+     > x
+     10
+     > y
+     5
+
+When the `var` keyword is used, the value of the expression is stored, but *NOT* returned.  When a bare identifier is used, the value is also returned, as well as stored.
+
+If you need to access any of the builtin modules, or any third party modules, they can be accessed with `require`, just like in the rest of Node.
+
+For example:
+
+     node
+     > path = require('path')
+     { resolve: [Function],
+       normalize: [Function],
+       join: [Function],
+       dirname: [Function],
+       basename: [Function],
+       extname: [Function],
+       exists: [Function],
+       existsSync: [Function] }
+     > path.basename("/a/b/c.txt")
+     'c.txt'
+
+Note once again that without the `var` keyword, the contents of the object are returned immediately and displayed to `stdout`.
diff --git a/locale/uk/knowledge/advanced/buffers/how-to-use-buffers.md b/locale/uk/knowledge/advanced/buffers/how-to-use-buffers.md
new file mode 100755
index 0000000000000..2660e5d56e0de
--- /dev/null
+++ b/locale/uk/knowledge/advanced/buffers/how-to-use-buffers.md
@@ -0,0 +1,161 @@
+---
+title: How to Use Buffers in Node.js
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - Buffer
+  - buffer
+  - buffers
+  - binary
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+## Why Buffers?
+
+Pure javascript, while great with unicode-encoded strings, does not handle straight binary data very well. This is fine on the browser, where most data is in the form of strings. However, node.js servers have to also deal with TCP streams and reading and writing to the filesystem, both which make it necessary to deal with purely binary streams of data.
+
+One way to handle this problem is to just use strings *anyway*, which is exactly what Node.js did at first. However, this approach is extremely problematic to work with; It's slow, makes you work with an API designed for strings and not binary data, and has a tendency to break in strange and mysterious ways.
+
+Don't use binary strings. Use *buffers* instead!
+
+## What Are Buffers?
+
+Buffers are instances of the `Buffer` class in node, which is designed to handle raw binary data. Each buffer corresponds to some raw memory allocated outside V8. Buffers act somewhat like arrays of integers, but aren't resizable and have a whole bunch of methods specifically for binary data. In addition, the "integers" in a buffer each represent a byte and so are limited to values from 0 to 255 (2^8 - 1), inclusive.
+
+## Where You See Buffers:
+
+In the wild, buffers are usually seen in the context of binary data coming from streams, such as `fs.createReadStream`.
+
+## Usage:
+
+### Creating Buffers:
+
+There are a few ways to create new buffers:
+
+    var buffer = new Buffer(8);
+
+This buffer is uninitialized and contains 8 bytes.
+
+    var buffer = new Buffer([ 8, 6, 7, 5, 3, 0, 9]);
+
+This initializes the buffer to the contents of this array. Keep in mind that the contents of the array are integers representing bytes.
+
+    var buffer = new Buffer("I'm a string!", "utf-8")
+
+This initializes the buffer to a binary encoding of the first string as specified by the second argument (in this case, utf-8). **utf-8** is by far the most common encoding used with node, but `Buffer` also supports:
+
+* **"ascii"**: This encoding is way fast, but is limited to the ascii character set. Moreover, it will convert null characters into spaces, unlike the utf-8 encoding.
+* **"ucs2"**: A two-byte, little-endian encoding. Can encode a subset of unicode.
+* **"base64"**: Base64 string encoding.
+* **"binary"**: This is the "binary string" format mentioned earlier, and is in the process of being deprecated. Avoid its use.
+
+### Writing to Buffers
+
+Given that there is already a buffer created:
+
+    > var buffer = new Buffer(16);
+
+we can start writing strings to it:
+
+    > buffer.write("Hello", "utf-8")
+    5
+
+The first argument to `buffer.write` is the string to write to the buffer, and the second argument is the string encoding. It happens to default to utf-8 so this argument is extraneous.
+
+`buffer.write` returned 5. This means that we wrote to five bytes of the buffer. The fact that the string "Hello" is also 5 characters long is coincidental, since each character *just happened* to be 8 bits apiece. This is useful if you want to complete the message:
+
+    > buffer.write(" world!", 5, "utf-8")
+    7
+
+When `buffer.write` has 3 arguments, the second argument indicates an offset, or the index of the buffer to start writing at.
+
+### Reading from Buffers:
+
+#### toString:
+
+Probably the most common way to read buffers is to use the `toString` method, since many buffers contain text:
+
+    > buffer.toString('utf-8')
+    'Hello world!\u0000�k\t'
+
+Again, the first argument is the encoding. In this case, it can be seen that not the entire buffer was used! Luckily, because we know how many bytes we've written to the buffer, we can simply add more arguments to "stringify" the slice that's actually interesting:
+
+    > buffer.toString("utf-8", 0, 12)
+    'Hello world!'
+
+#### Individual octets:
+
+You can also set individual bytes by using an array-like syntax:
+
+    > buffer[12] = buffer[11];
+    33
+    > buffer[13] = "1".charCodeAt();
+    49
+    > buffer[14] = buffer[13];
+    49
+    > buffer[15] = 33
+    33
+    > buffer.toString("utf-8")
+    'Hello world!!11!'
+
+In this example, I set the remaining bytes, by hand, such that they represent utf-8 encoded "!" and "1" characters.
+
+### More Fun With Buffers
+
+#### Buffer.isBuffer(object)
+
+This method checks to see if `object` is a buffer, similar to `Array.isArray`.
+
+#### Buffer.byteLength(string, encoding)
+
+With this function, you can check the number of bytes required to encode a string with a given encoding (which defaults to utf-8). This length is *not* the same as string length, since many characters require more bytes to encode. For example:
+
+    > var snowman = "☃";
+    > snowman.length
+    1
+    > Buffer.byteLength(snowman)
+    3
+
+The unicode snowman is only one character, but takes 3 entire bytes to encode!
+
+#### buffer.length
+
+This is the length of your buffer, and represents how much memory is allocated. It is not the same as the size of the buffer's contents, since a buffer may be half-filled. For example:
+
+    > var buffer = new Buffer(16)
+    > buffer.write(snowman)
+    3
+    > buffer.length
+    16
+
+In this example, the contents written to the buffer only consist of three groups (since they represent the single-character snowman), but the buffer's length is still 16, as it was initialized.
+
+#### buffer.copy(target, targetStart=0, sourceStart=0, sourceEnd=buffer.length)
+
+`buffer.copy` allows one to copy the contents of one buffer onto another. The first argument is the target buffer on which to copy the contents of `buffer`, and the rest of the arguments allow for copying only a subsection of the source buffer to somewhere in the middle of the target buffer. For example:
+
+    > var frosty = new Buffer(24)
+    > var snowman = new Buffer("☃", "utf-8")
+    > frosty.write("Happy birthday! ", "utf-8")
+    16
+    > snowman.copy(frosty, 16)
+    3
+    > frosty.toString("utf-8", 0, 19)
+    'Happy birthday! ☃'
+
+In this example, I copied the "snowman" buffer, which contains a 3 byte long character, to the "frosty" buffer, to which I had written to the first 16 bytes. Because the snowman character is 3 bytes long, the result takes up 19 bytes of the buffer.
+
+#### buffer.slice(start, end=buffer.length)
+
+This method's API is generally the same as that of `Array.prototype.slice`, but with one very import difference: The slice is **not** a new buffer and merely references a subset of the memory space. *Modifying the slice will also modify the original buffer*! For example:
+
+    > var puddle = frosty.slice(16, 19)
+    > puddle.toString()
+    '☃'
+    > puddle.write("___")
+    3
+    > frosty.toString("utf-8", 0, 19)
+    'Happy birthday! ___'
+
+Now Frosty has been turned into a puddle of underscores. Bummer.
diff --git a/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md b/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md
new file mode 100755
index 0000000000000..d0a4823c575b1
--- /dev/null
+++ b/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-read-stream.md
@@ -0,0 +1,35 @@
+---
+title: How to use fs.createReadStream?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - streams
+  - fs
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+The function `fs.createReadStream()` allows you to open up a readable stream in a very simple manner. All you have to do is pass the path of the file to start streaming in. It turns out that the response (as well as the request) objects are streams. So we will use this fact to create a http server that streams the files to the client. Since the code is simple enough, it is pretty easy just to read through it and comment why each line is necessary.
+
+    var http = require('http');
+    var fs = require('fs');
+
+    http.createServer(function(req, res) {
+      // The filename is simple the local directory and tacks on the requested url
+      var filename = __dirname+req.url;
+
+      // This line opens the file as a readable stream
+      var readStream = fs.createReadStream(filename);
+
+      // This will wait until we know the readable stream is actually valid before piping
+      readStream.on('open', function () {
+        // This just pipes the read stream to the response object (which goes to the client)
+        readStream.pipe(res);
+      });
+
+      // This catches any errors that happen while creating the readable stream (usually invalid names)
+      readStream.on('error', function(err) {
+        res.end(err);
+      });
+    }).listen(8080);
+
diff --git a/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-write-stream.md b/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-write-stream.md
new file mode 100755
index 0000000000000..8c678f854fc76
--- /dev/null
+++ b/locale/uk/knowledge/advanced/streams/how-to-use-fs-create-write-stream.md
@@ -0,0 +1,34 @@
+---
+title: How to use fs.createWriteStream?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - streams
+  - fs
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+The function `fs.createWriteStream()` creates a writable stream in a very simple manner. After a call to `fs.createWriteStream` with the filepath, you have a writeable stream to work with. It turns out that the response (as well as the request) objects are streams. So we will stream the `POST` data to the file `output`. Since the code is simple enough, it is pretty easy just to read through it and comment why each line is necessary.
+
+    var http = require('http');
+    var fs = require('fs');
+
+    http.createServer(function(req, res) {
+      // This opens up the writeable stream to `output`
+      var writeStream = fs.createWriteStream('./output');
+
+      // This pipes the POST data to the file
+      req.pipe(writeStream);
+
+      // After all the data is saved, respond with a simple html form so they can post more data
+      req.on('end', function () {
+        res.writeHead(200, {"content-type":"text/html"});
+        res.end('<form method="POST"><input name="test" /><input type="submit"></form>');
+      });
+
+      // This is here incase any errors occur
+      writeStream.on('error', function (err) {
+        console.log(err);
+      });
+    }).listen(8080);
diff --git a/locale/uk/knowledge/advanced/streams/how-to-use-stream-pipe.md b/locale/uk/knowledge/advanced/streams/how-to-use-stream-pipe.md
new file mode 100755
index 0000000000000..e93f1c32ba359
--- /dev/null
+++ b/locale/uk/knowledge/advanced/streams/how-to-use-stream-pipe.md
@@ -0,0 +1,88 @@
+---
+title: How to use stream.pipe
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - streams
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+If you've been using node.js for a while, you've definitely run into streams.  HTTP connections are streams,  open files are streams;  stdin, stdout, and stderr are all streams as well.  A 'stream' is node's I/O abstraction - if you feel like you still need to understand them better, you can read more about them [here](http://nodejs.org/api/stream.html#stream_stream).
+
+Streams make for quite a handy abstraction, and there's a lot you can do with them - as an example, let's take a look at stream.pipe, the method used to take a readable stream and connect it to a writeable steam.  Suppose we wanted to spawn a `node` child process and pipe our stdout and stdin to its corresponding stdout and stdin. 
+
+     #!/usr/bin/env node
+
+     var child = require('child_process');
+
+     var myREPL = child.spawn('node');
+
+     myREPL.stdout.pipe(process.stdout, { end: false });
+
+     process.stdin.resume();
+
+     process.stdin.pipe(myREPL.stdin, { end: false });
+
+     myREPL.stdin.on('end', function() {
+       process.stdout.write('REPL stream ended.');
+     });
+
+     myREPL.on('exit', function (code) {
+       process.exit(code);
+     });
+
+There you have it - spawn the node REPL as a child process, and pipe your stdin and stdout to its stdin and stdout.  Make sure to listen for the child's 'exit' event, too, or else your program will just hang there when the REPL exits.
+
+Another use for stream.pipe is file streams.  In node.js, fs.createReadStream and fs.createWriteStream are used to create a stream to an open file descriptor.  Now let's look at how one might use stream.pipe to write to a file.  You'll probably recognize most of the code:
+
+     #!/usr/bin/env node
+
+     var child = require('child_process'),
+         fs = require('fs');
+
+     var myREPL = child.spawn('node'),
+         myFile = fs.createWriteStream('myOutput.txt');
+
+     myREPL.stdout.pipe(process.stdout, { end: false });
+     myREPL.stdout.pipe(myFile);
+
+     process.stdin.resume();
+
+     process.stdin.pipe(myREPL.stdin, { end: false });
+     process.stdin.pipe(myFile);
+
+     myREPL.stdin.on("end", function() {
+       process.stdout.write("REPL stream ended.");
+     });
+
+     myREPL.on('exit', function (code) {
+       process.exit(code);
+     });
+
+With those small additions, your stdin and the stdout from your REPL will both be piped to the writeable file stream you opened to 'myOutput.txt'.  It's that simple - you can pipe streams to as many places as you want.
+
+Another very important use case for stream.pipe is with HTTP request and response objects.  Here we have the very simplest kind of proxy:
+
+     #!/usr/bin/env node
+
+     var http = require('http');
+
+     http.createServer(function(request, response) {
+       var proxy = http.createClient(9000, 'localhost')
+       var proxyRequest = proxy.request(request.method, request.url, request.headers);
+       proxyRequest.on('response', function (proxyResponse) {
+         proxyResponse.pipe(response);
+       });
+       request.pipe(proxyRequest);
+     }).listen(8080);
+
+     http.createServer(function (req, res) {
+       res.writeHead(200, { 'Content-Type': 'text/plain' });
+       res.write('request successfully proxied to port 9000!' + '\n' + JSON.stringify(req.headers, true, 2));
+       res.end();
+     }).listen(9000);
+
+One could also use stream.pipe to send incoming requests to a file for logging, or to a child process, or any one of a number of other things.
+
+Hopefully this has shown you the basics of using stream.pipe to easily pass your data streams around.  It's truly a powerful little trick in node.js, and its uses are yours to explore.  Happy coding, and try not to cross your streams!
diff --git a/locale/uk/knowledge/advanced/streams/what-are-streams.md b/locale/uk/knowledge/advanced/streams/what-are-streams.md
new file mode 100755
index 0000000000000..a2e709b931e74
--- /dev/null
+++ b/locale/uk/knowledge/advanced/streams/what-are-streams.md
@@ -0,0 +1,45 @@
+---
+title: What are streams?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - streams
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+
+
+Streams are another basic construct in node.js that encourages asynchronous coding. Streams allow you to process the data as it is generated or retrieved. Streams can be readable, writeable, or both. 
+
+In other words, Streams use events to deal with data as it happens, rather than only with a callback at the end.  Readable streams emit the event `data` for each chunk of data that comes in, and an `end` event, which is emitted when there is no more data. Writeable streams can be written to with the `write()` function, and closed with the `end()` function.  All types of streams emit `error` events when errors arise.
+
+As a quick example, we can write a simple version of `cp` (the unix utility that copies files). We could do that by reading the whole file with standard filesystem calls and then writing it out to a file. Unfortunately, that requires that the whole file be read in before it can be written. In the case of 1-2 giga files, you could run into out of memory operations. The biggest advantage that streams give you over their non-stream versions are that you can start process the info before you have all the information. In this case, writing out the file doesn't get sped up, but if we were streaming over the internet or doing cpu processing on it then there could be measurable performance improvements.
+
+Run this script with arguments like `node cp.js src.txt dest.txt`. This would mean, in the code below, that `process.argv[2]` is `src.txt` and `process.argv[3]` is `desc.txt`. 
+
+    var fs = require('fs');
+    console.log(process.argv[2], '->', process.argv[3]);
+
+    var readStream = fs.createReadStream(process.argv[2]);
+    var writeStream = fs.createWriteStream(process.argv[3]);
+
+    readStream.on('data', function (chunk) {
+      writeStream.write(chunk);
+    });
+
+    readStream.on('end', function () {
+      writeStream.end();
+    });
+
+    //Some basic error handling
+    readStream.on('error', function (err) {
+      console.log("ERROR", err);
+    });
+
+    writeStream.on('error', function (err) {
+      console.log("ERROR", err);
+    });
+
+
+This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/how-to-use-stream-pipe) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way.
\ No newline at end of file
diff --git a/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md b/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md
new file mode 100755
index 0000000000000..9f89edb57c25a
--- /dev/null
+++ b/locale/uk/knowledge/child-processes/how-to-spawn-a-child-process.md
@@ -0,0 +1,39 @@
+---
+title: How to spawn a child process - the basics
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - child_process
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+
+If you find yourself wishing you could have your Node.js process start another program for you, then look no further than the `child_process` module.
+
+The simplest way is the "fire, forget, and buffer" method using `child_process.exec`.  It runs your process, buffers its output (up to a default maximum of 200kb), and lets you access it from a callback when it is finished. Let us take a look at an example:
+
+     var childProcess = require('child_process'),
+         ls;
+
+     ls = childProcess.exec('ls -l', function (error, stdout, stderr) {
+       if (error) {
+         console.log(error.stack);
+         console.log('Error code: '+error.code);
+         console.log('Signal received: '+error.signal);
+       }
+       console.log('Child Process STDOUT: '+stdout);
+       console.log('Child Process STDERR: '+stderr);
+     });
+
+     ls.on('exit', function (code) {
+       console.log('Child process exited with exit code '+code);
+     });
+
+NODE PRO TIP: `error.stack` is a stack trace to the point that the [Error object](/what-is-the-error-object) was created.
+
+It should be noted that the `STDERR` of a given process is not exclusively reserved for error messages. Many programs use it as a channel for secondary data instead.  As such, when trying to work with a program that you have not previously spawned as a child process, it can be helpful to start out dumping both `STDOUT` and `STDERR`, as shown above, to avoid any surprises.
+
+While `child_process.exec` buffers the output of the child process for you, it also returns a `ChildProcess` object, Node's way of wrapping a still-running process.  In the example above, since we are using `ls`, a program that will exit immediately regardless, the only part of the `ChildProcess` object worth worrying about is the `on exit` handler.  It is not necessary here - the process will still exit and the error code will still be shown on errors.
+
+
diff --git a/locale/uk/knowledge/command-line/how-to-get-colors-on-the-command-line.md b/locale/uk/knowledge/command-line/how-to-get-colors-on-the-command-line.md
new file mode 100755
index 0000000000000..fbf7f83af8e70
--- /dev/null
+++ b/locale/uk/knowledge/command-line/how-to-get-colors-on-the-command-line.md
@@ -0,0 +1,66 @@
+---
+title: How to get colors on the command line
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - cli
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+When working on the command line, it can be both fun and extremely useful to colorize one's output. To colorize console output, you need to use ANSI escape codes. The module `colors.js`, available on `npm`, provides an extremely easy to use wrapper that makes adding colors a breeze.
+
+First, install it to the directory you'd like to work in.
+
+     cd mydir
+     npm install colors
+
+Now open up a little test script for yourself, and try something like this:
+
+     var colors = require('colors'),
+         stringOne = 'This is a plain string.',
+         stringTwo = 'This string is red.'.red,
+         stringThree = 'This string is blue.'.blue;
+     
+     console.log(stringOne.green);
+     console.log(stringOne.yellow);
+
+     console.log(stringTwo);
+     console.log(stringThree);
+
+     console.log(stringTwo.magenta);
+     console.log(stringThree.grey.bold);
+
+There are several things to take note of here - first, the string object has been prototyped, so any color may be added simply by adding the property to the string!  It works both on string literals and on variables, as shown at the top of the example above.
+
+Notice, also, from the second pair of `console.log` statements, that once set, a color value persists as part of the string.  This is because under the hood, the proper ANSI color tags have been prepended and appended as necessary - anywhere the string gets passed where ANSI color codes are also supported, the color will remain.
+
+The last pair of `console.log` statements are probably the most important.  Because of the way `colors.js` and ANSI color codes work, if more than one color property is set on a string, **only the first color property to be set on the string takes effect.**  This is because the colors function as 'state shifts' rather than as tags.
+
+Let's look at a more explicit example.  If you set the following properties with `colors.js`:
+
+     myString.red.blue.green
+
+You can think of your terminal saying to itself, "Make this green. No, make this blue.  No, make this red.  No more color codes now?  Red it is, then."  The codes are read in the reverse order, and the last/'innermost' is applied.  This can be extremely useful if you're using a library that sets its own default colors that you don't like - if you set a color code yourself on the string you pass in to the library, it will supersede the other author's color code(s).
+
+The last thing to note is the final line of the example script.  While a color code was set previously, a 'bold' code was not, so the example was made bold, but not given a different color.
+
+One last thing: the colors can look quite different in different terminals - sometimes, `bold` is bold, sometimes it's just a different color. Try it out and see for yourself!
+
+For reference, here's the full list of available `colors.js` properties.
+
+- bold
+- italic
+- underline
+- inverse
+- yellow
+- cyan
+- white
+- magenta
+- green
+- red
+- grey
+- blue
+- rainbow
+
+Some people may tell you that `colors.js` is haunted, but those people are just trolls... right?
diff --git a/locale/uk/knowledge/command-line/how-to-parse-command-line-arguments.md b/locale/uk/knowledge/command-line/how-to-parse-command-line-arguments.md
new file mode 100755
index 0000000000000..63547f643f95f
--- /dev/null
+++ b/locale/uk/knowledge/command-line/how-to-parse-command-line-arguments.md
@@ -0,0 +1,93 @@
+---
+title: How to parse command line arguments
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - cli
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+Passing in arguments via the command line is an extremely basic programming task, and a necessity for anyone trying to write a simple Command-Line Interface (CLI).  In Node.js, as in C and many related environments, all command-line arguments received by the shell are given to the process in an array called `argv` (short for 'argument values').  
+
+Node.js exposes this array for every running process in the form of `process.argv` - let's take a look at an example.  Make a file called `argv.js` and add this line:
+
+     console.log(process.argv);
+
+Now save it, and try the following in your shell:
+
+     $ node argv.js one two three four five
+     [ 'node',
+       '/home/avian/argvdemo/argv.js',
+       'one',
+       'two',
+       'three',
+       'four',
+       'five' ]
+
+There you have it - an array containing any arguments you passed in.  Notice the first two elements - `node` and the path to your script.  These will always be present - even if your program takes no arguments of its own, your script's interpreter and path are still considered arguments to the shell you're using.  
+
+Where everyday CLI arguments are concerned, you'll want to skip the first two.  Now try this in `argv.js`:
+
+     var myArgs = process.argv.slice(2);
+     console.log('myArgs: ', myArgs);
+
+This yields:
+
+     $ node argv.js one two three four
+     myArgs:  [ 'one', 'two', 'three', 'four' ]
+
+Now let's actually do something with the args:
+
+     var myArgs = process.argv.slice(2);
+     console.log('myArgs: ', myArgs);
+
+     switch (myArgs[0]) {
+       case 'insult':
+         console.log(myArgs[1], 'smells quite badly.');
+         break;
+       case 'compliment':
+         console.log(myArgs[1], 'is really cool.');
+         break;
+       default:
+         console.log('Sorry, that is not something I know how to do.');
+     }
+
+JS PRO TIP: Remember to `break` after each `case` - otherwise you'll run the next case too!
+
+Referring to your command-line arguments by array index isn't very clean, and can quickly turn into a nightmare when you start working with flags and the like - imagine you made a server, and it needed a lot of arguments.  Imagine having to deal with something like `myapp -h host -p port -r -v -b --quiet -x -o outfile` - some flags need to know about what comes next, some don't, and most CLIs let users specify arguments in any order they want.  Sound like a fun string to parse?
+
+Luckily, there's a third party module that makes all of this trivial - it's called [Optimist](https://github.com/substack/node-optimist), written by one Mr. James Halliday (aka SubStack).  It's available via `npm`.  Use this command from your app's base path:
+
+     npm install optimist
+     
+Once you have it, give it a try - it can really be a life-saver.  
+
+     var myArgs = require('optimist').argv,
+         help = 'This would be a great place for real help information.';
+     
+     if ((myArgs.h)||(myArgs.help)) {
+       console.log(help);
+       process.exit(0);
+     }
+     
+     switch (myArgs._[0]) {
+       case 'insult':
+         console.log(myArgs.n || myArgs.name, 'smells quite badly.');
+         break;
+       case 'compliment':
+         console.log(myArgs.n || myArgs.name, 'is really cool.');
+         break;
+       default:
+         console.log(help);
+     }
+     
+     console.log('myArgs: ', myArgs);
+     
+The last line was included to let you see how Optimist handles your arguments.  Here's a quick reference:
+
+- `argv.$0` contains the first two elements of `process.argv` joined together - "node ./myapp.js".
+- `argv._` is an array containing each element not attached to a flag.
+- Individual flags become properties of `argv`, such as with `myArgs.h` and `myArgs.help`.  Note that non-single-letter flags must be passed in as `--flag`.  
+
+For more information on Optimist and the many, many other things it can do for your command-line arguments, please visit [https://github.com/substack/node-optimist](https://github.com/substack/node-optimist)
diff --git a/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md b/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md
new file mode 100755
index 0000000000000..c170d9af62ca1
--- /dev/null
+++ b/locale/uk/knowledge/command-line/how-to-prompt-for-command-line-input.md
@@ -0,0 +1,91 @@
+---
+title: How do I prompt users for input from a command-line script?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - javascript
+  - core
+  - cli
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+So you've got a little CLI tool, but you want to be able to prompt a user for additional data after the script has started, rather than passing it in as a command line argument or putting it in a file.  To do this, you'll need to listen to STDIN ("standard input", i.e. your keyboard), which Node.js exposes for you as `process.stdin`, a readable stream.
+
+Streams are Node's way of dealing with evented I/O - they're a big topic, and you can read more about them (here).  For now, we're only going to deal with the Stream methods relevant to working with `process.stdin` so as to keep the examples easy.
+
+The first two Readable Stream methods you'll need to know about here are `pause()` and `resume()`.  Not every program needs to care whether or not you're pressing keys at a given moment, so `process.stdin` is paused by default. 
+
+Here's a simple example.  Try the following in a new file:
+
+      process.stdin.resume();
+      process.stdin.setEncoding('utf8');
+      var util = require('util');
+      
+      process.stdin.on('data', function (text) {
+        console.log('received data:', util.inspect(text));
+        if (text === 'quit\n') {
+          done();
+        }
+      });
+      
+      function done() {
+        console.log('Now that process.stdin is paused, there is nothing more to do.');
+        process.exit();
+      }
+      
+
+If all of this sounds complicated, or if you want a higher-level interface to this sort of thing, don't worry - as usual, the Node.js community has come to the rescue.  One particularly friendly module to use for this is Prompt, maintained by Nodejitsu.  It's available on `npm`:
+
+     npm install prompt
+
+Prompt is built to be easy - if your eyes started to glaze over as soon as you saw `Readable Stream`, then this is the section for you.  Compare the following to the example above:
+
+      var prompt = require('prompt');
+      
+      prompt.start();
+      
+      prompt.get(['username', 'email'], function (err, result) {
+        if (err) { return onErr(err); }
+        console.log('Command-line input received:');
+        console.log('  Username: ' + result.username);
+        console.log('  Email: ' + result.email);
+      });
+      
+      function onErr(err) {
+        console.log(err);
+        return 1;
+      }
+
+NODE PRO TIP: This short script also demonstrates proper error handling in node - errors are a callback's first argument, and `return` is used with the error handler so that the rest of the function doesn't execute when errors happen.  For more information, look (here).
+
+Prompt also makes it trivial to handle a certain set of recurring properties that one might want to attach. 
+
+      var prompt = require('prompt');
+
+      var properties = [
+        {
+          name: 'username', 
+          validator: /^[a-zA-Z\s\-]+$/,
+          warning: 'Username must be only letters, spaces, or dashes'
+        },
+        {
+          name: 'password',
+          hidden: true
+        }
+      ];
+
+      prompt.start();
+
+      prompt.get(properties, function (err, result) {
+        if (err) { return onErr(err); }
+        console.log('Command-line input received:');
+        console.log('  Username: ' + result.username);
+        console.log('  Password: ' + result.password);
+      });
+
+      function onErr(err) {
+        console.log(err);
+        return 1;
+      }
+      
+For more information on Prompt, please see [the project's GitHub page](http://github.com/nodejitsu/node-prompt).
diff --git a/locale/uk/knowledge/cryptography/how-to-use-crypto-module.md b/locale/uk/knowledge/cryptography/how-to-use-crypto-module.md
new file mode 100755
index 0000000000000..efe5c00b49589
--- /dev/null
+++ b/locale/uk/knowledge/cryptography/how-to-use-crypto-module.md
@@ -0,0 +1,126 @@
+---
+title: How to use the crypto module
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - crypto
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+The [crypto](http://nodejs.org/docs/v0.4.10/api/crypto.html) module is a wrapper for [OpenSSL](http://en.wikipedia.org/wiki/Openssl) cryptographic functions. It supports calculating hashes, authentication with HMAC, ciphers, and more!
+
+The crypto module is mostly useful as a tool for implementing [cryptographic protocols](http://en.wikipedia.org/wiki/Cryptographic_protocol) such as [TLS](http://en.wikipedia.org/wiki/Transport_Layer_Security) and [https](http://en.wikipedia.org/wiki/Https). For most users, Node's built-in [tls module](http://nodejs.org/docs/v0.4.10/api/tls.html) and [https module](http://nodejs.org/docs/v0.4.10/api/https.html) should more than suffice. However, for the user that only wants to use small parts of what's needed for full-scale cryptography or is crazy/desperate enough to implement a protocol using OpenSSL and Node: Read on.
+
+## Hashes
+
+### What Is A Hash?
+
+A hash is a fixed-length string of bits that is procedurally and deterministially generated from some arbitrary block of source data. Some important properties of these hashes (the type useful for cryptography) include:
+
+* **Fixed length:** This means that, no matter what the input, the length of the hash is the same. For example, md5 hashes are always 128 bits long whether the input data is a few bits or a few gigabytes.
+
+* **Deterministic:** For the same input, you should expect to be able to calculate exactly the same hash. This makes hashes useful for checksums.
+
+* **Collision-Resistant:** A collision is when the same hash is generated for two different input blocks of data. Hash algorithms are designed to be extremely unlikely to have collisions -- just how unlikely is a property of the hash algorithm. The importance of this property depends on the use case.
+
+* **Unidirectional:** A good hash algorithm is easy to apply, but hard to undo. This means that, given a hash, there isn't any reasonable way to find out what the original piece of data was.
+
+### Hash Algorithms That Work With Crypto
+
+The hashes that work with crypto are dependent on what your version of OpenSSL supports. If you have a new enough version of OpenSSL, you can get a list of hash types your OpenSSL supports by typing `openssl list-message-digest-algorithms` into the command line. For older versions, simply type `openssl list-message-digest-commands` instead! Some of the most common hash types are: 
+
+* [sha1](http://en.wikipedia.org/wiki/Sha1)
+* [md5](http://en.wikipedia.org/wiki/Md5).
+
+### How To Calculate Hashes with Crypto
+
+Crypto has a method called `createHash` which allows you to calculate a hash. Its only argument is a string representing the hash This example finds the md5 hash for the string, "Man oh man do I love node!":
+
+    require("crypto")
+      .createHash("md5")
+      .update("Man oh man do I love node!")
+      .digest("hex");
+
+The `update` method is used to push data to later be turned into a hash with the `digest` method. `update` can be invoked multiple times to ingest streaming data, such as buffers from a file read stream. The argument for `digest` represents the output format, and may either be "binary", "hex" or "base64". It defaults to binary.
+
+## HMAC
+
+HMAC stands for Hash-based Message Authentication Code, and is a process for applying a hash algorithm to both data and a secret key that results in a single final hash. Its use is similar to that of a vanilla hash, but also allows to check the *authenticity* of data as *well* as the integrity of said data (as you can using md5 checksums).
+
+The API for hmacs is very similar to that of `createHash`, except that the method is called `createHmac` and it takes a key as a second argument:
+
+    require("crypto").createHmac("md5", "password")
+      .update("If you love node so much why don't you marry it?")
+      .digest("hex");
+
+The resulting md5 hash is unique to both the input data and the key.
+
+## Ciphers
+
+Ciphers allow you to encode and decode messages given a password.
+
+### Cipher Algorithms That Work With Crypto
+
+Like crypto's hash algorithms, the cyphers that work with crypto are dependent on what your version of OpenSSL supports. You can get a list of hash types your OpenSSL supports by typing `openssl list-cipher-commands` into the command line for older versions, or `openssl list-cipher-algorithms` for newer versions of OpenSSL. OpenSSL supports *many* ciphers; A good and popular one is [AES192](http://en.wikipedia.org/wiki/Aes192).
+
+### How To Use Cipher Algorithms with Crypto:
+
+Crypto comes with two methods for ciphering and deciphering:
+
+* `crypto.createCypher(algorithm, key)`
+* `crypto.createDecipher(algorithm, key)`
+
+Both of these methods take arguments similarly to `createHmac`. They also both have analogous `update` functions. However, each use of `update` returns a chunk of the encoded/decoded data instead of requiring one to call `digest` to get the result. Moreover, after encoding (or decoding) your data, you will likely have to call the `final` method to get the last chunk of encoded information.
+
+Here's an example, slightly less trivial than previous examples, that uses crypto and [optimist](https://github.com/substack/node-optimist) to encode and decode messages from the command line:
+
+    #!/usr/bin/env node
+
+    var crypto = require("crypto"),
+        argv = require("optimist").argv;
+
+    if (argv.e && argv.password) {
+        var cipher = crypto.createCipher("aes192", argv.password),
+            msg = [];
+
+        argv._.forEach( function (phrase) {
+            msg.push(cipher.update(phrase, "binary", "hex"));
+        });
+
+        msg.push(cipher.final("hex"));
+        console.log(msg.join(""));
+
+    } else if (argv.d && argv.password) {
+        var decipher = crypto.createDecipher("aes192", argv.password),
+            msg = [];
+
+        argv._.forEach( function (phrase) {
+            msg.push(decipher.update(phrase, "hex", "binary"));
+        });
+
+        msg.push(decipher.final("binary"));
+        console.log(msg.join(""));   
+    }
+
+Using this script to encode a message looks like this:
+
+    $ ./secretmsg.js -e --password="popcorn" "My treasure is buried behind Carl's Jr. on Telegraph."
+    6df66752b24f0886f8a6c55e56977788c2090bb657ff3bd645097f8abe11099963fb3bd9627986c60fa7e5120d8fead928cff620b37e3e79be8de519f490527a
+
+Now, if I gave somebody the same script, my encoded message and the password, they can decode the message and find out where I buried my treasure:
+
+    $ ./secretmsg.js -d --password="popcorn" 6df66752b24f0886f8a6c55e56977788c2090bb657ff3bd645097f8abe11099963fb3bd9627986c60fa7e5120d8fead928cff620b37e3e79be8de519f490527a
+    My treasure is buried behind Carl's Jr. on Telegraph.
+
+You should know that what I buried behind Carl's Jr was just a cigarette butt, and that this script is obviously not for serious use.
+
+## Signing and Verification
+
+Crypto has other methods used for dealing with certificates and credentials, as used for TLS:
+
+* `crypto.createCredentials`
+* `crypto.createSign`
+* `crypto.createVerify`
+
+These methods supply the last building blocks for a complete cryptographic protocol, and require an advanced knowledge of real-world cryptographic protocols to be useful. Again, it is recommended that developers use either the [tls](http://nodejs.org/docs/v0.4.10/api/tls.html) module or the [https](http://nodejs.org/docs/v0.4.10/api/https.html) module if applicable.
diff --git a/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md
new file mode 100755
index 0000000000000..b3935ffb3dc07
--- /dev/null
+++ b/locale/uk/knowledge/cryptography/how-to-use-the-tls-module.md
@@ -0,0 +1,160 @@
+---
+title: How To Use The TLS Module
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - tls
+  - ssl
+  - secure
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+## What is TLS?
+
+[Transport Layer Security](http://en.wikipedia.org/wiki/Transport_Layer_Security) (or TSL) is the successor to Secure Sockets Layer (or SSL). It, along with SSL, are the de-facto standard cryptographic protocols for secure communications over the web. TSL encrypts communications on top of a network transport layer (typically tcp), and uses public-key cryptography to encrypt messages.
+
+### Public-Key Cryptography
+
+In public-key cryptography, each peer has two keys: A public key, and a private key. The public key is shared with everyone, and the private key is (naturally) kept secret. In order to encrypt a message, a computer requires its private key and the recipient's public key. Then, in order to decrypt the message, the recipient requires its *own* private key and the *sender*'s public key.
+
+In TLS connections, the public key is called a *[certificate](http://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](http://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](http://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public.
+
+### History of TLS/SSL Support in Node.JS
+
+TLS support in node is relatively new. The first stable version of node.js to support TSL and HTTPS was the v0.4 branch, which was released in early 2011. Since then, the primary focus of the core developers has shifted from TLS/HTTPS to Windows support in the v0.5 branch. As such, the TSL APIs in node are still a little rough around the edges, and documentation leaves something to be desired.
+
+## The tls Module
+
+### tls.createServer
+
+In most ways, the tls module's server api is similar to that of the net module. Besides the fact that it's for encrypted connections, the major difference is that the options object passed to `tls.connect` or `tls.createServer` needs to include information on both the private key and the certificate, in [pem format](http://en.wikipedia.org/wiki/X.509#Certificate_filename_extensions). Here's an example of a tls server:
+
+    var tls = require('tls'),
+        fs = require('fs'),
+        colors = require('colors'),
+        msg = [
+                ".-..-..-.  .-.   .-. .--. .---. .-.   .---. .-.",
+                ": :; :: :  : :.-.: :: ,. :: .; :: :   : .  :: :",
+                ":    :: :  : :: :: :: :: ::   .': :   : :: :: :",
+                ": :: :: :  : `' `' ;: :; :: :.`.: :__ : :; ::_;",
+                ":_;:_;:_;   `.,`.,' `.__.':_;:_;:___.':___.':_;" 
+              ].join("\n").cyan;
+
+    var options = {
+      key: fs.readFileSync('private-key.pem'),
+      cert: fs.readFileSync('public-cert.pem')
+    };
+
+    tls.createServer(options, function (s) {
+      s.write(msg+"\n");
+      s.pipe(s);
+    }).listen(8000);
+
+
+In this example, a "hello world" tls server is created, listening on port 8000. The options object includes two properties: `key` and `cert`. The contents of these properties come directly from the private key and public certificate stored on the filesystem. In this case they are binary buffers, but the tls module can also accept unicode strings.
+
+### Generating Your Private Key And Certificate With OpenSSL:
+
+In order for this example server to work, of course, you will need a private key and a certificate. You can generate both of these with OpenSSL.
+
+First, generate a private key:
+
+    $ openssl genrsa -out private-key.pem 1024
+    Generating RSA private key, 1024 bit long modulus
+    ......................................++++++
+    ........++++++
+    e is 65537 (0x10001)
+
+This creates a suitable private key and writes it to `./private-key.pem`.
+
+Next, create a Certificate Signing Request file using your private key:
+
+    $ openssl req -new -key private-key.pem -out csr.pem
+    You are about to be asked to enter information that will be incorporated
+    into your certificate request.
+    What you are about to enter is what is called a Distinguished Name or a DN.
+    There are quite a few fields but you can leave some blank
+    For some fields there will be a default value,
+    If you enter '.', the field will be left blank.
+    -----
+    Country Name (2 letter code) [AU]:US
+    State or Province Name (full name) [Some-State]:California
+    Locality Name (eg, city) []:Oakland
+    Organization Name (eg, company) [Internet Widgits Pty Ltd]:Panco, Inc.
+    Organizational Unit Name (eg, section) []:
+    Common Name (eg, YOUR name) []:Joshua Holbrook
+    Email Address []:josh.holbrook@gmail.com
+
+    Please enter the following 'extra' attributes
+    to be sent with your certificate request
+    A challenge password []:dangerface
+    An optional company name []:
+
+The purpose of this CSR is to "request" a certificate. That is, if you wanted a CA to sign your certificate, you could give this file to them to process and they would give you back a certificate.
+
+Alternately, however, you may self-sign your certificate, again using your private key:
+
+    $ openssl x509 -req -in csr.pem -signkey private-key.pem -out public-cert.pem
+    Signature ok
+    subject=/C=US/ST=California/L=Oakland/O=Panco, Inc./CN=Joshua Holbrook/emailAddress=josh.holbrook@gmail.com
+    Getting Private key
+
+This generates your certificate. Now you're cooking!
+
+### Trying it out:
+
+One way to test out your new "hello world" server is to again use OpenSSL:
+
+    $ openssl s_client -connect 127.0.0.1:8000
+
+You should see a bunch of output regarding the handshaking process, and then at the very end you should see a big, cyan figlet banner saying, "Hi world!"
+
+### tls.connect
+
+The tls module also supplies tools for connecting to such a server:
+
+    var tls = require('tls'),
+        fs = require('fs');
+
+    var options = {
+      key: fs.readFileSync('private-key.pem'),
+      cert: fs.readFileSync('public-cert.pem')
+    };
+
+    var conn = tls.connect(8000, options, function() {
+      if (conn.authorized) {
+        console.log("Connection authorized by a Certificate Authority.");
+      } else {
+        console.log("Connection not authorized: " + conn.authorizationError)
+      }
+        console.log();
+    });
+
+
+
+    conn.on("data", function (data) {
+      console.log(data.toString());
+      conn.end();
+    });
+
+The idea is similar, except instead of creating a server, this script connects to one instead. `tls.connect` also takes an options object, but then returns a stream.
+
+`tls.connect` also fires a callback when the connection is made, which allows for checking to see if the connection is authorized---that is, if all the certificates are in order. `conn.authorized` is a boolean, and `conn.authorizationError` is a string containing the reason that the connection is unauthorized.
+
+This is what happens when the client is ran (with the server running):
+
+    $ node client.js
+    Connection not authorized: DEPTH_ZERO_SELF_SIGNED_CERT
+
+    .-..-..-.  .-.   .-. .--. .---. .-.   .---. .-.
+    : :; :: :  : :.-.: :: ,. :: .; :: :   : .  :: :
+    :    :: :  : :: :: :: :: ::   .': :   : :: :: :
+    : :: :: :  : `' `' ;: :; :: :.`.: :__ : :; ::_;
+    :_;:_;:_;   `.,`.,' `.__.':_;:_;:___.':___.':_;
+
+Note that self-signing the server certificate results in a non-authorized status because you're not listed as a trusted certificate authority.
+
+## "starttls"
+
+It's entirely possible to "upgrade" an existing tcp connection into a TLS-encrypted one with node. However, node does not have a special functions for doing so as of the v0.4 branch. Therefore, it needs to be done "by-hand", using the crypto module and some undocumented tls module functionality. Node's documentation points to <https://gist.github.com/848444>, which aims to abstract the process.
diff --git a/locale/uk/knowledge/errors/what-are-the-error-conventions.md b/locale/uk/knowledge/errors/what-are-the-error-conventions.md
new file mode 100755
index 0000000000000..6dd2d64f19d84
--- /dev/null
+++ b/locale/uk/knowledge/errors/what-are-the-error-conventions.md
@@ -0,0 +1,49 @@
+---
+title: What are the error conventions?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - errors
+  - conventions
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+In node.js, it is considered standard practice to handle errors in asynchronous functions by returning them as the first argument to the current function's callback.  If there is an error, the first parameter is passed an `Error` object with all the details. Otherwise, the first parameter is null. 
+
+It's simpler than it sounds; let's demonstrate.
+
+    var isTrue = function(value, callback) {
+      if (value === true) {
+        callback(null, "Value was true.");
+      }
+      else {
+        callback(new Error("Value is not true!"));
+      }
+    }
+
+    var callback = function (error, retval) {
+      if (error) {
+        console.log(error);
+        return;
+      }
+      console.log(retval);
+    }
+
+    // Note: when calling the same asynchronous function twice like this, you are in a race condition.
+    // You have no way of knowing for certain which callback will be called first when calling the functions in this manner.
+
+    isTrue(false, callback);
+    isTrue(true,  callback);
+
+    { stack: [Getter/Setter],
+      arguments: undefined,
+      type: undefined,
+      message: 'Value is not true!' }
+    Value was true.
+
+As you can see from the example, the callback is called with null as its first argument if there is no error. However, if there is an error, you create an `Error` object, which then becomes the callback's only parameter. 
+
+The `callback` function shows the reason for this: it allows a user to easily know whether or not an error occurred.  If `null` was not the first argument passed on success, the user would need to check the object being returned and determine themselves whether or not the object constituted an error - a much more complex and less user-friendly approach.
+
+So to wrap it all up, when using callbacks, if an error comes up, then pass it as the first argument.  Otherwise, pass `null` first, and then your return arguments.  On the receiving end, inside the callback function, check if the first parameter is non-null;  if it is, handle it as an error.
diff --git a/locale/uk/knowledge/errors/what-is-the-error-object.md b/locale/uk/knowledge/errors/what-is-the-error-object.md
new file mode 100755
index 0000000000000..574bf38264ff8
--- /dev/null
+++ b/locale/uk/knowledge/errors/what-is-the-error-object.md
@@ -0,0 +1,42 @@
+---
+title: What is the error object?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - errors
+  - builtin
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+The error object is a built-in object that provides a standard set of useful information when an error occurs, such as a stack trace and the error message. For example:
+
+Code:
+
+     var error = new Error("The error message");
+     console.log(error);
+     console.log(error.stack);
+
+Result:
+
+     { stack: [Getter/Setter],
+       arguments: undefined,
+       type: undefined,
+       message: 'The error message' }
+     Error: The error message
+         at Object.<anonymous> (/home/nico/example.js:1:75)
+         at Module._compile (module.js:407:26)
+         at Object..js (module.js:413:10)
+         at Module.load (module.js:339:31)
+         at Function._load (module.js:298:12)
+         at Array.0 (module.js:426:10)
+         at EventEmitter._tickCallback (node.js:126:26)
+
+`error.stack` shows you where an error came from, as well as a list of the function calls that preceded it - for your convenience, `error.stack` always prints `error.message` as the first line of its output, making `error.stack` a convenient single property to log during debugging.
+
+If you want to add more information to the Error object, you can always add properities, just as with any other Javascript object: 
+
+    var error = new Error("The error message");
+    error.http_code = 404;
+    console.log(error);
+
+For more details how to use the Error object, check out the [article on error conventions](/articles/errors/what-are-the-error-conventions)
diff --git a/locale/uk/knowledge/errors/what-is-try-catch.md b/locale/uk/knowledge/errors/what-is-try-catch.md
new file mode 100755
index 0000000000000..e79ef44b44d43
--- /dev/null
+++ b/locale/uk/knowledge/errors/what-is-try-catch.md
@@ -0,0 +1,49 @@
+---
+title: What is try-catch?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - errors
+  - builtin
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Example:
+
+    console.log("entering try-catch statement");
+
+    try {
+      console.log("entering try block");
+      throw "thrown message";
+      console.log("this message is never seen");
+    }
+    catch (e) {
+      console.log("entering catch block");
+      console.log(e);
+      console.log("leaving catch block");
+    }
+    finally {
+      console.log("entering and leaving the finally block");
+    }
+
+    console.log("leaving try-catch statement");
+
+Results:
+
+    entering try-catch statement
+    entering try block
+    entering catch block
+    thrown message
+    leaving catch block
+    entering and leaving the finally block
+    leaving try-catch statement
+
+Javascript's `try-catch-finally` statement works very similarly to the `try-catch-finally` encountered in C++ and Java.  First, the try block is executed until and unless the code in it throws an exception (whether it is an explicit `throw` statement, the code has an uncaught native exception, or if the code calls a function that uses `throw`). 
+
+If the code doesn't throw an exception, then the whole try block is executed. If the code threw an exception inside the try block, then the catch block is executed.  Last of all, the finally block is always executed, subsequent to the other blocks but prior to any subsequent code located outside of the `try-catch-finally` blocks.  The `finally` block will just about always execute, no matter what kind of throwing, catching, or returning one might be trying to do inside the `try` or `catch` blocks.
+
+Note that you can omit the `catch` or `finally` block, but one of them must be present.
+
+## But wait, isn't it Node.js convention to not use try-catch?
+
+In the core node.js libraries, the only place that one really *needs* to use a try-catch is around `JSON.parse()`. All of the other methods use either the standard Error object through the first parameter of the callback or emit an `error` event. Because of this, it is generally considered [standard](/what-are-the-error-conventions) to return errors through the callback rather than to use the `throw` statement. 
diff --git a/locale/uk/knowledge/file-system/how-to-read-files-in-nodejs.md b/locale/uk/knowledge/file-system/how-to-read-files-in-nodejs.md
new file mode 100755
index 0000000000000..91864caf3d988
--- /dev/null
+++ b/locale/uk/knowledge/file-system/how-to-read-files-in-nodejs.md
@@ -0,0 +1,53 @@
+---
+title: How do I read files in node.js?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - filesystem
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+Reading the contents of a file into memory is a very common programming task, and, as with many other things, the Node.js core API provides methods to make this trivial.  There are a variety of file system methods, all contained in the `fs` module.  The easiest way to read the entire contents of a file is with `fs.readFile`, as follows:
+
+    fs = require('fs');
+    fs.readFile(file, [encoding], [callback]);
+
+    // file = (string) filepath of the file to read
+
+`encoding` is an optional parameter that specifies the type of encoding to read the file. Possible encodings are 'ascii', 'utf8', and 'base64'. If no encoding is provided, the default is `null`.
+
+`callback` is a function to call when the file has been read and the contents are ready - it is passed two arguments, `error` and `data`.  If there is no error, `error` will be `null` and `data` will contain the file contents; otherwise `err` contains the error message.
+
+So if we wanted to read `/etc/hosts` and print it to stdout (just like UNIX `cat`):
+
+    fs = require('fs')
+    fs.readFile('/etc/hosts', 'utf8', function (err,data) {
+      if (err) {
+        return console.log(err);
+      }
+      console.log(data);
+    });
+
+The contents of `/etc/hosts` should now be visible to you, provided you have permission to read the file in the first place.
+
+Let's now take a look at an example of what happens when you try to read an invalid file - the easiest example is one that doesn't exist.
+
+    fs = require('fs');
+    fs.readFile('/doesnt/exist', 'utf8', function (err,data) {
+      if (err) {
+        return console.log(err);
+      }
+      console.log(data);
+    });
+
+This is the output:
+
+    { stack: [Getter/Setter],
+      arguments: undefined,
+      type: undefined,
+      message: 'ENOENT, No such file or directory \'/doesnt/exist\'',
+      errno: 2,
+      code: 'ENOENT',
+      path: '/doesnt/exist' }
+
+This is a basic Node.js [Error object](/what-is-the-error-object) - it can often be useful to log `err.stack` directly, since this contains a stack trace to the location in code at which the Error object was created.
diff --git a/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md b/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md
new file mode 100755
index 0000000000000..a708eb556f33a
--- /dev/null
+++ b/locale/uk/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md
@@ -0,0 +1,42 @@
+---
+title: How do I search files and directories?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - filesystem
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Suppose you want to list all the files in the current directory.  One approach is to use the builtin `fs.readdir` [method](/how-do-i-read-files-in-node-js). This will get you an array of all the files and directories on the specified path:
+
+    fs = require('fs');
+
+    fs.readdir(process.cwd(), function (err, files) {
+      if (err) {
+        console.log(err);
+        return;
+      }
+      console.log(files);
+    });
+
+
+Unfortunately, if you want to do a recursive list of files, then things get much more complicated very quickly. To avoid all of this scary complexity, this is one of the places where a Node.js user-land library can save the day. [Node-findit](https://github.com/substack/node-findit), by SubStack, is a helper module to make searching for files easier.  It has interfaces to let you work with callbacks, events, or just plain old synchronously (not a good idea most of the time).
+
+To install `node-findit`, simply use npm:
+
+    npm install findit
+
+In the same folder, create a file called `example.js`, and then add this code.  Run it with `node example.js`.  This example uses the `node-findit` event-based interface.
+
+    //This sets up the file finder
+    var finder = require('findit').find(__dirname);
+
+    //This listens for directories found
+    finder.on('directory', function (dir) {
+      console.log('Directory: ' + dir + '/');
+    });
+
+    //This listens for files found
+    finder.on('file', function (file) {
+      console.log('File: ' + file);
+    });
diff --git a/locale/uk/knowledge/file-system/how-to-store-local-config-data.md b/locale/uk/knowledge/file-system/how-to-store-local-config-data.md
new file mode 100755
index 0000000000000..4e6aba75d9ed0
--- /dev/null
+++ b/locale/uk/knowledge/file-system/how-to-store-local-config-data.md
@@ -0,0 +1,85 @@
+---
+title: How to store local configuration data
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - conventions
+  - filesystem
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+Storing your Node.js application's configuration data is quite simple - every object in JavaScript can be easily rendered as [JSON](/what-is-json), which in turn is just string data that can be sent or saved any way you'd like.  The simplest way to do this involves the built-in `JSON.parse()` and `JSON.stringify()` methods.
+
+Let's take a look at a very simple (and contrived) example.  First, to save some very simple data:
+
+      var fs = require('fs');
+
+      var myOptions = {
+        name: 'Avian',
+        dessert: 'cake'
+        flavor: 'chocolate',
+        beverage: 'coffee'
+      };
+
+      var data = JSON.stringify(myOptions);
+
+      fs.writeFile('./config.json', data, function (err) {
+        if (err) {
+          console.log('There has been an error saving your configuration data.');
+          console.log(err.message);
+          return;
+        }
+        console.log('Configuration saved successfully.')
+      });
+
+It's really that simple - just `JSON.stringify()` and then save it however you'd like.
+
+Now let's load some configuration data:
+
+      var fs = require('fs');
+
+      var data = fs.readFileSync('./config.json'),
+          myObj;
+
+      try {
+        myObj = JSON.parse(data);
+        console.dir(myObj);
+      }
+      catch (err) {
+        console.log('There has been an error parsing your JSON.')
+        console.log(err);
+      }
+
+NODE PRO TIP:  Even if you don't like using `try/catch`, this is a place to use it.  `JSON.parse` is a very strict JSON parser, and errors are common - most importantly, though, `JSON.parse` uses the `throw` statement rather than giving a callback, so `try/catch` is the only way to guard against the error.
+
+Using the built-in `JSON` methods can take you far, but as with so many other problems you might be looking to solve with Node.js, there is already a solution in Userland that can take you much further.  The solution, in this case, is `nconf`.  Written by Charlie Robbins, it's a configuration manager for Node.js, supporting in-memory storage, local file storage, as well as support for a `redis` backend, provided in a separate module.
+
+Let's take a look now at how we'd perform some local configuration access with `nconf`.  First, you'll need to install it to your project's working directory:
+
+      npm install nconf
+
+After that, the syntax is a breeze. Have a look at an example:
+
+      var nconf = require('nconf');
+
+      nconf.use('file', { file: './config.json' });
+      nconf.load();
+      nconf.set('name', 'Avian');
+      nconf.set('dessert:name', 'Ice Cream');
+      nconf.set('dessert:flavor', 'chocolate');
+
+      console.log(nconf.get('dessert'));
+
+      nconf.save(function (err) {
+        if (err) {
+          console.error(err.message);
+          return;
+        }
+        console.log('Configuration saved successfully.');
+      });
+
+The only tricky thing to notice here is the delimiter - ':'.  When accessing nested properties with `nconf`, a colon is used to delimit the namespaces of key names.  If a specific sub-key is not provided, the whole object is set or returned.
+
+When using `nconf` to store your configuration data to a file, `nconf.save()` and `nconf.load()` are the only times that any actual file interaction will happen.  All other access is performed on an in-memory copy of your data, which will not persist without a call to `nconf.save()`.  Similarly, if you're trying to bring back configuration data from the last time your application ran, it will not exist in memory without a call to `nconf.load()`, as shown above.
+
diff --git a/locale/uk/knowledge/file-system/how-to-use-the-path-module.md b/locale/uk/knowledge/file-system/how-to-use-the-path-module.md
new file mode 100755
index 0000000000000..d2e7c94962683
--- /dev/null
+++ b/locale/uk/knowledge/file-system/how-to-use-the-path-module.md
@@ -0,0 +1,68 @@
+---
+title: How to use the path module?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - filesystem
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+The path module contains several helper functions to help make path manipulation easier.
+
+The first function worth mentioning is `path.normalize`.  This function takes a path (in the form of a string) and strips it of duplicate slashes and normalizes directory abbreviations, like '.' for 'this directory' and '..' for 'one level up'. For example:
+
+    > var path = require('path');
+    > path.normalize('/a/.///b/d/../c/')
+    '/a/b/c/'
+
+A closely related function to `normalize` is `join`.  This function takes a variable number of arguments, joins them together, and normalizes the path.
+
+    > var path = require('path');
+    > path.join('/a/.', './//b/', 'd/../c/')
+    '/a/b/c'
+
+A possible use of `join` is to manipulate paths when serving urls:
+
+    > var path = require('path');
+    > var url = '/index.html';
+    > path.join(process.cwd(), 'static', url);
+    '/home/nico/static/index.html'
+
+There are three functions which are used to extract the various parts of the path name: `basename`, `extname`, and `dirname`. 
+- `basename` returns the last portion of the path passed in. 
+- `extname` returns the extension of the last portion. Generally for directories, `extname` just returns ''. 
+- Finally, `dirname` returns everything that `basename` does not return.
+For example:
+
+    > var path = require('path')
+    > var a = '/a/b/c.html'
+    > path.basename(a)
+    'c.html'
+    > path.extname(a)
+    '.html'
+    > path.dirname(a)
+    '/a/b'
+
+Note that `basename` has an optional second parameter that will strip out the extension if you pass the correct extension.
+
+    > var path = require('path')
+    > var a = '/a/b/c.html'
+    > path.basename(a, path.extname(a))
+    'c'
+
+Lastly, the `path` module provides methods to check whether or not a given path exists: `exists` and `existsSync` They both take the path of a file for the first parameter. 
+
+`exists` takes a callback as its second parameter, to which is returned a boolean representing the existance of the file. 
+
+`existsSync`, on the other hand, checks the given path synchronously, returning the boolean directly.  In Node.js, you will typically want to use the asynchronous functions for most file system I/O - the synchronous versions will block your entire process until they finish. 
+
+Blocking isn't always a bad thing.  Checking the existence of a vital configuration file synchronously makes sense, for example - it doesn't matter much if your process is blocking for something it can't run without!  Conversely, though, in a busy HTTP server, any per-request file I/O **MUST** be asynchronous, or else you'll be responding to requests one by one. See the article on [asynchronous operations](/how-to-write-asynchronous-code) for more details.
+
+        > var path = require('path')
+        > path.exists('/etc', function(exists){console.log("Does the file exist?", exists)})
+        > Does the file exist? true
+
+        > path.existsSync('/etc')
+        true
+
diff --git a/locale/uk/knowledge/file-system/how-to-write-files-in-nodejs.md b/locale/uk/knowledge/file-system/how-to-write-files-in-nodejs.md
new file mode 100755
index 0000000000000..b45699d4d7883
--- /dev/null
+++ b/locale/uk/knowledge/file-system/how-to-write-files-in-nodejs.md
@@ -0,0 +1,50 @@
+---
+title: How do I write files in node.js?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - filesystem
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+Writing to a file is another of the basic programming tasks that one usually needs to know about - luckily, this task is very simple in Node.js.  We can use the handy `writeFile` method inside the standard library's `fs` module, which can save all sorts of time and trouble.
+
+    fs = require('fs');
+    fs.writeFile(filename, data, [encoding], [callback])
+
+`file = (string)` filepath of the file to read
+
+`data = (string or buffer)` the data you want to write to the file
+
+`encoding = (optional string)` the encoding of the `data`. Possible encodings are 'ascii', 'utf8', and 'base64'. If no encoding provided, then 'utf8' is assumed.
+
+`callback = (optional function (err) {})` If there is no error, `err === null`, otherwise `err` contains the error message.
+
+So if we wanted to write "Hello World" to `helloworld.txt`:
+
+    fs = require('fs');
+    fs.writeFile('helloworld.txt', 'Hello World!', function (err) {
+      if (err) return console.log(err);
+      console.log('Hello World > helloworld.txt');
+    });
+
+    [contents of helloworld.txt]:
+    Hello World!
+
+If we purposely want to cause an error, we can try to write to a file that we don't have permission to access:
+
+    fs = require('fs')
+    fs.writeFile('/etc/doesntexist', 'abc', function (err,data) {
+      if (err) {
+        return console.log(err);
+      }
+      console.log(data);
+    });
+
+    { stack: [Getter/Setter],
+      arguments: undefined,
+      type: undefined,
+      message: 'EACCES, Permission denied \'/etc/doesntexist\'',
+      errno: 13,
+      code: 'EACCES',
+      path: '/etc/doesntexist' }
diff --git a/locale/uk/knowledge/file-system/security/introduction.md b/locale/uk/knowledge/file-system/security/introduction.md
new file mode 100755
index 0000000000000..8803a3e8964b4
--- /dev/null
+++ b/locale/uk/knowledge/file-system/security/introduction.md
@@ -0,0 +1,50 @@
+---
+title: How can I secure my code?
+date: null
+tags:
+  - filesystem
+  - security
+difficulty: 3
+layout: knowledge-post.hbs
+---
+
+Sometimes, you might want to let users read or write files on your server. For example, maybe you want to write a forum software without using an actual database. The problem is that you do not want your users to be able to modify or to read arbitrary files on your server, and there sometimes are ways to get around restrictions that should prevent it. Read on to see how you can secure your code against evil attackers trying to mess with your files.
+
+Poison Null Bytes
+=================
+Poison null bytes are a way to trick your code into seeing another filename than the one that will actually be opened. This can in many cases be used to circumvent directory traversal protections, to trick servers into delivering files with wrong file types and to circumvent restrictions on the file names that may be used. [A more detailed description is here.](http://groups.google.com/group/nodejs/browse_thread/thread/51f66075e249d767/85f647474b564fde) Always use code like this when accessing files with user-supplied names:
+
+    if (filename.indexOf('\0') !== -1) {
+      return respond('That was evil.');
+    }
+
+Whitelisting
+============
+You won't always be able to use whitelisting, but if you are, do it - it's very easy to implement and hard to get wrong. For example, if you know that all filenames are lowercase alphanumeric strings:
+
+    if (!/^[a-z0-9]+$/.test(filename)) {
+      return respond('illegal character');
+    }
+
+However, note that whitelisting alone isn't sufficient anymore as soon as you allow dots and slashes - people could enter things like `../../etc/passwd` in order to get files from outside the allowed folder.
+
+Preventing Directory Traversal
+==============================
+Directory traversal means that an attacker tries to access files outside of the folder you want to allow him to access. You can prevent this by using nodes built-in "path" module. **Do not implement the stuff in the path module again yourself** - for example, when someone runs your code on a windows server, not handling backslashes like slashes will allow attackers to do directory traversal.
+
+This example assumes that you already checked the `userSuppliedFilename` variable as described in the "Poison Null Bytes" section above.
+
+    var rootDirectory = '/var/www/';
+
+Make sure that you have a slash at the end of the allowed folders name - you don't want people to be able to access `/var/www-secret/`, do you?.
+
+    var path = require('path');
+    var filename = path.join(rootDirectory, userSuppliedFilename);
+
+Now `filename` contains an absolute path and doesn't contain `..` sequences anymore - `path.join` takes care of that. However, it might be something like `/etc/passwd` now, so you have to check whether it starts with the `rootDirectory`:
+
+    if (filename.indexOf(rootDirectory) !== 0) {
+      return respond('trying to sneak out of the web root?');
+    }
+
+Now the `filename` variable should contain the name of a file or directory that's inside the allowed directory (unless it doesn't exist).
diff --git a/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md b/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md
new file mode 100755
index 0000000000000..0f24e1baf418e
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/control-flow/how-to-write-asynchronous-code.md
@@ -0,0 +1,80 @@
+---
+title: How to write asynchronous code
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - asynchronous
+  - callbacks
+  - event-emitters
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Nodejs promotes an asynchronous coding style from the ground up, in contrast to many of the most popular web frameworks. There are a number of important things to be aware of when learning to write asynchronous code - otherwise, you will often find your code executing in extremely unexpected ways.  Take this (general) rule to heart:
+
+### Use the asynchronous functions, avoid the synchronous ones!
+
+Many of the functions in Node.js core have both synchronous and asynchronous versions. Under most circumstances, it will be far better for you to use the asynchronous functions - otherwise, why are you using Node.js?
+
+As a quick example comparing and contrasting the two, using `fs.readFile`:
+
+    var fs = require('fs');
+
+    fs.readFile('example.file', 'utf8', function (err, data) {
+        if (err) {
+          return console.log(err);
+        }
+        console.log(data);
+    });
+
+    //====================
+
+    var data = fs.readFileSync('example.file','utf8');
+    console.log(data);
+
+Just looking at these two blocks of code, the synchronous version appears to be more concise. However, the asynchronous version is more complicated for a very good reason. In the synchronous version, the world is paused until the file is finished reading - your process will just sit there, waiting for the OS (which handles all file system tasks).
+
+The asynchronous version, on the other hand, does not stop time - instead, the callback function gets called when the file is finished reading. This leaves your process free to execute other code in the meantime.
+
+When only reading a file or two, or saving something quickly, the difference between synchronous and asynchronous file I/O can be quite small. On the other hand, though, when you have multiple requests coming in per second that require file or database IO, trying to do that IO synchronously would be quite thoroughly disastrous for performance.
+
+
+### Callbacks
+Callbacks are a basic idiom in node.js for asynchronous operations. When most people talk about callbacks, they mean the function that is passed as the last parameter to an asynchronous function. The callback is then later called with any return value or error message that the function produced. For more details, see the article on [callbacks](/articles/getting-started/control-flow/what-are-callbacks)
+
+### Event Emitters
+Event Emitters are another basic idiom in node.js. A constructor is provided in Node.js core: `require('events').EventEmitter`. An Event Emitter is typically used when there will be multiple parts to the response (since usually you only want to call a callback once). For more details, see the article on [EventEmitters](/articles/getting-started/control-flow/what-are-event-emitters)
+
+### A gotcha with asynchronous code
+A common mistake in asynchronous code with javascript is to write code that does something like this:
+
+     for (var i = 0; i < 5; i++) {
+       setTimeout(function () {
+         console.log(i);
+       }, i);
+     }
+
+The unexpected output is then:
+
+    5
+    5
+    5
+    5
+    5
+
+The reason this happens is because each timeout is created and then `i` is incremented. Then when the callback is called, it looks for the value of `i` and it is 5. The solution is to create a closure so that the current value of `i` is stored. For example:
+
+     for (var i = 0; i < 5; i++) {
+       (function(i) {
+         setTimeout(function () {
+           console.log(i);
+         }, i);
+       })(i);
+    }
+
+This gives the proper output:
+
+    0
+    1
+    2
+    3
+    4
diff --git a/locale/uk/knowledge/getting-started/control-flow/what-are-callbacks.md b/locale/uk/knowledge/getting-started/control-flow/what-are-callbacks.md
new file mode 100755
index 0000000000000..11d7c26c7647c
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/control-flow/what-are-callbacks.md
@@ -0,0 +1,54 @@
+---
+title: What are callbacks?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - javascript
+  - core
+  - asynchronous
+  - callbacks
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+In a synchronous program, you would write something along the lines of:
+
+    function processData () {
+      var data = fetchData ();
+      data += 1;
+      return data;
+    }
+
+This works just fine and is very typical in other development environments. However, if fetchData takes a long time to load the data (maybe it is streaming it off the drive or the internet), then this causes the whole program to 'block' - otherwise known as sitting still and waiting - until it loads the data. Node.js, being an asynchronous platform, doesn't wait around for things like file I/O to finish - Node.js uses callbacks.  A callback is a function called at the completion of a given task; this prevents any blocking, and allows other code to be run in the meantime.
+
+The node.js way to deal with the above would look a bit more like this:
+
+    function processData (callback) {
+      fetchData(function (err, data) {
+        if (err) {
+          console.log("An error has occured. Abort everything!");
+          return callback(err);
+        }
+        data += 1;
+        callback(data);
+      });
+    }
+
+At first glance, it may look unnecessarily complicated, but callbacks are the foundation of Node.js. Callbacks give you an interface with which to say, "and when you're done doing that, do all this." This allows you to have as many IO operations as your OS can handle happening at the same time. For example, in a web server with hundreds or thousands of pending requests with multiple blocking queries, performing the blocking queries asynchronously gives you the ability to be able to continue working and not just sit still and wait until the blocking operations come back.  This is a major improvement.
+
+The typical convention with asynchronous functions (which almost all of your functions should be):
+
+    function asyncOperation ( a, b, c, callback ) {
+      // ... lots of hard work ...
+      if ( /* an error occurs */ ) {
+        return callback(new Error("An error has occured"));
+      }
+      // ... more work ...
+      callback(null, d, e, f);
+    }
+
+    asyncOperation ( params.., function ( err, returnValues.. ) {
+       //This code gets run after the async operation gets run
+    });
+
+You will almost always want to follow the [error callback convention](/articles/errors/what-are-the-error-conventions), since most Node.js users will expect your project to follow them. The general idea is that the callback is the last parameter. The callback gets called after the function is done with all of its operations. Traditionally, the first parameter of the callback is the `error` value. If the function hits an error, then they typically call the callback with the first parameter being an Error object. If it cleanly exits, then they will call the callback with the first parameter being null and the rest being the return value(s).
diff --git a/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md b/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md
new file mode 100755
index 0000000000000..b7900ec0fa953
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/control-flow/what-are-event-emitters.md
@@ -0,0 +1,103 @@
+---
+title: What are Event Emitters?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - asynchronous
+  - event-emitters
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+
+In node.js an event can be described simply as a string with a corresponding callback. An event can be "emitted" (or in other words, the corresponding callback be called) multiple times or you can choose to only listen for the first time it is emitted. So a simple example ran on the node [REPL](/articles/REPL/how-to-use-nodejs-repl):
+
+    var example_emitter = new (require('events').EventEmitter);
+    example_emitter.on("test", function () { console.log("test"); });
+    example_emitter.on("print", function (message) { console.log(message); });
+    example_emitter.emit("test");
+    example_emitter.emit("print", "message");
+    example_emitter.emit("unhandled");
+
+    > var example_emitter = new (require('events').EventEmitter);
+    {}
+    > example_emitter.on("test", function () { console.log("test"); });
+    { _events: { test: [Function] } }
+    > example_emitter.on("print", function (message) { console.log(message); });
+    { _events: { test: [Function], print: [Function] } }
+    > example_emitter.emit("test");
+    test //console.log'd
+    true //return value
+    > example_emitter.emit("print", "message");
+    message //console.log'd
+    true    //return value
+    > example_emitter.emit("unhandled");
+    false   //return value
+
+This demonstates all the basic functionality of an EventEmitter. The `on` or `addListener` method (basically the subscription method) allows you to choose the event to watch for and the callback to be called. The `emit` method (the publish method), on the other hand, allows you to "emit" an event, which causes all callbacks registered to the event to 'fire', (get called).
+
+So in the example, we first subscribe to both the `test` and `print` events. Then we emit the `test`, `print`, and `unhandled` events. Since `unhandled` has no callback, it just returns false; the other two run all the attached callbacks and return true.
+
+In the `print` event, note that we pass an extra parameter - all the extra parameters passed to 'emit' get passed to the callback function as arguments.
+
+If you use the method `once` instead of `on`, after the callback is fired, it is removed from the list of callbacks. A handy little function if you want to detect only the first time an event has been emitted.
+
+If you want remove a specific callback, you can use `removeListener`. If you want to remove all callbacks to a specific event, you can use `removeAllListeners`.
+
+    var EventEmitter = require('events').EventEmitter,
+        ee = new EventEmitter();
+
+    function callback() {
+      console.log("Callback has been called!");
+    }
+
+    ee.once("event", callback);
+    ee.emit("event");
+    ee.emit("event");
+
+    ee.on("event", callback);
+    ee.emit("event");
+    ee.emit("event");
+    ee.removeListener("event", callback);
+    ee.emit("event");
+
+    ee.on("event", callback);
+    ee.emit("event");
+    ee.removeAllListeners("event");
+    ee.emit("event");
+
+    > var ee = new (require('events').EventEmitter);
+    > var callback = function () { console.log("Callbacked!"); }
+    > ee.once("event", callback);
+    { _events: { event: { [Function: g] listener: [Function] } } }
+    > ee.emit("event");
+    Callbacked! //console.log'd
+    true
+    > ee.emit("event");
+    false
+
+    > ee.on("event", callback);
+    { _events: { event: [Function] } }
+    > ee.emit("event");
+    Callbacked! //console.log'd
+    true
+    > ee.emit("event");
+    Callbacked! //console.log'd
+    true
+    > ee.removeListener("event", callback);
+    { _events: {} }
+    > ee.emit("event");
+    false
+
+    > ee.on("event", callback);
+    { _events: { event: [Function] } }
+    > ee.emit("event");
+    Callbacked! //console.log'd
+    true
+    > ee.removeAllListeners("event");
+    { _events: { event: null } }
+    > ee.emit("event");
+    false
+
+NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidently leaking event listeners.
+
diff --git a/locale/uk/knowledge/getting-started/globals-in-node-js.md b/locale/uk/knowledge/getting-started/globals-in-node-js.md
new file mode 100755
index 0000000000000..8a2f2d83ede17
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/globals-in-node-js.md
@@ -0,0 +1,27 @@
+---
+title: The built-in globals in Node.js
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - globals
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Node.js has a number of built-in global identifiers that every Node.js developer should have some familiarity with.  Some of these are true globals, being visible everywhere; others exist at the module level, but are inherent to every module, thus being pseudo-globals.
+
+First, let's go through the list of 'true globals':
+
+- `global` - The global namespace.  Setting a property to this namespace makes it globally visible within the running process.
+- `process` - Node's built-in `process` module, which provides interaction with the current Node process.  [Read More](/articles/getting-started/the-process-module)
+- `console` - Node's built-in `console` module, which wraps various STDIO functionality in a browser-like way.  [Read More](/articles/getting-started/the-console-module)
+- `setTimeout()`, `clearTimeout()`, `setInterval()`, `clearInterval()` - The built-in timer functions are globals. [Read More](/articles/javascript-conventions/what-are-the-built-in-timer-functions)
+
+As mentioned above, there are also a number of 'pseudo-globals' included at the module level in every module:
+
+- `module`, `module.exports`, `exports` - These objects all pertain to Node's module system.  [Read More](/articles/getting-started/what-is-require)
+- __filename - The `__filename` keyword contains the path of the currently executing file.  Note that this is not defined while running the [Node REPL](/articles/REPL/how-to-use-nodejs-repl).
+- __dirname - Like `__filename`, the `__dirname` keyword contains the path to the root directory of the currently executing script.  Also not present in the Node REPL.
+- require() - The `require()` function is a built-in function, exposed per-module, that allows other valid modules to be included.  [Read More](/articles/getting-started/what-is-require)
+
+Much of this functionality can be extremely useful for a Node.js developer's daily life - but at the very least, remember these as bad names to use for your own functions! 
diff --git a/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md b/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md
new file mode 100755
index 0000000000000..f20cdc8d67c4f
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/how-to-debug-nodejs-applications.md
@@ -0,0 +1,93 @@
+---
+title: How to debug a node application
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - debug
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Often times, not just in the Node.js community but in software at large, people debug simply with a liberal sprinkle of standard output statements. This allows you to track down where unexpected values are being generated. However, this method can be tedious, or worse yet, not robust enough to detect the real problem.
+
+
+### Set up
+
+Thankfully, through the use of `node-inspector`, we can harness to power of the webkit-debuggers to work with our node.js code. The process itself is simple.
+
+First, ensure that node-inspector is installed:
+
+    npm install node-inspector -g
+
+A good example application to experiment with is a basically 'hello world' server with a counter (copied from the `node-inspector` repo):
+
+    var http = require('http');
+
+    var x = 0;
+    http.createServer(function (req, res) {
+      x += 1;
+      res.writeHead(200, {'Content-Type': 'text/plain'});
+      res.end('Hello World ' + x);
+    }).listen(8124);
+    console.log('Server running at http://127.0.0.1:8124/');
+
+First, we start your node program with debugging enabled.
+
+    node --debug app.js
+
+which should print something along the lines of `debugger listening on port 5858` to stderr. Take note of the port number, it is the port that the debugger is running on.
+
+Next, start up `node-inspector`. If your program uses port 8080, then you may have to pass it a custom port.
+
+    node-inspector [--web-port=<custom port number>]
+
+Finally you fire up a webkit browser such as chrome or safari. and go to `127.0.0.1:8080/debug?port=5858`. Note, if the debugger is listening on a port other than `5858`, you will need to change it. Also, if you passed a custom webport to node-inspector, then you will have to modify the `8080`.
+
+At this point, you will be met with a fairly empty screen with the `scripts`, `profiles`, and `console` tabs.
+
+### Scripts tab
+
+This is just like most webkit/firebug debuggers. It has a list of all the javascript files (including node.js core and third party libraries) which you can select and dive into. To stop the interpreter on a specific line, you set a breakpoint by clicking on the number of the desired line. When the execution is frozen, by a breakpoint or by manually pausing interpretation by pressing the pause button, you can check the callstack and examine all the local, closure, and global variables. You can also modify the code to try and fix behavior. Note that when you modify the code through the script tab, it does not get saved to the file, so you will need to transfer the modifications back by hand.
+
+### Profiles tab
+
+To use the profile tab, you need a library called `v8-profiler`:
+
+    npm install v8-profiler
+
+Next, you have to require it inside the file you are debugging:
+
+    var profiler = require('v8-profiler');
+
+Now you can finally enable the `profiles` tab, unfortunately, all you can do from this screen is a heap snapshot. So from the code, you need to select where you want to start to cpu profiler and can select more precise location for heap snapshots.
+
+To take a heap snapshot, just insert this line in the desired location and optionally pass it a name.
+
+    var snapshot = profiler.takeSnapshot(name);
+
+To take a cpu profile, just surround the code that you are profiling with the two lines shown below.  Optionally, a name can be included to indentify the cpu profile.
+
+    profiler.startProfiling(name);
+    //..lots and lots of methods and code called..//
+    var cpuProfile = profiler.stopProfiling([name]);
+
+As an example how to use these, here is the code given earlier modified to take a cpu profile on every request and take a heap snapshot: after the server is created.
+
+    var http = require('http');
+    var profiler = require('v8-profiler');
+
+    var x = 0;
+    http.createServer(function (req, res) {
+      x += 1;
+      profiler.startProfiling('request '+x);
+      res.writeHead(200, {'Content-Type': 'text/plain'});
+      res.end('Hello World ' + x);
+      profiler.stopProfiling('request '+x);
+    }).listen(8124);
+    profiler.takeSnapshot('Post-Server Snapshot');
+    console.log('Server running at http://127.0.0.1:8124/');
+
+Note that despite these apis returning objects, it is much easier to sort through the data through the node-inspector interface. Hopefully with these tools, you can make more informed decisions about memory leaks and bottlenecks.
+
+### Console tab
+
+Finally, the console tab allows you to use node's REPL in your program's global scope. This has a few gotchas since that means you can not access in local variables. Thus the variables you can read or write are variables that were defined without a `var` statement. The other gotcha is when you use `console.log` refers to node's `console.log` and not webkit's console.log. This means the output goes to stdout and not to your console tab. Otherwise it is a very straightforward node REPL.
diff --git a/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md b/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md
new file mode 100755
index 0000000000000..9f9844ddebd74
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/how-to-use-util-inspect.md
@@ -0,0 +1,49 @@
+---
+title: How to use util.inspect
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - debug
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Node provides a utility function, for debugging purposes, that returns a string representation of an object.  `util.inspect()` can be a true lifesaver while working with properties of large, complex objects. 
+
+Let's provide a basic example. `util.inspect()` can be used on any object - a good demonstration will be one of Node's built-in objects.  Try this in the REPL (type `node` at your command line with no arguments):
+
+     var util = require('util');
+     util.inspect(console);
+     
+The output will be:
+
+     '{ log: [Function], info: [Function], warn: [Function], error: [Function], dir: [Function], time: [Function], timeEnd: [Function], trace: [Function], assert: [Function] }'
+     
+This is a listing of all the enumerable properties of the `console` object.  It is also worth noting that `console.dir` is a wrapper around `util.inspect` that uses its default arguments.
+
+In the REPL, `util.inspect` will immediately return its output - this is not usually the case.  In the context of normal Node.js code in a file, something must be done with the output.  The simplest thing to do:
+
+     console.log(util.inspect(myObj));
+
+`util.inspect` can also be passed several optional arguments, shown here with their defaults:
+
+     util.inspect(object, showHidden=false, depth=2, colorize=true);
+
+For example, `util.inspect(myObj, true, 7, true)` would inspect `myObj`, showing all the hidden and non-hidden properties up to a depth of `7` and colorize the output.  Let's go over the arguments individually.
+
+The `depth` argument is the number of levels deep into a nested object to recurse - it defaults to 2.  Setting it to `null` will cause it to recurse 'all the way', showing every level.  Compare the (size of) the outputs of these two `util.inspect` statements in the REPL:
+
+     var http = require('http');
+     util.inspect(http, true, 1);
+     util.inspect(http, true, 3);
+
+The optional argument `showHidden` is a boolean that determines whether or not the 'non-enumerable' properties of an object will be displayed - it defaults to `false`, which tends to result in vastly more readable output.  This isn't something a beginner needs to worry about most of the time, but it's worth demonstrating briefly.  Once more, try the following in the REPL:
+
+     var util = require('util');
+     util.inspect(console, true);
+
+Finally, the optional argument `colorize` is a boolean that adds ANSI escape codes to the string output. When logged to a terminal window, it should be pretty printed with colors.
+
+     var util = require('util');
+     console.log(util.inspect({a:1, b:"b"}, false,2,true));
+
diff --git a/locale/uk/knowledge/getting-started/npm/how-to-access-module-package-info.md b/locale/uk/knowledge/getting-started/npm/how-to-access-module-package-info.md
new file mode 100755
index 0000000000000..7c4b67ae7cf4a
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/npm/how-to-access-module-package-info.md
@@ -0,0 +1,32 @@
+---
+title: How to access module package info
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - npm
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+There are many situations in the world of software development where using the wrong version of a dependency or submodule can cause all sorts of pain and anguish - luckily for you, node.js has a module available called pkginfo that can help keep these sorts of troubles at bay.
+
+Let's take a look at pkginfo - first, install via npm:
+
+     npm install pkginfo
+
+Now all we need to do is require it, and invoke it.
+
+     var pkginfo = require('pkginfo')(module);
+
+     console.dir(module.exports);
+
+That would show us the entire contents of the package.json, neatly displayed to our console.  If we only wanted certain pieces of information, we just specify them like so:
+
+     var pkginfo = require('pkginfo')(module, 'version', 'author');
+
+     console.dir(module.exports);
+
+And only the fields we specify will be shown to us.
+
+For more information, see http://github.com/indexzero/ .
diff --git a/locale/uk/knowledge/getting-started/npm/what-is-npm.md b/locale/uk/knowledge/getting-started/npm/what-is-npm.md
new file mode 100755
index 0000000000000..89b91a5bd085f
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/npm/what-is-npm.md
@@ -0,0 +1,26 @@
+---
+title: What is npm?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - npm
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+`npm`, short for Node Package Manager, is two things: first and foremost, it is an online repository for the publishing of open-source Node.js projects; second, it is a command-line utility for interacting with said repository that aids in package installation, version management, and dependency management.  A plethora of node.js libraries and applications are published on npm, and many more are added every day. These applications can be searched for on http://search.npmjs.org/. Once you have a package you want to install, it can be installed with a single commmand-line command.
+
+
+Let's say you're hard at work one day, developing the Next Great Application.  You come across a problem, and you decide that it's time to use that cool library you keep hearing about - let's use Caolan McMahon's [async](http://github.com/caolan/async) as an example. Thankfully, `npm` is very simple to use: you only have to run `npm install async`, and the specified module will be installed in the current directory under `./node_modules/`.  Once installed to your `node_modules` folder, you'll be able to use `require()` on them just like they were built-ins.
+
+Let's look at an example of a global install - let's say `coffee-script`. The npm command is simple: `npm install coffee-script -g`. This will typically install the program and put a symlink to it in `/usr/local/bin/`.  This will then allow you to run the program from the console just like any other CLI tool.  In this case, running `coffee` will now allow you to use the coffee-script REPL.
+
+Another important use for npm is dependency management.  When you have a node project with a [package.json](/articles/getting-started/npm/what-is-the-file-package-json) file, you can run `npm install` from the project root and npm will install all the dependencies listed in the package.json. This makes installing a Node project from a git repo much easier! For example, `vows`, one of Node's testing frameworks, can be installed from git, and its single dependency, `eyes`, can be automatically handled:
+
+Example:
+
+    git clone https://github.com/cloudhead/vows.git
+    cd vows
+    npm install
+
+After running those commands, you will see a `node_modules` folder containing all of the project dependencies specified in the package.json.
+
diff --git a/locale/uk/knowledge/getting-started/npm/what-is-the-file-package-json.md b/locale/uk/knowledge/getting-started/npm/what-is-the-file-package-json.md
new file mode 100755
index 0000000000000..40e5ea40a57fc
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/npm/what-is-the-file-package-json.md
@@ -0,0 +1,46 @@
+---
+title: What is the file `package.json`?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - npm
+  - conventions
+  - core
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+All npm packages contain a file, usually in the project root, called `package.json` - this file holds various metadata relevant to the project.  This file is used to give information to `npm` that allows it to identify the project as well as handle the project's dependencies. It can also contain other metadata such as a project description, the version of the project in a particular distribution, license information, even configuration data - all of which can be vital to both `npm` and to the end users of the package. The `package.json` file is normally located at the root directory of a Node.js project.
+
+Node itself is only aware of two fields in the `package.json`:
+
+    {
+      "name" : "barebones",
+      "version" : "0.0.0",
+    }
+
+The `name` field should explain itself: this is the name of your project. The `version` field is used by npm to make sure the right version of the package is being installed. Generally, it takes the form of `major.minor.patch` where `major`, `minor`, and `patch` are integers which increase after each new release. For more details, look at this spec: http://semver.org .
+
+For a more complete package.json, we can check out `underscore`:
+
+    {
+      "name" : "underscore",
+      "description" : "JavaScript's functional programming helper library.",
+      "homepage" : "http://documentcloud.github.com/underscore/",
+      "keywords" : ["util", "functional", "server", "client", "browser"],
+      "author" : "Jeremy Ashkenas <jeremy@documentcloud.org>",
+      "contributors" : [],
+      "dependencies" : [],
+      "repository" : {"type": "git", "url": "git://github.com/documentcloud/underscore.git"},
+      "main" : "underscore.js",
+      "version" : "1.1.6"
+    }
+
+As you can see, there are fields for the `description` and `keywords` of your projects. This allows people who find your project understand what it is in just a few words. The `author`, `contributors`, `homepage` and `repository` fields can all be used to credit the people who contributed to the project, show how to contact the author/maintainer, and give links for additional references. 
+
+The file listed in the `main` field is the main entry point for the libary; when someone runs `require(<library name>)`, require resolves this call to `require(<package.json:main>)`. 
+
+Finally, the `dependencies` field is used to list all the dependencies of your project that are available on `npm`. When someone installs your project through `npm`, all the dependencies listed will be installed as well.  Additionally, if someone runs `npm install` in the root directory of your project, it will install all the dependencies to `./node_modules`.
+
+It is also possible to add a `devDependencies` field to your `package.json` - these are dependencies not required for normal operation, but required/recommended if you want to patch or modify the project.  If you built your unit tests using a testing framework, for example, it would be appropriate to put the testing framework you used in your `devDependencies` field.  To install a project's `devDependencies`, simply pass the `--dev` option when you use `npm install`.
+
+For even more options, you can look through the [online docs](https://github.com/npm/npm/blob/master/doc/files/package.json.md) or run `npm help json`
diff --git a/locale/uk/knowledge/getting-started/the-console-module.md b/locale/uk/knowledge/getting-started/the-console-module.md
new file mode 100755
index 0000000000000..a95a62b07e477
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/the-console-module.md
@@ -0,0 +1,53 @@
+---
+title: The built-in console module
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - cli
+  - globals
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+
+Anyone familiar with browser-side development has probably used `console.log` for debugging purposes - Node.js has implemented a built-in `console` object to mimic much of this experience.  Since we're working server-side, however, it wraps `stdout`, `stdin`, and `stderr` instead of the browser's debugging console.
+
+Because of this browser parallel, the `console` module has become home to quite a bit of Node's standard output functionality.  The simplest is `console.log()`.
+
+     console.log('Hi, everybody!');
+     console.log('This script is:', __filename);
+     console.log(__filename, process.title, process.argv);
+
+The first, simplest example just prints the provided string to `stdout`.  It can also be used to output the contents of variables, as evidenced in #2; furthermore, `console.dir()` is called on any objects passed in as arguments, enumerating their properties.
+
+NODE.JS PRO TIP:
+`console.log()` accepts three format characters, `%s`, `%d`, and `%j`.  These format characters can be used to insert string, integer, or JSON data into your output - the order of format characters must match the order of arguments.
+
+     var name = 'Harry',
+         number = 17,
+         myObj = {
+           propOne: 'stuff',
+           propTwo: 'more stuff'
+         };
+     console.log('My name is %s, my number is %d, my object is %j', name, number, myObj);
+
+A gotcha with `console.log`, and all functions that depend on it, is that it buffers the output. So if your process ends suddenly, whether it be from an exception or from `process.exit()`, it is entirely possible that the buffered output will never reach the screen. This can cause a great deal of frustration, so watch out for this unfortunate situation.
+
+`console.error()` works the same as `console.log`, except that the output is sent to `stderr` instead of `stdout`.  This is actually an extremely important difference, as `stderr` is always written to synchronously.  Any use of `console.error`, or any of the other functions in Node.js core that write to `stderr`, will block your process until the output has all been written.  This is useful for error messages - you get them exactly when they occur - but if used everywhere, can greatly slow down your process.
+
+`console.dir()`, as mentioned above, is an alias for `util.inspect()` - it is used to enumerate object properties.  [Read More](/articles/getting-started/how-to-use-util-inspect)
+
+That covers the basic `console` module functionality, but there are a few other methods worth mentioning as well.  First, the `console` module allows for the marking of time via `console.time()` and `console.timeEnd()`.  Here is an example:
+
+     console.time('myTimer');
+     var string = '';
+     for (var i = 0; i < 300; i++) {
+       (function (i) {
+         string += 'aaaa' + i.toString();
+       })(i);
+     }
+     console.timeEnd('myTimer');
+
+This would determine the amount of time taken to perform the actions in between the `console.time` and `console.timeEnd` calls.
+
+One last function worth mentioning is `console.trace()`, which prints a stack trace to its location in your code without throwing an error.  This can occasionally be useful if you'd like to figure out where a particular failing function was called from.
diff --git a/locale/uk/knowledge/getting-started/the-process-module.md b/locale/uk/knowledge/getting-started/the-process-module.md
new file mode 100755
index 0000000000000..90158e568a80b
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/the-process-module.md
@@ -0,0 +1,104 @@
+---
+title: How to use the global process module
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - globals
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+
+Each Node.js process has a set of built-in functionality, accessible through the global `process` module.  The `process` module doesn't need to be required - it is somewhat literally a wrapper around the currently executing process, and many of the methods it exposes are actually wrappers around calls into some of Node's core C libraries.
+
+##Events
+
+There are two built-in events worth noting in the `process` module, `exit` and `uncaughtException`.
+
+The `exit` event fires whenever the process is about to exit.
+
+     process.on('exit', function () {
+      fs.writeFileSync('/tmp/myfile', 'This MUST be saved on exit.');
+     });
+
+Code like the above can occasionally be useful for saving some kind of final report before you exit.  Note the use of a synchronous file system call - this is to make sure the I/O finishes before the process actually exits.
+
+The other built-in event is called `uncaughtException`.  It fires, as you might guess, whenever an exception has occurred that hasn't been caught or dealt with somewhere else in your program.  It's not the ideal way to handle errors, but it can be very useful as a last line of defense if a program needs to stay running indefinitely.
+
+     process.on('uncaughtException', function (err) {
+       console.error('An uncaught error occurred!');
+       console.error(err.stack);
+     });
+
+The default behavior on `uncaughtException` is to print a stack trace and exit - using the above, your program will display the message provided and the stack trace, but will **not** exit.
+
+##Streams
+
+The `process` object also provides wrappings for the three `STDIO` streams, `stdin`, `stdout`, and `stderr`.  Put briefly, `stdin` is a readable stream (where one would read input from the user), `stdout` is a non-blocking writeable stream (writes to `stdout` are asynchronous, in other words), and `stderr` is a blocking (synchronous) writeable stream.
+
+The simplest one to describe is `process.stdout`.  Technically, most output in Node is accomplished by using `process.stdout.write()` - though most people would never know it.  The following is from `console.js` in Node core:
+
+      exports.log = function() {
+        process.stdout.write(format.apply(this, arguments) + '\n');
+      };
+
+Since most people are used to the `console.log` syntax from browser development, it was provided as a convenient wrapper.
+
+Next we have `process.stderr`, which is very similar to `process.stdout` with one key exception - it blocks.  When you write to `stderr`, your process blocks until the write is completed.  Node.js provides a number of alias functions for output, most of which either end up using `stdout` or `stderr` under the hood.  Here's a quick reference list:
+
+STDOUT, or non-blocking functions: `console.log`, `console.info`, `util.puts`, `util.print`
+
+STDERR, or blocking functions: `console.warn`, `console.error`, `util.debug`
+
+Lastly, `process.stdin` is a readable stream for getting user input.  See [more on cli input](/articles/command-line/how-to-prompt-for-command-line-input).
+
+##Other Properties
+
+The `process` object additionally contains a variety of properties that allow you to access information about the running process.  Let's run through a few quick examples with the help of the REPL:
+
+      > process.pid
+      3290
+      > process.version
+      'v0.4.9'
+      > process.platform
+      'linux'
+      > process.title
+      'node'
+
+The `pid` is the OS Process ID, `platform` is something general like 'linux' or 'darwin', and `version` refers to your Node version.  `process.title` is a little bit different - while set to `node` by default, it can be set to anything you want, and will be what gets displayed in lists of running processes.
+
+The `process` module also exposes `process.argv`, an array containing the command-line arguments to the current process, and `process.argc`, an integer representing the number of arguments passed in.  Read more on [how to parse command line arguments](/articles/command-line/how-to-parse-command-line-arguments)
+
+`process.execPath` will return the absolute path of the executable that started this process.
+
+`process.env` contains your environment variables.  Try `process.env.HOME`, for example.
+
+##Methods
+
+There are also a variety of methods attached to the `process` object, many of which deal with quite advanced aspects of a program.  We'll take a look at a few of the more commonly useful ones, while leaving the more advanced parts for another article.
+
+`process.exit` exits the process.  If you call an asynchronous function and then call `process.exit()` immediately afterwards, you will be in a race condition - the asynchronous call may or may not complete before the process is exited.  `process.exit` accepts one optional argument - an integer exit code.  `0`, by convention, is an exit with no errors.
+
+`process.cwd` returns the 'current working directory' of the process - this is often the directory from which the command to start the process was issued.
+
+`process.chdir` is used to change the current working directory.  For example:
+
+      > process.cwd()
+      '/home/avian/dev'
+      > process.chdir('/home/avian')
+      > process.cwd()
+      '/home/avian'
+
+Finally, on a more advanced note, we have `process.nextTick`.  This method accepts one argument - a callback - and places it at the top of the next iteration of the event loop.  Some people do something like this:
+
+      setTimeout(function () {
+        // code here
+      }, 0)
+
+This, however, is not ideal.  In Node.js, this should be used instead:
+
+      process.nextTick(function () {
+        console.log('Next trip around the event loop, wheeee!')
+      });
+
+It is much more efficient, and much more accurate.
diff --git a/locale/uk/knowledge/getting-started/what-is-node-core-verus-userland.md b/locale/uk/knowledge/getting-started/what-is-node-core-verus-userland.md
new file mode 100755
index 0000000000000..8407feda81661
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/what-is-node-core-verus-userland.md
@@ -0,0 +1,39 @@
+---
+title: What is node core versus userland
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - npm
+  - core
+  - userland
+  - terminology
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Occasionally, in the discussions in the NodeJS mailing lists and IRC channels, you may hear things referred to as "node-core" and "userland".
+
+Of course, traditionally, "userland" or "userspace" refer to everything outside the operating system kernel.  In that sense, Node itself is a "userland" program.
+
+However, in the context of NodeJS, "core" refers to the modules and bindings that are compiled into NodeJS.  In general, they provide a hook into very well-understood low-level functionality which almost all networking programs are going to require: TCP, HTTP, DNS, the File System, child processes, and a few other things.  If something is fancy enough to argue about, there's a good chance it won't be part of node-core.  HTTP is about as big as it gets, and if it wasn't so popular, it'd certainly not be a part of node.
+
+There are also some things in node-core that are simply too painful to do without in a JavaScript environment, or which have been created to implement some BOM constructs which are not part of the JavaScript language, but may as well be (eg, setTimeout, setInterval, and console).
+
+Everything else is "userland".  This includes: npm, express, request, coffee-script, mysql clients, redis clients, and so on.  You can often install these programs using [npm](http://npmjs.org/).
+
+The question of what is properly "node-core" and what belongs in "userland" is a constant battleground.  In general, node is based on the philosophy that it should *not* come with "batteries included".  It is easier to move things out of node-core than it is to move them in, which means that core modules must continually "pay rent" in terms of providing necessary functionality that nearly everyone finds valuable.
+
+## This is a Good Thing.
+
+One goal of node's minimal core library is to encourage people to implement things in creative ways, without forcing their ideas onto everyone.  With a tiny core and a vibrant user space, we can all flourish and experiment without the onerous burden of having to always agree all the time.
+
+## Userland isn't Less
+
+If anything, it's more.  Building functionality in userland rather than in node-core means:
+
+* You have a lot more freedom to iterate on the idea.
+* Everyone who wants your module can install it easily enough (if you publish it with npm).
+* You have freedom to break node conventions if that makes sense for your use-case.
+
+If you believe that something *really* just *needs* to be part of node's core library set, you should *still* build it as a module!  It's much more likely to be pulled into node-core if people have a chance to see your great ideas in action, and if its core principles are iterated and polished and tested with real-world use.
+
+Changing functionality that is included in node-core is very costly.  We do it sometimes, but it's not easy, and carries a high risk of regressions.  Better to experiment outside, and then pull it into node-core once it's stable.  Once it's usable as a userland package, you may even find that it's less essential to node-core than you first thought.
\ No newline at end of file
diff --git a/locale/uk/knowledge/getting-started/what-is-require.md b/locale/uk/knowledge/getting-started/what-is-require.md
new file mode 100755
index 0000000000000..411931848e07a
--- /dev/null
+++ b/locale/uk/knowledge/getting-started/what-is-require.md
@@ -0,0 +1,60 @@
+---
+title: What is require?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - npm
+  - core
+  - globals
+  - builtin
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+ Node.js follows the CommonJS module system, and the builtin `require` function is the easiest way to include modules that exist in separate files. The basic functionality of `require` is that it reads a javascript file, executes the file, and then proceeds to return the `exports` object. An example module:
+
+    console.log("evaluating example.js");
+
+    var invisible = function () {
+      console.log("invisible");
+    }
+
+    exports.message = "hi";
+
+    exports.say = function () {
+      console.log(exports.message);
+    }
+
+So if you run `var example = require('./example.js')`, then `example.js` will get evaluated and then `example` be an object equal to:
+
+    {
+      message: "hi",
+      say: [Function]
+    }
+
+If you want to set the exports object to a function or a new object, you have to use the `module.exports` object. So for an example:
+
+    module.exports = function () {
+      console.log("hello world")
+    }
+
+    require('./example2.js')() //require itself and run the exports object
+
+It is worth noting that each time you subsequently require an already-required file, the `exports` object is cached and reused. To illustrate this point:
+
+    node> require('./example.js')
+    evaluating example.js
+    { message: 'hi', say: [Function] }
+    node> require('./example.js')
+    { message: 'hi', say: [Function] }
+    node> require('./example.js').message = "hey" //set the message to "hey"
+    'hey'
+    node> require('./example.js') //One might think that this "reloads" the file...
+    { message: 'hey', say: [Function] } //...but the message is still "hey" because of the module cache.
+
+
+As you can see from the above, `example.js` is evaluated the first time, but all subsequent calls to `require()` only invoke the module cache, rather than reading the file again.  As seen above, this can occasionally produce side effects.
+
+The rules of where `require` finds the files can be a little complex, but a simple rule of thumb is that if the file doesn't start with "./" or "/", then it is either considered a core module (and the local Node path is checked), or a dependency in the local `node_modules` folder. If the file starts with "./" it is considered a relative file to the file that called `require`. If the file starts with "/", it is considered an absolute path. NOTE: you can omit ".js" and `require` will automatically append it if needed. For more detailed information, see [the official docs](http://nodejs.org/docs/v0.4.2/api/modules.htmll#all_Together...)
+
+An extra note: if the filename passed to `require` is actually a directory, it will first look for `package.json` in the directory and load the file referenced in the `main` property. Otherwise, it will look for an `index.js`.
+
diff --git a/locale/uk/knowledge/index.md b/locale/uk/knowledge/index.md
new file mode 100755
index 0000000000000..aad1ff4ba9a34
--- /dev/null
+++ b/locale/uk/knowledge/index.md
@@ -0,0 +1,6 @@
+---
+title: База знань
+layout: knowledge-base-index.hbs
+---
+
+# База знань
diff --git a/locale/uk/knowledge/intermediate/how-to-log.md b/locale/uk/knowledge/intermediate/how-to-log.md
new file mode 100755
index 0000000000000..560226ac429b1
--- /dev/null
+++ b/locale/uk/knowledge/intermediate/how-to-log.md
@@ -0,0 +1,92 @@
+---
+title: How to log in node.js
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - logging
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+Many processes, including most servers, write logs in one form or another. Reasons for logging include debugging, keeping track of users and resource usage, and reporting application state.
+
+### Simple Logging
+
+The simplest form of logging involves simply using `console.log` or one of the other standard output methods. In this approach, any information is printed to `stdout` where it can either be read by the developer as it occurs, or, for example, redirected to a log file. 
+
+    console.log('Web Server started, waiting for connections...');
+
+Because it's so simple, console.log is by far the most common way of logging data in node.js.
+
+### Custom Logging
+
+Logging only with functions such as `console.log` is not ideal for every use case, however.  Many applications have some sort of 'debugging mode', for example, that shows the user much more output than normal execution.  To do something like this, a better idea is to write your own simple logger, and use it instead of `console.log`. 
+
+Here is an example of a basic custom logging module with configurable debugging levels.
+
+      var logger = exports;
+      logger.debugLevel = 'warn';
+      logger.log = function(level, message) {
+        var levels = ['info', 'warn', 'error'];
+        if (levels.indexOf(level) <= levels.indexOf(logger.debugLevel) ) {
+          if (typeof message !== 'string') {
+            message = JSON.stringify(message);
+          };
+          console.log(level+': '+message);
+        }
+      }
+
+Usage would then look like the following:
+
+      var logger = require('./logger');
+      logger.debugLevel = 'warn';
+      logger.log('info', 'Everything started properly.');
+      logger.log('warn', 'Running out of memory...');
+      logger.log('error', { error: 'flagrant'});
+    
+Because `logger.debugLevel` was set to `warn`, the warning message and the error would both be displayed, but the `info` message would not be.
+
+The advantage here is that the behavior of our logging mechanisms can now be modified and controlled from a central part of our code. In this case, logging levels were added, and messages are converted to JSON if they aren't already in string form. There is a lot more that could be done here - saving logs to a file, pushing them to a database, setting custom colors and formatting the output - but by the time you want that much functionality from your custom logging function, it might be time to use an already-existing library.
+
+### Winston - multi-transport logging made easy
+
+[Winston](https://github.com/indexzero/winston) is a multi-transport, asynchronous logging library for node.js.  It is conceptually similar to our custom logger, but comes with a wide variety of useful features and functionality baked in. In addition, `winston` is battle-hardened by internal use at Nodejitsu!
+
+Here is an example of setting up a `winston` logger.  This example includes most of the transports one could ever possibly want - please note that most use cases will only warrant a few of these.
+
+      var winston = require('winston');
+
+      require('winston-riak').Riak;
+      require('winston-mongo').Mongo;
+      require('winston-couchdb').Couchdb;
+      
+      var logger = new (winston.Logger)({
+        transports: [
+          new winston.transports.Console(),
+          new winston.transports.File({ filename: 'path/to/all-logs.log' }),
+          new winston.transports.Couchdb({ 'host': 'localhost', 'db': 'logs' }),
+          new winston.transports.Riak({ bucket: 'logs' }),
+          new winston.transports.MongoDB({ db: 'db', level: 'info'})
+        ],
+        exceptionHandlers: [
+          new winston.transports.File({ filename: 'path/to/exceptions.log' })
+        ]
+      });
+
+Here, we have instantiated a new `winston` logger, and provided a number of logging transports.  Winston has built-in support for configurable logging levels, and provides alias methods for each configured logging level.  For example, `winston.warn(x)` is an alias for `winston.log('warn', x)`.  Thus, the following:
+
+      logger.warn('Hull Breach Detected on Deck 7!'); 
+
+Would output to the screen:
+
+      warn: Hull Breach Detected on Deck 7!
+
+Because of the file transport we set up, winston also logged the warning to 'somefile.log'.  After the `logger.warn` call we just used, the log file, `somefile.log`, would contain the following output:
+
+      $ cat somefile.log 
+      {'level':'warn','message':'Hull Breach Detected on Deck 7!'}
+
+Note that winston's file logger formats the logs differently for file logging (JSON in this case) than it does for the console transport.
+
+Winston also supports logging to Riak, CouchDB, MongoDB and [many other transports](https://github.com/winstonjs/winston/blob/master/docs/transports.md).  The `logger.warn` call we used before also put the same message into each database, according to the options we gave to each transport.
+
+For further information, please see the [thorough documentation for Winston.](https://github.com/indexzero/winston).
diff --git a/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md b/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md
new file mode 100755
index 0000000000000..4308b4d6bb700
--- /dev/null
+++ b/locale/uk/knowledge/javascript-conventions/how-to-create-default-parameters-for-functions.md
@@ -0,0 +1,68 @@
+---
+title: How To Create Default Parameters for Functions
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - javascript
+  - builtin
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+Usually a function will take a set number of parameters, and require that all of them be present before it can be executed successfully. However, you will sometimes run into situations where you want to provide a default value for a parameter or take a variable number of parameters. Unfortunately, javascript does not have a builtin way to do that; over time, however, people have developed idioms to compensate.
+
+The first idiom is giving a default value for the last parameter. This is done by checking if the last parameter is `undefined` and setting it to a default value if it is. Sometimes people use the idiom: `optionalParameter = optionalParameter || defaultValue`. This can have some undesirable behavior when they pass values that are equal to false such as `false`, `0`, and `""`. So a better way to do this is by explicitly checking that the optional parameter is `undefined`. Here is some code showing the two styles and the differing behavior:
+
+    example = function (optionalArg) {
+      optionalArg = optionalArg || "No parameter was passed";
+      console.log(optionalArg);
+    }
+
+    betterExample = function (optionalArg) {
+      if (typeof optionalArg === 'undefined') {
+        optionalArg = "No parameter was passed";
+      }
+      console.log(optionalArg);
+    }
+
+    console.log("Without parameter:");
+    example();
+    betterExample();
+
+    console.log("\nWith paramater:");
+    example("parameter was passed");
+    betterExample("parameter was passed");
+
+    console.log("\nEmpty String:");
+    example("");
+    betterExample("");
+
+
+If the optional value is in the middle it can cause some undesired effects, since all the parameters are shifted over. The optional parameter is not the `undefined` value in this case - the last parameter is the `undefined` one. So you have to check if the last parameter is `undefined` and then manually fix all the other parameters before continuing in the code. This example shows you how to do that:
+
+    example = function (param1, optParam, callback) {
+      if (typeof callback === 'undefined') {
+        // only two paramaters were passed, so the callback is actually in `optParam`
+        callback = optParam;
+
+        //give `optParam` a default value
+        optParam = "and a default parameter";
+      }
+      callback(param1, optParam);
+    }
+
+    example("This is a necessary parameter", console.log);
+    example("This is a necessary parameter", "and an optional parameter", console.log);
+
+More complicated cases require more code and can obscure the meaning of what you are trying to do. It then becomes a good idea to use helper functions - for example, suppose we wanted to take a variable amount of parameters and pass them all to the callback. You could try to accomplish this by manipulating the `arguments` variable - however, it is just easier to use the [vargs](https://github.com/cloudhead/vargs) library. As you can see by this code, it makes the whole process a little simpler:
+
+    var Args = require("vargs").Constructor;
+
+    example = function () {
+      var args = new Args(arguments);
+      args.callback.apply({},args.all);
+    }
+
+    example("The first parameter", console.log);
+    example("The first parameter", "and second parameter", console.log);
+    example("The first parameter", "and second parameter", "and third parameter", console.log);
+    example("The first parameter", "and second parameter", "and third parameter", "etc", console.log);
diff --git a/locale/uk/knowledge/javascript-conventions/using-ECMA5-in-nodejs.md b/locale/uk/knowledge/javascript-conventions/using-ECMA5-in-nodejs.md
new file mode 100755
index 0000000000000..57e10e05bd18c
--- /dev/null
+++ b/locale/uk/knowledge/javascript-conventions/using-ECMA5-in-nodejs.md
@@ -0,0 +1,97 @@
+---
+title: Using ECMA5 in node.js
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - builtin
+  - globals
+difficulty: 2
+layout: knowledge-post.hbs
+---
+
+When developing in the browser there are many wonderful built in JavaScript functions that we can't use because certain browsers don't implement them.  As a result, most developers never use them.  In Node, however we can assume that everyone has the same JavaScript implementation and as such can use these wonderful functions and not implement them over and over in our own libraries.
+
+The following is a list of some interesting api bits that aren't considered safe to use in a web setting but are built in to node's V8 engine.
+
+Note that V8 implements all of ECMA 3rd edition and parts of the new stuff in the [ECMA 5th edition](http://www.ecma-international.org/publications/standards/Ecma-262.htm)
+
+## Syntax extensions
+
+ * `var obj = { get a() { return "something" }, set a() { "do nothing" } }` getter/setter syntax
+
+## Array
+
+ * `Array.isArray(array)` - Returns true if the passed argument is an array.
+
+## Array.prototype
+
+ * `indexOf(value)` - Returns the first (least) index of an element within the array equal to the specified value, or -1 if none is found.
+ * `lastIndexOf(value)` - Returns the last (greatest) index of an element within the array equal to the specified value, or -1 if none is found.
+ * `filter(callback)` - Creates a new array with all of the elements of this array for which the provided filtering function returns true.
+ * `forEach(callback)` - Calls a function for each element in the array.
+ * `every(callback)` - Returns true if every element in this array satisfies the provided testing function.
+ * `map(callback)` - Creates a new array with the results of calling a provided function on every element in this array.
+ * `some(callback)` - Returns true if at least one element in this array satisfies the provided testing function.
+ * `reduce(callback[, initialValue])` - Apply a function simultaneously against two values of the array (from left-to-right) as to reduce it to a single value.
+ * `reduceRight(callback[, initialValue])` - Apply a function simultaneously against two values of the array (from right-to-left) as to reduce it to a single value.
+
+## Date
+
+ * `Date.now()` - Returns the numeric value corresponding to the current time.
+
+## Date.prototype
+
+ * `toISOString()` - 
+
+## Object
+
+ * `Object.create(proto, props)` - Creates a new object whose prototype is the passed in parent object and whose properties are those specified by props. 
+ * `Object.keys(obj)` - Returns a list of the ownProperties of an object that are enumerable.
+ * `Object.defineProperty(obj, prop, desc)` - Defines a property on an object with the given descriptor
+ * `Object.defineProperties(obj, props)` - Adds own properties and/or updates the attributes of existing own properties of an object
+ * `Object.getOwnPropertyNames(obj)` - Returns a list of the ownProperties of an object including ones that are not enumerable.
+ * `Object.getPrototypeOf(obj)` - Returns the prototype of an object.
+ * `Object.getOwnPropertyDescriptor(obj, property)` - Returns an object with keys describing the description of a property (value, writable, enumerable, configurable)
+ * `Object.preventExtensions(obj)` - Prevents any new properties from being added to the given object.
+ * `Object.isExtensible(obj)` - Checks if Object.preventExtensions() has been called on this object.
+ * `Object.seal(obj)` - Prevents code from adding or deleting properties, or changing the descriptors of any property on an object. Property values can be changed however.
+ * `Object.isSealed(obj)` - Checks if Object.seal() has been called on this object.
+ * `Object.freeze(obj)` - Same as Object.seal, except property values cannot be changed.
+ * `Object.isFrozen(obj)` - Checks if Object.freeze() has been called on this object.
+
+## Object.prototype
+
+ * `__defineGetter__(name, callback)` - (Mozilla extension, not ECMAScript 5) Associates a function with a property that, when accessed, executes that function and returns its return value.
+ * `__defineSetter__(name, callback)` - (Mozilla extension, not ECMAScript 5) Associates a function with a property that, when set, executes that function which modifies the property.
+ * `__lookupGetter__(name)` - (Mozilla extension, not ECMAScript 5) Returns the function associated with the specified property by the __defineGetter__ method.
+ * `__lookupSetter__(name)` - (Mozilla extension, not ECMAScript 5) Returns the function associated with the specified property by the __defineSetter__ method.
+ * `isPrototypeOf(obj)` - (EcmaScript 3 and 5) Returns true if `this` is a prototype of the passed in object.
+
+## Function.prototype
+
+ * `bind(thisArg[, arg1[, argN]])` - Sets the value of 'this' inside the function to always be the value of thisArg when the function is called. Optionally, function arguments can be specified (arg1, arg2, etc) that will automatically be prepended to the argument list whenever this function is called.
+
+## JSON
+
+ * `JSON.stringify(obj [, replacer [, space]])` - Takes any serializable object and returns the JSON representation as a string [More info](https://developer.mozilla.org/En/Using_JSON_in_Firefox)
+ * `JSON.parse(string)` - Takes a well formed JSON string and returns the corresponding JavaScript object.
+
+## String.prototype
+
+ * `trim()` - Trims whitespace from both ends of the string
+ * `trimRight()` - Trims whitespace from the right side of the string
+ * `trimLeft()` - Trims whitespace from the left side of the string
+
+## Property Descriptor Defaults
+
+ * `value` - undefined
+ * `get` - undefined
+ * `set` - undefined
+ * `writable` - false
+ * `enumerable` - false
+ * `configurable` - false
+
+# Missing features
+
+ * `Object.__noSuchMethod__` (Mozilla extension, not ECMAScript 5)
+ * `"use strict";` syntax extension ([v8 issue](http://code.google.com/p/v8/issues/detail?id=919))
\ No newline at end of file
diff --git a/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md b/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md
new file mode 100755
index 0000000000000..4fc966d1ebefd
--- /dev/null
+++ b/locale/uk/knowledge/javascript-conventions/what-are-the-built-in-timer-functions.md
@@ -0,0 +1,68 @@
+---
+title: What are the built-in timer functions?
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - core
+  - builtin
+  - globals
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+There are two built-in timer functions, `setTimeout` and `setInterval`, which can be used to call a function at a later time. For an example usage:
+
+    setTimeout(function() { console.log("setTimeout: It's been one second!"); }, 1000);
+    setInterval(function() { console.log("setInterval: It's been one second!"); }, 1000);
+
+An example output is:
+
+    setTimeout: It's been one second!
+    setInterval: It's been one second!
+    setInterval: It's been one second!
+    setInterval: It's been one second!
+    setInterval: It's been one second!
+    ...
+
+As you can see the parameters to both are the same. The number second paramter says how long in milliseconds to wait before calling the function passed into the first parameter. The difference between the two functions is that `setTimeout` calls the callback only once while `setInterval` will call it over and over again.
+
+Typically you want to be careful with `setInterval` because it can cause some undesireable effects.  If, for example, you wanted to make sure your server was up by pinging it every second, you might think to try something like this:
+
+    setInterval(ping, 1000);
+
+This can cause problems, however, if your server is slow and it takes, say, 3 seconds to respond to the first request. In the time it takes to get back the response, you would have sent off 3 more requests - not exactly desirable!  This isn't the end of the world when serving small static files, but if you doing an expensive operation such as database query or any complicated computation this can have some undiserable results. A common solution looks like this:
+
+    var recursive = function () {
+        console.log("It has been one second!");
+        setTimeout(recursive,1000);
+    }
+    recursive();
+
+As you can see, it makes a call to the `recursive` function which, as it completes, makes a call to `setTimeout(recursive, 1000)` which makes it call `recursive` again in 1 second - thus having near the same effect as setInterval while being resilient to the unintended errors that can pile up.
+
+You can clear the timers you set with `clearTimeout` and `clearInterval`. Their usages are very simple:
+
+    function never_call () {
+      console.log("You should never call this function");
+    }
+
+    var id1 = setTimeout(never_call,1000);
+    var id2 = setInterval(never_call,1000);
+
+    clearTimeout(id1);
+    clearInterval(id2);
+
+So if you keep track of the return values of the timers, you can easily unhook the timers. 
+
+The final trick for the timer objects is you can pass parameters to the callback by passing more parameters to setTimeout and setInterval:
+
+    setTimeout(console.log, 1000, "This", "has", 4, "parameters");
+    setInterval(console.log, 1000, "This only has one");
+
+
+    This has 4 parameters
+    This only has one
+    This only has one
+    This only has one
+    This only has one
+    This only has one
+    ...
diff --git a/locale/uk/knowledge/javascript-conventions/what-are-truthy-and-falsy-values.md b/locale/uk/knowledge/javascript-conventions/what-are-truthy-and-falsy-values.md
new file mode 100755
index 0000000000000..15233b4e0f791
--- /dev/null
+++ b/locale/uk/knowledge/javascript-conventions/what-are-truthy-and-falsy-values.md
@@ -0,0 +1,74 @@
+---
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - truthy
+  - falsy
+  - types
+  - coercion
+title: 'What are &quot;truthy&quot; and &quot;falsy&quot; values?'
+difficulty: 4
+layout: knowledge-post.hbs
+---
+
+
+Javascript is weakly typed language. That means different types can be
+used in operations and the language will try to convert the types
+until the operation makes sense.
+
+    console.log("1" > 0); // true, "1" converted to number
+    console.log(1 + "1"); // 11, 1 converted to string
+
+Type conversion also applys when values are used in unary boolean
+operations, most notably if statements. If a value converts to the
+boolean true, then it is said to be "truthy". If it converts to false
+it is "falsy".
+
+    var myval = "value";
+    if(myval) {
+      console.log("This value is truthy");
+    }
+    
+    myval = 0;
+    if(!myval) {
+      console.log("This value is falsy");
+    }
+
+Since most values in javascript are truthy, e.g. objects, arrays, most
+numbers and strings, it's easier to identify all of the falsy
+values. These are:
+
+    false // obviously
+    0     // The only falsy number
+    ""    // the empty string
+    null
+    undefined
+    NaN
+    
+Note that all objects and arrays are truthy, even empty ones.
+
+Truthiness and Falsiness also come into play with logical
+operators. When using logical AND/OR, the values will be converted
+based on truthiness or falsyness and then the expression will resolve
+to the last truthy value. Short circuit rules apply. Here's an
+extended example.
+
+    var first = "truthy"
+      , second = "also truthy";
+
+    var myvalue = first && second;
+    console.log(myvalue); // "also truthy"
+
+    first = null;
+    second = "truthy";
+
+    myvalue = first || second;
+    console.log(myvalue); // "truthy"
+
+    myvalue2 = second || first;
+    console.log(myvalue2); // "truthy"
+
+    var truthy = "truthy"
+      , falsy = 0;
+
+    myvalue = truthy ? true : false;
+    myvalue = falsy ? true : false;
diff --git a/locale/uk/knowledge/javascript-conventions/what-is-json.md b/locale/uk/knowledge/javascript-conventions/what-is-json.md
new file mode 100755
index 0000000000000..5cf2a033ac112
--- /dev/null
+++ b/locale/uk/knowledge/javascript-conventions/what-is-json.md
@@ -0,0 +1,126 @@
+---
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - json
+  - stringify
+  - parse
+title: What is JSON?
+difficulty: 5
+layout: knowledge-post.hbs
+---
+
+JavaScript Object Notation, or JSON, is a lightweight data format that
+has become the defacto standard for the web. JSON can be represented
+as either a list of values, e.g. an Array, or a hash of properties and
+values, e.g. an Object.
+
+    // a JSON array
+    ["one", "two", "three"]
+
+    // a JSON object
+    { "one": 1, "two": 2, "three": 3 }
+
+## Encoding and Decoding
+
+Javascript provides 2 methods for encoding data structures to json and
+encoding json back to javascript objects and arrays. They are both
+available on the `JSON` object that is available in the global scope.
+
+`JSON.stringify` takes a javascript object or array and returns a
+serialized string in the JSON format.
+
+    var data = {
+      name: "John Doe"
+      , age: 32
+      , title: "Vice President of JavaScript"
+    }
+
+    var jsonStr = JSON.stringify(data);
+
+    console.log(jsonStr);
+
+    // prints '{"name":"John Doe","age":32,"title":"Vice President of JavaScript"}'
+
+`JSON.parse` takes a JSON string and decodes it to a javascript data
+structure.
+
+    var jsonStr = '{"name":"John Doe","age":32,"title":"Vice President of JavaScript"}';
+
+    var data = JSON.parse(jsonStr);
+
+    console.log(data.title);
+
+    // prints 'Vice President of JavaScript'
+
+## What is valid JSON?
+
+There are a few rules to remember when dealing with data in JSON
+format. There are several gotchas that can produce invalid JSON as well.
+
+* Empty objects and arrays are okay
+* Strings can contain any unicode character, this includes object properties
+* `null` is a valid JSON value on it's own
+* All object properties should always be double quoted
+* Object property values must be one of the following: String, Number, Boolean, Object, Array, null
+* Number values must be in decimal format, no octal or hex representations
+* Trailing commas on arrays are not allowed
+
+These are all examples of valid JSON.
+
+    {"name":"John Doe","age":32,"title":"Vice President of JavaScript"}
+
+    ["one", "two", "three"]
+
+    // nesting valid values is okay
+    {"names": ["John Doe", "Jane Doe"] }
+     
+    [ { "name": "John Doe"}, {"name": "Jane Doe"} ]
+
+    {} // empty hash
+
+    [] // empty list
+
+    null
+
+    { "key": "\uFDD0" } // unicode escape codes
+
+These are all examples of bad JSON formatting.
+
+    { name: "John Doe", 'age': 32 } // name and age should be in double quotes
+
+    [32, 64, 128, 0xFFF] // hex numbers are not allowed
+
+    { "name": "John Doe", age: undefined } // undefined is an invalid value
+
+    // functions and dates are not allowed
+    { "name": "John Doe"
+      , "birthday": new Date('Fri, 26 Aug 2011 07:13:10 GMT')
+      , "getName": function() {
+          return this.name;
+      }
+    }
+
+Calling `JSON.parse` with an invalid JSON string will result in a
+SyntaxError being thrown. If you are not sure of the validity of your
+JSON data, you can anticipate errors by wrapping the call in a
+try/catch block.
+
+Notice that the only complex values allowed in JSON are objects and
+arrays. Functions, dates and other types are excluded. This may not
+seem to make sense at first. But remember that JSON is a data format,
+not a format for transfering complex javascript objects along with
+their functionality.
+
+## JSON in other languages
+
+Although JSON was inspired by the simplicity of javascript data
+structures, it's use is not limited to the javascript language. Many
+other languages have methods of transfering native hashes and lists
+into stringified JSON objects. Here's a quick example in ruby.
+
+    require 'json'
+
+    data = { :one => 1 }
+    puts data.to_json
+
+    # prints "{ \"one\": 1 }"
diff --git a/locale/uk/knowledge/javascript-conventions/what-is-the-arguments-object.md b/locale/uk/knowledge/javascript-conventions/what-is-the-arguments-object.md
new file mode 100755
index 0000000000000..2f6bde9db5261
--- /dev/null
+++ b/locale/uk/knowledge/javascript-conventions/what-is-the-arguments-object.md
@@ -0,0 +1,64 @@
+---
+date: '2011-08-26T10:08:50.000Z'
+tags:
+  - truthy
+  - falsy
+  - types
+  - coercion
+title: What is the arguments object?
+difficulty: 4
+layout: knowledge-post.hbs
+---
+
+The `arguments` object is a special construct available inside all
+function calls. It represents the list of arguments that were passed
+in when invoking the function. Since javascript allows functions to be
+called with any number args, we need a way to dynamically discover and
+access them.
+
+The `arguments` object is an array-like object. It has a length
+property that corresponds to the number of arguments passed into the
+function. You can access these values by indexing into the array,
+e.g. `arguments[0]` is the first argument. The only other standard
+property of `arguments` is callee. This always refers to the function
+currently being executed. Here's an example that illustrates the
+properties of `arguments`.
+
+    var myfunc = function(one) {
+      arguments.callee === myfunc;
+      arguments[0] === one;
+      arguments[1] === 2;
+      arguments.length === 3;
+    }
+
+    myfunc(1, 2, 3);
+
+This construct is very useful and gives javascript functions a lot of
+flexibility. But there is an important gotcha. The `arguments` object
+behaves like an array, but it is not an actual array. It does not have
+Array in its prototype chain and it does not respond to any array
+methods, e.g. `arguments.sort()` raises a TypeError. Instead you need to
+copy the values into a true array first. Since a normal for loop
+works, this is pretty easy.
+
+    var args = [];
+    for(var i = 0; i < arguments.length; i++) {
+      args.push(arguments[i]);
+    }
+
+In certain cases you can still treat `arguments` as an array. You can
+use `arguments` in dynamic function invocations using apply. And most
+native Array methods will also accept `arguments` when dynamically
+invoked using call or apply. This technique also suggests another way
+to convert `arguments` into a true array using the Array#slice method.
+
+    myfunc.apply(obj, arguments).
+
+    // concat arguments onto the 
+    Array.prototype.concat.apply([1,2,3], arguments).
+
+    // turn arguments into a true array
+    var args = Array.prototype.slice.call(arguments);
+
+    // cut out first argument
+    args = Array.prototype.slice.call(arguments, 1);
diff --git a/locale/uk/knowledge/other-resources/tutorials-and-how-tos.md b/locale/uk/knowledge/other-resources/tutorials-and-how-tos.md
new file mode 100755
index 0000000000000..6eec2ce73fed7
--- /dev/null
+++ b/locale/uk/knowledge/other-resources/tutorials-and-how-tos.md
@@ -0,0 +1,30 @@
+---
+title: Tutorials and How-Tos
+date: '2011-09-15T23:04:37.000Z'
+tags:
+  - help
+  - resources
+difficulty: 1
+layout: knowledge-post.hbs
+---
+
+## [Nodejitsu Blog](http://blog.nodejitsu.com)
+
+Nodejitsu's developers blog regularly about how to use node.js libraries, best practices *and* community news!
+
+## [How To Node](http://howtonode.org)
+
+How To Node is a community-driven blog with lots of node.js tutorials, complete with code snippets.
+
+## [The Node Beginner Book](http://nodebeginner.org/)
+
+The Node Beginner Book is a free book that teaches how to program with javascript and node.js by having the reader build a fully-functional bare-bones web application.
+
+## [Node.js Guide](http://nodeguide.com/)
+
+Felix Geisendörfer, one of the very first people to use Node in production, assembled an unofficial guide not only on writing node apps, but also on coding style, the Node community and on convincing the boss.
+
+## [Node Tuts](http://nodetuts.com/)
+
+Not only does Node Tuts have nearly two dozen screencasts on node, it also is the home of the e-book "Hands-On Node.js"!
+
diff --git a/locale/uk/security.md b/locale/uk/security.md
new file mode 100755
index 0000000000000..bc573b9c7192c
--- /dev/null
+++ b/locale/uk/security.md
@@ -0,0 +1,48 @@
+---
+layout: security.hbs
+title: Безпека
+---
+# Безпека
+
+## Повідомлення про помилки
+
+Всі помилки, що стосуються безпеки в Node.js, серйозно беруться до уваги і повинні бути надіслані на [security@nodejs.org](mailto:security@nodejs.org).
+Вони будуть передані відповідній підгрупі, яка займається питаннями безпеки.
+
+Ваш лист буде розглянуто протягом 24 годин, а протягом 48–и годин вам буде надіслано більш деталізовану відповідь з вказівками щодо подальшої обробки вашого запиту.
+
+Після першої відповіді на ваше повідомлення, команда безпеки буде тримати вас в курсі стосовно прогресу у вирішенні проблеми та може запитати вас додаткову інформацію, або інструкції стосовно повідомленої помилки.
+Ці оновлення будуть надсилатись принаймні раз в п’ять днів, на практиці, скоріш за все, кожні 24-48 годин.
+
+Проблеми з безпекою в модулях сторонніх розробників повинні повідомлятись їхнім мейнтейнерам, а також можуть бути зкоординовані через [Node Security Project](https://nodesecurity.io).
+
+Дякуємо вам, за покращення безпеки в Node.js. Ваші зусилля та відповідальність високо цінуються та будуть визнаними.
+
+
+## Розкриття політики
+
+Ось політика розкриття безпеки для Node.js
+
+- Звіт про безпеку приймається і назначається основному обробнику. Ця людина координуватиме процес виправлення та релізу. Список всіх версій визначиться тоді, коли підтвердиться проблема, яку вони містять в собі. Код перевіряється для знаходження потенційних подібних проблем. Виправлення готуються для всіх релізів, що досі підтримуються. Ці виправлення не приймаються в публічний репозиторій, а скоріше зберігаються локально в очікуванні анонсу.
+
+- Обирається дата закриття цієї вразливості і стосовно неї запитується CVE (Common Vulnerabilities and Exposures (CVE®)).
+
+- У день закриття, поштове розсилання стосовно безпеки Node.js розсилає копії анонсу. Зміни передаються у публічний репозиторій і нові збірки розгортаються на nodejs.org. Протягом 6 годин після розсилки повідомлень, копію оголошення буде опубліковано у блозі Node.js.
+
+- Зазвичай дата закриття встановлюється протягом  72 годин від отримання CVE. Однак, це може залежати від серйозності помилки та складнощів стосовно її вирішення.
+
+- Цей процес може зайняти деякий час, особливо коли необхідна координація з мейнтейнерами інших проектів. Всі зусилля будуть спрямовані на те, щоб вирішити проблему настільки швидко, наскільки це можливо, однак, важливо, щоб ми дотримувались процесу релізу, щоб бути певними, що все відбувається належним чином.
+
+
+## Отримання оновлень безпеки
+
+Сповіщення, що стосуються безпеки, будуть поширюватись за допомогою:
+
+- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec)
+- [https://nodejs.org/en/blog](https://nodejs.org/en/blog)
+
+
+## Коментарі стосовно цієї політики
+
+Якщо ви маєте поради щодо вдосконалення цього процесу, будь ласка, надішліть [pull request](https://github.com/nodejs/nodejs.org)
+або напишіть лист на  [security@nodejs.org](mailto:security@nodejs.org).
diff --git a/locale/uk/site.json b/locale/uk/site.json
new file mode 100755
index 0000000000000..64a69d2d9969e
--- /dev/null
+++ b/locale/uk/site.json
@@ -0,0 +1,165 @@
+{
+    "title": "Node.js",
+    "author": "Node.js Foundation",
+    "url": "https://nodejs.org/uk/",
+    "locale": "uk",
+    "scrollToTop": "Вгору",
+    "reportNodeIssue": "Проблеми з Node.js",
+    "reportWebsiteIssue": "Проблеми з сайтом",
+    "getHelpIssue": "Допомога",
+    "by": "від",
+    "all-downloads": "Всі варіанти завантажень",
+    "nightly": "Нічні збірки",
+    "feeds": [
+        {
+            "link": "feed/blog.xml",
+            "text": "Блог Node.js"
+        },
+        {
+            "link": "feed/releases.xml",
+            "text": "Блог Node.js: Релізи"
+        },
+        {
+            "link": "feed/vulnerability.xml",
+            "text": "Node.js Blog: Звіти про вразливості"
+        },
+        {
+            "link": "feed/tsc-minutes.xml",
+            "text": "Протоколи засідання Node.js TSC"
+        }
+    ],
+    "home": { "text": "Головна" },
+    "about": {
+        "link": "about",
+        "text": "Про проект",
+        "governance": {
+            "link": "about/governance",
+            "text": "Управління"
+        },
+        "workinggroups": {
+            "link": "about/working-groups",
+            "text": "Робочі групи"
+        },
+        "releases": {
+            "link": "about/releases",
+            "text": "Релізи"
+        },
+        "resources": {
+            "link": "about/resources",
+            "text": "Ресурси"
+        },
+        "foundation": {
+            "link": "foundation",
+            "text": "Фундація"
+        },
+        "security": {
+            "link": "security",
+            "text": "Безпека"
+        },
+        "trademark": {
+            "link": "about/trademark",
+            "text": "Товарний знак"
+        }
+    },
+    "download": {
+        "link": "download",
+        "text": "Завантаження",
+        "releases": {
+            "link": "download/releases",
+            "text": "Попередні Релізи"
+        },
+        "package-manager": {
+            "link": "download/package-manager",
+            "text": "Встановлення Node.js через пакетний менеджер"
+        }
+    },
+    "docs": {
+        "link": "docs",
+        "text": "Документація",
+        "es6": {
+            "link": "docs/es6",
+            "text": "ES6 і вище"
+        },
+        "faq": {
+            "link": "docs/faq",
+            "text": "FAQ"
+        },
+        "api-lts": {
+            "link": "/dist/latest-v4.x/docs/api",
+            "subtext": "LTS",
+            "text": "%ver% API"
+        },
+        "api-current": {
+            "link": "/dist/latest-v6.x/docs/api",
+            "text": "%ver% API"
+        },
+        "guides": {
+            "link": "docs/guides",
+            "text": "Керівництва"
+        }
+    },
+    "foundation": {
+        "link": "foundation",
+        "text": "Фундація",
+        "casestudies": {
+            "link": "foundation/case-studies",
+            "text": "Ресурси"
+        },
+        "members": {
+            "link": "foundation/members",
+            "text": "Учасники"
+        },
+        "board": {
+            "link": "foundation/board",
+            "text": "Рада директорів"
+        },
+        "tsc": {
+            "link": "foundation/tsc",
+            "text": "Технічне керівництво"
+        },
+        "itn": {
+             "link": "foundation/in-the-news",
+             "text": "У новинах"
+        },
+        "announce": {
+            "link": "foundation/announcements",
+            "text": "Анонси"
+        }
+    },
+    "getinvolved": {
+        "link": "get-involved",
+        "text": "Приєднатись",
+        "code-and-learn": {
+            "link": "get-involved/code-and-learn",
+            "text": "Code + Learn"
+        },
+        "contribute": {
+            "link": "get-involved/contribute",
+            "text": "Сприяння"
+        },
+        "development": {
+            "link": "get-involved/development",
+            "text": "Розробка"
+        },
+        "events": {
+          "link": "get-involved/events",
+          "text": "Події"
+        },
+        "conduct": {
+            "link": "https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-of-conduct",
+            "text": "Правила"
+        }
+    },
+    "security"   : { "link": "security",        "text": "Безпека" },
+    "blog"       : { "link": "blog",            "text": "Новини" },
+
+    "releases": {
+        "title": "Історія релізів",
+        "downloads": "Завантаження"
+    },
+    "links": {
+        "pages": {
+            "changelog": "Список змін"
+        }
+    }
+}
diff --git a/locale/uk/styles.styl b/locale/uk/styles.styl
new file mode 100755
index 0000000000000..1eb060f320a76
--- /dev/null
+++ b/locale/uk/styles.styl
@@ -0,0 +1 @@
+@import 'base'