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] Please welcome Jan Beulich as Xen committer & revisions to Xen

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>, xen-arm@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Please welcome Jan Beulich as Xen committer & revisions to Xen governance
From: Lars Kurth <lars.kurth@xxxxxxx>
Date: Fri, 30 Sep 2011 12:16:35 +0100
Delivery-date: Fri, 30 Sep 2011 04:17:01 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Ze5tiMKpwzhjPLmU1/Ylv5nF1fBNr3ZmtqKY9IbDrPc=; b=fvg0L/Z3hbhLXi/Pmx3hfExt07uHvDeidEUtxkgKtM2D8jvhP3XON1r0MQDGvFnVLR wq0XWToMcKgrFQ5DHcFkDQuy0G+PdGZU4fUjK2suO7nvEVze+CiLn/D9/oyVnYgPy0TT QNQQfdOK4qq6BaDB02HjtQ8YUYYqZgo06ZX+0=
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 NT 6.1; rv:7.0) Gecko/20110922 Thunderbird/7.0
Dear Xen developers,

I wanted to announce that Jan Beulich has been nominated for as Xen Hypervisor committer and confirmed by vote by the other Xen committers (which are Keir Fraser, Tim Deegan and Ian Jackson).

Jan's Contribution
Jan has made a tremendous contribution to the project over the years and was was one of the top 3 contributors to the project for several years. Just to quote a few stats
- 2009 : 107 patches changing 11746 lines of code
- 2010 : 147 patches changing 7613 lines of code
- 2011 : 204 patches changing 2655 lines of code


I do have to apologize that we did not entirely follow the new governance process as described at http://www.xen.org/projects/governance.html due to an oversight. The nomination and vote was meant to happen in public, but has happened in private amongst the existing committers. We will do better next time. This exercise has also shown some bugs in the process which need fixing.

Bugs in the Process
See http://www.xen.org/projects/governance.html)

Committer vs. Maintainers: The process talks about maintainers as if they were committers and mixes some aspects of both roles. This is incorrect.

- Split the role into two
- What is a maintainer?
  - A maintainer owns one or several component in the Xen tree
  - A maintainer reviews and approves changes that affect their component
- Note that some components will be owned by several maintainers (in that case consensus
    decision making applies)
- Election: new maintainers are nominated and voted for by other maintainers
- What is a committer?
  - A maintainer with write access to the code tree
- The committer acts on the wishes of the maintainers and applies changes approved
    by the respective maintainer(s).
- Helps resolve disagreements between maintainers of the same component should they arise - Election: new committers are nominated and voted for only by other committers
- Allow a committer to be a sponsor for a new Xen.org project
- Reflect above changes in Elections
- I believe we should keep "Project Lead Elections" as it is
(We could restrict elections to committers, but in practice committers will have a much higher chance to be elected. I believe we should leave things as they are.)

Please let me know your views, by responding to this thread. If there are no objections by next friday, Oct 7th, we will just update the document. And then give another week for additional discussion and the change will be considered approved.


xen-api mailing list