Re: I resign

Thank you for all the work you've done here, Mike. Sad to see you go, but I hope you feel better for it. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, s

Re: [PSR-7] Do different implementations truly exist?

> > Stream implementation is definitely out of scope for FIG, it has nothing > to do with this topic. It is of particular interest to the async interoperability work going on. Perhaps we'll get a specification/implementation out of there... -- You received this message because you are subsc

Re: Resignation from Secretary Position

Thank you for your hard work and empathy, Joe. Good luck growing OSMI! -- You received this message because you are subscribed to the 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..

Re: [Internal] [Discussion] Paul M Jones

> > Finally, to the complainants: you wanted to hang me, so start tying the > noose and call the vote. > That is uncalled for. Asking for something to be addressed/discussed is in no way a desire to hang you. This statement does nothing but appear to vilify folks obviously seeking some kind of

Re: [Internal] [Discussion] Paul M Jones

> > I will not disclose who as it is for individuals to make their own cases My strongest motivation for leaving was Paul's conduct on this list, towards me and others. For the record: I do not care to discuss different political views we may hold elsewhere. He is technically proficient and I

Re: [Internal] [Discussion] Paul M Jones

Joshua, As far as I can tell, your first comment on this thread (on the 19th) came a day after Michael asked Paul to respond to proposed measures to address the problem under discussion (on the 18th). You are not the first person to suggest actions, nor are we all waiting for you, but rather a

Re: [Internal] [Discussion] Paul M Jones

Hi Tom, > So is this thread really going to go on an on until Paul comes here and > agrees or disagrees with each "You're an asshole" comment on here? No, that is not the case. Many folks have suggested options which are not limited to expulsion or language reviews. If you go to back to Mich

Re: [Internal] [Discussion] Paul M Jones

Roman, - Vote is last resort - We are waiting for Paul's feedback on the options he asked for - Please be constructive Regards Chris -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this grou

Re: On the Interoperability of Cryptographic Components -or- Stop Writing In-House Cryptography Features

> > I find it a bit concerning that the reflexive response to my post was the > consideration of "Should we make this a rule?" To be fair, this isn't an unreasonable assumption of intent given where you've posted it. :) -- You received this message because you are subscribed to the Google G

Re: FIG 3.0 (Including a TL;DR Summary)

> > secretaries taking an active role in a discussion threads, versus aiding > members in understanding content I don't understand the difference. Unless by "aiding members in understanding" you mean not speaking. Then I understand the difference. :) -- You received this message because you

Re: FIG 3.0 (Including a TL;DR Summary)

Hi Adam, I apologise, that was not meant condescendingly at all! I sincerely do not understand what you meant. Kind regards Chris -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop

Re: [Nomination] FIG Secretary: Phil Sturgeon

The potential for Paul and Phil being secretaries together. What is happening to this day? > > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an ema

Harmony between secretaries

Hey folks, Nominations appear to be proceeding well. Given how many people (and diverse personalities) have been nominated, it seems appropriate to discuss the issue of harmony between secretaries. Let me give two examples: 1. Paul and Phil get voted in at the same time. What does that mean for

Re: FIG 3.0 Discussion Period

> > I suppose one could say that the discussion has been going off-and-on for > months at this point. > Whether or not officially announced; I can count roughly 14 threads discussion various aspects of it. The earliest one seems to have been started around April 28th

Re: FIG 3.0 Discussion Period

I understand your concern - few have time to read entire proposals before a vote starts. I think the summary thread you were looking for can be found here . Perhaps apart from "TL;DR" the thread title should have included "[discu

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

> > FIG has served its purpose and should be archived. > You mean aside from the ongoing PSR work? The 10 or so PSRs, approved by vote, to be worked on? Seems a bit premature to say FIG is purposeless and/or useless... -- You received this message because you are subscribed to the Google Grou

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

Also skipped the async stuff (event loops and promises), which are also *-interop projects. My point was less about things that are *-interop and more all these things having started as projects under the FIG banner, with their natural conclusion set for the same. -- You received this messag

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

> > I don't see an "async" PSR listed (unless you mean the Event Manager PSR, > in which case it was indeed included my original list). You know I don't mean event manager. Though, to be frank, I think it would be better not to bring the final standards and implementations back to FIG. --

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

Performing managerial tasks doesn't make someone a manager of people. I suggest we ask ourselves the question - does FIG 3.0's definition of the secretaries differ from the current bylaws definition of the secretaries? Does the current definition of secretaries (or someone's disagreement of the

Re: Comments please: Asset Scheme

Nice write-up. Do you think it would be possible to survey member projects (including recently departed projects, like Laravel), to determine things like the most common/preferred name for the webroot folder? -- You received this message because you are subscribed to the Google Groups "PHP Fra

Re: [CC][Nomination] Graham Daniels

> > Somebody who feels he's not "adding value" is a very poor choice for a CC > member. Not to put words in Graham's mouth (or Michael's mouth), but the previous FIG structure is *very* different from this new incarnation. I didn't feel like I was adding enough value to justify the amount of

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

The only concern I have* here is that Graham has also been nominated, and that I don't think it's best for the committee for spouses to be on it together. * I love both these people, and I think they're both qualified and fantastic humans. I'd be saying the same thing if any other couple were

Re: [CC][Nomination] Graham Daniels

I'll respond, since I was the first to bring this issue up, in Samantha's nomination thread. I don't personally think it's a good idea, because it puts added pressure on Samantha and Graham. Not because I think they'll be forced to always agree with each other but because they'll be under incre

Re: [CC][Nomination] Graham Daniels

Hey Matthew, Let's take a step back here. I have given a reason for why I think it's a bad idea, but I'ave also said (very clearly I think) that it's just my personal opinion. That these are two very capable people, and that *sometimes* being reactive isn't the only approach we could take. You

Re: [CC][Nomination] Graham Daniels

Could we lock this thread please? I think it's getting blown way out of proportion, and is just as harmful to the nomination as it is to the expression of opinion. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsu

[CC][Nomination] Sam Minnée

Hi folks, I'd like to nominate Sam, but I'm not a voting member. Would anyone else like to? Sam is the original author, and a current core committer of the SilverStripe framework and CMS. He's a talented developer, an insightful project leader, and a wonderful human. Here's a bit of history, of

[CC][Nomination Request] Sam Minnée

Hi folks, I'd like to nominate Sam, but I'm not a voting member. Would anyone else like to? Sam is the original author, and a current core committer of the SilverStripe framework and CMS. He's a talented developer, an insightful project leader, and a wonderful human. Here's a bit of history, of

Re: [VOTE] First Core Committee Elections

Sam Minnée (aka Same Minée) Beau Simensen Cees-Jan Kiewiet Graham Daniels Samantha Quiñones Chris Tankersley Gary Hockin Larry Garfield Matthew Weier O’Phinney Sara Golemon -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group"

Re: [PSR-5] @method Pointers

It's an interesting idea, but I've always understood @method to be an inherited thing. So that "extends \X\Y" or "@mixin \X\Y" indicate where to find inherited methods, and @method/@mixin applied to the parent also applies to the child. -- You received this message because you are subscribed t

Re: Seeking Explanations of PRS-2 Standards

Hey Spencer, To answer these why's, the team behind PSR-2 did a survey of commonalities amongst PHP frameworks: http://www.php-fig.org/psr/psr-2/#appendix-a-survey Kind regards Chris -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability G

Re: Seeking Explanations of PRS-2 Standards

The survey showed what was common, which became what was standard, as I recall. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+