sieve and global/default scripts

[Dave McMurtrie]

Hi,

First, apologies for the top-post.  The client I'm responding from doesn't allow me to quote inline because apparently in 2015 we no longer need to do that.  But I digress...

I think everyone agrees that the state of Cyrus documentation is deplorable, but it's very understandable.  The people who contribute the most to the Cyrus project are the people who are writing code.  There is nobody dedicated full-time to writing documentation and the result of that is what you've observed: lackluster documentation.

Jeroen has put considerable effort into improving that, but it's been mostly a solo effort up to this point.  You can see his work at http://cyrusimap.org/~vanmeeuwen/.  

In the true spirit of open source collaboration, I invite you to contribute to the project by improving the documentation that exists and adding any documentation that is missing.  I can create an account for you in the wiki if you're interested.  Please let me know.

Thanks!

Dave
________________________________________
From: info-cyrus-bounces+dave64=andrew.cmu.edu at lists.andrew.cmu.edu [info-cyrus-bounces+dave64=andrew.cmu.edu at lists.andrew.cmu.edu] on behalf of Eugene M. Zheganin [eugene at zhegan.in]
Sent: Friday, February 06, 2015 6:20 AM
To: info-cyrus at lists.andrew.cmu.edu
Subject: Re: sieve and global/default scripts

Hi.

On 06.02.2015 14:46, Niels Dettenbach wrote:
> did you still have read the manual?:
I really do. The most sad thing - is that I have to read the part that
isn't yet written. The thought of the author of this particular article
was dwelling for some reason, there's no explanation about how the
global script can be enabled by default for all users (without the need
of linking them manually): the author first decided to explain different
kinds of scripts, then he switched to another topic - shared folders,
and then he totally forgot what he was talking about at the start.

I'm using cyrus-imapd for like 12 years. I often see complaints that
it's documented badly. I often see the responses to such complaints -
with appropriate manual quoting. Well, "badly documented" doesn't mean
that it's not documented - it means that the documentation is fragmented
across a set of man pages, README files, web articles - and they all
aren't linked together, and this situation doesn't change. There's no
definitive guide on Cyrus (at least I didn't see such one). I assume
there can be an article on sieve and about how to enable the global
scripts, but I decided it would be more simple to ask here - I assume
one of the reasons for having such unorganized documentation set is the
need to communicate with users inside this mailing list.

I really do need to read the manual - do you by any chance have it by
any chance ?

Thanks.
Eugene.
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus