Hi,

I think having Evolving Proposals would be a good thing.

Then people only have to bookmark the PER once and revisit it when
appropriate instead of having to follow a trail to see what the most
up-to-date recommendation is.
For example, somebody coming back to PHP after a while might not know that
PSR-12 exists but knows about PSR-2. When they find PER-CodingStandards
they can be sure of the most recent PSR in that area.

I mentioned this on Discord today. Alessandro Lai suggested that for this
scenario in relation to code, we can bind that to new major versions, for
CS maybe we can use a meta-package so projects can declare with a
constraint their "version" of adherence to the PER.

I think that for deprecated PSRs -  in this instance PSR 2 -  we could
expand the Deprecated Notice block to identify and link to the pertinent
PSR.
This would mean someone will hopefully have fewer steps to go through to
find the most recent relevant PSR.

As an example the message "Deprecated - As of 2019-08-10 PSR-2 has been
marked as deprecated. PSR-12 is now recommended as an alternative." would
be changed to "Deprecated - As of 2019-08-10 PSR-2 has been marked as
deprecated. Please consult PER-CodingStandards to quickly identify the most
recent applicable PSR. At the time of this update, PSR-12 is the new
Recommendation superseding this one (PSR-2)."

Regards,

Ken

On Mon, 16 Aug 2021 at 21:24, Larry Garfield <[email protected]> wrote:

> Thank you everyone for the feedback here and on GitHub.  Based on that,
> I've refactored the bylaws quite a bit more to support a cleaner way to
> define the PER process, and to split auxiliary resources (eg, util
> libraries) off to their own setup.  The full changelog is in the PR:
>
> https://github.com/php-fig/fig-standards/pull/1235
>
> Feedback, round two!
>
> --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/fa785737-c508-4e41-a799-790e2dd487a0%40www.fastmail.com
> .
>


-- 
http://about.me/kenguest/

-- 
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/CAKcc2m_67PHxwd9GwVOojpXBm9Us4%3DQHHLsUk3n%3DLHYtV0cWVg%40mail.gmail.com.

Reply via email to