Instructions to propose changes to Eta.
The Eta Programming Language development process is community-driven. Significant changes to the language, tools and the ecosystem must be discussed and documented before they can be implemented.
This document contains the process for Eta Proposals (EPs) that specify precise changes to Eta and it's infrastructure.
When you have an idea for a major change and you are interested in writing a detailed proposal for it, you proceed as follows:
This step is not required, but it is a good way to test the waters before devoting time to contemplating a design and/or implementation plan for your idea.
Once you have submitted a pull request, the Eta Proposal Process starts.
Once a proposal has been merged, it can be in one of two states (indicated by a label): active or proposed.
If it is active, it means the EP can be implemented in the near future. Proposals in this category will also be assigned one of three priority labels:
If it is postponed, it means the EP will not be implemented in the near future, but the status may change to active if conditions permit.
Moreover, if an implementation plan has not been specified in the proposal, a TypeLead member will provide a brief sketch of the implementation plan.