I agree wholeheartedly with Woody Gilk. FWIW, from a non-member :) John
On Apr 11, 2017, at 6:08 PM, Woody Gilk <[email protected]<mailto:[email protected]>> wrote: I've taken the survey. Been thinking about this for several days and I think this is just pointing at a deeper issue with PSR numbering. Bottom line is, the numbering of PSRs has always been broken: - sequential numbering is not semver - numbers are assigned before acceptance, leaving gaps - the only number anyone cares about is the composer version - numbers are noise and always have been I realize that FIG has taken the IETF approach, but I just don't think it works for when you try to apply it to code. Regardless of whether or not adding type hints to (eg) PSR-3 requires an entirely new PSR, the package/namespaces shouldn't be any different, it should just be a major version change in the composer package. Pushing the PSR numbering into code is counter productive and confusing. -- Woody Gilk http://about.me/shadowhand On Tue, Apr 11, 2017 at 3:19 PM, Larry Garfield <[email protected]<mailto:[email protected]>> wrote: Hello, peoples. In response to some recent off-list discussion (at conferences and elsewhere), I offer this brief survey about how we should namespace interface PSRs once we start producing "updated" versions (eg, PHP 7-ified versions) of existing specs. The survey itself has more details, and should take under a minute to complete. Please do so! https://docs.google.com/forms/d/e/1FAIpQLSc8VJySoz_3koQThe057zYhzSkmOvOAgO0pEmenwr1Biu6JEA/viewform This is a non-binding information gathering tool only to kick off a discussion, not to end one. Feel free to discuss more in this thread. I'll leave the survey open for 2 weeks or until people stop responding to it. :-) All are welcome and encouraged to respond, even if you're not a Core Committee member or Project Rep. --Larry Garfield -- 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:php-fig%[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/1a010cb1-a7fa-286a-ac7d-d932177a26d5%40garfieldtech.com. For more options, visit https://groups.google.com/d/optout. -- 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/CAGOJM6JvcPSy_SJjqP6RGnMc1mOzrQUbdSynPTB93%2BM8Fhau-A%40mail.gmail.com<https://groups.google.com/d/msgid/php-fig/CAGOJM6JvcPSy_SJjqP6RGnMc1mOzrQUbdSynPTB93%2BM8Fhau-A%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- 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/3D4EB0D9-C6E1-4E8B-A35D-3EB4F7BCCA80%40buffalo.edu. For more options, visit https://groups.google.com/d/optout.
