Keeping proposals productive and increasing mailing list efficiency

Isiah Meadows isiahmeadows at
Wed Jul 4 01:05:46 UTC 2018

First, I found this resource that does clarify a *few* things, but it
doesn't go over details.


Second, if you feel strongly enough, feel free to ping one of the
active committee members either through email or on #tc39 (on Freenode
IRC) to see about getting a little more clarification to the process.

Oh, and side note: one plus to having it email-only is that it's
easier to respond on-the-fly on mobile, and that's not quite so easy
when it's all on some platform thingy. (The list also isn't quite
active enough to merit the need for sorting and organization beyond
what provides.)


Isiah Meadows
me at

On Mon, Jul 2, 2018 at 3:19 PM, Mark <mark at> wrote:
> Yeah I looked at those but they are rather outdated. A lot of the pushback
> from moving to other platforms (ie. lack of mailing list features, forced
> browser usage, etc) are no longer the case and therefore dont really help
> explain why this list has avoided doing it for so long now.
> On Mon, Jul 2, 2018, 3:12 PM Jerry Schulteis <jdschulteis at> wrote:
>> One way to find related conversations is to add to the
>> search terms.
>> E.g. " mailing list alternative":
>> Perhaps such a hint, as well as guidelines for self-vetting proposals
>> before submitting, should appear in the list welcome message or the
>> information page.
>> On Monday, July 2, 2018, 12:22:14 PM CDT, Mark <mark at> wrote:
>> previous related conversations are not being considered because they are
>> not prominent or easily found- they are kept in an archive that is totally
>> separate from the email clients being used to facilitate these mailing list
>> discussions. This means it is not likely that a person making a proposal,
>> who is new to this mailing list format (which is mostly the case with new
>> proposals), will even see the archives.
>> Another point: there are plenty of alternative solutions out there that
>> would make this list much more usable and efficient (discourse, slack,
>> GitHub etc), which have wide support and are reliable. Is there a reason why
>> this list hasn’t embraced any of these newer technologies? Although not
>> necessary, they offer strong feature sets that will make it quite easy to
>> provide solutions to the above points.
>> _______________
>> es-discuss mailing list
>> es-discuss at
> _______________________________________________
> es-discuss mailing list
> es-discuss at

More information about the es-discuss mailing list