google / closure-compiler

A JavaScript checker and optimizer.
https://developers.google.com/closure/compiler/
Apache License 2.0
7.4k stars 1.15k forks source link

Define process for making closure-compiler future plans visible to the Open Source community #3229

Open brad4d opened 5 years ago

brad4d commented 5 years ago

I'm proposing that we, the closure-compiler team, update our planning process to include some form of publication of those plans where they can be easily seen by the Open Source community.

I expect this increased visibility will make people much more comfortable using closure-compiler.

At the moment, I'm thinking this would include:

For each quarter:

  1. New features we're actively working to add.
  2. Limitations and bugs we're actively working to eliminate.
  3. Use-cases we're actively working to enable.

In some general place, but reviewed for possible update each quarter.

  1. A general statement of our goals for closure-compiler.
  2. A gneral statement of use-cases we actively support (or don't).
brad4d commented 5 years ago

Internal issue http://b/124249394 created for this