To answer your question: no, I was not overruled -- it's been clear to me for quite some time that node.js would be best served by a foundation. That said, getting the mechanics of that foundation established has taking (is taking) a long time (and, it must be said, involves a lot of hard, thankless work from a lot of people). Foundations might feel "easy", but they aren't: 501(c)(3) organizations are highly regulated entities that require not just a lot of groundwork and forethought but extensive maintenance. Fortunately, we have made great progress (and we have built a terrific collection of founding members), and we are getting the node.js community what it needs: a foundation that can assure the consensus-driven advancement of the technology, in perpetuity.
[1] http://www.slideshare.net/bcantrill/corporate-open-source-an...
[2] http://www.youtube.com/watch?v=NhgXQFk9noI
[3] https://www.joyent.com/blog/sdc-and-manta-are-now-open-sourc...
Regardless of the event itself, that was an exceptionally poor handling (soapboxing?) of the situation, and didn't speak much of ability to mediate a heated situation. A foundation born from this management style? Doesn't sound encouraging.
http://www.zdnet.com/article/how-suns-need-to-control-the-code-cost-them-the-company/
or: http://www.cryptnet.net/mirrors/texts/kissedagirl.htmlIt's not so much to do with my opinion of the specifics of the situation with Noordhuis, or the announcement that is the object of this conversation, but rather the vaguer feeling that they feel way too much like a 'company' acting in its own interest for me to trust them.
This announcement feels like hurried back-room politics, and your reply is reinforcing that impression.
This is the closest entry I could find on his blog regarding node.js and its governance: http://dtrace.org/blogs/bmc/2014/06/11/broadening-nodejs/