I finally read it and it's very good (I have some comments but will
keep them for when this become a documentation as they are really
minor).
Thank you Benoit, I think it will help building a overall picture of
what James is and how it works.
-- Matthieu Baechler
On Mon, 2020-05-25 at 12:00
Hi Benoît,
Thanks for the effort you put into this. It's very useful.
I also saw the list of documents
https://github.com/apache/james-project/tree/master/src/adr . I need to
go through them.
@Raphaël : IMO there are many points of view here:
- the technical / developer view - we work on
Hello,
Even if I globally agree with your definition of extension, I think
import/export is a very valuable feature and should be promoted (when
finished). Of course from an architecture point of view it could be seen
as an extension but for an admin it should be well integrated and easy
to
On 10/06/2020 22:49, Raphaël Ouazana-Sustowski wrote:
> Hi Benoît,
>
> This inventory is amazing, thanks for having issued it.
>
> For my part it's just missing the LDAP read only user repository as an
> implementation of the user repository.
True.
> But I probably missed things :)
>
> Oh
Hi Benoît,
This inventory is amazing, thanks for having issued it.
For my part it's just missing the LDAP read only user repository as an
implementation of the user repository.
But I probably missed things :)
Oh for example the (unfinished?) import / export mechanism.
Regards,
Raphaël.
Hi Benoit:
> I gave a shot at defining:
>
> - Core components, that offers services at heart of James
> - Utility components, that offers services core-components
> implementations can rely on.
> - Mailbox sub-components.
Wow, there is a lot here! It will take me some time to digest, but
Hi David,
I gave a shot at defining:
- Core components, that offers services at heart of James
- Utility components, that offers services core-components
implementations can rely on.
- Mailbox sub-components.
Here is the result. I encourage other project members to review it.
- Did I
