[Kolab-devel] NEW KEP: KEP #14: Non-conflicting edits of RFC5228/Sieve scripts by multiple editors
Georg C. F. Greve
greve at kolabsys.com
Thu Sep 1 14:27:03 CEST 2011
On Thursday 01 September 2011 13.19:26 Jeroen van Meeuwen wrote:
> I agree strictly speaking only the "include" capability is required for
> this KEP, and perhaps a different KEP would outline different features and
> recommended or even mandatory implementations or Sieve extensions to use.
Actually Christoph in conversation also suggested he'd like to see something
like a reference guide as to which functions should be supported, and how they
should be used, to allow one Sieve editor to parse the output of another Sieve
editor, so users can edit the same script with different editors.
That would definitely be worthwhile.
But it would definitely also completely overreach the intention of this KEP, so
my suggestion would be to focus KEP 14 on the non-conflicting mechanism, and
then start another KEP with capabilities and canonical approaches to Sieve
usage within Kolab.
Best regards,
Georg
--
Georg C. F. Greve
Chief Executive Officer
Kolab Systems AG
Zürich, Switzerland
e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com
pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110901/eccbd6f8/attachment.sig>
More information about the devel
mailing list