There was great interest on our big news in recent days: clients, partners, open source community? and within Citrix itself. Everyone seems to realize that taking fully open source XenServer is a big step, and means big changes in the way we interact with the world. The overwhelming response has been very positive (which is quite a relief at this point in the game!), But there is a particular issue that keeps coming: "Who is in control of XenServer, now that it is Open Source "
The question asks in a number of ways, and it is an understandable one. Before answering, it is worth briefly explain how we arrived at this position. As we recently announced, XenServer 6.2 is now Open Source. This means that all the code is available to the wider community for its members to look at, modify, add new features and even create new products that are based on it. And this is what has led to some questions.
"If anyone can add functionality or features in XenServer," people ask, "then that control?"
The answer to this question is actually very simple, and it is this :. Citrix
"How is Citrix support the wide range of features that could be added," is the question, "and how can I be sure that the functionality I need, which I plan my business around, will continue to be there "
the answer to this is simple: Citrix XenServer is the owner of the product, and when we release a new version, it will be us - the XenServer team and, more specifically, the product management team -.. who decide what features go into it This press will be tested, documented, maintained and supported in the same way as all other versions of Citrix We are will launch roadmaps, plan with our partners and customers, and ensure that we match the functionality in the product strategy we are pursuing.
Can partners, customers, enthusiasts and others add new features to the codebase? Absolutely. They can create their own product based on this codebase, and decide to have a different set of features in their version. But this will not be Citrix XenServer and Citrix will not support it. There will be occasions where our partners and customers will add new functionality to the codebase and ask if Citrix XenServer add to the product. In fact, we already see that, and sooner than expected. We will work with them to decide whether they should be added to XenServer product, and many of them, but it will be the decision of the XenServer team. All features that are added to XenServer, either architected, designed and coded internally or externally, will be subjected to the same test regime
It should be noted that Citrix not rise to the down its engineering efforts XenServer. We still have a thriving XenServer engineering group, working on the next version (not yet teasers, I'm afraid!). The main difference in the way they work is that all they are doing now be shared with the open source community, and now they have new peers in the community who will add their own code, criticize and refine the existing code, and to make their own tests together.
We confidently expect to see the codebase XenServer expand and morph into new and exciting directions. Some of these directions, we know, will not be the central Citrix vision "for XenServer, but that's fine. Others will, and we look forward to working with the community to build an even better product within the Citrix portfolio.
0 Komentar