From ecec0697df948418a07e69ad767b89c8fa6d270c Mon Sep 17 00:00:00 2001 From: Hans Kristian Flaatten Date: Tue, 9 Aug 2016 21:28:05 +0200 Subject: [PATCH] wip --- .../2016-06-26-open-open-source-with-node.md | 64 +++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 _posts/2016-06-26-open-open-source-with-node.md diff --git a/_posts/2016-06-26-open-open-source-with-node.md b/_posts/2016-06-26-open-open-source-with-node.md new file mode 100644 index 0000000..c7e2d8d --- /dev/null +++ b/_posts/2016-06-26-open-open-source-with-node.md @@ -0,0 +1,64 @@ +--- +layout: post +title: Open Open Source with Node.js +date: 2016-06-26 +tag: [rand] +twitter: starefossen +published: true +--- + +Node has become one of the biggest success stories and failures of open source. +In January of 2014 a bounch of active contributors to the Node.js project became +increasingly conserned about the decrease in contibutors and new realses of Node.js. + +At this time Node.js was run by Joyent with the BDFL model. A the concerned +contributors asked Joyent if they (the community) could take over Node.js and +started a process. It was rocky and a bit up and down. Joyent got a new CEO, +Scot Hammond, and he got involved and built out an Advicory Board. + +But the progress slow and involved a bounch of involved companies getting +together in a room and trying to solve the various problems. The big probelm +with this process was that the open source contributors of the open source +community was left out and was not not in a positition to fix the problem with +Node.js slowing down. Having a room full of companies does not fix that. + +Around the same time as the Node.js Avisory Board was fomalized a project named +Node Forward was initiated. Node Forward would try to formalize and galvanize +some of the problems around some of the higher level problems of Node.js. For a +short time there was a fork of Node.js landing patches. Node Forward was +informed by Joyent (who owned the trademarks to Node.js) that the fork was a +trade mark violation whiched forces Node Forward to make the fork private. + +Fedor Indutny (a core contributor to Node.js and a member of the Node Forward) +pushed the fork button on GitHub and renamed the fork io.js which would not +infringe on the Node.js trademark. Within a short period of time the rest of the +active contributors moved to the io.js fork, except for those emplyed by Joyent ofcours. + +

+ January saw @official_iojs + clock the 3rd highest # of commits/month in the Node codebase @ 294. Beaten by + Feb-2012 @ 308 & Aug-2011 @ 307.

— Rod Vagg (@rvagg) 3. februar 2015 +

+ + +

+ In a single day we've built a 27 language 146 person localizations effort. + This is truly amazing. What a community!

— io.js (@official_iojs) 8. februar + 2015 +

+ + +2015-01-14 - io.js v1.0.0 released +2015-01-27 - Travis.ci io.js support +2015-02-03 - Atom switches to io.js +2015-02-05 - Codeship io.js support + +https://medium.com/@mikeal/65e5b1c49a62 +https://medium.com/@mikeal/2b3094e6f923 +https://hueniverse.com/2014/12/04/before-the-drama/ + +https://twitter.com/mikeal/status/560920566761537536 +https://twitter.com/mikeal/status/540587547978891265 +https://twitter.com/rvagg/status/562426788844818433