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

, Jan 13, 2016 at 1:26 AM, Sascha Schumann < sascha.schum...@myrasecurity.com> wrote: > > On January 12, 2016 at 7:05 PM Adam Howard <oldschool...@gmail.com> > wrote: > > > > Can we please move on past this and get back to actual code. Because if > >

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

filter or just don't open the emails. Its not > that hard. > > > On Wed, Jan 13, 2016 at 8:52 AM John Bafford <jbaff...@zort.net> wrote: > >> Adam, Sascha, >> >> > On Jan 13, 2016, at 08:53, Adam Howard <oldschool...@gmail.com> wrote: >> > &

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

I honestly think most of the people who have replied dragging on this nonsense have been top-posting, so you'll excuse me if I feel that argument is moot. On Wed, Jan 13, 2016 at 10:53 AM, Peter Lind <peter.e.l...@gmail.com> wrote: > On 13 January 2016 at 16:49, Adam Howard &

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

an actual draft (solution). On Wed, Jan 13, 2016 at 9:51 AM, John Bafford <jbaff...@zort.net> wrote: > Adam, Sascha, > > > On Jan 13, 2016, at 08:53, Adam Howard <oldschool...@gmail.com> wrote: > > > > Well, I'm glad someone is in agreement. I really wis

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

Can we please move on past this and get back to actual code. Because if not, perhaps PHP Internals has outgrown the email format and should migrate to a forum type format. On Tue, Jan 12, 2016 at 11:45 AM, Pierre Joye wrote: > On Jan 12, 2016 11:17 PM, "Sascha Schumann" <

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

First and foremost, as PHP is an open source project and the lifeblood of any open source project is accepting that people do come (and go). I've been watching internals for a few years and that is clearly obvious. So it seems silly for any open source project to argue against newcomers. On

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

I question if there is a way to keep all communication in PHP Internals on PHP Internals, which would minimize the risk of someone reaching someone outside of PHP Internals. By that I mean, as it stands now, everyone's email is public and someone meaning to cause or threaten harm could personally

Re: [PHP-DEV] PHP 5 Support Timeline - voting in January

Seasons Greetings and Happy Holidays to everyone at PHP and in the mailing list. May the new year bring you all good health and good fortune. On Sun, Dec 20, 2015 at 4:46 AM, Zeev Suraski wrote: > All, > > > > While in theory we could go to a vote already, I’d like to wait with

Re: [PHP-DEV] [RFC] [VOTE] Add HTTP/2 Server Push Support to ext/curl

YES On Wed, Dec 9, 2015 at 1:51 PM, Davey Shafik wrote: > Hey folks, > > It's been 3 weeks since I first put this up on the ML and there has been no > changes proposed, so I'm moving forward with a vote. > > It's a simple Yes/No 50%+1 majority required as it's not a language

Re: [PHP-DEV] PHP 5.6 life cycle

The EOL (end of life) date does influence people. True, not everyone will simply jump ship upon EOL. But it is still has a significant enough influence on adoption and urgency in general. Especially toward new development projects or new releases in general that are less likely to code with

Re: [PHP-DEV] RFC: PHP 5.6 Support Timeline

#3 all the way. Extending support only extends the excuse of poor habits and encourages those habits. On Tue, Dec 8, 2015 at 2:13 PM, Scott Arciszewski wrote: > On Tue, Dec 8, 2015 at 10:14 AM, Zeev Suraski wrote: > > > Following the initial discussion, I

Re: [PHP-DEV] PHP 5.6 life cycle

I see the same people who had a problem with the EOL (end of life) date for 5.4, 5.5, are going to be the same people who have a problem with 5.6 EOL. Extended the support will only enable those and others to validate their excuse for not needing to migrate to the new code base. I agree, a date

Re: [PHP-DEV] PHP 5.6 life cycle

2016, not 2017. Extended support for nearly 2 years is a bad idea and only further enables bad practices. On Mon, Dec 7, 2015 at 9:32 AM, Adam Howard <oldschool...@gmail.com> wrote: > I see the same people who had a problem with the EOL (end of life) date > for 5.4, 5.

Re: [PHP-DEV] Re: PHP 5.6 life cycle

OS's (CentOS/Debian) for example do offer official upgrade paths via their own repositories and 3rd party repositories. However has history has shown extended support only extends the resistance to update those paths, Alain Williams While the PHP Development Team obviously cannot control the

Re: [PHP-DEV] PHP 5.6 life cycle

Adding extended support does justify (provide an excuse) for others not adapt or upgrade to new code. While PHP Development obvious cannot control the actions of others (obviously), extending support does unintentionally enables poor practices. Once support is ended, people do begin to migrate.

Re: [PHP-DEV] Re: PHP 5.6 life cycle

This is the current official timeline http://php.net/supported-versions.php I personally think it is long enough and would actually suggestion shortening it (2016, not 2017). Extended the timeline would only further influence people not to upgrade, as an excuse that it was still supported. On

Re: [PHP-DEV] PHP 5.6 life cycle

I think 5.6 should not be extended. It should be treated like any other release and given the same length of time originally planned for any previous release. It should not be the responsibility of PHP Development to be used as an excuse not to update adapt to newer code standards. Which is

Re: [PHP-DEV] PHP 5.6 life cycle

. No one is going to force you to update, but it should not be PHP Development's strance to further enable people to use old code. On Sun, Dec 6, 2015 at 7:38 PM, Scott Arciszewski <sc...@paragonie.com> wrote: > On Sun, Dec 6, 2015 at 7:33 PM, Jan Ehrhardt <php...@ehrhardt.nl> wr

Re: [PHP-DEV] PHP 5.6 life cycle

I agree with Scott. With each extension we only seem to be enabling people with bad habits. 8 months is almost a full year and more than enough time. On Sun, Dec 6, 2015 at 6:51 PM, Scott Arciszewski wrote: > On Sun, Dec 6, 2015 at 6:17 PM, Stanislav Malyshev

Re: [PHP-DEV] PHP 5.6 life cycle

8 months is fine. It is more than enough time for people to upgrade and adapt. Extending support longer only extends the excuse for other developments not to upgrade and adapt, as history has proven time and time again. On Sun, Dec 6, 2015 at 5:38 PM, François Laupretre

Re: [PHP-DEV] PHP 7.0.0 final RTM delay

With the holiday season quickly approaching and with more developers taking time off as a result, I would like to again propose (suggest) that January 2016 release maybe more appropriate. I would not wish for PHP development to rush to release and I feel it would give everyone more time to review

Re: [PHP-DEV] PHP 7.0.0 final RTM delay

Disregard. I now see that a completed build was released. On Thu, Dec 3, 2015 at 6:11 PM, Adam Howard <oldschool...@gmail.com> wrote: > With the holiday season quickly approaching and with more developers > taking time off as a result, I would like to again propose (suggest) that &g

Re: [PHP-DEV] Re: PHP 7 ?! :)

I asked the same question. Congratulations on successfully releasing 7.0 On Thu, Dec 3, 2015 at 6:06 PM, Stanislav Malyshev wrote: > Hi! > > > Never mind. It returned. Congratulations everyone! > > Congratulations to us all and many thanks to those who worked tirelessly >

Re: [PHP-DEV] Changes in 7.0 RMs team

I would like to thank Kalle for the work and dedicated he previously offered to PHP. And of course thanks to all the current developers that continue with PHP. On Mon, Nov 30, 2015 at 4:42 AM, wrote: > Hi, > > I'm writing to inform the community that from now on Kalle is

Re: [PHP-DEV] PHP 7 RTM date

I love that The PHP Development Team is not looking to rush a release and while I, like many others wish to see PHP 7.0 I would rather have a stable and solid release over the idea of a rushed release. So I commend the choice of releasing another RC (RC7) coming up in the next few days There

Re: [PHP-DEV] Re: Small regression in PHP-LDAP

I don't think it is possible to make everyone happy all the time. I think this should be kept for a user code fix. On Thu, Nov 5, 2015 at 2:37 PM, Ferenc Kovacs wrote: > On Thu, Nov 5, 2015 at 5:38 PM, Bishop Bettini wrote: > > > On Thu, Nov 5, 2015 at 8:56

Re: [PHP-DEV] PHP 7.0.0RC6 is available

I am confident that critical bugs will be resolved before release. And if I am not mistaken, Drupal themselves found a fix. However, it should go without saying that the November 12 deadline could be pushed back if necessary. On Thu, Oct 29, 2015 at 9:49 AM, Anthony Ferrara