Everything

php

Home » Project » Newsgroups » php.internals » Official Twitter Account »

Official Twitter Account

php.internals

Trevor Suarez

7 years ago

I'm not sure who runs the "official_php" Twitter account, but its supposed
to be THE account and is verified on Twitter (a relatively big deal as far
as account status goes on Twitter).

In any case, I feel like its usually the last place where I see
announcements made. For example, there's no tweet yet about the
announcement/availability of the PHP 7.3.0 release.

Its not a huge deal, really, but I follow a lot of PHP community members
that have all tweeted about 7.3.0 and I'd like to point people to the
official account for official announcements.

Maybe, in the future, tweeting from that account can be made a part of
coordinating an announcement? Just a thought. :)


- Trevor Suarez
https://trevorsuarez.com/

Sara Golemon

7 years ago

On Thu, Dec 6, 2018 at 11:09 AM Trevor Suarez <rican7@gmail.com> wrote:

> In any case, I feel like its usually the last place where I see
> announcements made.

I'll take exception to that.  I've been pushing both branches of the last
several releases, and tweeting about it just after the announcements are
visible on news.php.net.
So no, if it's the last place you're seeing it, then you're only visiting
fortune tellers.

> For example, there's no tweet yet about the
> announcement/availability of the PHP 7.3.0 release.
>
> Because I batch them, and the 7.0.33 announcement hasn't gone out yet.

When that announcement happens, you'll see a tweet.

> Its not a huge deal, really, but I follow a lot of PHP community members
> that have all tweeted about 7.3.0 and I'd like to point people to the
> official account for official announcements.
>

Because Europeans have different sleeping hours than Americans.

Nikita Popov

7 years ago

On Thu, Dec 6, 2018 at 7:08 PM Sara Golemon <pollita@php.net> wrote:

> On Thu, Dec 6, 2018 at 11:09 AM Trevor Suarez <rican7@gmail.com> wrote:
>
> > In any case, I feel like its usually the last place where I see
> > announcements made.
>
> I'll take exception to that.  I've been pushing both branches of the last
> several releases, and tweeting about it just after the announcements are
> visible on news.php.net.
> So no, if it's the last place you're seeing it, then you're only visiting
> fortune tellers.
>
>
> > For example, there's no tweet yet about the
> > announcement/availability of the PHP 7.3.0 release.
> >
> > Because I batch them, and the 7.0.33 announcement hasn't gone out yet.
> When that announcement happens, you'll see a tweet.
>

Given that the PHP 7.3 release announcement is somewhat more significant
than our usual maintenance releases, maybe that one could be done
separately?

Nikita

Sara Golemon

7 years ago

On Thu, Dec 6, 2018 at 12:14 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Given that the PHP 7.3 release announcement is somewhat more significant
> than our usual maintenance releases, maybe that one could be done
> separately?
>
> Given that the migration guide link is currently pointing at dead air,

I'll probably give Christoph some time to fix that.
http://php.net/manual/en/migration73.php

-Sara

Trevor Suarez

7 years ago

On Thu, Dec 6, 2018 at 11:29 AM Sara Golemon <pollita@php.net> wrote:

> On Thu, Dec 6, 2018 at 12:14 PM Nikita Popov <nikita.ppv@gmail.com> wrote:
>
>> Given that the PHP 7.3 release announcement is somewhat more significant
>> than our usual maintenance releases, maybe that one could be done
>> separately?
>>
>> Given that the migration guide link is currently pointing at dead air,
> I'll probably give Christoph some time to fix that.
> http://php.net/manual/en/migration73.php
>
> -Sara
>

Yea, I noticed that too. I also noticed that all of the feature/change
links on the release announcement page <http://php.net/releases/7_3_0.php>
are linked to GitHub anchors of the UPGRADING doc, rather than RFC Wiki
links like they have been in the past <http://php.net/releases/7_2_0.php>.

Christoph Becker

7 years ago

On 06.12.2018 at 19:59, Trevor Suarez wrote:

> On Thu, Dec 6, 2018 at 11:29 AM Sara Golemon <pollita@php.net> wrote:
>
>> On Thu, Dec 6, 2018 at 12:14 PM Nikita Popov <nikita.ppv@gmail.com> wrote:
>>
>>> Given that the migration guide link is currently pointing at dead air,
>> I'll probably give Christoph some time to fix that.
>> http://php.net/manual/en/migration73.php
>
> Yea, I noticed that too. I also noticed that all of the feature/change
> links on the release announcement page <http://php.net/releases/7_3_0.php>
> are linked to GitHub anchors of the UPGRADING doc, rather than RFC Wiki
> links like they have been in the past <http://php.net/releases/7_2_0.php>.

Sorry, missed to commit an important change in doc-base yesterday, so
the migration guide will likely be rolled out in about six hours only.
This is why I linked to UPGRADING in the release announcement on php.net
(I'll fix that when the migration guide is available), and why I wrote
“will be available in the PHP Manual, shortly” in the announcement mails.

Sorry, again, for the inconvenience.

(Maybe someone wants to have a look at bug #77246; having docs.php.net
available is really helpful for such issues.  It wouldn't have prevented
the missing migration guide, but I would now know for sure, whether the
migration guide will be rolled out tonight.)

--
Christoph M. Becker

Björn Larsson

7 years ago

Den 2018-12-06 kl. 19:59, skrev Trevor Suarez:

> On Thu, Dec 6, 2018 at 11:29 AM Sara Golemon <pollita@php.net> wrote:
>
>> On Thu, Dec 6, 2018 at 12:14 PM Nikita Popov <nikita.ppv@gmail.com> wrote:
>>
>>> Given that the PHP 7.3 release announcement is somewhat more significant
>>> than our usual maintenance releases, maybe that one could be done
>>> separately?
>>>
>>> Given that the migration guide link is currently pointing at dead air,
>> I'll probably give Christoph some time to fix that.
>> http://php.net/manual/en/migration73.php
>>
>> -Sara
>>
> Yea, I noticed that too. I also noticed that all of the feature/change
> links on the release announcement page <http://php.net/releases/7_3_0.php>
> are linked to GitHub anchors of the UPGRADING doc, rather than RFC Wiki
> links like they have been in the past <http://php.net/releases/7_2_0.php>.

This was something that I also noticed, earlier all references was
pointing to a
*.php.net site in the release announcement. For 7.x releases mostly RFCs was
listed. Should the announcement be updated pointing to a non github adress?

r//Björn Larsson

Christoph Becker

7 years ago

On 06.12.2018 at 21:46, Björn Larsson wrote:

> This was something that I also noticed, earlier all references was
> pointing to a
> *.php.net site in the release announcement. For 7.x releases mostly RFCs
> was
> listed. Should the announcement be updated pointing to a non github adress?

Yes.  However, only two (and a half) of the features could be linked to
RFCs, and the migration guide has not yet been rolled out.  I'll fix
this as soon as possible.

--
Christoph M. Becker

Björn Larsson

7 years ago

Den 2018-12-07 kl. 00:00, skrev Christoph M. Becker:

> On 06.12.2018 at 21:46, Björn Larsson wrote:
>
>> This was something that I also noticed, earlier all references was
>> pointing to a *.php.net site in the release announcement. For 7.x
>> releases mostly RFCs was listed. Should the announcement be updated
>> pointing to a non github adress?
> Yes.  However, only two (and a half) of the features could be linked to
> RFCs, and the migration guide has not yet been rolled out.  I'll fix
> this as soon as possible.

Thanks a million :) One thing I missed as a highlight in the announcement
was the JSON RFC, it's a clear improvement in error handling, maybe also
the list RFC implementing a 16 year old feature request...

OTOH, the announcement is out so maybe that train has left the station ;-)

r//Björn L

Christoph Becker

7 years ago

On 07.12.2018 at 00:47, Björn Larsson wrote:

> Thanks a million :) One thing I missed as a highlight in the announcement
> was the JSON RFC, it's a clear improvement in error handling, maybe also
> the list RFC implementing a 16 year old feature request...

It seems to me that all users have their own favorites.  For instance,
somebody never using LDAP is certainly not interested in any news
regarding this extension.  Even the switch to PCRE2 may not be
interesting for many users, since the changes are supposed to be mostly
transparent.  And of course, others may be delighted to know that array
destructuring now supports reference assignments.

So I suggest to read the whole migration guide (and also have a look at
updates to it; seems some stuff is yet missing), anyway.

> OTOH, the announcement is out so maybe that train has left the station ;-)

I'd say yes. :)

--
Christoph M. Becker

Trevor Suarez

7 years ago

On Thu, Dec 6, 2018 at 11:08 AM Sara Golemon <pollita@php.net> wrote:

> On Thu, Dec 6, 2018 at 11:09 AM Trevor Suarez <rican7@gmail.com> wrote:
>
>> In any case, I feel like its usually the last place where I see
>> announcements made.
>
> I'll take exception to that.  I've been pushing both branches of the last
> several releases, and tweeting about it just after the announcements are
> visible on news.php.net.
> So no, if it's the last place you're seeing it, then you're only visiting
> fortune tellers.
>
>
>> For example, there's no tweet yet about the
>> announcement/availability of the PHP 7.3.0 release.
>>
>> Because I batch them, and the 7.0.33 announcement hasn't gone out yet.
> When that announcement happens, you'll see a tweet.
>
>
>> Its not a huge deal, really, but I follow a lot of PHP community members
>> that have all tweeted about 7.3.0 and I'd like to point people to the
>> official account for official announcements.
>>
>
> Because Europeans have different sleeping hours than Americans.
>
>
>> Maybe, in the future, tweeting from that account can be made a part of
>> coordinating an announcement? Just a thought. :)
>>
>> It is already.
>

Haha, all fair points.

What made me actually post this though, is that I saw you personally tweet
about it, Sara, along with a few others, and didn't see it on the official
account.

Sorry if I was way off base here. Keep up the good work. :)

Good Guy

7 years ago

On 06/12/2018 18:08, Sara Golemon wrote:

> Because Europeans have different sleeping hours than Americans.
>
>

No the hours are the same;  Time Zones are different; :-) :-) :-)

Kris Craig

7 years ago

On Thu, Dec 6, 2018 at 10:08 AM Sara Golemon <pollita@php.net> wrote:

> On Thu, Dec 6, 2018 at 11:09 AM Trevor Suarez <rican7@gmail.com> wrote:
>
> > In any case, I feel like its usually the last place where I see
> > announcements made.
>
> I'll take exception to that.  I've been pushing both branches of the last
> several releases, and tweeting about it just after the announcements are
> visible on news.php.net.
> So no, if it's the last place you're seeing it, then you're only visiting
> fortune tellers.
>
>
> > For example, there's no tweet yet about the
> > announcement/availability of the PHP 7.3.0 release.
> >
> > Because I batch them, and the 7.0.33 announcement hasn't gone out yet.
> When that announcement happens, you'll see a tweet.
>
>
> > Its not a huge deal, really, but I follow a lot of PHP community members
> > that have all tweeted about 7.3.0 and I'd like to point people to the
> > official account for official announcements.
> >
>
> Because Europeans have different sleeping hours than Americans.
>
>
> > Maybe, in the future, tweeting from that account can be made a part of
> > coordinating an announcement? Just a thought. :)
> >
> > It is already.
>

Have we ever considered automating these social media posts?  Not just
Twitter, but Reddit, as well.   A bot could be setup to monitor for
announcements and repost them to social media without it having to be done
manually.

--Kris

Sara Golemon

7 years ago

On Fri, Dec 7, 2018 at 12:38 AM Kris Craig <kris.craig@gmail.com> wrote:

> Have we ever considered automating these social media posts?  Not just
> Twitter, but Reddit, as well.   A bot could be setup to monitor for
> announcements and repost them to social media without it having to be done
> manually.
>
> It's not a terrible idea. We've got an API to list current releases....

somewhere (if not, making one is trivial given our data structures).
Having a cron job live somewhere with an API key is a small step from
there.

The hard part is deciding on the text.  For example, "this is a security
(or bugfix) release" is salient.  Personally, I quite enjoy giving
flavorful announcements.  Lastly, there's noise; I think that usually we'll
want these to be batched, and each branch has a different RM (except when
I'm doing 7.1 for joe).

-Sara