Then again, this doesn't seem anywhere near as crazy as the IO.js days.
Node.js is forked to Ayo.js (pronounced like “IO”)
61–70 of 150 posts
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#62Reasons for fork: "Repeated ToC violations by an authority figure went unaddressed." https://twitter.com/alicegoldfuss/status/900109726872068096 Not sure what ToC is, but the alleged violations appear to be of Code of Conduct. Alleged violations are described here: https://twitter.com/ohhoe/status/899748838302302212 Most links are private, but here are the public ones: https://twitter.com/rvagg/status/887652116524707…
Try working on an open source project for 5 years and then we can talk about altruism.
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#63Reasons for fork: "Repeated ToC violations by an authority figure went unaddressed." https://twitter.com/alicegoldfuss/status/900109726872068096 Not sure what ToC is, but the alleged violations appear to be of Code of Conduct. Alleged violations are described here: https://twitter.com/ohhoe/status/899748838302302212 Most links are private, but here are the public ones: https://twitter.com/rvagg/status/887652116524707…
What I see is a screenshot of a GitHub issue (https://twitter.com/ohhoe/status/899748838302302212) which was already redacted and does no longer provide any links. Tweet in support of "anti-CoC article" is there (https://twitter.com/rvagg/status/887652116524707841) but that alone would not assert a "harmful person" in my opinion.
I understand the fork is not on political reasons which may be very well grounded. But I don't think they are not explained to the public well enough. There must be a clear answer to "Why should I care?" but there is not. This will probably lead to ignorance and dismissal.
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#64Sounds like BS. Possibly relevant: Eric S. Raymond: Why Hackers Must Eject the SJWs (2015) http://esr.ibiblio.org/?p=6918
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#65That 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.
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: https://twitter.com/ohhoe/status/899748838302302212.
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#66Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#67Earlier quoted context omitted.
It is unclear. Seemed like he has repeatedly used a language that some community members found offensive. His stance against Code of Conduct, as evident by this Tweet: https://twitter.com/rvagg/status/887652116524707841 and follow up comments were considered inappropriate by some. Even more details here: https://github.com/nodejs/TSC/issues/310 """ The TSC members were not able to reach a natural consensus on the ste…
They had a vote to remove him, it failed. Move on!
I'm just wondering what would've happened if Rod was forced to resign and the other <50% voters who voted against it. Maybe a fork of NodeJS, but this time from Rod's fellows?
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#68Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#69Sounds like BS. Possibly relevant: Eric S. Raymond: Why Hackers Must Eject the SJWs (2015) http://esr.ibiblio.org/?p=6918
Good christ, I can't believe I'm responding to an ESR blog post, but this "djangoconcardiff" account joined Github [1] the same day every comment in that thread was posted… which was, by the way, months after the DjangoCon in Cardiff wrapped up. How do people not see that whole incident as the bad-faith troll that it clearly is? [1]: https://archive.is/UDFZt#selection-193.0-193.16
Re: Node.js is forked to Ayo.js (pronounced like “IO”)
#70What's the reason they forked/main difference from Node.js?
From an issue: > I'd be open to re-merging if and when the problems plaguing Node.js are resolved. Problematic people removed; use of "policy" as an excuse ended; power structures reorganized to emphasize community over tech. So far though it seems like there's little desire to fix these problems from those with the power to do so.