It's insane that we might reach a point where people install different branches of a project based on their political leanings... I think the main takeaway here is that a Code of Conduct, while valuable, has to be treated carefully. A lot of these projects agreed to a Code of Conduct just to appease a certain faction of their devs, and are now seeing that it can be used against them.
Rod Vagg's statement on the request to be removed from the Node.js CTC
21–30 of 186 posts
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#22Are long-winded quarrels and dysfunctions unique to node core, or is node core just transparent in documenting the making of the sausage?
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#23This, to me, is one of the most important lines of his response. I feel like critiques of CoCs and other related documents and processes coming from a white male are often interpreted as hostile. I would consider myself an ally, but I am afraid to weigh in on these kinds of discussions because differing opinions are so often manipulated into "hate" and "toxicity."
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#24Earlier quoted context omitted.
While the snark of this comment may push it into obscurity by those who hate snarky comments, I totally agree. I was surprised we could even still have Node.js after the huge Node.js vs io.js debacle. I think all of these arguments are about important issues, but they also can give a very negative impression to outsiders (not to mention how insiders aware of all the facts may feel). That said, I am at least happy to…
The Node.js vs io.js fork changed the way many looked at node and probably changed its growth axis. This is not the same and highlights why a code of conduct focusing on moral issues is not always the best path for a project/language.
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#25> I have submitted myself to our Code of Conduct as a participant in this project. I have been involved in the application of our Code of Conduct. But I do not accept it as a sacred text that is above critique or even discussion. This, to me, is one of the most important lines of his response. I feel like critiques of CoCs and other related documents and processes coming from a white male are often interpreted as hos…
At what point do we stop ignoring this inconvenient truth?
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#26It's insane that we might reach a point where people install different branches of a project based on their political leanings... I think the main takeaway here is that a Code of Conduct, while valuable, has to be treated carefully. A lot of these projects agreed to a Code of Conduct just to appease a certain faction of their devs, and are now seeing that it can be used against them.
There is absolutely no evidence that this fork will gain traction, because it contributes nothing new technically, so it's unlikely we'll reach the point you mention.
There is no doubt that this fork is future of server-side JS.
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#27Does anyone have a TLDR about this story? I haven't had the time to follow all the drama.
Given the types of complaints and their subjective nature in some instances, I imagine you're probably looking at something close to 4-5 hours at least to get enough context to form an objective opinion of your own on this situation if you aren't coming into it with that background knowledge already. I'm not willing to invest that.
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#28It's insane that we might reach a point where people install different branches of a project based on their political leanings... I think the main takeaway here is that a Code of Conduct, while valuable, has to be treated carefully. A lot of these projects agreed to a Code of Conduct just to appease a certain faction of their devs, and are now seeing that it can be used against them.
There is absolutely no evidence that this fork will gain traction, because it contributes nothing new technically, so it's unlikely we'll reach the point you mention.
Also, several members of their ruling committee left to make the fork. So it's not just a bunch of randoms, and they might be able to make some meaningful progress on their own.
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#29Shame how such a cool project as node.js can drown in political fingerpointing. The only measurement that counts (in my opinion) is cold hard code contributions.
"Cold hard code" contributions are an option available to anyone who feels comfortable with donating their labor under an opaque pseudonym. It's a good way to proactively shield oneself from disputes of this nature. It's a natural continuation of the quip "On the Internet, nobody knows you're a dog" -- except if you tell everyone you're a dog. Plenty of people contribute to collaborative projects solely on the merit of their contributions, even as many projects have come to follow the trend of considering other factors as well [1].
Re: Rod Vagg's statement on the request to be removed from the Node.js CTC
#30A bit of a thought experiment for myself: suppose that Rod were as terrible as the worst possible claims made against him. (I am confident he's not.) Suppose he were actively, consciously hoping to deceive and harm the Node community. (I am also confident he's not.) What sort of statement would he write? How much would it look like this one?
This has been happening more and more recently, both online and in geopolitics.