Re: [PHP-DEV] Re: [RFC] Traits with interfaces

2016-02-18 Thread Chase Peeler
On Thu, Feb 18, 2016 at 5:35 AM Larry Garfield wrote: > On Wed, Feb 17, 2016, at 01:05 PM, Kevin Gessner wrote: > > On Wed, Feb 17, 2016 at 9:25 AM, Kevin Gessner > wrote: > > > > > Hello internals team! I'd like to propose an RFC to allow traits to > > > implement interfaces. > > > > > > > I'v

Re: [PHP-DEV] [RFC] Traits with interfaces

2016-02-17 Thread Chase Peeler
I agree. with Sebastian. I'm personally a big fan of using traits as the implementation mechanism for interfaces (i.e. implement the interfaces methods in a trait, then use that trait in a class that implements the interface), but I don't think there is anything positive to gain from having the tra

Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct

2016-01-22 Thread Chase Peeler
On Fri, Jan 22, 2016 at 2:42 PM John Bafford wrote: > Chase, > > On Jan 22, 2016, at 13:15, Chase Peeler wrote: > > > > 1.) I think everyone already knows how to be an adult. The fact that > > sometimes we don't act in a civil manner isn't because we don

Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct

2016-01-22 Thread Chase Peeler
ul to Anthony and Derick for carrying this RFC. > > Now… I have one issue with this argument : > > Chase Peeler a écrit le 22/01/2016 19:15 : > > 3.) Finally, I think a Code of Conduct that includes punitive > > measures is a bad idea. I won't go into details on why,

Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct

2016-01-22 Thread Chase Peeler
I just want to reiterate what I've said a few times before. I'm leaving the points about why I think a Code of Conduct, in general, is a bad idea until the end, in hopes that others will at least read my other points. I don't think there is anything "new" in what I'm saying below either - I'm prett

Re: [PHP-DEV] Re: Internals and Newcomers and the Sidelines -- "let's proceed to ideas"

2016-01-13 Thread Chase Peeler
On Wed, Jan 13, 2016 at 2:46 PM Larry Garfield wrote: > On 1/13/16 1:18 PM, Tom Worster wrote: > > On 1/12/16 5:58 PM, Stanislav Malyshev wrote: > > > >> But we can not change the conduct of "whole of internals as a group". > > > > Yes we can! > > > > Let's say *we* would improve our conduct. I m

Re: [PHP-DEV] Re: Internals and Newcomers and the Sidelines (WAS: Adopt Code of Conduct)

2016-01-12 Thread Chase Peeler
I personally offered at least two emails with constructive feedback and alternative solutions. I never saw any reply or feedback to either one. I also had some emails in which I was somewhat argumentative (the ones related to the definition of harassment). I still stand by those emails as they were

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-11 Thread Chase Peeler
On Mon, Jan 11, 2016 at 12:52 PM Pierre Joye wrote: > On Jan 11, 2016 8:47 PM, "Brandon Savage" > wrote: > > > > > > > > At the same time, though, if someone is being maliciously hostile what > > > great cover! A private email is not a PHP-Group managed resource, so > no > > > rules! Twitter,

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-08 Thread Chase Peeler
On Fri, Jan 8, 2016 at 12:28 PM Paul M. Jones wrote: > > > On Jan 7, 2016, at 23:52, Larry Garfield wrote: > > > > Do you think we can find 5 people in the PHP community that we can trust > to make fair decisions (NOT that we would always agree with, but that are > fair) that don't fall too far

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-08 Thread Chase Peeler
Let's look at this from the perspective of a conflict mediation standpoint On Fri, Jan 8, 2016 at 11:55 AM Anthony Ferrara wrote: > Keith, > > On Fri, Jan 8, 2016 at 11:38 AM, D Keith Casey > wrote: > > On 1/7/16 11:52 PM, Larry Garfield wrote: > >> > >> On 01/07/2016 10:08 PM, Brian Moon wrote

Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct

2016-01-08 Thread Chase Peeler
On Fri, Jan 8, 2016 at 10:49 AM Anthony Ferrara wrote: > Kevin, > > On Fri, Jan 8, 2016 at 10:39 AM, Kevin Smith wrote: > > > > > >> On Jan 8, 2016, at 9:09 AM, Anthony Ferrara > wrote: > >> > >> > >> Simply look at the level of attacks that me and a few other committers > >> have received by m

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-07 Thread Chase Peeler
On Thu, Jan 7, 2016 at 3:07 PM, Pierre Joye wrote: > > On Jan 8, 2016 2:58 AM, "Chase Peeler" wrote: > > > > > > > > On Thu, Jan 7, 2016 at 2:51 PM, Pierre Joye > wrote: > >> > >> On Jan 8, 2016 2:44 AM, "Paul M. Jones&quo

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-07 Thread Chase Peeler
On Thu, Jan 7, 2016 at 3:37 PM, Pierre Joye wrote: > > On Jan 8, 2016 3:34 AM, "Chase Peeler" wrote: > > > > > > > > On Thu, Jan 7, 2016 at 3:21 PM, Pierre Joye > wrote: > >> > >> > >> On Jan 8, 2016 3:14 AM, "Chas

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-07 Thread Chase Peeler
On Thu, Jan 7, 2016 at 3:21 PM, Pierre Joye wrote: > > On Jan 8, 2016 3:14 AM, "Chase Peeler" wrote: > > > > > And none of those caveats exist in the definition you provided. > > Hmmm. Which one did you read? > > "the act of systematic and/or

Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct

2016-01-07 Thread Chase Peeler
The way I see this, and I believe others do as well based on the previous recommendation to split this into two RFCs, is there are two goals: 1.) Making it clear that the community welcomes all individuals 2.) A means for handling conflict resolution. To me, #1 doesn't really fall into a "Code of

Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct

2016-01-05 Thread Chase Peeler
While overall I tend to agree with Paul on the concept of a CoC, I don't think that precludes the ability to offer suggestions. It's to everyone's advantage to make sure that if we do adopt a CoC, we adopt the best one possible. Obviously one of the biggest fears is unjust treatment of the accused

<    1   2   3