Re: [nodejs] node.js and io.js reconciliation

On Wed, Dec 10, 2014 at 12:27 AM, Ryan Schmidt wrote: > > On Dec 9, 2014, at 1:09 PM, Matt wrote: > > > I highly recommend you subscribe to nodeweekly - it's a weekly roundup > of node news where you'll at least get to hear about this stuff. > > > > http://nodeweekly.com/ > > Done. I'll point out

Re: [nodejs] node.js and io.js reconciliation

On Dec 9, 2014, at 1:09 PM, Matt wrote: > I highly recommend you subscribe to nodeweekly - it's a weekly roundup of > node news where you'll at least get to hear about this stuff. > > http://nodeweekly.com/ Done. I'll point out that this, too, is a resource that has never been mentioned here

Re: [nodejs] node.js and io.js reconciliation

On Dec 9, 2014, at 2:09 PM, Matt wrote: > > Ravi, > > I highly recommend you subscribe to nodeweekly - it's a weekly roundup of > node news where you'll at least get to hear about this stuff. > > http://nodeweekly.com/ > Done! Thank you for sharing that, —ravi -- Job board: http

Re: [nodejs] node.js and io.js reconciliation

Joyent is already unhappy about all this. An "official" thread on here would probably not be well received, and iojs is trying really hard not to get on Joyent's bad side. On Dec 9, 2014 12:12 PM, "Dick Hardt" wrote: > +1 that significant events such as forking would have a post on this mail > li

Re: [nodejs] node.js and io.js reconciliation

Ravi, I highly recommend you subscribe to nodeweekly - it's a weekly roundup of node news where you'll at least get to hear about this stuff. http://nodeweekly.com/ On Tue, Dec 9, 2014 at 1:57 PM, // ravi wrote: > On Dec 9, 2014, at 1:36 PM, Stephen Belanger > wrote: > > > > The node communit

Re: [nodejs] node.js and io.js reconciliation

+1 that significant events such as forking would have a post on this mail list. On Tue, Dec 9, 2014 at 10:57 AM, // ravi wrote: > On Dec 9, 2014, at 1:36 PM, Stephen Belanger > wrote: > > > > The node community is huge. If everyone just communicated via the > mailing list, it'd be an unfollowab

Re: [nodejs] node.js and io.js reconciliation

On Dec 9, 2014, at 1:36 PM, Stephen Belanger wrote: > > The node community is huge. If everyone just communicated via the mailing > list, it'd be an unfollowable firehose of noise. > At the risk of belabouring the point: I somewhat agree, but then again, mailing lists are particularly well-s

Re: [nodejs] node.js and io.js reconciliation

The node community is huge. If everyone just communicated via the mailing list, it'd be an unfollowable firehose of noise. Between IRC and the mailing list, you can get most things. Twitter sometimes gets you early info about new stuff particular people are working on. Conferences are really effic

Re: [nodejs] node.js and io.js reconciliation

On Dec 9, 2014, at 9:02 AM, Aria Stewart wrote: > On 9 Dec 2014, at 04:26, Ryan Schmidt wrote: > >> How can there be "a broad community effort", how can there be "open >> collaboration", how can the "community step in and effectively solve the >> problems" if the existence of these efforts is

Re: [nodejs] node.js and io.js reconciliation

On Dec 9, 2014, at 10:02 AM, Aria Stewart wrote: >> On 9 Dec 2014, at 04:26, Ryan Schmidt wrote: >> >> How can there be "a broad community effort", how can there be "open >> collaboration", how can the "community step in and effectively solve the >> problems" if the existence of these efforts

Re: [nodejs] node.js and io.js reconciliation

> On 9 Dec 2014, at 04:26, Ryan Schmidt wrote: > > > How can there be "a broad community effort", how can there be "open > collaboration", how can the "community step in and effectively solve the > problems" if the existence of these efforts is not announced to the > community--this communit

Re: [nodejs] node.js and io.js reconciliation

I am subscribed to this discussion group in order to be connected with the community of other nodejs developers and to learn about important new developments affecting the nodejs community. I think having core nodejs contributors leave and start their own fork would qualify. On the Node Forward

Re: [nodejs] node.js and io.js reconciliation

On Dec 8, 2014, at 2:12 PM, Harald Hanche-Olsen wrote: > > And here is the original blog post that sparked the discussion. > > http://wesleyio.tumblr.com/post/104637877991/node-js-is-forked-not-f-ed > Where in we read: "Now, some people will scream about fragmentation”. People do not scream

Re: [nodejs] node.js and io.js reconciliation

Here is the forking issue being discussed on Hacker News: https://news.ycombinator.com/item?id=8716966 And here is the original blog post that sparked the discussion. http://wesleyio.tumblr.com/post/104637877991/node-js-is-forked-not-f-ed I, for one, breathe a little easier now that these

Re: [nodejs] node.js and io.js reconciliation

I appreciate your detailed response Forrest. Perhaps it would also help to clarify what to expect and where to go for help. Example: Use: * joyent/node GitHub issues for confirmed bugs in Node core * This list for discussion of general Node issues, technical and otherwise * Gitter for quick on

Re: [nodejs] node.js and io.js reconciliation

Thanks for your response. I'll keep waiting what happens in the next weeks, hoping all of this comes with a solution that is satisfactory for everyone. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: htt

Re: [nodejs] node.js and io.js reconciliation

I can shed a little more light on what’s going on. Keep in mind that while I work for a company (npm, Inc.) that has someone in the middle of a lot of the discussions around Node’s governance, and while I’m connected in various ways to both node-forward and io.js, I’m not a member of the Node core

Re: [nodejs] node.js and io.js reconciliation

On Dec 5, 2014, at 11:46 PM, Boris Matos Morillo wrote: > > First of all I would like to quote an article I read on the official blog of > node.js: "Listening to the Community", after reading this I decided to write > this. > > In these last days appeared a fork of nodejs called iojs, which lo

Re: [nodejs] node.js and io.js reconciliation

On Dec 6, 2014, at 12:04 AM, // ravi wrote: > > It’s the “apparently”s that bother me. I feel like one among the proverbial > blind men trying to figure out an elephant. The blog post you linked to > suggests comments be posted to this list, but the blog post (or its contents) > itself was not

[nodejs] node.js and io.js reconciliation

First of all I would like to quote an article I read on the official blog of node.js: "Listening to the Community ", after reading this I decided to write this. In these last days appeared a fork of nodejs called iojs, which looked