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")? * What technical knowledge and skills are required of a "User" to "use" James? * What level of investment is required in order to “use” James? * What are the infrastructure and operational requirements expected of a “User” to “use” James? * What does it even mean to “use” James? Finally, what is the intention going forward regarding “Users”? To what extent will the James community support (or not) these “Users”? I think the answer to these questions will help me determine my path forward. Cheers, =David
signature.asc
Description: Message signed with OpenPGP
