Reasons for fork:<p>"Repeated ToC violations by an authority figure went unaddressed."<p><a href="https://twitter.com/alicegoldfuss/status/900109726872068096" rel="nofollow">https://twitter.com/alicegoldfuss/status/900109726872068096</a><p>Not sure what ToC is, but the alleged violations appear to be of Code of Conduct.<p>Alleged violations are described here: <a href="https://twitter.com/ohhoe/status/899748838302302212" rel="nofollow">https://twitter.com/ohhoe/status/899748838302302212</a><p>Most links are private, but here are the public ones:<p><a href="https://twitter.com/rvagg/status/887652116524707841" rel="nofollow">https://twitter.com/rvagg/status/887652116524707841</a><p><a href="https://twitter.com/rvagg/status/887790865766268928" rel="nofollow">https://twitter.com/rvagg/status/887790865766268928</a><p><a href="https://twitter.com/captainsafia/status/887782785221615618" rel="nofollow">https://twitter.com/captainsafia/status/887782785221615618</a><p><a href="https://twitter.com/nodebotanist/status/887724138516951049" rel="nofollow">https://twitter.com/nodebotanist/status/887724138516951049</a>
The way this fork has been presented clearly indicates this fork has no future.<p>If you indeed have problems with the way nodejs is run, the first thing you do with a fork is present it upfront in your fork, with some idea on how you're going to go forward. All you see here is one issue potentially discussing some bad policies or people. wishy washy.<p>And discussion in another thread is almost satirical -- discussing "lifetime" of a benevolent dictator "for life". [1]<p>There's no clear leadership or goals for this fork.<p>[1] <a href="https://github.com/ayojs/ayo/issues/2" rel="nofollow">https://github.com/ayojs/ayo/issues/2</a>
They're flipping out because of a tweet, and all it had was a link to an article against codes of conduct.<p>"Additionally he discussed private information from the moderation repo in the public thread, which is explicitly against he moderation policy".<p>I don't like such secrecy. What's going on in there? Wasn't community so important, why can't we know?<p>So what if that guy doesn't like CoCs? It is <i>fine</i> for people to have other opinions. This is another case of people over reacting over small stuff like it happened with Brendan Eich or Douglas Crockford.<p>Oh gee, some people need to chill out.
Line that stood out to me: "Rod retweeted in support of an inflammatory anti-Code-of-Conduct article"<p>If you're not 100% onboard with the politics, you're a horrible person.
The issues page says it all: <a href="https://github.com/ayojs/ayo/issues" rel="nofollow">https://github.com/ayojs/ayo/issues</a> . This is not a software project. There will be no actual code written.
I'm sick of all this <i>drama</i> that people create around this bullshit around <i>wrongthink</i> and the like.<p>Didn't they ever learn as kids sticks and stones may break my bones but names will never hurt me?<p>Surely, in OSS tons of people are going to have different opinions about many things, as long as they are respectful who cares what they think?<p>Seriously some people in this world need to eat a bag of concrete and harden the fuck up.
This is probably the best possible course of action at this stage, even if I'm extremely skeptical about the longevity of the fork. The ideal scenario is to compartmentalize people who can't get along, like you would in a workplace - having two separate forks that absorb each other's changes is not too far off from that.<p>There's another reason too; there's a theory going around that there's a sizable pool of potential competent contributors who are currently staying away from the Node.js project (and other projects) because they feel excluded (and this is commonly used as an argument as to why policies need to be changed). This fork is going to show whether that group of people really exists; if it does, then the fork will thrive, but if it does not, then it will die.<p>I don't think there's much to do about this now other than wait and see it play out. The results of this fork will become obvious soon enough, and it seems that this at least will get everybody off each other's backs for a while.<p>EDIT: Also, let's dial down the vitriol in this thread a little. There's no point in getting outraged over something that'll resolve itself.
Open a perfectly fine PR that fixes/accomplishes something but prefix PR comment with: "Hey guys,"<p>Sit back and watch as you're bombarded with threats and comments about being pro-rape, a straight white male and the like
Make sure you use proper [1] CoC next time you start new project. Proper as in not easy to abuse for political reason or just because some SJW decided you are wrong.<p>[1] <a href="https://github.com/fantasylandinst/fcop" rel="nofollow">https://github.com/fantasylandinst/fcop</a>
The more I code, the more I appreciate projects and languages that are not based on a democratic committee and have a consistent unique single minded vision.<p>I'd rather stick to a language/framework that aligns with my own preferences, than stick to one that tries to please to a large group of people.<p>I feel this is the major problem with Javascript, Node, etc.
For those asking what the reason of the fork is it looks like it has something to do with a code of conduct violation by one of the node developers that the steering committee voted to ignore. I have no idea what the story behind it as it doesn't seem like anyone has actually published the full story.<p>Regardless of the reason, this seems like a premature announcement of the project. There isn't a roadmap, list of distinguishing features, or the guiding principles. More information is definitly needed here.
Newest development: <a href="https://github.com/nodejs/board/issues/67" rel="nofollow">https://github.com/nodejs/board/issues/67</a><p>"We don't like the outcome, so we have to change the rules."
Please note that @ag_dubs that started the shit stirring after Rod's post sits on that board and was part of that decision.
Still we don't know what Rod did to her in the first place.
The previous fork was successful because a lot of the developers went with the fork and it was fulfilling an unserviced need in the community for a node built on newer versions of v8. Does anyone know if this fork has much of a chance of survival?
First: I like the name!<p>That said, it is a bit unfortunate to fork or at least to try to fork a project like Node.js over these reasons. Although it is quite likely that the fork was mainly created to pressure the Node-devs to remove rvagg from the project after all.<p>What puzzles me: Even if we agree that rvagg violated the Code of Conduct, I am not sure that this should be enough to remove him from the TSC (Technical Steering Committee). Here are the alleged violations, so that you can decide for yourself: <a href="https://twitter.com/ohhoe/status/899748838302302212" rel="nofollow">https://twitter.com/ohhoe/status/899748838302302212</a>.
Since the comments say this is probably due to political reasons, I feel like this fork would mean a lot more if it included contributions that were rejected by nodejs as well as a communitity of contributors to keep this fork active.
I've been clicking around on twitter and github for five minutes and there seems to be zero specifics about what actually happened.<p>What's with the secrecy? Not saying this is a non-issue, but the best way to present your issue as a non-issue is to be this vague about what you're complaining about.
Blog post: <a href="https://medium.com/@mylesborins/effective-immediately-i-am-stepping-down-from-the-nodejs-tsc-3df37c6ccbae" rel="nofollow">https://medium.com/@mylesborins/effective-immediately-i-am-s...</a>
Every time I see something about NodeJS, an image of a flaming dumpster overflowing with left-padded trash comes to mind.<p>I've never seen a technology deep sixed not by its technology, but by its politics and ideology.
Node.js can, of course, merge in any changes of merit that this fork produces. Especially since the fork isn't for technical reasons they are unlikely to diverge in fundamental ways... Atleast until the fork is abandoned entirely for providing no value over node.js -- especially if they don't keep up with the upstream progress.
> Humans are more important than APIs and Benchmarks.<p><a href="https://github.com/ayojs/ayo/blob/zkat/values/VALUES.md" rel="nofollow">https://github.com/ayojs/ayo/blob/zkat/values/VALUES.md</a>
Also related to this: <a href="https://medium.com/@mylesborins/effective-immediately-i-am-stepping-down-from-the-nodejs-tsc-3df37c6ccbae" rel="nofollow">https://medium.com/@mylesborins/effective-immediately-i-am-s...</a>
I have yet to find any good reason for this fork, but I wish the forkers all the best. If they can actually make something better, I'm sure we'll switch. Until then I see no reason to not support Node.
Sounds like BS.<p>Possibly relevant:<p>Eric S. Raymond: Why Hackers Must Eject the SJWs (2015)<p><a href="http://esr.ibiblio.org/?p=6918" rel="nofollow">http://esr.ibiblio.org/?p=6918</a>
He seems like a candidate for being a douchey provocateur. Tech-libertarian too?<p>It's hard enough having the JS community taken seriously with the zeitgeist framework changing too quickly.