> On 06 Aug 2016, at 02:06, Adam Culp <[email protected]> wrote:
> 
> Thank you for doing this Michael, it clarified a few questions I had while 
> highlighting a new concern:
> 
> Based on what I see the Member Projects of the FIG do not get to vote, though 
> they can share their comments via the group. However, Member Projects are 
> encouraged to implement these interoperability "standards" without said vote. 
> (imposed "tax") Dramatic I know, but valid.
> 
> I foresee a future full of squabbling and rejection to use PSRs because, "I 
> didn't vote for it!" There would be no "ownership" of these new PSRs.
> 
> I fully understand the working group would be composed of individuals that 
> are best in a given field as subject experts, and who may have a more active 
> role in the given technology. But again...ownership is key to ensure these 
> interoperability recommendations are accepted by more projects.
> 
> As such, I would suggest the addition of a "Member Projects Vote" after the 
> "Review stage" but before the "Core Committee: Acceptance Vote". Make it a 
> standard 2 week combined voting/feedback period to air out any unforeseen 
> comments/concerns, where simple majority passes the motion. Then when the 
> Core Committee accepts the PSR there will be much wider adoption and 
> acceptance.
> 
> Thoughts?

Without suggesting a specific mechanic, I also agree that at some stage a PSR 
should get voted on by all members. In practice this should be more or less an 
“easy vote” but its important in order to get the buy-in from the member 
projects and to ensure that working groups do not over engineer.

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/D8D52C95-DEF2-485F-9992-2C305A151318%40pooteeweet.org.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to