The last Wednesday of the month is Xen Project Document Day! Join us as we seek to make our documentation better. Go to our Document Day page for instructions.
Today, Citrix announced that XenServer would be fully open sourced and that it will be made available from XenServer.org. This document explores how the Xen Project is impacted by this announcement.
I am a XAPI developer: How am I impacted?
The short answer is: not at all. Contribution to the XAPI packages continues to be handled by the Xen Project under Xen Project governance. The XAPI project will make some changes to how it operates, but any changes will follow Xen Project community rules, will be discussed openly and made using the Xen Project decision making process. In fact discussions on consolidating mailing lists, how to release XAPI, etc. had already started several weeks ago.
How will XAPI sub-project Development Change?
The XAPI project plans to change how it develops and releases XAPI components (as initially discussed at the Xen Hackathon). To summarize, the following changes are being discussed in the community:
- Change the release from an infrequent XCP ISO release to a source release that is identified by a unique version number and provide a convenient mechanism for distros to consume the release (e.g. a tarball).
- Increase the release frequency : publish a build every other week (aka a sprint) and provide a release every 3 months
- Publish what is planned to go into the next few sprints as information becomes available
- Contribution to the project will happen via the project’s Github instance (as now)
Note that this discussion has not yet concluded: feel free to join! Other changes that are currently being discussed are about mailing lists for the project, how to raise bugs, etc.
I am a user of XAPI Linux packages: How am I impacted?
The short answer is: not at all. Development of the XAPI toolstack and the packaging of these components continue as part of the Xen Project. However, there will not be an immediate update of the XCP-XAPI packages in Linux distros. Before there can be an update to these packages, the XAPI project team needs to deliver an independent XAPI release. For more information check the “What’s next”section below. Discussion, questions and bug reports for XCP-XAPI packages can be made on the appropriate distro mailing lists and on Xen Project mailing lists, IRC channels or the Q&A system.
I am a user of XCP: how am I impacted?
In the past, XCP ISOs have been built by Citrix and have been delivered to users via Xen.org. The XCP ISOs were migrated to the Xen Project. By fully open sourcing XenServer, the need to deliver new XCP ISOs via the Xen Project website has gone away. XCP ISOs will be replaced by open source XenServer binaries which are available from XenServer.org. The transition from XCP ISOs to XenServer should be smooth and painless:
- No functionality will be taken away from XCP users
- Users of XCP 1.6 will be able to upgrade to XenServer
The main difference for you will be that you need to download the product from a different place and that it has been renamed. XCP users have been supporting each other through mailing lists (email@example.com) and the #xen-api IRC channel. These mechanisms will of course not go away, but we hope that you will find the resources on XenServer.org useful.
The Xen Wiki has been subject to a severe spam attack for several months and attempts to address this via different CAPTCHA mechanisms available for MediaWiki have been unsuccessful. To solve this and keep the wiki usable for everyone, we had to lock down the wiki and create an editors group.
To become an editor, please:
- Create a wiki account via this link (if you do not have one)
- Write down your wiki username. Note that we cannot look up your wiki username from your e-mail address.
- Fill in the information below. The e-mail address helps us follow up in case there is a problem
This document has come in effect in May 2013 and will be reviewed periodically (see revision sections).
List Naming Conventions
In the past the Xen Project has named mailing list in an ad-hoc fashion, which has sometimes caused confusion amongst it's user base. This document intends to create clarity when new lists need to created.
Project and team lists
The Xen Project encompasses several sub-projects, which we also refer to as teams. Each team - depending on its size - can have on or several mailing lists. The general convention for lists specific to a team is to the following pattern:
Team prefix and list descriptor are encoded in lower case.
The following prefixes are in use now:
Examples of list descriptors are:
- This is a general list for users and developers
- This is a development list only
- This is a user list only
- This is list to publish Git changelogs
General Purpose Lists
Mailing lists, whose scope is not restricted to a team or sub-project but encompass the entirety of the Xen Project, adhere to the following pattern:
Again list descriptor are encoded in lower case.
Examples of list descriptors are:
- This is the discussion list for the Xen Project Advisory Board
- This is a low volume announce list for the Xen Project
- This is a list to coordinate content for the Xen Project blog and other media, for press, for event presence, etc.
- This is a list to report security vulnerability in Xen Project software
Xen Project community members conduct email discussions on public mailing lists whenever possible and allow the general public (including search engine indexes) to be privy to the discussion. Further, all Xen project mailing lists are generally open to all community members to join as well as to post. Also, mailing list archives are generally accessible to all.
There are however a few exceptions:
- Subscribe only lists
- A number of lists, such as the ANNOUNCE and CHANGELOG lists are subscribe only lists
- Invite only lists
- A number of lists, such as the ADVISORY BOARD and SECURITY list, are invite only lists. These lists are for teams within the community that are by appointment only.
- Private lists
- In some cases confidentiality expectations and requirements prevent list traffic from being published. Examples are lists related to security vulnerabilities.
Special Mailing Lists
This list is for maintainers of all Xen teams, and key developers that have been invited by maintainers. This list is intended to be used only when privacy implications or similar prevent usage of a public list. Example usage may be to let other community members know of absence (due to holidays, maternity/paternity leave, etc.) and to arrange cover. Another example may be to ask other team members for advice on how to respond to a difficult situation in the community. This list is invite only and is not archived.
- v1.0 May 2013: Intial document approved