Re: PSR-17 Explicit Nullable

+1 CRB On Mon, Apr 15, 2024, 07:12 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

Re: Service Provider PSR: rebooting the proposal

On Sun, Mar 24, 2024 at 10:31 AM Larry Garfield wrote: > On Sun, Mar 24, 2024, at 1:47 AM, Rasmus Schultz wrote: > > There's nothing wrong with anything Larry posted. > > > > But I already knew all of that would work. > > > > The issue is extensions - if you want to change an argument to a > >

[PSR-5] Reviving Working Group

This is a request to recharter a Working Group for PSR-5 / PSR - 19. I specifically need a new Sponsor from the Core Committee. This is also a call for interested members for the new Working Group. These individuals have already expressed interest: * Alexander Makarov * Ken Guest * Jaap van

Re: [Internals][ELECTIONS] Request for Nominations

Ken, do you accept? CRB *about.me/ashnazg <http://about.me/ashnazg>* On Fri, Feb 9, 2024 at 8:34 AM 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 Co

Re: [Internals][ELECTIONS] Request for Nominations

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

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

+1 CRB On Thu, Oct 5, 2023, 09:43 Vincent de Lau wrote: > +1, unfortunate indeed. > > On Thursday, October 5, 2023 at 4:39:26 PM UTC+2 Navarr Barnier wrote: > >> +1. An unfortunate necessity. >> >> On Thursday, October 5, 2023 at 10:37:39 AM UTC-4 Vincent de Lau wrote: >> >>> This thread is to

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

+1 CRB On Thu, Oct 5, 2023, 09:43 Vincent de Lau wrote: > +1, unfortunate indeed. > > On Thursday, October 5, 2023 at 4:39:31 PM UTC+2 Navarr Barnier wrote: > >> +1. An unfortunate necessity. >> >> On Thursday, October 5, 2023 at 10:38:37 AM UTC-4 Vincent de Lau wrote: >> >>> This thread is to

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

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

Re: [VOTE][CC] Hyperf Membership vote

+1 CRB On Mon, Jul 24, 2023, 04:14 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

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

+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

Re: [VOTE][CC][PSR-7] Errata proposal, urlencoding clarification

+1 CRB On Wed, Jun 14, 2023, 09:47 Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > +1 from me > > On Wed, Jun 14, 2023, 9:01 AM Matthew Weier O'Phinney < > mweierophin...@gmail.com> wrote: > >> In https://github.com/php-fig/fig-standards/pull/1298, David Buchmann >> proposed errata

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

+1 CRB *about.me/ashnazg * On Tue, Mar 21, 2023 at 11:44 AM Alessandro Chitolina wrote: > +1 > Il giorno lunedì 20 marzo 2023 alle 17:31:09 UTC+1 Ken Guest ha scritto: > >> +1 >> >> On Monday, March 20, 2023 at 4:18:55 PM UTC Navarr Barnier wrote: >> >>> +1 >>> >>> On

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

+1 CRB On Mon, Mar 13, 2023, 15:03 Matthew Weier O'Phinney < mweierophin...@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

Re: [ACCEPTANCE VOTE][CC] PSR-20 Clock Interface

Voting closed November 18th, with these results: Voting +1: Matthew Weier O’Phinney Chuck Burgess Michelle Sanver Alessandro Chitolina Ken Guest Jaap van Otterdijk Navarr Barnier Not voting: Larry Garfield Cees-Jan Kiewiet Chris Tankersley Korvin Szanto Enrico Zimuel With 50% quorum met (7/12

Re: [ACCEPTANCE VOTE][CC] PSR-20 Clock Interface

+1 CRB On Thu, Nov 3, 2022, 13:47 Chuck Burgess wrote: > I am opening an ACCEPTANCE VOTE for PSR-20, the Clock Interface. Per the > by-laws, the acceptance vote is limited to Core Committee members. The > vote will close either at 23:59:59 UTC on 18 November 2022, or when all > CC

[ACCEPTANCE VOTE][CC] PSR-20 Clock Interface

kages/kreait/clock - https://packagist.org/packages/beste/clock PLEASE DO NOT VOTE UNLESS YOU ARE A CC MEMBER. Current CC Members are as follows: Larry Garfield Matthew Weier O’Phinney Cees-Jan Kiewiet Chris Tankersley Korvin Szanto Chuck Burgess Enrico Zimuel Michelle Sanver Alessandro Chitolina Ke

Re: [Vote][PSR-20] Readiness Vote

roviders/psr/clock-implementation > > The vote will remain open for 2 weeks ending on September 5th or until > all 6 WG > members have voted, whichever comes first. If it meets a 2/3 majority, the > spec will go to the Core Committee for Review, moderated by our Sponsor, > Chuck Burges

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

+1 CRB On Fri, Aug 19, 2022, 01:17 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

[Nomination][CC] Jaap van Otterdijk

I nominate Jaap van Otterdijk for the role of CC member. He is a developer at Ingewikkeld and on the phpDocumentor core team. Chuck Burgess Core Committee member -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group&q

Re: PSR-20 Clock status

Burgess wrote: > Given no further discussion, I'm trying to reach the Editor via Github and > Discord (and here, if you see this, Chris Seufert) to get his ok on a > readiness vote. > CRB > > On Sat, Jul 23, 2022, 11:36 Chuck Burgess wrote: > >> On the timezone

Re: [Nomination][CC] Chuck Burgess

I accept... thanks Vincent. CRB On Mon, Aug 8, 2022, 04:44 Vincent de Lau wrote: > Hi all, > > Hereby I nominate Chuck Burgess for the role of CC member. > > -- > Kind Regards, > Vincent de Lau > PHP-FIG Secretary > > > -- > You received this message beca

Re: Rename php-fig/log-util into php-fig/log-util-test

On Wed, Aug 3, 2022, 10:12 Ralf Lang wrote: > > Am 03.08.2022 um 16:55 schrieb Larry Garfield: > > On Wed, Aug 3, 2022, at 6:56 AM, Vincent de Lau wrote: > >> The bylaws are not very clear on this, but I would think an Implicit > >> Approval would be sufficient here. My interpretation would be

Re: [Internal][ELECTIONS] August 2022 election round, request for nominations

e following people will be ending by the end of August: > - Cees-Jan Kiewiet (Core Committee) > - Chuck Burgess (Core Committee) > - Woody Gilk (Core Committee) > - Ben Edmunds (Core Committee) > - Alessandro Lai (Secretary) > > With this email, we open the nomination period, whic

Re: PSR-20 Clock status

Given no further discussion, I'm trying to reach the Editor via Github and Discord (and here, if you see this, Chris Seufert) to get his ok on a readiness vote. CRB On Sat, Jul 23, 2022, 11:36 Chuck Burgess wrote: > On the timezone being undefined... the UNIX timestamp integer retur

Re: PSR-20 Clock status

t's not that you have an ambiguous value in hand... it's just that the interface doesn't demand it present its "string value" in a single way... right? CRB *about.me/ashnazg <http://about.me/ashnazg>* On Sat, Jul 23, 2022 at 11:00 AM Chuck Burgess wrote: > My rewording PR for th

Re: PSR-20 Clock status

> -- > Larry Garfield > la...@garfieldtech.com > > On Tue, Jul 19, 2022, at 5:25 PM, Chuck Burgess wrote: > > After the progress Chris and I made since Sunday, I want to do one more > > read-over, possibly a wording PR... and then see if he as Editor is > > ready for the nex

Re: PSR-20 Clock status

field > la...@garfieldtech.com > > On Tue, Jul 5, 2022, at 6:30 AM, Chuck Burgess wrote: > > Sorry folks... if there was another email thread on this trying to move > > it along, I somehow missed it... and if Discord was deemed the official > > replacement to replace the emai

Re: PSR-20 Clock status

roup to be inactive. The Editor, Chris > Seufert, > >> has been inactive and unreachable via Discord in the WG's channel for > >> several months. The Sponsor, Chuck Burgess, has also not responded to > >> messages on Discord in the WG's channel. > >> >

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

+1 On Wed, May 25, 2022, 11:20 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

Re: [Vote] Maintainer for log-util library

+1 On Wed, May 18, 2022, 13:36 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

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

+1 On Wed, Apr 20, 2022, 09:28 Matthew Weier O'Phinney < mweierophin...@gmail.com> 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

Re: [ENTRANCE] [VOTE] [CC] Tracing PSR

+1 CRB On Tue, Mar 29, 2022, 03:03 Alessandro Chitolina wrote: > As the Sponsor for this candidate PSR, after seeing a positive response > and a great interest from the community, I hereby call the Entrance Vote. > > The PR of this proposal is here: >

Re: [VOTE] Core Committee Election January 2022

Ken Guest Korvin Szanto Chris Tankersley Enrico Zimuel Florian Engelhardt Navarr Barnier CRB (PEAR) On Sat, Jan 15, 2022, 10:51 Vincent de Lau wrote: > Hello everyone, > > Yesterday the nomination period ended, and we got 7 nominations in total, > which is great! > For the secretary seat, we

Re: [ENTRANCE] [VOTE] [CC] PER Coding Style

+1 On Sat, Jan 15, 2022, 21:33 Chris Tankersley wrote: > As the sponsor for this PER Working Group, I hereby call an entrance vote > for the PER Coding Style. > > The purpose of this PER is to migrate PSR-12 to a living document under > the new PHP Evolving Recommendations structure. This will

Re: [Entrance Vote]{CC] Localization PSR

+1 On Wed, Dec 8, 2021, 16:04 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

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

+1 On Thu, Oct 14, 2021, 02:12 Alessandro Lai wrote: > 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

Re: [PSR-20] Feedback for the ClockInterface

I think I remember most/all of the working group projects argued against the TZ piece. The metadoc specifically says TZ is not included... maybe that section should go deeper into the decision... ? CRB On Mon, Sep 13, 2021, 09:39 Woody Gilk wrote: > On Mon, Sep 13, 2021 at 9:26 AM Larry

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

+1 CRB On Tue, Sep 7, 2021, 12:06 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

Re: Proposal: PHP Evolving Recommendations (PERs)

I added some tiny correction comments, but overall, I like it  CRB On Thu, Aug 26, 2021, 10:00 Ken Guest wrote: > Hi, > > I think having Evolving Proposals would be a good thing. > > Then people only have to bookmark the PER once and revisit it when > appropriate instead of having to follow

Re: [PSR-12] Proposal for a @generated tag

PSR-19 actually... that's the tag catalog. CRB On Tue, Aug 10, 2021, 11:09 'Alexander Makarov' via PHP Framework Interoperability Group wrote: > That sounds like a candidate for PSR-5, not for PSR-12. > > On Tuesday, August 10, 2021 at 7:05:01 PM UTC+3 ezimuel wrote: > >> Hi, >> >> While

Re: [VOTE][CC] AzuraCast Membership vote

+1 Chuck Burgess (CC) On Sat, Jul 31, 2021, 10:05 Vincent de Lau 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 rep

Re: [Vote] PSR-3 Updates for Types

Sorry for missing this, team... I'm catching up this morning and see that I just missed it. FTR, I'd have been +1 too. CRB *about.me/ashnazg * On Tue, Jul 13, 2021 at 9:10 AM Larry Garfield wrote: > On Fri, Jun 25, 2021, at 9:35 AM, Larry Garfield wrote: > > Hear ye,

Re: [VOTE] Core Committee Election

1. Matthew Weier O'Phinney 2. Larry Garfield 3. Michelle Sanver 4. Woody Gilk 5. Alessandro Chitolina Chuck Burgess (PEAR) On Thu, Jun 10, 2021, 10:42 Alessandro Lai wrote: > Hello everyone, > as specified in the previous thread ( > https://groups.google.com/g/php-fig/c/9X

Re: [VOTE][CC] Bylaw CS update

+1 On Wed, Mar 31, 2021, 02:15 Alessandro Lai 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

Re: [Internal] Sunset Slack workspace?

+1 On Wed, Mar 24, 2021, 07:24 Alessandro Lai wrote: > Hello everyone, > I'm happy to see that the Discord experiment is going well: over 200 users > have joined, the newly formed WG for PSR-20 has found a home there, and > we've now migrated the Twitter and site deploy integration too. > > So,

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

gt; >> We have a new PSR-19 in draft status! >> >> Il giorno martedì 23 marzo 2021 alle 16:55:39 UTC+1 ch...@ctankersley.com >> ha scritto: >> >>> -1 >>> >>> -Chris >>> >>> On Mon, Mar 15, 2021 at 7:35 PM Chuck Burges

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

+1 On Mon, Mar 15, 2021, 18:35 Chuck Burgess 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 >

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

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

Re: Propsal Idea: ClockInterface

I'll sponsor this... there seems to be a good amount of interest. CRB On Mon, Mar 8, 2021, 18:08 Larry Garfield wrote: > On Mon, Mar 8, 2021, at 5:14 PM, Chris Seufert wrote: > > Hi, > > > > To update anyone on the progress made via the currently pull requests > > on github. The consensus is

Re: [Vote] PSR-13 Link Errata

+1 On Wed, Feb 24, 2021, 15:51 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 > >

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

+1 On Fri, Feb 19, 2021, 08:31 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

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

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

Re: [Vote] [PSR-13] updates

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

Re: [Internal][ELECTIONS] Core Committee nominations needed!

I accept... thanks Mike. CRB On Thu, Aug 13, 2020, 08:31 Mike van Riel wrote: > As phpDocumentor representative, I re-nominate Chuck Burgess for a new > term. > > On Tuesday, 11 August 2020 at 16:00:17 UTC+2 alessand...@gmail.com wrote: > >> Thank you Ben for stepping up

Re: [Internal][ELECTIONS] Secretary nominations needed!

As the PEAR representative, I nominate Alessandro Lai for a new term. CRB On Wed, Jul 29, 2020, 09:45 Alessandro Lai wrote: > > Hello everyone, > it's that time of the year again: August will be an election month, and a > Secretary seat (mine!) is expiring, and we need to fill it again. > > For

Re: [VOTE][CC] Errata bylaw update

+1 On Thu, Jul 9, 2020, 03:46 Alessandro Lai 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,

Re: [VOTE][CC] TYPO3 Membership vote

+1 On Fri, Jul 3, 2020, 02:16 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 >

Re: PSR Evolution, PSR-13, and nuance

A lengthy Slack discussion brought us to the thoughts that: * both the *string* typehint and the *static* return type issues should make us wait until *PHP8* to incorporate those changes in the PSR interfaces * at a minimum, in PHP7, this would mean doing the previously proposed typehint

Re: PSR Evolution, PSR-13, and nuance

I'll second Korvin's pair of "BC" choices. CRB On Friday, March 6, 2020 at 7:17:26 PM UTC-6, Korvin Szanto wrote: > > > > On Mon, Mar 2, 2020 at 9:00 AM Matthew Weier O'Phinney < > mweiero...@gmail.com > wrote: > >> >> >> On Sun, Feb 23, 2020 at 1:58 PM Larry Garfield > > wrote: >> >>> OK, this

Re: Easy object based relational php database system that saves data to files only needing 1 file (the library php file)

You continue to send more emails on a topic not relevant for this forum, even after being told it is not relevant. This moves from being incorrect behavior to being unwelcome behavior. Repeated, unwelcome emails are spam. Developers that are interested in libraries **know how to search for

Re: [VOTE] Core Committee Election

1. Enrico Zimuel 2. Massimiliano Arione 3. Korvin Szanto 4. Chris Tankersley 5. Ben Edmunds On Fri, Jan 10, 2020, 02:42 Alessandro Lai wrote: > Hello everyone, > as specified in the previous thread ( > https://groups.google.com/d/topic/php-fig/te-IAmuZte0/discussion), > yesterday at

Re: [VOTE][PROJECTS][BYLAW] PSR evolution

Ah, then ignore my PEAR vote as well... CRB On Wed, Nov 13, 2019, 03:11 Alessandro Lai wrote: > Matthew's and Matteo's votes are to be ignored, since they already voted > as CC members. > > Il giorno mercoledì 13 novembre 2019 10:05:16 UTC+1, Matteo Beccati ha > scritto: >> >> +1 from Revive

Re: [VOTE][PROJECTS][BYLAW] PSR evolution

+1 from PEAR On Mon, Nov 11, 2019, 03:49 Alessandro Lai wrote: > Hello everyone, > after a long review phase of my PR and multiple fixes and amendments, I > think it's now ready: > > https://github.com/php-fig/fig-standards/pull/1195 > > The PR adds a new document that addresses the issue of

Re: [VOTE][CC][BYLAW] PSR evolution

+1 On Mon, Nov 11, 2019, 03:48 Alessandro Lai wrote: > Hello everyone, > after a long review phase of my PR and multiple fixes and amendments, I > think it's now ready: > > https://github.com/php-fig/fig-standards/pull/1195 > > The PR adds a new document that addresses the issue of upgrading

Re: A question about PSR-12

et/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 >> wro

Re: A question about PSR-12

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 |

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

+1 On Mon, Aug 5, 2019, 10:53 Samantha Quiñones wrote: > +1 > > Very exciting stuff! > > -- > 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 >

Re: [VOTE] Core Committee Election

>From PEAR: 1. Matthew Weier O'Phinney 2. Larry Garfield 3. Woody Gilk 4. Matteo Beccati 5. Benni Mack 6. Beau Simensen 7. Adam Englander CRB *about.me/ashnazg * On Sun, May 5, 2019 at 4:48 PM Alessandro Lai wrote: > Hello everyone, > as

Re: [INTERNAL] Core Committee & Secretary nominations open

I nominate Sara Goleman for another CC term, if she's willing. CRB -- 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: [INTERNAL] Core Committee & Secretary nominations open

I nominate Margaret Staples for another Secretary term, if she's willing. CRB On Mon, Apr 8, 2019, 05:56 Alessandro Lai wrote: > Hello everyone, > May is approaching, and since it's the designated month for the next > election cycle, we need to get started on nominations! > > This time we have

Re: PSR-19. inline @see tag

Correct... things were being pared out of the doc initially, in an attempt to get consensus on a minimum baseline of items. Restoring some things would follow, as well as potential new things. CRB On Thu, Apr 18, 2019, 14:55 Joe T. wrote: > Hopefully this is just part of the early draft

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

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

Re: [REVIEW] PSR-14 Event Dispatcher

LGTM... my only feedback was my corrections PR -- https://github.com/php-fig/fig-standards/pull/1149 I'm also good with both of these being applied: https://github.com/php-fig/fig-standards/pull/1152 https://github.com/php-fig/fig-standards/pull/1153 CRB *about.me/ashnazg

Re: Proposal: Adopt Code Manifesto

Looking over both the manifesto and the covenant, I didn't really notice anything that would conflict between the two, if we wanted to simply include *both*... doing so would just be presenting an intersection of their requirements. Is that too much verbiage overall? Maybe just link to both,

Re: [PSR-5][PSR-19] Is there a way to annotate interface that acts as iterator over some type?

Yes, it needs generics syntax, making it currently intentionally > out-of-scope. > If you don't mind ugly hacks with unclear semantics that may stop working > in the future, you can also use `iterable|User[]`. > > > On Saturday, December 8, 2018 at 9:44:14 PM UTC+1, Chuck

Re: Test dependencies in the psr/log package??

At first glance, I think I'm good with moving this out to a log-util package, with perhaps a bump to v1.2. Adjusting testcases has never really urged me into being concerned about versioning, at least when working in my packages. The BC extent of anyone actually depending on these for their own

Re: [PSR-5][PSR-19] Is there a way to annotate interface that acts as iterator over some type?

rry Garfield > wrote: > >> On Monday, November 12, 2018 10:06:08 AM CST Chuck Burgess wrote: >> > So here we do indeed have a special IDE implementation to try to deal >> with >> > the OP's kind of use case. >> > >> > Again, I can't envision a more

Re: [PSR-19] Multiline descriptions for @property and @method

Something I'd highlight is that the main discussion here revolves around the specific Description portion of tags, whereas Jan's PR example talks about multi-lining the Type portion, which is something I don't recall ever coming across before. -1 from me on allowing for multi-line Types... this

Re: PSR-19 Prevent PHPDoc inheritance

I'm -1 on this... it seems too edge casey to me to come up with a new complex way to handle it. CRB *about.me/ashnazg * On Wed, Nov 28, 2018 at 11:44 AM Miguel Rosales wrote: > (I think I've sent this message to 3 wrong places now - trying again... 臘) > > Personally, I

Re: PSR-19 @triggers tag

I'm accustomed to seeing such old-style error behavior wrapped by exceptions as much as possible, so I'm -1 on the idea. Working Group / others, thoughts? CRB *about.me/ashnazg * On Mon, Nov 26, 2018 at 5:00 AM Magnar Ovedal Myrtveit wrote: > Would it be interesting

Re: [PSR-5] Intersection Types

Yep... that's why I like Larry's suggestion to apply & before | when both are used. CRB On Fri, Nov 23, 2018, 09:55 Matthew Brown One problem with allowing just one of & or | > > The type \Mockery\MockInterface&\Foo\Bar|null should be valid IMO > > On Nov 21, 2018, at 7:44 AM,

Re: [PSR-5] Intersection Types

t these two Type Operators into the >> language, it seems likely to me that the Operators chosen will be `|` and >> `&` if they do ever get in. As such, I'm personally good with the choice >> of `&` for Intersection Operator for Typing in Tags. >> >>

Re: [PSR-19] Multiline descriptions for @property and @method

plicit in the standard, leaves no room for misinterpretation on > whether it is the expected result or not. > > _marcos > > Em qui, 15 de nov de 2018 às 12:44, Chuck Burgess > escreveu: > >> I don't know that I remember ever encountering any Description piece, >>

Re: [PSR-19] Multiline descriptions for @property and @method

I don't know that I remember ever encountering any Description piece, whether for DocBlock overall or individual Tags, where multiline was prohibited. The only arguments I've ever seen regarding multiline Tag Descriptions was about indenting the subsequent lines. Let me know if you see any

Re: [PSR-19] Class and methods links

same that JavaDocs adopts. > > - Marcos > > On Thursday, November 15, 2018 at 12:22:21 PM UTC-2, Chuck Burgess wrote: >> >> Yes, I plan to reintroduce that. The current draft has aspects to it that >> date way back to efforts in phpDocumentor to deprecate some things,

Re: [PSR-19] Class and methods links

Yes, I plan to reintroduce that. The current draft has aspects to it that date way back to efforts in phpDocumentor to deprecate some things, including the @link tag completely. I'm guiding the Working Group through reviews of individual tags right now, and already have this topic as a point to

Re: [PSR-5][PSR-19] Is there a way to annotate interface that acts as iterator over some type?

Things[] $things >> */ >> function do_stuff(iterable $things) { >> // ... >> } >> >> The docblock here technically says "$things is an array of Thing >> objects", >> whereas the type declaration says "$things is an iterable that

Re: [PSR-5][PSR-19] Is there a way to annotate interface that acts as iterator over some type?

... > } > > The docblock here technically says "$things is an array of Thing objects", > whereas the type declaration says "$things is an iterable that produces > Thing > objects". > > What should the @param statement be so that it matches the actual code? &g

Re: [PSR-5] Intersection Types

equires some more work... > > > Regards, Alex > > > > On Sat, Nov 10, 2018 at 12:14 AM Matthew Brown > wrote: > >> I agree - I don’t think we want to encourage types that expand into >> monstrosities once the brackets have been evaluated out. Better to disa

Re: [PSR-5][PSR-19] Is there a way to annotate interface that acts as iterator over some type?

; iterable. (I'm really big on iterables these days, as anyone who follows > my > blog has noticed.) > > --Larry Garfield > > On Thursday, November 8, 2018 1:18:49 PM CST Chuck Burgess wrote: > > Revisiting this, I'm leaning towards there *not* being a way to > accom

Re: [PSR-5] Intersection Types

itself is the way to madness. :-) > > --Larry Garfield > > On Thursday, November 8, 2018 12:52:18 PM CST Chuck Burgess wrote: > > Previous replies indicate that whitespace around operators is perfectly > > acceptable, so that seems resolved. > > > > What about the is

Re: [PSR-5] Nullable type shorthand in PHPDoc (e.g. `@return ?string`)

I think I would argue that this example is not quite the same thing as a Nullable Type. I see the Nullable Type as a special case involving nulls, but not as *every* case involving nulls. I see it as a method signature type hint equivalent of `AnyClass|null`, so that the *signature* can still

Re: [PSR-19] Working Group Plan

ithub.com/php-fig/fig-standards/blob/master/proposed/phpdoc-tags.md#57-global [6] -- https://github.com/php-fig/fig-standards/blob/master/proposed/phpdoc-tags.md#59-license On Wed, Oct 31, 2018 at 12:56 PM Chuck Burgess wrote: > Ok, Working Group, let's start small... > > I've gone throu

Re: [PSR-5] Nullable type shorthand in PHPDoc (e.g. `@return ?string`)

'm leaning towards just saying that a simple "?" at the beginning is fully enough for the Nullable Type use case. CRB On Tuesday, October 16, 2018 at 7:54:17 AM UTC-5, Chuck Burgess wrote: > > On Tuesday, October 16, 2018 at 2:26:51 AM UTC-5, Jan Schneider wrote: >> >&

Re: [PSR-5] Intersection Types

bility of one Type being listed multiple times: @return A & C | B & C Or should they be equal precedence, needing parentheses to enforce order: @return (A | B) & C CRB On Tuesday, October 23, 2018 at 8:09:19 AM UTC-5, Chuck Burgess wrote: > > Having both operators at dif

Re: [PSR-5] Summary

and.me > > > On Mon, Oct 29, 2018 at 3:10 PM Chuck Burgess > wrote: > >> Yes guys, I understand you both. My comments are directed at the angle >> of discussion that the spec *should* **require** periods. My argument is >> that they don't need to be expli

Re: [PSR-5][PSR-19] Standard for describing properties with the @var tag

Thanks for the thread, Andrew. I've added to my TODO notes for the @var Tag that an example of a full DocBlock needs to be the basic example (like your first example), with the one-line DocBlock variant being an allowed alternative syntax. More generally addressing your question for the One True

[PSR-19] Working Group Plan

Ok, Working Group, let's start small... I've gone through the tag catalog (phpdoc-tags.md), and made notes on each tag as it is *currently* shown in the catalog. I see these tags as being perfectly fine, needing no changes: api [1], author [2], copyright [3], todo [4]. I'd like the group to

[PSR-5][PSR-19] Weekly Update - 2018-10-31

-it & look-at-it & ( ok-it | slack-about-it ). *Again, this is strictly to get the drafts up to a minimum baseline of content and consensus. Aside from contributing, if you have feedback on the structure or content of this update email, please let me know. Chuck Burgess, Editor *about.me/

Re: [PSR-5] Summary

gt;> all! >> >> If you ask me, I'd require full stops, but I do see how it may be >> overkill - what I do think is at least the examples should include them, as >> a suggestion for best practices, imho anyway. >> >> El lunes, 29 de octubre de 2018, 17:45:36

  1   2   >