I don't plan to lead this through the PER process but I'd be happy to be on the WG under your leadership Alex.
On Wed, Dec 15, 2021, 12:43 PM Alex Makarov <s...@rmcreative.ru> wrote: > I can be part of the group. If there will be a lack of editor role, I > can handle it. > > On Wed, Dec 15, 2021 at 5:53 PM Larry Garfield <la...@garfieldtech.com> > wrote: > > > > On Wed, Dec 15, 2021, at 8:45 AM, Alex Makarov wrote: > > > What's needed to do it? A list of new shiny stuff and rules for it? > > > Could be done. What else? > > > > > > On Wed, Dec 15, 2021 at 5:34 PM Alessandro Lai > > > <alessandro.la...@gmail.com> wrote: > > >> > > >> Hello and welcome! > > >> PSR-12 is unfortunately not up to date with the latest shiny stuff > that we got with PHP 8+. We recently approved the PER workflow, so we could > try to migrate PSR-12 to a PER, and make it easier to update. > > >> > > >> Anyone willing to help on this? > > > > Process wise, here's how it should happen: > > > > * A new working group gets together and petitions the CC to get > recognized for a "coding standards" per. I am going to request that it be > a full-size group (5 member including CC Sponsor) not a mini-group, given > its importance. > > > > * The first thing the new WG does is copy-paste PSR-12 to a new doc and > release it as CodingStandards v1. (Or maybe we can get away with tagging > it v2? Either/or.) The exact process for that is noted in the byalws, and > will require another CC vote. > > > > * Once that's done, the WG can start debating/accepting PRs for coding > standards updates; when there's "enough" (as defined by the Editor), they > can release either a 1.1 or a 2.0 (or 2.1/3.0), with the exact process > again noted in the bylaws. This MAY require a CC vote, depending on how > the CC feels about it. Again, all explained in the bylaws. > > > > I would encourage the Editor to be someone who was involved in PSR-12, > but beyond that it's the same "anyone interested and dedicated" as any > other WG. > > > > --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 php-fig+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/1fd118b6-d80f-480d-b033-a22d79b9d0c6%40www.fastmail.com > . > > -- > 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/CA%2BFA5VXox7EZsJNH4MZ-FH51b-tgb5ygAaY%3DRHo4uqfwH4-qGw%40mail.gmail.com > . > -- 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/CANeXGWXD8O90_N5VYdi7H11s4%3DqXNs9Fn_FY%3DYzhmcBvRsRymQ%40mail.gmail.com.
