Slashdot: Node.js Forked Again Over Complaints of Unresponsive Leadership

Node.js Forked Again Over Complaints of Unresponsive Leadership
Published on August 24, 2017 at 12:40PM
New submitter Kant shares a report: The codebase for popular Node.js JavaScript runtime has been forked again — the second time in less than three years — with a growing number of contributors charging that the Technical Steering Committee (TSC) leadership is ignoring repeated violations of the project’s code of conduct. The new project, called Ayo will be managed under an open governance model. The complaints centered around ongoing behavior of NodeSource Director of Engineering, and Node.js TSC member Rod Vagg. The TSC received multiple complaints from Node.js members about a Tweet from Vagg promoting a Men’s Rights Activist-slanted article, one that cast doubt on the validity of project Code-of-Conducts. In that Tweet, Vagg commented “If you’ve never considered the potential downsides of codes of conduct, here’s a good place to start.” […] On August 21, The TSC voted on whether or not to remove Vagg from its ranks. Of the 10 TSC members who voted, 60 percent voted against removing Rod from the TSC and 60 percent voted against asking Rod to voluntarily resign. That the TSC voted to keep Vagg on the committee inflamed others in the project. One committee member, Myles Borins, resigned in protest. The decision to keep Vagg “undermines our Conduct Guidelines, drives away potential contributors, and in my opinion undermines the Committee’s ability to govern,” he wrote in a blog post. In a post further explaining the need for the forked Ayo project, developer Rudolf Olah explained that “Driving away contributors can be fatal in the open source world where most developers are essentially using their free time and volunteering to contribute. It is already difficult enough to attract contributors to smaller projects and larger projects, such as Node.js, need to be careful to make all contributors feel welcome.”