fine for me. though I have no preference for or against this.
> On 06 Dec 2016, at 16:24, Michael Cullum <[email protected]> wrote: > > Hi all, > > It was noted by a few individuals that the way the bylaws stand about > fulfilling the initial 12 Core Committee roles as if there is a 12-member > vacancy this leads to a rather inefficient situation where some people would > have their terms expire in April/May of this year which I'm sure you all > agree is non-ideal as (1) they won't have time to settle in (2) CC elections > take time and focus away from working on specifications and two in such a > short period is relatively unhelpful. > > However, a small change could help resolve this issue so I'm just asking if > anyone objects to us doing it slightly differently** > > The old system would have involved the following three terms: > Top four candidates term expires in: August 2018 > Next four candidates term expires in: January 2018 > Last four candidates terms expire in: April 2017 > > My suggestion is to change it so they receive the following (slightly > extended terms so the minimum term is ~1 year and maximum is just over 2 > years): > Top four candidates term expires in: April 2019 > Next four candidates term expires in: August 2018 > Last four candidates terms expire in: January 2018 > > Essentially, we just skip the first normal CC election and extend everyone's > term by a few months so that we stay on the defined calendar for future > elections. > > -- > Many thanks > FIG Secretaries > > ** If there are more than a couple of objections from voting members then I > guess it will just be dropped as an entire vote to decide if we should do > this doesn't really help with the aim of reducing bureaucracy in this instance > > -- > 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 [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/php-fig/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. regards, Lukas Kahwe Smith [email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/B8FED62F-AF83-405B-AE52-BBD6A109D7DE%40pooteeweet.org. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
