New Role Proposal in the oVirt Project
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? Thanks Mike
On 9/5/12 10:57 AM, "Mike Burns" <mburns@redhat.com> 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
----- Original Message -----
From: "Jon Benedict" <Jon.Benedict@netapp.com> To: "Mike Burns" <mburns@redhat.com>, "board" <board@ovirt.org>, "arch" <arch@ovirt.org> 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@redhat.com> 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 09/05/2012 08:09 AM, Andrew Cathrow wrote:
Yep a program manager type role would be valuable.
For other projects at Red Hat, we have someone from the program management team work directly, including in the upstream. (That was Fedora Project Leader Robyn Bergeron's role before her new job, for example.) Can we get that level of commitment for PM work from someone? Is that a role that one of the sponsoring Board organizations can supply someone for? Even if it's someone who isn't as familiar with working in open source, we can help train. :) - Karsten -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
On Wed, 2012-09-05 at 11:09 -0400, Andrew Cathrow wrote:
----- Original Message -----
From: "Jon Benedict" <Jon.Benedict@netapp.com> To: "Mike Burns" <mburns@redhat.com>, "board" <board@ovirt.org>, "arch" <arch@ovirt.org> 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@redhat.com> 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).
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. Mike
Jon
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 9/5/12 11:25 AM, "Mike Burns" <mburns@redhat.com> 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
On Wed, 2012-09-05 at 18:55 +0000, Benedict, Jon wrote:
On 9/5/12 11:25 AM, "Mike Burns" <mburns@redhat.com> 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.
True, but we're supposedly moving to 6 month release cycle, after this next release. I guess the release schedule is also owned by the Project Manager too, so they can determine it. Mike
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 09/05/2012 10:25 PM, Mike Burns wrote:
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?
I would like to nominate myself for this role. pros: -I generally have the bellow responsibilities on RHEM, from dev perspective. cons: -many of you don't personally knows me since till now i was usually taking the backstage roles on upstream matters. I'm willing to take the step forward, let me know what you think.
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
_______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
On Thu, 2012-09-06 at 11:21 +0300, Moran Goldboim wrote:
On 09/05/2012 10:25 PM, Mike Burns wrote:
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?
I would like to nominate myself for this role. pros: -I generally have the bellow responsibilities on RHEM, from dev perspective.
cons: -many of you don't personally knows me since till now i was usually taking the backstage roles on upstream matters.
I'm willing to take the step forward, let me know what you think.
Thanks Moran. We'll give it a couple days for other volunteers to step forward or be nominated and then setup a vote. Mike
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
_______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 9/6/12 7:51 AM, "Mike Burns" <mburns@redhat.com> 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? Thanks, Jon
Hi, On 09/06/2012 02:09 PM, Benedict, Jon wrote:
On 9/6/12 7:51 AM, "Mike Burns" <mburns@redhat.com> 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. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On Thu, 2012-09-06 at 14:20 +0200, Dave Neary wrote:
Hi,
On 09/06/2012 02:09 PM, Benedict, Jon wrote:
On 9/6/12 7:51 AM, "Mike Burns" <mburns@redhat.com> 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.
+1
Is there a process in place for deciding this sort of thing?
http://www.ovirt.org/governance/voting/
Cheers, Dave.
On Wed, 2012-09-05 at 15:25 -0400, Mike Burns wrote:
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?
Forgot to mention that I'm willing to take this role on for the next couple releases. As for my qualifications: I've been doing a number of the coordination responsibilities already I'm involved in both the Node (as maintainer) and Infra (as a contributor) projects. I've been pretty visible to the community already through both upstream IRC and meetings and the oVirt Workshops.
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
participants (6)
-
Andrew Cathrow -
Benedict, Jon -
Dave Neary -
Karsten 'quaid' Wade -
Mike Burns -
Moran Goldboim