Re: [Internal] [Discussion] Paul M Jones

urge people to work towards accepting Paul as someone that communicates on a very technical and abstract level. he is driven by technology, not by making other people lives miserable. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed

Re: I resign

more productivity to be able to release PSR’s quicker .. but lets also not make this group smaller than it is .. for all its faults, FIG is very important for PHP! regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the Google Groups "PH

Re: A message from the Zend Framework CR team

nk Paul has so far not shown any willingness to adjust his behavior regardless of offlist or onlist discussions on this topic, so I understand the frustration that led to expulsion vote. There Paul imho rather than mend fences favored to fuel the fire once again. If this was done intentionally

Re: [Internal] [Discussion] Paul M Jones

feel is worthy of critique. These are the types of things I would write into a netiquette but probably is too fuzzy for a CoC. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" gro

Re: [VOTE] Membership Application: pimcore

+1 from Jackalope (I am not sure if I am allowed to vote as the sponsor for the application) > On 18 Jul 2016, at 16:02, Michiel Rook <michiel.r...@gmail.com> wrote: > > +1 from Phing > > On 18-07-16 16:00, Lukas Kahwe Smith wrote: >> Aloha, >> >> S

Re: [Internal] [Discussion] Paul M Jones

is once more when someone else wondered about the same thing and Angie mentioned it again in our post today that this has been confirmed by me via Michael (though it was not confirmed by Paul who might have a different point of view). I saw several posts that either assumed no such attemp

Re: [Internal] [Discussion] Paul M Jones

regards, Lukas > On 09 Jul 2016, at 09:52, 'scott molinari' via PHP Framework Interoperability > Group wrote: > > On Saturday, July 9, 2016 at 1:30:03 AM UTC+2, Christopher Pitt wrote: >> >>> Finally, to the complainants: you wanted to hang me, so start tying the

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

8-bff8-922ab22dd4b5%40googlegroups.com > > <https://groups.google.com/d/msgid/php-fig/6c57f47b-bca3-47e8-bff8-922ab22dd4b5%40googlegroups.com?utm_medium=email_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>.

Re: [Discussion][Internals] Remove the Interface suffix from PSR naming conventions

incompatible to previous PSRs. But overall I have not seen any significant arguments from either side that would sway me in either direction and as such I would stick with the status quo. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the

Re: [Discussion][Internals] Remove the Interface suffix from PSR naming conventions

such a scenario let's discuss > it. it was a general comment in reply to your general comment that past decision should not prevent is from doing something different in the future. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the Go

Re: [VOTE] PSR-6 Errata

om 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/e9508662-70c7-e91a-05ff-82c8dfb59884%40garfieldtech.com. > For more o

Re: [VOTE] [Bylaw Amendment] Do not require interface suffix on future PSR Interfaces

-1 from Jackalope regards, Lukas > On 04 Sep 2016, at 18:26, Michael Cullum wrote: > > 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

Re: Alternative to FIG 3.0 - Is it time to call FIG complete?

neral community isn’t pondering our mission statements, they are looking at the PSRs that come out and not how they were crafted. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group

Re: [Important] [Internals] All projects must declare intention to remain members

> <https://groups.google.com/d/msgid/php-fig/CAAqcDMhL7F2PGfKoASNUDAFuLe3LcRUYYOyp7T-UfqVdQWoFpA%40mail.gmail.com?utm_medium=email_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. regards, Lukas Kahwe Smith

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

://groups.google.com/d/msgid/php-fig/CAJp_myXK4gb9b4%2Bph4Oac979bW0RpCDy5HbC4e70ght5xeeFcQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the Google Gro

Re: [CC][Nomination] Lukas Kahwe Smith

ects. He was also one of the people who helped > change the PHP development process a few years back. > > I'm sure he would do a wonderful job as a member of the Core Committee. Thank you for the nomination. I accept regards, Lukas Kahwe Smith sm...@pooteeweet.org PS: I am going on vacation

[CC][About Candidate] Lukas Kahwe Smith

towards resolving potential issues. regards, Lukas Kahwe Smith sm...@pooteeweet.org (*) Disclaimers: I did have a pretty hard falling out with Matthew on an argument related to Apigility which afaik let to him blocking me on Twitter, which is unfortunate but I hold no hard feelings towards ZF

Re: [VOTE] First Core Committee Elections

>From Jackalope: Beau Simensen Larry Garfield Sara Golemon Matthew Weier O’Phinney Tobias Nyholm Samantha Quiñones Lukas Kahwe Smith Stefano Torresi Graham Daniels Jeremy Coates Chris Tankersley Cees-Jan Kiewiet Marc Alexander Same Minée David Négrier Korvin Szanto Gary Hockin Steve Winter Ja

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

+1 from Jackalope regards, Lukas > On 23 Dec 2016, at 21:24, Fabien Potencier wrote: > > +1 Symfony > >> On 12/23/16 20:42, Cees-Jan Kiewiet wrote: >> +1 from ReactPHP >> >> On Fri, Dec 23, 2016 at 4:38 PM, Leo Feyer > >

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

msgid/php-fig/bc288330-b520-4248-b8fb-588e6fd5de09%40googlegroups.com > > <https://groups.google.com/d/msgid/php-fig/bc288330-b520-4248-b8fb-588e6fd5de09%40googlegroups.com?utm_medium=email_source=footer>. > For more options, visit https://groups.google.com/d/optout > &

Re: [VOTE] Secretary Election

subscr...@googlegroups.com>. > To post to this group, send email to php-fig@googlegroups.com > <mailto:php-fig@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/c38e9460-fe49-4687-b783-710932557e3f%40googlegroups.com > > &

Re: New Secretaries

our terms Margret and Alessandro! Furthermore thank you Mark for stepping up for the vote and hope you are not too disappointed. There are plenty of other opportunities to support FIG and any work will be highly appreciated. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You rec

Re: Should new PSRs support PHP5?

> On 28 Oct 2017, at 20:23, Oscar Otero wrote: > > > Ok, I see. > Could this be solved with php 7.2, that implements parameter type widening? > (https://wiki.php.net/rfc/parameter-no-type-variance) > So we can keep releasing interfaces compatible with php5 and in a short

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

ooglegroups.com>. > To post to this group, send email to php-fig@googlegroups.com > <mailto: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 > &g

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

+1 Lukas Kahwe Smith > On 12 Jan 2018, at 16:47, Matthew Weier O'Phinney <mweierophin...@gmail.com> > wrote: > > The REVIEW period for the proposed PSR-15, HTTP Server Request > Handlers, hit its minimum required length on 2 January 2018. We > continued the perio

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

an > email to php-fig+unsubscr...@googlegroups.com. > To post to this group, send email to php-fig@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/CAJp_myWaxDJ9biQvWjiSVoZ%2Brga%3DLVt99jE20c0jbYvxBLBL0A%40mail.gmail.com. > For

Re: [VOTE] Secretary Elections - Voting is Now!

Jackalope votes > On 4 Aug 2018, at 18:36, Dead Lugosi wrote: > > Alessandro Lai > Daniyal Hamid PS: Not sure if I am still/also eligible to vote as a CC member? -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To

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

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/5365608.7dg2KeOeTa%40vulcan. > For more options, visit https://groups.google.

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

+1 -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to

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

-fig/fig-standards/blob/master/proposed/http-client/ht >> tp-client.md - Metadocument: >> https://github.com/php-fig/fig-standards/blob/master/proposed/http-client/ht >> tp-client-meta.md >> >> PLEASE DO NOT VOTE UNLESS YOU ARE A CC MEMBER. >> Current CC Me

Re: [ENTRANCE] [VOTE] [CC] PHPDoc & PHPDoc Tags PSRs

visit > https://groups.google.com/d/msgid/php-fig/3cc1f7f8-97be-4c8d-9b29-353aa3365b35%40googlegroups.com > > <https://groups.google.com/d/msgid/php-fig/3cc1f7f8-97be-4c8d-9b29-353aa3365b35%40googlegroups.com?utm_medium=email_source=footer>. > For more options, visit https://gro

Re: Proposal: Adopt Code Manifesto

On Wed, Jan 23, 2019 at 1:17 AM Larry Garfield wrote: > > Greetings, FIGians. > > This has been bounced around in back channels on and off for a while, so I > think it's finally time to make it official. I propose that we officially > adopt the Code Manifesto[1] as our official standard of

Re: Proposal: Adopt Code Manifesto

On Wed, 23 Jan 2019 at 20:42, Matthew Weier O'Phinney < mweierophin...@gmail.com> wrote: > > > On Wed, Jan 23, 2019 at 2:49 AM Lukas Kahwe Smith > wrote: > >> On Wed, Jan 23, 2019 at 1:17 AM Larry Garfield >> wrote: >> > >> > Greetings, FIGi

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

-meta.md > > PLEASE DO NOT VOTE UNLESS YOU ARE A CC MEMBER. > Current CC Members are as follows: > > Beau Simensen > Larry Garfield > Matthew Weier O’Phinney > Sara Golemon > Cees-Jan Kiewiet > Lukas Kahwe Smith > Samantha Quiñones > Chris Tankersley > Kor

Re: Proposal: Adopt Code Manifesto

Maybe just link to both, >> since they are standalone entities (that seem to be versioned, or at least >> versionable)? Stating that we want to abide by both, then delineating how >> those in FIG positions can act to enforce, ... maybe that would cover the >> conce

Re: [VOTE] Core Committee Election

Aloha, Jackalope votes: Larry Garfield Matteo Beccati Benni Mack Beau Simensen Woody Gilk Matthew Weier O'Phinney Adam Englander regards, Lukas On Sun, May 5, 2019 at 11:48 PM Alessandro Lai wrote: > > Hello everyone, > as specified in the previous thread >

Re: naming PSR

or by-law but that is updated once per year (or more often), that is referenced from an inclusive language PSR similar to the other resources. wdyt? regards Lukas On Wed, 19 Aug 2020 at 16:11, Lukas Kahwe Smith wrote: > > > On Tue, Aug 11, 2020 at 6:02 PM Alessandro Lai > wrote:

Re: naming PSR

On Tue, Aug 11, 2020 at 6:02 PM Alessandro Lai wrote: > Thanks Lukas for the continued effort on this topic. You're basically > stumbling on a recurring problem that we have here at PHP-FIG: we don't > have a way to stipulate a "living document", something that is similar to a > PSR but can

Re: naming PSR

On Wed, 15 Jul 2020 at 17:49, Lukas Kahwe Smith wrote: > Aloha, > > First up Chris thank you for your input specifically. > > Happy to see so many voices of support as well. > > In general: Who would be motivated to work with me on shaping a proposal? > Please conta

Re: FIG CoC - take 2

On Sun, Aug 9, 2020 at 12:14 AM Larry Garfield wrote: > Getting back to this... > > It looks like there's a couple of different threads here, which I will try > to separate: > > 1) Code Manifesto vs Contributor Covenant. I really wish we wouldn't get > hung up and side tracked on this,

Re: naming PSR

Aloha, First up Chris thank you for your input specifically. Happy to see so many voices of support as well. In general: Who would be motivated to work with me on shaping a proposal? Please contact me directly via slack, email, twitter (@lsmith) .. Note: For now I would put the scope on

naming PSR

Aloha, So the topic of naming things has become even more discussed as in the previous years in part due to recent protests in the world. I think most of us are familiar with the saying "There are only two hard things in Computer Science: cache invalidation and naming things." Many of us are

Re: FIG CoC - take 2

Aloha, thank you for bringing this up again. there were already quite a few comments on the PR at the time, which interested people should have a look at. I also share the concern that this CoC lacks explicitness which is why I also favor a covenant of code based CoC. this is what we created