This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Xen.org Governance Proposal

To: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] Xen.org Governance Proposal
From: Lars Kurth <lars.kurth@xxxxxxx>
Date: Wed, 11 May 2011 10:22:15 +0100
Delivery-date: Wed, 11 May 2011 02:22:29 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:content-type; bh=Rt1uFiQSmfu0VLKnN4Z8sE29lf4zDCkNmj6nSD0bOZc=; b=BtTEtio+2mL8RgO5GDlE6IuXfvDfZaR5NmrMEOsLIzAR6HFDQRTS3F/xfiPrJJdfCu fTxSDcM7zA5ggYcNzc0wjk7fOtIn9hH6UxmN+yiMK7TrZPGu41cRs9jHY3D22TI/RJ/U 6EPtAzmmAm7ezWLoImzh5DRuSz3N4b8OMBbFA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :content-type; b=nLGnP7WGGeWHijAmsLIX00NDrSK+uMlpsHwaSKsP6+tnGQ+BoZeBCi5s9Fy6iTejjv VIO1nstglWKWtTauUXTh53F+CbqjL7N79Qqubz/0ztYSa1f88V8zFVy/R1mNG0KJ7PPF rmvxqoahais6qJwUwRjz1QPiPSNKU05bhWr6s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv: Gecko/20110414 Thunderbird/3.1.10

one of the objectives that I was given, when I started as Xen.org community manager was to learn about the unwritten rules of how Xen.org governance works, write them down and make some improvement proposals. At this point, I wanted to present my findings and also make an improvement proposal. Governance changes can be quite divisive, which is why we are going to consult you and ask for input. The proposal has already been reviewed by key stake-holders in the community and by the Xen Advisory Board. The feedback we have received, has so far been positive.

The detailed proposal can be found on http://www.xen.org/files/Proposals/XenGovernanceProposal1.pdf and essentially consists of three parts:

  • Basic principles describing how the community works: these are Openness, Transparency, Meritocracy and Consensus Decision Making
  • Key roles in the community: these are Maintainers, Project leads and a lightweight nomination and election process
  • A lightweight project life cycle that shows how a project gets from an idea to maturity and is eventually archived. There is also a section on how this works in practice.

If you are a contributor to Xen.org or an otherwise active community member, please review the preoposal (http://www.xen.org/files/Proposals/XenGovernanceProposal1.pdf). We also created a poll (http://www.xen.org/polls/governance_proposal1.html) to find out whether the proposal resonates with you. The poll will be open for 4 weeks (until Jun 7th).

Best Regards
xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] Xen.org Governance Proposal, Lars Kurth <=