Re: PSR-17 Explicit Nullable

+1 On Mon, Apr 15, 2024, 6:28 AM Vincent de Lau wrote: > +1 from me as well. > > I would not mind a small rationale in the errata why it is `?string` and > not `string|null`. > > On Monday, April 15, 2024 at 3:19:43 PM UTC+2 Ken Guest wrote: > >> and it's a +1 from me :-) >> >> On Monday, April

Re: [Discussion][Member Projects] Chevereto membership application

On Wed, Mar 20, 2024, 6:01 AM Rodolfo Berrios wrote: > I didn't block you, we don't share any servers. I left the PHP-FIG Discord > and in all honesty, I don't feel welcomed here except by two people. It > seems that FIG doesn't need my help so why bother. > > The level of hostility and

Re: [Discussion][Member Projects] Chevereto membership application

On Sun, Mar 10, 2024, 8:57 AM Larry Garfield wrote: > On Sun, Mar 10, 2024, at 10:21 AM, Rodolfo Berríos wrote: > > Thanks Vincent and hello PHP-FIG. > > > > My name is Rodolfo Berrios and I'm software engineer from Chile. I've > > been using PHP since v5.2 and I've a lots of projects with PHP

Re: Service Provider PSR: rebooting the proposal

Thanks for putting so much effort into this Rasmus, On Fri, Jan 12, 2024 at 9:35 AM Larry Garfield wrote: > > On Fri, Jan 12, 2024, at 4:44 PM, Rasmus Schultz wrote: > > Dear Figs :-) > > > > I've been hard at work these past couple of months, since I became > > interested in the Service

Re: [Internals][ELECTIONS] Request for Nominations

I however will accept your nomination, thanks! On Wed, Feb 14, 2024, 2:37 AM 'Alexander Makarov' via PHP Framework Interoperability Group wrote: > I'll renomiate Korvin Szanto if he's willing to. Also I nominate Larry > Garfield. > > On Friday, February 9, 2024 at 5:34:23 PM UTC+3 C

Re: [VOTE][CC] Expulsion Vote for eZ Systems

+1 On Thu, Oct 5, 2023, 7:37 AM Vincent de Lau wrote: > This thread is to collect Core Committee votes on the eZ Systems Expulsion > vote. > > The proposal is to expel eZ Systems as a Member Project. > > There have been various efforts to prevent this drastic measure, without > any result. The

Re: [VOTE][CC] Expulsion Vote for Stormpath PHP SDK

+1 On Thu, Oct 5, 2023, 7:38 AM Vincent de Lau wrote: > This thread is to collect Core Committee votes on the Stormpath PHP SDK > Expulsion vote. > > The proposal is to expel Stormpath PHP SDK as a Member Project. > > There have been various efforts to prevent this drastic measure, without >

Re: [VOTE][CC] New bylaw: funding

-1 On Thu, Aug 31, 2023 at 1:07 AM Alessandro Lai wrote: > > This is the voting thread dedicated to Core Committee members only. > > I'm proposing a new bylaw do handle funding and fiscal representation of the > PHP-FIG. > > The discussion thread can be found here: >

Re: [VOTE][CC] Hyperf Membership vote

+1 On Monday, July 24, 2023 at 2:14:42 AM UTC-7 Vincent de Lau wrote: > This thread is to collect Core Committee votes on the Hyperf Membership > vote. > > The proposal is to accept Hyperf as a Member Project. Hyperf will be > represented by Leo Cavalcante. The membership application is being

Re: [VOTE][Projects] Hyperf Membership vote

+1 Concrete CMS On Monday, July 24, 2023 at 2:13:59 AM UTC-7 Vincent de Lau wrote: > This thread is to collect Member Project votes on the Hyperf Membership > vote. > > The proposal is to accept Hyperf as a Member Project. Hyperf will be > represented by Leo Cavalcante. The membership

Re: [VOTE][CC] Copyright Ownership Approval Vote

+1 On Sat, Jul 15, 2023, 11:59 AM Ken Guest wrote: > +1 > > On Sat, 15 Jul 2023, 17:47 Chuck Burgess, wrote: > >> +1 >> CRB >> *about.me/ashnazg * >> >> >> On Sat, Jul 15, 2023 at 5:49 AM Jaap van Otterdijk wrote: >> >>> +1 >>> >>> Jaapio >>> Op 14 jul. 2023, om

PER-CS Editor Stepping Down - Transition from Korvin Szanto to Larry Garfield

Hi Everyone, Now that v2.0.0 of PER-CS is tagged and released, I will be stepping down from the editor role and rejoining the working group. To replace me as Editor I have selected Larry Garfield. Larry has been an active member of our working group and I have full confidence that he will do a

Re: [VOTE][CC] Coding Style 2.0.0 Approval Vote

gt; wrote: > >> +1 >> >> On Mon, Mar 20, 2023 at 11:05 AM Korvin Szanto >> wrote: >> >>> Hi Everyone, >>> The `2.0.0` version of the Coding Style PER has been approved by its >>> working group. This update introduces requirements for new PHP

Re: PSR-12 declare(strict_types=1) and mixed with HTML should require semi-colon, causes fatal error with PHP CS Fixer

Hi Julian, The best place to effect change in coding standards these days is in PER-CS since it can actually change in future releases: https://github.com/php-fig/per-coding-style That said, I struggle to see how this isn't just an issue with CS Fixer. For example if you completely exclude CS

Re: [VOTE][CC] Coding Style 2.0.0 Approval Vote

+1 On Mon, Mar 20, 2023, 12:17 PM Larry Garfield wrote: > +1 > > -- > Larry Garfield > la...@garfieldtech.com > > On Mon, Mar 20, 2023, at 11:05 AM, Korvin Szanto wrote: > > Hi Everyone, > > The `2.0.0` version of the Coding Style PER has been approved by i

[VOTE][CC] Coding Style 2.0.0 Approval Vote

Hi Everyone, The `2.0.0` version of the Coding Style PER has been approved by its working group. This update introduces requirements for new PHP syntax and offers clarification on existing syntax such as trailing commas, empty spaces in function and class bodies, new keywords, named arguments,

Re: [VOTE][WG] Coding style 2.0.0 Readiness Vote

Thanks everyone for voting! Votes are as follows: - Korvin Szanto: +1 - Chris Tankersley: +1 - Alexander Makarov: +1 - Ken Guest: +1 - Larry Garfield: +1 - Luke Diggins: +1 - Woody Gilk: +1 I will open the CC vote later today! On Mon, Mar 20, 2023 at 8:05 AM Korvin Szanto wrote: > &

Re: [VOTE][WG] Coding style 2.0.0 Readiness Vote

Tankersley >>> http://ctankersley.com >>> >>> >>> On Mar 10, 2023 at 10:47:00 AM, Korvin Szanto wrote: >>>> >>>> Hi Everyone, >>>> I am pleased to announce that the Coding Style PER version 2.0.0 is >>>> now ready!

Re: [VOTE][PSR-7] Type declaration updates

+1 On Tuesday, March 14, 2023 at 6:33:44 AM UTC-7 Chris Tankersley wrote: > +1 > > Chris Tankersley > http://ctankersley.com > > > On Mar 13, 2023 at 4:02:57 PM, Matthew Weier O'Phinney < > mweiero...@gmail.com> wrote: > >> As the two week comment period has concluded, I hereby call a vote of

[VOTE][WG] Coding style 2.0.0 Readiness Vote

Hi Everyone, I am pleased to announce that the Coding Style PER version 2.0.0 is now ready! This version adds requirements for new PHP syntax and some clarifications for existing syntax including trailing commas, empty function and class bodies, new keywords, named arguments, match expressions,

Re: [BYLAW] New: funding bylaw

I understand that our expenses are under $100/yr total, Concrete CMS would be happy to cover that cost moving forward! I don't really get how asking for donations contributes to our mission as an organization. Can you speak how it does and to what you intend to spend extra funds on specifically?

Re: [VOTE][CC] fig/log-test 1.0.0 Approval Vote

+1 On Sun, Aug 21, 2022, 9:01 AM Cees-Jan Kiewiet wrote: > +1 > > On Sat, 20 Aug 2022 at 07:11, ch...@ctankersley.com > wrote: > >> +1 >> >> -Chris >> >> On Fri, Aug 19, 2022 at 2:17 AM Ralf Lang wrote: >> >>> Hello everyone, >>> >>> >>> I hereby call a CC vote for the approval of the first

Re: [VOTE][CC] Coding Style 1.0.0 Approval Vote

Hi Everyone, Two weeks have gone by and this vote has passed making the Coding Style PER the first approved PER! Following the order on our personnel page, the vote was as follows: +1: Larry Garfield Matthew Weier O'Phinney Cees-Jan Kiewiet Chris Tankersley Korvin Szanto Chuck Burgess Woody

Re: [VOTE][CC] Coding Style 1.0.0 Approval Vote

+1 On Wednesday, May 25, 2022 at 9:20:18 AM UTC-7 Korvin Szanto wrote: > Hi Everyone, > The Coding Style PER 1.0.0 tag has been voted ready by the working group. > This > version of the Coding Style PER is effectively the same as PSR-12 with only > basic updates to term

[VOTE][CC] Coding Style 1.0.0 Approval Vote

Hi Everyone, The Coding Style PER 1.0.0 tag has been voted ready by the working group. This version of the Coding Style PER is effectively the same as PSR-12 with only basic updates to terminology, naming, and formatting so any project compatible with PSR-12 today will also be compatible with this

Re: [VOTE][WG] Coding Style 1.0.0 Readiness Vote

Everyone has weighed in and we have voted to move forward with a CC readiness vote! Votes are as follows: - Korvin Szanto: +1 - Chris Tankersley: +1 - Alexander Makarov: +1 - Kathryn Reeve: +1 - Ken Guest: +1 - Larry Garfield: +1 - Luke Diggins: +0 - Woody Gilk: +1 I'll open the CC readiness

Re: [VOTE][WG] Coding Style 1.0.0 Readiness Vote

+1 On Thursday, May 19, 2022 at 9:21:48 AM UTC-7 Korvin Szanto wrote: > Hi Everyone, > The Coding Style PER is ready for a 1.0.0 tag! This version is effectively > the > same as PSR-12 with only basic updates to terminology, naming, and > formatting. > You can review the fu

[VOTE][WG] Coding Style 1.0.0 Readiness Vote

Hi Everyone, The Coding Style PER is ready for a 1.0.0 tag! This version is effectively the same as PSR-12 with only basic updates to terminology, naming, and formatting. You can review the full list of changes here: https://github.com/php-fig/per-coding-style/compare/8201676...master This vote

Re: [Vote] Maintainer for log-util library

+1 On Wed, May 18, 2022 at 5:44 PM Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > +1 from me. > > On Wed, May 18, 2022, 1:36 PM Larry Garfield > wrote: > >> I hereby open a Core Committee Vote to appoint Ralf Lang as Maintainer >> for a new log-util library that kinda-sorta exists

Re: [VOTE][PSR-7] Header validation errata

+1 On Wed, Apr 20, 2022 at 10:35 AM Larry Garfield wrote: > +1 > > -- > Larry Garfield > la...@garfieldtech.com > > On Wed, Apr 20, 2022, at 9:27 AM, Matthew Weier O'Phinney wrote: > > Hi, all! > > > > The two week discussion period regarding proposed errata on PSR-7 > > related to

Re: [PER-Coding-Style] Editor Change

has been inactive and unreachable for the >> last 60 days. While all of us in the working group hope everything is OK, >> as Sponsor I have decided to name a new Editor. >> >> Korvin Szanto will be taking over the Editor duties for the time being, >> and if Al

Re: [Nomination][CC] Korvin Szanto

Thank you Alex! I accept this nomination. On Sat, Dec 25, 2021, 5:42 AM 'Alexander Makarov' via PHP Framework Interoperability Group wrote: > Korvin is a core commitee member since 2016. In the past he helped getting > PSR-12 and PSR-11 done and overall moved the group to the right direction. >

Re: Add rule for PHP 8 promotion constructor in PSR-12?

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 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

Re: [Entrance Vote]{CC] Localization PSR

+1 On Wed, Dec 8, 2021, 9:42 PM Michelle Sanver wrote: > +1 > > On 8 Dec 2021, at 23:23, Woody Gilk wrote: > > +1 > > -- > Woody Gilk > https://www.shadowhand.com > > > On Wed, Dec 8, 2021 at 4:04 PM Larry Garfield > wrote: > >> +1 >> >> -- >> Larry Garfield >> la...@garfieldtech.com >>

Re: In PSR-12, what are lines 255 and 256 actually referring to?

Hi Shawn, You can trust the section header, those lines are referring to style when dealing with implements and extends. The reason we are so verbose in this spot is partly because some of this is left verbatim from PSR-2 as we added around it and partly because we want to be sure we cover all

Re: [VOTE][CC] PSR-16 (simple-cache) evolution

+1 On Sunday, October 24, 2021 at 10:52:42 PM UTC-7 Michelle Sanver wrote: > +1 > On 24 Oct 2021, 22:56 +0200, cees...@gmail.com , wrote: > > +1 > > On Tuesday, October 19, 2021 at 4:19:42 PM UTC+2 ezimuel wrote: > >> +1 >> >> Cheers, >> Enrico Zimuel >> >> Il giorno gio 14 ott 2021 alle ore

Re: [VOTE][CC] Bylaw change: introduce PHP Evolving Recommendations (PERs)

+1 On Tue, Sep 7, 2021 at 8:28 PM Chris Tankersley wrote: > +1 > > -- > Chris Tankersley > > On Tue, Sep 7, 2021 at 1:06 PM Vincent de Lau wrote: > >> This is the voting thread for the Core Committee only. There is a >> separate thread for Project Representative >> >> Larry Garfield has

Re: [VOTE][CC] AzuraCast Membership vote

+1 On Sat, Jul 31, 2021, 8:38 AM Nikolaos Dimopoulos wrote: > +1 > > Phalcon Framework > > On Saturday, July 31, 2021 at 11:05:07 AM UTC-4 vin...@delau.nl wrote: > >> This thread is to collect votes on the AzuraCast Membership vote. >> >> Details: >> - membership request: >>

Re: PSR-12 question about "endif" "endwhile" etc

Hi Liam, We discussed alternative control syntax at least once[0] (I recall a few times) and decided that we wanted to leave them unspecified for fear of needing to codify mixed PHP and HTML where they are primarily used. That says PSR-12 specifically requires control structures use brackets in

Re: [VOTE] Core Committee Election

1. Larry Garfield 2. Michelle Sanver 3. Alessandro Chitolina 4. Matthew Weier O'Phinney 5. Woody Gilk On Fri, Jun 11, 2021, 8:26 AM Jason Coward wrote: > 1) Michelle Sanver > 2) Matthew Weier O'Phinney > 3) Woody Gilk > 4) Alessandro Chitolina > 5) Larry Garfield > > Regards, > > *Jason Coward*

Re: [VOTE][Projects] Bylaw CS update

+1 On Sat, Apr 3, 2021 at 9:57 AM 'Alexander Makarov' via PHP Framework Interoperability Group wrote: > > +1 from Yii framework. > On Friday, April 2, 2021 at 7:31:06 PM UTC+3 ni...@niden.net wrote: > >> +1 >> >> Phalcon Framework >> >> On Wednesday, March 31, 2021 at 3:16:33 AM UTC-4

Re: [ENTRANCE] [VOTE] [CC] Clock Interface PSR

+1 On Monday, March 15, 2021 at 4:35:58 PM UTC-7 demon...@gmail.com wrote: > As the Sponsor for this new candidate PSR, I hereby call the Entrance Vote. > > > Proposal PR: https://github.com/php-fig/fig-standards/pull/1224 > > > Editor: Chris Seufert > Sponsor: Chuck Burgess - PHP-FIG >

Re: [Vote] PSR-13 Link Errata

+1 On Fri, Mar 5, 2021 at 12:13 AM cees...@gmail.com wrote: > +1 > > On Friday, March 5, 2021 at 9:09:18 AM UTC+1 Matteo Beccati wrote: > >> +1 >> >> On 24/02/2021 22:50, Larry Garfield wrote: >> > Since there seems to be no dissension, no sense waiting any longer. >> > >> > I am hereby calling

Re: [VOTE][PSR-11] Type Updates

+1 On Wed, Mar 3, 2021, 7:22 AM Chris Tankersley wrote: > +1 > > -Chris > > On Fri, Feb 19, 2021 at 9:31 AM Matthew Weier O'Phinney < > mweierophin...@gmail.com> wrote: > >> Hi, everyone! >> >> On 2021-01-25, I opened the discussion period around updating PSR-11 per >> the PSR Evolution bylaw

Re: [Vote] [PSR-13] updates

+1 On Sat, Jan 16, 2021, 9:07 AM Larry Garfield wrote: > I hereby call a vote of the Core Committee to approve the following PRs to > update PSR-13 to use modern PHP typing capabilities, as previously > discussed. > > This is a Core Committee vote requiring a 50% quorum and 2/3 majority, > with

Re: [Vote] [PSR-6] Type updates

+1 On Sat, Jan 16, 2021, 9:09 AM Larry Garfield wrote: > I hereby call a vote of the Core Committee to approve the following PRs to > update PSR-6 to use modern PHP typing capabilities, as previously discussed. > > This is a Core Committee vote requiring a 50% quorum and 2/3 majority, > with

Re: [VOTE][CC] Errata bylaw update

+1 On Thu, Jul 9, 2020, 8:46 AM Woody Gilk wrote: > +1 > > On Thursday, July 9, 2020 at 3:46:46 AM UTC-5 alessand...@gmail.com wrote: > >> Since the mandatory two weeks are passed on the discussion ( >> https://groups.google.com/g/php-fig/c/CObJmc5jDcE), I'm hereby calling a >> CC vote for this

Re: [VOTE][CC] TYPO3 Membership vote

+1 On Fri, Jul 3, 2020, 8:58 AM Larry Garfield wrote: > +1 > > -- > Larry Garfield > la...@garfieldtech.com > > On Fri, Jul 3, 2020, at 2:16 AM, Alessandro Lai wrote: > > This thread is to collect votes on the TYPO3 Membership vote. > > > > Details: > > - membership request: > >

Re: PSR Evolution, PSR-13, and nuance

On Mon, Mar 2, 2020 at 9:00 AM Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > > > On Sun, Feb 23, 2020 at 1:58 PM Larry Garfield > wrote: > >> OK, this has been sitting far too long now. Mostly my fault, but no one >> else seems to be pressing the issue, either... >> >>

Re: [PSR-12] Anonymous classes

at 3:35:55 AM UTC-8, Alex Makarov wrote: > > I'd prefer errata as well. > > On Fri, Jan 24, 2020 at 2:23 PM Alessandro Lai > > wrote: > > > > First we need the opinion of the editor (Korvin Szanto), to decide if we > want to correct course or just clarify our i

Re: [Nomination][CC] Korvin Szanto

Thanks Chris, I accept this nomination and I'm excited for the opportunity to continue working in the CC! On Wednesday, January 8, 2020 at 8:58:31 AM UTC-8, Chris Tankersley wrote: > > Hello everyone! > > Since his term is coming up per the notification[1], I'd like to > re-

Re: A question about PSR-12

PHP 7.1 added exception multicatch using a single pipe operator, so no we wouldn't want to use an OR operator here https://www.php.net/manual/en/language.exceptions.php On Sun, Sep 22, 2019, 8:49 AM Chuck Burgess wrote: > That's not a pipeline from code... it's only an OR delimiter in the

Re: Revert inappropriate PSR-12 post-vote merge

Hi Everyone, I totally agree that merging #1183 was an overstep on my part, the bylaws are clear that it should be a secretary managing merging and not the editor of the PSR. I also agree that some of these changes would qualify for errata, I appreciate you paying attention and holding me

Re: [VOTE] [Accept] PSR-12 Extended Coding Style Guide

Thanks for being our sponsor Chris! +1 -- 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

Re: [BYLAW] Proposal: let PSRs evolve with the language

Hi Everyone, I'm glad to see this coming up, this is something I've seen discussed a lot on and off the list. It strikes me that asking an implementor to support multiple PSR versions is too much if we're just using composer versions. The only way I can imagine implementing something like that is

Re: [VOTE] Core Committee Election

concrete5: 1. Matthew Weier O'Phinney 2. Larry Garfield 3. Woody Gilk 4. Matteo Beccati 5. Adam Englander 6. Beau Simensen 7. Benni Mack On Tue, May 14, 2019 at 5:22 AM Stefano Torresi wrote: > 1. Matteo Beccati > 2. Matthew Weier O'Phinney > 3. Larry Garfield > 4. Woody Gilk > 5. Benni Mack

Re: [ACCEPTANCE VOTE][CC] PSR-14 Event Dispatcher

> >> Beau Simensen >> Larry Garfield >> Matthew Weier O’Phinney >> Sara Golemon >> Cees-Jan Kiewiet >> Lukas Kahwe Smith >> Samantha Quiñones >> Chris Tankersley >> Korvin Szanto >> Stefano Torresi >> Michael Cullum &

Re: [VOTE][WG] PSR-12 Readiness Vote

The entire group has had a chance to weigh in and it looks like we've unanimously voted to move into review! Just to make the record clear as I totally missed adding Alessandro in my hasty copy/paste: Editor: Korvin Szanto: +1 Sponsor: Chris Tankersley: +1 Members: Alessandro Lai: +1 Alexander

Re: [VOTE][WG] PSR-12 Readiness Vote

+1 On Monday, January 28, 2019 at 9:25:37 AM UTC-8, Korvin Szanto wrote: > > Hi Everyone, > After a few revisions and additions, the PSR-12 working group is again > ready to transition out of draft and into review. > > Please do not vote in this thread unless you are

Re: [ACCEPTANCE VOTE][CC] PSR-18 HTTP Client

+1 On Mon, Oct 15, 2018 at 12:38 PM Samantha Quiñones wrote: > +1 > > -- > 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

Re: [WG][VOTE] PSR-17 Review

ditor) > - myself (Sponsor) > - Stefano Torresi > - Matthieu Napoli > - Korvin Szanto > - Glenn Eggleton > - Oscar Otero > - Tobias Nyholm > > The by-laws do not stipulate a time-frame for how long the vote must > run, though 2 weeks is the standard period. As suc

Re: [PSR-14][Entrance][VOTE]

+1 On Sat, Apr 14, 2018 at 12:45 PM Larry Garfield wrote: > On Tuesday, April 10, 2018 12:17:27 AM CDT Vilsa fur wrote: > > +1 > > You're not a member of the Core Committee. We appreciate the voice of > endorsement but this thread is just for CC members to vote.

Re: [PSR-6][Errata][Vote]

+1 On Thu, Mar 15, 2018 at 6:23 AM Stefano Torresi wrote: > +1 > > Il giorno gio 15 mar 2018 alle ore 12:53 Matthew Weier O'Phinney < > mweierophin...@gmail.com> ha scritto: > >> +1 >> >> On Mon, Mar 12, 2018, 4:22 PM Larry Garfield >> wrote: >> >>>

Re: [CC][VOTE] PSR-17 Working Group

2018-02-19, whichever occurs >> soonest. >> >> The proposed working group is as follows: >> >> - Editor: Woody Gilk >> - Sponsor: myself >> - Members: Stefano Torresi, Matthieu Napoli, Korvin Szanto, Glenn >> Eggleton, Oscar Otero, and Tobias Nyholm. &

Re: [VOTE][Internals] Secretary election

1. Robert Parker 2. Mark Railton Thanks, Korvin On Fri, Jan 12, 2018 at 6:44 AM 'Alexander Makarov' via PHP Framework Interoperability Group wrote: > +1 for Mark Railton from Yii framework. > > > On Friday, January 12, 2018 at 5:37:01 PM UTC+3, Alessandro Lai wrote:

Re: [ACCEPTANCE VOTE][CC] PSR-15 HTTP Server Request Handlers

+1 Korvin Szanto Thank you Matthew for your continued focus and dedication! On Fri, Jan 12, 2018 at 8:07 AM Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > +1 from Matthew Weier O'Phinney > > On Fri, Jan 12, 2018 at 9:47 AM, Matthew Weier O'Phinney > <mwe

[Secretary nomination] Robert Parker

Hi Everyone, I'd like to nominate Robert Parker for the position of PHP-FIG Secretary. Robert is a member of the Portland PHP meetup and strikes me as a great fit for this role. Check out Robert's profiles: https://github.com/diaboloshogunate https://twitter.com/diaboloshogun Best wishes, Korvin

Re: [CC nomination] Korvin Szanto

Thanks Adam, I accept this nomination! Best wishes, Korvin On Wed, Jan 10, 2018 at 1:21 PM Adam Culp <thegeeky...@gmail.com> wrote: > I would like to hereby nominate Korvin Szanto to the CC. > > -- > You received this message because you are subscribed to the Google Group

Re: [VOTE][WG] PSR-12 Readiness Vote

is strictly prohibited. If you have received this > communication in error, please notify me immediately by replying to this > message, and deleting it and all copies and backups thereof. > > On Nov 7, 2017, at 10:31 PM, Chris <ch...@ctankersley.com > > wrote: > > +

Re: [VOTE][WG] PSR-12 Readiness Vote

+1 On Tuesday, November 7, 2017 at 12:06:09 PM UTC-8, Korvin Szanto wrote: > > Hi Everyone, > We in the PSR-12 working group believe we are ready to move forward with > our draft. To that end, we are holding a public vote amongst ourselves on > the mailing list in order to ens

[VOTE][WG] PSR-12 Readiness Vote

decision before we continue. -- The current working group for PSR-12 is as follows: Editor: Korvin Szanto Sponsor: Chris Tankersley Members: Alexander Makarov Michael Cullum Robert Deutz Please do not reply to this thread unless your name is listed above. Thanks, Korvin -- You received

Re: [VOTE] Secretary Election

1. Alessandro Lai 2. Margret Staples 3. Mark Railton On Thu, Oct 26, 2017 at 8:59 AM Beau Simensen wrote: > 1. Margret Staples > 2. Alessandro Lai > 3. Mark Railton > > On Thursday, October 19, 2017 at 4:17:12 PM UTC-5, Michael Cullum wrote: >> >> Hi all, >> >> We've been

Re: [PSR-12] Function declarations with multiline arguments AND return type declaration

Thank you for your efforts here Vinor, it's very much appreciated! I do disagree with the idea that we should require a new line, instead we should continue to leave it up to the implementor of PSR-12 whether they'd like a newline or not. I've added this discussion to the meta document for

Re: [VOTE][CC] Entrance vote for PSR-12: Extended Coding Style Guide

+1 Korvin Szanto -- 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,

[VOTE][CC] Entrance vote for PSR-12: Extended Coding Style Guide

vote and asking kindly that the CC allows us to keep the number 12. Our working group is as follows: Editor: Korvin Szanto Sponsor: Chris Tankersley Working Group Members: Alexander Makarov Michael Cullum Robert Deutz If you'd like to read more about PSR-12, check out the completed draft[2

Re: [VOTE][CC] Entrance vote for HTTP Client

+1 Thanks! Korvin Szanto On Thu, Aug 3, 2017 at 9:28 AM Samantha Quiñones <ieatkillerb...@gmail.com> wrote: > much +1 very yusss > > -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. &

FIG 3.0 Working Group for PSR12

Hi Everyone, Thank you to Alexander Makarov for getting the ball rolling on this! I wanted to reiterate what he had written in a couple of replies; the official working group we are putting forward is as follows: Editor: Korvin Szanto Sponsor: Chris Tankersley Working Group: Alexander Makarov

Re: Proposing PSR 18 'Singleton' Pre-Draft

however, I > figured I would try to add some code to this great community :) > > Thanks, > Richard Miles > > On Sunday, February 19, 2017 at 7:59:11 PM UTC-6, Korvin Szanto wrote: > > Hi Richard, > I took a really fast look at the repo since I'm currently waiting for a > p

Re: PSR-7 Alternate Proposal

Hi Everyone, On Sun, Feb 19, 2017 at 2:04 PM John Porter wrote: > Hi Michael, > > Thanks for your response. I have read about, and personally discussed the > SOLID principles with Uncle Bob, and I do believe that there is more than > one final interpretation of those

Re: Proposing PSR 18 'Singleton' Pre-Draft

Hi Richard, I took a really fast look at the repo since I'm currently waiting for a plane. I noticed that this seems to be more of an implementation than a set of interfaces to standardize on. Are you wanting to standardize the implementation? Thanks, Korvin On Sun, Feb 19, 2017 at 5:55 PM

Re: [Vote] [Core Committee] Membership Application: Phergie

Errr to early to be reading and typing at the same time :S +1 On Wed, Feb 8, 2017 at 7:52 AM Korvin Szanto <korvinsza...@gmail.com> wrote: > +1 Phergie > On Wed, Feb 8, 2017 at 7:40 AM Samantha Quiñones <ieatkillerb...@gmail.com> > wrote: > > +1 > > -- > Y

Re: [Vote] [Core Committee] Membership Application: Phergie

+1 Phergie On Wed, Feb 8, 2017 at 7:40 AM Samantha Quiñones wrote: > +1 > > -- > 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,

Re: Enhance code readability

I agree that this could be organized to be easier to understand at a glance, but I don't understand why this is still an issue. It sounds like PHPCS is assuming that code needs to exactly match examples in every way. That's simply not the case. I've shown that the document says specifically that

Re: Enhance code readability

Hi Everyone, On Sat, Feb 4, 2017 at 11:41 AM Ryan R. wrote: > Hello, > I'd like to propose a change to the PSR-2 rule concerning the presence of > one (and only one) empty line after opening braces for conditional > statements. > I wasn't aware that this was the case,

Re: [VOTE][Accept] PSR-11 ContainerInterface

+1 concrete5 On Fri, Feb 3, 2017 at 7:32 AM Michiel Rook wrote: > +1 from Phing. > > > On 31-01-17 16:35, Matthew Weier O'Phinney wrote: > > After a couple months of review, and no additional tweaks during the > last couple weeks, we are ready to initiate an acceptance

Re: Membership Request: H.Bora ABACI (Catappa)

Hi, In order to begin the process of being accepted into the group you first need to have a sponsor. Just a quick look into the project shows no issues or pull requests open or closed, is this a new project without a community? If so you may find it much easier to contribute as an individual once

Re: [VOTE][Accept] PSR-16: Simple Cache

+1 concrete5 On Fri, Dec 30, 2016 at 2:58 PM Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > -1 from Zend Framework > > I'm missing a few details in the meta document and the spec for which I > cannot find discussions: > > - I've seen a number of libraries allow a callback for the

Re: [VOTE] First Core Committee Elections

Hi All, I'm super excited about this lineup of names, I think the PHP is going to benefit immensely from this first CC. Korvin Szanto Larry Garfield Sara Golemon Matthew Weier O’Phinney Beau Simensen Graham Daniels Gary Hockin Cees-Jan Kiewiet Tobias Nyholm Chris Tankersley Samantha Quiñones I

Re: [CC][Nomination] Korvin Szanto

are meant for and don't become overcomplicated like we've seen happen in the past. Best wishes, Korvin On Mon, Nov 14, 2016 at 1:02 PM Michael Cullum <m...@michaelcullum.com> wrote: Thanks both! http://bit.ly/cc-election-candidates -- Michael C On 13 November 2016 at 19:01, Korvin Szanto <kor

Re: [Internals] Change to FIG 3.0 term lengths

I was going to remain silent since I didn't have objections but it looks like we are going to be +1'ing instead. So +1 :) On Wed, Dec 7, 2016 at 11:34 AM Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > On Tue, Dec 6, 2016 at 9:24 AM, Michael Cullum > wrote:

Re: [CC Nomination] Chris, Tobias, Sam, Beau, Marc, Steve

hank you for the deciding to nominate me formally. > > I, in turn, accept the nomination request from Korvin. > > -Chris > > On Dec 7, 2016 6:19 PM, "Korvin Szanto" <korvinsza...@gmail.com> wrote: > > Hi Everyone > I am posting here to formally nominate the pe

[CC Nomination] Chris, Tobias, Sam, Beau, Marc, Steve

Hi Everyone I am posting here to formally nominate the people who have posted to the list but haven't had a nomination come in yet. I think it's better to have more people in the running and to let the electorate decide instead of letting our inaction be the decider, so I'm going to flex my fig

Re: [PSR-12]

Hi All, This is something that we polled with the survey. At this point we are still waiting for some member replies but I can tell you that by and large things were pretty unanimous. As far as this specific issue, it looks like 94% responded with no objections and 2/3rds of responses preferred

Re: [CC][Nomination] Korvin Szanto

I accept this nomination, thanks Adam! Best wishes, Korvin On Sun, Nov 13, 2016 at 2:34 PM Adam Culp <thegeeky...@gmail.com> wrote: > I hereby nominate Korvin Szanto for the FIG CC. He is a regular > contributor, and constructively communicates to find meaningful solutions > to i

Re: [Internals][FIG 3.0] Extending Nomination Period & Delaying FIG 3.0 Transition

We definitely need to delay this. Thank you for raising the issue Michael and Roman. On Wed, Nov 9, 2016 at 9:53 AM Larry Garfield wrote: > Under the circumstances, I do not object. What end-date are you proposing > for nominations? Early December? > > --Larry Garfield

Re: [CC][Nomination] Samantha Quiñones

Errm we can delete posts on google groups at our own discretion? Is there a way to disable that? On Tue, Nov 8, 2016 at 6:37 AM Adam Culp wrote: > Sorry about that. Appears that in my posting to multiple similar threads > I pasted the link to a thread I'd previously

Re: [VOTE][Accept] PSR-13: Link Definition Interfaces

+1 concrete5 On Mon, Nov 7, 2016 at 5:30 AM Matteo Beccati wrote: > +1 from Revive Adserver > > On 31/10/2016 22:15, Matthew Weier O'Phinney wrote: > > Per the by-laws, the required review period has passed for the > > proposed standard PSR-13 (Link Definition Interfaces).

[PSR-12] Survey for outstanding issues

Hi All, I've been dragging my feet a bit on getting this survey completed and put out there, but I think we're now ready to get some real feedback. We will be accepting responses to this survey for about the next two weeks. I'm not going to be super specific about the timing of it, but at some

Re: Output escaping PSR

Hi Chris, Are you thinking like a text filter PSR or more of an output management PSR? It sounds like a single interface with a single method to me: `FilterInterface::filter($mixed): mixed;`. Thanks, Korvin On Tue, Oct 4, 2016 at 7:39 AM Chris Riley wrote: > Hi, > > I

Re: [Review][Discuss] FIG 3.0 Upcoming Vote

Great job guys, I'm excited to see where this takes us and the php community at large. I will say that it's too bad this discussion period was wasted, it would've been nice to have an opportunity to talk about fig 3.0 at all. Thanks, Korvin On Sat, Sep 17, 2016 at 8:06 AM Paul Jones

  1   2   >