[eeps] Commit: r41 - eeps/trunk

raimo+eeps <>
Fri Aug 15 10:31:38 CEST 2008

Author: raimo
Date: 2008-08-15 10:31:38 +0200 (Fri, 15 Aug 2008)
New Revision: 41

Elaborated on how to submit large EEPs.

Modified: eeps/trunk/eep-0000.txt
--- eeps/trunk/eep-0000.txt	2008-08-14 08:09:14 UTC (rev 40)
+++ eeps/trunk/eep-0000.txt	2008-08-15 08:31:38 UTC (rev 41)
@@ -22,7 +22,7 @@
      ---  -----                                          -----
  P     0  Index of Erlang Enhancement Proposals (EEPs)   Raimo Niskanen
- P     1  EEP Purpose and Guidelines                     Per Gustafsson
+ P     1  EEP Purpose and Guidelines                     Per Gustafsson, Raimo Niskanen
  P     2  Sample Plaintext EEP Template                  Per Gustafsson
  P     3  Sample reStructuredText EEP Template           Per Gustafsson

Modified: eeps/trunk/eep-0001.txt
--- eeps/trunk/eep-0001.txt	2008-08-14 08:09:14 UTC (rev 40)
+++ eeps/trunk/eep-0001.txt	2008-08-15 08:31:38 UTC (rev 41)
@@ -74,10 +74,16 @@
 into the Erlang development work flow by sending a patch to
-The EEP champion subscribes to the email list <> (see
-http://www.erlang.org/mailman/listinfo/eeps) and sends a rough
-but fleshed out draft of the EEP, with a proposed title, to that list.
-This draft must be written in EEP style as described below.
+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
+<>, 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, he will assign the EEP a number, label it
 as Standards Track or Process, give it status "Draft",

More information about the eeps mailing list