Hi Sara,
> -Original Message-
> From: p...@golemon.com [mailto:p...@golemon.com] On Behalf Of Sara
> Golemon
> Sent: Tuesday, July 18, 2017 5:08 PM
> To: PHP internals
> Subject: [PHP-DEV] Images on Workflow Wiki
>
> Who does the art for https://wiki.php.net/vcs/gitworkflow ? It could us
>
> I have looked at various ways of doing this, but it isn't trivial and it
> has absolutely nothing to do with the actual html and slapping in some
> https links instead of http. The problem here is that we have external
> volunteers running all our mirrors and we do geo-dns for www.php.net to
>
> On 20 Jul 2017, at 07:40, Rasmus Lerdorf wrote:
>
>> On Wed, Jul 19, 2017 at 1:42 PM, Niklas Keller wrote:
>>
>>
>> We should really change that and fully move to HTTPS.
>>
>
> I have looked at various ways of doing this, but it isn't trivial and it
> has absolutely nothing to do with the
On Wed, Jul 19, 2017 at 1:50 PM, Sara Golemon wrote:
>
> * Use docker hub as the distribution channel. (https out of the box)
>
Getting https support in the web server is not what prevents us from
getting https for www.php.net. It is key management across our geodns
www.php.net that is the limiti
On Wed, Jul 19, 2017 at 1:42 PM, Niklas Keller wrote:
>
> We should really change that and fully move to HTTPS.
>
I have looked at various ways of doing this, but it isn't trivial and it
has absolutely nothing to do with the actual html and slapping in some
https links instead of http. The probl
Hi Chris,
> -Original Message-
> From: Christopher Jones [mailto:christopher.jo...@oracle.com]
> Sent: Thursday, July 20, 2017 2:11 AM
> To: Anatol Belski ; php-...@lists.php.net; Tianfang Yang
>
> Subject: Re: [PHP-CVS] com php-src: fix default args for --with-pcre-valgrind:
> ext/pcre/c
Results for project PHP master, build date 2017-07-18 19:22:37-07:00
commit: 21d5636
previous commit:a39fd99
revision date: 2017-07-19 01:06:01+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
As someone who has made a decent number of changes to the website I think
our future direction should focus on these points:
1. Ease of setup and deployment
2. Fewer moving parts (related to above)
3. Move to modern HTML, JavaScript and CSS practices (perhaps completely
disallowing inline CS
>
> And for my $0.02, I agree with Andreas. Caesar's wife must be beyond
> reproach, and quite frankly there is plenty that can be done to
> beautify/update the web-php codebase that doesn't involve frameworks.
> *cough*globals*cough*.
>
> In fact, if you want to start with a more constrained prob
Bugs could be good thing as well.
What the case with the bugs?
For the php.net I think it could actually be worthy generating html.
But as I said, the idea is to make the code readable again, be it with a
framework or not.
Having all that html mixed with php + globals is really bad. Even if we
wan
On Wed, Jul 19, 2017 at 4:02 PM, Andreas Heigl wrote:
> I personally strongly disagree with that approach. Most of the pages on
> php.net are static pages. And those few that aren't can be well addressed
> with their own script and within that vanillaPHP-script the task can be
> solved. IMO there
On Mi, 2017-07-19 at 21:34 +0200, Mathias Grimm wrote:
> Thats a valid point but that can be addressed in some nice ways.
>
> The documentation can mention it somehow and that doesn't mean
> somebody else should use that framework/lib for every project/case.
> That would be similar to saying that
On Di, 2017-07-18 at 21:42 +0200, li...@rhsoft.net wrote:
>
> Am 18.07.2017 um 21:37 schrieb Nikita Popov:
> >
> > I just found out that some of the PDO code contains MySQL version
> > checks
> > going all the way back to MySQL 3.22.30, which has been released in
> > 2000.
> >
> > What is the mi
Hi,
On Di, 2017-07-18 at 21:37 +0200, Nikita Popov wrote:
> I just found out that some of the PDO code contains MySQL version
> checks going all the way back to MySQL 3.22.30, which has been
> released in 2000.
>
> What is the minimum MySQL version we support? can I drop checks for
> MySQL 3.x an
> Am 19.07.2017 um 20:34 schrieb Mathias Grimm :
>
> Thats a valid point but that can be addressed in some nice ways.
>
> The documentation can mention it somehow and that doesn't mean somebody else
> should use that framework/lib for every project/case.
> That would be similar to saying that
Thats a valid point but that can be addressed in some nice ways.
The documentation can mention it somehow and that doesn't mean somebody
else should use that framework/lib for every project/case.
That would be similar to saying that we prefer Linux over Windows, just
because we use Linux hosting a
Am 19.07.2017 um 19:12 schrieb Mathias Grimm :
>
> I think it's a great idea about docker, although a separated project.
>
> The wiki says minimum php is 5.3 but that page is from 2013 and would be
> really great to not depend on the mirrors php version, although we can
> write beautiful php even
I think it's a great idea about docker, although a separated project.
The wiki says minimum php is 5.3 but that page is from 2013 and would be
really great to not depend on the mirrors php version, although we can
write beautiful php even in php 4 (never did prior to 4)
On 19 July 2017 at 19:50
On 19 July 2017 at 20:06, Mathias Grimm wrote:
>
>
> On 19 July 2017 at 19:41, Niklas Keller wrote:
>
>> Hey,
>>
>>
>>> I would like to know who is/are "in charge" of the website (
>>> https://github.com/php/web-php).
>>> I think I would like to help improving it a bit.
>>>
>>> I can possibly un
On Wed, Jul 19, 2017 at 1:42 PM, Niklas Keller wrote:
> We should really change that and fully move to HTTPS.
>
I was actually just thinking how lovely it would be to re-architect
the mirroring process to use docker images.
Benefits:
* Usual consistent/predictable deployment arguments...
* Full c
>
> On Wed, Jul 19, 2017 at 1:07 PM, Mathias Grimm
> wrote:
> > I was briefly asking Sara about it and as she pointed out it is likely a
> > big project but I think we can do something about it.
> >
> One thing I should have mentioned on twitter was:
> https://wiki.php.net/web/mirror
>
> That'll g
Hey,
> I would like to know who is/are "in charge" of the website (
> https://github.com/php/web-php).
> I think I would like to help improving it a bit.
>
> I can possibly understand the reasons why it is still like it is, code
> wise, but I think there is a lot of room from improvement. Also, f
On Wed, Jul 19, 2017 at 1:07 PM, Mathias Grimm wrote:
> I was briefly asking Sara about it and as she pointed out it is likely a
> big project but I think we can do something about it.
>
One thing I should have mentioned on twitter was:
https://wiki.php.net/web/mirror
That'll get you a locally ru
I can help.
> On 19 Jul 2017, at 19:07, Mathias Grimm wrote:
>
> Hi,
>
> I would like to know who is/are "in charge" of the website (
> https://github.com/php/web-php).
> I think I would like to help improving it a bit.
>
> I can possibly understand the reasons why it is still like it is, code
Hi,
I would like to know who is/are "in charge" of the website (
https://github.com/php/web-php).
I think I would like to help improving it a bit.
I can possibly understand the reasons why it is still like it is, code
wise, but I think there is a lot of room from improvement. Also, from the
refer
Hi Anatol.
Anatol Belski in php.internals (Wed, 19 Jul 2017 13:37:59 +):
>Hi Jan,
>
>> Congrats. Question, maybe for Anatol: what did change in the Windows Build
>> environment? It was taking ages for 'Generating code', for each extension.
>> Now
>> it is as fast as building PHP 7.1.
>
>There
Hi Andrey,
Thanks for you remark. If I understand correctly, PHP was 4-5 years
ahead of HttpOnly becoming an actual standard. What a leaders they were
back then.
Best,
Frederik
On 19-07-17 17:06, Andrey Andreev wrote:
Hi,
Not realizing I was looking at EOL dates, I (unintentionally) prov
Hi,
Not realizing I was looking at EOL dates, I (unintentionally) provided
some wrong info yesterday:
On Tue, Jul 18, 2017 at 5:13 PM, Andrey Andreev wrote:
>
> - HttpOnly was released with PHP 5.2.0 in January 2011 - just 3 months prior
> to IETF RFC 6265 (April 2011) becoming a standards track
Hi Sara
2017-07-19 15:34 GMT+02:00 Sara Golemon :
> There's some (admittedly limited) benefit to having such instructions
> in tree. Is there any way this can be auto-generated from docbook
> sources? We could easily add it to the release process.
I think it would be fairly easy, for me persona
Hi Jan,
> -Original Message-
> From: Jan Ehrhardt [mailto:php...@ehrhardt.nl]
> Sent: Tuesday, July 18, 2017 7:11 PM
> To: internals@lists.php.net
> Subject: [PHP-DEV] Re: PHP 7.2 forked
>
> Sara Golemon in php.internals (Tue, 18 Jul 2017 10:48:16 -0400):
> >That's it! Feature freeze is o
On Wed, Jul 19, 2017 at 3:12 AM, Kalle Sommer Nielsen wrote:
> I did a recent commit with some internal cleanup and I noticed both of
> these files are largely outdated, is there any objects of replacing
> their contents with a link to our docs at php.net instead?
>
There's some (admittedly limite
On Wed, Jul 19, 2017 at 9:53 AM, Bartłomiej Krukowski <
krukowski.bartlom...@gmail.com> wrote:
> Hello,
>
> Class *ReflectionProperty* allows to get access to private properties in
> library. Unfortunately there is one unexpected (or at least undocumented)
> case - *ReflectionProperty* tries execu
Hello,
Class *ReflectionProperty* allows to get access to private properties in
library. Unfortunately there is one unexpected (or at least undocumented)
case - *ReflectionProperty* tries execute *__call* method. In my opinion
this approach is bad, because method *__call* can change state of
appli
Howdy
I did a recent commit with some internal cleanup and I noticed both of
these files are largely outdated, is there any objects of replacing
their contents with a link to our docs at php.net instead?
Side note, far from all doc people have karma for these two files, and
they are largely uncha
34 matches
Mail list logo
