Proposal accepted on 2020-11-03
Affirming:
Abstaining:
None.
"An open, inclusive process for Carbon changes" requires us to make the decision to go public in a clear and unsurprising way, with criteria that are written down.
Going public too early introduces risks to the long-term evolution and maintenance of the language by increasing the costs of the community members developing it.
Ensuring that Carbon meets its functional goals, especially that of interoperability and migration, will inherently require large scale experimentation that is infeasible to do without becoming public at some point.
The core team is aligned on the core policy decisions, which are:
Changes to the text and wording that align with these items should be submitted as code reviews. The core team members chandlerc and zygloid will both approve each code review.
An example change that would be covered by a code review: there will be no automatic going public just because the criteria are met -- it will be a decision of the core team.