summaryrefslogtreecommitdiff
path: root/KEP-0001.txt
diff options
context:
space:
mode:
authorGeorg Greve <greve@katana.(none)>2010-11-19 12:34:01 (GMT)
committerGeorg Greve <greve@katana.(none)>2010-11-19 12:34:01 (GMT)
commit9671102dbaf9b8d64930e5aa3054a6be41f5f479 (patch)
tree170ec847f7ada36e0211ac54ec1a4215ce7f77a2 /KEP-0001.txt
parentccc12fce4d6b346484a0c65b1da44bc84399d966 (diff)
downloadkeps-9671102dbaf9b8d64930e5aa3054a6be41f5f479.tar.gz
Lower the tooling threshold to avoid overtooling. KISS me.
Diffstat (limited to 'KEP-0001.txt')
-rw-r--r--KEP-0001.txt35
1 files changed, 22 insertions, 13 deletions
diff --git a/KEP-0001.txt b/KEP-0001.txt
index fd1425e..8f68025 100644
--- a/KEP-0001.txt
+++ b/KEP-0001.txt
@@ -38,27 +38,34 @@ 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.
+* 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 following header fields are mandatory:
+** TITLE of the KEP, which should be as descriptive and summarizing as possible
+** AUTHOR(S) of the KEP who are involved in the drafting and volunteer to drive the process. If there are multiple authors they should agree on a primary author who should be listed first.
+** TYPE of the KEP, according to the types listed and explained above.
+** MAILINGLIST that will be canonical for discussion of this KEP. In principle, any English speaking public mailing list for Kolab can be chosen, the following lists are recommended for the various types of KEP:
+*** '''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]
+*** '''Informational KEP''' are typically discussed on [mailto:kolab-devel@kolab.org kolab-format@kolab.org]
+*** '''Process KEP''' are typically discussed on [mailto:kolab-devel@kolab.org kolab-format@kolab.org]
+** (if applicable) KEPs that are going to be obsoleted/replaced by this KEP.
+* The secretariat assigns the next sequential number to this KEP, ensures the formatting is correct, all header fields are provided and places the file in the [http://git.kolabsys.com/keps/ GIT repository], ensuring the author(s) have access.
+* The primary author then places the draft in their personal namespace on wiki.kolab.org, the recommended naming is /User:<NAME>/Drafts:KEP:<NUMBER>
+* The primary author then announces and introduces the draft KEP to the canonical mailing list for discussion, resending this mail to other public Kolab mailing lists as required. One copy should always go to [mailto:kolab-devel@kolab.org kolab-devel@kolab.org].
=== 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]
-** '''Informational KEP''' are typically discussed on [mailto:kolab-devel@kolab.org kolab-format@kolab.org]
-** '''Process KEP''' are typically discussed on [mailto:kolab-devel@kolab.org kolab-format@kolab.org]
-* Feedback or comments should always be sent with CC: to the author(s) or be entered into the respective Bugzilla issue.
+* The KEP will be discussed on the most appropriate public mailing list.
* The author(s) have the obligation to consider each substantive submission and comment, to judge it carefully and on its technical/substantive merits, and to try and incorporate it in the most constructive, inclusive and consensus building manner.
-* KEPs are adopted by consensus in the form of lack of sustained, qualified opposition.
* While all kinds of comments are welcome, opposing views owe it to the author(s) to have given good consideration to the aspects raised in the KEP. Depending on the kind of KEP, this means qualified opposition must meet certain minimum criteria:
** For opposition to be technically qualified, it should be based on the KEP and its references, and make a topical technical point disproving any particular part of the KEPs argument, conclusion or decision.
** For opposition to be procedurally qualified, it should be based on procedural questions and concerns, as well as accompanied by an improvement proposal.
-* When a KEP has been thoroughly discussed, either on public list before it has become formalized, or in its drafting stage, the secretariat should issue a "closing call" for the KEP, stating the deadline by which it will be considered adopted. This deadline should be
+* As the drafting continues, the author(s) will continue to work in feedback, bringing the document to a consensus opinion, providing updated drafts through wiki.kolab.org, as sensible, helpful and appropriate to facilitate good and timely consensus building.
+* KEPs are adopted by consensus in the form of lack of sustained, qualified opposition.
+* When a KEP has been thoroughly discussed, either on public list before it has become formalized, or in its drafting stage, the secretariat should then issue a "closing call" for the KEP, stating the deadline by which it will be considered adopted. This deadline should be
** '''two weeks''' after the closing call for all KEP that are based on more than '''six weeks''' of discussion on the respective public mailing lists, either before they became formalized as KEP, or after, and
** '''six weeks''' for all KEP that have been discussed shorter.
-* The closing call should go to kep-announce@lists.kolabsys.com as well as the public mailing list on which the discussion took place.
+* When the closing call is issued, the KEP should be moved into the authoritative name space on wiki.kolab.org/KEP:<NUMBER> and while the authors can continue to work on the version in git, updates of the authoritative version should now go through the secretariat.
+* The closing call should go to the canonical discussion mailing list, as well as all public mailing list that seem sensible and relevant. kolab-devel@kolab.org shall always be informed.
* In reaction to the closing call, any member of the Kolab community can request a two week extension for important reasons with the secretariat. This extension will be granted once for any KEP.
* 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.
@@ -70,13 +77,15 @@ The life cycle of a KEP is
=== 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 is no longer relevant to Kolab, the secretariat shall send a note of 'pending retirement' to the canonical mailing list on which it was discussed, as well as kolab-devel@kolab.org (if not identical) 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.
+In absence of volunteers who are not themselves active authors or participating in the discussions, it shall deemed acceptable to have author participate in the secretariat. In no case shall an active author of a KEP perform the secretariat duties for their own KEP in question.
+
== References ==
{{Reflist}}