I apologise for the double post, I had not seen Matthieu's last post, after
this post I will self-throttle as I have been previously and not reply for
the rest of the day. I'm also about to go away for a few days so I will be
responding less but Larry is of course still around.

On 7 August 2016 at 09:31, Matthieu Napoli <[email protected]> wrote:
>
>
> My last concern would then be: are we confident that the scope of the Core
> Committee vote is well defined and cannot be abused even a little? Here is
> an extreme scenario: could a Core Committee member vote -1 on a standard
> because that member has an implementation in their framework that is
> different, and the new standard could threaten somehow their de-facto
> existing standard in the community? Do those vote need to be justified
> somehow, and is their a recourse if their's a doubt or flagrant abuse?
> Sorry for bringing such a "dark" question up :)
>
> In any case all of this is a very good improvement, thanks to those
> working on that.
>

Thank you also for your kind words and raising such important points for
addressing.

You bring up an entirely valid point, people in any position of
responsibility are subject to abusing that power and responsibility they
hold, whether they are Secretaries or Core Committee Members. There are
mechanisms in place for calling for what is essentially a removal vote/vote
of no confidence (Recall Vote) in Core Committee Members and Secretaries,
and of course they will be subject to forced re-election once their terms
end, a good time to elect people who will be voting within their remit and
taking the FIG in the desired direction of the wider FIG community and
structure. I'd also note that with 12 of them, 4 of them would need to vote
-1 for a motion to fail. I'd imagine that the Secretaries and Core
Committee would all work closely together to ensure that everyone is
fulfilling their role properly. I would also imagine that whilst it is not
required in the bylaws, those electing the Core Committee would expect any
-1 votes to be appropriately justified to the rest of the Core Committee
and the wider FIG community; similarly to how judges in a supreme court
might publish a dissent <https://en.wikipedia.org/wiki/Dissenting_opinion>.

Many thanks,
Michael C

-- 
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/CAAqcDMhD6eEYjsgGdCUbJy-Ebvt9io1kzmRwnET6Y%3DHQTaXZwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to