Will anyone else second Larry? Hi Michelle,
Because this is a first, I will address your points. > > I have read through some of this long discussion, and in essence, I agree > with Larry thay using “PSR” in the PHP community for a standard that is not > a FIG standard is harmful to the community and devalues the work of FIG. > > My PSRs literally rely on FIG PSRs and refer to them in the documentation. How are my prototypes going to hurt the community when almost none of the PHP community knows about them? When they are designed not to conflict? How do my PSRs, that pay reverence to the existing PSRs by extending them, devalue FIG PSRs? > We have been around for a long time; when PHP developers see “PSR” they > will look it up at FIG, not find it; and get confused. Let’s not confuse > our wonderful community. > The idea that google will choose to show my PSRs over FIG's PSRs is kind of absurd. And, the case you present is also kind of absurd since I refer directly to the FIG PSRs in the documentation, and anyone arriving at my PSRs would be directed to FIG PSRs if that is what they were looking for. And like I already said, I'm perfectly willing to add a header "Not a FIG PSR" if desired. > I’m sorry Adam that you felt that the communication was patronizing. That > is perhaps something that we can look into. > Don't worry about it - it is truly something you can not fix. -- 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/18dcba38-2115-4061-98b5-c61423ccbfc4n%40googlegroups.com.
