Attached is the final, complete Xen Trademark Policy as approved by the Xen Advisory Board and updated with your comments. Please feel free to offer any additional feedback you have as this document is meant to “live” as Xen continues to evolve.
Xen Trademark Policy June 08 in pdf
Also, the FIT discussed in the document is being worked on by the Advisory Board and I will publish the latest proposal shortly after it is reviewed by the Advisory Board.
The updated Xen Trademark Policy based on your feedback is almost complete and ready for final community inspection; however, I did get a response from Citrix about the decision to restrict usage of the Xen name in products. Please feel free to add comments or send me any questions. Thanks.
The comment from Citrix legal is as follows:
Citrix, in conjunction with the Xen AB, seeks to protect the trademarks associated with the open source Xen® hypervisor in order to both strengthen the public’s identification of the Xen marks and prevent the widespread and unregulated use that can sometimes lead to trademark genericide. This is for the benefit of all those in the Xen community who distribute and contribute to the open source project, and not just for the benefit of Citrix. It is for these reasons that the Xen Trademark Policy was originally put forward.
With respect to the limited restriction on product names combining “Xen” with another name, Citrix believes this restriction is in keeping with XenSource, Inc’s longstanding use of “Xen” in the names of the company (“XenSource™”) and its flagship product (“XenServer™”), which is now marketed by Citrix. Citrix believes, and hopes that the community understands, that use of other Xen-combined names might confuse potential users of Citrix-sourced products as to the source of a particular product or service. Since all Xen-based commercial products on the market today (of which Citrix is aware) from other vendors are all non-Xen branded, Citrix believes that this is the appropriate time to clarify this issue.
For example, an ISV may create a service for registering servers running Xen and decide to call the service “XenRegister”. A reasonable IT consumer could be confused and assume that the XenRegister service is sourced by XenSource and Citrix. Instead, the ISV could call their service, for example, “VM Registration for the Xen® hypervisor” or “MegaRegister™ for Xen®,” or any other name which is in keeping with the Xen Trademark Policy and does not reasonably confuse an IT consumer as to its source.
Ultimately, the Xen Trademark Policy benefits all those who use or assist in the development of the Xen® hypervisor, in part by maintaining the value of the Xen Marks. Citrix must police the marks in accordance with the Policy and in conjunction with the Xen AB in order for everyone to see value in their use as product identifiers. Otherwise, the trademark can become a generic term (see escalator or aspirin in the U.S.) at which point anyone could call their hypervisor “xen” regardless of the source of the hypervisor.
Attention all interested speakers for Xen Summit Boston – tomorrow at 5pm PDT will be the official close of topic submissions. Anyone still wanting to present at the event should have their topic and short abstract submitted to firstname.lastname@example.org by 5pm PDT tomorrow. We have received 30+ topics for the event and the Program Committee has an excellent set of proposed topics to put together a fantastic event. There is still time to submit your topic but I will be closing acceptance tomorrow so the final agenda can be compiled.
The first meeting of the Xen API Community Project has been completed and meeting minutes are available in the Xen Wiki at http://wiki.xensource.com/xenwiki/XenApi#preview. A follow-up meeting will be scheduled for later this month or early June to discuss the existing Xen API specifications with an emphasis on comparing them to the Citrix XenServer API definitions available at http://community.citrix.com/display/cdn/XenServer%20SDK. Anyone interested in assisting in this project is encouraged to review the API specifications in preparation for the next meeting.
For those of you who read my blog posting on ending software patents, you might want to read the overview from several people on what happened at the Courthouse for this case. The link is http://www.groklaw.net/article.php?story=20080508231813484.
The case is State Street Bank vs Signature Financial Group and involves the following:
From the Electronic Frontier Foundation: “An appellate court case that provides an opportunity to eliminate business method patents and curtail efforts to claim monopolies on basic human skills, behaviors, and interactions. Bilski is challenging the rejection of his application for a patent on a method of managing the risk of bad weather through commodities trading.”
I am pleased to announce that we have over 50 people registered for Xen Summit Boston with attendees coming from 7 countries – India, Israel, Japan, South Korea, Sweden, UK, & US. Over 30 topics were submitted to the Program Committee who are actively reviewing the requests and working on a putting together an excellent agenda. I anticipate final publication of the agenda later this month, but the current approved topics list is at http://xen.org/files/xensummitagenda.pdf.
Make sure you are registered for Xen Summit as this event looks to be an exciting, in-depth immersion in all things Xen!