On Fri, Nov 19, 2021 at 5:38 AM Rowan Tommins
wrote:
> Perhaps there should be a section at the end of the 8.1 page saying
> something like "If you're still on PHP 7.x, upgrading gets you all this
> as well!" with the headlines from the 8.0 page, and a link through.
>
>
^^ This. Maybe even a
On 19/11/2021 09:38, Giovanni Giacobbi wrote:
Why don't you guys keep the same page for the whole 8.x series? You just
need to drop the ".0" and append at the end (maybe stating what's new from
8.1 specifically). The rationale is that people will be migrating from 7.x
for a long time (hell, I'm
On Fri, 19 Nov 2021 at 10:13, Pierre wrote:
> Le 19/11/2021 à 10:10, Kamil Tekiela a écrit :
> > I would suggest option number 5. Leave it as it is. Many people are still
> > not aware that PHP 8 has been released.
> > If that's not possible, then we should keep the page (opt 3), otherwise
> we
Le 19/11/2021 à 10:10, Kamil Tekiela a écrit :
I would suggest option number 5. Leave it as it is. Many people are still
not aware that PHP 8 has been released.
If that's not possible, then we should keep the page (opt 3), otherwise we
will be breaking links to it, e.g. on Stack Overflow.
Adding
I would suggest option number 5. Leave it as it is. Many people are still
not aware that PHP 8 has been released.
If that's not possible, then we should keep the page (opt 3), otherwise we
will be breaking links to it, e.g. on Stack Overflow.
Adding PHP 8.1 alongside would be great, but we already
On Fri, Nov 19, 2021 at 2:35 AM Nikita Popov wrote:
> On Fri, Nov 19, 2021 at 4:16 AM Sara Golemon wrote:
>
>> In seven days, https://www.php.net/releases/8.0/en.php is going to be
>> obsolete.
>>
>> Well, that's a harsh term, but it certainly won't reflect the current
>> state
>> on the
On Fri, Nov 19, 2021 at 4:16 AM Sara Golemon wrote:
> In seven days, https://www.php.net/releases/8.0/en.php is going to be
> obsolete.
>
> Well, that's a harsh term, but it certainly won't reflect the current state
> on the ground, and we need to decide (should have decided, weeks ago) what
>
In seven days, https://www.php.net/releases/8.0/en.php is going to be
obsolete.
Well, that's a harsh term, but it certainly won't reflect the current state
on the ground, and we need to decide (should have decided, weeks ago) what
we're going to do with it.
1/ Make a new announcement page for
On Mon, 19 Oct 2020 at 15:54, Roman Pronskiy
wrote:
> On Fri, Oct 16, 2020 at 1:51 AM Gabriel Caruso
> wrote:
> >
> > Roman,
> >
> > One question that I've received from a couple of communities about this
> proposal: can we have translations of this page? Portuguese, French,
> Russian, etc.
> >
On Fri, Oct 16, 2020 at 1:51 AM Gabriel Caruso
wrote:
>
> Roman,
>
> One question that I've received from a couple of communities about this
> proposal: can we have translations of this page? Portuguese, French, Russian,
> etc.
>
>From a technical perspective, I assume it should be possible to
Hi folks,
Thank you all for the feedback. Here is a quick recap of where the
matter stands.
1. It seems there’s a consensus that it would be great if the PHP 8
release had a nice sharable release announcement page. But we need to
keep neutrality.
We’ll update the concept to remove potentially
I can handle the French one if you need someone.
Just send me the texts!
— Benjamin
On Mon, 19 Oct 2020 at 15:59, Sergey Panteleev
wrote:
> Hi there!
>
> I'm also ready to help with Russian translation
>
> wbr,
> Sergey Panteleev
> On 19 Oct 2020, 16:54 +0300, Roman Pronskiy ,
> wrote:
> >
> >
Hi there!
I'm also ready to help with Russian translation
wbr,
Sergey Panteleev
On 19 Oct 2020, 16:54 +0300, Roman Pronskiy ,
wrote:
>
> From a technical perspective, I assume it should be possible to reuse
> php.net/manual/ mechanism for translations.
>
> As for the texts, the only way we can
On Thu, Oct 15, 2020 at 9:25 AM Benjamin Eberlei
wrote:
>
> 1. October: RMs and/or php-web maintainers should give their go on the
idea
> (someone else?), so that more detailed creative time investment is not
> going to waste.
FTR they came to Gabriel and I *first*. Sounded like a neat idea to
On Mon, 12 Oct 2020 at 09:57, Roman Pronskiy
wrote:
> Hello Internals,
>
> The PHP 8 release is going to be huge, and in some sense, you could
> say it's a whole new language. There is a feeling that more can be
> done to promote it more extensively.
>
> Usually for releases, there’s a short
> On Oct 15, 2020, at 11:32, Larry Garfield wrote:
>
> On Thu, Oct 15, 2020, at 11:17 AM, Ben Ramsey wrote:
>
>> If there’s interest in turning this into a community project outside
>> the official PHP project, I’d be interested in helping coordinate the
>> efforts, in addition to the use of
On Thu, Oct 15, 2020, at 11:17 AM, Ben Ramsey wrote:
> If there’s interest in turning this into a community project outside
> the official PHP project, I’d be interested in helping coordinate the
> efforts, in addition to the use of the domain gophp8.dev and hosting.
>
> This way, the PHP
> On Oct 15, 2020, at 10:32, Kalle Sommer Nielsen wrote:
>
> Hi
>
> Den man. 12. okt. 2020 kl. 10.57 skrev Roman Pronskiy
> :
>> https://i.imgur.com/6fKmTyM.jpg
>
> The concept looks great, however in the current state, it cannot go in
> like that which mainly comes down to neutrality.
>
> -
Hi
Den man. 12. okt. 2020 kl. 10.57 skrev Roman Pronskiy
:
> https://i.imgur.com/6fKmTyM.jpg
The concept looks great, however in the current state, it cannot go in
like that which mainly comes down to neutrality.
- This means we cannot display projects such as Symfony, Laravel and
WordPress at
On Wed, Oct 14, 2020 at 1:56 AM tyson andre
wrote:
> Hi internals,
>
> > As far as php.net can help with PHP's reputation, I think a brief
> homepage
> > intro that showcased some modern-looking PHP code would be great (e.g.
> > typescriptlang.org, golang.org). The docs design could also be
> >
>
> > or https://psalm.dev/ (open source) are projects in that area
> > (Matthew Brown is one of the authors of Psalm)
> >
> I don't like the idea of executing that on www.php.net for a few reasons,
> but someone else mentioned the possibility of donated cpu time from
> somewhere that's worth a
On Wed, Oct 14, 2020 at 6:18 AM Dik Takken wrote:
>
> However, then we should also make sure that the example
> code actually works, and on which PHP versions. As soon as examples can
> be run right from the documentation pages, the examples will be run far
> more frequently than they are now,
On Mon, Oct 12, 2020 at 2:10 PM Eliot Lear wrote:
>
> What helps me when I spread the word is if there is a simple page that
> will look good on a retweet/FB/LinkedIn page, with a couple of release
> highlights. It doesn't need to be fancy, but something that flashes a
> big PHP 8.0 logo or some
Hi internals
Regarding the matter of a sandbox, one of my colleagues open sourced a Laravel
sandbox that runs straight in the browser and uses docker containers, with a
little work you can extract away the Laravel part and have it run plain PHP.
Here's the source:
On 14-10-2020 03:41, Larry Garfield wrote:
> This sounds like a fantastic idea. The inline-run capability of Go and
> Rust's documentation is a huge win. Writing good sample code for the
> documentation would be an interesting challenge, but it's the sort of thing
> that can be done over
On Wed, 14 Oct 2020 at 00:56, tyson andre wrote:
> There's two main options available for testing out php in a browser right
> now:
>
> - A general sandboxed php implementation hosted by the owners of php.net
> (requires that it be secured and may lead to additional hosting costs),
>
On Tue, Oct 13, 2020, at 6:56 PM, tyson andre wrote:
> Hi internals,
>
> > As far as php.net can help with PHP's reputation, I think a brief homepage
> > intro that showcased some modern-looking PHP code would be great (e.g.
> > typescriptlang.org, golang.org). The docs design could also be
> >
Hi internals,
> As far as php.net can help with PHP's reputation, I think a brief homepage
> intro that showcased some modern-looking PHP code would be great (e.g.
> typescriptlang.org, golang.org). The docs design could also be
> slightly tweaked to make everything seem newer, while still
Agree, this should be for every release. So with this concept, we can
start from PHP 8.0, see how it works, and then reuse the template for
subsequent releases.
On Mon, Oct 12, 2020 at 12:54 PM Rowan Tommins wrote:
>
> On Mon, 12 Oct 2020 at 08:57, Roman Pronskiy
> wrote:
>
> > The PHP 8
Hi Roman,
I 100% agree with what Benjamin has just written. Marketing PHP as a
modern, thriving
programming language which (mostly) left its dark past behind is very much
needed.
That said, I'm very grateful for this idea, so thank you! I like the design
as well:
it's informative, looks clean,
Hi Roman,
On Mon, Oct 12, 2020 at 9:57 AM Roman Pronskiy
wrote:
> Hello Internals,
>
> The PHP 8 release is going to be huge, and in some sense, you could
> say it's a whole new language. There is a feeling that more can be
> done to promote it more extensively.
>
> Usually for releases,
W/r/t the goals:
– Promote the release of PHP 8 to the PHP developers
> – Promote PHP as a modern language, as well as the PHP 8 release, to the
> general tech audience
The page's design does a *great* job of promoting PHP 8 to existing PHP
developers, but a general tech audience skeptical of
On Mon, 12 Oct 2020 at 15:25, Larry Garfield wrote:
> On Mon, Oct 12, 2020, at 6:10 AM, Eliot Lear wrote:
> > What helps me when I spread the word is if there is a simple page that
> > will look good on a retweet/FB/LinkedIn page, with a couple of release
> > highlights. It doesn't need to be
> On Oct 12, 2020, at 08:24, Larry Garfield wrote:
>
> On Mon, Oct 12, 2020, at 6:10 AM, Eliot Lear wrote:
>> What helps me when I spread the word is if there is a simple page that
>> will look good on a retweet/FB/LinkedIn page, with a couple of release
>> highlights. It doesn't need to be
On Mon, Oct 12, 2020, at 6:10 AM, Eliot Lear wrote:
> What helps me when I spread the word is if there is a simple page that
> will look good on a retweet/FB/LinkedIn page, with a couple of release
> highlights. It doesn't need to be fancy, but something that flashes a
> big PHP 8.0 logo or some
Hello Internals,
The PHP 8 release is going to be huge, and in some sense, you could
say it's a whole new language. There is a feeling that more can be
done to promote it more extensively.
Usually for releases, there’s a short text announcement on php.net.
This may be okay for minor releases and
What helps me when I spread the word is if there is a simple page that
will look good on a retweet/FB/LinkedIn page, with a couple of release
highlights. It doesn't need to be fancy, but something that flashes a
big PHP 8.0 logo or some such as the image as part of the preview would
be quite
Can confirm, Gmail ate the email into spam folder.
On Mon, Oct 12, 2020, 10:16 Lynn wrote:
> On Mon, Oct 12, 2020 at 9:57 AM Roman Pronskiy <
> roman.prons...@jetbrains.com>
> wrote:
>
> > Hello Internals,
> >
>
> Hi, this message ended up in my spam directory with the message, could be
> that
On 12/10/2020 08:56, Roman Pronskiy wrote:
Hello Internals,
The PHP 8 release is going to be huge, and in some sense, you could
say it's a whole new language. There is a feeling that more can be
done to promote it more extensively.
Usually for releases, there’s a short text announcement on
On Mon, 12 Oct 2020 at 08:57, Roman Pronskiy
wrote:
> The PHP 8 release is going to be huge, and in some sense, you could
> say it's a whole new language.
>
I think that's going a bit far. I don't want to detract from the great
features in 8.0, but there were great features in other releases
On 12/10/2020 08:56, Roman Pronskiy wrote:
The PHP 8 release is going to be huge, and in some sense, you could
say it's a whole new language. There is a feeling that more can be
done to promote it more extensively.
HOPEFULLY that does not mean it's as much of a cock-up as Python 2 to
Python 3
Am 12.10.2020 um 09:56 schrieb Roman Pronskiy:
The PHP 8 release is going to be huge, and in some sense, you could
say it's a whole new language. There is a feeling that more can be
done to promote it more extensively.
Agreed!
So, the idea is to create a separate release announcement landing
On Mon, Oct 12, 2020 at 9:57 AM Roman Pronskiy
wrote:
> Hello Internals,
>
Hi, this message ended up in my spam directory with the message, could be
that people missed it. When opening the message, gmail told me: "Gmail
could not verify that it actually came from jetbrains.com. Avoid clicking
43 matches
Mail list logo
