From: Lars Kurth <lars.kurth@citrix.com>
To: George Dunlap <George.Dunlap@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [PATCH v2 3/3] Significant changes to decision making; some new roles and minor changes
Date: Tue, 13 Sep 2016 16:57:44 +0000 [thread overview]
Message-ID: <D3FDEDEA.2DC2C%lars.kurth@citrix.com> (raw)
In-Reply-To: <acc7ca0c-537d-02d3-7bfc-1577dcf36d58@citrix.com>
On 13/09/2016 17:46, "George Dunlap" <george.dunlap@citrix.com> wrote:
>On 12/09/16 17:20, Lars Kurth wrote:
>> Added RTC Policy
>> Added +2 ... -2 scheme for votes
>> Clarified lazy consensus (tallying and lazy voting)
>> Added Informal Votes/Surveys
>> Added Project Team Leadership role and Decision making
>> Added Community Decisions with Funding and Legal Implications
>> Changed Project Wide Decision making: per project based scheme
>> Clarified scope of Decision making
>
>Hey Lars,
>
>Would it be possible to break some of these down into separate patches?
>This is an awfully long "patch" to review all at once; and it seems like
>it would be nice for you as well to be able to get Acked / Reviewed-by's
>for some of the smaller and/or less contentious items as you go along.
I could, but it isn't really that long. And it makes life hard for me, as
there is only one file. Thus breaking it into bits and maintaining the
changes is hard in git.
Also, it is unclear whether we need to follow the regular process, as
technically we need to have a vote on the final proposal.
>There are a number of sections of this that I have read and basically
>approve of; a number that I have read and am still thinking about or
>some comments on; and a number that I haven't grokked yet and will want
>to do later. (I'll think for a bit and maybe come back to this later
>this week.)
Thanks
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-13 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 16:20 [PATCH v2 0/3] Significant changes to Xen Project Governance (governance.html) Lars Kurth
2016-09-12 16:20 ` [PATCH v2 1/3] Code motion changes to make real patches easier to read Lars Kurth
2016-09-12 16:20 ` [PATCH v2 2/3] Added comment sections to highight problem areas Lars Kurth
2016-09-12 16:20 ` [PATCH v2 3/3] Significant changes to decision making; some new roles and minor changes Lars Kurth
2016-09-13 16:46 ` George Dunlap
2016-09-13 16:57 ` Lars Kurth [this message]
2016-09-19 14:01 ` Ian Jackson
2016-09-19 14:46 ` Lars Kurth
2016-09-19 15:36 ` Ian Jackson
2016-09-20 17:01 ` Ian Jackson
2016-09-20 18:53 ` 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=D3FDEDEA.2DC2C%lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=committers@xenproject.org \
--cc=xen-devel@lists.xenproject.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).