PSR status update

[Alessandro Lai]

Hello everyone,

we (the secretaries) decided it was time to post a status update for the PSR which are pending, as a way to update you members and the whole community on our work, and also to start discussion around some PSR that need a little more participation. Here it is:

PSR-5 (PHPDoc)

Status: abandoned / regrouping

Last time, it was brought up to be resurrected with a new and fresh working group (https://groups.google.com/forum/?fromgroups#!topic/php-fig/bcV4KXIW6dQ): Chuck Burgess expressed his intention of stepping up as the editor, and Gary Hockin said that he could step in as a CC member to be the sponsor.

We also need to form a Working Group, so (at least) three other persons are needed. If you are able to contribute, please reach out.

PSR-6 (Caching Interface)

Status: amendment vote in progress

There was a PR opened a long time ago with an errata about the expiresAt() method and its handling of the \DateTimeInterface argument: https://github.com/php-fig/fig-standards/pull/915/files

The PR created a long discussion and 2 failed attempts to vote that in, but recently all the participants reached an agreement. Please, vote!

PSR-9 and PSR-10 (security)

Status: abandoned / regrouping

Currently not active. Michael Cullum is attempting to take over. Adam Englander has signed on to help. They still need a few team members before they can initiate a vote on the new PSR team. They specifically are wanting security leads from PHP-FIG member projects. If you are willing to help, please reach out to Michael, Adam, or one of the Secretaries and let us know.

PSR-12 (code style)

Status: in review

The WG is currently working on the two implementations needed to ask for the acceptance vote. One of the two is currently worked on by Korvin Szanto, and it’s viewable here: https://github.com/KorvinSzanto/PHP-CS-Fixer/tree/feature/psr12.

We need a second implementation to move forward. Is anyone currently working on a second implementation?

It’s also getting some attention from the Prettier package (see https://github.com/prettier/plugin-php/pull/200 and https://github.com/prettier/plugin-php/issues/167).

Larry Garfield has re-raised concerns. Please, take a look and provide any feedback you have here: https://groups.google.com/forum/#!msg/php-fig/vZOpga3xoLg/_Q-CbeWMAQAJ.

Michael Cullum believes this will be ready for vote in 2 months.

PSR-14 (event manager)

Status: abandoned / regrouping

This PSR is getting some attention on the ML recently, and it’s getting discussed here: https://groups.google.com/forum/?fromgroups#!topic/php-fig/EwCZ9ritJcA. Larry Garfield is trying to step in as the editor, Benni Mack and Stéphane Hulard have volunteered to help. Larry has said that he will push this forward next week, after Tuesday 20th.

PSR-17 (HTTP factories)

Status: Draft

PSR entered the draft status thanks to Matthew (https://groups.google.com/forum/?fromgroups#!searchin/php-fig/PSR-17%7Csort:date/php-fig/A5mZYTn5Jm8/8nqDCh5TBgAJ).

The new PSR working group is:

- Editor: Woody Gilk

- Sponsor: Matthew Weier O’Phinney

- Members: Stefano Torresi, Matthieu Napoli, Korvin Szanto, Glenn Eggleton, Oscar Otero, and Tobias Nyholm.

The working group is currently looking at proposal and hope to have it ready to share for general review in the next two weeks.

PSR-18 (HTTP client)

Status: Draft

The working group is currently deciding on an upgrade path from HTTPlug. They have a proposal that they think will work which is being reviewed by a small group and once they’re happy with it that will be posted to the PHP-FIG for comments.

PSR-19? (Streams / Async)

Status: Pre-Draft

Currently on hold until Sara can make time in her schedule.

[Ben Ramsey]

I’m interested in working with Chuck and Gary on PSR-5.

Cheers,

Ben

--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/4d3edf58-5392-44af-8b2d-2a28b2fa8316%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[e.cour...@gmail.com]

Hi

I am very interested to help on PSR-19.

Cheers

Eric

[Michael Babker]

Hi,

I'd be interested in helping with PSR-9/10 as a past lead (and still current member of) Joomla's security team.

[Chris Cornutt]

I'd like to get back involved with PSR-9/PSR-10 to help out whoever ends up leading that effort. I'd still like to see some of the projects come in. It seems like there are several out there already making a serious investment in the security of their project including Drupal, WordPress, Symfony and Zend Framework.

On Friday, March 16, 2018 at 3:46:17 AM UTC-5, Alessandro Lai wrote:

[in...@ph-il.ca]

I would like to help too... But question for PSR-10 why not using security.txt ( http://securitytxt.org )?

[Matthew Brown]

I'm happy to work on PSR-5

[Chuck Burgess]

I'll be unavailable next week (traveling with a high school group), so I'll reach out to everyone about starting the WG the following week 👍

CRB

To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscribe@googlegroups.com.

To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/4d3edf58-5392-44af-8b2d-2a28b2fa8316%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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+unsubscribe@googlegroups.com.

To post to this group, send email to php...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/16CB4733-E07B-405B-8595-70A06C0BCFCB%40benramsey.com.

[Larry Garfield]

When PSRs 9 and 10 were first given numbers securitytxt.org didn't exist yet.
:-) And they've not really been updated since then, hence their current
abandoned status.

Once the WGs are reassembled it would make sense to look at securitytxt.org
and similar efforts to see what can be stolen^W borrowed from them.

--Larry Garfield

[Joe T.]

Looking forward to working on PSR-5 since i missed my chance for 12.

As far as 12 goes, i really do hope some genuine discussion happens for the inconsistencies and concerns raised by Larry before it's finalized. If no other reason raised so far makes sense, consider how much simple it would be to write and maintain the linters/validators when all occurrences of characters and structures are expected to look the same regardless of their context...

Thanks.

-jlt

On Friday, 16 March 2018 04:46:17 UTC-4, Alessandro Lai wrote:

[Larry Garfield]

On Friday, March 16, 2018 3:46:17 AM CDT Alessandro Lai wrote:
> Hello everyone,
> we (the secretaries) decided it was time to post a status update for the
> PSR which are pending, as a way to update you members and the whole
> community on our work, and also to start discussion around some PSR that
> need a little more participation. Here it is:

A request to everyone stepping forward to help out with one WG or another
(thank you!):

When doing so, please also state explicitly what your relevant background is.
One of the goals of the working groups is to bring together domain experts for
that problem space, not just people who think it's cool. Have you experience
in managing security processes for an Open Source project? We definitely want
your help on PSR-9 and PSR-10! Do you just think that it would be good to
have standards but don't really have any insight into them beyond the casual
user? Please think hard about what you'd be bringing to the table and if
you'd have enough time to commit to it.

I don't want to dissuade people from getting involved if they're genuinely
interested and have something to add. However, I also want to make sure we
stay focused on the goal of working groups: Bring together the specialists in
that field/topic to come to a consensus that has buy-in from domain experts.
"I think it's important so I'll offer to help as a vote of support" is a
really easy trap to fall into (and I've certainly done so myself on more than
one occasion), but is less helpful in practice than "I've been working/
researching in this space for a while and I've got experience to share."

If the latter is the case for you, then please please step forward and say so.
You're the people we want to hear from.

--Larry Garfield

[Matthew Brown]

I’m interested in PSR-5 because I wrote a static analysis tool called Psalm. Part of that has involves parsing docblocks to extract information that improves its analysis, and it also involves creating new Psalm-specific docblock annotations to convey information the the current PHPDoc standard does not allow (like array<int, string>).

> --
> You received this message because you are subscribed to a topic in the Google Groups "PHP Framework Interoperability Group" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/php-fig/ywaSYo_tXdc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to php-fig+u...@googlegroups.com.

> To post to this group, send email to php...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/2850867.WhT4q5Pu0L%40vulcan.

[Ben Ramsey]

I’m retracting my interest in PSR-5 to allow others more qualified to participate.

Cheers,
Ben

> --
> 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+u...@googlegroups.com.

[Ondřej Mirtes]

I'd like to join the PSR-5 group. I wrote a static analyser called PHPStan (https://github.com/phpstan/phpstan) and it's doing quite a lot phpDoc interpretation by itself, namely:

* Union vs. intersection types (I'm talking about this in an article: https://medium.com/@ondrejmirtes/union-types-vs-intersection-types-fd44a8eacbb)
* Combining native typehints with phpDocs resulting in what the developer wants (e. g. "self" in native typehint and "static" in phpDoc gets combined into "static", and there's a lot more going on)
* Interpreting special iterable types like Collection|Foo[] with conventional wisdom
* Parsing @method and @property annotations above a class

[Joe T.]

Given the criteria for participation (thanks for clarifying, Larry), i'll step back from PSR-5 for now so that a group with more direct experience can be formed. However, i'm still available if any slots remain open.

-jlt

[Matteo Beccati]

Hi,

I'd be happy to help PSR-9/10.

Background: I've been dealing with the security issues in Revive
Adserver through its various names and iterations since roughly 15yrs.


Cheers

On 16/03/2018 16:21, Chris Cornutt wrote:
> I'd like to get back involved with PSR-9/PSR-10 to help out whoever ends
> up leading that effort. I'd still like to see some of the projects come
> in. It seems like there are several out there already making a serious
> investment in the security of their project including Drupal, WordPress,
> Symfony and Zend Framework.
>
> On Friday, March 16, 2018 at 3:46:17 AM UTC-5, Alessandro Lai wrote:
>
> Hello everyone,
> we (the secretaries) decided it was time to post a status update for
> the PSR which are pending, as a way to update you members and the
> whole community on our work, and also to start discussion around
> some PSR that need a little more participation. Here it is:
>
>
> PSR-5 (PHPDoc)
>
> Status: abandoned / regrouping
>
> Last time, it was brought up to be resurrected with a new and fresh
> working group
> (https://groups.google.com/forum/?fromgroups#!topic/php-fig/bcV4KXIW6dQ

> <https://groups.google.com/forum/?fromgroups#!topic/php-fig/bcV4KXIW6dQ>):

> Chuck Burgess expressed his intention of stepping up as the editor,
> and Gary Hockin said that he could step in as a CC member to be the
> sponsor.
>
> We also need to form a Working Group, so (at least) three other
> persons are needed. If you are able to contribute, please reach out.
>
>
> PSR-6 (Caching Interface)
>
> Status: amendment vote in progress
>
> There was a PR opened a long time ago with an errata about the
> expiresAt() method and its handling of the \DateTimeInterface
> argument: https://github.com/php-fig/fig-standards/pull/915/files
> <https://github.com/php-fig/fig-standards/pull/915/files>
>
> The PR created a long discussion and 2 failed attempts to vote that
> in, but recently all the participants reached an agreement. Please,
> vote!

> <https://groups.google.com/forum/#!msg/php-fig/q41LZJspm48/JP0MEZ1lAgAJ>

>
>
> PSR-9 and PSR-10 (security)
>
> Status: abandoned / regrouping
>
> Currently not active. Michael Cullum is attempting to take over.
> Adam Englander has signed on to help. They still need a few team
> members before they can initiate a vote on the new PSR team. They
> specifically are wanting security leads from PHP-FIG member
> projects. If you are willing to help, please reach out to Michael,
> Adam, or one of the Secretaries and let us know.
>
>
> PSR-12 (code style)
>
> Status: in review
>

> The WG is currently working on the twoimplementations needed to ask

> for the acceptance vote. One of the two is currently worked on by
> Korvin Szanto, and it’s viewable here:
> https://github.com/KorvinSzanto/PHP-CS-Fixer/tree/feature/psr12

> <https://github.com/KorvinSzanto/PHP-CS-Fixer/tree/feature/psr12>.

>
>
> We need a second implementation to move forward. Is anyone currently
> working on a second implementation?
>
>
> It’s also getting some attention from the Prettier package (see
> https://github.com/prettier/plugin-php/pull/200

> <https://github.com/prettier/plugin-php/pull/200>and
> https://github.com/prettier/plugin-php/issues/167
> <https://github.com/prettier/plugin-php/issues/167>).

>
>
> Larry Garfield has re-raised concerns. Please, take a look and
> provide any feedback you have here:
> https://groups.google.com/forum/#!msg/php-fig/vZOpga3xoLg/_Q-CbeWMAQAJ

> <https://groups.google.com/forum/#!msg/php-fig/vZOpga3xoLg/_Q-CbeWMAQAJ>.

>
>
> Michael Cullum believes this will be ready for vote in 2 months.
>
>
> PSR-14 (event manager)
>
> Status: abandoned / regrouping
>
> This PSR is getting some attention on the ML recently, and it’s
> getting discussed here:
> https://groups.google.com/forum/?fromgroups#!topic/php-fig/EwCZ9ritJcA

> <https://groups.google.com/forum/?fromgroups#!topic/php-fig/EwCZ9ritJcA>.

> Larry Garfield is trying to step in as the editor, Benni Mack and
> Stéphane Hulard have volunteered to help. Larry has said that he
> will push this forward next week, after Tuesday 20th.
>
>
> PSR-17 (HTTP factories)
>
> Status: Draft
>
> PSR entered the draft status thanks to Matthew
> (https://groups.google.com/forum/?fromgroups#!searchin/php-fig/PSR-17%7Csort:date/php-fig/A5mZYTn5Jm8/8nqDCh5TBgAJ

> <https://groups.google.com/forum/?fromgroups#!searchin/php-fig/PSR-17%7Csort:date/php-fig/A5mZYTn5Jm8/8nqDCh5TBgAJ>).

>
>
> The new PSR working group is:
>
> - Editor: Woody Gilk
>
> - Sponsor: Matthew Weier O’Phinney
>
> - Members: Stefano Torresi, Matthieu Napoli, Korvin Szanto, Glenn
> Eggleton, Oscar Otero, and Tobias Nyholm.
>
> The working group is currently looking at proposal and hope to have
> it ready to share for general review in the next two weeks.
>
>
> PSR-18 (HTTP client)
>
> Status: Draft
>
> The working group is currently deciding on an upgrade path from
> HTTPlug. They have a proposal that they think will work which is
> being reviewed by a small group and once they’re happy with it that
> will be posted to the PHP-FIG for comments.
>
>
> PSR-19? (Streams / Async)
>
> Status: Pre-Draft
>
> Currently on hold until Sara can make time in her schedule.
>
>

> --
> 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+u...@googlegroups.com

> <mailto:php-fig+u...@googlegroups.com>.

> To post to this group, send email to php...@googlegroups.com

> <mailto:php...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/php-fig/5b4bac43-6d33-4064-9be5-2bdafd9bfaa1%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/5b4bac43-6d33-4064-9be5-2bdafd9bfaa1%40googlegroups.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.

--
Matteo Beccati

Development & Consulting - http://www.beccati.com/

[Philippe Gamache]

Like I said earlier, I'm interested on PSR-9 and PSR-10. 

Was on the security team of Tiki and with Sensio. Did the only french book on PHP security (with Damien Seguy). Wrote a lot about it, and speak in different conferences (PHP and Security alike). Fonder of the OWASP Montreal Chapters. Work for 12 years as a Security Consultant on PHP projects.

[Alexey Gopachenko]

JetBrains PhpStorm development lead here.

I would like to participate in PSR-5 (and actually all others) from perspective of tool-ability and consistency of introduced features and specs.

I personally have created and still maintaining PhpStorm static analysers/type inference engine and other features.

We already have both "invented" what is now de-facto standards (eg ObjectArray[] notation, union types) and lobbied deterministic behaviour (eg. leading \ in namespace in PhpDoc  when major frameworks were adopting namespaces). We recognise that our "support" of certain conventions and technologies has an influence and always have used it with reserve and good karma in mind, keeping contact with PSR authors.

We think that more direct participation will help us to serve PHP community.

[Joe T.]

+1000 for this guy. :)