-
FEATURED COMPONENTS
First time here? Check out the FAQ!
We have a very large open source project based on ZK and use features from the enterprise edition. While we have a ZK open license that allows us to access the EE artifacts via the ZK private repo, this requirement is a significant barrier to adoption by the open source community. I would urge ZK consider adopting a model that is used by many other dual licensed technologies where all artifacts are publicly available with commercial use being constrained by the license. This would greatly simplify access to advanced features without jeopardizing your business model.
Again, why not just put all of the ZKEE artifacts in Maven Central with clear license terms for commercial use? This is consistent with other dual license technologies and does not require any special configuration for consumption of the artifacts.
Asked: 2014-09-12 02:16:37 +0800
Seen: 21 times
Last updated: Nov 17 '14
Do you mean put EE evaluation artifacts to Maven central? Would please describe more detail about what kind of barrier you encounter when you use ZK private repo?
hawk ( 2014-09-15 02:15:41 +0800 )editIt is not a barrier for us, as we have taken steps to acquire the necessary access. For many interested in our platform, the steps necessary to gain access to the EE artifacts are a showstopper and run counter to the spirit of open source.
martindk ( 2014-10-07 01:39:54 +0800 )editfor evaluation purposes the EE artifacts are available in the eval repository e.g. http://mavensync.zkoss.org/eval/org/zkoss/zk/zkmax/7.0.3-Eval/ there you can access the latest nightly (FL) builds without a barrier, just with an uptime limitation, ideal for getting familiar with the EE features.
cor3000 ( 2014-10-21 01:17:08 +0800 )edit