Process for creating environment name definitions

[guybedford]

It would be worth discussing this process further.

In terms of the rules for a definition, we should flesh out some basic requirements like -

• The environment definition should be clear enough such that any existing or new JS environments in future can easily work out whether to support it.
• The definition should not change over time.

In addition, the process for a definition should likely be two-phase - provisional definition registration moving to a final definition.

Where the stability process might be something like - a definition is provisional until there is agreement between at least three separate tools or environments.

It seems like a website and form to manage the above would make sense.

Any further thoughts / ideas on the above?

[mathiasbynens]

Note that Closure Compiler is paving the way here, with the following approach: #2 (comment)

Since alignment is desirable, it makes sense to consider matching Closure Compiler's design here.

[guybedford]

I'm all for the design... this issue is actually more of a meta issue around defining target names in general... with the aim to think about exactly how to move forward with a process of standardising those definitions.