summaryrefslogtreecommitdiff
path: root/KEP-0001.txt
diff options
context:
space:
mode:
authorJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2010-11-18 14:58:25 (GMT)
committerJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2010-11-18 14:58:25 (GMT)
commit5b977e2de5948ee38c9c00f8da6734658a01cb85 (patch)
tree27ecf7f669f9e015960772a04671d7ce467a06b7 /KEP-0001.txt
parentacbb36bfa64436482de359ceb4aa9a86c27d1f5d (diff)
downloadkeps-5b977e2de5948ee38c9c00f8da6734658a01cb85.tar.gz
Improve non-wiki readibility by inserting a blank line below each section header.
Diffstat (limited to 'KEP-0001.txt')
-rw-r--r--KEP-0001.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/KEP-0001.txt b/KEP-0001.txt
index b635052..fd1425e 100644
--- a/KEP-0001.txt
+++ b/KEP-0001.txt
@@ -37,11 +37,13 @@ The KEP Process began with a rough approximation of the PEP process, excluding t
The life cycle of a KEP is
=== Creation ===
+
* A new draft KEP is sent to [mailto:kep-secretariat@lists.kolabsys.com kep-secretariat@lists.kolabsys.com] with the request to assign a number for this KEP.
* The secretariat assigns the next sequential number to this KEP, ensures the formatting is correct and all header fields are provided, sets up the corresponding tooling, such as the [http://wiki.kolab.org/KEP Wiki] page, the corresponding [https://bugzilla.kolabsys.com Bugzilla] issue, and places the file in the [http://git.kolabsys.com/keps/ GIT repository].
* The secretariat then announces the new KEP to kep-announce@lists.kolabsys.com and gives the author(s) of the KEP access to the repository.
=== Discussion and Finalization ===
+
* The KEP will then be discussed on the most appropriate public mailing list:
** '''Design KEP''' are typically discussed on [mailto:kolab-format@kolab.org kolab-format@kolab.org]
** '''Technology KEP''' are typically discussed on [mailto:kolab-devel@kolab.org kolab-format@kolab.org]
@@ -61,15 +63,18 @@ The life cycle of a KEP is
* If there is sustained, qualified opposition (as described above) after the closing call, the author(s) must take that into account in the best way possible, potentially documenting sustained opposition in the KEP. Afterwards, the author(s) shall request another closing call from the secretariat.
=== Adoption, Rejection and Retraction ===
+
* If there was no qualified opposition to a closing call on a KEP within the deadline set by the secretariat, the KEP has been formally adopted and its status will be changed to 'accepted'.
* The author(s) of a KEP can at any point in time retract their proposal, the KEP will then be considered closed, its status will be changed to 'retracted'.
* If a KEP fails to gain acceptance within '''one calendar year''' after it was initially proposed, its status shall be changed to 'rejected'. A new KEP with a similar proposition can then be requested by the same author(s) or others.
=== Replacement, Retirement ===
+
* If a KEP is no longer relevant to Kolab, the secretariat shall send a note of 'pending retirement' to kep-announce@lists.kolabsys.com with no less than '''six weeks''' of notice period for opposition. If no opposition is received, the KEP shall be deemed 'retired' and of purely historical interest.
* If a KEP has been replaced by another KEP which has been duly accepted, its status shall be set to 'replaced'.
== The Secretariat ==
+
The secretariat shall consist of volunteers who are '''not''' currently active in the KEP process as authors or discutants and shall understand their role as a purely faclitatory one. Any member of the Kolab community can volunteer for the secretariat, and shall be held in high honors for helping with this important task.
== References ==