Changes to 'refs/tags/kep8/approved'

[Jeroen van Meeuwen]

Tag 'kep8/approved' created by Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com> at 2011-09-07 18:59 +0200

KEP #8 formally approved
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk5nsRkACgkQKN6f2pNCvwjwwQCfQQisSZjCv+61I/pNaBrYdUKD
cQYAnRbLYAuKVBrRTB+e/konPURGtaFk
=If9D
-----END PGP SIGNATURE-----

Changes since the dawn of time:
Alex Potter (1):
      Patch from Alex Potter to fix spelling and clumsy construction

Georg C. F. Greve (10):
      Incorporated results of some talks, RFC3339 for future-proofing, change XML version due to old clients not following the "preserve all tags unknown to you" rule.
      Minor formatting update, make this explicit for event XML 1.1
      Based on discussion on kolab-format@: Parsing MUST support RFC3339, but writing MUST take place in Zulu for existing objects
      Some editorial restructuring, and further examples added
      Initial draft.
      Substantial edits, based upon email conversation and phone calls with Till Adam, Allen Winter, Bernhard Reiter
      The discussion revealed that this issue affects normal events as well if there is a change of DST rules between their creation and they are located in the "vulnerable zone."
      Major rewrite based on discussion on kolab-format@ to switch to local time storage according to RFC3339.
      Included suggestion by Jeroen van Meeuwen
      Merge branch 'master' of ssh://git.kolabsys.com/git/keps

Georg Greve (22):
      Drafting on procedure, based on some discussions with Jeroen and others.
      Added some more background based on the discussion to allow others to better understand what has been considered thus far.
      Added reference to Douglass draft at IETF
      Lower the tooling threshold to avoid overtooling. KISS me.
      Added Authoritative Component Contact concept, as well as issue tracking methodology, after discussion with Jeroen & Christoph
      Included feedback from Paul regarding kolab.org usage & KEP tagging for server side releases, as well as revision-specific linking that came out of discussion.
      First revision of KEP #4, as submitted by Jeroen van Meeuwen
      New revision, based on last discussions w/Florian v. Samson & Bernhard Reiter
      Merge branch 'master' of ssh://git.kolabsys.com/git/keps
      One more round of feedback from Florian von Samson & Bernhard Reiter
      Last round of changes based on feedback from Florian von Samson
      Included feedback from http://kolab.org/pipermail/kolab-format/2011-May/001348.html and some smaller stylistic things.
      http://kolab.org/pipermail/kolab-format/2011-June/001372.html
      http://kolab.org/pipermail/kolab-format/2011-June/001373.html
      First draft, still lots of work to do
      Update based on http://kolab.org/pipermail/kolab-format/2011-July/001380.html http://kolab.org/pipermail/kolab-format/2011-July/001382.html and http://kolab.org/pipermail/kolab-format/2011-July/001383.html
      Merge branch 'master' of ssh://git.kolabsys.com/git/keps
      small language fix
      Included feedback from Florian & Jeroen
      Some language improvements suggested by Bernhard Reiter
      Fixed RFC number-jumble, caught by Alec. Thanks\!
      Merge branch 'master' of ssh://git.kolabsys.com/git/keps

Georg Greve (Kolab Systems) (1):
      Check in KEP-0001

Jeroen van Meeuwen (Kolab Systems) (20):
      Initial commit
      Empty the related list; there are no tickets or other KEPs related yet
      three -> four kinds of KEP
      Improve non-wiki readibility by inserting a blank line below each section header.
      Check in initial draft of KEP-0002
      Check in initial draft of KEP-0003
      Touch up the wiki syntax of KEP-0002.
      Adjust the title for KEP-0005
      APPROVED KEP #1
      Add new KEP #6: Server Development and Release Process
      As per feedback from Alex Potter, use less jargon and replace the use of 'to bump' with 'to increment'.
      Adjust the title to indicate KEP #5 concerns Server Product Versioning
      KEP #2: Add link to discussion page with options, arguments and considerations.
      Add new submitted KEP 0007 titled "Definitions of Kolab Objects"
      Update the KEP #7 draft in light of some hidden feedback received
      Add KEP-0008 by Georg Greve <greve at kolabsys.com>
      Add KEP 0010 on Kolab SMTP Access Policy by Jeroen van Meeuwen
      Correct the use of SHOULD not vs. SHOULD NOT
      Update KEP #5 with APT packaging specific notes
      Add KEP #11