After concluding our poll about changes to the security discussion, we determined that “Pre-disclosure to software vendors and a wide set of users” was probably the best fit for the community. A set of concrete changes to the policy have now been discussed on xen-devel (here and here), and we seem to have converged on something everyone finds acceptable.
We are now presenting these changes for public review. The purpose of this review process is to allow feedback on the text which will be voted on, in accordance to the Xen.org governance procedure. Our plan is to leave this up for review until the third week in January. Any substantial updates will be mentioned on the blog and will extend the review time.
All feedback and discussion should happen in public on the xen-devel mailing list. If you have any suggestions for how to improve the proposal, please e-mail the list, and cc George Dunlap (george dot dunlap at citrix.com).
Read on for a summary of the updates, as well as links to the full text of the original and proposed new policies.
Summary of the updates
As discussed on the xen-devel mailing list, expand eligibility of the pre-disclosure list to include any public hosting provider, as well as software project:
- Change “Large hosting providers” to “Public hosting providers”
- Remove “widely-deployed” from vendors and distributors
- Add rules of thumb for what constitutes “genuine”
- Add an itemized list of information to be included in the application, to make expectations clear and (hopefully) applications more streamlined.
The first will allow hosting providers of any size to join.
The second will allow software projects and vendors of any size to join.
The third and fourth will help describe exactly what criteria will be used to determine eligibility for 1 and 2.
Additionally, this proposal adds the following requirements:
- Applicants and current members must use an e-mail alias, not an
- Applicants and current members must submit a statement saying that
they have read, understand, and will abide by this process document.
The new policy in its entirety can be found here:
For comparison, the current policy can be found here: