End of goPhp71.org

I launched goPhp71.org in June 2017, just 6 months after release of PHP 7.1. In those times nobody was sure what version to require - 7.1? 7.0? Or wait for 7.2?

Future is now. There is no need for the initiative now and it's time to let it go.
How much did it cost? What was the effect? Was it worth it? I'll share answers to these question so you know what to expect when you start a similar project. Let's get numberz!

When I bought the gophp71.org domain, I had no idea what it will become. You know, try to tell the whole PHP open-source community what min version should they use in composer.json, right? Explain why it's a good idea to work as a community to people you've never met. But when I saw Go PHP 5 I felt it's my duty to give back to PHP community and help with PHP 7.1.

Today it's gonna about numbers, how well PHP community works together and few of mine fuck-ups :)

How Much Did it Cost?

What was The Impact?

I took a while. Thanks to Jordi (thank you!), we have numbers on min. required PHP version on Packagist:

Is 19,4 % to small for you?

What about 38 528? That's the absolute number of packages that required PHP 7.1 in November 2018.


I look forward to May 2019 stats update coming anytime soon.

Correlation !== Causality

I don't think one website changed the PHP world. We made it together as one community. I tried to convince David from PHP 7.0 to PHP 7.1 over lunch. I thought I lost him not having enough arguments and Nette will go with PHP 7.0. Later that month Nette went 7.1 as one of the first PHP frameworks - it was not stable, but still had a big effect on Czech open-source maintainers 👍

There was a sparkle of hope this might work.


Fabien from Symfony helped by opening a pool on Twitter:

Over 1000 people helped this in that pool! To sum it up - 1003 specific people so far 👍


Doctrine team also helped with PHP 7.1 announcement for all their packages. They also explained very nicely Why dropping PHP support in a minor version is not a BC break 👍

"A BC break happens when there is an incompatible change that your package manager can't handle. For example, changing a method signature in a minor version is a no-go, since the composer version constraints mentioned above assume any minor upgrade can safely be used."

Remember this quote, we'll need it when we'll go PHP 8.1 (maybe?) later.


Over 19 PHP projects have added their go PHP 7.1 statement to the website in the 1st year. Thank you' all! 👍

Last but not the least, the_alias_of_andrea helped spread the news on Reddit 👍


"Sure Tom, good job... you're the best, but we're really reading just for your fuck-ups."

All right...

What I Fucked Up?

Too Complicated Wording

I wrote "add your project too" instructions on the website, so all projects could join. I learned that people don't understand my complicated thoughts.

Instead of keeping it as simple as:

I created a mess like this:

That led to hanged PRs, manual yes/no corrections that didn't have much-added value and confused comments from contributors (I'm sorry about that).

Too Late

I fucked up timing. PHP 7.1 was released in December 2016, yet gophp71.org was not launched until 7 months later. I had the idea before, but I was afraid how will you react. I had thoughts like "Who the hell is this Votruba and why does he think he is that he tells us what PHP version should we use?" or "Do you want us to go PHP 7.1? Well, we'll go PHP 7.0 on one project and PHP 7.2 on the other, a-ha!" or "What is he selling us? That's some version conspiracy!"

Now I see that was stupid. I should start earlier, try it, give a go and adapt upon the feedback.


That's all folks, hope you enjoyed it! I sure did start almost 24 months ago with just this:

What's Going to be Next?

Will we "Go PHP 8"? Someone from Arizona, US already bought the gophp8.org domain. Or 8.1, when 8 becomes more mature?

Who knows. All I know I'm very happy to be part of our PHP community family ❤️️, where we support each other despite our differences and work together when we need to.


Happy coding!