Hi all, I realise this is a little old now and things have probably moved on again, but I'm interested in helping to get PSR-5 back in the game. I believe it's an important standard to establish and am happy to help as needed.
Thanks, Robbie On Friday, 16 March 2018 09:42:32 UTC+1, Alessandro Lai wrote: > > Hello all! > If anyone like you is interested in helping pushing PSR-5 back in the > draft stage, please contact Chuck (which is willing to step in as a new > Editor) or to us secretaries (me, Mark Railton or Margaret Staples). We > need 5 persons (including an editor and a CC sponsor) to build a Working > group; also refer to the previous discussion here: > https://groups.google.com/forum/?fromgroups#!topic/php-fig/bcV4KXIW6dQ > > Thank you! > > Il giorno venerdì 16 marzo 2018 04:33:01 UTC+1, Joe T. ha scritto: >> >> Interest here as well. Basically on stand-by waiting for further >> instruction. >> >> -joe >> >> >> On Thursday, 15 March 2018 14:33:50 UTC-4, Chuck Burgess wrote: >>> >>> Hey Alice, >>> >>> I'm slowly trying to form a Working Group in order to resurrect PSR-5. >>> >>> CRB >>> >>> >>> On Mar 15, 2018 13:28, "Alice Wonder" <alicedo...@gmail.com> wrote: >>> >>> Is there any desire to bring something like PSR-5 back? >>> >>> There are two reasons why I think there should be some standards related >>> to the doc block. >>> >>> A) For legal reasons, every file needs to have author(s) and license >>> specified in a way that it can be programmatically retrieved. >>> >>> File level comment with @author and @license seems to be the defacto way >>> that is done. >>> >>> B) Code analysis tools often use function comment blocks to determine >>> what type a parameter should be and what type the output should be. Psalm >>> is a good tool for doing that, and since I started using Psalm it has found >>> many bugs of mine that I otherwise would never have triggered myself but I >>> could see how someone using my classes might. >>> >>> But there is some confusion there. I usually specify the types as they >>> would be used in type hinting (e.g. bool or int) but some standards want >>> those same types expressed as boolean or integer. vimeo/psalm seems to like >>> the way I do it, may work with the other I don't know, but that's where a >>> standard like PSR-5 would be useful. It could specify how to indicate the >>> type and then both code analysis tools and programmers can follow the spec. >>> >>> For the most part I think the old PEAR standard is good and most of my >>> checking is done against that, but I just wanted to express that at least >>> one user would be very interested in something like PSR-5 existing. >>> >>> Thank you for your time. >>> >>> -- >>> 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/27026c23-9142-432b-88ad-7f99a87fecde%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/php-fig/27026c23-9142-432b-88ad-7f99a87fecde%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/669c30e5-eb61-420c-af56-fab8461484f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
