Hunter,
If you simply want to fork the repository and use it in your company,
respecting the Apache license then in my opinion there is no issue.
As Christopher said problems will arise if you redistribute that code or
binaries outside the limits of Apache license, call it 'Zookeeper'...
We are re
Hi Hunter,
A public fork is certainly an option under the Apache License. Many
contributors maintain their own public forks on GitHub to enable them
to contribute via a pull request on GitHub. While most contributors
don't build and reproduce artifacts from their forks, they could do
so, in theory
It is totally fine to release modified versions of Zookeeper.
Just don't call it Zookeeper. You can (and likely should) say that it is
based on (or powered by) Zookeeper, but don't claim it is the same thing if
it isn't.
But are you sure that you wouldn't really rather contribute directly to
Zook
Hi ZooKeeper devs -
I wanted to get an opinion on public, open-source forks of ZooKeeper. I am
aware that there are companies maintaining private or public forks of ZooKeeper
to deploy & develop their own flavor of ZooKeeper (or ZooKeeper + alpha), like
to have a public fork with our own potent
