They're not written down anywhere, and they change based on the makeup of the committee.
However, in general, the wider committee strives to avoid complexity, and absolutely will demand a justification for adding anything to JavaScript, including for changing the *process by which changes are made* to JavaScript. https://github.com/tc39/proposals is the list of current proposals, https://tc39.github.io/process-document/ describes the stage process, and https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md describes how one can contribute. I strongly encourage thorough familiarization with all those documents, including the spec/language itself, if you want to increase the effectiveness of a proposal. On Sat, May 12, 2018 at 10:12 AM, kdex <[email protected]> wrote: > A good place to start is [1]. > > [1] https://github.com/tc39/proposals > > On Saturday, May 12, 2018 7:11:36 PM CEST Abdul Shabazz wrote: > > I wasn't aware of the committees view of synonyms and that they perceive > > them ad clutter. This unfortunate but i will moderate my future > suggestions > > accordingly. btw where can i find their submission/proposal guidelines? > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
