From: "Jon Benedict" <Jon.Benedict(a)netapp.com&gt; To: "Mike Burns" <mburns(a)redhat.com&gt;, "board" <board(a)ovirt.org&gt;, "arch" <arch(a)ovirt.org&gt; Sent: Wednesday, September 5, 2012 11:06:04 AM Subject: Re: New Role Proposal in the oVirt Project On 9/5/12 10:57 AM, "Mike Burns" <mburns(a)redhat.com&gt; wrote: >Given some of the difficulties we've had recently with planning and >getting releases pulled together, I'd like to propose we have a new >role >in the Project. > >Project Manager > >Responsibilities: > >Maintain Schedule >Run weekly meeting >Coordinate with project maintainers on dates, features, etc >Ensure that docs and release materials are ready for release >Final say on what goes into a release >Tracking new features >Tracking action items > >This person should be empowered to make decisions for the project >(based >on input from maintainers, but final call is theirs). > >As for choosing this person, it could be done via general election >on >email or an IRC meeting. I'd suggest having someone do it for a >limited >timeline, maybe 2 or 3 releases, max, then someone else takes over. > >Any thoughts, suggestions, comments?

Mike, I'm definitely in favor of a PM. I like the 2-3 term requirement, but if they want to serve again it should be an option (subject to re-election). Jon _______________________________________________ Board mailing list Board(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/board

----- Original Message ----- > From: "Jon Benedict" <Jon.Benedict(a)netapp.com&gt; > To: "Mike Burns" <mburns(a)redhat.com&gt;, "board" <board(a)ovirt.org&gt;, "arch" <arch(a)ovirt.org&gt; > Sent: Wednesday, September 5, 2012 11:06:04 AM > Subject: Re: New Role Proposal in the oVirt Project > > On 9/5/12 10:57 AM, "Mike Burns" <mburns(a)redhat.com&gt; wrote: > > > >Given some of the difficulties we've had recently with planning and > >getting releases pulled together, I'd like to propose we have a new > >role > >in the Project. > > > >Project Manager > > > >Responsibilities: > > > >Maintain Schedule > >Run weekly meeting > >Coordinate with project maintainers on dates, features, etc > >Ensure that docs and release materials are ready for release > >Final say on what goes into a release > >Tracking new features > >Tracking action items > > > >This person should be empowered to make decisions for the project > >(based > >on input from maintainers, but final call is theirs). > > > >As for choosing this person, it could be done via general election > >on > >email or an IRC meeting. I'd suggest having someone do it for a > >limited > >timeline, maybe 2 or 3 releases, max, then someone else takes over. > > > >Any thoughts, suggestions, comments? Yep a program manager type role would be valuable. > > > Mike, > > I'm definitely in favor of a PM. I like the 2-3 term requirement, but > if > they want to serve again it should be an option (subject to > re-election).

> > Jon > > _______________________________________________ > Board mailing list > Board(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/board > _______________________________________________ Board mailing list Board(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/board

On 9/5/12 11:25 AM, "Mike Burns" <mburns(a)redhat.com&gt; wrote: >Correct, they can continue on if they want (if re-elected) and I suppose >we could also let them resign from the post as well. Hmmm. I figured one of the benefits of having a 2-3 month term would be that if they ~really~ didn't like it that they could see the light at the end of the tunnel and hang in for the term. But that's just me.

Jon

There seems to be general agreement that we could use someone filling this role. Are there any objections? Assuming no, are there an nominations or volunteers for someone to take the role?

On Wed, 2012-09-05 at 10:57 -0400, Mike Burns wrote: > Given some of the difficulties we've had recently with planning and > getting releases pulled together, I'd like to propose we have a new role > in the Project. > > Project Manager > > Responsibilities: > > Maintain Schedule > Run weekly meeting > Coordinate with project maintainers on dates, features, etc > Ensure that docs and release materials are ready for release > Final say on what goes into a release > Tracking new features > Tracking action items > > This person should be empowered to make decisions for the project (based > on input from maintainers, but final call is theirs). > > As for choosing this person, it could be done via general election on > email or an IRC meeting. I'd suggest having someone do it for a limited > timeline, maybe 2 or 3 releases, max, then someone else takes over. One slight tweak to the above: The existing person can continue in the role if re-elected and there are no term limits. > Any thoughts, suggestions, comments? > > Thanks > > Mike > > _______________________________________________ > Board mailing list > Board(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/board _______________________________________________ Arch mailing list Arch(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/arch

Thanks Moran. We'll give it a couple days for other volunteers to step forward or be nominated and then setup a vote.

Hi, On 09/06/2012 02:09 PM, Benedict, Jon wrote: > On 9/6/12 7:51 AM, "Mike Burns" <mburns(a)redhat.com&gt; wrote: > >> Thanks Moran. We'll give it a couple days for other volunteers to step >> forward or be nominated and then setup a vote. > > Thanks to Mike and Moran for throwing their hats in the ring. Do we want > to wait until next weeks meeting for other volunteers, or was there > another date in mind? I think a week is long enough to wait.

Is there a process in place for deciding this sort of thing?

Cheers, Dave.