3 ms·

>Not sure what the answer is here, but I do feel that if you are a money making business, buying servers for thousands, a percentage of that should go to the so

by tw04 9y ago

>Not sure what the answer is here, but I do feel that if you are a money making business, buying servers for thousands, a percentage of that should go to the software you use to make those servers useful. Totally respect where you're coming from - but at some point isn't that kind of their problem? It's not your job to monetize it for them. I respect them making this move, however I think they had better options. Part of their problem is it's TOUGH to go from giving something away to monetizing. At the same time the people like you who were making a profit off of it probably will begrudgingly pay for the upgrade. I think they should've gone the Redhat route - where they only release source to patches between releases. If you REALLY want to apply the code and build the new binaries yourself, so be it. If you find value in them writing and providing the patches - pay for it. There is no perfect answer, but I think the people calling for their heads are being a bit silly. I have no doubt the two options were: make this change, or kill the project entirely. ESPECIALLY in the face of Amazon moving away from Xen - I would imagine there was some back-end funding going on there.

keepper 9y ago
Oh of course, but I'm a big believer in social contracts. What can I say :) - Citrix used to have XCP ( Xen Cloud Platform ), as a way of OSS the core functionality away from the paid functionality. They moved to one build in the possibly naive thought that making licensing a feature of a support contract, would enforce a social contract of "hey, why not pay these guys". That did not work. I think AWS moving away from XEN is a bit moot. While AWS did contribute back some to XEN, they mostly forked it for their use case. They are doing the same with KVM. Citrix has been by enlarge, the majority contributor to XEN.

by tw04 9y ago

keepper 9y ago

Oh of course, but I'm a big believer in social contracts. What can I say :) - Citrix used to have XCP ( Xen Cloud Platform ), as a way of OSS the core functionality away from the paid functionality. They moved to one build in the possibly naive thought that making licensing a feature of a support contract, would enforce a social contract of "hey, why not pay these guys". That did not work. I think AWS moving away from XEN is a bit moot. While AWS did contribute back some to XEN, they mostly forked it for their use case. They are doing the same with KVM. Citrix has been by enlarge, the majority contributor to XEN.