Re : ADR files hierarchy

Hello,

Thanks for bringing this discussion onto the mailing list.

My opinion: +0.5

The proposal is OK to me as it keeps ADRs groupped thought I feel uneasy with not having things flat.
Conceptually I like a succession of records to be a log.

Regarding the overall discoverability topic, maybe another alternative is "tagging"

We could rewirte ADR top section as

---adr: 0075title: Deleted Message Vaultstatus: accepted (lazy consensus)date: 2024-10-12tags:  - tag:mailbox  - tag:plugins---

grep 'tag:mailbox' src/adr 

would then be sufficient to return me ADR about the mailbox.
-- 

Best regards,

Benoit TELLIER

General manager of Linagora VIETNAM.
Product owner for Twake-Mail product.
Chairman of the Apache James project.

Mail: [email protected]
Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)


Le janv. 7, 2026 4:54 AM, de Rene Cordier <[email protected]>Hello guys,

There was a remark on this ADR 
github.com/apache/james-project/pull/2894 expressed by the 
community regarding proposing restructuring the way we organize ADRs.

It might be better to not mix the ADRs belonging to James Core with the 
ADRs related to some James extensions (like the Deleted Message Vault).

We seem to overall agree that it would be easier to allow new developers 
for example to catch up with James core architecture as an all without 
over-complexify it for them with the extensions.

However we seem to be less sure on how to manage that.

Spark of initial idscussion in the folloowing PR comment: 
github.com/apache/james-project/pull/2894#discussion_r2658835617

I think the easiest way IMO would be to divide the `src/adr` folder into 
subfolders?  Something like:

```
src/
   - adr/
     + core/
     + extensions/
[...]
```

Then it would be easy to maintain ADRs for both core and extensions, 
easy for everybody to find, easy to add new ones... Not confusing as 
well on what is core and what is extension ADR...

Well that's my proposition anyways, opened to discussion !

Best regards,

Rene.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]