I am lurking a bit within that interesting conversation and might only answer some points I might have something to propose.
This thread discusses what we try to do as a project. In my previous post on this list, I (tried to) explain the legacy behind the James project goals. But I of course agree rationalizing the James project goals to align it with what the current contributors try to deliver. Now branding being definitely funny: On 25/05/2020 03:54, Matthieu Baechler wrote: > [..] > Another point is "Enterprise": I think that any "Enterprise" software is > suspicious at best. Free Software should empower anybody. So I would > propose to drop that word. Coffee thoughts: We could very well change the "e" meaning in the James acronym too. Something like `JAva Mail Extensible Server/Solutions` ? > Finally, I think that Java is not a selling point any longer, the JVM is. > So I would rather propose "JVM Mail Server". I globally agree with this point, that converges with the growing usage of Scala programming language within the code base. Do you think we could keep the acronym `James`? A quick search on google for adjective starting by `A` lead to the following results: - `Adaptable` enforces the idea you can adapt James to your needs. However I would see it as a duplicate of the `Extensible` mentioned above. - `Advanced` is a bit more boiler plate.... - <joke>awesome</joke> :-) > > Coming back to the documentation: James is pointless without (at least) > Mailets. I would focus the documentation mainly on the Mail Server target > and would promote customization as a top-level concept of it. > > My 2 cents > > Cheers, > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
