Re: [VOTE] Membership Application: pimcore
Abstain, Horde. Zitat von Lukas Kahwe Smith : Aloha, So given that there didn’t see to be any opposition (then again also no support by-side me) for the adoption of pimcore in the original thread requesting for addition to the member list, I am not calling for a formal vote on the matter. The intended representative is Bernhard Rusch who is part of the core team. Voting members only, just +1/-1/abstain please. For reference here is the link to said original thread: https://groups.google.com/d/msg/php-fig/7qcqblUe2hk/Gtl_0gG1EgAJ regards, Lukas Kahwe Smith sm...@pooteeweet.org PS: Here for quick reference the initial email: Hi, I would like to submit my application for membership on behalf of Pimcore. Pimcore is an open source CMF for building highly customized websites and applications. Link: http://pimcore.org/ On Github: https://github.com/pimcore/pimcore A little bit about myself: My name is Bernhard Rusch, I'm working with PHP since 14 years and worked with many different products and frameworks during that time, mainly in the area of content management and ecommerce. We started pimcore 6 years ago with the mission to make enterprise web content management easier for developers and editors. Thank you for your consideration. Bernhard Rusch https://github.com/brusch -- Jan Schneider The Horde Project http://www.horde.org/ -- 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/20160729091727.Horde.8PNSSEDLSBaLAKT_niTa8Hd%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: FIG 3.0 (Including a TL;DR Summary)
Zitat von Michael Cullum : Hi all, A vote for FIG 3.0 is [potentially/hopefully] getting closer and one big thing people had been asking for is a TL;DR of FIG 3.0 to give an overview of the new structure and processes. The last couple of days I've been working with Larry on compressing it into 3 graphics and a post that, according to medium, takes 3 minutes or less to read. I'd invite to you all to have a read of that version, and if that wets your appetite for more, then of course I'd suggest you take a read of the full bylaws (after all, that is what will actually be being voted upon). I'd love to see some active discussion (or if you are just in general agreement about it, some +1s) about this over the next couple of weeks as discussion has been quite quiet on it over the last few weeks on the mailing list; however what I've heard from people at conferences and elsewhere has been a good positive reception. Assuming there are no major objections and we don't end up making major changes we'd like to see this going to a vote on the 17th August, to end on the 31st August. The CC elections would then be able to take place in September. Without further comment, THE TL;DR OF FIG 3.0: HTTP://BIT.LY/FIG-3-0 Many thanks, Michael & Larry (Note: I am not posting this as a secretary but as a co-author of FIG 3.0 in line with my declared conflict of interest) I like this direction a lot, especially the vote "burden" being delegated to WGs that actually know what they talk and vote about. I don't think it would still be required to have the whole FIG resp. all member projects having a final vote. This is similar to the RFC process where WGs are formed to work on a specific Draft, sometimes being a subset of a larger interest group herding related RFCs of a certain technical area. Jan - Jan Schneider The Horde Project http://www.horde.org/ -- 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/20160809074932.Horde.yR-DUx0BYBpH4BFexHt3pVI%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: Alternative to FIG 3.0: Encourage *-interop projects
Zitat von Paul Jones : Dear Voting Members, There is another way to solve the problems listed in the [FIG 3.0 summary][1]: formally encourage the creation of a *-interop project as a prerequisite to a FIG entrance vote. (Look to container-interop and async-interop as examples.) IMO the WGs are the formal creation of what used to be interop projects. Lessons learned from these projects have sure been taking into account when creating the ideas of working groups. At least that's my personal impression. * * * Point by point from the FIG 3.0 tl;dr: Everyone has equal say on FIG PSRs, no matter their expertise or their project’s relevance in the PSR’s problem space A *-interop project concentrates on its particular problem, and can invite (or draw the attention of) those who have relevant expertise. Both container-interop and async-interop were able to this successfully. There are lots of clever awesome people involved in the FIG who are not project representatives A *-interop project need not be limited to only project representatives. It can accept (or refuse) anyone it wants. Member projects find it difficult to engage in everything going on in the FIG Interested parties can enagage in as many, or as few, *-interop projects as they like. There is an ongoing question if the FIG produces PSRs for member projects or for the wider community; especially when the wider community pays it so much attention due to its de-facto status as ‘the php standards body’. Each *-interop project can define for itself the audience it addresses. Besides that latter, all this applies to the FIG 3.0 WGs too. And I don't think that each group should define its own audience. For consistency and relevance reasons, this should be defined by the FIG as a whole. If a WG considers the audience too narrow for their purposes, they can start a discussion to broaden the audience on the FIG level. * * * This has several advantages over the FIG 3.0 approach. - fewer rules changes (perhaps only one!) This is not necessarily an advantage on its own. - less bureaucracy While I consider this generally a good idea, I would also say that more rules make some discussions less necessary. Or even meaningful. Also, for a standardization entity, a very formal approach is making the outcome more transparent and confident. - less centralization This is also achieved by the FIG 3.0 proposal. - reduced hierarchy Didn't work in the past where the whole FIG body discussed and decided everything. I suggest we see more hierarchy as distributed responsibility instead. - fewer committees See above. - more flexibility Not necessarily a good goal for a standardization body. - greater openness I don't see this. Each *-interop gets to operate in the way it likes, according to its own project members. Again, not necessarily good in standardization processes. Who trusts a standardization group if the groups processes aren't standardized too? Each *-interop can work through its ideas among a smaller set of interested participants, perhaps with implementation trials, without having the pressure of "being a standard" from the outset. Once a *-interop project feels it has solved its particular problem, it can petition for FIG entrance under current FIG bylaws. Like the WG. If there is more than one *-interop groups tackling the same problem in different ways, FIG can pick from the different groups, or ask that they merge their efforts before entrance. This shouldn't even happen right from the start. That's why the CC is a good idea. FIG can also see how broadly the work of *-interop group has been accepted, providing real-world information as to the value of the work before the entrance vote. * * * Please consider this the opening of the 2-week discussion that occurs prior to a vote; of course, it may go on longer than that. [1]: https://medium.com/@michaelcullumuk/fig-3-0-91dbfd21c93b#.4fhp3srq0 -- Paul M. Jones http://paul-m-jones.com -- Jan Schneider The Horde Project http://www.horde.org/ -- 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/20160809080550.Horde.9sAhhSqf3Qh0QSo_kW5u7qU%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE] [Bylaw Amendment] Do not require interface suffix on future PSR Interfaces
-1 from Horde Zitat von Michael Cullum : Hi all, The PSR-11 Editors have requested we open this vote for them as they are unable to do so not being voting members. STATUS QUO: The bylaw states that all interfaces in PSRs published by the PHP FIG must have the interface name suffix of 'Interface' e.g. `LoggerInterface` CHANGE: The proposed change is that we no longer require that interfaces are suffixed by 'Interface' so `ContainerInterface` would become `Container` Arguments for/against and [two week] DISCUSSION: http://bit.ly/interface-suffix-discussion PULL REQUEST FOR BYLAW CHANGE: http://bit.ly/interface-suffix-pr Note: This will only affect future PSR production (of PSRs in draft or not yet through an entrance vote) so will not break or change any current PSRs. It is also not a standard or recommendation for the PHP community or member projects, but an internal bylaw on how we name interfaces in our own interfaces in PSRs. Voting will close in two weeks on the 18th September at 23:59 UTC. Voting is available to voting members and may be cast as +1 (For), -1 (Against) or 0 (Abstain). -- Many thanks, Michael Cullum -- 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/CAAqcDMh4JSN1Opsiam8GgjXc1vsTfSuFJ7fEJvtoRoxBxRv_xQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. - Jan Schneider The Horde Project http://www.horde.org/ -- 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/20160905090428.Horde.HNs4O1bx44LXOTU7_Xv1MOS%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE] "FIG 3.0" Bylaw amendments (Take 2)
Though I question one or two phrases +1 from Horde. Zitat von Larry Garfield : I hereby open a vote for the following bylaw changes, colloquially known as "FIG 3.0". I'm fairly certain anything that needs to be said has been said by now by all parties. https://github.com/php-fig/fig-standards/pull/752 The vote will be open for 2 weeks, closing on 30 September 2016. As usual, the vote is open to voting representatives only and is a simple +1/-1 vote. --Larry Garfield -- Jan Schneider The Horde Project http://www.horde.org/ -- 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/20160920094323.Horde.RYVugLRGyVluNgYrhIc1-Pk%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: [Important] [Internals] All projects must declare intention to remain members
Horde remains. Zitat von Michael Cullum : As per the FIG 3.0 bylaws, all member projects must, between the 1st October and 31st October, declare they wish to remain a member project of the FIG. If you don't wish to remain, then it would be useful for you to also state this so we don't chase you up on it. Project reps, simply reply to this topic if you wish to remain. I'd note that with FIG 3.0; there is much less of a burden/requirement for project reps to put time into FIG efforts, but of course remaining ensures you can still have a main seat at the table in deciding who steers the FIG and assurance to be involved in any PSRs that are relevant to your project and you can of course continue to be as actively involved (or more so) than presently too. Should any old member projects who have previously left wish to re-join the FIG due to the new lower requirement on activity, I imagine in January there will be a combined vote for new member projects. Many thanks, The 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/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. --------- Jan Schneider The Horde Project http://www.horde.org/ -- 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/20161004072800.Horde.7ogUjtAaunO5y-XBjf2FWHx%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE][Accept] PSR-13: Link Definition Interfaces
+1 from Horde Zitat von Matthew Weier O'Phinney : 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. -- Matthew Weier O'Phinney mweierophin...@gmail.com https://mwop.net/ -- Jan Schneider The Horde Project http://www.horde.org/ -- 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/20161102130625.Horde.4DopeqHoXlQ1eBAQiCl55Sq%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: [Internals][FIG 3.0] Extending Nomination Period & Delaying FIG 3.0 Transition
+1 from Horde. Zitat von Michael Cullum : Answering this required me working backwards so I just did the full timetable. The new FIG 3.0 transition timetable would be as follows: 1st November: CC Nominations open 7TH DECEMBER: CC NOMINATIONS CLOSE (Initial nominations, people can accept nominations after this so long as voting hasn't started) 9TH DECEMBER: CC ELECTION VOTING BEGINS 23RD DECEMBER: CC VOTING ENDS 24th December: CC results announced 25th December: CC takes post 16th January: Recommended date for PSRs to have working groups fully formed with a CC sponsor 17th January: Latest date for any FIG 2.0 votes to start except acceptance votes 17th January: Latest date for any PSRs to enter review under the old system 31st January: Latest date for any PSRs to start approval votes under the old system 31st January: Final deadline for PSRs to have full working groups formed with a CC sponsor 1ST FEBRUARY: ALL VOTES AND ACTIONS TAKE PLACE UNDER NEW SYSTEM; FULL TRANSITION 14th February: Latest possible date for any FIG 2.0 approval votes to have finished by 28th February: Deadline for any PSRs which entered review before the 17th December to form a Working Group with a CC sponsor if they failed their approval vote/didn’t get to their approval vote in time May 2017: Next Secretary and CC election -- Michael C On 9 November 2016 at 12:53, 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/CAAqcDMhOwpMH%3D%3Di5Az41Y_UQhA-so_02k6z2sF6DDjZMAW6a4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. - Jan Schneider The Horde Project http://www.horde.org/ -- 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/20161110113334.Horde.Y86zwXJdOjuAYOqxBH0nxhD%40neo.wg.de. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE][Accept] PSR-11 ContainerInterface
+1 from Horde. Zitat von Matthew Weier O'Phinney : 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! -- Matthew Weier O'Phinney mweierophin...@gmail.com https://mwop.net/ -- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20170201094155.Horde.HeK_JWxcb1xWmbVg8tBlHLk%40neo.fritz.box. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE][CC] Entrance vote for HTTP Client
+1 Zitat von Sara Golemon : Per http://www.php-fig.org/bylaws/psr-workflow/ This is the entrance vote for the HTTP Client PSR Discussion https://github.com/php-http/fig-standards/blob/master/proposed/http-client/http-client-meta.md Sponsor: Sara Golemon Editor: Tobias Nyholm Thanks to PSR-7 we know how HTTP requests and responses ideally look like, but nothing defines how a request should be sent and a response received. A common interface for HTTP client will allow libraries to be decoupled from an implementation such as Guzzle. Voting opens 2017 Aug 3 at 16:00 UTC Voting Closes 2017 Aug 17 at 16:00 UTC Per http://www.php-fig.org/bylaws/voting-protocol/#entrance-vote this vote is for Core Committee members to approve or reject the discussion phase of this proposed PSR. -Sara -- 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/bc288330-b520-4248-b8fb-588e6fd5de09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ----- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20170807071821.Horde.xvGp7wSrOZe_24vMfONNUXt%40neo.fritz.box. For more options, visit https://groups.google.com/d/optout.
Re: PSR for HTTP clients
s.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/0db70a2c-d528-44df-b7f5-62387eb67872%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+u...@googlegroups.com[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAPY1sU_e%2BwDVGGm-3VGZzjNfPUpAyA3Ng6tk04%2BdtLcADMqAwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Cheers, -- Tuomas Humap Software Ltd http://humapsoftware.com Twitter: @humapsoftware LinkedIn: https://www.linkedin.com/company/humap-software-ltd Facebook: http://facebook.com/humapsoftware/ Instagram: @humapsoftware -- 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[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAND7_93GNv9R0_e%3DU-e%2B%3DfGWh%3D99hHR5RtkQb2Nde%2BvaSj5vA%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[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/6ac1a1f0-f62b-42e3-912c-74faa3e28950%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+u...@googlegroups.com[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/f47fa29c-7176-44a5-bd0c-436df87f34a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/php-fig/iFZF6T9L2zA/unsubscribe. To unsubscribe from this group and all its topics, send an email to php-fig+u...@googlegroups.com[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAKiSzdBMhrjab-VzrASmu%2B5audhGt-KEbrsx7TM%2BBSwPgbwmcg%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[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/6383CD29-BA16-4253-91C3-72CBDB2EA9F6%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+u...@googlegroups.com[1]. To post to this group, send email to php...@googlegroups.com[1]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAKiSzdDmRdzeCjWghZSWpeHLskpUg-cq5xu%2B485GoAdyo7-%2BNg%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 v
Re: [VOTE][CC] Entrance vote for PSR-12: Extended Coding Style Guide
+1 from Horde Zitat von 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. --------- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20171020090646.Horde.MlcHA8GiOPhUbwYKnHwCy3a%40neo.fritz.box. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE][Internals] Secretary election
1. Robert Parker 2. Mark Railton from Horde Zitat von Alessandro Lai : 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:[1] WHO CAN VOTE?[1] As specified in the bylaws, ANY PROJECT REPRESENTATIVE OR CORE COMMITTEE MEMBER is eligible to vote on Secretary candidates.[1] WHEN CAN YOU VOTE?[1] Voting will be open UNTIL 26TH JANUARY 23:59 UTC.[1] _HOW TO VOTE_[1] 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] 1. Luke[1] 2. Leia[1] 3. Anakin[1] 4. Rey[1] 5. Padmé[1] 6. Finn[1] 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.[1] Thanks![1] Alessandro Lai[1] PHP-FIG Secretary[1] [1]: STV User-friendly Explanation [1]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/efa147fc-ff7c-4537-9e43-3bb4cf3c5249%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Links: -- [1] http://www.php-fig.org/bylaws/mission-and-structure/#secretaries --------- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20180119192838.Horde.cBfO5mE0hxLfRQ6ZYGoHPdk%40yunosh.horde.org. For more options, visit https://groups.google.com/d/optout.
Re: PSR for Mailer?
ps.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/CAESZFtLSDeMDuYRAJXz8zAYmDN-BQGJUO0X3mDZmkCJwc-rxHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Links: -- [1] http://designcise.com [2] https://github.com/yiisoft/yii2-framework/tree/master/mail [3] - Jan Schneider The Horde Project https://www.horde.org/ -- 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/20180802071047.Horde.S-S6FjVVl5jkAu5sNsxluG-%40yunosh.horde.org. For more options, visit https://groups.google.com/d/optout.
Re: [PSR-5] Variadic Parameters
Agreed, feels like the most natural notation. Zitat von Robbie Averill : Hi Chuck, Seeing as $intervals is an array when accessed directly from within the method (via $intervals), it seems to me that @param DateInterval[] ...$intervals would make sense. Cheers, Robbie On Mon, 15 Oct 2018 at 22:46, Chuck Burgess wrote: The current draft does not contain references to or examples of variadic parameters, since they entered the PHP language after the early PSR-5 drafts were done. Assuming that folks agree that they should be represented in the spec, this email thread opens the discussion on the syntax to use. Previous discussion exists here (https://github.com/phpDocumentor/fig-standards/issues/121), for background reading. The key question on syntax is not whether to include "..." in the spec, but with whether or not "[]" should also be shown: * @param DateInterval[] ...$intervals vs * @param DateInterval ...$intervals Both are meant to imply that the variable number of parameters passed can be expected to be found inside an $intervals array of DateInterval objects. Please reply to this thread with thoughts on this... 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 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/7176991b-5b4e-4d88-adeb-9ccd3189f7a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Robbie Averill | Senior Developer 04 978 7330 http://silverstripe.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/CANv6TC1XyHBVnj1siXkQcHH3SNahVrsRBLSf7XTy1v2Bmh6T5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. - Jan Schneider The Horde Project https://www.horde.org/ -- 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/20181016072251.Horde.0sGaOFbxDIUNbTJMKWmTBx4%40yunosh.horde.org. For more options, visit https://groups.google.com/d/optout.
Re: [PSR-5] Variadic Parameters
That would be @param DateInterval[][] ...$intervals then.
Zitat von Stefano Torresi :
Hey list,
what if one wanted to hint to a varable number of arrays of
DateInterval?
e.g. `func(array ...$intervals) {}`
Isn't this what `@param DateInterval[] ...$intervals` should
actually be used for?
Cheers
Il Lun 15 Ott 2018, 23:12 Woody Gilk
ha scritto:
I agree with Chuck's analysis, as it follows closely with how the code
is written.
--
Woody Gilk
https://shadowhand.me
On Mon, Oct 15, 2018 at 3:55 PM Robbie Averill
wrote:
Hi Chuck,
Seeing as $intervals is an array when accessed directly from
within the method (via $intervals), it seems to me that @param
DateInterval[] ...$intervals would make sense.
Cheers,
Robbie
On Mon, 15 Oct 2018 at 22:46, Chuck Burgess wrote:
The current draft does not contain references to or examples of
variadic parameters, since they entered the PHP language after
the early PSR-5 drafts were done. Assuming that folks agree that
they should be represented in the spec, this email thread opens
the discussion on the syntax to use.
Previous discussion exists here
(https://github.com/phpDocumentor/fig-standards/issues/121), for
background reading.
The key question on syntax is not whether to include "..." in the
spec, but with whether or not "[]" should also be shown:
* @param DateInterval[] ...$intervals
vs
* @param DateInterval ...$intervals
Both are meant to imply that the variable number of parameters
passed can be expected to be found inside an $intervals array of
DateInterval objects.
Please reply to this thread with thoughts on this...
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 php-fig+unsubscr...@googlegroups.com[1].
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/7176991b-5b4e-4d88-adeb-9ccd3189f7a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Robbie Averill | Senior Developer
04 978 7330
http://silverstripe.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[1].
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/CANv6TC1XyHBVnj1siXkQcHH3SNahVrsRBLSf7XTy1v2Bmh6T5g%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[1].
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/CAGOJM6%2BG9_Pwf-NWE6JTBh1cJ%3Dqx3_3vLYU0NrBFTgAh%2BXSGqA%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/CAFojS1tMJGeXmzeo5_jVrSpt2UZu93iBpN195hbYKzoNHtHQxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Links:
--
[1] mailto:php-fig%2bunsubscr...@googlegroups.com
-
Jan Schneider
The Horde Project
https://www.horde.org/
--
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/20181016072341.Horde.tiuPVdy5rkvZXMmPNIzZYiY%40yunosh.horde.org.
For more options, visit https://groups.google.com/d/optout.
Re: [PSR-5] Nullable type shorthand in PHPDoc (e.g. `@return ?string`)
Zitat von Tyson Andre : Earlier discussion about including this in PSR-5 is found in https://github.com/phpDocumentor/fig-standards/issues/153 , I'm re-opening the discussion here. This shorthand isn't part of the PSR-5 draft : https://github.com/phpDocumentor/fig-standards/blob/master/proposed/phpdoc.md#abnf Reasons: - Nullable types are part of the language syntax for real signatures, so adding this in PHPDoc makes some sense - @return ?string is shorter than @return string|null - Many static analyzers support this syntax in PHPDoc already (Phan/Psalm/PHPStan (and phpdocumentor3 will?)). Questions that were already brought up: - A canonical way to represent the union type after parsing it in union types - ?int|string, ?(int|string), ?int|?string, int|string|null are equivalent, but which should be preferred for the output of tools (not sure if that would need to be part of the standard) - Operator precedence (e.g. ?string[]) - I suggested treating that as ?(string[]), others suggested forbidding ambiguous cases and forcing phpdoc authors to add brackets - either explicitly write (?string)[] or ?(string[]). For the sake of unambiguousity I'd prefer the latter, i.e. forcing to use brackets. This would also solve the first question. --------- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20181016072643.Horde.mLp9DEQavbMCoO3TNj3ksFx%40yunosh.horde.org. For more options, visit https://groups.google.com/d/optout.
Re: Code style for php [] array arguments - need advice
+1
Zitat von Joe T. :
For what it's worth...
The requirement for my team is that any time a function call
spans multiple lines, /ALL/ arguments must be split to individual
lines, and any additional formatting for the arguments goes
according to their own rules.
someFunction(
$foo,
$bar,
['short', 'array', 'arg'],
$baz
);
//or
someFunction(
$foo,
$bar,
[
'longer' => 'array',
'with' => 'keys',
'or',
'other',
'mixed up stuff',
],
$baz
);
i find the PSR incredibly frustrating sometimes. It seems it's not
written for readability and consistency (especially to assist young
devs to acclimate quickly), it's written so legacy code authors
won't cry. That's a cynical statement, i suppose, but some of the
rules seem to have no rationale behind them.
-jlt
On Friday, 26 October 2018 12:42:30 UTC-4, Miguel Rosales wrote:
Sorry I'm new to the group so I'm not 100% aware of the process,
but the site says PSR-12 is under draft, so I guess things can
still be discussed...
I was going to open a new topic about this but found this one,
and just wanted to say I agree with the previous message - I don't
like this part of the recommendation:
A single argument being split across multiple lines (as might be
the case with an anonymous function or array) does not constitute
splitting the argument list itself.
somefunction($foo, $bar, [
// ...
], $baz);
$app->get('/hello/{name}', function ($name) use ($app) {
return 'Hello ' . $app->escape($name);
});
I know many developers are used this in some scenarios, but
particularly when there are many arguments it gets lets readable.
Also I assume that implementation of auto-formatting allowing
this would be quite trickier (in fact for example PhpStorm doesn't
support this atm).
So, is this something that has been decided already or is it
open to changes?
El sábado, 20 de enero de 2018, 17:34:26 (UTC), Joe T. escribió:
The short-style syntax does make arrays much more readable, as it
no longer makes them look like function calls.
However, the rule you're referencing is for when you are
keeping arguments on the *same* line. It permits for splitting an
array in that signature to multiple lines, and continuing the
signature after the end of the multi-line array.
i see now your first example was following the guideline of
the format from your second message. Your right, technically that
does comply with the standard. When you start the signature on the
same line as the opening "(", all successive arguments after
should continue on the line where the previous argument ends. But
hopefully you can see how muddled that pattern is for readability.
It's hard to tell where the arrays begin or end, particularly in
context of being function arguments. So many commas and brackets...
Honestly, i dislike the standard's allowance of the style in
your second message. It seems very awkward and visually clunky to
me. But i don't have a vote in accepting the standard, and came to
the group a bit late to make a case for changing it. For me (and
the guide my team uses), any time any argument is split to
multiple lines, the whole signature should follow the multi-line
signature rule.
Ultimately, i think the goal is readable & maintainable
code, so when two versions are technically legal, let that
objective be the deciding factor.
Hope that helps.
-jlt
--
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/2083e29f-f66e-4769-a6fb-f6b9dc710586%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-
Jan Schneider
The Horde Project
https://www.horde.org/
--
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/20181029083739.Horde.pGZ_h14bCR3r0iOf_SV465s%40yunosh.horde.org.
For more options, visit https://groups.google.com/d/optout.
Re: [VOTE] Core Committee Election
Horde: - Matthew - Larry - Beau - Matteo - Woody Zitat von Alessandro Lai : Hello everyone, as specified in the previous thread (https://groups.google.com/d/topic/php-fig/SSGn1VJtOJs/discussion), 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. 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 2020, due to Lukas 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 seven nominations (listed in chronological order of nomination): - Woody Gilk https://groups.google.com/d/topic/php-fig/DaoLQAiykpc/discussion - Larry Garfield https://groups.google.com/d/topic/php-fig/HqtrPuUI_YQ/discussion - Adam Englander https://groups.google.com/d/topic/php-fig/3TjKW8MmBks/discussion - Matthew Weier O'Phinney https://groups.google.com/d/topic/php-fig/PAnOZqE4QiQ/discussion - Matteo Beccati https://groups.google.com/d/topic/php-fig/Mahn59nAmbU/discussion - Beau Simensen https://groups.google.com/d/topic/php-fig/v1cPGmMT430/discussion - Benni Mack https://groups.google.com/d/topic/php-fig/wVIhtZNVgmM/discussion 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 May 19th 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 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/9e1624fa-b968-43c6-923f-5d507774703e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. - Jan Schneider The Horde Project https://www.horde.org/ -- 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/20190520084153.Horde.CUDJbzwRagmTy-aioF4AjOs%40yunosh.horde.org. For more options, visit https://groups.google.com/d/optout.
Re: [VOTE][PROJECTS][BYLAW] PSR evolution
+1 from Horde Zitat von Alessandro Lai : 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 the code of a PSR to leverage new language features. I started working on this draft after a long discussion here on the ML (https://groups.google.com/d/topic/php-fig/OyC3plRYhqg/discussion), after that the issue surfaced many times on our communication channels. The PR has been reviewed by multiple parties, and I consider it now ready to be put to a vote. So I hereby call a bylaw vote, following following our Voting Protocol: https://www.php-fig.org/bylaws/voting-protocol/ THIS THREAD IS FOR VOTES OF PROJECT REPRESENTATIVES ONLY; any other message or "vote" will be ignored. As always, you can vote with a +1, +0 or -1, you will have a period of two weeks to cast your vote, so this will be closed after 23:59:59 UTC of Monday 25th. There is no quorum for this vote, and a 2/3 majority is required for it to pass. Thank you. -- 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/fc771d51-13e8-411f-8b0e-eae400f92897%40googlegroups.com. --------- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20191117214356.Horde.UmGaMBdZtxQ7AwlDE3GBoKF%40neo.fritz.box.
Re: [VOTE] Core Committee Election
* Korvin Szanto * Chris Tankersley * Enrico Zimuel * Massimiliano Arione * Ben Edmunds Zitat von Alessandro Lai : Hello everyone, as specified in the previous thread (https://groups.google.com/d/topic/php-fig/te-IAmuZte0/discussion), yesterday at midnight UTC 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 4 SPOTS ON THE CORE COMMITTEE up for reelection; we also have one full-term spot for secretary but, 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): - Enrico Zimuel: https://groups.google.com/d/topic/php-fig/G9O263am5Bs/discussion - Massimiliano Arione: https://groups.google.com/d/topic/php-fig/CXS_djlzI6E/discussion - Korvin Szanto: https://groups.google.com/d/topic/php-fig/suq1VFu3N8Y/discussion - Chris Tankersley: https://groups.google.com/d/topic/php-fig/O-qPhtb3li4/discussion - Ben Edmunds: https://groups.google.com/d/topic/php-fig/xk6cHWzOr6s/discussion 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 PHP-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 January 23rd 23:59: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. 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/c9f56a7f-adf7-4b31-b5a9-65635560d104%40googlegroups.com. - Jan Schneider The Horde Project https://www.horde.org/ -- 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/20200113081513.Horde.JU9xWaGLK-kdG1VKufvz2rO%40yunosh.horde.org.
Re: [VOTE][Projects] TYPO3 Membership vote
+1 from Horde! Zitat von Alessandro Lai : [VOTE][CC] TYPO3 Membership vote 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: 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/82e47db9-d147-4c80-ad03-ccf4599ee09co%40googlegroups.com. ----- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20200703092318.Horde.ksYC8jfvmiFMndgvAAd1aiN%40yunosh.horde.org.
Re: [PSR-13] Type updates
Zitat von Larry Garfield : We previously attempted to upgrade a few PSRs to PHP 7, in stages per bylaw. However, we discovered through experimentation with PSR-13 and others that the upgrades would be a lot easier if we jumped straight to PHP 8, thanks to its more robust type support. (Specifically, string|\Stringable and return static.) PHP 8 is now here, so let's get back to it. Here are the re-upped PSR-13 PRs to add modern typing. This requires a 2/3 CC vote, I believe. Today begins the 2 week discussion period, although since that puts the vote starting smack in the middle of everyone's Christmas holiday I will likely not call the vote to start until early January. There is still the bikeshedding around whether these are 1.1/2.0 or 2.0/3.0, for which I do not have enough energy to really give a damn either way. The vote would be to accept all 3 PRs and tag accordingly. Step 1: https://github.com/php-fig/link/pull/6 Why does only withHref() accept Stringable, and not the other methods with string parameters? 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 -- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20201215164531.Horde.ng4H_VsifHeiprYqqUrM92b%40yunosh.horde.org.
Re: [VOTE][PSR-11] Type Updates
+1 Zitat von Matthew Weier O'Phinney : 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. - Jan Schneider The Horde Project https://www.horde.org/ -- 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/20210226093539.Horde.-ujorvk-x-J7ifbv3KblBQ1%40yunosh.horde.org.
Re: [VOTE][Projects] Bylaw CS update
+1 Zitat von Alessandro Lai : 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/cb74c462-a5ba-4879-943d-4002ef331090n%40googlegroups.com. ----- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20210412070101.Horde.TYulAZbLw6BuAVcTmQdjppr%40yunosh.horde.org.
Re: [VOTE][Projects] AzuraCast Membership vote
+1 from Horde Zitat von Vincent de Lau : 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: 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/67e2255d-a32f-44db-8921-bb95a748199dn%40googlegroups.com. ----- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20210806070818.Horde.SNLxyhrOVAnPOPC8EVzhGNO%40yunosh.horde.org.
Re: [VOTE] Core Committee Election January 2022
Representing Horde: * Korvin Szanto * Chris Tankersley * Ken Guest * Florian Engelhardt Zitat von Vincent de Lau : Hello everyone, Yesterday the nomination period ended, and we got 7 nominations in total, which is great! For the secretary seat, we have one uncontested nomination. For the Core Committee, we have 6 nominations against 4 available seats, so this means that we will be holding a proper election, starting now! The nominees are (in temporal order of nomination): *Korvin Szanto - https://groups.google.com/g/php-fig/c/Rv43KRFOt_A *Navarr Barnier - https://groups.google.com/g/php-fig/c/kAOTuIFB7Eg *Chris Tankersley - https://groups.google.com/g/php-fig/c/xtrwd7o6SOQ *Ken Guest - https://groups.google.com/g/php-fig/c/QtKqPOYZ2HA *Florian Engelhardt - https://groups.google.com/g/php-fig/c/wjxZf1VMzDA *Enrico Zimuel - https://groups.google.com/g/php-fig/c/vA-dFT8lXbM You can find information about the nominees inside the linked nomination thread. 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, the vote for CC members is open to Project Representatives and individuals from the community. To be eligible to vote as an individual, the bylaw established the following threshold:: /"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."/ We will obviously consider Discord in this account; feel free to reach to me or any other secretary to check on the matter. WHEN CAN YOU VOTE? Voting will be open in this thread until January 29th 17:00 UTC. HOW TO VOTE Votes are cast by replying in this thread on the list. For individuals that have not used the mailing list before, please be sure to identify yourself, for instance by including your Discord or Github handle. 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 all 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, secretaries will be announcing the results, and all the newly elected (both CC members and secretary). Thanks, and happy voting! Alessandro Lai and Vincent de Lau 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/22dd11d5-8d4a-46d7-ab77-e291b4e03f49n%40googlegroups.com. --------- Jan Schneider The Horde Project https://www.horde.org/ -- 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/20220124111547.Horde.0arFNRMvwQ1in6jUqg1Ej4y%40yunosh.horde.org.
