Release Managers for oVirt

[Jon Choate]

----- Original Message -----
> From: "Perry Myers" <pmyers at redhat.com>
> To: "Jon Choate" <jchoate at redhat.com>
> Cc: arch at ovirt.org
> Sent: Wednesday, November 16, 2011 2:45:08 PM
> Subject: Re: Release Managers for oVirt
> 
> > "The second thing is for each sub-project to nominate a point
> > person
> > for sub-project release mgmt."
> > 
> > Its a little unclear from this wording but I'm assuming that anyone
> > in the community can nominate anyone for any subproject. For
> > instance, you don't have to be a maintainer of or even a
> > contributor
> > to a subproject to nominate or be nominated. Is that what is
> > intended?
> 
> Not sure why that wording is ambiguous.  It says 'each sub-project to
> nominate', that means the sub-project team itself (i.e. oVirt Node
> team)
> would nominate someone internally to be release manager for that
> sub-project
> 
> I don't think it makes sense to have the community at large nominate
> release managers for the subprojects
> 
Well then I guess my follow-up question is what constitutes team membership? Does that mean maintainers only or maintainers and board?