Yeah, the point is exactely that. The core committee doesn't need to be experts on the field, they can relay that to the WG. They can (and must) however reject a PSR if they think that the WG ignored or didn't listen to experts or big players in the context of the PSR.
Il giorno lunedì 22 agosto 2016 01:03:01 UTC+2, Alexander Makarov ha scritto: > > Chris Tankersley, thanks for info. I've somehow missed renewal terms. > Members are elected for 2 years. That's probably a bit lengthy period. > > Do you know why the number of core committee members is exactly 12? > > I understood that after work is done, proposal is passed to core committee > for final vote. I still wonder what happens if current core committee > members do not have expertise about the topic to vote... they can ensure > quality of the text itself and its clarity but can't ensure that the > proposal itself is a good one. Probably not a big issue since proposal > already passed multiple stages. > > *// Just realized I haven't finished 2nd sentence :) Please ignore "To me > it looks wrong that".* > > On Monday, August 22, 2016 at 1:12:42 AM UTC+3, Chris Tankersley wrote: >> >> >> >> On Sunday, August 21, 2016, 'Alexander Makarov' via PHP Framework >> Interoperability Group <php...@googlegroups.com> wrote: >> >>> Voting on FIG 3.0 started. I've read diff of the changes (huge one), >>> TLDR at medium and searched ML but haven't found answers to some questions. >>> Please help me find the answers. Thanks! >>> >>> 1. What's the reason to limiting core committee to 12 members? To me it >>> looks wrong that >>> >> >> If I remember correctly, the idea was to have a smaller, dedicated core >> group to encourage the members to be more active. All of the work regarding >> each PSR will be handled by the individual working groups though, which may >> contain core members but ideally are made up of many different member >> projects. >> >> >>> 2. Why 12 exactly? What if there's a PSR on a topic any of these 12 >>> members don't care about or don't have expertise about? >>> >> >> That's what the working groups are for. The Working Group should be made >> up of people interested and knowledgeable about the topic. When the PSR is >> all finished (wording and two implementations) and ready to be finalized, >> it's passed onto the core committee for a final vote. >> >> >>> 3. Have I missed information about how core committee members are >>> rotated / re-elected? >>> >> >> That info was in the PR for the change. I'm on mobile otherwise I would >> link to it. >> >> >>> -- >>> 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/8629479a-0c05-468d-9705-a1003d1bc368%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/php-fig/8629479a-0c05-468d-9705-a1003d1bc368%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> Chris Tankersley >> http://ctankersley.com >> >> -- 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/5f9f8966-8956-4ef4-9b65-7dfad796254a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
