Hello all, I am having a look at simplifying some community related documents on my spare time. Especially the README and the download page.
I hope that by getting things more concise we would be more engaging to the users. Here are some suggestions for the download page: - Remove mirror section: download links point to https://www.apache.org/dyn/closer.lua/james/* already handling this - File integrity verification: again above link handles it and we can link https://www.apache.org/info/verification.html to not repeat stuff - stick with ASF best practices. - Avoid referencing the archive - I am not sure that is a best practice. Now there is some explicit mentions regarding cryptography - even mentioning Java runtime... While I understand the US law constraints, I see that major other ASF projects do not take such care on their download pages despite doing some SSL cryptography too (Cassandra, Spark, pulsar.) Even older, and more crypto-oriented projects (https://commons.apache.org/proper/commons-crypto/download_crypto.cgi) don't do it. As such I don't see why we should keep such (polluting) information on our download page. It just gets our users away from their contents, and they need to scroll to get to server downloads, even on a 1024p scree... (Crypto notice are already embedded in the downloadable artifacts). Is there some objections on removing the crypt-notices? Cheers, Benoit --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
