Author: Per Gustafsson <pergu(at)it(dot)uu(dot)se>, Raimo Niskanen <raimo(at)erlang(dot)org> Status: Draft Type: Process Created: 29-Jan-2007 Post-History: 29-Jan-2007
EEP stands for Erlang Extension Proposal, or Erlang Enhancement Process. It is a concept borrowed from the Python language to facilitate community involvement in developing Erlang. This document is heavily based on PEP 1. An EEP is a design document providing information to the Erlang community, or describing a new feature for Erlang or its processes or environment. The EEP should provide a concise technical specification of the feature and a rationale for the feature.
We intend EEPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Erlang. The EEP author is responsible for building consensus within the community and documenting dissenting opinions.
Because the EEPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.
There are two kinds of EEPs:
A Standards Track EEP describes a new feature or implementation for Erlang.
A Process EEP describes a process surrounding Erlang, or proposes a change to (or an event in) a process. Process EEPs are like Standards Track EEPs but apply to areas other than the Erlang language itself. They may propose an implementation, but not to Erlang's codebase; they often require community consensus; they are more than recommendations, and users are typically not free to ignore them. Examples include release schedules, procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Erlang development.
The EEP editors assign EEP numbers and change their status. Please send all EEP-related email to email@example.com.
The EEP process begins with a new idea for Erlang. It is highly recommended that a single EEP contain a single key proposal or new idea. The more focused the EEP, the more successful it tends to be. The EEP editor reserves the right to reject EEP proposals if they appear too unfocused or too broad. If in doubt, split your EEP into several well-focused ones.
Each EEP must have a champion -- someone who writes the EEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The EEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is EEP-able. Posting to the firstname.lastname@example.org mailing list is recommended. Small enhancements or patches often don't need a EEP and can be injected into the Erlang development work flow by sending a patch to email@example.com.
The EEP champion writes a rough but fleshed out draft of the EEP, with a proposed title. This draft must be written in EEP style as described below. Then, after subscribing to the email list firstname.lastname@example.org, the EEP champion sends the EEP to that list. Note that the list has a size limit for posts, at the time of writing 128 KByte, so EEPs with attachments that are too large will bounce. Large attachments can be put on a suitable web page and then be referred to from the EEP. If that is not possible, ask on the list how to submit the large EEP in question.
If the EEP editor approves, she/he will assign the EEP a number, label it as Standards Track or Process, give it status "Draft", and create and check-in the initial draft of the EEP. The EEP editor will not unreasonably deny a EEP. Reasons for denying EEP status include duplication of effort, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Erlang philosophy.
If a pre-EEP is rejected, the author may elect to take the pre-EEP to the email@example.com mailing list to help flesh it out, gain feedback and consensus from the community at large, and improve the EEP for re-submission.
The author of the EEP is then responsible for posting the EEP to the community forums, and marshaling community support for it. As updates are necessary, the EEP author can check in new versions if they have commit permissions, can email new EEP versions or diffs to the EEP editor for committing, or submit changes in any other suitable way for the version control system.
Standards Track EEPs consist of two parts, a design document and a reference implementation. The EEP should be reviewed and accepted before a reference implementation is begun, unless a reference implementation will aid people in studying the EEP. Standards Track EEPs must include an implementation -- in the form of code, a patch, or a URL to same -- before it can be considered Final.
EEP authors are responsible for collecting community feedback on a EEP before submitting it for review. A EEP that has not been discussed on the erlang mailing list will not be accepted. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. Strategies to keep the discussions efficient include: setting up a separate SIG mailing list for the topic, having the EEP author accept private comments in the early design phases, setting up a wiki page, etc. EEP authors should use their discretion here.
Once the authors have completed a EEP, they must inform the EEP editor that it is ready for review. EEPs are reviewed by a committee of people from the Erlang/OTP and the Erlang community who may accept or reject a EEP or send it back to the author(s) for revision. For a EEP that is pre-determined to be acceptable (e.g., it is an obvious win as-is and/or its implementation has already been checked in) the Erlang/OTP team may also initiate a EEP review, first notifying the EEP author(s) and giving them a chance to make revisions.
The committee members are the internal Erlang/OTP Technical Board plus for the specific case summoned experts.
For a EEP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the interpreter unduly. Finally, a proposed enhancement must be compatible with the Erlang philosophy in order to be accepted.
Once a EEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and accepted, the status will be changed to "Final".
A EEP can also be assigned status "Deferred". The EEP author or editor can assign the EEP this status when no progress is being made on the EEP. Once a EEP is deferred, the EEP editor can re-assign it to draft status.
A EEP can also be "Rejected". Perhaps after all is said and done it was not a good idea. It is still important to have a record of this fact.
EEPs can also be replaced by a different EEP, rendering the original obsolete.
EEP work flow is as follows:
Some Process EEPs may also have a status of "Active" if they are never meant to be completed. E.g. EEP 1 (this EEP).
Each EEP should have the following parts:
Preamble -- RFC 822 style headers containing meta-data about the EEP, including the EEP number, a short descriptive title (limited to a maximum of 44 characters), the names, and optionally the contact info for each author, etc.
Abstract -- a short (~200 word) description of the technical issue being addressed.
Copyright/public domain -- Each EEP must either be explicitly labelled as placed in the public domain (see this EEP as an example) or licensed under the Open Publication License, or the Creative Commons Attribution 3.0 License.
Specification -- The technical specification should describe the syntax and semantics of any new language feature. The specification should be detailed enough to allow competing, interoperable implementations.
Motivation -- The motivation is critical for EEPs that want to change the Erlang language. It should clearly explain why the existing language specification is inadequate to address the problem that the EEP solves. EEP submissions without sufficient motivation may be rejected outright.
Rationale -- The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages.
The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion.
Backwards Compatibility -- All EEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The EEP must explain how the author proposes to deal with these incompatibilities. EEP submissions without a sufficient backwards compatibility treatise may be rejected outright.
Reference Implementation -- The reference implementation must be completed before any EEP is given status "Final", but it need not be completed before the EEP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code.
The final implementation must include test code and documentation appropriate for either the Erlang language reference or the standard library reference.
An EEP is written as an UTF-8-encoded text file in Markdown format. EEP 33 is a template and contains an instruction of how to write an EEP.
In the repository there is also a version of the Markdown
Perl program and a some Perl scripts for building the EEP index.
Just give the command
./build.pl in the toplevel directory.
Each EEP must begin with an RFC 822 style header preamble all indented four spaces to make them Markdown code style. The headers must appear in the following order. Headers marked with "*" are optional and are described below. All other headers are required:
Author: <list of authors' real names and optionally, email addrs> * Discussions-To: <email address> Status: <Draft | Active | Accepted | Deferred | Rejected | Final | Replaced> Type: <Standards Track | Process> * Content-Type: <text/plain | text/x-rst> * Requires: <eep numbers> Created: <date created on, in dd-mmm-yyyy format> * Erlang-Version: <version number> Post-History: <dates of postings to erlang-questions> * Replaces: <eep number, ...> * Replaced-By: <eep number, ...>
Then follows a Markdown horizontal rule, the EEP number and title
as a Markdown header 2, and a blank line, all required:
The Author header lists the names, and optionally the email addresses of all the authors/owners of the EEP. The format of the Author header value must be
Random J. User <firstname.lastname@example.org>
if the email address is included, and just
Random J. User
if the address is not given.
If there are multiple authors, each should be on a separate line following RFC 2822 continuation line conventions. Note that personal email addresses should be obscured as a defense against spam harvesters.
While a EEP is in private discussions (usually during the initial Draft phase), a Discussions-To header will indicate the mailing list or URL where the EEP is being discussed. No Discussions-To header is necessary if the EEP is being discussed privately with the author, or on the erlang mailing list. Remember to obscure email addresses here to.
The Type header specifies the type of EEP: Standards Track or Process.
The Created header records the date that the EEP was assigned a number, while Post-History is used to record the dates of when new versions of the EEP are posted to erlang-questions. Both headers should be in dd-mmm-yyyy format, e.g. 14-Aug-2009.
Standards Track EEPs must have a Erlang-Version header which indicates the version of Erlang that the feature will be released with. Process EEPs do not need a Erlang-Version header.
EEPs may have a Requires header, indicating the EEP numbers that this EEP depends on..
EEPs may also have a Replaced-By header indicating that a EEP has been rendered obsolete by later EEP(s); the value is the number(s) of the EEP(s) that replaces the current document. The newer EEP(s) must have a Replaces header containing the number(s) of the EEP(s) that it rendered obsolete.
EEPs may include auxiliary files such as diagrams. Such files must be
eep-XXXX-Y.ext, where "XXXX" is the EEP number, "Y" is a
serial number (starting at 1), and ".ext" is replaced by the actual
file extension (e.g. ".png").
How you report a bug, or submit a EEP update depends on several factors, such as the maturity of the EEP, the preferences of the EEP author, and the nature of your comments. For the early draft stages of the EEP, it's probably best to send your comments and changes directly to the EEP author. For more mature, or finished EEPs you may want to submit corrections to the email@example.com mailing list.
When in doubt about where to send your changes, please check first with the EEP author and/or EEP editor.
EEP authors can update EEPs by submitting new versions to the editors.
It occasionally becomes necessary to transfer ownership of EEPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred EEP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the EEP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the EEP. We try to build consensus around a EEP, but if that's not possible, you can always submit a competing EEP.
If you are interested in assuming ownership of a EEP, send a message asking to take over, addressed to both the original author and the EEP editor firstname.lastname@example.org. If the original author doesn't respond to email in a timely manner, the EEP editor will make a unilateral decision (it's not like such decisions can't be reversed :).
This document has been placed in the public domain.