Le 14/06/2020 à 10:46, David Leangen a écrit :
> Hello Apache James Community!
>
> As you may know, I became interested in James and wanted to learn about how
> to set up my own mail server. My main interests in James are (1) the admin
> api and (2) the ability to extend via Mailets. I was intending to use James
> as a “User”, and not necessarily get involved with "development”. (I use
> quotes because I now realize that I am using my own personal definition of
> these terms, as I explain below.)
>
> I figured that my complete and utter ignorance of James actually gave me an
> advantage in that I could see things from a brand new “User’s” perspective
> that long-time community members may no longer see. I could be that annoying
> person who points out when the emperor has no clothes. 😇
>
> To that end, in the spirit of open source, I have been trying to contribute
> back in the form of writing documentation, a task that developers often don’t
> have the time or desire to do. 😆
>
> Several people have been helping me, but I would like to especially point out
> Benoit and Matthieu for their numerous interventions. Thanks!!
>
>
> Anyway, I need to ask some blunt questions that will determine how I go from
> here.
>
> First of all, I have come to the conclusion that we need a more precise
> definition of a “James User”:
>
> * What is meant by “James User” (as opposed to “Developer")?
In my opinion a user is someone running James. He don't compile nor
write James related code.
This can range from a hobbyist wanting a self hosted server to companies
relying on James.
> * What technical knowledge and skills are required of a "User" to "use"
> James?
I would expect them to have a basic knowledge of mail architecture
(protocols), and basic sysadmin skills.
> * What level of investment is required in order to “use” James?
Low. I expect them to download James, adapt ~10 lines of configuration,
run ~10 cli command and be able to use it straight away.
> * What are the infrastructure and operational requirements expected of a
> “User” to “use” James?
Ranging from laptop for demo to a (small) VM for production server.
> * What does it even mean to “use” James?
For me the term "user" refers to "running code", and should be different
from "end user" whose mail are on James and will interact with it via
mail protocols.
The fact of using James should IMO be transparent to the end user.
> Finally, what is the intention going forward regarding “Users”? To what
> extent will the James community support (or not) these “Users”?
IMO:
- Regarding "end user", we are willing to support bugs within the mail
protocol implementations
-Regarding "code runner" we should of course have a deep look on their
issue, given enough detail for issue reproduction and logs are provided.
>
> I think the answer to these questions will help me determine my path forward.
That's for sure, and I believe this is an important question.
>
> Cheers,
> =David
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
