How to Change JavaScript

The JavaScript committee follows a well-defined, multi-stage process for considering proposals. This structured approach guides ideas from their initial conception through to their potential inclusion in the JavaScript standard.

The process moves an idea from being a mere concept to a final stage where it officially becomes a part of the JavaScript standard.

A proposal ultimately becomes an official part of the JavaScript standard. This integration is the final goal of the committee's rigorous review process, ensuring that new features are thoroughly vetted.

The public can participate by following discussions in GitHub repositories, which are maintained for every proposal. These repositories provide a transparent platform for tracking the evolution of potential JavaScript features.

The entire process is open and public, allowing anyone to follow and comment. The committee actively values feedback from the language community and developers, integrating it into their decision-making process.

If a developer has an idea for a new feature, they can convince a committee member to champion it. This sponsorship is crucial for the idea to be formally presented to the entire committee.

Once championed, the idea is presented to the full committee. If deemed interesting, the committee will consider it for further development.

The committee will consider a proposal if they find it interesting. For those serious about contributing to JavaScript, direct engagement with the committee is an option.

Joining the committee is not on an individual basis; only organizations can become members. An employer can join ECMA International, the standardization organization, to gain access to TC39.

An employer can join ECMA International, the standardization organization, to gain access to TC39. This membership allows organizations to participate directly in the JavaScript development process.

Member organizations can attend meetings and actively participate in technical decision-making. However, even without officially joining the committee, individuals can still contribute significantly.

Even without officially joining the committee, individuals can still contribute. For example, developers can write tests for the Test262 testing suite, which is a vital part of the development process.

Every proposal requires a completed testing suite, a mandatory step for a proposal to advance through the TC39 process. While not everyone enjoys writing tests, it is a highly valuable contribution.

Writing tests is a crucial and valuable contribution, essential for proposals to advance through the TC39 process. Despite some aversion to test writing, it is not as difficult as it might seem.

Mikhail Barash, from the University of Bergen in Norway, notes that writing tests is not difficult. He highlights that multiple students from his university have successfully written tests for JavaScript.

Students from the University of Bergen have become contributors to the JavaScript specification through their test-writing efforts. This demonstrates that even those new to the field can make meaningful contributions to the language.