Answering this required me working backwards so I just did the full timetable. The new FIG 3.0 transition timetable would be as follows:
1st November: CC Nominations open *7th December: CC Nominations close* (Initial nominations, people can accept nominations after this so long as voting hasn't started) *9th December: CC Election voting begins* *23rd December: CC voting ends* 24th December: CC results announced 25th December: CC takes post 16th January: Recommended date for PSRs to have working groups fully formed with a CC sponsor 17th January: Latest date for any FIG 2.0 votes to start except acceptance votes 17th January: Latest date for any PSRs to enter review under the old system 31st January: Latest date for any PSRs to start approval votes under the old system 31st January: Final deadline for PSRs to have full working groups formed with a CC sponsor *1st February: All votes and actions take place under new system; full transition* 14th February: Latest possible date for any FIG 2.0 approval votes to have finished by 28th February: Deadline for any PSRs which entered review before the 17th December to form a Working Group with a CC sponsor if they failed their approval vote/didn’t get to their approval vote in time May 2017: Next Secretary and CC election -- Michael C On 9 November 2016 at 12:53, Larry Garfield <la...@garfieldtech.com> wrote: > Under the circumstances, I do not object. What end-date are you proposing > for nominations? Early December? > > --Larry Garfield > > > On 11/09/2016 11:08 AM, Michael Cullum wrote: > > Hi all, > > Does anyone have any objections to extending the Core Committee nomination > period one month and pushing the FIG 3.0 implementation timetable back a > month (so the new implementation date will be 1st February)? > > There are still a number of people looking to be nominated or considering > standing; meanwhile right now we only have 7 candidates when 15-20 would be > a much more appropriate number for a fair election and we think at least 12 > at a minimum is still achievable if given a little more time. > > -- > FIG Secretaries > -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to php-fig+unsubscr...@googlegroups.com. > To post to this group, send email to php-fig@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/php-fig/CAAqcDMhSgM3qMZAnV9674xuLuLF3YQtx_otOv53ANJHsk%2Bq%2B7Q% > 40mail.gmail.com > <https://groups.google.com/d/msgid/php-fig/CAAqcDMhSgM3qMZAnV9674xuLuLF3YQtx_otOv53ANJHsk%2Bq%2B7Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to php-fig+unsubscr...@googlegroups.com. > To post to this group, send email to php-fig@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/php-fig/bf316ec9-a158-a358-b310-5ba364a17add%40garfieldtech.com > <https://groups.google.com/d/msgid/php-fig/bf316ec9-a158-a358-b310-5ba364a17add%40garfieldtech.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAqcDMhOwpMH%3D%3Di5Az41Y_UQhA-so_02k6z2sF6DDjZMAW6a4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
