+1 from PPI Framework
On Tue, Oct 17, 2023 at 8:50 AM Alex Makarov wrote:
> +1
>
> On Tue, Oct 17, 2023 at 10:49 AM Cees-Jan Kiewiet
> wrote:
>
>> +1 sadly
>>
>> On Mon, 9 Oct 2023 at 17:43, Chris Tankersley
>> wrote:
>>
>>> +1, unfortunately.
>>>
>>> Chris Tankersley
>>>
+1 from PPI Framework
On Tue, Oct 17, 2023 at 8:50 AM Alex Makarov wrote:
> +1
>
> On Tue, Oct 17, 2023 at 10:48 AM Cees-Jan Kiewiet
> wrote:
>
>> +1 sadly
>>
>> On Mon, 9 Oct 2023 at 17:43, Chris Tankersley
>> wrote:
>>
>>> +1, unfortunately.
>>>
>>> Chris Tankersley
>>>
way, there are standard requests, standard
> responses, standard request handling, but no standard for storing data
> between requests, and PHP sessions dont work nicely with PSR 7 response
> objects, so by having a standard we dont need to worry about that anymore.
>
> Amanda.
>
>
Hi Amanda,
Ask yourself. What problem in the community are you solving?
We don't want to make standards for the sake of it.
Are people actively trying to write code in Symfony that doesn't wanna use
Symfony sessions?
Figure out the demand first, validate it, present some info.
I'm not a
Fair play! Sounds like a solid initiative/idea.
On Sun, Jan 16, 2022 at 3:33 AM 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
Voting as the PPI Representative
1. Korvin Szanto
2. Chris Tankersley
3. Ken Guest
4. Enrico Zimuel
5. Florian Engelhardt
6. Navarr Barnier
On Tue, Jan 18, 2022 at 6:02 PM Matthew Weier O'Phinney <
mweierophin...@gmail.com> wrote:
> Voting as the Laminas representative:
>
> 1. Enrico Zimuel
>
On Sat, May 22, 2021 at 1:51 AM Larry Garfield
wrote:
> Greetings, FIGlets. (What does one call a FIG-involved person, anyway?
> FIGlet? FIGment?)
>
We're definitely FIGlet's ;-) Spiderfig, spiderdig, codes whatever a
spiderfig codes.
>
> As you may be aware, PHP 8.1 is going to include
On Wed, 16 Dec 2020, 16:41 Andreas Heigl, wrote:
> Am 16.12.20 um 17:38 schrieb Ben Ramsey:
> > My $0.02 as one who lurks on the mailing lists:
> >
> > Chat programs, whether it be Slack or Discord or Rocket.Chat or
> > Mattermost or whatever, are inherently bad at transparency, which is
> >
Saeed, this question is out of scope.
Your question/conversation is better suited for reddit.
https://www.reddit.com/r/PHP/
On Tue, 4 Feb 2020, 11:46 saeed jahanakbari,
wrote:
> We know that composer adds file dependencies and we can also save our
> custom dependencies to composer.json file.
1. Chris Tankersley
2. Korvin Szanto
3. Enrico Zimuel
4. Ben Edmunds
5. Massimiliano Arione
On Fri, 10 Jan 2020, 13:43 Woody Gilk, wrote:
> 1. Chris Tankersley
> 2. Korvin Szanto
> 3. Ben Edmunds
> 4. Enrico Zimuel
> 5. Massimiliano Arione
> --
> Woody Gilk
> https://www.shadowhand.com
>
>
> On
As per last year, I'm still keen to continue to contribute to this.
I have already implemented and solved this situation for the laravel
project.
I gave my client container interop and interoperable service providers and
respective config, and brought this to laravel projects
This was to share
Hey Gabriel,
Thanks for showing an interest in PSR-6, and for making PRs in the first
place! All community feedback is welcomed.
I noticed Larry commented on github already.
Although we don't like to change a spec once published, for adding new
features, this is actually a good addition which
Welcome Anton
On Tue, 15 May 2018, 18:04 Ben Marks, wrote:
> Hi all,
>
> Effective immediately the representative for Magento will be Anton Kril (
> anton.k...@gmail.com), who is Magento's Director of Architecture. His
> knowledge and experience make him a much better fit
Hi Alice,
It's recommended not to throw \Exception but throw your own cache exception
class, which implement's PSR-16's CacheException.
"""
use Psr\SimpleCache\CacheException;
class MyProjectsCacheException extends Exception implements CacheException
"""
This way you'll be able to continue to
I will talk to Jordi about it and get back to you. Cheers
On 9 Nov 2017 19:46, "Pol Dellaiera" wrote:
> In the meantime, I've created a PR for php-fig/cache-util: https://
> github.com/php-fig/cache-util/pull/13
>
> Let's see if we can add it to that repo or create a new
1. Margret Staples
2. Mark Railton
3. Alessandro Lai
On Mon, Oct 23, 2017 at 10:16 PM, Joe Ferguson wrote:
> 1. Margret Staples
> 2. Mark Railton
> 3. Alessandro Lai
>
> Good Luck and Godspeed Secretaries :D
>
> - Phergie
>
> On Mon, Oct 23, 2017 at 4:06 PM, GeeH
On 20 Oct 2017 4:38 pm, "Sara Golemon" wrote:
On Thursday, October 19, 2017 at 2:39:36 PM UTC-4, Korvin Szanto wrote:
>
> 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
I already worked a lot on these problems with PPI. If you want me to join
the WG then i will help out
On 28 Mar 2017 11:01 am, "David Négrier" wrote:
> Hey list!
>
>
> PSR-11 has been accepted so we have standardized how to fetch entries from
> containers.
>
> The next
I already worked a lot on these problems with PPI. If you want me to join
the WG then i will help out.
On 28 Mar 2017 11:01 am, "David Négrier" wrote:
> Hey list!
>
>
> PSR-11 has been accepted so we have standardized how to fetch entries from
> containers.
>
> The next
utside of PSR-1. There's nothing wrong with that
really.
A personal suggestion, so you're sticking to StudlyCaps, is you could do
something like TokenEcho TokenEmpty for class names, if PSR-1 is important
to you.
>
> 2017-03-10 9:49 GMT+01:00 Paul Dragoonis <dragoo...@gmail.com>:
&g
Hi Marco,
Comments inline.
On Thu, Mar 9, 2017 at 10:40 PM, Marco Perone wrote:
> As per PSR-1 specifications, class names must be in StudlyCaps.
>
>
> However, if I want to define a class named Echo (or any other Php
> keyword), I am not able to do that beacuse if I do so
+1 from PPI
On Fri, Feb 10, 2017 at 5:29 AM, Shefik wrote:
> + 1 from Zikula
>
> - Shefik
>
> On Feb 8, 2017, at 9:01 AM, Matthew Weier O'Phinney <
> mweierophin...@gmail.com> wrote:
>
> +1
>
> On Monday, February 6, 2017 at 10:54:18 AM UTC-6, Chris Tankersley wrote:
+1 from PPI
On 2 Feb 2017 4:05 pm, "André R." wrote:
> +1 from eZ
>
> Best,
> André R.
>
> --
> You received this message because you are subscribed to the Google Groups
> "PHP Framework Interoperability Group" group.
> To unsubscribe from this group and stop receiving
Used most used (the commonalities) between the frameworks and major
libraries at the time.
Cognitive load for switching between these frameworks and providing a level
of consistency between them.
Phpstorm has an auto formatter to format your code for you, so even if its
not natural to you it
On Mon, Jan 2, 2017 at 1:44 PM, Jordi Boggiano wrote:
> Happy new year everyone!
>
> The vote ended yesterday, and passed! Thanks all for taking the time to
> review.
>
What Jordi said :-)
Upon putting together the initial version of PSR-16, I set up some Docker
Hey,
+1 for PPI Framework Engine
Can the rest of the group please get behind this, and vote?
Many thanks,
Paul
On Sun, Dec 18, 2016 at 3:26 PM, Jordi Boggiano wrote:
> Before I forget, +1 for Composer :)
>
> --
> Jordi Boggiano
> @seldaek - http://seld.be
>
> --
> You
h "natural
>> standardization" for a PSR to be viable.
>>
>> --Larry Garfield
>>
>> On 11/19/2016 11:51 AM, Cees-Jan Kiewiet wrote:
>>
>> Same here, would be very interested to see what Paul has in mind for a
>> routing PSR
>>
>
Hey,
Just wanted to say thanks everyone for the compliments and for the
constructive feedback.
If there's any more clarifications in the spec that you feel are *not*
tight enough please continue to raise here or make a PR so we can review it.
Many thanks,
Paul
On Fri, Nov 18, 2016 at 4:21 PM,
Hello everyone,
I have been waiting to announce this until after I finish with PSR16, but
there's no time like the present.
I have been working on the routing PSR for some time now, given my passion
and experience at integrating 5 different routers into PPI Framework Engine.
I have spoke with a
Hi Michael,
I am happy with this. I think it is the right call to make.
Many thanks,
Paul
On 9 Nov 2016 17:09, "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
Hello,
We all know quality != quantity. I'm sure you're factoring that in here.
There's people in this group that aren't that active, whom I rely on their
judgement to vote on such matters.
Can you, Michael or another appointed secretary, open up to the whole FIG
group the logic behind deciding
PPI Framework will remain.
On 6 Oct 2016 9:09 a.m., "Dracony" wrote:
> PHPixie of course will stay, +1 :)
>
> On Monday, October 3, 2016 at 1:44:02 AM UTC+2, Michael Cullum wrote:
>>
>> As per the FIG 3.0 bylaws, all member projects must, between the 1st
>> October and
PPI votes +1
On 24 Sep 2016 00:00, "Chuck Burgess" wrote:
> +1 from PEAR
>
> On Sep 23, 2016 13:39, "Michiel Rook" wrote:
>
>> +0 Phing
>>
>> On 17-9-2016 1:14, Larry Garfield wrote:
>>
>> I hereby open a vote for the following bylaw changes,
-1 from PPI Framework
On Sat, Sep 10, 2016 at 2:53 AM, Andres Gutierrez <
gutierrezandresfel...@gmail.com> wrote:
> -1 from Phalcon
>
> On Sunday, 4 September 2016 11:26:50 UTC-5, Michael Cullum wrote:
>>
>> Hi all,
>>
>> The PSR-11 Editors have requested we open this vote for them as they are
g and adds
a skin then the existing team gets booted out.
I'd like to be re-instated back into the web team.
>
> Thanks,
> Michael
>
>
> On Monday, 11 July 2016 12:55:32 UTC+1, Paul Dragoonis wrote:
>>
>> All of a sudden my RW access to the website got removed. Can this be
Votes for PPI
1. Samantha Quiñones
2. Jonathan Reinink
3. Amanda Folson
4. Matthew 'Matt' Trask
5. Paul 'PMJ' Jones
6. Phil Sturgeon
On Sun, Aug 14, 2016 at 10:31 PM, Dracony wrote:
> Votes for PHPixie:
>
> Paul 'PMJ' Jones
> Samantha Quiñones
> Amanda Folson
> Jonathan
On 9 Aug 2016 9:22 p.m., "Samantha Quiñones"
wrote:
>
> As Gary said, please let's keep this on-topic and not personal. I advise
you to please assume that others are contributing constructively unless
it's been shown otherwise.
I want to aplogise for the personal nature
On 9 Aug 2016 17:54, "Larry Garfield" wrote:
>
> Given that there's ~9 specs being worked on currently in various stages,
the idea that FIG's work is "done" seems completely unsupportable.
>
> FIG is already the de facto PHP Standards Body. That much is very clear;
some
That's to be discussed later.
This is a fair compromise
>
> On Sunday, July 31, 2016 at 10:12:16 PM UTC+3, Paul Dragoonis wrote:
>>
>> On 31 Jul 2016 19:58, "Paul Jones" <pmjo...@gmail.com> wrote:
>>
>> >
>> >
>> > > On Jul 31, 2016, a
On 31 Jul 2016 19:58, "Paul Jones" wrote:
>
>
> > On Jul 31, 2016, at 13:36, Michael Cullum wrote:
> >
> > Hi Paul,
> >
> > A mix of the two.
>
> Well, let's remove one part of that mix, then.
>
>
> > As previously stated, this PSR was always going to
On Thu, Jul 28, 2016 at 5:28 PM, Larry Garfield
wrote:
> Hm. I would be open to this. We can include the sample code to
> copy-paste in the errata, and include it in the utlis package.
>
> Does anyone object to this recommendation for the errata? Paul and Robert
>
-1 PPI
On 29 Jul 2016 2:54 p.m., "Michael Cullum" wrote:
> Judd,
>
> Voting is for project representatives of member projects only as per the
> voting protocol[1] and only votes, not discussion or opinion polling,
> should take place in this thread.
>
> Thanks,
> Michael
All of a sudden my RW access to the website got removed. Can this be
reinstated please. Thanks.
On Sat, Jul 9, 2016 at 2:40 PM, Michael Cullum wrote:
> Hi all,
>
> I've just done a bit of updating with regards to github permissions. Those
> who should have access to
43 matches
Mail list logo