On Tue, Mar 15, 2016 at 09:41:41PM +0000, Hayes, Graham wrote: > I do not see the time frame for defining an electorate there. > > PTL seats are completely renewed every 6 months. A separate election is > run for > each project team. These elections are collectively held 5 weeks prior > to each > design summit, with nominations due 6 weeks prior to the summit and > elections > held open for no less than five business days. > > The way the rules are currently worded if the extra ATC patch merged > before the deadline for PTL nomination anyone in that patch would be > able to run. > > Where do we define the cut off date for electorate definition? [1] roughly defines it as "committed a change to a repository of a project over the last two 6-month release cycles" For the sake of generating the full APC roles we (the election officials) define the exact range and communicate that[2]. At approximately the same time the governance repo is tagged and used for reference[3]. There are no extra-ATCs for Packaging-deb[4]. That is how we define the electorate, changing that mid-election is not an option. Yours Tony. [1] http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc [2] https://wiki.openstack.org/wiki/PTL_Elections_March_2016#Electorate [3] http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml?id=march-2016-elections [4] https://github.com/openstack/governance/blob/march-2016-elections/reference/projects.yaml#L3147-L3282 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160316/2fa0150d/attachment.pgp>