On Sat, Jul 10, 2021, at 11:16 AM, Adam Frederick wrote:
> > If you continue this work outside the FIG procedures, we request that you > > don't claim any affiliation to the PHP-FIG. Specifically, we ask you to not > > cause confusion to the PHP community at large by representing your proposal > > as a PSR. > > I do not claim any affiliation with FIG. If so desired, I'll even put > such in the READMEs and anywhere else you want. The phrase PHP > standard recommendation is generic and the most suiting phrase for the > description of what I am presenting. If you have another name for a > PHP standards recommendation I could use, I'll consider it. But I > already made the PSRs start at 100 for the explicit purpose of > separating them from FIG PSRs. As I presented in the PSR 100 README: "The phrase PHP standard recommendation is generic" Incorrect. "PSR" is a very well-understood term for the specifications published by FIG, specifically. If everyone went around calling every package they released "PSR", it would only do harm to the community because it would confuse everything. Doctrine for instance is super popular, more popular than some FIG specs, but if they started calling Doctrine ORM "PSR-30"... that would just be a lie. > "I've numbered this PSR 1XX under the premise FIG will not get to 1XX > in a long time, or will never get to it, and so, my PSR's will not > conflict for a very long time, and if they ever conflict, and my > standards are not accepted, they can just be ignored at that time." And when 30 other people decide to start publishing "PSRs" and randomly grabbing various number ranges? There are people who didn't think FIG would get to 10 specs, much less 20 PSR numbers, including some of its founders. If you want to publish a package that combines PSR-15 and PSR-17 in some way, you're certainly welcome to do so. But by using the term "PSR" you are implying an affiliation with FIG and its approval process that is not present, and thus misrepresenting your work. There is no situation in which that is not harmful and unprofessional. Most framework leaders would recognize it as such and actively avoid your "standards" for that reason. --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]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/2f548ee2-f939-41a6-b57d-363fa98cc74a%40www.fastmail.com.
