Open source China global exclusive benefits, computing conference ticket rebate! >>>  

Ayo (pronounced “eye-oh” or IO) is an offshoot of the currently popular JavaScript runtime Node.js. It was created as a result of a “Code of Conduct” issue within the Node.js project.

A Node.js project committee (TSC) voted on whether a Node.js developer should be allowed to continue working on the project, and the vote was 60% in favor. The vote was taken because of a number of “code of conduct” violations by the developer. In fact, the vote means they take this “code of conduct” seriously.

Unfortunately, as Twitter user MaybeKatz pointed out, if committee members vote to keep developers working on the project, it makes the “code of conduct” look unenforceable.

And now the lack of enforcement of the “code of conduct” has led not only to the bifurcation of Node.js, but also to the resignation of a Node.js committee member from the TSC.

Here’s what the developer had to say:

A recent decision by TSC leads me to believe that the technical Steering Committee is making decisions that are not in the best interest of the Node.js project. It’s not just about a specific individual, it’s about the responsibilities that we take on as a project, it’s about the values that we choose to present to others.

TSC has ultimate authority over the project and includes:

  • Technical direction

  • Project governance and procedures (including this Rule)

  • Detailed rules for the contribution

  • GitHub repository hosting

  • Code of conduct

  • Maintains a list of additional collaborators

The current decision undermines our “code of conduct” and, in my view, not only drives away potential contributors but also undermines the commission’s ability to govern.

Pushing out contributors to open source projects can be a fatal move in the open source world, given that most developers basically volunteer to contribute to projects in their free time. Attracting contributors to both small projects and large ones like Node.js can be difficult, so we need to make sure that all contributors are happy.

Open source projects should adopt a “code of conduct” because it makes contributors feel safe in contributing to the project and increases their courage in submitting patches. Contributors may be a little “shy” when they first join a project, but a “code of conduct” can help overcome this. It’s also a good idea to include a “contribution” document that explains how to contribute to the project and where to start. Anything that makes it easier for the public to contribute to open source projects is a good thing.

Update aug 23, 2017 11:26 am: Ayo.js discusses multiple issues on Github, including management structure and project goals.

One of the top responses to an issue about whether to merge back into Node.js was as follows:

I just hope the bug can be fixed. I don’t care what the project is called or who controls it, as long as it serves the community, it’s worth pushing forward.

Translation: sourcecontribute.com/