Andrew Sykes wrote:
Stefano,
This is exactly the kind of thing I was thinking about. It's one that
can be really easily delegated to a newbie.
The problem with IMAP is that there is no lead to coordinate the
activity you are describing.
There is a need of a lead that knows his fact about IMAP and understand
James too in order to create subtask, assign them, know the current
status, being able to review the code proposed.
I don't know IMAP so I can't be of help here.
I had a look at the JIRA stuff for IMAP. There are 5 open issues here, I
assume that doesn't represent all the work required for a functional
IMAP. Everyone I've spoken to about JAMES has ruled it out because
there's no IMAP support (and a few have complained about the GUI) - Ok,
enough already!
So the Solution is...
Break down IMAP stuff into little tasks like the logging one. This would
have 3 effects...
[...]
Let me know what you think...
The current effort is to release James 2.3.0 *without* IMAP.
As far as I understood in past the main blocking IMAP issue is related
to repositories. We want to (scheduled to) change/improve repositories
but we can't do that before 2.3.0 is out.
I always heard about IMAP SEARCH command implementation that is a big
thing and we don't have it and it is not so related to James. You may
want to look in the James archives for "Imap search" and try to
understand something about.
Again, I don't know much / I don't use IMAP so take my words as a vague
memory dump.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
