> -Original Message-
> From: Derick Rethans [mailto:der...@php.net]
> Sent: Monday, January 25, 2016 1:01 PM
> To: Stanislav Malyshev
> Cc: Pierre Joye ; PHP internals
>
> Subject: Re: [PHP-DEV] Specific incident in relationship to the proposed Code
> of Con
On Sat, 23 Jan 2016, Stanislav Malyshev wrote:
> > I think we should have used temporary bans a bit more to cool down
> > things. Including to myself along other.
>
> Ban is a very dangerous thing, since it excludes people from discussion
> thus preventing it from reaching a conclusion, achievin
On Sun, Jan 24, 2016 at 6:49 PM, Zeev Suraski wrote:
>> > I've been reading the mini-thread that followed this message, and I'm
>> wondering, almost out loud:
>> > Isn't it obvious we're trying to create an amateur drive-by judicial
>> > system,
>> borrowing ideas from the law (some mostly univer
> > I've been reading the mini-thread that followed this message, and I'm
> wondering, almost out loud:
> > Isn't it obvious we're trying to create an amateur drive-by judicial system,
> borrowing ideas from the law (some mostly universal, some not),
> oversimplifying them (amateurishly, as we wou
Hi Scott,
On 24 January 2016 at 03:25, Scott Arciszewski wrote:
> I think focusing on the extreme behaviors is harmful towards a mature and
> progressive discussion on these matters. My opinion is based on two
> premises:
>
> 1. Good opsec, which career criminals and dedicated harassers would be
On Sun, Jan 24, 2016 at 5:22 PM, Pádraic Brady wrote:
> Hi,
>
> On 24 January 2016 at 02:31, Stanislav Malyshev wrote:
>> Hi!
>>
>>> perspective. The absolute best we can do is just that - the absolute
>>> best. And it's entirely responsible to ensure that it IS the absolute
>>> best that can be
Hi All.
Am 23.01.16 um 18:43 schrieb Brandon Savage:
> All,
>
> It's encouraging to see people working hard to improve and expand on the
> proposed Code of Conduct for PHP. The strenuous and passionate debates
> aside, I'm pleased to see so many people working on this together.
>
> I want to pro
Hi,
On 24 January 2016 at 02:31, Stanislav Malyshev wrote:
> Hi!
>
>> perspective. The absolute best we can do is just that - the absolute
>> best. And it's entirely responsible to ensure that it IS the absolute
>> best that can be achieved.
>
> I think this is an incorrect approach - both in mak
Hi!
> I think we should have used temporary bans a bit more to cool down
> things. Including to myself along other.
Ban is a very dangerous thing, since it excludes people from discussion
thus preventing it from reaching a conclusion, achieving consensus and
closure, and it also hurts people and
On Sat, Jan 23, 2016 at 9:59 PM, Pierre Joye wrote:
> Hello,
>
> On Jan 24, 2016 9:31 AM, "Stanislav Malyshev" wrote:
> >
> > Hi!
> .
> >
> > > day. To state an obvious question - what precisely is the status quo
> > > in comparison to a COC? Ad-hoc bans by whoever has access to the ML?
> >
> >
Hello,
On Jan 24, 2016 9:31 AM, "Stanislav Malyshev" wrote:
>
> Hi!
.
>
> > day. To state an obvious question - what precisely is the status quo
> > in comparison to a COC? Ad-hoc bans by whoever has access to the ML?
>
> Yes, status quo is pretty much that. IIRC we needed it one, two times
> ove
Hi!
> perspective. The absolute best we can do is just that - the absolute
> best. And it's entirely responsible to ensure that it IS the absolute
> best that can be achieved.
I think this is an incorrect approach - both in making software and
other places. You don't release software when it's ab
On Jan 24, 2016 5:02 AM, "Zeev Suraski" wrote:
>
> > -Original Message-
> > From: Brandon Savage [mailto:bran...@brandonsavage.net]
> > Sent: Saturday, January 23, 2016 7:44 PM
> > To: PHP internals
> > Subject: [PHP-DEV] Specific incid
Hi,
On 23 January 2016 at 22:02, Zeev Suraski wrote:
>> -Original Message-
>> From: Brandon Savage [mailto:bran...@brandonsavage.net]
>> Sent: Saturday, January 23, 2016 7:44 PM
>> To: PHP internals
>> Subject: [PHP-DEV] Specific incident in relati
> -Original Message-
> From: Brandon Savage [mailto:bran...@brandonsavage.net]
> Sent: Saturday, January 23, 2016 7:44 PM
> To: PHP internals
> Subject: [PHP-DEV] Specific incident in relationship to the proposed Code of
> Conduct
>
> Open to suggestions/commen
On 23/01/2016 17:43, Brandon Savage wrote:
* The Code of Conduct should specifically state that a person who is not a
direct party to the alleged incident is not permitted to make a complaint.
While I'd agree with this in general, there might be circumstances where
a "direct party" doesn't feel
Hi,
On 23 January 2016 at 17:43, Brandon Savage wrote:
> I think these are fixable problems. I propose the following:
>
> * The Code of Conduct should specifically state that a person who is not a
> direct party to the alleged incident is not permitted to make a complaint.
Maybe. My main concern
Whoops, I accidentally hit reply instead of reply to all on this earlier,
thanks Brandon for pointing that out.
On 23 January 2016 at 17:43, Brandon Savage
wrote:
> The Code of Conduct, as written, makes no exception for the intent of the
> person involved. This is an important problem, becaus
Hey Brandon, definitely some thoughts for consideration. I did want to
respond to one piece of this:
> This is an important problem, because intent ("mens rea"
> in Latin, for "guilty mind") is typically required to convict people of
> criminal acts in much of the world. For example, you cannot b
All,
It's encouraging to see people working hard to improve and expand on the
proposed Code of Conduct for PHP. The strenuous and passionate debates
aside, I'm pleased to see so many people working on this together.
I want to propose a scenario that I came across this morning, that might
work wel
20 matches
Mail list logo
