We have an open source tool that we want to deliver to users with a specific JRE version. As Oracle is so unclear and closed with licensing (even with newest jlink possibilities), and unofficial openjdk builds are so hard to "follow", we think that Zulu can be the right alternative here. Thus the only worry I have:
Can I freely redistribute this JVM in my distributions? It's nothing more than having a /jre directory in my distribution and making start-up scrips going for provided JVM instead of the system default.
The Zulu Terms of Use are not 100% clear here:
You also represent and warrant that you do not intend to distribute the software in a manner that is not compliant with relevant export control laws or regulations administered by the U.S. Commerce Department, OFAC, or any other government agency.
This question comes up regularly with software developers wanting to redistribute Zulu with their applications. The specific item in the Terms of Use you highlighted calls out specific export controls to remind you of the implications that every Java SE distribution from any vendor including Azul has some cryptography features inside in. Because of that fact, you should be aware of US export laws, and that many countries have import restrictions, too. Zulu does not have any field of use restrictions, though we needed to assert the statement about export in the ToU.
We typically share the details of what it means to redistribute Zulu through our Zulu Embedded offering. I make several points why it is at least worth a call to Azul to discuss alternatives in my forum post here: http://zulu.org/forum/thread/bundle-zulu-community-jre-with-our-product/ If you are doing anything other than open source software, there are potential pitfalls redistributing community binaries. Azul can help clarify your risks.
Matt
Disclaimer: I am the Zulu product manager at Azul, though this response reflects my personal opinions.