Re: [Xen-devel] [Vote] Approve hypervisor project check-in policy
> On Jan 27, 2020, at 2:12 PM, George Dunlap wrote: > > I have drafted an explicit policy on what is (generally) required to > check a patch in. It's been through several rounds, and v4 has been > acked [1]. > > I've had informal assent from all committers, but just to dot all our > i's and cross all our t's, it's probably worth having a vote of the > committers, in line with the XenProject governance policy [1]. > > Please respond by 10 February with your vote: > +1: for proposal > -1: against proposal > in public or private. By my count we have 4 +1’s and no objections, so the policy is approved. I’ll check in the patch modifying MAINTAINERS. -George ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Vote] Approve hypervisor project check-in policy
Hi all, +1. Cheers, On 27/01/2020 14:12, George Dunlap wrote: I have drafted an explicit policy on what is (generally) required to check a patch in. It's been through several rounds, and v4 has been acked [1]. I've had informal assent from all committers, but just to dot all our i's and cross all our t's, it's probably worth having a vote of the committers, in line with the XenProject governance policy [1]. Please respond by 10 February with your vote: +1: for proposal -1: against proposal in public or private. Thanks, -George [1] https://marc.info/?i=<20200113150455.400733-1-george.dun...@citrix.com> [2] https://xenproject.org/developers/governance/ ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel -- Julien Grall ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Vote] Approve hypervisor project check-in policy
On Mon, Jan 27, 2020 at 03:27:40PM +0100, Jan Beulich wrote: > On 27.01.2020 15:12, George Dunlap wrote: > > I have drafted an explicit policy on what is (generally) required to > > check a patch in. It's been through several rounds, and v4 has been > > acked [1]. > > > > I've had informal assent from all committers, but just to dot all our > > i's and cross all our t's, it's probably worth having a vote of the > > committers, in line with the XenProject governance policy [1]. > > > > Please respond by 10 February with your vote: > > +1: for proposal > > -1: against proposal > > in public or private. > > +1 > > As an aside, I notice you may want to update your address book. I've > corrected Wei's and Julien's email addresses. Thanks. +1 to this proposal. Wei. > > Jan ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Vote] Approve hypervisor project check-in policy
On 27/01/2020, 14:12, "George Dunlap" wrote: I have drafted an explicit policy on what is (generally) required to check a patch in. It's been through several rounds, and v4 has been acked [1]. I've had informal assent from all committers, but just to dot all our i's and cross all our t's, it's probably worth having a vote of the committers, in line with the XenProject governance policy [1]. Please respond by 10 February with your vote: +1: for proposal -1: against proposal in public or private. George: in this case - as it is not a Xen Project wide policy - the voting options are a bit wider +2 : I am happy with this proposal, and I will argue for it +1 : I am happy with this proposal, but will not argue for it 0 : I have no opinion -1 : I am not happy with this proposal, but will not argue against it -2 : I am not happy with this proposal, and I will argue against it See https://xenproject.org/developers/governance/#decisions Leadership Team Decisions For project wide decisions we ended up with a simpler and different scheme Lars ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [Vote] Approve hypervisor project check-in policy
On 27.01.2020 15:12, George Dunlap wrote: > I have drafted an explicit policy on what is (generally) required to > check a patch in. It's been through several rounds, and v4 has been > acked [1]. > > I've had informal assent from all committers, but just to dot all our > i's and cross all our t's, it's probably worth having a vote of the > committers, in line with the XenProject governance policy [1]. > > Please respond by 10 February with your vote: > +1: for proposal > -1: against proposal > in public or private. +1 As an aside, I notice you may want to update your address book. I've corrected Wei's and Julien's email addresses. Jan ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] [Vote] Approve hypervisor project check-in policy
I have drafted an explicit policy on what is (generally) required to check a patch in. It's been through several rounds, and v4 has been acked [1]. I've had informal assent from all committers, but just to dot all our i's and cross all our t's, it's probably worth having a vote of the committers, in line with the XenProject governance policy [1]. Please respond by 10 February with your vote: +1: for proposal -1: against proposal in public or private. Thanks, -George [1] https://marc.info/?i=<20200113150455.400733-1-george.dun...@citrix.com> [2] https://xenproject.org/developers/governance/ ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
