From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Xen-devel <xen-devel@lists.xen.org>,
appointments@xenproject.org, advisory-board@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
sstabellini@kernel.org, WeiLiu <wei.liu2@citrix.com>,
George Dunlap <george.dunlap@citrix.com>
Subject: Shortlist of people for Committer and Security Team member election
Date: Wed, 6 Apr 2016 11:43:31 +0100 [thread overview]
Message-ID: <B42487CD-ED73-42EF-9BA7-AF91D95FE763@gmail.com> (raw)
Dear Community members,
you may remember the following e-mail called "Call for nominations for new
Hypervisor subproject maintainers and committers" (also see
http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg03459.html)
We had quite a few nominations for maintainers, committers as well as
security team members. We created a shortlist of maintainers based on
community input, discussed the shortlist and asked the future maintainers
on the shortlist to put forward changes to the MAINTAINERS file following
the normal process. This has mainly been done, but a few are still
outstanding.
We will also tidy up REST maintainership, after committers have been
confirmed.
For committers and security team members, the existing committers and
security team members put together a short list based on nominations,
verified with the nominees, whether they have the time going forward to
fulfil their respective roles and commitment.
== Committer Shortlist ==
The following people are on the shortlist for committers
- Andrew Cooper: focus area on the hypervisor
- George Dunlap
- Stefano Stabellini: focus area on ARM
- Wei Liu: focus area tools (alongside Ian Jackson)
== Security Team Member Shortlist ==
The following people are on the shortlist for security team membership
- Andrew Cooper
- George Dunlap
== Providing Feedback ==
We are inviting community members to provide comments regarding the
shortlist. As feedback may be personal and may make nominees
uncomfortable, we are asking you to provide feedback by sending a
private mail to appointments at xenproject dot org *before* April 13th,
2016 (please do *not* CC xen-devel@).
If you want to congratulate people on the shortlist, it is of course
OK to do this in public. Please use your judgement and common sense.
== Next Steps ==
Committers and security team members will review any feedback and will vote
to confirm people on the shortlists shortly after April 14th. As some of us
will be out-of-office the week before the Hackathon, I expect that we will
be able to confirm nominees at the latest during the Hackathon.
Best Regards
Lars Kurth
Xen Project Community Manager
Chairman of Xen Project Advisory Board
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2016-04-06 10:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B42487CD-ED73-42EF-9BA7-AF91D95FE763@gmail.com \
--to=lars.kurth.xen@gmail.com \
--cc=advisory-board@lists.xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=appointments@xenproject.org \
--cc=george.dunlap@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).