Adam, Showing up to this thread late and likewise in a capacity no more official than yours. I'll add my opinion in with Larry's to get closer to the requisite threshold where you tell FIG, which has gotten buy-in from various maintainers to use the same interfaces, just how wrong they are. While grabbing a namespace on GitHub purporting to be, well, more than yourself.
There is a difference between APIs I like and hard-fought specs with organizational buy-in, multiple distinct implementations...and a PSR number. Note that even FIG doesn't slap a number on *its own* specs until they've made it far down the process. They're named drafts for the first bit. Hopefully you can understand the consternation arising when you decide to skip that step after framework/middleware maintainers reply "yes, we thought of that, and here's why we didn't go down that route." At the end of the day, specs are only as good as their adoption, and FIG cannot, say, mandate Laravel, Symfony, or even Laminas to implement anything FIG turns into a numbered PSR. Nor does it take FIG's blessing for multiple frameworks to implement a given pattern that they see as useful. So if your concern is getting two frameworks that you like to adopt your set of interfaces, the most expedient way to proceed would be to see if those frameworks will accept a PR integrating the interface. Bonus points if the implementations are different, matching the framework's internals. Heck, if the idea is solid enough, maybe after the first framework merge you'll get someone willing to implement within their framework for you, which would provide you enormous validation. Or maybe they discuss with you and the result is a better spec, at which point you go back to the first framework you implemented with and change things before the de facto standard gets too set in stone. In the mean time, assuming you're operating in good faith in the direction of FIG, throwing numbered "PSRs" around is improper signaling, as a few folks have mentioned. With that in mind, which two frameworks do you intend to individually convince to accept a PR exhibiting the functionality you're championing? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAupm8jU2HkQ-zcbz-jwChbRa6zNOhzU0OquXRSV1RFVw7UzQA%40mail.gmail.com.
