MBOX-Line: From lyndon at orthanc.ca  Tue Mar 24 21:13:26 2015
To: imap-protocol@u.washington.edu
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Date: Fri Jun  8 12:34:54 2018
Subject: [Imap-protocol] Is OpenEmailSurvey open to share method or code?
In-Reply-To: <1427252504.1020832.244866921.0886703A@webmail.messagingengine.com>
References: <55109D4C.2080900@laposte.net>
	<1427153195.246194.244290758.41EF7C3D@webmail.messagingengine.com>
	<F90D4251-9EE1-493B-8A5F-31B8A1B41B87@orthanc.ca>
	<1427226341.922442.244719958.3B420059@webmail.messagingengine.com>
	<2FC3E597-358B-4F71-B1F6-68A18C85DB51@orthanc.ca>
	<1427252504.1020832.244866921.0886703A@webmail.messagingengine.com>
Message-ID: <2DDE9D54-577E-4DA7-99D6-1A531E9C86E0@orthanc.ca>


On Mar 24, 2015, at 8:01 PM, Bron Gondwana <brong@fastmail.fm> wrote:

> Honestly the simplest thing is what was discussed years ago on the imap5 list, just picking
> all the ones which really matter and get significant use, bunding them behind "IMAP5" and
> replacing all the other capabilities with just IMAP5.

But that resets the whole standards track progression.  I would rather we marked the unused extensions as Historic, then cleaned up the bugs in the rest and moved the whole mess forwards towards actual Standard status.  We certainly have enough implementation and interop experience to make this viable.

Proposing an IMAP5 would just let loose a bucket of snakes that would never get herded back into any sort of container.

--lyndon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 817 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150324/627f5787/attachment.sig>
