From: Lars Kurth <lars.kurth@xen.org>
To: lars.kurth@xen.org
Cc: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>,
"xen-users@lists.xen.org" <xen-users@lists.xen.org>,
"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all)
Date: Mon, 13 May 2013 13:11:01 +0100 [thread overview]
Message-ID: <5190D855.2020608__25214.3419850201$1368447234$gmane$org@xen.org> (raw)
In-Reply-To: <5190C0BC.5060008@xen.org>
On 13/05/2013 11:30, Lars Kurth wrote:
> Dear Community Members,
>
> ... To avoid voting fatigue, several proposals are up for review or
> voting:
I created a slight confusion here by taking the blog post at
http://blog.xen.org/index.php/2013/05/13/xen-project-governance-changes-for-review-and-vote/
and not removing "for review" from it.
The *only* proposal that is for review has been sent out separately on
friday to xen-devel and xen-users named "[Final Community Review] Xen
Security Problem Response Process v2" (see
http://lists.xen.org/archives/html/xen-devel/2013-05/msg01243.html). All
proposals in this mail are for voting, with the original discussions
x-reffed in
http://blog.xen.org/index.php/2013/05/13/xen-project-governance-changes-for-review-and-vote/
Regards
Lars
next parent reply other threads:[~2013-05-13 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5190C0BC.5060008@xen.org>
2013-05-13 12:11 ` Lars Kurth [this message]
2013-05-20 9:17 ` [Xen-users] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) Ian Campbell
[not found] ` <1369041476.2083.26.camel@zakaz.uk.xensource.com>
2013-05-21 9:06 ` Lars Kurth
2013-05-13 10:30 Lars Kurth
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='5190D855.2020608__25214.3419850201$1368447234$gmane$org@xen.org' \
--to=lars.kurth@xen.org \
--cc=xen-api@lists.xen.org \
--cc=xen-arm@lists.xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.