[Internals] Change to FIG 3.0 term lengths

[Michael Cullum]

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

[Larry Garfield]

This sounds reasonable to me.  Thanks, Secretaries.

--Larry Garfield

--

[Lukas Kahwe Smith]

fine for me.

though I have no preference for or against this.

--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

regards,

Lukas Kahwe Smith

sm...@pooteeweet.org

[Chris Tankersley]

I think that seems fine.

-Chris, Sculpin

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Chris Tankersley
http://ctankersley.com

[Cees-Jan Kiewiet]

Sounds good to me as well

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAL9n4XN8ybQS25d%3DouKcJf5MUFh-3h5568C2grSwfYW0Mi6YWw%40mail.gmail.com.

[Matthew Weier O'Phinney]

On Tue, Dec 6, 2016 at 9:24 AM, Michael Cullum <m...@michaelcullum.com> 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.

This sounds reasonable to me; I was taken by surprise by how quickly
the secretary position was up for election again this past year, and
would definitely like to avoid that situation again.


--
Matthew Weier O'Phinney
mweiero...@gmail.com
https://mwop.net/

[Korvin Szanto]

I was going to remain silent since I didn't have objections but it looks like we are going to be +1'ing instead. So +1 :)

--
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+u...@googlegroups.com.

To post to this group, send email to php...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAJp_myWuJiVdAwmERs772DRFb-%2BgU7uHZe0uJ%3D2MAkys_dbkKw%40mail.gmail.com.

[Michiel Rook]

No objections from Phing.

--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAqcDMgEO2UdVnJyDvf1hT7rc3o4L3AX1oY99xJsGG8C%3D-FghQ%40mail.gmail.com.