> I prefer the term "operator" to "user”. That’s fine. So I will collapse all those previous definitions into the single “Operator”.
When we say “User”, it will therefore mean: >> * Email User >> - Just uses email without any notion of what server is providing the >> service I think it’s better to have two different words rather than the same word + a qualifier. On that note, if we can find different words for these, it would be nice: * Extension Developer * Core Developer > +1, we need to build a common terminology, and document it somewhere > else that just in a mail thread. I will include it in the new documentation. I will add a section entitled “James User Model”. > If the contract don't exist it can't be respected :-) As we say in English: “touché". (We have so many great words in English.) > Also I would like to differentiate the terms "offering" (what do we > deliver as part of the James project, who do it targets, and how easy > should it be to use) from the term "support" which in my view implies > "how fast you solve my problems", and might be a more sensible topic. I think I understand what you mean, and it’s a good point. However, this is a separate topic, so I will move this to a separate thread. :-) > I perfectly agree to write an ADR for the offering, and evaluate the > work required to get there. After I produce the new docs and get some feedback, I will write the ADR. Cheers, =David
signature.asc
Description: Message signed with OpenPGP
