Re: PSR-17 Explicit Nullable

[Korvin Szanto]

+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 15, 2024 at 2:11:00 PM UTC+1 Matteo Beccati wrote:
>>
>>> +1
>>>
>>>
>>> thanks for the quick follow up!
>>>
>>> On Mon, Apr 15, 2024 at 2:12 PM Woody Gilk  wrote:
>>>
 As editor of PSR-17, I hereby call a vote to:

1. Change the minimum required version of PHP to 7.1 for PSR-17.
2. Add explicit nullable types to PSR-17 interfaces.
3. Tag a new release v1.1.0 of psr/http-factory with changes (1)
and (2).

 The relevant PRs are:

 https://github.com/php-fig/fig-standards/pull/1321
 https://github.com/php-fig/http-factory/pull/17

 Thank you,

 --
 Woody Gilk (he/him)
 https://www.shadowhand.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+u...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/php-fig/CAGOJM6JNuwYA9Twh-0FJZ7sgQ_kaLCdBUSHMTRLXgb95TSox4Q%40mail.gmail.com
 
 .

>>>
>>>
>>> --
>>> --
>>> Matteo Beccati
>>>
>>> Development & Consulting - http://www.beccati.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/c57a495e-f641-4891-919d-ea86dae170e4n%40googlegroups.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/CANeXGWXNFcp5x8h9%2Bz%2BNBWGNTe_a0hV7dkVOb%3DetTGOnNVBWoQ%40mail.gmail.com.

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

[Korvin Szanto]

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 regression that I read at phpc.social is just
> not what I'm looking for in my life, in all these years working in systems
> (since 2007) I never felt the urge of being part of the PHP community but
> when I reached certain age I wanted to be more active and perhaps bring
> something else to the table.
>
> It is sad to see how caustic people can get just because they don't want
> you in. Seeking excuses to start copyright infringement, calling morally
> questionable for picking certain names. I even saw people mentioning "it's
> for artisans!" as mocking Laravel users.
>
> You as a community have a serious problem when you enable this witch hunt.
>
> I don't want to be part of this.
> Sorry.
>
> On Wed, Mar 20, 2024 at 7:56 AM Vincent de Lau  wrote:
>
>> Hi Rodolfo,
>>
>> Since you blocked me on Discord, I have to take this public route to
>> continue this discussion.
>>
>> You have stated that you feel bullied and excluded and I'm sorry you feel
>> that way. However, after reading the discussions here, on Mastodon and
>> Discord, I don't see any behavior that would typically be labeled
>> unacceptable. The concerns raised about potential trademark and copyright
>> infringement are valid in my opinion. In the case of xrDebug, while it
>> technically might not be illegal, I perfectly understand Derick's
>> frustration and the confusion it might cause within the PHP community at
>> large.
>>
>> In my view multiple people were engaging with you to get their questions
>> answered and find solutions for the aspects that could be problematic.
>> Nobody in the FIG outright attacked you, shunned you or tried to exclude
>> you. Maybe there are some cultural or language barriers in the way,
>> although I am thinking this is more a personality issue.
>>
>> You have indicated that you don't want to be part of this group anymore,
>> although you didn't specifically ask me to cancel the application, nor did
>> you do so yourself. Since you have blocked conversation with me as the
>> Sponsor, I can no longer be the Sponsor of this application, and thus I
>> will cancel it.
>>
>> Having said all this, feel free to contact me again is you want to
>> reflect on what transpired over the last 24 hours. I wish you and your
>> projects all the best and still hope to see you around in the PHP community.
>>
>> Kind regards,
>> Vincent de Lau
>> PHP-FIG Core Committee member
>>
>> On Wednesday, March 20, 2024 at 11:05:50 AM UTC+1 Rodolfo Berrios wrote:
>>
>>> On the debugger name controversy this is ridiculous. Simple as that, I
>>> don't wan to be part of this group if that's how you embrace diversity.
>>>
>>> Very disappointed that nobody is saying anything on how these guys are
>>> bullying my pet project.
>>>
>>> El El mié, 20 mar. 2024 a la(s) 04:53, Alessandro Lai <
>>> alessand...@gmail.com> escribió:
>>>

 Thank you Rodolfo for the quick answer.

 I raised those concerns because you, as a person, are requesting to
 join the PHP-FIG as a representative of your project, and that's not only
 the project that is under scrutiny. I personally, being a secretary, don't
 even have the right to vote on your membership, but I wanted these concerns
 addressed so that everyone with voting rights could decide if and how to
 weight those on your membership request.

 Clarification: these below are my personal considerations, that aren't
 in any mean intended as a PHP-FIG official opinion.

 You answered that you "didn't intend" to infringe on copyright or
 trademarks, but to the eye of the law that doesn't matter, you're still
 committing copyright/trademark infringement, and it's a pretty clear and
 cut case, since you're using companies' trademarks, which IIRC aren't even
 covered by rules like fair use. You can't consider yourself in the right
 just because none of these companies haven't discovered you or bothered to
 issue a cease and desist to you, you're still infringing. And open source,
 the very core mission or PHP-FIG, is founded on copyright licenses, so I'm
 worried of your low consideration on this topic.

 I welcome your clarification on xrdebug, and I've also seen on Reddit
 that you consider it an open source alternative to Spatie's Ray, not to a
 full fledged debugger; but still, you're using a name that very closely
 resembles an established, widely known and copyright-covered tool, which is
 possibly not trademarked only because Derick didn't have the funds to
 register it; this is even a bit worse once we consider it not a proper
 debugger, because it makes me question further why you decided for such a
 

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

[Korvin Szanto]

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 as you
> > may check on Vincent's intro. I'm applying here because I want to get
> > more involved with the community around the language and its user
> > standards, I think that I can bring value here and learn from all of
> > you.
> >
> > I started Chevereto (2007) to learn PHP and I've been living from it
> > all these years. It is a high level system, used as a Flickr/Imgur
> > replacement. When I started with Chevere (2018) I got more into low
> > level components as I noticed lacking of certain software in PHP and I
> > got more interested in interoperability.
> >
> > I do belive that PHP-FIG is relevant, it represents what I want for PHP
> > and I want to be part of this group.
> >
> > Cheers,
> > Rodolfo.
>
> Hi Rodolfo.  It looks like an interesting and successful project.  I do
> have one question.  The GitHub repo lists the project as AGPLv3.  The
> pricing page talks about needing license keys.  How exactly does that
> work?  I do not understand this model.
>
> --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/5d59b758-ee4b-4d37-9b5e-665ad58655f6%40app.fastmail.com
> .
>

Welcome Rodolfo!
I see Chevereto has a paid closed source version and a free open source
version that has some features removed[1], is that correct? If so does the
paid version have a specific name that might help someone distinguish the
open source project that has FIG membership from the paid project that
potentially doesn't?

Thanks for your interest, Chevere and Chevereto look like good additions to
the group.

Best,
Korvin

1.
https://rodolfoberrios.com/2022/12/01/chevereto-goes-free/#%F0%9F%98%98-made-for-personal-usage

-- 
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/CANeXGWXOygUPEkihpHi3%2BF91Qjm7sQ1j-sKBNcD%3D54u4g%3DwgaA%40mail.gmail.com.

Re: Service Provider PSR: rebooting the proposal

[Korvin Szanto]

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 Provider PSR proposal again.
> >
> > I've spent many nights and have read through every issue and comment on
> > the issue tracker, and many old discussions here on the group, going
> > back as far as 6-7 years.
> >
> > I eventually ended up writing a proper draft for the PSR itself, as
> > well as a meta-document. And the updated proposal features optional
> > dependency enumeration, which you can read more about in the new
> > documents.
> >
> > You can find the new documents here:
> >
> > https://github.com/container-interop/service-provider
> >
> > This is a call for participation! I'd like to invite you to read the
> > drafts, comment on open issues, and contribute to discussions.
> >
> > Note that the "Issues" tab on the Github page is intended for issues
> > with the documents themselves, while the "Discussion" tab should be
> > used to propose ideas and discuss implications. ("there is a problem
> > with the spec" is an issue, while "how about this cool idea" is a
> > discussion.)
> >
> > I worked hard on this, and I'm taking the lead on another push to bring
> > this proposal to fruition, so I really hope some of you will take an
> > interest. Let's make it happen! :-)
> >
> > Thank You.
> >
> > Regards,
> >   Rasmus Schultz
>
> First off, thank you for resurrecting this topic.  I argued at the time of 
> PSR-11 that the registration side was at least as important as the extraction 
> side, and while I eventually came around on PSR-11 doing just the extraction 
> part, I still believe the registration side is just as important.

I totally agree, it'd be really nice to be able to provide a generic
implementation of some kind that makes accessing my library as
painless as possible.

> That said, I don't think the current approach is viable.  I appreciate the 
> simplicity argument for it over some of the alternatives, but it has one 
> rather large flaw: It's incompatible (as far as I can tell) with compiling or 
> optimizing containers.
>
> To be very brief (more for the audience than for Rasmus, who I'm sure knows 
> this already), some containers do all registration at runtime.  In that case, 
> having every provider return an array of closures works well enough.  Others 
> collect the service and dependency information once and code-generate a file 
> or files that are used at runtime, with all the information pre-computed so 
> the registration process does not need to run.
>
> The quality of compiled container output varies widely, but all of them are 
> substantially faster than a runtime container.  The best use generated 
> match() statements, which benchmarks show are faster than even a chain of 
> if-statements and, likely, an array lookup to a closure.  In the ideal case, 
> you end up with generated code like:
>
> public function get(string $service): mixed
> {
> return $this->cache[$service] ??= match($service) {
> \App\A::class => new \App\A(),
> \App\B::class => new \App\B($this->get(\App\A::class)),
> \App\C::class => new \App\C($this->get(\App\A::class), 
> $this->get(\App\C::class), 'some-constant'),
> default => throw new Exception(...);
> };
> }
>
> (You could actually do better than that, but I'm trying to keep it simple.)
>
> The problem is, Closures cannot be serialized.  That means the factory 
> approach as presented is incompatible with a compiled container; the only 
> option would be to do some kind of AST parsing of the closure and regenerate 
> its code, which... ew.
>
> So standardizing registration on a mechanism that is incompatible with 
> high-performance containers seems... not great.  I realize the alternatives 
> with standard file formats have their own challenges, which is why they 
> haven't been done yet.
>
> I think probably the best option would be to effectively standardize 
> something along the lines of Symfony's compiler passes, with a more modern 
> API design.  Pass a ContainerBuilder to a series of objects with some 
> standard interface for defining and modifying service entries.  With the data 
> then in-memory in an abstracted form, it could be used at runtime or 
> compiled, as the container implementation prefers.
>
> Part of me wants to build such a compiler-pass system on top of PSR-14, since 
> it's virtually the same model.  (And that kind of "registration pass" was an 
> explicit design target of PSR-14.)  It could probably be done in a 
> PSR-14-optional way.
>
> --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 

Re: [Internals][ELECTIONS] Request for Nominations

[Korvin Szanto]

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 Chuck Burgess wrote:
>
>> I'll renominate Ken.
>> CRB
>>
>> On Fri, Feb 9, 2024, 07:57 Ken Guest  wrote:
>>
>>> I would like to serve another term as a member of the Core Committee, so
>>> I am seeking a renomination.
>>>
>>> Thanks
>>>
>>> Ken
>>>
>>> On Fri, 9 Feb 2024 at 13:05, Mark Niebergall 
>>> wrote:
>>>
>>>> My apologies all, I have a typo in the date for elections ending.
>>>>
>>>> On Thursday, February 8, 2024 at 5:19:21 PM UTC-7 Mark Niebergall wrote:
>>>>
>>>> Hello Everyone,
>>>>
>>>> It is a little late, but it is election time again. To make up for some
>>>> time, we are immediately opening the nominations.
>>>>
>>>> The following 4 Core Committee seats are up for election: Chris
>>>> Tankersley, Korvin Szanto, Enrico Zimuel, and Ken Guest.
>>>>
>>>> There is also 1 Secretary position up for election: Steve Winter.
>>>>
>>>> Those with seats expiring may express their intention to run again for
>>>> election. Anyone else is also welcome to seek a nomination to be included
>>>> in the election.
>>>>
>>>> Nominations will be open until 2024-02-16 00:00 UTC, at which time the
>>>> election will start. Elections will run for two weeks, ending 2024-01-01
>>>> 00:00 UTC.
>>>>
>>>>
>>>>  Elections will run for two weeks, ending 2024-03-01 00:00 UTC (not
>>>> 2024-01-01, which has already passed).
>>>>
>>>>
>>>>
>>>> Feel free to reach out to the other two secretaries (Alessandro and
>>>> Mark), or any other sitting PHP-FIG member, to ask for a nomination or for
>>>> further information.
>>>>
>>>> *FAQ:*
>>>>
>>>> Q: Who can be nominated?
>>>> A: Anyone! The secretaries of the PHP-FIG are basically administrative
>>>> clerks and community handlers. For more details, see
>>>> https://www.php-fig.org/bylaws/mission-and-structure/#secretaries
>>>> The CC members of the PHP-FIG are basically the technical steering
>>>> committee; citing the bylaw:
>>>> https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee
>>>>
>>>> Q: Who can nominate?
>>>> A: Citing the bylaw: "Candidates for Secretary or the Core Committee
>>>> must be nominated/proposed by an existing Project Representative or FIG
>>>> Secretary to be considered, and must publicly accept their nomination in
>>>> order to be valid. Prospective candidates may seek nominations in any way
>>>> they see fit."
>>>>
>>>> For full election bylaws, please see the PHP-FIG bylaws:
>>>> https://www.php-fig.org/bylaws/elections-and-vacancies/
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Mark Niebergall
>>>> PHP-FIG Secretary
>>>>
>>>> --
>>>> 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 view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/php-fig/17464186-b8c2-45eb-8c45-7a57b72a3a6an%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/php-fig/17464186-b8c2-45eb-8c45-7a57b72a3a6an%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>> 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 php-fig+u...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/php-fig/CAKcc2m8%2BTR1BsAfwvV3rKErjbtjVU8PNvhhomR9XCKeEDtnRkw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/php-fig/CAKcc2m8%2BTR1BsAfwvV3rKErjbtjVU8PNvhhomR9XCKeEDtnRkw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/99f50b27-7da2-4a83-8b94-cbe7648c49e7n%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/99f50b27-7da2-4a83-8b94-cbe7648c49e7n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CANeXGWXujNQKBNWFQVQ7-EH5D5-bNx_m%2B9_JVRFN91krNHO5-w%40mail.gmail.com.

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

[Korvin Szanto]

+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 final discussion thread with the background leading to this
> proposal can be found here:
> https://groups.google.com/g/php-fig/c/zYvUOTH-y3I
>
> Voting ends by 2023-10-19 17:00 UTC
>
> Voting options:  For (+1), Against (-1), or Abstain (+0)
> Quorum: 50%
> Majority: 50%
> https://www.php-fig.org/bylaws/voting-protocol/#expulsion-vote
>
> ONLY CORE COMMITTEE MEMBERS CAN VOTE HERE
>
> --
> 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/f1b409b7-0463-4b67-b840-99ab90011b61n%40googlegroups.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/CANeXGWXjDvnm_G7vbvLH6fudRdXPS%3DB7W_FuQavagpzo81Nh%2Bg%40mail.gmail.com.

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

[Korvin Szanto]

+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
> any result. The final discussion thread with the background leading to this
> proposal can be found here:
> https://groups.google.com/g/php-fig/c/zYvUOTH-y3I
>
> Voting ends by 2023-10-19 17:00 UTC
>
> Voting options:  For (+1), Against (-1), or Abstain (+0)
> Quorum: 50%
> Majority: 50%
> https://www.php-fig.org/bylaws/voting-protocol/#expulsion-vote
>
> ONLY CORE COMMITTEE MEMBERS CAN VOTE HERE
>
> --
> 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/7d95e151-c1ab-42a1-a0bc-177f2b1f0438n%40googlegroups.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/CANeXGWV9sCG7%2Bq5V%2BtpD6ovyYEa0C1arM2iwvPJHBHdQE0pp4g%40mail.gmail.com.

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

[Korvin Szanto]

-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: 
> https://groups.google.com/g/php-fig/c/6uC3hjL0Nig
> Further discussion and the full text of the bylaw can be found in this PR: 
> https://github.com/php-fig/fig-standards/pull/1295
>
> Per voting protocol: https://www.php-fig.org/bylaws/voting-protocol/
>
> Voting options are For (+1), Against (-1), or Abstain (+0)
> Quorum is 50%, a 2/3 majority is required for passage.
> Voting ends in two weeks, 2023-09-14 17:00:00 UTC
>
> --
> 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/6661ea7f-22ba-4c2e-97dd-f0a97ee73ff7n%40googlegroups.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/CANeXGWWr9p%2BNu6W1AfhZZyUhvxCfWAt3VogrF6Dy_%2BXtTS5xiQ%40mail.gmail.com.

Re: [VOTE][CC] Hyperf Membership vote

[Korvin Szanto]

+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 
> sponsored by Vincent de Lau as a Core Committee member.
>
> The membership application and discussion thread can be found here: 
> https://groups.google.com/g/php-fig/c/zwsMt9E6wzw
>
> Voting ends by 2023-08-07 10:00 UTC
>
> Voting options:  For (+1), Against (-1), or Abstain (+0)
> Quorum: 50%
> Majority: 50%
> https://www.php-fig.org/bylaws/voting-protocol/#membership-vote
>
> ONLY CORE COMMITTEE MEMBERS CAN VOTE HERE

-- 
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/c4e90519-5816-4949-9f1f-209b1ff45a16n%40googlegroups.com.

Re: [VOTE][Projects] Hyperf Membership vote

[Korvin Szanto]

+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 application is being 
> sponsored by Vincent de Lau as a Core Committee member.
>
> The membership application and discussion thread can be found here: 
> https://groups.google.com/g/php-fig/c/zwsMt9E6wzw
>
> Voting ends by 2023-08-07 10:00 UTC
>
> Voting options: For (+1), Against (-1), or Abstain (+0)
> Quorum: none
> Majority: 50%
> https://www.php-fig.org/bylaws/voting-protocol/#membership-vote
>
> ONLY PROJECT REPRESENTATIVES CAN VOTE HERE, see current list: 
> https://www.php-fig.org/personnel/#member-projects

-- 
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/64e51c20-7db6-47d4-86b1-02ea6f8b59cfn%40googlegroups.com.

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

[Korvin Szanto]

+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 18:48, Vincent de Lau  schreef:

 +1

 Kind regards,
 Vincent de Lau

 On Friday, July 14, 2023 at 6:45:01 PM UTC+2 Navarr Barnier wrote:

> +1
>
> On Friday, July 14, 2023 at 12:36:35 PM UTC-4 Larry Garfield wrote:
>
>> +1
>>
>> --
>> Larry Garfield
>> la...@garfieldtech.com
>>
>> On Fri, Jul 14, 2023, at 4:24 PM, Mark Niebergall wrote:
>> > Hi Everyone,
>> >
>> > I'm calling a CC vote for the approval of the Copyright Ownership
>> > updates. This change adds a "Copyright Ownership" section to the
>> > Licensing Policies section
>> > (https://www.php-fig.org/bylaws/licensing-policies/). The
>> associated PR
>> > is: https://github.com/php-fig/fig-standards/pull/1290
>> >
>> > Approval Voting rules apply
>> > (https://www.php-fig.org/bylaws/voting-protocol/#vote-types):
>> > • Only Core Committee members may vote, either For (+1), Against
>> (-1),
>> > or Abstain (+0). Quorum is 50%. A 2/3 majority is required for
>> passage.
>> > Voting will be open for two weeks (until 2023-07-28 16:30:00 UTC)
>> or
>> > until all quorum members have voted, whichever occurs first. If the
>> > vote passes, the PR will be merged and the Licensing Policies will
>> be
>> > updated on the website.
>> >
>> > - Mark Niebergall
>> >
>> >
>> > --
>> > 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 view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/php-fig/bac05ee7-803a-444d-949f-43443a6e0b51n%40googlegroups.com
>> > <
>> https://groups.google.com/d/msgid/php-fig/bac05ee7-803a-444d-949f-43443a6e0b51n%40googlegroups.com?utm_medium=email_source=footer>.
>>
>>
> --
>>> 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/6389df02-09cd-43c5-9f15-fff627698135%40ijaap.nl
>>> 
>>> .
>>>
>> --
>> 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/CANsgjnuk86z40ag0ECMaw3usxENZTw8kKOYdha_UFwWkvh6W-A%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/CAKcc2m__UuqMJbqhHzKYLxGxe%3DxdbWZE56JaqcZRmNeZwn2bYQ%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/CANeXGWWkP8xf5oraf1oObxiu91G6Kx8g93%3Dp7LuH%3DGLBnfAgqg%40mail.gmail.com.

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

[Korvin Szanto]

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 great job as Editor. I believe he has a
great vision for the future of PER-CS and will continue to guide it in
the right direction.

Thank you all for the support during my time as Editor,
Korvin

-- 
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/CANeXGWXx5nN4%3DWcfTotCg89AuS1yxkEOu5LuU0w6Xg%3Dw7N13Wg%40mail.gmail.com.

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

[Korvin Szanto]

Hi Everyone,
This vote has passed with 10 in favor, 0 opposed, and 0 abstaining. I'll
get v2.0.0 tagged!

Thanks,
Korvin


On Sun, Apr 2, 2023 at 12:45 AM Cees-Jan Kiewiet  wrote:

> +1
>
> On Mon, 27 Mar 2023 at 16:28, Matthew Weier O'Phinney <
> mweierophin...@gmail.com> 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 syntax
>>> and offers clarification on existing syntax such as trailing commas,
>>> empty spaces in function and class bodies, new keywords, named
>>> arguments, match expressions, short closures, enums, attributes, and
>>> more.
>>>
>>> You can review the full list of changes here:
>>> https://github.com/php-fig/per-coding-style/compare/1.0.0...0e0fc1d
>>>
>>> This is an approval vote limited to the Core Committee. A 50% quorum
>>> and a 2/3 majority are required for this vote to pass. If successful
>>> `0e0fc1d` will be tagged as `2.0.0`.
>>>
>>> Thanks,
>>> Korvin
>>>
>>> --
>>> 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/CANeXGWW7VPwak_u84%3DyTiGW5MywencSrkYqD_M1WOd3gAoM_BA%40mail.gmail.com
>>> .
>>>
>>
>>
>> --
>> Matthew Weier O'Phinney
>> mweierophin...@gmail.com
>> https://mwop.net/
>> he/him
>>
>> --
>> 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/CAJp_myWX%2B%2B1q91-hSES-RdOtXTsB9WBNLwd_juhVkUoGK33Pkw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/php-fig/CAJp_myWX%2B%2B1q91-hSES-RdOtXTsB9WBNLwd_juhVkUoGK33Pkw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> <http://wyrihaximus.net/>
> Website
> <http://wyrihaximus.net/?utm_source=signature_medium=email_campaign=emailsignature>
>  | Blog
> <http://blog.wyrihaximus.net/?utm_source=signature_medium=email_campaign=emailsignature>
>  |
> Github <https://github.com/WyriHaximus> | Linkedin
> <http://nl.linkedin.com/in/ceesjankiewiet> | Twitter
> <http://twitter.com/wyrihaximus>
>
> --
> 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/CAPY1sU-e6Dy3%3DGRd80gHCKn4NJRmTu0beBMowfZB%2BXewDohFRQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAPY1sU-e6Dy3%3DGRd80gHCKn4NJRmTu0beBMowfZB%2BXewDohFRQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CANeXGWVhSvh_269SL4tuEA9p_hiOEunZo%3D5C0R8j_Pgz0J6LTg%40mail.gmail.com.

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

[Korvin Szanto]

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 Fixer the following is valid and
parses fine:

```

Hello Word
```
https://3v4l.org/oJlV4

Restricting valid syntax in order to prevent unforeseeable bugs in
third-party tools would require us to make guesses about what to disallow
which would lead to a more restrictive spec without improving readability.

On Thu, Mar 30, 2023, 6:29 AM 'Julian Wittorf' via PHP Framework
Interoperability Group  wrote:

> The title basically says it all but I'll list the issue I found so one can
> reproduce it:
>
>1. Copy the code example from
>
> https://www.php-fig.org/psr/psr-12/#3-declare-statements-namespace-and-import-statements
>into a file and DO NOT add optional semi-colon (although this is a part of
>the PHP manual
>https://www.php.net/manual/en/control-structures.declare.php)
>2. Run PHP CS Fixer on the file
>3. The code is now broken, because the fixer kind of thinks it's a
>function (call? declaration?) (but not really either), see code example
>below.
>4. This FatalError could simply be prevent if the semi-colon is
>required in PSR-12.
>
> Broken/resulted code due to the missing semi-colon:
>  ;
> } ?>
> 
> ...
>
> I'm aware the PHP-FIG can't respond to all the tools out there but I'm
> just trying to make the point, that a coding standard must not make
> recommendations, that don't follow the official language documentation and
> general coding best practices like "finish a statement/instruction properly
> with a terminating semicolon" which is mentioned in the manual as well:
> https://www.php.net/manual/en/language.basic-syntax.instruction-separation.php
>
> --
> 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/3564160b-b997-4f6a-a3d8-9e61baa35659n%40googlegroups.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/CANeXGWURhs-frA%2B9kvEmdGCmpOix%3Dhtrev4qdWHvWN%2BWj%2Bm%3D2w%40mail.gmail.com.

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

[Korvin Szanto]

+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 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, match expressions, short closures, enums, attributes, and
> > more.
> >
> > You can review the full list of changes here:
> > https://github.com/php-fig/per-coding-style/compare/1.0.0...0e0fc1d
> >
> > This is an approval vote limited to the Core Committee. A 50% quorum
> > and a 2/3 majority are required for this vote to pass. If successful
> > `0e0fc1d` will be tagged as `2.0.0`.
> >
> > Thanks,
> > Korvin
> >
> > --
> > 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/CANeXGWW7VPwak_u84%3DyTiGW5MywencSrkYqD_M1WOd3gAoM_BA%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/d5043493-e5e8-4f01-b1b9-6594dc2bb89e%40app.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/CANeXGWWrn69qcAW9a7Ui3unE4caeBWZqBqY%2BN_--o2LJuhO0Nw%40mail.gmail.com.

[VOTE][CC] Coding Style 2.0.0 Approval Vote

[Korvin Szanto]

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, match expressions, short closures, enums, attributes, and
more.

You can review the full list of changes here:
https://github.com/php-fig/per-coding-style/compare/1.0.0...0e0fc1d

This is an approval vote limited to the Core Committee. A 50% quorum
and a 2/3 majority are required for this vote to pass. If successful
`0e0fc1d` will be tagged as `2.0.0`.

Thanks,
Korvin

-- 
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/CANeXGWW7VPwak_u84%3DyTiGW5MywencSrkYqD_M1WOd3gAoM_BA%40mail.gmail.com.

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

[Korvin Szanto]

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:
>
> +1
>
> On Mon, Mar 20, 2023 at 7:57 AM Woody Gilk  wrote:
> >
> > +1
> >
> > On Friday, March 10, 2023 at 12:12:28 PM UTC-6 Ken Guest wrote:
> >>
> >> +1
> >>
> >> On Fri, 10 Mar 2023 at 17:52, Chris Tankersley  
> >> wrote:
> >>>
> >>> +1
> >>>
> >>> Chris 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! 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, short closures, enums and attributes, and more.
> >>>>
> >>>> You can review the full list of changes here:
> >>>> https://github.com/php-fig/per-coding-style/compare/1.0.0...master
> >>>>
> >>>> This vote is limited to the members of the working group:
> >>>>
> >>>> - Editor: Me
> >>>> - Sponsor: Chris Tankersley
> >>>> - Alexander Makarov
> >>>> - Ken Guest
> >>>> - Larry Garfield
> >>>> - Luke Diggins
> >>>> - Woody Gilk
> >>>>
> >>>> This is a readiness vote so quorum is 50% and 2/3 majority is required
> >>>> to pass. If this vote passes, another vote will begin for the Core
> >>>> Committee's approval.
> >>>>
> >>>> --
> >>>> 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 view this discussion on the web visit 
> >>>> https://groups.google.com/d/msgid/php-fig/CANeXGWWxq6ys%2Bza0vZXno%3DBZAciXAdm1crbjULq68eT144d2ug%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+u...@googlegroups.com.
> >>>
> >>> To view this discussion on the web visit 
> >>> https://groups.google.com/d/msgid/php-fig/CAL9n4XPLrmE-E%2BE8OwWTAm49DsUqrwK270m2yRBH6Bg%3DaJYWJg%40mail.gmail.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 php-fig+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/php-fig/f0404dd4-0f93-40e9-9e8f-9f8def10d359n%40googlegroups.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/CANeXGWXE%3DN37XJgJSHCHLC2Vb%2BwvMVTpujnsoDw1aRNjOjKx1Q%40mail.gmail.com.

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

[Korvin Szanto]

+1

On Mon, Mar 20, 2023 at 7:57 AM Woody Gilk  wrote:
>
> +1
>
> On Friday, March 10, 2023 at 12:12:28 PM UTC-6 Ken Guest wrote:
>>
>> +1
>>
>> On Fri, 10 Mar 2023 at 17:52, Chris Tankersley  wrote:
>>>
>>> +1
>>>
>>> Chris 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! 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, short closures, enums and attributes, and more.
>>>>
>>>> You can review the full list of changes here:
>>>> https://github.com/php-fig/per-coding-style/compare/1.0.0...master
>>>>
>>>> This vote is limited to the members of the working group:
>>>>
>>>> - Editor: Me
>>>> - Sponsor: Chris Tankersley
>>>> - Alexander Makarov
>>>> - Ken Guest
>>>> - Larry Garfield
>>>> - Luke Diggins
>>>> - Woody Gilk
>>>>
>>>> This is a readiness vote so quorum is 50% and 2/3 majority is required
>>>> to pass. If this vote passes, another vote will begin for the Core
>>>> Committee's approval.
>>>>
>>>> --
>>>> 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 view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/php-fig/CANeXGWWxq6ys%2Bza0vZXno%3DBZAciXAdm1crbjULq68eT144d2ug%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+u...@googlegroups.com.
>>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/php-fig/CAL9n4XPLrmE-E%2BE8OwWTAm49DsUqrwK270m2yRBH6Bg%3DaJYWJg%40mail.gmail.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 php-fig+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/php-fig/f0404dd4-0f93-40e9-9e8f-9f8def10d359n%40googlegroups.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/CANeXGWX7_En2YGk_YtqiW-Gy-Xf%2B38d4SKK12d9phWCAQ0yC0A%40mail.gmail.com.

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

[Korvin Szanto]

+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 the 
>> Core Committee to approve the following PRs to update PSR-7 to add explicit 
>> type declarations.
>>
>> This is a Core Committee vote requiring a 50% quorum and 2/3 majority, 
>> with voting ending on 30 March 2023.
>>
>>
>>- Version 1.1 patch (parameter type declarations): 
>>https://github.com/php-fig/http-message/pull/94
>>- Version 2.0 patch (return type declarations): 
>>https://github.com/php-fig/http-message/pull/95
>>- Specification errata patch: 
>>https://github.com/php-fig/fig-standards/pull/1296
>>
>> -- 
>>
> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/php-fig/d84ebc94-ee4e-4928-aceb-10563b25a163n%40googlegroups.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/25b8693c-e5d2-48df-bde7-f40c0cb2e895n%40googlegroups.com.

[VOTE][WG] Coding style 2.0.0 Readiness Vote

[Korvin Szanto]

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, short closures, enums and attributes, and more.

You can review the full list of changes here:
https://github.com/php-fig/per-coding-style/compare/1.0.0...master

This vote is limited to the members of the working group:

- Editor: Me
- Sponsor: Chris Tankersley
- Alexander Makarov
- Ken Guest
- Larry Garfield
- Luke Diggins
- Woody Gilk

This is a readiness vote so quorum is 50% and 2/3 majority is required
to pass. If this vote passes, another vote will begin for the Core
Committee's approval.

-- 
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/CANeXGWWxq6ys%2Bza0vZXno%3DBZAciXAdm1crbjULq68eT144d2ug%40mail.gmail.com.

Re: [BYLAW] New: funding bylaw

[Korvin Szanto]

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? To me this sounds against the spirit of our
organization and feels like a big mistake.

Thanks,
Korvin

On Sat, Feb 25, 2023, 5:05 AM Tim Düsterhus  wrote:

> Hi
>
> On 2/24/23 00:03, Alessandro Lai wrote:
> > I had the idea of proposing a "funding" bylaw for quite some time,
> > especially because, as a secretary, I had to see the domains or the email
> > account nearly expire multiple times during this year, and finding a
> > permanent solution to that issue is something that I want.
> >
>
> Regarding the domain expiry I can recommend choosing a registrar that
> supports multi-year registrations to avoid the hassle of renewing
> domains on short notice (and possibly forgetting entirely).
>
> All my important personal domains and all $dayjob domains using a TLD
> that supports multi-year registrations are registered for the next five
> years or so *and* are yearly topped up by another year. That way there's
> always a 5-year headroom if something goes wrong (e.g. the registrar
> going out of business).
>
> In fact it appears that the current registrar "Namecheap" does support
> multi-year registrations:
>
> https://www.namecheap.com/support/knowledgebase/article.aspx/770/35/is-it-possible-to-registerrenew-a-domain-name-for-more-than-10-years/
>
> Best regards
> Tim Düsterhus
>
> --
> 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/3ab0d950-32f7-75c7-fd19-5e691676f8be%40bastelstu.be
> .
>

-- 
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/CANeXGWWSP3Yv4p629vhJWvzmXfRHqi8z-O7k%2ByB8nfrP1tyeiw%40mail.gmail.com.

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

[Korvin Szanto]

+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 release 1.0.0 of
>>> auxiliary resource fig/log-test.
>>>
>>> The library is a direct port of existing repo psr/log-util (unreleased)
>>> which has been in the current form for long but has naming issues. You can
>>> view it as-is here: https://github.com/php-fig/log-test/ - Direct
>>> editing was the exception.
>>> Further evolution will be handled as PRs with the appropriate process.
>>>
>>> As per the bylaws I understand this is an Approval vote and it requires
>>> 2/3 approval/yes of voting CC Members, voting quorum 50%.
>>>
>>> Mission and Structure
>>>
>>>- Auxiliary Resources (ARs) are additional tools, code libraries, or
>>>examples that relate to or support a PSR or PER. Examples include common
>>>partial implementations of a PSR or PER, "no-op" implementations, or
>>>testing utilities for PSR or PER implementations. All ARs must directly
>>>relate to one or more PSRs or PERs. An AR is developed by a Maintainer.
>>>- For changes that would qualify as major releases, the release is
>>>subject to a mandatory Approval Vote from the Core Committee.
>>>
>>> Voting Protocol
>>>
>>>- Only Core Committee members may vote, either For (+1), Against
>>>(-1), or Abstain (+0). Quorum is 50%. A 2/3 majority is required for
>>>passage.
>>>
>>> Votes take place over a period of two weeks (or at the reaching of 100%
>>> quorum), so votes will be accepted up to 2022-09-02 11:00:00 UTC.
>>>
>>>
>>> Regards
>>>
>>> Ralf Lang
>>>
>>> --
>>> 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/23ffedad-e087-f10c-da66-d7f95c61e26e%40gmail.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/Mime4j.0.4a156b085a892c8.182b9a96f37%40imap.gmail.com
>> 
>> .
>>
>
>
> --
> 
> Website
> 
>  | Blog
> 
>  |
> Github  | Linkedin
>  | Twitter
> 
>
> --
> 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/CAPY1sU8xxKFQR23AwcLxJ%2BgCzAs%3D59naB23XpDtjhK-mS_uZbg%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/CANeXGWUZcEOXH4HACWkmUtaAo4rszX0beyYCK_b7FuksLyRLug%40mail.gmail.com.

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

[Korvin Szanto]

 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 Gilk
Ben Edmunds
Michelle Sanver
Alessandro Chitolina 

Did not vote: 
Enrico Zimuel
Ken Guest

I have tagged 1.0.0 here: 
https://github.com/php-fig/per-coding-style/releases/tag/1.0.0
Our next steps are to update the website design to include PERs and to add 
support for PHP features that aren't yet covered.

Thanks everyone,
Korvin

On Friday, May 27, 2022 at 2:30:42 PM UTC-7 mweiero...@gmail.com wrote:

> +1
>
> On Wed, May 25, 2022, 11:20 AM 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 terminology, naming, and formatting so any project
>> compatible with PSR-12 today will also be compatible with this proposed 
>> 1.0.0.
>> Please review the full list of changes here:
>> https://github.com/php-fig/per-coding-style/compare/8201676...b5cac84
>>
>> This is an approval vote limited to Core Committee members, so quorum is 
>> 50%
>> and 2/3 majority is required to pass. If this vote passes, `b5cac84` will 
>> be
>> tagged as `1.0.0`.
>>
>> Thanks,
>> Korvin
>>
>> -- 
>>
> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/php-fig/CANeXGWUR2Q3pv4Vuqce0w3WFO7%3DnfJSm0Hncmi3eaFbs%3DcEKyQ%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/php-fig/CANeXGWUR2Q3pv4Vuqce0w3WFO7%3DnfJSm0Hncmi3eaFbs%3DcEKyQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/ca1292b2-ba8b-4e58-9df7-48621e65f4a6n%40googlegroups.com.

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

[Korvin Szanto]

+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 terminology, naming, and formatting so any project
> compatible with PSR-12 today will also be compatible with this proposed 
> 1.0.0.
> Please review the full list of changes here:
> https://github.com/php-fig/per-coding-style/compare/8201676...b5cac84
>
> This is an approval vote limited to Core Committee members, so quorum is 
> 50%
> and 2/3 majority is required to pass. If this vote passes, `b5cac84` will 
> be
> tagged as `1.0.0`.
>
> Thanks,
> Korvin
>

-- 
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/2872293d-e586-4a11-8e19-0932fb44c59an%40googlegroups.com.

[VOTE][CC] Coding Style 1.0.0 Approval Vote

[Korvin Szanto]

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 proposed
1.0.0.
Please review the full list of changes here:
https://github.com/php-fig/per-coding-style/compare/8201676...b5cac84

This is an approval vote limited to Core Committee members, so quorum is 50%
and 2/3 majority is required to pass. If this vote passes, `b5cac84` will be
tagged as `1.0.0`.

Thanks,
Korvin

-- 
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/CANeXGWUR2Q3pv4Vuqce0w3WFO7%3DnfJSm0Hncmi3eaFbs%3DcEKyQ%40mail.gmail.com.

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

[Korvin Szanto]

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 vote tomorrow morning, thanks everyone!

On Tue, May 24, 2022 at 5:11 AM Luke Diggins  wrote:

> +0
>
> On Tuesday, 24 May 2022 at 17:21:37 UTC+10 ezimuel wrote:
>
>> +1
>>
>> Enrico Zimuel
>>
>> Il giorno gio 19 mag 2022 alle ore 18:21 Korvin Szanto <
>> korvin...@gmail.com> ha scritto:
>>
>>> 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 is limited to the members of the working group:
>>>
>>> - Editor: Me
>>> - Sponsor: Chris Tankersley
>>> - Alexander Makarov
>>> - Kathryn Reeve
>>> - Ken Guest
>>> - Larry Garfield
>>> - Luke Diggins
>>> - Woody Gilk
>>>
>>> This is a readiness vote so quorum is 50% and 2/3 majority is required
>>> to pass.
>>> If this vote passes, another vote will begin for the Core Committee's
>>> approval.
>>>
>>> Thanks,
>>> Korvin
>>>
>>> --
>>>
>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/php-fig/CANeXGWVA94Fq3R71J5yP9L8xZjf%2BCgfyxJqd4R8t6KcMONG-4w%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/php-fig/CANeXGWVA94Fq3R71J5yP9L8xZjf%2BCgfyxJqd4R8t6KcMONG-4w%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/c522cf9c-131e-4a8e-8c63-28bed02b786dn%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/c522cf9c-131e-4a8e-8c63-28bed02b786dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CANeXGWV%3Dab40N%3DgZkNjThxz86B7zsef8rzrhhwWAOrV%2B5Zq0tw%40mail.gmail.com.

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

[Korvin Szanto]

+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 full list of changes here: 
> https://github.com/php-fig/per-coding-style/compare/8201676...master 
>
> This vote is limited to the members of the working group:
>
> - Editor: Me
> - Sponsor: Chris Tankersley
> - Alexander Makarov
> - Kathryn Reeve
> - Ken Guest
> - Larry Garfield
> - Luke Diggins
> - Woody Gilk
>
> This is a readiness vote so quorum is 50% and 2/3 majority is required to 
> pass.
> If this vote passes, another vote will begin for the Core Committee's 
> approval.
>
> Thanks,
> Korvin
>

-- 
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/255cdf03-ae7c-4cf3-af48-71dfe25fdc9dn%40googlegroups.com.

[VOTE][WG] Coding Style 1.0.0 Readiness Vote

[Korvin Szanto]

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 is limited to the members of the working group:

- Editor: Me
- Sponsor: Chris Tankersley
- Alexander Makarov
- Kathryn Reeve
- Ken Guest
- Larry Garfield
- Luke Diggins
- Woody Gilk

This is a readiness vote so quorum is 50% and 2/3 majority is required to
pass.
If this vote passes, another vote will begin for the Core Committee's
approval.

Thanks,
Korvin

-- 
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/CANeXGWVA94Fq3R71J5yP9L8xZjf%2BCgfyxJqd4R8t6KcMONG-4w%40mail.gmail.com.

Re: [Vote] Maintainer for log-util library

[Korvin Szanto]

+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 but has no releases yet.
>> :-)
>>
>> https://github.com/php-fig/log-util/
>>
>> This is an Approval Vote, Core Committee only, quorum is 50%, passage is
>> 2/3.  The vote will end on 1 June or when all of the CC has voted,
>> whichever occurs first.
>>
>> --
>>   Larry Garfield
>>   la...@garfieldtech.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/f7e8b221-fb23-4894-8dd8-7745d3ee110e%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/CAJp_myWMma87AYBDYXJAwtGkmH-1sDhVQ0CV90Hy%2BMtnuDaRag%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/CANeXGWVeceLixtcUfG1xRwr7Q39KQXPZUf6UEjB24yKFihpfsw%40mail.gmail.com.

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

[Korvin Szanto]

+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 validation of header fields has completed. We had some
> > feedback basically immediately, and that feedback was incorporated. For
> > reference:
> >
> > - https://github.com/php-fig/fig-standards/pull/1274
> >
> > The tl;dr: PSR-7 implementations SHOULD strictly validate header names
> > and contents according to the most recent HTTP specification ([RFC
> > 7230#3.2][1] at the time of writing). The implementation SHOULD reject
> > invalid values and SHOULD NOT make any attempt to automatically correct
> > the provided values. The errata provides more specific details about
> > this validation, but it's primarily around line wrapping of headers.The
> > changes are suggested to ensure that implementations provide a minimum
> > amount of security for end-users.
> >
> > At this time, I am opening a VOTE for inclusion of this errata in
> > PSR-7. The vote is open to CC members only, and requires a 50% quorum,
> > and a 2/3 approval to pass. The vote will end 2 weeks from the time I
> > send this.
> >
> > --
> > Matthew Weier O'Phinney
> > mweierophin...@gmail.com
> > https://mwop.net/
> > he/him
> >
> > --
> > 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/CAJp_myVoiiH2qd_HwTxT5UgSeGqNVqmsQ4sDur1Km%2BYuqccigQ%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/php-fig/CAJp_myVoiiH2qd_HwTxT5UgSeGqNVqmsQ4sDur1Km%2BYuqccigQ%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
> --
> 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/3706be0a-5ba8-4274-9ce2-a33391c58505%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/CANeXGWWyZK_%3DGVC0oZYxqmMeSLBx4eyDwXRdd4r68uROqBiF-w%40mail.gmail.com.

Re: [PER-Coding-Style] Editor Change

[Korvin Szanto]

Glad to hear from you Alex!

> I'll get back in a month or so
Sounds good, I'll be happy to work with you to get you back in the editor
seat once you're able to be more active.

On Wed, Apr 13, 2022 at 2:15 PM Alex Makarov  wrote:

> Thanks Chris. I was unable to cope with my feelings and work on the PER as
> well as to access Discord (some tech difficulties). I'll get back in a
> month or so.
>
> ср, 13 апр. 2022 г., 23:26 Chris Tankersley :
>
>> As per https://www.php-fig.org/bylaws/elections-and-vacancies/, the
>> original editor Alexander Makarov 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 Alexander returns we will look into reinstating him as the Editor.
>>
>> --
>> Chris Tankersley
>> http://ctankersley.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/CAL9n4XMh-gyhNyTzksnz1vA9n9WFB96utH3OKLte5PftaBxt7A%40mail.gmail.com
>> <https://groups.google.com/d/msgid/php-fig/CAL9n4XMh-gyhNyTzksnz1vA9n9WFB96utH3OKLte5PftaBxt7A%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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%2BFA5VXGD7ESHB0S0b%3DBWBNiHAOOTX3TYacQRB9C12E36ym7TA%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CA%2BFA5VXGD7ESHB0S0b%3DBWBNiHAOOTX3TYacQRB9C12E36ym7TA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CANeXGWVO5PMcPwipNSPuhwnLo%3DSbL5Rpek_HwJJ9p5fBNgkoaw%40mail.gmail.com.

Re: [Nomination][CC] Korvin Szanto

[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.
> His term ends soon so as a representative of Yii framework, I'd like to
> re-nominte him for the core commitee position.
>
> --
> 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/8b414a22-e48c-42dc-98ef-3783def1675an%40googlegroups.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/CANeXGWVp_K2g%3DocyPKJe7QL5j%2B%2B1_31uM_Y7YL4Ea2nzj8wG%3Dw%40mail.gmail.com.

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

[Korvin Szanto]

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

Re: [Entrance Vote]{CC] Localization PSR

[Korvin Szanto]

+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
>>
>> On Wed, Dec 8, 2021, at 4:03 PM, Larry Garfield wrote:
>> > After a great deal of offlist discussion, I hereby call an Entrance
>> > Vote on a Code Localization PSR.
>> >
>> > Specifically, the charter is here:
>> >
>> > https://github.com/php-fig/fig-standards/pull/1259/files
>> >
>> > Little has been firmly defined yet, of course.  That's why we're
>> > building a Working Group. :-)  But we have narrowed the scope to
>> > something we believe is manageable.
>> >
>> > We are open to, and still soliciting, additional WG members who have
>> > particular experience with major projects that have existing code
>> > localization systems.  Additional personnel MAY be added in the future,
>> > therefore.
>> >
>> > This is a Core Committee vote only.  Non-CC members, please sit tight.
>> :-)
>> >
>> > --
>> >   Larry Garfield
>> >   la...@garfieldtech.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/6b75ff3d-f909-49d3-a277-00e49d1fa8ae%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/99912321-fdfb-4a06-80ae-017426ba51e5%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/CAGOJM6LLO9uPr%3D6q-ZBSE6TvQ9Joc8khNbRJsJpw1S9%2Bw-i_ig%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/658BD6BD-C13D-4F68-9882-A7240FF5CF66%40sanver.se
> 
> .
>

-- 
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/CANeXGWWtQFnqjTuWMN6uPCbmx%2B8A_T7%2BVp7PZm3khbAsMkcuqA%40mail.gmail.com.

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

[Korvin Szanto]

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 bases when dealing with single line vs multi-line
class declaration lines.

On Mon, Nov 29, 2021, 10:16 AM Shawn Corrigan 
wrote:

> Hi everyone,
>
> I tried to find an answer to this in the existing conversations here but I
> couldn't seem to find anything, I apologize if it's already been discussed.
>
> I'm reading PSR-12 and trying to understand what these two lines mean.
> They seem to be disconnected from the subsection they're in, so it's hard
> to tell what it's referring to exactly.
>
> Lines 255 and 256
> 
>  are
> under subsection 4.1 -  *Extends and Implements. *They are also under
> section 4 -
>
> *Classes, Properties, and Methods.*They say...
>
> > Opening braces MUST be on their own line and MUST NOT be preceded or
> followed by a blank line
> > Closing braces MUST be on their own line and MUST NOT be preceded by a
> blank line.
>
> There are no opening or closing braces directly associated with the
> "extends" or "implements" keywords, just for the class.
>
> Above that, in the same section, it says “The opening brace *for the
> class* MUST […]”. That line explicitly specifies the brace is for the
> class, but the two lines in question don't specify what the braces are for.
>
> Are those lines referring to the class, just as the line above it is? Or
> is it referring to the section title; *Classes, Properties, and Methods*?
> (leaving out properties).
>
> --
> 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/ef016517-32bd-4f83-9ad6-443d8e5c2244n%40googlegroups.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/CANeXGWX5LfH2%2Bno1AGuzw4%3D3RifErYwtYudxb3NgXFHN0RtwsA%40mail.gmail.com.

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

[Korvin Szanto]

+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 09:12 Alessandro Lai <
>> alessand...@gmail.com> ha scritto:
>>
>>> Hello everyone,
>>> I hereby call a CC vote for the approval of the evolution of PSR-16 - 
>>> Simple Cache.
>>>
>>> The change in the spec is reviewable in this PR: 
>>> https://github.com/php-fig/fig-standards/pull/1252
>>> Inside the PR description you'll find the links to the two PR containing 
>>> the code changes:
>>>  - v2 adds parameters types, and makes CacheException extend \Throwable
>>>  - v3 (which obviously builds upon the previous) adds return types
>>>
>>> Both require PHP 8 at a minimum, since mixed and union types were 
>>> needed, and also to avoid issues when extending \Throwable (as it happened 
>>> with the evolution of PSR-11, see 
>>> https://github.com/php-fig/container/issues/33).
>>>
>>> As per our bylaws:
>>>  - only Core Committee members may vote
>>>  - either For (+1), Against (-1), or Abstain (+0)
>>>  - quorum is 50%
>>>  - a 2/3 majority is required for passage.
>>>
>>> Votes take place over a period of two weeks (or at the reaching of 100% 
>>> quorum), so votes will be accepted up to 2021-10-28 10:00:00 UTC.
>>>
>>> --
>>>
>> 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 view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/php-fig/78c7b658-9db7-46a0-b715-b8b96e236dedn%40googlegroups.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+u...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/php-fig/d6de90a1-9693-4fc1-995a-cb961da710edn%40googlegroups.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/584a7918-bfd1-4550-abe6-c3136507c379n%40googlegroups.com.

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

[Korvin Szanto]

+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 created a proposal for a change to the bylaws to
>> introduce PHP Evolving Recommendations. As part of that proposal, some
>> restructuring of the bylaws has been performed to be streamline the PSR,
>> PER and AR processes.
>>
>> The discussion thread can be found here:
>> https://groups.google.com/g/php-fig/c/gLNKg9jpRCU and some additional
>> discussions on Discord.
>>
>> The proposed change can be seen in the pull request:
>> https://github.com/php-fig/fig-standards/pull/1235 *(commit on day of
>> voting fdadde82c28d517b515b6aa87d42cb71daded4b4)*
>>
>>
>> Per the voting protocol: https://www.php-fig.org/bylaws/voting-protocol/
>>
>>- Voting options are For (+1), Against (-1), or Abstain (+0)
>>- Quorum is 50%, a 2/3 majority is required for passage.
>>- Voting ends in two weeks, 2021-09-21 17:00:00 UTC
>>
>>
>> --
>> 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/4d18ec79-8417-4938-aa7b-6fbd32c4b22bn%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Chris Tankersley
> http://ctankersley.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/CAL9n4XO5oU%3D578R2eLhEaLaA9qf_SN7j5_6%3DeMyg3hgiS4UefA%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/CANeXGWXV1wOsk9Fw9fm9TrvH6AVHQOH5CZL3tTrYkRUwphnRGw%40mail.gmail.com.

Re: [VOTE][CC] AzuraCast Membership vote

[Korvin Szanto]

+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:
>> https://groups.google.com/g/php-fig/c/0fVYv0ha4Lo/m/SN7_aviaBAAJ
>>  - proposed project representative: Felix Bachmann, which is the second
>> lead developer.
>>  - disclosure: Current Secretary Buster Neese is a project lead for
>> AzureCast. He will continue to be secretary and thus will not represent
>> AzuraCast.
>>  - request sponsored by Larry Garfield 2 weeks ago:
>> https://groups.google.com/g/php-fig/c/0fVYv0ha4Lo/m/SN7_aviaBAAJ
>>
>> Voting ends by 2021-08-14 17:00 UTC
>>
>> Voting options:  For (+1), Against (-1), or Abstain (+0)
>> Quorum: 50%
>> Majority: 50%
>> https://www.php-fig.org/bylaws/voting-protocol/#membership-vote
>>
>> ONLY CORE COMMITTEE MEMBERS CAN VOTE HERE
>
> --
> 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/a3b99de4-ffae-4512-97c8-6a94c9cf59b2n%40googlegroups.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/CANeXGWUV33gDn4A1BnvntOsz5n8SmBiRTVQMR93zDsZy4ghPFQ%40mail.gmail.com.

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

[Korvin Szanto]

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 the
section you quoted but there's nothing stopping you from using PSR-12 and
allowing them in your own projects.

[0]
https://groups.google.com/g/php-fig/c/q5B_f0WQsOA/m/vC5ZpV5CBwAJ?utm_medium=email_source=footer

Best wishes,
Korvin

On Thu, Jul 15, 2021, 2:20 PM Liam Hennessy  wrote:

> Greetings!
>
> According to Section 5 of PSR-12  
> (Control
> Structures):
>
> *The body of each structure MUST be enclosed by braces. This standardizes
> how the structures look and reduces the likelihood of introducing errors as
> new lines get added to the body.*
>
> Does this mean that *endif, endwhile, endfor, endforeach, *and *endswitch*
> are not permitted by PSR-12?
>
> It would be helpful if PSR-12 was more explicit about this, even if the
> consensus is that you MAY use them, as it is easy to overlook this point
> completely or misinterpret this point as a strict exclusion.
>
> As a new member, please accept my thanks for your time and effort.
>
> Regards,
>
> Liam
>
> --
> 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/f0d9e0c7-9957-45fe-9721-5d3e2f71b613n%40googlegroups.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/CANeXGWU7bSrjxQpo3QtKe%3DyT%3DVgUm6wijNAcTK-MH8H%3DwZ6UQw%40mail.gmail.com.

Re: [VOTE] Core Committee Election

[Korvin Szanto]

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*
> *Slim Framework Project Representative*
> On Thursday, June 10, 2021 at 9:42:31 AM UTC-6 alessand...@gmail.com
> wrote:
>
>> Hello everyone,
>> as specified in the previous thread (
>> https://groups.google.com/g/php-fig/c/9Xeon2rP4SE), yesterday the
>> nominations ended, and since today it's possible to vote for the renewal of
>> the terms that are up for this elections.
>>
>> We have *5 spots on the Core Committee* up for reelection, four with a
>> full two year term and a shorter one, that will end in August 2021, due to
>> Beau Simensen stepping down; we also have one full-term spot for secretary.
>>
>> Since we have only one unopposed nomination for the secretary election,
>> we will need to vote for the Core Committee positions only, for which we
>> have five nominations (listed in chronological order of nomination):
>>
>>  - Larry Garfield
>>  - Matthew Weier O'Phinney
>> 
>>  - Michelle Sanver
>>  - Alessandro Chitolina
>>  - Woody Gilk
>> 
>>
>> Full information about the Core Committee vote and role is visible in the
>> bylaws here:
>> https://www.php-fig.org/bylaws/mission-and-structure/#the-core-committee
>>
>> *Who can vote?*
>> As specified in the bylaws, any Project Representative or any participant
>> in the PHP-FIG ML can vote on the CC elections. A ML participant is defined
>> in the bylaws as follows:
>> "Any individual that has posted a non-trivial message in the official FIG
>> venue (mailing list, forum, etc.) at least five (5) times within the past
>> calendar year as of the start of nominations [...] is eligible to vote on
>> Core Committee candidates."
>>
>>  *When can you vote?*
>> Voting will be open in this thread until June 24th 23:59 UTC.
>>
>> *How to vote*
>> The voting system used is STV[1][2], so basically, there is no tactical
>> voting possible (like with FPTP); vote for who you want, even if they are a
>> less popular candidates as your vote will move down to a different
>> candidate if you back an unpopular candidate who doesn't have enough votes;
>> if a candidate is elected, their surplus votes are also re-allocated so you
>> are not punished for backing popular candidates either. There is no quorum,
>> you are of course entitled to not vote and it will not count as a missed
>> vote on the voting sheet. Rank the candidates in order of preference for
>> example:
>>
>> 1. Luke
>> 2. Leia
>> 3. Anakin
>> 4. Rey
>> 5. Padmé
>> 6. Finn
>>
>> At the end of the voting phase I will be announcing the results, and all
>> the newly elected (both CC members and secretary), as announced before.
>> Vote ordering will be also used to assign the terms, so the last of the
>> elected will take the shorter one.
>>
>> Thanks!
>>
>> Alessandro Lai
>> PHP-FIG Secretary
>>
>> [1]: STV User-friendly Explanation
>> https://www.youtube.com/watch?v=l8XOZJkozfI
>> [2]: https://en.wikipedia.org/wiki/Single_transferable_vote
>>
> --
> 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/de0942f1-8fb4-43b0-8c77-ce4b0a5411bcn%40googlegroups.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/CANeXGWVSoz0TX6%2B2ZUdfJ0zDZuV9kYT-tR__f-5MVhad08HW_Q%40mail.gmail.com.

Re: [VOTE][Projects] Bylaw CS update

[Korvin Szanto]

+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 alessand...@gmail.com
>> wrote:
>>
>>>
>>> Hello everyone,
>>> this my seem a small formality, but we need a vote for a small bylaw
>>> amendment: https://github.com/php-fig/fig-standards/pull/1203
>>>
>>> Basically, we need to update the guidelines to follow PSR-12, since it
>>> deprecated PSR-2.
>>>
>>> As per our voting protocol:
>>> https://www.php-fig.org/bylaws/voting-protocol/
>>>
>>> This is a vote for the Project Representative only.
>>> If a PR is serving as a Core Committee too, he's not elegible to vote
>>> here.
>>> There's no quorum.
>>> A 2/3 majority is required for passage.
>>> Voting ends in two weeks, at midnight UTC between 14th & 15th of April.
>>>
>>> For CC, there's already another thread:
>>> https://groups.google.com/g/php-fig/c/GK-fjLdQFBk
>>>
>> --
> 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/11989fc8-47d0-4171-9cf5-67e9a80e17d6n%40googlegroups.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/CANeXGWXkcws1uw7Jb6YdhaSH6xqdi6%3DYeWgoseDAmghhyhyg5A%40mail.gmail.com.

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

[Korvin Szanto]

+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
> Working Group:
> - Jérôme Gamez (kreait/clock)
> - Andreas Möller (ergebnis/clock)
> - Luís Cobucci (lcobucci/clock)
> - Pol Dellaiera
> - Ben Edmunds
> - Andreas Heigl (ergebnis/clock)
>
>
> Please do not reply to this topic if you are not a CC member. 
> --
>

-- 
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/c4ad8317-b080-46c7-a182-b25df75a0d7cn%40googlegroups.com.

Re: [Vote] PSR-13 Link Errata

[Korvin Szanto]

+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 an Errata vote on the following Link fixes,
>> including the linked (no pun intended) PRs.
>> >
>> > https://github.com/php-fig/fig-standards/pull/1222
>> >
>> > This is a CC Vote, requiring 2/3 to pass. Voting will remain open until
>> 10 March, unless all 11 CC members vote before then. (Hint hint, folks. :-)
>> )
>> >
>>
>>
>> --
>> Matteo Beccati
>>
>> Development & Consulting - http://www.beccati.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/997ddfd5-76ab-4683-966e-0ba44a1af12fn%40googlegroups.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/CANeXGWUxPFadQWSwE-ing1K%2BYCOZ4bBL1-%2B60eVEPE0cLmkV8A%40mail.gmail.com.

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

[Korvin Szanto]

+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 (https://www.php-fig.org/bylaws/psr-evolution/).
>> The discussion centers around three related proposals:
>>
>> - https://github.com/php-fig/fig-standards/pull/1215 (the errata for the
>> specification)
>> - https://github.com/php-fig/container/pull/20 (the first step of the
>> evolution, adding argument typehints, and modifying defined exception
>> interfaces to extend Throwable)
>> - https://github.com/php-fig/container/pull/28 (the second step of the
>> evolution, adding return typehints where reasonable)
>>
>> Since opening the discussion period, the main question was whether the
>> second step should have the specification target PHP 8 in order to pick up
>> the "mixed" type. Consensus is that we should target PHP 7 releases at this
>> time, as this will allow libraries to adopt the changes faster. (As an
>> example, we're only just now getting around to having
>> laminas-servicemanager typehint explicitly against PSR-11 and not
>> container-interop; we'll be able to jump to the latest versions of the spec
>> immediately as a result.)
>>
>> As the discussion period has passed the two-week minimum threshold, I now
>> hereby open the vote.
>>
>> +1 to merge the patches and create the new releases
>> -1 to leave things as-is
>> +0 to abstain
>>
>> Thanks in advance, everyone!
>>
>> --
>> Matthew Weier O'Phinney
>> mweierophin...@gmail.com
>> https://mwop.net/
>> he/him
>>
>> --
>> 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/CAJp_myVHMjmrQmk5LP_5rvdLYzbTPquQJSX%2BDE%2B2KS4UzbsJ2A%40mail.gmail.com
>> 
>> .
>>
>
>
> --
> Chris Tankersley
> http://ctankersley.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/CAL9n4XM0ZgycOwkD_EDYgFk02v2a_kpNgH2TVH2bUmWVTAzaFA%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/CANeXGWV8CK0MORU0hm8ySCtpD%2Bxg-eOq0XOPFQiwNP3%2BOPDsyw%40mail.gmail.com.

Re: [Vote] [PSR-13] updates

[Korvin Szanto]

+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 voting ending on 30 January.
>
> CC members, please cast your votes.
>
> Step 1: https://github.com/php-fig/link/pull/6
> Step 2: https://github.com/php-fig/link/pull/7
> Spec: https://github.com/php-fig/fig-standards/pull/1199
>
> --
>   Larry Garfield
>   la...@garfieldtech.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/fb854aac-a513-4d19-b2f0-1a4740e7d1e8%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/CANeXGWWhBbgm6CQHxXYPfVvn%3DvvyhtyhvYgVzCWDJPaKsGJhqA%40mail.gmail.com.

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

[Korvin Szanto]

+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 voting ending on 30 January.
>
> CC members, please cast your votes.
>
> Spec: https://github.com/php-fig/fig-standards/pull/1220
> Step 1: https://github.com/php-fig/cache/pull/23
> Step 2: https://github.com/php-fig/cache/pull/24
>
> --
>   Larry Garfield
>   la...@garfieldtech.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/09b03692-a9d4-4f14-a931-7723aaf94d19%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/CANeXGWX3c46BKN%2BdpAzASSrGrhHff2sQN45E5616r1mTtJDaGw%40mail.gmail.com.

Re: [VOTE][CC] Errata bylaw update

[Korvin Szanto]

+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 bylaw change.
>>
>> As always, quorum is 50%, majority 2/3.
>> Vote will end July 23rd, 23:59:59 UTC.
>>
>> THIS THREAD IS FOR CORE COMMITTEE VOTES ONLY
>>
> --
> 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/88160afe-79a9-4ed8-b090-03eee4bdb35cn%40googlegroups.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/CANeXGWXWYvM-mnmtyQ%2BVmJ8o9qtgZu6gYEhP%3DdngSTQNEQ%2By_w%40mail.gmail.com.

Re: [VOTE][CC] TYPO3 Membership vote

[Korvin Szanto]

+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:
> > https://groups.google.com/d/topic/php-fig/qDOyOuLuoKc/discussion
> >  - proposed project representative: Benni Mack, which is project lead
> >  - request sponsored by Matteo Beccati 2 weeks ago:
> > https://groups.google.com/d/msg/php-fig/qDOyOuLuoKc/HtwMXZ_jBgAJ
> >
> >
> > Quorum: 50%
> > Majority: 50%
> > https://www.php-fig.org/bylaws/voting-protocol/#membership-vote
> >
> > ONLY CORE COMMITTEE MEMBERS CAN VOTE HERE
> >
> >  --
> >  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/cf05addb-2600-483c-ae7c-8766cf6f27c2o%40googlegroups.com
> <
> https://groups.google.com/d/msgid/php-fig/cf05addb-2600-483c-ae7c-8766cf6f27c2o%40googlegroups.com?utm_medium=email_source=footer
> >.
>
> --
> 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/2294a507-e8f9-4cf2-b655-b76c4f57a78f%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/CANeXGWVEk_fgdUAq%3Dj9kp8GKKeOKRB1mRdrd7d6noeUi6tYF_Q%40mail.gmail.com.

Re: PSR Evolution, PSR-13, and nuance

[Korvin Szanto]

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...
>>
>> Background: Back in December I filed a pair of PRs to update PSR-13 to
>> use type hints, per the recently-passed evolution bylaw.  I figured it
>> would make a good test case to flush out edge cases, and I was right.
>>
>> PRs:
>> https://github.com/php-fig/link/pull/6
>> https://github.com/php-fig/link/pull/7
>>
>> From the discussion here, there, and elsewhere (musical references FTW),
>> I've identified two primary concerns that should be *globally* resolved for
>> any spec updating in this fashion, not just PSR-13, although PSR-13 is the
>> case in point.
>>
>> 1) string parameters are a potential BC break in strict mode; does that
>> require a v2 rather than v1.1?
>>
>> This is an issue that Symfony ran into when upgrading some of its own
>> libraries, and prompted the "Stringable" RFC from Nicolas for PHP 8. (cf
>> https://wiki.php.net/rfc/stringable, currently in voting as I write
>> this, and seems likely to pass but not overwhelmingly.)
>>
>> The specific issue is that if a method takes an untyped string parameter,
>> right now that implicitly means `string` or "object with __toString"... at
>> least most of the time.
>>
>> If it is typed `string`, then in weak mode it means the same, although
>> the object will get cast to a real string at call time rather than sometime
>> later; in strict mode, a Stringable object is no longer allowed.  That
>> means a nominal API change, which should necessitate a new major of the
>> interface package (v2, not v1.1).  (According to Nicolas on the PHP
>> Internals News podcast (https://phpinternals.news/39), Symfony missed
>> this implication originally and inadvertently broke Drupal, which was
>> passing a stringable object to a method to which they'd added a string type
>> hint.  That was the impetus for the Stringable RFC.)
>>
>> Example (try flipping the declare statement on and off):
>>
>> https://3v4l.org/0dpsJ
>>
>> It's been pointed out that since by design an implementation can continue
>> to omit the parameter type, it's a BC break by the implementer, not the
>> spec, and thus the spec has only a non-breaking change and can be a 1.1.  I
>> disagree; for one, I don't expect most implementers to be thinking of that
>> sort of nuance.  Honestly I likely wouldn't until it tripped someone up.
>> For another, we *want* implementers to be, in the long run, fully
>> implementing the spec and not dropping random parameters, even if the
>> language allows it.  That would result in some implementations accepting
>> stringable objects and others not, which is directly contrary to the goal
>> of interoperability.
>>
>
> I disagree with this analysis.
>
> If the specification indicates that an argument should be a string, then
> passing anything other than a string for that argument is an error on the
> part of the user. If the particular implementation allows it, then that
> implementation is coded incorrectly.
>
> While I understand and appreciate the issue that Symfony has experienced,
> I'd argue that their change to use strict_types fixed an issue with their
> code, and Drupal then discovered they were incorrectly consuming the
> Symfony API. If Symfony type-hinted as "string", but allowed non-strings
> previously, this change is a bugfix. Yes, Drupal is left needing to change
> their code after a minor release, but they should have been using it
> correctly previously, and either casting to string ((string) $value) or
> calling the object's `__toString()` method.
>
> Yes, PHP has allowed munging types when undefined or in weak mode.
> Generally speaking, if the type is important, the implementation should:
>
> - when untyped, check the type explicitly
> - when weakly typed, assume that the consumer is casting
> - when strictly typed, require the consumer to cast
>
> It's that second point where I can see the potential argument around
> "well, PHP will cast objects that define __toString()"; that is in fact
> exactly what happens when an object defining __toString is encountered when
> passed to a parameter defining a string typehint when strict_types is not
> enabled. That said, _doing so is counter to the type hint_, and even your
> IDE will tell you there's an error (e.g., intelephense raises "Expected
> type 'string' Found '{Object type}'"); as a consumer, you shouldn't rely on
> PHP's value munging _as you cannot know that strict_types is NOT enabled_,
> unless your tests pass without munging. And even then, that's an indication
> that you're passing a value that might be considered invalid in the future,
> and you shouldn't rely on it.
>
> The problem with that second option (weak types, string typehint) is more
> difficult from the _implementation_ aspect. Because PHP 

Re: [PSR-12] Anonymous classes

[Korvin Szanto]

I'd argue what is confusing here is the lack of parenthesis on the 
anonymous class in the example and not that section 4 doesn't cover 
anonymous classes explicitly. If we do anything, it would be that we add 
adjust the code sample and describe the change in errata.

On Friday, January 24, 2020 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 intention. 
> > 
> > IMHO, looking at the code example, it seems that we're not requiring the 
> parentheses, but it would be inconsistent, so I would prefer an errata that 
> requires them. 
> > 
> > This PR contains my proposed fix, minus the errata text that should be 
> added in the meta: https://github.com/php-fig/fig-standards/pull/1206 
> > 
> > Il giorno venerdì 24 gennaio 2020 11:12:59 UTC+1, Alex Makarov ha 
> scritto: 
> >> 
> >> How would you word it instead? 
> >> 
> >> On Fri, Jan 24, 2020 at 11:46 AM Alessandro Lai 
> >> > wrote: 
> >> > 
> >> > While following PSR-12 implementation on PHP-CS-Fixer, a comment 
> indicated a possible inconsistency in the PSR-12 text: 
> https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4502#issuecomment-578006523
>  
> >> > 
> >> > The issue is in the fact that chapter 4 says: 
> >> > 
> >> > The term “class” refers to all classes, interfaces, and traits. 
> >> > [...] 
> >> > When instantiating a new class, parentheses MUST always be present 
> even when there are no arguments passed to the constructor. 
> >> > 
> >> > But chapter 8 for anonymous classes says: 
> >> > 
> >> > Anonymous Classes MUST follow the same guidelines and principles as 
> closures in the above section. 
> >> > 
> >> >  >> > 
> >> > $instance = new class {}; 
> >> > 
> >> > 
> >> > Should we make this clearer? 
> >> > 
> >> > -- 
> >> > 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...@googlegroups.com . 
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/php-fig/4f9352d1-f65b-47bb-9c08-e06ecc6ece1f%40googlegroups.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...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/php-fig/53ab5bcd-6f18-4b71-aee3-1f1838a98d84%40googlegroups.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/e7f2b331-0d37-467e-a240-c726f08d325a%40googlegroups.com.

Re: [Nomination][CC] Korvin Szanto

[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-nominate Korvin Szanto for the CC position. Korvin has been a major part 
> of the Core Committee for years, and has helped on various PSRs including 
> PSR-11 as the sponsor and PSR-12 as the editor. I think he's done a great 
> job in his tenure, and would like to see him continue.
>
> --
> Chris Tankersley
> Sculpin Representative, CC member
>
> [1] https://groups.google.com/forum/#!topic/php-fig/te-IAmuZte0
>
>

-- 
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/b3035a49-7053-46db-a7e9-e07e95fdf94a%40googlegroups.com.

Re: A question about PSR-12

[Korvin Szanto]

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 pseudo
> code of documenting.
> CRB
>
> On Sun, Sep 22, 2019, 10:47 Memo Chou  wrote:
>
>> Hi, everyone!
>>
>> This is a part of PSR-12.
>>
>> Can anybody tell me why use pipeline here? Is it should be an "or"(||)?
>>
>> OtherThrowableType | AnotherThrowableType
>>
>> Thanks!
>>
>> [image: 螢幕快照 2019-09-22 下午11.45.00.png]
>>
>> --
>> 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/3ad8cf97-5a9a-4529-b4ee-06be47177e18%40googlegroups.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/CANsgjnu37K3_%3DuBSCDJJ%3D1UFHRr87kvGAQ%3Dg3g0axCiTyUQCKA%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/CANeXGWVgcj_ymuiLX92_g%3D%2Bb1qGbdwEPiFd71pu7ZJuTq1D9MA%40mail.gmail.com.

Re: Revert inappropriate PSR-12 post-vote merge

[Korvin Szanto]

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

That said I think our bylaws are a little too open when it comes to
managing these sorts of changes. Once a PSR is accepted, secretaries are
charged with managing "typos, changes or errata" with the optional help of
the editor:
> If the Acceptance Vote passes, ... the Working Group is automatically
dissolved, however the Editor’s input (or a nominated individual
communicated to the secretaries) may be called upon in the future should
typos, changes or Errata on the specification be raised.

The "typos" and "changes" portion of that is classified more specifically
in the Amendments bylaw as "formatting and typo" fixes:

> If formatting is broken for any reason then changing formatting must not
be considered a change to the document. These can be merged or pushed
without hesitation by a secretary, as long as they don’t change anything of
any meaning or syntax.

So secretaries are expected to ensure modifications are "not ... considered
a change to the document" and "don’t change anything of any meaning or
syntax" with the occasional help of the Editor as needed. In practice, as
demonstrated here these things are subjective and can be interpreted
differently by different individuals. In this case, both the Editor of the
PSR and current secretaries looked at these changes and agreed they could
be merged without errata votes.

I think we should consider changing the typos and formatting change process
so that it's less subjective and more likely to result in stable
specifications. Perhaps we could have a subcommittee in the CC that has to
give blessing to merge changes to any approved specification.

Thanks again for keeping an eye on these things Larry,
Korvin

On Wed, Sep 18, 2019 at 9:42 AM Larry Garfield 
wrote:

> Hi all.
>
> I noticed this morning that this PRs had been merged against PSR-12:
>
> https://github.com/php-fig/fig-standards/pull/1185
> https://github.com/php-fig/fig-standards/pull/1183
>
> I do not believe the changes in them are appropriate for an
> already-voted-on PSR.  Changes post-vote are permitted in only very narrow
> circumstances:
>
> https://www.php-fig.org/bylaws/psr-amendments/#3-acceptable-amendments
>
> The following changes in that PR go well beyond Annotations or Formatting
> & Typos:
>
> https://github.com/php-fig/fig-standards/pull/1185/files
>
> Changing "would not" (a non-binding term) to a "MUST NOT" (an RFC defined
> term with very specific meaning) is a substantive change.  The original
> "Would not" language is, in context, entirely adequate.
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9L99
>
> This block changes the meaning of the spec, and thus is not allowed.
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9L369
>
> Because capitalized MUST has a specific "legal" meaning, this is also
> technically a substantive change.
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9L439
>
> Substantive change, and isn't even explained.
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9L464
>
> While this is a net-zero impact change because the language already
> requires it, I would still say it's more than is allowed without an errata.
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9L689
>
> These buts don't really add anything.  (Insert inappropriate joke here.)
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9L885
>
> This change is even noted in the comments as being a substantive change.
> This is not acceptable post-vote.
>
>
> https://github.com/php-fig/fig-standards/pull/1183/files#diff-53ccbb40a68e167a66735993f78e0bb9R918
>
> I... don't even know what this is about at all.
>
> As a result, what is currently published as PSR-12 is not what was
> approved by the Core Committee.  That situation must be corrected.
>
> I ask the Secretaries to revert both PRs promptly. Additionally, I do not
> believe PRs to approved specs should be merged by anyone other than the
> Secretaries, as they are the ones nominally responsible for typo-fix level
> changes.
>
> There are some non-substantive changes in the larger one that are fine
> (adding newlines and fixing some commas or capitalization), which can be
> resubmitted.  Any substantive changes must go through an Errata vote, and
> if approved added to the meta document.
>
> (Note: I am not making any statement here on the substance of those
> changes, and whether they're good or bad for the spec.  Just that they are
> 

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

[Korvin Szanto]

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 this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CANeXGWV4JUEY_f%3Dw5FxGsPqDBB%2BbsokW1KbhAbN9Bg1D5220kA%40mail.gmail.com.

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

[Korvin Szanto]

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 by detecting the spec version
and loading different versions of your implementation with your class
loader.

I really like Stefano's thinking. The namespace bit isn't my favorite but I
understand why it could be important.

- The Revision number matches the Semver package version, but it's doesn't
> map exactly to the same concept. The most relevant part is obviously the
> major number because minor and patch should not break compatibility, thus
> releasing a new Revision will not be required.
>

What would distinguish a "minor" change from a "patch" change? Are you
thinking a minor change would be errata and a patch would be typo fixes?

Thanks,
Korvin

-- 
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/CANeXGWXti2DXW9VByMDZ2wtSNLJqAzP6tN9jsFvki17z6b%2BV7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [VOTE] Core Committee Election

[Korvin Szanto]

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
> 6. Adam Englander
> 7. Beau Simensen
>
> Ciau!
>
> --
> 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/CAFojS1uAPEBOkQ2wVO_5%3DjH9aMEh-BOsVcHXkWHX1cs%3DEzK03g%40mail.gmail.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+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/CANeXGWUge2UVb%2BgteUJeFEkoHCse_eYhvazcYFXv6osgmGnjGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+1

On Wed, Mar 13, 2019, 9:10 AM Chris Tankersley 
wrote:

> +1
>
> -Chris Tankersley
>
> On Sun, Mar 10, 2019 at 2:31 PM Cees-Jan Kiewiet 
> wrote:
>
>> The REVIEW period for the proposed PSR-14, Event Dispatcher, hit its
>> minimum required length on 27 February 2019. We continued the period since
>> then to make sure nothing came up and some minor concerns where raised as
>> PR, which have all since been merged.
>>
>> At this time, I am opening an ACCEPTANCE VOTE. Per the by-laws, the
>> acceptance vote is limited to Core Committee members. The vote will close
>> either at 23:59:59 UTC on 24 March 2019, or when all CC members have cast
>> their vote, whichever comes first.
>>
>> The relevant materials are as follows:
>>
>> - Specification:
>> https://github.com/php-fig/fig-standards/blob/master/proposed/event-dispatcher.md
>>
>> - Metadocument:
>> https://github.com/php-fig/fig-standards/blob/master/proposed/event-dispatcher-meta.md
>>
>>
>> PLEASE DO NOT VOTE UNLESS YOU ARE A CC MEMBER.
>> Current CC Members are as follows:
>>
>> 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
>> Chuck Burgess
>>
>>
>> Cees-Jan Kiewiet, your friendly neighbourhood PSR-14 Sponsor
>>
>> --
>> 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/b46fe9d1-0290-4b31-9629-03ffe109b709%40googlegroups.com
>> <https://groups.google.com/d/msgid/php-fig/b46fe9d1-0290-4b31-9629-03ffe109b709%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Chris Tankersley
> http://ctankersley.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 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/CAL9n4XP0w8coNa-L%2BKF%2B8q%3DqDuMZ9eOzRv01X5uGdEwuyfhXNA%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAL9n4XP0w8coNa-L%2BKF%2B8q%3DqDuMZ9eOzRv01X5uGdEwuyfhXNA%40mail.gmail.com?utm_medium=email_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/CANeXGWX6%3D7ViUesWmDZU7B1GpiiESTrALZUggrnGQHgYQv4MvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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 Makarov: +1
Michael Cullum: +1
Robert Deutz: +1

Thanks Everyone!

On Sun, Feb 3, 2019 at 7:30 AM 'Robert Deutz' via PHP Framework
Interoperability Group  wrote:

> +1
>
>
> Am Montag, 28. Januar 2019 18:25:37 UTC+1 schrieb Korvin Szanto:
>>
>> 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 listed as a member of
>> the working group. A +1 vote means that you support moving forward into
>> review, and a -1 means that you think the working group should discuss this
>> more.
>>
>> As this is a readiness vote, quorum will be 50% and a majority of at
>> least 2/3 is required for passage. Though I hope to see a unanimous
>> 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 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/039723fd-82b2-44c7-a3ae-929e286b6fc1%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/039723fd-82b2-44c7-a3ae-929e286b6fc1%40googlegroups.com?utm_medium=email_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/CANeXGWUWoUTAEUim5G6HnsG_pFecS2vDHUeufPEVO%2BQEGOnc3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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 listed as a member of the 
> working group. A +1 vote means that you support moving forward into review, 
> and a -1 means that you think the working group should discuss this more.
>
> As this is a readiness vote, quorum will be 50% and a majority of at least 
> 2/3 is required for passage. Though I hope to see a unanimous 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 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/a9d8c0f7-0c31-4fb2-81a5-d2afc91b01ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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 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/d4f04edc-1e15-4bb5-a1dd-e7b4d3fc1c51%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+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/CANeXGWWehqpzXViA5CU7mXjUM1sc2e0pfi_%3D3N0CE3uWSGARxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+1

On Tuesday, May 15, 2018 at 9:06:02 AM UTC-7, Matthew Weier O'Phinney wrote:
>
> Woody has delegated to me to open a vote to enter the REVIEW period for 
> PSR-17. This vote is open only to PSR-17 Working Group members; at this 
> time, that means: 
>
> - Woody Gilk (Editor) 
> - 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 such, the vote will run 
> until 23:59:59 on 29 May 2018, or until all members have responded. Once 
> the vote is closed, I 
> will post the results, and indicate next steps for the proposal. 
>
> PLEASE DO NOT RESPOND TO THIS POST UNLESS YOU ARE ONE OF THE MEMBERS 
> LISTED ABOVE. 
>
> -- 
> Matthew Weier O'Phinney 
> mweiero...@gmail.com  
> https://mwop.net/ 
>

-- 
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/dce619fe-0d81-4510-9e4b-139b8b6e27ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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.  Thanks.
>
> --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 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/1683831.LIx0pLXE5i%40vulcan.
> 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/CANeXGWXuVQo_bPOkwd9ZDX5q6GyeuOqnnNy8H%3DGuzEjVEcDTbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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:
>>
>>> Take 3, or 4, or something...
>>>
>>> This is a Core Committee vote to merge the following Errata PR for PSR-6:
>>>
>>> https://github.com/php-fig/fig-standards/pull/915
>>>
>>> I believe all discussion that needs to be had has been had.
>>>
>>> Vote is open now for 2 weeks, and will close on 3/26.
>>>
>>> Core Committee, an up or down vote please.
>>>
>>> --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 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/2209261.54JSFkv1d7%40vulcan.
>>> 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/CAJp_myU70F4s6uTOMGf-%3DkukjHvgRKG1gnhSeAgN_fHvwQKfzQ%40mail.gmail.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+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/CAFojS1sW3Yto1yWQiwwtpjzoB2B5AL%3Dgfh31w6Z%2B-wfevFN1Ow%40mail.gmail.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+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/CANeXGWWus3h5VqnoYjWV%3D9z7MaBZO%2B%3DMQGZGkuM76gBh9n5KOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+1
On Sat, Feb 10, 2018 at 4:38 PM Sara Golemon <p...@golemon.com> wrote:

> On Monday, February 5, 2018 at 1:22:37 PM UTC-5, Matthew Weier O'Phinney
> wrote:
>>
>> Last year, in May, I opened a discussion period regarding the PSR-17
>> working group, as the proposal pre-dated the latest by-laws... and
>> then evidently forgot to open a vote for it.
>>
>> So, I'm opening a vote as of today, 2018-02-05. Per the by-laws, this
>> vote is for Core Committee members only, and will run until all
>> members have voted, or 23:59:59 on 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.
>>
>>  +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 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/4637468f-8ab7-4885-bc07-d7657bf0f72d%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/4637468f-8ab7-4885-bc07-d7657bf0f72d%40googlegroups.com?utm_medium=email_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/CANeXGWWn2Gy8V7sbstD7t3%2Ba%3DLbHfXjDOrFruhFXEXvMGqm8Ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [VOTE][Internals] Secretary election

[Korvin Szanto]

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:
>>
>> Hello everyone,
>> as specified in the previous thread (
>> https://groups.google.com/forum/?fromgroups#!topic/php-fig/EKDIoSHqMSo),
>> yesterday at midnight the nominations ended, and since today it's possible
>> to vote for the renewal of the terms that are up for this elections.
>>
>> These are the nominations results:
>> https://docs.google.com/spreadsheets/d/1u_Bi2EXJ47iC_xMAUjkJWjz7Gks_BCW15RDXy_qXR9c/
>>
>> Since we have 4 unopposed nominations for the CC spots (and the terms are
>> all equals, so no sorting is necessary), we will need to vote for the
>> secretary position only, for which we have two nominations:
>>
>>  - Mark Railton
>> https://groups.google.com/forum/#!topic/php-fig/U5eaI90NOsc
>>  - Robert Parker
>> https://groups.google.com/forum/?fromgroups=#!topic/php-fig/BjxM9CVZ3Bg
>>
>> Full information about the Secretary vote and role is visible in the
>> bylaws here:
>> http://www.php-fig.org/bylaws/mission-and-structure/#secretaries
>> 
>>
>> Normally we should use STV, but since we have just one term and two
>> candidates, it will be the same if we simply vote with one direct, single
>> preference. So, to recap:
>>
>> *Who can vote?*
>> As specified in the bylaws, *any Project Representative or Core
>> Committee member* is eligible to vote on Secretary candidates.
>>
>> *When can you vote?*
>> Voting will be open *until 26th January 23:59 UTC.*
>>
>> *How to vote*
>> The voting system used is STV[1][2], so basically, *there is no tactical
>> voting possible* (like with FPTP); *vote for who you want*, even if they
>> are a less popular candidates as your vote will move down to a different
>> candidate if you back an unpopular candidate who doesn't have enough votes;
>> if a candidate is elected, their surplus votes are also re-allocated so you
>> are not punished for backing popular candidates either. There is no quorum,
>> you are of course entitled to not vote and it will not count as a
>> missed vote on the voting sheet. *Rank the candidates in order of
>> preference *for example*:*
>>
>> 1. Luke
>> 2. Leia
>> 3. Anakin
>> 4. Rey
>> 5. Padmé
>> 6. Finn
>>
>> At the end of the voting phase I will be announcing the results, and all
>> the newly elected (both CC members and secretary) on the 28th, as announced
>> before.
>>
>> Thanks!
>>
>> Alessandro Lai
>> PHP-FIG Secretary
>>
>> [1]: STV User-friendly Explanation
>> https://www.youtube.com/watch?v=l8XOZJkozfI
>> [2]: https://en.wikipedia.org/wiki/Single_transferable_vote
>>
> --
> 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/a6ce2237-2a2b-4d38-a624-73367e94dace%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+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/CANeXGWUWXTxXGnG88f2eNBL7FeYxiJqgo8iq%3DbHJ%3DjP%2BidO1Pw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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
> <mweierophin...@gmail.com> wrote:
> > The REVIEW period for the proposed PSR-15, HTTP Server Request
> > Handlers, hit its minimum required length on 2 January 2018. We
> > continued the period since then to iron out additional clarifications
> > to the specification, which have all since been merged.
> >
> > At this time, I am opening an ACCEPTANCE VOTE. Per the by-laws, the
> > acceptance vote is limited to Core Committee members. The vote will
> > close either at 23:59:59 UTC on 26 January 2018, or when all CC
> > members have cast their vote, whichever comes earlier.
> >
> > The relevant materials are as follows:
> >
> > - Specification:
> >
> https://github.com/php-fig/fig-standards/tree/4b417c91b89fbedaf3283620ce432b6f51c80cc0/proposed/http-handlers/request-handlers.md
> > - Meta Document:
> >
> https://github.com/php-fig/fig-standards/tree/4b417c91b89fbedaf3283620ce432b6f51c80cc0/proposed/http-handlers/request-handlers-meta.md
> >
> > Implementations include those implementing only the
> > `MiddlewareInterface` (e.g., middleware providers) to those
> > implementing full middleware frameworks. Below is a list of some that
> > we feel are particularly representative:
> >
> > - https://github.com/northwoods/broker — Maintained by Woody Gilk, our
> > Editor, this is a middleware dispatcher.
> > - https://github.com/middlewares — Maintained by Oscar Otero, a
> > working group member, this is a suite of reusable PSR-15 middleware
> > implementations you can compose into an application.
> > - https://github.com/zendframework/zend-stratigility/pull/134 — This
> > is a patch to an upcoming 3.0 version of zend-stratigility (maintained
> > by Zend Framework) that demonstrates the project plans to implement a
> > pure PSR-15 middleware dispatcher (vs a hybrid dispatcher as we do in
> > version 2). It provides a hybrid request handler/middleware
> > implementation allowing creation of a queue of middleware, and uses an
> > intermediary request handler to manage and dispatch that queue.
> > -
> https://github.com/zendframework/zend-expressive-skeleton/tree/release-3.0.0
> > — This is a proposed version of Expressive that uses Stratigility v3,
> > and thus represents a full PSR-15 middleware framework. The Zend
> > Framework project also has around 2 dozen middleware packages that all
> > have branches dedicated to PSR-15 support at this time; these are
> > representative of reusable PSR-15 `MiddlewareInterface`
> > implementations.
> > - https://github.com/ellipsephp/dispatcher — Maintained by Pierre
> > Mallinjoud, this is a PSR-15 middleware dispatcher that recursively
> > decorates a middleware queue in request handlers.
> >
> > We identified around a half-dozen other projects as well, some of
> > which were still pinned to earlier revisions of the specification, but
> > theoretically compatible with little effort. As such, we more than
> > satisfy the minimum of 2 reference implementations. We can provide
> > additional links on request.
> >
> > --
> > Matthew Weier O'Phinney
> > mweierophin...@gmail.com
> > https://mwop.net/
>
>
>
> --
> Matthew Weier O'Phinney
> mweierophin...@gmail.com
> https://mwop.net/
>
> --
> 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/CAJp_myWRiR9oMNvsbrWrtm%3DHeHhZF%3DXcObxUHwr9ucAs4_BEJA%40mail.gmail.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+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/CANeXGWXbsqhz3Fb5ffukuZfzExGyHt6yRLKVZjiAD10QaV5Wgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Secretary nomination] Robert Parker

[Korvin Szanto]

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

-- 
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/CANeXGWWTbibGK1%2B_U-cG0rCLzwGLF9XYU6JNVZqsTw9n8Xj6Tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC nomination] Korvin Szanto

[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 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/d664cac1-9164-4c7e-afb4-8e9bd080b987%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/d664cac1-9164-4c7e-afb4-8e9bd080b987%40googlegroups.com?utm_medium=email_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/CANeXGWUaaCHdNAmv8t0KqER6Z1ivO2NiFWfMTkvGgTdp6jw8mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

Hi Everyone,
With a unanimous vote, we have decided to move into review!
https://github.com/php-fig/fig-standards/pull/955

Thanks,
Korvin

On Wednesday, November 8, 2017 at 1:23:39 AM UTC-8, Michael Cullum wrote:
>
> +1
>
> Michael
>
> (This email is posted not as a FIG secretary but as a WG member)
>
> On 8 Nov 2017 4:13 am, "Shefik" <shefik@gmail.com > 
> wrote:
>
> +1 Zikula
>
> -
>
> Shefik
> +1 914-548-5033 mobile
> she...@shefik.info 
>
> Portfolio: http://shefik.info
> LinkedIn: https://www.linkedin.com/in/shefik
> Twitter: @shefik_info
> GitHub: https://github.com/shefik
>
> The information contained in this message and any attachment may 
> be proprietary, confidential, and privileged or subject to the work 
> product doctrine and thus protected from disclosure. If the reader of this 
> message is not the intended recipient, or an employee or agent responsible 
> for delivering this message to the intended recipient, you are hereby 
> notified that any dissemination, distribution or copying of this 
> communication 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:
>
> +1
>
> -Chris Tankersley
>
> On Tue, 2017-11-07 at 20:05 +, 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 ensure the process is
> properly followed.
>
> Please do not vote in this thread unless you are listed as a member
> of the working group. A +1 vote means that you support moving forward
> into review, and a -1 means that you think the working group should
> discuss this more.
>
> As this is a readiness vote, quorum will be 50% and a majority of at
> least 2/3 is required for passage. Though I hope to see a unanimous
> 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 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/CANeXGWVDdjJhG93x-
> YwgUh2SU93wKXzNfSQ4NcGEQCV12D5o%2BQ%40mail.gmail.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+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/1510111877.27420.142.camel%40ctankersley.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+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/76CAD787-93BB-463C-8FF3-113462926298%40gmail.com
>  
> <https://groups.google.com/d/msgid/php-fig/76CAD787-93BB-463C-8FF3-113462926298%40gmail.com?utm_medium=email_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/0cb56bf6-28c0-47f6-a758-eea5d63e215f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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 ensure the process is properly followed.
>
> Please do not vote in this thread unless you are listed as a member of the 
> working group. A +1 vote means that you support moving forward into review, 
> and a -1 means that you think the working group should discuss this more.
>
> As this is a readiness vote, quorum will be 50% and a majority of at least 
> 2/3 is required for passage. Though I hope to see a unanimous 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 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/33c72fdd-e827-4d9b-ac7e-1b9bb1a4ddd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[VOTE][WG] PSR-12 Readiness Vote

[Korvin Szanto]

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 ensure the process is properly followed.

Please do not vote in this thread unless you are listed as a member of the
working group. A +1 vote means that you support moving forward into review,
and a -1 means that you think the working group should discuss this more.

As this is a readiness vote, quorum will be 50% and a majority of at least
2/3 is required for passage. Though I hope to see a unanimous 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 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/CANeXGWVDdjJhG93x-YwgUh2SU93wKXzNfSQ4NcGEQCV12D5o%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [VOTE] Secretary Election

[Korvin Szanto]

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 attempting to get more nominations so this has been delayed a
>> few times but we now have three candidates so we're rolling with it.
>>
>> Full information about the Secretary vote and role is visible in the
>> bylaws here:
>> http://www.php-fig.org/bylaws/mission-and-structure/#secretaries
>>
>> You can check out their nomination topics and ask questions there.
>>
>> *Votes may be cast by project reps or CC members.* If an individual is
>> both a rep and a CC member, they may one vote once.
>>
>> *Nominations List*
>>
>>- Margret Staples - Topic
>>
>>- Alessandro Lai - Topic
>>
>>- Mark Railton - Topic
>>
>>
>> *How to vote*
>> The voting system used is STV[1][2], so basically, *there is no tactical
>> voting possible* (like with FPTP); *vote for who you want*, even if they
>> are a less popular candidates as your vote will move down to a different
>> candidate if you back an unpopular candidate who doesn't have enough votes;
>> if a candidate is elected, their surplus votes are also re-allocated so you
>> are not punished for backing popular candidates either. There is no quorum,
>> you are of course entitled to not vote and it will not count as a missed
>> vote on the voting sheet. *Rank the candidates in order of preference *for
>> example*:*
>>
>> 1. Luke
>> 2. Leia
>> 3. Anakin
>> 4. Rey
>> 5. Padmé
>> 6. Finn
>>
>> *You may, if you wish, not rank all three candidates* (however this is
>> relatively pointless in STV, only do this if your bottom candidates are of
>> equal preference to you). For example:
>>
>> 1. Luke
>> 2. Anakin
>> 3. Padmé
>> 4. Leia
>>
>> *The vote ends at 23:59 UTC on the 2nd November,* and I will close the
>> vote and *announce the result at some point on the 3rd*. At any time,
>> any candidate or voting member may privately ask me to do a count and tell
>> them who would be elected to which term if the vote ended at that point.
>> Please be wary of 'STV calculators' on the internet as there are many
>> different ways of calculating the vote reallocation for STV and many are
>> inaccurate, our methods are dictated in the bylaws.
>>
>> Good luck to all the candidates!
>>
>> --
>> Many thanks,
>> Michael Cullum
>> FIG Secretary
>>
>> [1]: STV User-friendly Explanation
>> https://www.youtube.com/watch?v=l8XOZJkozfI
>> [2]: https://en.wikipedia.org/wiki/Single_transferable_vote
>>
> --
> 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/8bfa4c34-75d5-484e-b02c-1f01d9ceabdd%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+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/CANeXGWXjODDG7MVdxnmzd32L2w7D_5k7itztr9Oxch%3D4cYyxsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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 anyone 
that comes across this issue and is wondering what the best way to handle 
this is: https://github.com/php-fig/fig-standards/pull/939

Best wishes,
Korvin


On Thursday, September 28, 2017 at 1:22:05 AM UTC-7, Vinor cola wrote:
>
> Please check this: https://youtu.be/ZsHMHukIlJY?t=1319 (watch few 
> minutes, especially where the guy replace the code with X)
>
> Understand that visualy, a parenthesis is not enough to quickly make a 
> block distinction. This is a matter of readability: you cannot at a glance 
> get where parameters ends and where code starts. You said PS-12 allow new 
> lines after opening bracket. I think in this particular context, it should 
> make the new line mandatory.
>

-- 
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/f8227106-6c78-4266-93e6-8e507784c3d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/39a74ddc-ce85-4039-9568-38aac95a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

Hi Everyone,
PSR-12 was already accepted and assigned the number 12 back in FIG 2.0[0], 
however, it turns out that my post on the 30th of June[1] was way too late 
to qualify as a grandfathered recommendation. So in order to make sure we 
follow the process properly, we're holding an entrance 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] 
and the meta document[3] but please keep in mind that we are not voting on 
the content of this draft.

Thank you for your time!
Korvin Szanto

[0]: https://groups.google.com/d/msg/php-fig/P9atZLOcUBM/_jwkvlYKEAAJ
[1]: https://groups.google.com/d/msg/php-fig/iqLzVvj6C2c/2hEOAQFbAAAJ
[2]: 
https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide.md
[3]: 
https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide-meta.md

-- 
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/09e35685-1488-45f7-96ee-14b5265cdfd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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.
> 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/608dfbea-b47b-4004-b642-358da6656b71%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/608dfbea-b47b-4004-b642-358da6656b71%40googlegroups.com?utm_medium=email_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/CANeXGWW4XjPzLhwMKe2YJ-F9X2cgnuqeSe128kOKPYaPz4Rj2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

FIG 3.0 Working Group for PSR12

[Korvin Szanto]

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
Michael Cullum
Robert Deutz

If anyone is interested in joining, please feel free to reach out to any of
us!

Best wishes,
Korvin

-- 
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/CANeXGWXqpcgpZbGf-Z8mm9N9hf9nRYETETj51cNh%3D9%3D2ZezXLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposing PSR 18 'Singleton' Pre-Draft

[Korvin Szanto]

Hi Richard,
Perhaps moving forward we have an opportunity to include more code in our
recommendations, and I think that's likely a good thing. With that said, I
would think with containerization being a big thing in PHP these days,
singletons are going to be a tough sell.

I think something like this would best benefit the community as an open
source project perhaps on composer that people can use if they want. That
way if it gains serious traction you'll have had feedback and a solid proof
of the idea that people want to not have to think about how they work with
singletons.

Some things that would be good to pay attention to as you do this is
implementing other PSRs (like PSR-1 and 2 and PSR-11), ensuring your
contracts are defined in something that is typehint-able (you can't
typehint on traits), and perhaps thinking about how you can invert the
responsibility of bootstrapping the singleton that is being used.

Thanks for your interest in the FIG, I hope to hear from you more in the
future!

Best wishes,
Korvin

On Sun, Feb 19, 2017 at 6:35 PM Richard T. Miles <tmiles...@gmail.com>
wrote:

> I suppose I was thinking 'How should one implement for maximum
> portability?' A Skeleton system requires the use of methods that can not
> be defined in a standard interface ( static members ). I do consider myself
> a bit novice; however, the intention of the singleton isn't to limit the
> creative process of the developer. I believe storing data in skeleton
> pattern is a `Cleaner` abstraction model than a container system. I
> definitely want to hear what the communities thoughts on the matter are.
> I understand PHP-Fig tries to leave the creative process open to the next
> innovation, and it may be that this abstraction is to detailed; 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
> 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 Richard T. Miles <tmil...@gmail.com>
> wrote:
>
> Hello to everyone here at PHP-FIG!
>
> I have been working on 'Singleton' in my spare time and think it may have
> some use in this community.
> I am a Computer Science student at the University of North Texas so
> development starts and stops pretty
> sporadically ( 1 am and coffee ). I think it finally has enough content to
> be presentable under a 'Pre-draft'
> context.
>
> Singleton Github Repository:
> https://github.com/RichardTMiles/Singleton-Standard
>
> All comments and constructive criticism welcome!
>
> Thanks for your time,
> Richard Miles
>
> --
> 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/19954bdc-3c2d-4dc4-a4d8-eee58c9891ec%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/19954bdc-3c2d-4dc4-a4d8-eee58c9891ec%40googlegroups.com?utm_medium=email_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/255df385-98b9-42a4-b98d-00be86c57e1b%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/255df385-98b9-42a4-b98d-00be86c57e1b%40googlegroups.com?utm_medium=email_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/CANeXGWWb9KNSkQ06nymoi_TC0XtG7wBi9Sx-0UhACYorrn81Vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: PSR-7 Alternate Proposal

[Korvin Szanto]

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 principles. I can see your points, but
> raise you this:
>
> SRP says only that a `car` class should not implement both
> responsibilities *by itself*!
>
>
> Currently, the middleware proposal and current used implementation ask for
> exactly that. That the middleware be responsible for the inbound and
> outbound flow. Even if it is for the middleware to decide that for itself,
> it is still a breach of SRP allowing a class to decide that. My point is
> the choice should not be there in the first place, by way of defined
> interfaces.
>

The middleware doesn't necessarily dictate where your behavior takes place.
Follow Dependency Inversion and Interface Segregation and you can achieve a
single responsibility for each class, even for the extra-strict (in my
opinion) version of SRP/ISP you are presenting. If you want to have these
concerns be separate, inject the behaviors as dependencies and treat the
middleware itself as more of a behavior router. That way each of your
individual behaviors are handled in individual classes.

A good example of this in my mind is containers. We have the container PSR
that is super minimal (has / get). That doesn't mean that a container won't
also try to do dependency injection and automatic instance inflation all
kinds of other stuff. In fact most of them WILL. They simply delegate those
responsibilities / behaviors to a dependency and there-by avoid SRP/ISP/OCP
issues. IMHO


> My point about ISP is to follow the definition you stated. If we take away
> the choice of multiple responsibilities from the middleware, then we must
> separate the interfaces. And I do know that it is not about PHP interfaces,
> but that is what they are for, along with the same in JAVA, and class
> abstractions; they are used to define the contract between classes: Can
> this middleware affect the request? Can this middleware affect the
> response? That kind of question comes from the interface the class
> implements.
>

The current state of PSR-15 as I see it doesn't prevent tracking what the
middleware is doing in the course of a request. Since the DelegateInterface
is an instance that a middleware stack is injecting, you can track pretty
easily how far the request moves through the stack.

Now if the issue is trying to preemptively know whether or not the
middleware does this or that, PSR-15 currently doesn't cover inserting
middleware into a stack. In my mind this is something that humans do so
they should be aware of what the middleware does and is for when they add
it to the stack.

So with those two arguments in mind, can you provide an example where a
middleware stack would need to be able to identify whether a middleware
will be returning a response or a request or dieing without simply
observing what happens when the request flows through the stack?

Thanks for the interest and discussion, I'm very pleased with the state of
the FIG these days, very constructive and interesting.

-- 
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/CANeXGWX%3Dpnu4t3gA4F3GhQ9ikpqv7v6h5tyGUG7pmniF-s1FpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposing PSR 18 'Singleton' Pre-Draft

[Korvin Szanto]

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 Richard T. Miles 
wrote:

> Hello to everyone here at PHP-FIG!
>
> I have been working on 'Singleton' in my spare time and think it may have
> some use in this community.
> I am a Computer Science student at the University of North Texas so
> development starts and stops pretty
> sporadically ( 1 am and coffee ). I think it finally has enough content to
> be presentable under a 'Pre-draft'
> context.
>
> Singleton Github Repository:
> https://github.com/RichardTMiles/Singleton-Standard
>
> All comments and constructive criticism welcome!
>
> Thanks for your time,
> Richard Miles
>
> --
> 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/19954bdc-3c2d-4dc4-a4d8-eee58c9891ec%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+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/CANeXGWUrYRoJjiCOCT6p9oro%2Bbr_%3DHAgtvT6iDXnYvKmb4CeTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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
>
> --
> 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/d6cdb84c-7148-4c75-95ab-e4b8d749f977%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/d6cdb84c-7148-4c75-95ab-e4b8d749f977%40googlegroups.com?utm_medium=email_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/CANeXGWXXWpXf4-i4Zh9y_519aws25DA%2B5uaYxhFRzkbJvJWNLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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, 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/d6cdb84c-7148-4c75-95ab-e4b8d749f977%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+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/CANeXGWVRxQJnJAkucHpsJr7DEJEvyAVC8R2nRxXOp-%2B_c8gGRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enhance code readability

[Korvin Szanto]

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 blank lines are allowed for readability, can anyone show anything in
the document that says differently?

What I would do is take this to PHPCS. I don't think this deserves errata,
instead we should take care with PSR-12 to make sure that this
misunderstanding doesn't continue.

Best wishes,
Korvin
On Mon, Feb 6, 2017 at 6:15 PM Greg Sherwood  wrote:

> On Monday, 6 February 2017 20:45:47 UTC+11, Ryan R. wrote:
>
> I use an extreme example here to show how relaxing coding standards can
> lead to unexpected results and thus inconsistency. It seems to me that
> developers relying on PHPCS to keep their code clean through checking and
> auto-fixing will now have to use custom rulesets to enforce what is a
> pretty standard rule. That feels like a big step backwards.
>
>
> @Greg : Would it not be possible to add some kind of parameter value to
> indicate the upper limits authorized ? And set it to 1 by default (or 0
> since you do not want to modify the current system because of the number of
> projects relying on it) ?
> Then if we want to allow empty lines we could simply modify the parameter
> value !
>
>
> Yes, that's what I was trying to suggest in my reply. Either way, some set
> of developers would not be able to use the included PSR2 standard as-is -
> they would need to use a ruleset.xml file and either include a specific
> sniff or change a sniff option.
>
> Given that developers who want to allow a single blank line already have
> to use a custom ruleset, keeping the default at 0 blank lines means those
> developers can change their ruleset from excluding the sniff to changing
> one of its settings - making it more useful.
>
> But obviously, the side effect is that you're not following PSR2 as PHPCS
> sees it. I don't think this makes any difference (any consistency is good)
> but maybe others do.
>
> If you think an option would solve your specific problem and you're not
> too concerned about if PSR-2 in PHPCS enforces 0 or 1 blank lines, then I'd
> suggest opening a new Github issue and we can work out a solution along
> those lines.
>
> Greg
>
> --
> 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/10a99a91-547e-4cc9-b05f-d58f2b6ef7b4%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+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/CANeXGWVXauPbbRkeJnaOc%2BQT5X%2BJbUYn5_Wyn1ZN37K6MSYyMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enhance code readability

[Korvin Szanto]

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, can you link to where in PSR-2
you're seeing that? From what I understand PSR-2 currently allows blank
lines and even (sort of) encourages adding them to improve readability [1]:

> Blank lines MAY be added to improve readability and to indicate related
blocks of code.

 so we should be all set on this front.

[1] http://www.php-fig.org/psr/psr-2/#lines

Best wishes,
Korvin

-- 
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/CANeXGWXSXXmQkOdJV4WSxndCzLkjp2C8Bi3i%2BxeGm6ckQ3jqQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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 vote for
> PSR-11.
>
> Please find the specification here:
>
> - 
> https://github.com/php-fig/fig-standards/blob/c4cbf7c1ef5052e10e776381d69670beaa59beed/proposed/container.md
>
> and the metadocument here:
>
> - 
> https://github.com/php-fig/fig-standards/blob/c4cbf7c1ef5052e10e776381d69670beaa59beed/proposed/container-meta.md
>
> This vote falls in the tail-end of the FIG 2.0 by-laws. As such:
>
> - We currently have 37 voting member projects, which means
> - We need 13 votes to pass quorum, and
> - Half or more of all votes cast must be in favor
>
> in order for the vote to approve acceptance of PSR-11.
>
> Voting starts now, and will run until 23:59 UTC on 13 February 2017.
>
> On behalf of the PSR-11 team, thanks for your attention!
>
>
>
>
> --
> 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/f52652a0-61ff-7833-f021-7591dad8c8f2%40gmail.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+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/CANeXGWU0%3Dbi-2%3D8ZsAXXAUvr5y2RSOCj7NYHBcn9JVNGO55O%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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 we have the new structure
fully laid out.

Best wishes,
Korvin
On Tue, Jan 3, 2017 at 10:46 AM  wrote:

Hi,
I would like to submit my application for membership on behalf of the
"Catappa Framework. "
Catappa provides an Annotation-based MVC and ORM.

Catappa,  implementation "PSR-4: Improved Auto Loading" and "PSR-7: HTTP
message interfaces".

As we add new features, we will pay attention to compatibility with other
PSR standards.

Link:www.catappaframework.com
Github:https://github.com/HBora/Catappa-Framework/tree/1.0.3
Packagist:https://packagist.org/packages/catappa/catappa


Thanks for the consideration.

H.Bora ABACI.

-- 
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/ed2d9379-3b73-4680-8919-cf1949dae614%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+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/CANeXGWUm68%3D34yJwyMUe74m-qaCmGEDtGjMaMGkwaXbQPk4miw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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 "default"
> value, which allows deferring calculation of such a value until it's
> needed. Was this ever considered? If so, why was it rejected? If not, could
> this be important?
>
> - The spec mentions compatibility with psr-6, and mentions that each
> instance should be considered a logical pool instance. What I fail to see
> in the meta document is any indication of examples of how the two relate at
> an operational level. Examples, I feel, are required here.
>
> - I've seen discussion of why hasMultiple was omitted, but those are not
> captured in the meta document.
>
> As such, the spec feels incomplete.
>
> On Dec 18, 2016 9:25 AM, "Jordi Boggiano"  wrote:
>
> After a fruitful month of review and final tweaks (thanks to all
> involved), I think we are ready for a vote here at the PSR-16 headquarters.
>
> Please find the specification here:
>
> -
> https://github.com/php-fig/fig-standards/blob/1d4f586d0bbe7e30cf8972268be8cef9d321fdcc/proposed/simplecache.md
>
> And the meta document:
>
> -
> https://github.com/php-fig/fig-standards/blob/1d4f586d0bbe7e30cf8972268be8cef9d321fdcc/proposed/simplecache-meta.md
>
> There are currently 37 voting member projects, which means we must
> have 13 votes to pass quorum, with half or more of all votes cast in
> favor, in order to approve acceptance of PSR-16.
>
> Voting starts now (Dec 18th 15:25 UTC) and will therefore run until
> January 1st, 15:25 UTC - so we can hopefully start the year on a good note
> ;)
>
> Best Regards and Merry Christmas while I am at it,
> Jordi
>
> --
> Jordi Boggiano
> @seldaek - http://seld.be
>
> --
> 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/612cb66a-2ff8-ef20-7314-4c5d14cef0a0%40seld.be
> .
> 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/CAJp_myVFG7JD5HX_%2B0%2Bs4Ss84iicPh2V7omD9Q7LH-6AUz7qyg%40mail.gmail.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+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/CANeXGWVbBfW7dyzjnBT8p_ZSt%2B_cnL%2Bp8HDf7%2BG4TAFGrfq%2BHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [VOTE] First Core Committee Elections

[Korvin Szanto]

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 voted for those who have impressed me with their knowledge and/or effort 
in the PHP-FIG and greater PHP community.

Best wishes,
Korvin

-- 
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/04081a8c-3cb8-4804-928a-a0a03b58035e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [CC][Nomination] Korvin Szanto

[Korvin Szanto]

Hi All,
I wanted to post back to this thread and give a rundown of who I am for
those who don't know me.

* I am extremely passionate about opening up communities and working
together rather than separately
* Working on an open source CMS has taught me to work with competition to
better serve the users rather than against each other
* I’ve lived through the pain of closed source / closed community “this
just works” thinking, and it has annoyed me so deeply I’ve made career
decisions based on it
* I manage large swaths of a big open source project including things
important to FIG like principle design and security issue management
* I’ve always been active in FIG decisions, and I think my track record
shows I am considerate of all views and careful with political situations

So why do I want to be a member of the Core Committee?

I have worked with many different languages in many different environments
and I'm always excited by best practices and elegant code. PHP is an
extremely forgiving language and it's taken us quite a long time to bolster
the community up to the point where we can hold a conversation about SOLID.
I'd say the community has shown that they are ready for FIG 3.0 to exist,
and I think it's important that we realize that we are writing rules that
will have an effect on EVERYONE and not just framework developers who are
implementing them. Working to modernize concrete5 over the years has taught
me some extremely valuable lessons and has allowed me to shift my mind away
from "RULES RULES RULES" and towards a more pragmatic approach that suits
junior and senior devs alike instead of just the computer scientists at the
top.

If you vote for me, you're voting for an active thorough reviewer that will
ensure PSRs work for everyone they 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 <korvinsza...@gmail.com> wrote:

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 issues even when voices become heated. His technical ability is also of
a level that he brings a high level of quality to each thread he has
contributed to.

Regards,
Adam Culp
IBMiToolkit

-- 
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/7b56aaff-0ce3-4256-9c7c-46d6161af49e%40googlegroups.com
<https://groups.google.com/d/msgid/php-fig/7b56aaff-0ce3-4256-9c7c-46d6161af49e%40googlegroups.com?utm_medium=email_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/CANeXGWU0QPaNj5C_Vt7LE8s0%3DCSYEN7qVsZopcDy6BOT_bHR3w%40mail.gmail.com
<https://groups.google.com/d/msgid/php-fig/CANeXGWU0QPaNj5C_Vt7LE8s0%3DCSYEN7qVsZopcDy6BOT_bHR3w%40mail.gmail.com?utm_medium=email_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/CAAqcDMgyuhf-5wF1WECR2uhy7wKMdaUqGuZfbQEbOMmt%3DG0%3DMA%40mail.gmail.com
<https://groups.google.com/d/msgid/php-fig/CAAqcDMgyuhf-5wF1WECR2uhy7wKMdaUqGuZfbQEbOMmt%3DG0%3DMA%40mail.gmail.com?utm_medium=email_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 

Re: [Internals] Change to FIG 3.0 term lengths

[Korvin Szanto]

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:
> > Hi all,
> >
> > It was noted by a few individuals that the way the bylaws stand about
> > fulfilling the initial 12 Core Committee roles as if there is a 12-member
> > vacancy this leads to a rather inefficient situation where some people
> would
> > have their terms expire in April/May of this year which I'm sure you all
> > agree is non-ideal as (1) they won't have time to settle in (2) CC
> elections
> > take time and focus away from working on specifications and two in such a
> > short period is relatively unhelpful.
> >
> > However, a small change could help resolve this issue so I'm just asking
> if
> > anyone objects to us doing it slightly differently**
> >
> > The old system would have involved the following three terms:
> > Top four candidates term expires in: August 2018
> > Next four candidates term expires in: January 2018
> > Last four candidates terms expire in:  April 2017
> >
> > My suggestion is to change it so they receive the following (slightly
> > extended terms so the minimum term is ~1 year and maximum is just over 2
> > years):
> > Top four candidates term expires in: April 2019
> > Next four candidates term expires in: August 2018
> > Last four candidates terms expire in:  January 2018
> >
> > Essentially, we just skip the first normal CC election and extend
> everyone's
> > term by a few months so that we stay on the defined calendar for future
> > elections.
>
> This sounds reasonable to me; I was taken by surprise by how quickly
> the secretary position was up for election again this past year, and
> would definitely like to avoid that situation again.
>
>
> --
> Matthew Weier O'Phinney
> mweierophin...@gmail.com
> https://mwop.net/
>
> --
> 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/CAJp_myWuJiVdAwmERs772DRFb-%2BgU7uHZe0uJ%3D2MAkys_dbkKw%40mail.gmail.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+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/CANeXGWVg4P%3DDYRWjheKKtQcHO5dZx-BsVLrK0gxgOKanWMmUPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

Ah I see, I was confused because the titles of those threads are
"Nomination Request". Thanks for clearing that up!

On Wed, Dec 7, 2016 at 3:23 PM Chris Tankersley <ch...@ctankersley.com>
wrote:

> Beau and Tobias were formally nominated by me via Sculpin :P
>
> I do thank 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 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
> representative muscles and use my power to nominate them all at once.
>
> So I am nominating the following people in no particular order:
> Chris Tankersley
> Tobias Nyholm
> Sam Minnée
> Beau Simensen
> Marc Alexander
> Steve Winter
>
> Please let me know if I missed anyone (sorry in advance), or if for some
> reason a bulk nomination doesn't work.
>
> Best wishes,
> Korvin
>
>
> --
> 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/CANeXGWWqZZ1v4RkWjJHLYGFYZUuOY1fBA9d7%2B_gV45pC5Am3Rg%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CANeXGWWqZZ1v4RkWjJHLYGFYZUuOY1fBA9d7%2B_gV45pC5Am3Rg%40mail.gmail.com?utm_medium=email_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/CAL9n4XM-LPwKBFake%3D2pkh%3DvaoTQdHoEtizQKfDqeAOKsOB96Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/php-fig/CAL9n4XM-LPwKBFake%3D2pkh%3DvaoTQdHoEtizQKfDqeAOKsOB96Q%40mail.gmail.com?utm_medium=email_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/CANeXGWUhWHYsF16yjuEjqiroBO8MRkQmx5eY4%2BePjkVr0qT13A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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
representative muscles and use my power to nominate them all at once.

So I am nominating the following people in no particular order:
Chris Tankersley
Tobias Nyholm
Sam Minnée
Beau Simensen
Marc Alexander
Steve Winter

Please let me know if I missed anyone (sorry in advance), or if for some
reason a bulk nomination doesn't work.

Best wishes,
Korvin

-- 
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/CANeXGWWqZZ1v4RkWjJHLYGFYZUuOY1fBA9d7%2B_gV45pC5Am3Rg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PSR-12]

[Korvin Szanto]

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 the
status quo of declare on the next line. Because of that data and because of
the subjective nature of this issue, we're probably unlikely to take
further discussion into serious consideration unless there's a new argument
that we haven't discussed before.

Thank you all for paying such close attention, I really appreciate you
keeping the discussion and excitement going while we work to get this
wrapped up. I plan to collect the remaining member replies and post some
results with a plan moving forward sometime this week.

Best wishes,
Korvin

On Sun, Dec 4, 2016 at 2:52 PM Michael Sheakoski <
michael.sheako...@gmail.com> wrote:

> Michael Mayer, I think your suggestion sounds like a good idea. My main
> point originally was to keep the declare() statements close to the  because they change how the language works. An example of what your
> suggestion might look like:
>
>  declare(strict_types=1);
> declare(encoding='ISO-8859-1');
> declare(ticks=1);
>
> /**
>  * Hello. I am a file-level DocBlock.
>  * I hope you are enjoying the example.
>  */
>
> use Foo\Bar\Baz;
> use InvalidArgumentException;
>
> /**
>  * Class Thing is a wonderful class,
>  * the best class.
>  */
> class Thing extends Baz
> {
> ...
> }
>
> I left the  they're closely related, but a blank line between other blocks should still
> remain. What does everyone think?
>
> -Michael
>
>
> On Sunday, December 4, 2016 at 2:01:09 PM UTC-5, Michael Mayer wrote:
>
> But we already have today:
>
> declare(encoding='ISO-8859-1');
> declare(ticks=1);
>
> And for both holds: *the file is running a special mode of PHP, not the
> usual one.*
> – Should I write all of them in the first line, or is strict_types such
> special?
> – And, if so, what makes it such special?
>
> Furthermore, at least for ticks, I see valid multi-line use cases:
>
> Block declare statements are allowed and MUST be formatted as below. Note
> position of braces and spacing:
> declare(ticks=1) {
> //some code
> }
>
>
> Moreover:
>
>  Each block MUST be in the order listed below, although blocks that are
> not relevant may be omitted.
>
>- File-level docblock.
>
>
>- One or more declare statements.
>
>
>- The namespace declaration of the file.
>
>
>- …
>
> Hence, I know where they are, and *I don't need to scan around doc blocks
> and namespace declarations.*
>
> Sorry, but I cannot see at the moment, how a consistent style
> recommendation may look like with that change.
> However, I understand that declare statements are more important than the 
> *File-level
> docblock –* thus why
> not move them to the top of the list instead?
>
> Best regards,
> Michael Mayer
>
> Am Sonntag, 4. Dezember 2016 18:50:55 UTC+1 schrieb Jordi Boggiano:
>
> I'm with Rudolph on this one, as I replied in the survey that was sent a
> while back. IMO it should be on the first line to make sure it's visible
> and not missed because it is such a meaningful line. It completely
> changes the way the engine works, it's not php anymore, but strict php,
> and you better be aware of it.
>
> As for the fear that more flags will be added, well of course it's
> possible but IMO unlikely. In any case we can revisit that topic if
> needed when we have more flags, I don't think we need to set the rule of
> today based on future unknowns.
>
> Cheers
>
> On 04/12/2016 14:48, Michael Mayer wrote:
> > I disagree too.
> >
> > What, if PHP8 will introduce a new execution directive and PHP9 as well
> > etc. And all of these are considered as good practice.
> > Where should I put them? All in the same line?
> >
> > |
> >  >
> declare(strict_types=1);declare(php8_directive=1);declare(php9_directive=1);
>
> >
> > useFoo\Bar\Baz;
> >
> > classThingextendsBaz
> > {
> > }
> > |
> >
> > Ewww!
> >
> > Best regards,
> > Michael Mayer
> >
> > --
> > 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/07f36815-e178-42ee-b76c-42fa446fbfd9%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/php-fig/07f36815-e178-42ee-b76c-42fa446fbfd9%40googlegroups.com?utm_medium=email_source=footer>.
>
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Jordi Boggiano
> @seldaek - http://seld.be
>
> --
> You received this message because you are subscribed to the Google Groups
> 

Re: [CC][Nomination] Korvin Szanto

[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 issues even when voices become heated. His technical ability is also of
> a level that he brings a high level of quality to each thread he has
> contributed to.
>
> Regards,
> Adam Culp
> IBMiToolkit
>
> --
> 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/7b56aaff-0ce3-4256-9c7c-46d6161af49e%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/7b56aaff-0ce3-4256-9c7c-46d6161af49e%40googlegroups.com?utm_medium=email_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/CANeXGWU0QPaNj5C_Vt7LE8s0%3DCSYEN7qVsZopcDy6BOT_bHR3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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
>
>
> On 11/09/2016 11:08 AM, Michael Cullum wrote:
>
> Hi all,
>
> Does anyone have any objections to extending the Core Committee nomination
> period one month and pushing the FIG 3.0 implementation timetable back a
> month (so the new implementation date will be 1st February)?
>
> There are still a number of people looking to be nominated or considering
> standing; meanwhile right now we only have 7 candidates when 15-20 would be
> a much more appropriate number for a fair election and we think at least 12
> at a minimum is still achievable if given a little more time.
>
> --
> FIG Secretaries
> --
> 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/CAAqcDMhSgM3qMZAnV9674xuLuLF3YQtx_otOv53ANJHsk%2Bq%2B7Q%40mail.gmail.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+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/bf316ec9-a158-a358-b310-5ba364a17add%40garfieldtech.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+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/CANeXGWUZs0VOFZ4pcSXtqvecKtFGYM5s4Ku0KtKC_Jw808oBgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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 deleted because I wanted to
> rephase it. (we can't edit posts here)
>
> I will remove the post with the cross link, it is no longer relevant.
>
> Regards,
> Adam Culp
>
>
> On Tuesday, November 8, 2016 at 8:26:42 AM UTC-5, Brian Teeman wrote:
>
> Adam that link point back to this thread
>
> --
> 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/6e7614af-d716-4759-ad0d-e4489562f8d2%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+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/CANeXGWWhMyrRCMrH8J5ZUW3PeCKHWB9-VtGBwjCfJuizYu%2B14A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

+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). No changes have
> > been made in the past two weeks since re-opening the review period.
> >
> > The specification is here:
> >
> > -
> https://github.com/php-fig/fig-standards/blob/a47c644f9d0f914bb0a9777eeaec157f2d51dbff/proposed/links.md
> >
> > And the meta document is here:
> >
> > -
> https://github.com/php-fig/fig-standards/blob/a47c644f9d0f914bb0a9777eeaec157f2d51dbff/proposed/links-meta.md
> >
> > As coordinator, as of 21:20 UTC, I hereby open voting to accept the
> > proposed standard.
> >
> > There are currently 37 voting member projects, which means we must
> > have 13 votes to pass quorum, with half or more of all votes cast in
> > favor, in order to approve acceptance of PSR-13.
> >
>
>
> --
> Matteo Beccati
>
> Development & Consulting - http://www.beccati.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 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/bb103307-6f4a-79b6-ec79-ed12b96be5f7%40beccati.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+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/CANeXGWXHMjf8FTVFHjj%3D85aqNTU0m3Guebo%3D-PNA63%2BbCj3xWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[PSR-12] Survey for outstanding issues

[Korvin Szanto]

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 point after
two weeks has passed we will disable responses and start reviewing the
results.

Q: Who can take this survey?
A: Anyone who is familiar with PHP 7 and feels like they have a stake in
this should add a response to this survey.

Q: Should I research PHP 7 first?
A: It's important that you know all of the syntax and features that we plan
to be defining so you will do well by doing your research first.

Q: Do I need to read through PSR-12 first?
A: You certainly should. We do copy relevant text out directly from the
PSR-12 documents into the survey so you can likely get through this survey
without studying PSR-12 too hard.

Q: Why do you ask for my full name?
A: So that we can differentiate one reply from the next. A project
representative may reply to the form twice, once for the project and once
for themselves. If this makes you uncomfortable, feel free to put a handle
in instead. Try to make it unique.

Q: Why do you ask for my email?
A: If we have any kind of misunderstanding or want to get more information
we might shoot you an email. If this isn't something you want to share
please do not share it.

Q: I'm a jokester, wouldn't it be funny if I made a joke response?
A: Please oh please do not make me sort through joke / fake replies :(

We hope to get a good idea of what the public, projects, and
representatives think about what we have put together. We ask that you
respond only once unless you are also a representative of a project in the
PHP-FIG and ask that you read all directions in the survey carefully.

After we've had time to sift through the results, we will post a summary on
the list and post an anonymized list of responses that can be seen by all.

Please take this survey here: https://goo.gl/forms/SonvjwqicPoBBwwl1


PSR-12:
https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide.md
Meta:
https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide-meta.md

Thanks for taking the time to respond!
Korvin & the PSR-12 team

-- 
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/CANeXGWWkTNZRav-ufQiV8gv1zbyQwkbA0rqUPGTRG9RWpbSPrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Output escaping PSR

[Korvin Szanto]

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 think there could be quite some value in producing a spec and set of
> interfaces for consistent output escaping across frameworks. Security is an
> important consideration in every app and having a consistent API would make
> it much easier get it right.
>
> Would like to hear peoples opinions on this and collect volunteers to join
> a working group.
>
> ~C
>
> --
> 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/4c634f36-bd9c-43d2-a387-90a47f4dad84%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+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/CANeXGWVgL22eBfb4aQeA1p2k1c5z6iNqnNyg%2BTg5uFG6xiBTuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Korvin Szanto]

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

>
> > On Sep 15, 2016, at 13:37, Matthew Weier O'Phinney <
> mweierophin...@gmail.com> wrote:
> >
> > On Thu, Sep 15, 2016 at 9:11 AM, Paul Jones  wrote:
> >> So I still have no idea if the secretary role is intended as an
> "assistant" type of secretary, or some other type of secretary. Again, this
> should be a straightforward thing to answer.
> >
> > You're creating a false dichotomy, Paul.
>
> Not at all. It might be part assistant, part something else (or perhaps
> multiple something elses).
>
> Regardless, I seem to have gotten an answer from Larry's SitePoint article
> on the FIG at <
> https://www.sitepoint.com/the-past-present-and-future-of-the-php-fig/> :
>
> > In late 2015, FIG added a 3-person Secretary position, elected by
> project reps, to handle managerial tasks but stay out of technical tasks. I
> personally feel that change has been a resounding success, as managerial
> tasks are actually getting done now ...
>
> Based on that, it seems the Voting Members are the workers in FIG, and the
> secretaries are the managers in FIG.
>
> Is that what everyone who voted +1 on the secretary role understood the
> case to be?
>
>
> --
>
> Paul M. Jones
> http://paul-m-jones.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 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/7DBA8B40-A3C8-4683-8670-9B651A55A719%40gmail.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+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/CANeXGWX8Y17FDG49Aeay4OazkATEyZ8goOM2h0GvFTtUK5fhZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.