> On Jun 4, 2018, at 9:14 AM, Christian Kratzer <c...@cksoft.de> wrote: > > having all the premium features in a separate git repo with access to premium > members only would definetely be a real "premium" feature. > > As of now the separate distribution of the premium features kind of of breaks > the transparency which is a huge advance from the closed development model of > isc-dhcp. > > I am also considering purchasing a premium package for myself and > recommending it for my customers once they migrate from isc dhcp. > > Not having git access is a step back from the free version. >
Hi Christian, Thanks for this comment. We are in some new territory with these premium hooks applications. When we started offering premium hooks, the Kea project was almost entirely un-funded, and we were facing a crisis as far as how to sustain the work. Since we have adopted the premium-features model, the situation is improving, and we now have a growing list of support customers. it is hard to say exactly whether the premium-features have enabled this or not, but it does seem to be relevant. On the other hand, managing the non-public code is certainly a pita for everyone. We appreciate your comments, and any other ideas for how to manage an open source business funded with premium features. There are other vendors, nginx is one that comes to mind, that does this, if any of you have experience with another vendor whose practices are better than ours, we are open to ideas. Regards. Vicky Victoria Risk Product Manager Internet Systems Consortium vi...@isc.org
_______________________________________________ Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
