Nvm will **not** be adding support for Ayo.js
1–10 of 16 posts
Re: Nvm will **not** be adding support for Ayo.js
#2Can someone recap (or link to) the whole story behind the fork ?
Re: Nvm will **not** be adding support for Ayo.js
#3Can someone recap (or link to) the whole story behind the fork ?
https://github.com/nodejs/CTC/issues/165
I assume that they forked because they don't believe Rod should be on the node leadership teams.
Re: Nvm will **not** be adding support for Ayo.js
#4Oh no... what ever will all the memers and dreamers over at github.com/ayojs do with their political science project now.
From the makers of cringeworthy tumblrs, tune in next quarter for the next embarrassing episode of the hit millenial sitcom, "Are we enterprise yet?: The node.js/npm.js story",
Re: Nvm will **not** be adding support for Ayo.js
#5Looking at the forked repo all they did was rename node to ayo and add a VALUES.md with very little substance. Looks like a power grab by a bunch of control freaks to me.
At least io.js had some technical merit and seemed to genuinely want to improve node (which arguably it did).
Re: Nvm will **not** be adding support for Ayo.js
#6Maybe now we've got goddam, real, actual Nazis to worry about people can stop expending effort in creating straw nazis out of thin air.
Bigger fish to fry, people...
Re: Nvm will **not** be adding support for Ayo.js
#7> I'm not going to add support for a fork lightly; I don't think this will stick; and I don't think a fork is an appropriate or well-timed response to what's been happening. Either way, I wouldn't add support for a fork that adds nothing but a partial documentation commit - that has value for nobody.
I appreciate this straightforward and honest response to this issue. The responder has looked at the benefits of the fork and decided that it doesn't make sense to add it.
Re: Nvm will **not** be adding support for Ayo.js
#8Can we just let Ayo.js die in the obscurity it has an deserves and not encourage this sort of politics?
Re: Nvm will **not** be adding support for Ayo.js
#9Can someone recap (or link to) the whole story behind the fork ?
https://github.com/nodejs/CTC/issues/165 I assume that they forked because they don't believe Rod should be on the node leadership teams.
I must say that he has represented and defended himself very well here, and as a newcomer to this issue I am impressed with his analysis. However if it was possible to turn against him for what I understand to be such small accusations, such as simply disagreeing with one usage of CoCs in a particular setting, how might the project deal with a member who argues against code of conducts in general? Or how about the Node code of conduct?
It does not seem fair to me to exclude someone beacuse they are engaging in the process of discussion about a project policy, even if that policy is a touchy subject like the code of conduct. If there is nobody to debate such policies because they are immediately shoved out the second that they do, does that not say something about the policy being questioned too?
Re: Nvm will **not** be adding support for Ayo.js
#10Can someone recap (or link to) the whole story behind the fork ?
Some person's feelings were hurt, and they went "I'll show you all" mode.