# This forum doesn't allow to add new features, right?

**URL:** <https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109>\
**Category:** I have questions\
**Created:** [August 14, 2024, 7:59pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109 "2024-08-14T19:59:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![oleedd](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/oleedd/32/2148_2.png) [@oleedd](https://es.discourse.group/u/oleedd)\
**Post date:** [August 14, 2024, 7:59pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/1 "2024-08-14T19:59:07Z")

</div>

As I understood, this forum doesn't allow to add new features. If you want a new feature, you have to create a proposal on github yourself, even if you never read the ECMA documentation and know nothing about this process, no other way.  
This forum is probably only for questions, for other things it is absolutely useless.

To be useful, there should be voting of TC39 members - for or against, and depending on this, adding a new feature.

---

<div class="post-metadata">

**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\
**Post date:** [August 15, 2024, 8:46pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/2 "2024-08-15T20:46:01Z")

</div>

We don't make decisions by voting.

You can absolutely discuss a potential new feature here - that way you can get a better idea if it's worth the effort to make a proposal, based on the reaction.

---

<div class="post-metadata">

**Author:** ![tabatkins](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/tabatkins/32/170_2.png) [@tabatkins](https://es.discourse.group/u/tabatkins)\
**Post date:** [August 15, 2024, 9:02pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/3 "2024-08-15T21:02:37Z")

</div>

Ultimately, changes or additions to the language are proposed by members of the TC39 committee, and decided on during committee meetings several times a year. Non-members can _contribute_ to proposals (you can be a "champion" of a proposal without being part of TC39), but the proposal does _require_ at least one TC39 member to champion it.

So forums like this are useful for discussing an issue, and potentially getting a TC39 member interested in championing a proposal.

---

<div class="post-metadata">

**Author:** ![oleedd](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/oleedd/32/2148_2.png) [@oleedd](https://es.discourse.group/u/oleedd)\
**Post date:** [August 15, 2024, 9:53pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/4 "2024-08-15T21:53:07Z")

</div>

> [@ljharb](#):
>
> We don't make decisions by voting.

I know. That is why I say about this. I would like to see rejecting or accepting ideas. Not just nothing as now. I came for this.

> [@tabatkins](#):
>
> but the proposal does _require_ at least one TC39 member to champion it

Hm, I didn't know about this.

---

<div class="post-metadata">

**Author:** ![oleedd](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/oleedd/32/2148_2.png) [@oleedd](https://es.discourse.group/u/oleedd)\
**Post date:** [September 12, 2024, 4:15pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/5 "2024-09-12T16:15:58Z")

</div>

How do you reject or accept existing proposals if not by voting then?

---

<div class="post-metadata">

**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\
**Post date:** [September 12, 2024, 4:32pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/6 "2024-09-12T16:32:50Z")

</div>

TC39 operates on consensus - nothing advances unless there's zero objections to it.

---

<div class="post-metadata">

**Author:** ![oleedd](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/oleedd/32/2148_2.png) [@oleedd](https://es.discourse.group/u/oleedd)\
**Post date:** [September 12, 2024, 4:44pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/7 "2024-09-12T16:44:47Z")

</div>

Now I understand why many good proposals don't move for years.  
1 person may block all.  
How many members at all? The more members, the harder to achieve consensus.

---

<div class="post-metadata">

**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\
**Post date:** [September 12, 2024, 5:03pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/8 "2024-09-12T17:03:30Z")

</div>

There's probably 60-80 at this point.

Achieving consensus is difficult, but the process helps ensure we don't ship something we can never take back. It's better to go slow then to make something permanently worse.

---

<div class="post-metadata">

**Author:** ![theScottyJam](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/thescottyjam/32/616_2.png) [@theScottyJam](https://es.discourse.group/u/theScottyJam)\
**Post date:** [February 11, 2025, 2:56pm UTC](https://es.discourse.group/t/this-forum-doesnt-allow-to-add-new-features-right/2109/9 "2025-02-11T14:56:21Z")

</div>

I'm also not sure that there's any other way to do it besides consensus. If everyone votes for a feature, except, say, whoever represents Chrome is against that feature, well, it would be kind of pointless if everyone except the Chrome team implements the new feature.

I often read through the meeting notes. Usually we're not in a situation where a single person is blocking an entire feature from being implemented. If most people want a feature, and an individual, even if they don't love it, doesn't have overly strong disagreements against it, that individual will usually let it progress.

A lot of those great features you see getting stuck in the proposal pipeline are usually stuck because it's a controversial feature and there's lots of disagreement around it.
