Hi, La 15.06.2020 13:41, David Leangen a scris: >> 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
+ 1 . I would also propose we call these (Operator, Email user, Extension Developer, Developer) as "personas" in the docs (https://en.wikipedia.org/wiki/Persona#In_marketing): Operator persona, or Developer persona. When we talk about the specific persona, we have in mind the list of abilities he/she posses and what we expect him/her to be able to do. > 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 How about "Extension Developer" and "Developer" . A note, some developers are also Apache contributors. >> +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”. Please consider using the Persona terms for the above, as to not over load the "user". We can also link to what we mean by persona. >> 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. > :-) +1 for separation and the word change. "Support" implies quite a lot. "Offering" sounds good to me. >> 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. I think things are shaping up nicely and I like it. > > Cheers, > =David > -- Eugen Stan +40720 898 747 / netdava.com
<<attachment: eugen_stan.vcf>>
signature.asc
Description: OpenPGP digital signature
