Looks like this vote is not going to pass, but I feel like I should cast my
vote regardless and +0 feels like an easy way out.
+1 concrete5
To me the issue is that Paul does not acknowledge that his behavior is
detrimental, I have no reason to believe that he is going to make any
attempt to be
I think that's the way to go. Change it from "in both code and
documentation blocks i.e." to "in code i.e."
Thanks,
Korvin
On Tue, Aug 2, 2016 at 6:24 AM 'Alexander Makarov' via PHP Framework
Interoperability Group wrote:
> So would it be OK if we won't touch
So would it be OK if we won't touch documentation i.e. remove "in both code
and documentation blocks"?
On Tuesday, August 2, 2016 at 1:28:07 PM UTC+3, Michael Cullum wrote:
>
> My main issue with this change is that it dictates how it should be used
> in documentation (essentially doc blocks
> On 02 Aug 2016, at 13:10, Matteo Beccati wrote:
>
> Hi Gary,
>
> On 01/08/2016 17:50, GeeH wrote:
>> It was agreed as a group, that voting +1 for the replacement of Paul was
>> inherently pointless, as removing Paul as the voting representative is a
>> moot action
Hi Gary,
On 01/08/2016 17:50, GeeH wrote:
It was agreed as a group, that voting +1 for the replacement of Paul was
inherently pointless, as removing Paul as the voting representative is a
moot action resulting in no perceptible change to the situation. As
Matthew was one of the public