Hello Huy,
Concerns with the governance of the project, if needed, shall be
discussed on the Apache James private list ( priv...@james.apache.org ).
That's really unfortunate that a long standing bug on an experimental
documentation gives you this impression.
I am committed to enforce an open, inclusive governance of the James
project, and invested many hours, most of them on my personal time, to
improve James documentation.
Best regards,
Benoit TELLIER
On 06/03/2023 15:01, Huy Van wrote:
Hi Benoit,
Please understand how feeling is when the docs get disappeared and require
to look at source while studying on configuration. It made me think that
open source James was not the sense of freedom anymore.
I do understand your team's efforts to build open source James and how does
it feel about my declaration. I highly appreciate such efforts.
And finally, I hope this is just a confusion, bug.
Best regards,
Huy
Vào 13:29, T.2, 6 Th3, 2023 Benoit TELLIER <btell...@apache.org> đã viết:
Hi huy,
I suggest reading the ASF code of conducts [1]. I believe this email is
not compliant on several points.
Best regards,
Benoit
[1] https://www.apache.org/foundation/policies/conduct.html
On 06/03/2023 10:48, Huy Van wrote:
Hi,
You can take a look at my previous messages on mailing list:
https://www.mail-archive.com/server-user@james.apache.org/msg16663.html
.
I was suggested to go to that site. As you can see the mentioned link is
parent folder describing necessary parameter configuration, webadmin api
example. The documents have been no longer accessible after a few hours
since the suggestions.
This's fastest way to realize that spending on Apache James is
time-wasting.
Regards,
Huy Van
Vào 08:26, T.2, 6 Th3, 2023 tungtv...@gmail.com <tungtv...@gmail.com> đã
viết:
Hi Huy Van,
Where are you get this link?
>
https://james.staged.apache.org/james-distributed-app/3.7.3/operate/
On 06/03/2023 00:50, Huy Van wrote:
Hi everyone at open source Apache James,
This is to notify that James is similar to a closed source project.
Necessary documents at
https://james.staged.apache.org/james-distributed-app/3.7.3/operate/
are
currently not found (404). Documents on James website are outdated with
the
latest build.
Configuring James now for new users requires to look into source code,
logic, which is a crazy idea. Yes, it's always easier with technical
services behind James, but how to be sure that there are no
"unexpected"
errors occur during operation in the future, when valuable data going
huge.
I concern this because james's been contributed & maintain mostly by
companies providing technical services on James.
If any companies are not at Google, Microsoft, etc level, it's better
to
build own distributed business-logical mail system based on postfix,
dovecot, familiar db shard & replication, etc. It's peace of mind and
faster building than current document-hidden Apache James.
It's not too difficult unless you want. Hope James project is great in
the
future.
Regards,
Huy Van
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
