50 |
--------------------------------------------------------------------------------
/source/_pages/code-of-conduct.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Code of Conduct
3 | description: The PHP Foundation Code of Conduct
4 | permalink: code-of-conduct
5 | layout: page
6 | ---
7 |
8 | ### Our Pledge
9 |
10 | We as members, contributors, and leaders pledge to make participation in our
11 | community a harassment-free experience for everyone, regardless of age, body
12 | size, visible or invisible disability, ethnicity, sex characteristics, gender
13 | identity and expression, level of experience, education, socio-economic status,
14 | nationality, personal appearance, race, caste, color, religion, or sexual
15 | identity and orientation.
16 |
17 | We pledge to act and interact in ways that contribute to an open, welcoming,
18 | diverse, inclusive, and healthy community.
19 |
20 | ### Our Standards
21 |
22 | Examples of behavior that contributes to creating a positive environment
23 | include:
24 |
25 | - Demonstrating empathy and kindness toward other people
26 | - Being respectful of differing opinions, viewpoints, and experiences
27 | - Giving and gracefully accepting constructive feedback
28 | - Accepting responsibility and apologizing to those affected by our mistakes,
29 | and learning from the experience
30 | - Focusing on what is best not just for us as individuals, but for the overall
31 | community
32 |
33 | Examples of unacceptable behavior include:
34 |
35 | - The use of sexualized language or imagery, and sexual attention or advances of
36 | any kind
37 | - Trolling, insulting or derogatory comments, and personal or political attacks
38 | - Public or private harassment
39 | - Publishing others’ private information, such as a physical or email address,
40 | without their explicit permission
41 | - Other conduct which could reasonably be considered inappropriate in a
42 | professional setting
43 |
44 | ### Our Responsibilities
45 |
46 | CoC Active Response Ensurers (CARE) team members
47 | are responsible for clarifying and enforcing our standards of acceptable
48 | behavior **within the scope of PHP Foundation activities and spaces**.
49 | They are not responsible for adjudicating disputes or behaviors occurring in external communities or organizations, unless those actions directly affect the Foundation’s activities or its community spaces.
50 |
51 | CARE team members have the right and responsibility to remove, edit, or reject
52 | comments, commits, code, wiki edits, issues, and other contributions that are
53 | not aligned to this Code of Conduct, and will communicate reasons for moderation
54 | decisions when appropriate.
55 |
56 | ### Scope
57 |
58 | This Code of Conduct applies within all PHP Foundation-managed spaces (e.g., events, repositories, communication channels) and to all individuals officially representing the Foundation in those contexts.
59 |
60 | It does not extend to actions or disputes occurring solely within third-party communities or companies unless those actions directly and substantially affect Foundation operations or participants in our spaces.
61 |
62 | ### Sponsorship and Membership
63 |
64 | Sponsorship of the PHP Foundation is a financial contribution that supports our mission. Sponsorship does not imply governance rights, or endorsement of the sponsor’s actions, products, or policies.
65 |
66 | Members of the Foundation (e.g., Staff, Board and Advisory Board participants) are expected to uphold the Code of Conduct in all Foundation-related contexts. However, the Foundation does not assume responsibility for the actions of these individuals or their companies outside the scope of Foundation activities, unless those actions materially impact the Foundation’s work or violate this Code in our official spaces.
67 |
68 | ### Neutrality
69 |
70 | The PHP Foundation maintains a position of neutrality in disputes between companies, communities, and individuals within the broader PHP ecosystem. We focus on supporting PHP’s development and growth. The Foundation will not intervene in external disputes unless directly required to protect its contributors, events, or resources.
71 |
72 | ### Enforcement
73 |
74 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
75 | reported by contacting the CARE team members. All complaints will be reviewed
76 | and investigated promptly and fairly.
77 |
78 | CARE team members are obligated to respect the privacy and security of the
79 | reporter of any incident.
80 |
81 | ### Enforcement Guidelines
82 |
83 | The CARE team members will follow these Community Impact Guidelines in
84 | determining the consequences for any action they deem in violation of this Code
85 | of Conduct:
86 |
87 | #### 1. Correction
88 |
89 | **Community Impact:** Use of inappropriate language or other behavior deemed
90 | unprofessional or unwelcome in the community.
91 |
92 | **Consequence:** A private, written warning from a CARE team member,
93 | providing clarity around the nature of the violation and an
94 | explanation of why the behavior was inappropriate. A public apology
95 | may be requested.
96 |
97 | #### 2. Warning
98 |
99 | **Community Impact:** A violation through a single incident or series of actions.
100 |
101 | **Consequence:** A warning with consequences for continued behavior. No interaction
102 | with the people involved, including unsolicited interaction with those enforcing
103 | the Code of Conduct, for a specified period of time. This includes avoiding
104 | interactions in community spaces as well as external channels like social media.
105 | Violating these terms may lead to a temporary or permanent ban.
106 |
107 | #### 3. Temporary Ban
108 |
109 | **Community Impact:** A serious violation of community standards, including
110 | sustained inappropriate behavior.
111 |
112 | **Consequence:** A temporary ban from any sort of interaction or public
113 | communication with the community for a specified period of time. No public or
114 | private interaction with the people involved, including unsolicited interaction
115 | with those enforcing the Code of Conduct, is allowed during this period.
116 | Violating these terms may lead to a permanent ban.
117 |
118 | #### 4. Permanent Ban
119 |
120 | **Community Impact:** Demonstrating a pattern of violation of community standards,
121 | including sustained inappropriate behavior, harassment of an individual, or
122 | aggression toward or disparagement of classes of individuals.
123 |
124 | **Consequence:** A permanent ban from any sort of public interaction within the
125 | community.
126 |
127 | ### Attribution
128 |
129 | This Code of Conduct is adapted from the Contributor Covenant, version 2.1,
130 | available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131 |
132 | Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
133 |
134 | ### Related Documents
135 |
136 | - [Contributor Covenant](https://www.contributor-covenant.org)
137 | - [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity)
138 |
139 |
--------------------------------------------------------------------------------
/source/_pages/contact.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Contact The PHP Foundation
3 | permalink: contact
4 | layout: page
5 | ---
6 |
7 | Please email our team with general inquiries at [contact@thephp.foundation](mailto:contact@thephp.foundation).
8 |
9 | We will get back to you as soon as possible.
10 |
11 | Follow us on social media:
12 |
13 | - [Twitter](https://twitter.com/thephpf)
14 | - [LinkedIn](https://www.linkedin.com/company/phpfoundation/)
15 | - [Mastodon](https://phpc.social/@thephpf)
16 |
17 | {% include "newsletter.html" %}
18 |
--------------------------------------------------------------------------------
/source/_pages/foundation.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: What we do
3 | permalink: foundation
4 | layout: page
5 | ---
6 |
7 | ## Governance
8 |
9 | The current group collective administration focuses on maintaining the continuity of the PHP project,
10 | in particular on hiring, supporting, and guiding PHP project developers.
11 | The Administration also encourages other Financial Contributors and explores strategic partnerships and needs for the PHP project.
12 |
13 | The Administration consists of veteran PHP core developers, PHP community leaders,
14 | representatives of the founding companies, and other key stakeholders.
15 | In 2022, this is an invitation-only group, while we’re working to get our processes solidified.
16 |
17 | To promote transparency, we operate as a [collective on the Open Collective platform](https://opencollective.com/phpfoundation),
18 | through which we ensure certain activities, such as selection and financing of PHP core developers contributing
19 | to the development of the PHP language. The decisions about these activities are taken by
20 | consensus by the administration members, which meet regularly, and are executed by the
21 | collective administrators.
22 |
23 | All administration members of the PHP Foundation as well as contributors and PHP developers are
24 | expected to abide by the [Code of Conduct](/code-of-conduct) and follow our collective expectations
25 | guidelines and [Terms of Service](https://opencollective.com/tos) of the platform operated by Open Collective Inc.
26 |
27 | ## Foundation Activities
28 |
29 | The primary task of the PHP Foundation is to fund developers to work on PHP. Funds collected
30 | through the Open Collective platform may be used in the first place to engage the services of
31 | PHP developers to further advance the development and maintenance of the language.
32 |
33 | The current Request for Comments (RFC) is not affiliated to the PHP Foundation, and the language
34 | decisions are the matter of the PHP Internals community.
35 |
36 | ## Team Timeline
37 |
38 | We established the following timeline for team review.
39 |
40 | * January 2024: Developers start work according to the new contracts.
41 | * May 2024: Evaluate new developers, contracts are extended, expanded, or terminated after the first 6 months.
42 | * September 2024: Open applications for new developers, evaluate performance of the current group of developers.
43 | * October 2024: Evaluate applications, work out updates to compensation, decide on a budget.
44 | * November 2024: Renew contracts with existing developers, potentially sign contracts with new developers.
45 |
46 | And in 2025 we start the cycle again.
47 |
--------------------------------------------------------------------------------
/source/_pages/get-involved.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Get Involved
3 | permalink: get-involved
4 | layout: page
5 | ---
6 |
7 |
--------------------------------------------------------------------------------
/source/_pages/privacy-policy.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Privacy Policy
3 | permalink: privacy-policy
4 | layout: page
5 | ---
6 |
7 |
--------------------------------------------------------------------------------
/source/_pages/sponsor.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Sponsor The PHP Foundation
3 | permalink: sponsor
4 | layout: page-wide
5 | redirect:
6 | - join
7 | - donate
8 | ---
9 |
10 | _Shape the future of the language ecosystem and help make PHP sustainable._
11 |
12 | There are many ways you can support the development of the PHP language through The PHP Foundation:
13 |
14 | * [Credit Card](https://opencollective.com/phpfoundation/contribute)
15 | * [PayPal](https://opencollective.com/phpfoundation/contribute)
16 | * [Bank Transfer (ACH direct debit or wire transfer)](https://opencollective.com/phpfoundation/contribute)
17 | * [GitHub Sponsors](https://github.com/sponsors/ThePHPF)
18 |
19 | All financial contributions that we receive and our expenses are [public and fully transparent](https://opencollective.com/phpfoundation#category-BUDGET).
20 |
21 | ## Become a Company Member of The PHP Foundation
22 |
23 | Are you looking to sponsor The PHP Foundation as a company? Become a member and earn additional benefits at the Silver, Gold, or Platinum levels.
24 |
25 | Contact [contact@thephp.foundation](mailto:contact@thephp.foundation) to discuss your membership.
26 | Or [sponsor directly](https://opencollective.com/phpfoundation) to become a member.
27 |
28 | {% include "sponsorship-tiers.html" %}
29 |
30 | ## Yearly and Monthly Sponsorships for The PHP Foundation
31 |
32 | You can achieve Silver, Gold, or Platinum status by making financial contributions throughout the year. Contributions can be made annually, quarterly, or monthly.
33 |
34 | - Once your contributions exceed a certain sponsorship level threshold, either through a one-time donation or cumulative monthly contributions, you immediately become a sponsor at that level.
35 |
36 | - Sponsors are removed from the list at the end of each calendar year if their total contributions for that year do not meet the threshold for their level.
37 |
38 | For example, if you contribute $1,500 monthly in 2024, your total contribution by September will be $12,000, qualifying you as a Silver member for the rest of 2024 and all of 2025.
39 |
40 |
41 |
42 |
Want to learn more?
43 |
44 | See our presentation with the latest information
45 | and insights about The PHP Foundation.
46 |
47 |
55 |
56 | ## Official Info & Docs
57 |
58 | The PHP Foundation operates under the umbrella of [OpenSourceCollective](https://www.oscollective.org/), and we rely on [OpenCollective](https://opencollective.com/phpfoundation) to receive and distribute funds.
59 |
60 | Banking, taxes, legals:
61 | [https://docs.oscollective.org/about/official-info-and-docs](https://docs.oscollective.org/about/official-info-and-docs)
62 |
63 | * [Tax ID & W9](https://docs.oscollective.org/about/official-info-and-docs#tax-id-and-w9)
64 | * [Address & Contact Info](https://docs.oscollective.org/about/official-info-and-docs#address-and-contact-info)
65 |
66 | If you're experiencing any difficulties, require additional information, or would like to support the foundation in any other way, please don't hesitate to contact us at: [contact@thephp.foundation](mailto:contact@thephp.foundation).
67 |
68 |
--------------------------------------------------------------------------------
/source/_partials/sponsors.html:
--------------------------------------------------------------------------------
1 | {% set sponsors = fetch_sponsors() %}
2 | {% if sponsors['Platinum']|length > 0 %}
3 |
68 |
--------------------------------------------------------------------------------
/source/_posts/2022-01-21-the-php-foundation-update-january-2022.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: The PHP Foundation Update, January 2022
3 | description: Monthly updates to the PHP Foundation, January 2022
4 | layout: post
5 | tags:
6 | - update
7 | author:
8 | name: Roman Pronskiy
9 | url: https://twitter.com/pronskiy
10 | published_at: 21 January 2022
11 | ---
12 | ``` We've created an official LinkedIn page: [linkedin.com/company/phpfoundation](https://www.linkedin.com/company/phpfoundation/).
16 | > Subscribe to it and follow us on Twitter [@ThePHPF](https://twitter.com/thePHPF).
17 |
18 | ## PHP Core Roundup
19 |
20 | Here's a summary of what the foundation's developers have been working on lately:
21 |
22 | * [Arnaud Le Blanc](https://github.com/arnaud-lb) revised the RFC and implementation of multi-statement short closures. The proposal is now on vote. Arnaud has also finished the improvements to ini quantity parsing.
23 |
24 | * [Derick Rethans](https://github.com/derickr) continues to fix bugs in DateTime to make working with dates in PHP as reliable as possible.
25 |
26 | * [Gina P. Banyard](https://github.com/Girgias) has made several improvements to the type system: true, null, and false standalaone types have been added, and Disjunctive Normal Form Types put on vote. Gina also made a few fixes in SPL.
27 |
28 | * [Ilija Tovilo](https://github.com/iluuu1994) implemented multiple improvements for enums and put a couple on vote. He also made many fixes, like for instance fixed line numbers in backtrace of multi-line (fluent) function calls.
29 |
30 | * [Jakub Zelenka](https://github.com/bukka) made various fixes and improvements to PHP-FPM and OpenSSL extension.
31 |
32 | * [Máté Kocsis](https://github.com/kocsismate) makes improvements to stubs and other fixes.
33 |
34 | All developers devote significant time to maintenance, including fixing bugs, reducing technical debt, and making life easier for everyone working on PHP.
35 |
36 | In the **[PHP Roundup #3](https://thephp.foundation/blog/2022/06/30/php-core-roundup-3/)** post by Ayesh, you can find a detailed log of what's been done and discussed regarding the PHP engine during the past month.
37 |
38 | This time the list of changes is very long! Applause to all the PHP contributors and release managers.
39 |
40 | Tweet at us: [@ThePHPF](https://twitter.com/thephpf), [@Ayeshlive](https://twitter.com/Ayeshlive), [@pronskiy](https://twitter.com/pronskiy).
41 |
42 | ## Thank you to our sponsors
43 |
44 | This month we are glad to welcome a new major sponsor who joined the PHP Foundation’s sponsors herd: **[Mollie](https://www.mollie.com/en)**. Thank you, folks!
45 |
46 | By the way, we have updated the **[Sponsors section](https://thephp.foundation/#sponsors)** on our [website](https://thephp.foundation/). It now shows all major contributors sorted by the amount of donation. Kudos to [Sergei Panteleev](https://twitter.com/s_panteleev) for this tweak.
47 |
48 | Shout-out to everyone for your continued support – the PHP Foundation is all of us!
49 |
50 | ## Other ways to contribute
51 |
52 | We are receiving many offers of help from every corner of the community. We are grateful for the offers. There are essentially two kinds of offers being made:
53 |
54 | 1. An offer of development time
55 | 2. An offer of expertise
56 |
57 | ### How to contribute development time?
58 |
59 | The Foundation has limited resources to manage the developers we contract to work on PHP. For this reason, it is not sensible to assume the management of external developers.
60 |
61 | Any external developer who is compensated for their time spent on PHP is, of course, welcome to make use of our public communication channels:
62 |
63 | 1. Email as: [contact@thephp.foundation](mailto:contact@thephp.foundation)
64 | 2. Communicate via issues on GitHub repos: [github.com/php/php-src](https://github.com/php/php-src), [github.com/php/web-php](https://github.com/php/web-php), etc.
65 |
66 | ### How to contribute expertise?
67 |
68 | As the foundation begins to mature, a couple of currently unfulfilled roles have emerged.
69 |
70 | We will soon communicate the details of these roles.
71 |
72 | We intend to compile a list of all expertise on offer; If you haven't done so already, please tell what expertise you would like to make available using public communication channels.
73 |
74 | ---
75 |
76 |
77 | That’s all for today. Follow us on Twitter [@ThePHPF](https://twitter.com/thephpf) to get the latest updates from the Foundation.
78 |
79 | 💜🐘
80 |
--------------------------------------------------------------------------------
/source/_posts/2022-08-04-php-foundation-update-july-2022.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: PHP Foundation Update, July 2022
3 | layout: post
4 | tags:
5 | - update
6 | author:
7 | name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 4 August 2022
10 | ---
11 | ```
We’re eager to answer your questions and look forward to hearing your suggestions! pic.twitter.com/2x8id0mDZ5
— Sebastian Bergmann (@s_bergmann) July 5, 2022
25 |
26 |
27 |
28 | **Gina P. Banyard**, one of the PHP Foundation’s developers, will talk about PHP’s type system internals.
29 |
30 |
Nous sommes ravis d'accueillir pour la première fois @Girgias, jeune et talentueux core-contributeur à PHP, pour un talk sur les rouages du typage lors du Forum PHP 2022. 🎤 "Typage en PHP comment ça fonctionne ?" - Forum PHP 2022 - 13&14/10, Disneyland Paris pic.twitter.com/dB0pWflmKB
31 |
32 |
33 |
34 | **[SymfonyCon, Paris – November 17-18](https://live.symfony.com/2022-paris-con/)**
35 |
36 | At this conference, you’ll be able to catch up with Sebastian Bergmann, Roman Pronskiy, and Nicolas Grekas.
37 |
38 | **[International PHP Conference, Munich – October 23-24](https://phpconference.com/)**
39 |
40 | Sebastian Bergmann and Derick Rethans will each talk at the IPC this year.
41 |
42 | _Where else would you like to see us?_
43 |
44 |
45 | ### **Swag!**
46 |
47 | By the way, we’d like to have stickers and other swag for conference attendees. If you would like to help with the design or sponsor the production, please reach out to [contact@thephp.foundation](mailto:contact@thephp.foundation).
48 |
49 |
50 | ## Website updates
51 |
52 | Thanks to Sergey Panteleev, one of the PHP 8.2 release managers, we have a few nice additions to our website.
53 |
54 |
55 |
56 | * A new **[structure page](https://thephp.foundation/structure/)** where you can see all the people currently actively involved in the PHP Foundation activities.
57 | * Every post has a nicely generated preview image — please, share the links to the PHP Foundation to help spread the word.
58 |
59 | The [website is open-source](https://github.com/ThePHPF/thephp.foundation) and built with [Sculpin](https://github.com/sculpin/sculpin) and [Tailwind CSS](https://tailwindcss.com/). So if you stumbled upon a bug, please do not hesitate to report or submit a PR.
60 |
61 |
62 | ## PHP Core Roundup
63 |
64 | In July, we marked the feature-freeze for PHP 8.2, and this next version of PHP is being shaped by PHP Foundation members and all the contributors to be an exciting release!
65 |
66 | Catch up to this month's PHP Core changes on the **[PHP Core Roundup #4](https://thephp.foundation/blog/2022/07/28/php-core-roundup-4/)** post by Ayesh, where you can find a detailed log of what's been done and discussed regarding the PHP engine.
67 |
68 | **What if our proposal did not make it?**
69 |
70 | Among many fixes and improvements, some suggestions did not pass the RFC voting barrier. For instance, that happened to the [Short Closures 2.0](https://wiki.php.net/rfc/auto-capture-closure) proposal.
71 |
72 | We consider this a good experience in any case, and developers might reconsider, improve, and suggest it in the next release cycle, i.e., PHP 8.3.
73 |
74 | We also consider it to be a good thing that it's difficult to change the language, as these changes are forever.
75 |
76 | **What about deprecations?**
77 |
78 | PHP has a long 25-year history, and no wonder it has some old quirks. One of them relates to DateTime and DateTimeImmutable confusion.
79 |
80 | Derrick Rethans, a core developer of the PHP Foundation, asks for an opinion about in which way this confusion should be resolved; if it should:
81 |
82 |
Making PHP's DateTime class mutable was one of the bigger mistakes of the Date/Time APIs. I'm considering to change DateTime to be immutable by default in PHP 9, and to drop DateTimeImmutable altogether (or make it an alias). This is likely going to break some code. Opinions?
83 |
84 | Let Derick know what you think.
85 |
86 | > You can find more insights on PHP core development process in **[PHP Roundup Series](https://thephp.foundation/blog/tag/roundup/)**.
87 | >
88 | > Tweet at us: [@ThePHPF](https://twitter.com/thephpf), [@Ayeshlive](https://twitter.com/Ayeshlive), [@pronskiy](https://twitter.com/pronskiy).
89 |
90 |
91 |
92 | ## Thank you to our sponsors
93 |
94 | This month we are glad to welcome a new major sponsor who joined the PHP Foundation’s sponsors herd:
95 |
96 | **[Cybozu, Inc](https://opencollective.com/cybozu)**
97 |
98 | Thank you for supporting PHP!
99 |
100 | Shout-out to [everyone](https://thephp.foundation/#sponsors) for your continued support – the PHP Foundation is all of us!
101 |
102 | ---
103 |
104 |
105 | That’s all for today. Follow us on Twitter [@ThePHPF](https://twitter.com/thephpf) to get the latest updates from the Foundation.
106 |
107 | 💜🐘
108 |
109 |
110 |
--------------------------------------------------------------------------------
/source/_posts/2023-09-06-application-form-2023.md:
--------------------------------------------------------------------------------
1 |
2 | ---
3 | title: 'We Are Looking for Developers to Join the PHP Foundation'
4 | layout: post
5 | tags:
6 | - team
7 | author:
8 | - name: Roman Pronskiy
9 | url: https://twitter.com/pronskiy
10 |
11 | - name: Nils Adermann
12 | url: https://twitter.com/naderman
13 | published_at: 06 September 2023
14 |
15 | ---
16 |
17 | Working on an open-source project which is used by millions of developers and which is trusted by hundreds of thousands of businesses around the world. Getting paid for this work and not having a burnout. Sounds like a dream, doesn't it? But this is exactly the opportunity that the PHP Foundation provides to those who would like to develop and maintain the PHP language.
18 |
19 | The PHP Foundation is a non-profit organization, started in 2021 by Acquia, Automattic, Craft CMS, JetBrains, Laravel, PrestaShop, Private Packagist, Symfony, Tideways, and Zend by Perforce with a mission to support, advance, and develop the PHP language.
20 |
21 | Since April 2022, the foundation pays [six developers](https://thephp.foundation/structure/#core_developers) to work on the language. See what the foundation accomplished in 2022 in the [Impact and transparency report](https://thephp.foundation/blog/2022/11/22/transparency-and-impact-report-2022/).
22 |
23 |
24 | ## We are opening applications for new positions at the PHP Foundation
25 |
26 | The PHP Foundation is almost two years old, and we are gradually introducing structure into our activities and organizing processes. We’re opening a new round of applications for developer positions. We plan to open applications every September from now on, so if you are unable to apply now, you will have another chance next year. We intend to decide on who we will hire by the end of October. If selected, you would start your work January 1st, 2024.
27 |
28 | The application form will be **open until September 30, 2023**.
29 |
30 |
35 | Note: This is not a job for PHP developers or aspiring PHP developers.
36 | The development of PHP is done in the С programming language, and requires proficiency in system programming.
37 |
38 |
39 | ## What are the requirements?
40 |
41 | As before, we require previous experience in PHP core development. Ideally you should have all, but at least some of the following:
42 |
43 | * Pull-requests / commits to [php/php-src](https://github.com/php/php-src/)
44 | * Experience in writing PHP extensions
45 | * Participation in PHP mailing lists
46 | * Contributions to other open-source projects
47 |
48 | This time, however, we have a clearer idea of the tasks that can be engaged in and so the pool of considered candidates will be wider.
49 |
50 |
51 | ## What am I going to work on?
52 |
53 | Strategic areas we’d like you to work on:
54 |
55 | * Security
56 | * Performance
57 | * Infrastructure
58 | * Web APIs (json, PDO, streams, etc.)
59 | * Documentation
60 |
61 | This is not an exhaustive list, and if you would like to do something else, make sure to mention it in the form. The main criteria is a pragmatic approach. In this sense, we adhere to the position that Rasmus Lerdorf, the author of PHP, voiced back in 2014:
62 |
63 | ```Text
64 | And rather than piling on language features with the main justification
65 | being that other languages have them, I would love to see more focus on
66 | practical solutions to real problems. The password_hash() addition in
67 | 5.5 is a good example of addressing a real Web problem.
68 | …
69 | I know these are much harder and less sexy than adding a couple
70 | of tokens to the yacc grammar, but when we start looking at a new major
71 | release this is what I hear from people who are running PHP in
72 | production environments are looking for. Language features are nice, if
73 | they are well thought out, but significant infrastructure improvements
74 | are nicer.
75 | ```
76 | *[https://news-web.php.net/php.internals/71525](https://news-web.php.net/php.internals/71525)*
77 |
78 |
79 | ## What does working for the PHP foundation look like?
80 |
81 | Working for the PHP Foundation offers a lot of freedom, but it also requires discipline. Your work will roughly consist of the following:
82 |
83 | * 40% Triaging issues and fixing bugs
84 | * 30% Working on strategic areas
85 | * 20% Code reviews
86 | * 10% Preparing RFCs and developing new language features
87 |
88 | As you can see, developing new RFCs is a fairly small part of the job. Most of the work is a typical maintenance of an open source project.
89 |
90 | We are a fully distributed team. You can work from any place* and at any time. All communication is asynchronous via GitHub, Slack, and Email. We meet for synchronous calls 1-2 times a month.
91 |
92 | ***\*** We do not consider applications from persons residing in sanctioned territories.*
93 |
94 | Your work should be in line with the foundation’s mission statement, and we expect you to follow [the code of conduct](https://thephp.foundation/code-of-conduct/).
95 |
96 | > **PHP Foundation Mission Statement**
97 | >
98 | > The PHP Foundation is a collective of people and organizations relying on the PHP language. Its mission is to ensure the long-term prosperity of the PHP language. The PHP Foundation focuses on providing financial support and guidance to PHP language developers to support its goals of improving the language for its users, providing high-quality maintenance, and improving the PHP language project to retain current contributors and to integrate new contributors. The PHP Foundation aims to promote the public image of the PHP language in the interest of retaining existing and gaining new users and contributors.
99 |
100 | ## How to apply?
101 |
102 | Submit your application now and we will get back to you shortly. If you have any questions or suggestions, reach out to contact@thephp.foundation.
103 |
104 |
107 |
108 |
109 |
--------------------------------------------------------------------------------
/source/_posts/2023-11-23-php-83.md:
--------------------------------------------------------------------------------
1 |
2 | ---
3 | title: 'PHP 8.3 Released!'
4 | layout: post
5 | author:
6 | - name: Ayesh Karunaratne
7 | url: https://aye.sh
8 |
9 | - name: Sergey Panteleev
10 | url: https://sergeypanteleev.com
11 | published_at: 23 November 2023
12 |
13 | ---
14 |
15 |
16 |
17 |
20 |
21 |
22 |
23 | [PHP 8.3](https://www.php.net/releases/8.3) is here! Bringing a handful of new features, performance and functionality improvements, and a healthy amount of deprecations, PHP 8.3 was released today.
24 |
25 | PHP 8.3 will continue to receive active support for two years, followed by one year of security updates. Similar to the PHP 8.2 upgrade, the PHP 8.3 upgrade will be smooth as backward compatiblity is maintained. While some functionality is deprecated, there are no syntax, API*, and remove functionality in this release.
26 |
27 | ## What's in PHP 8.3
28 |
29 | Some of the major new features in PHP 8.3 include support for declaring a type for class constants, improvements to support deep-cloning of `readonly` properties, improvements to the new Random extension introduced in PHP 8.2, new [`json_validate()`](https://www.php.net/manual/en/function.json-validate.php),[`str_increment()`](https://www.php.net/manual/en/function.str-increment.php), and [`str_decrement()`](https://www.php.net/manual/en/function.str-decrement.php), functions, and a noticeable amount of improvements in DateTime, DOM, and Intl extensions.
30 |
31 | See the [PHP 8.3 release page](https://www.php.net/releases/8.3) for what's new and changed in PHP 8.3.
32 |
33 | > (*) Note that some of the PHP core extensions now declare types for built-in class constants. This is technically a BC break in case child classes declare the same constants without type declaration, which is only supported in PHP 8.3.
34 |
35 | ## Upgrade to PHP 8.3
36 |
37 | PHP packages on software repositories such as Debian and Ubuntu repos maintained by [Ondřej Surý](https://launchpad.net/~ondrej), [Remi Collet](https://github.com/remicollet) for Fedora/RHEL/EL already contain PHP 8.3 builds ready to install.
38 |
39 | Windows builds for PHP 8.3 are available on [windows.php.net](https://windows.php.net/download/)
40 |
41 | [Docker images](https://hub.docker.com/_/php) with PHP 8.3 will also be available on Docker hub in the coming days.
42 |
43 | ## PHP 8.3 Release in Numbers
44 |
45 | The PHP 8.3 release contains **over 1200 code commits** from **114 awesome contributors** to the `php-src` repository, and several more contributions to the documentation and its translations.
46 |
47 | Contributions from the **PHP Foundation members** consist of over **280 commits**.
48 |
49 | During the period from the PHP 8.2 release date and today, the **PHP Internals mailing list has received over 2800 emails**.
50 |
51 | PHP RFCs, where major changes to PHP are proposed, discussed, and voted on, PHP 8.3 received **23 RFCs that went to a vote**, and **18 RFCs passed**. This includes a number includes "catch-all" RFCs such as Deprecations for PHP 8.3, where multiple changes were voted at the same time. Out of the 23 RFCs with votes, **13 RFCs** were either proposed or implemented by the **PHP Foundation** members.
52 |
53 | The PHP documentation and php.net web site contributors have also made several impactful contributions to document the new features in PHP 8.3, prepare release pages, and more.
54 |
55 |
56 | ## 💜 Thank you 💜
57 |
58 | On behalf of the PHP Foundation, we take this post to thank everyone from this milestone in PHP. Your contributions to the PHP Foundation, code and documentation contributions, and several other ways of involvement and contributions help shape PHP to continue to be an exciting, feature-rich, and versatile programming language.
59 |
60 | Thank you 💜
61 |
62 | ## PHP 8.4 Outlook
63 |
64 | PHP 8.4, scheduled for the end of 2024 is already taking shape. Even at the moment PHP 8.3 is released, there are three active RFC votes, and some major changes such as JIT-IR, a brand-new HTML 5 parser in the DOM extension based on [Lexbor](https://github.com/lexbor/lexbor), and Bcrypt default cost increasing already been implemented for PHP 8.4
65 |
66 | We look forward to bringing you updates on our [PHP Core Roundup series](https://thephp.foundation/blog/tag/roundup/) and our newsletter:
67 |
68 | {% include "newsletter.html" %}
69 |
70 | ---
71 |
72 | 💜️ 🐘
73 |
74 | > PHP Roundup is prepared by Ayesh Karunaratne from **[PHP.Watch](https://php.watch)**, a source for PHP News, Articles, Upcoming Changes, and more.
75 |
76 |
77 |
78 |
--------------------------------------------------------------------------------
/source/_posts/2023-11-27-php-foundation-update-november-2023.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: PHP Foundation Update, November 2023
3 | layout: post
4 | tags:
5 | - update
6 | author:
7 | name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 27 November 2023
10 | ---
11 | ``` My name is Roman Pronskiy. I’m employed by [JetBrains](https://jetbrains.com/) to manage operations at the PHP Foundation. Reach out to me at pronskiy@thephp.foundation.
16 | >
17 | > You can find the full foundation structure [here](https://thephp.foundation/structure/), including all board members, developers, and the community.
18 |
19 | ## Team Growth
20 |
21 | In September, we initiated an open call for new developers to join the PHP Foundation by launching an [application form](https://thephp.foundation/blog/2023/09/06/application-form-2023/).
22 |
23 | We received a total of 207 applications. From this pool, we selected a shortlist of 12 qualified candidates. Following a comprehensive review and input from existing foundation members, we further refined our selection to 4 outstanding individuals. We will soon announce the new members.
24 |
25 | The primary focus for the new developers will be on the maintenance and modernization of PHP’s infrastructure — a critical step towards ensuring PHP being a robust and forward-looking language.
26 |
27 | The public work undertaken by our developers can be followed in our monthly ["PHP Core Roundup"](https://thephp.foundation/blog/tag/roundup/) series, which highlights the ongoing progress and developments within PHP core.
28 |
29 |
30 | ## Advisory Board
31 |
32 | For our major sponsors, we offer exclusive insights through occasional digests that provide a deeper dive into discussions, debates, and early-stage developments. This not only keeps our sponsors abreast of the latest happenings but also allows them to see the direct impact of their support. This is one of the benefits of being an Advisory Board member.
33 |
34 | We announced the advisory board initiative [in March](https://thephp.foundation/blog/2023/03/31/php-foundation-update-march-2023/#a-new-benefit-for-major-sponsors-%E2%80%93-advisory-board-membership). Since then, 9 companies have joined the initiative with their representatives.
35 |
36 | In addition to the [Governing Board](https://thephp.foundation/structure/) that includes Automattic, JetBrains, Private Packagist, Symfony, Tideways, Zend by Perforce, and PHP fellows, we now welcome the Advisory Board members: Moodle, Shopware, Laravel, Ardennes-étape, Les-Tilleuls.coop / API Platform, Aternos GmbH, PrestaShop, CraftCMS.
37 |
38 | There were several useful discussions within the group. Specifically, we’d like to highlight the one around [Property Hooks RFC](https://wiki.php.net/rfc/property-hooks). The Advisory Board feedback helped to shape the proposal design significantly.
39 |
40 | By the way, you can already try property hooks on [3v4l.org](https://3v4l.org/), thanks to [Sjon Hortensius](https://github.com/sponsors/SjonHortensius).
41 |
42 |
43 | ## Sovereign Tech Fund invests in PHP
44 |
45 | The [Sovereign Tech Fund](https://sovereigntechfund.de/en/) is an organization that supports the development, improvement, and maintenance of open digital infrastructure in the public interest. Its goal to strengthen the open-source ecosystem sustainably, focusing on security, resilience, technological diversity, and the people behind the code. STF is funded by the German Federal Ministry for Economic Affairs and Climate Action (BMWK) and supported by the German Federal Agency for Disruptive Innovation GmbH (SPRIND).
46 |
47 | We have collaborated with STF to create work plans for these specific projects: PECL overhaul, Testing tool for FPM, Security Audit, and Documentation improvements.
48 |
49 | We’ll share more details on each project early next year, and for now we are thrilled and grateful to the Sovereign Tech Fund for trusting us.
50 |
51 |
52 | ## Security audit of PHP is coming
53 |
54 | As mentioned above, STF is investing in PHP, and we are going to commission an audit of PHP's C code base. We expect security issues to be found. To mitigate possible bad perception, we aim to publish and fix the revealed security issues at the same time.
55 |
56 | For this security audit, we are partnering with [The Open Source Technology Improvement Fund, Inc](https://ostif.org/) (OSTIF), a corporate non-profit dedicated to securing critical open-source projects. They have a proven track record of audits for [popular open-source projects](https://github.com/ostif-org/OSTIF/blob/main/Completed-Engagements.md) such as cURL, Git, Linux Kernel, OpenSSL, Node.js, and others.
57 |
58 |
59 | ## Reports schedule
60 |
61 | Although we promised to prepare quarterly reports, that unfortunately did not happen to be feasible. So for 2023, we fall back to one yearly report. The 2023 transparency report will be published in December.
62 |
63 |
64 | ## Meet us at the conferences
65 |
66 | You can meet our team at the following conferences in late 2023:
67 |
68 | **[betterCode(PHP)](https://php.bettercode.eu/) – Nov 27**
69 |
70 | Jakub Zalenka will give a talk: "PHP 8.3: Changes and future plans".
71 | Besides Jakub, there will be talks from Niels Dossche and Sebastian Bergmann.
72 |
73 | **[SymfonyCon Brussels](https://live.symfony.com/2023-brussels-con/) – Dec 7–8**
74 |
75 | You’ll be able to meet and talk to our board members: Nils Adermann, Sebastian Bergmann, Nicolas Grekas, and Roman Pronskiy.
76 |
77 |
78 | ## Thank you to our sponsors
79 |
80 | Check out the [Sponsors section](https://thephp.foundation/#sponsors) on our [website](https://thephp.foundation/). It shows all major contributors sorted by donation amount.
81 |
82 | Big thanks to the **[Sentry](https://sentry.io/)** team for sponsoring the PHP foundation!
83 |
84 | Sentry is a popular application performance monitoring & error tracking tool, and they [just gave $500,000 to multiple open source maintainers](https://blog.sentry.io/we-just-gave-500-000-dollars-to-open-source-maintainers/?utm_source=linkedin&utm_content=blog-fundfest23-learnmore).
85 |
86 | **Shout-out to non-financial sponsors**
87 |
88 | [Digital Ocean](https://www.digitalocean.com/) has been supporting the PHP project for ages – [php.net](https://www.php.net/) servers run on DigitalOcean boxes. We would like to express our gratitude to DigitalOcean for their ongoing support.
89 |
90 | Big thanks to [everyone](https://thephp.foundation/#sponsors) for your continued support – the PHP Foundation is all of us!
91 |
92 | ---
93 |
94 | That’s all for today. Follow us on Twitter [@ThePHPF](https://twitter.com/thephpf) or Mastodon [phpc.social/@thephpf](https://phpc.social/@thephpf) to get the latest updates from the PHP Foundation.
95 | 💜🐘
96 |
--------------------------------------------------------------------------------
/source/_posts/2024-01-03-the-php-foundation-team-update-2024.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "The PHP Foundation\nTeam Update 2024"
3 | layout: post
4 | tags:
5 | - update
6 | author:
7 | name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 03 January 2024
10 | ---
11 |
12 | Now in our third year, we're gearing up to grow our impact. This year, four more developers are joining the PHP Foundation to further advance PHP.
13 |
14 | Since April 2022, the PHP Foundation has contracted six outstanding developers:
15 |
16 | * Arnaud Le Blanc [@arnaud-lb](https://github.com/arnaud-lb)
17 | * Derick Rethans [@derickr](https://github.com/derickr)
18 | * Gina Peter Banyard [@Girgias](https://github.com/Girgias)
19 | * Ilija Tovilo [@iluuu1994](https://github.com/iluuu1994)
20 | * Jakub Zelenka [@bukka](https://github.com/bukka)
21 | * Máté Kocsis [@kocsismate](https://github.com/kocsismate)
22 |
23 | All of them started as part-time contributors, and since then have significantly grown their capacity and dedication to PHP core tasks. We consider it a big achievement that the team continues to collaborate effectively, accumulating more experience and knowledge, and expanding their PHP Core involvement.
24 |
25 | ## Team Update 2024
26 |
27 | We are happy to announce a team expansion. Four talented developers are joining as part-time team members of the foundation.
28 |
29 | * David Carlier [@devnexen](https://github.com/devnexen)
30 | * James Titcumb [@asgrim](https://github.com/asgrim)
31 | * Saki Takamachi [@SakiTakamachi](https://github.com/SakiTakamachi)
32 | * Shivam Mathur [@shivammathur](https://github.com/shivammathur)
33 |
34 | Please give them a warm welcome! We are looking forward to the great things we will accomplish together.
35 |
36 | Happy New Year! 🎉🐘💜
37 |
--------------------------------------------------------------------------------
/source/_posts/2024-04-02-open-source-community-cra-compliance-initiative.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'Joining Forces for Open Source Cybersecurity Standards'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 02 April 2024
10 | ---
11 |
12 | The PHP Foundation, alongside leading open source organizations including the [Apache Software Foundation](https://www.apache.org/), [Blender Foundation](https://www.blender.org/about/foundation/), [OpenSSL Software Foundation](https://www.openssl.org/), [Python Software Foundation](https://www.python.org/psf-landing/), [Rust Foundation](https://foundation.rust-lang.org/), and [Eclipse Foundation](https://www.eclipse.org/), is excited to announce a collaborative initiative aimed at establishing common cybersecurity standards in alignment with the European Union’s [Cyber Resilience Act (CRA)](https://digital-strategy.ec.europa.eu/en/library/cyber-resilience-act).
13 |
14 | This initiative, hosted by the Eclipse Foundation, will focus on creating specifications for secure software development rooted in open source best practices.
15 |
16 | > We hope that our specifications could inform the formal standardisation processes of at least one of the European Standards Organisations. Given the tight time horizon for implementation of the CRA, we believe that this immediate start will provide a constructive environment to host the technical discussions necessary for the stewards, contributors, and adopters of open source to meet the requirements set forth in these new regulations.
17 |
18 | At The PHP Foundation, we are committed to supporting the open source community, ensuring that the PHP language and its ecosystem are prepared for the upcoming regulatory changes.
19 |
20 | For more information, see the [full announcement on the Eclipse Foundation website](https://eclipse-foundation.blog/2024/04/02/open-source-community-cra-compliance/).
21 |
--------------------------------------------------------------------------------
/source/_posts/2024-09-12-php-foundation-update-september-2024.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: PHP Foundation Update, September 2024
3 | layout: post
4 | tags:
5 | - update
6 | author:
7 | name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 12 September 2024
10 | ---
11 |
12 | ```
47 |
48 | That’s all for today. Follow us on X/Twitter [@ThePHPF](https://twitter.com/thephpf), Mastodon [phpc.social/@thephpf](https://phpc.social/@thephpf), and [LinkedIn](https://www.linkedin.com/company/phpfoundation/) to get the latest updates from the PHP Foundation.
49 | 💜🐘
50 |
--------------------------------------------------------------------------------
/source/_posts/2024-09-17-application-form-2025.md:
--------------------------------------------------------------------------------
1 |
2 | ---
3 | title: 'The PHP Foundation application form for 2025 is now open'
4 | layout: post
5 | tags:
6 | - team
7 | author:
8 | - name: Roman Pronskiy
9 | url: https://twitter.com/pronskiy
10 |
11 | - name: Nils Adermann
12 | url: https://twitter.com/naderman
13 | published_at: 17 September 2024
14 |
15 | ---
16 |
17 | The PHP Foundation is a non-profit organization, started in 2021 by Acquia, Automattic, Craft CMS, JetBrains, Laravel, PrestaShop, Private Packagist, Symfony, Tideways, and Zend by Perforce with a mission to support, advance, and develop the PHP language.
18 |
19 | The foundation pays [10 developers](https://thephp.foundation/structure/#core_developers) to work on the language. See what the foundation achieved in 2023 in the [Impact and transparency report](https://thephp.foundation/blog/2024/02/26/transparency-and-impact-report-2023/).
20 |
21 | We’re opening a new round of applications for developer positions. We intend to decide on who we will hire by the end of October. If selected, you would start your work January 1st, 2025\.
22 |
23 | The application form will be **open until October 10, 2024**.
24 |
25 |
30 | Note: This is not a job for PHP developers or aspiring PHP developers.
31 | The development of PHP is done in the С programming language, and requires proficiency in system programming.
32 |
33 |
34 | ## Note: Team size is unlikely to grow
35 |
36 | While we won’t rule out the possibility of expanding our team, it’s likely we won’t pay more than the current number of 10 developers. Mindful of our budget limitations, we may rather consider restructuring or adjusting our team to make space for any outstanding applications that better help us meet our goals.
37 |
38 | ## What are the requirements?
39 |
40 | As before, we require previous experience in PHP core development. Ideally you should have all, but at least some of the following:
41 |
42 | - Pull-requests / commits to [php/php-src](https://github.com/php/php-src/)
43 | - Experience in writing PHP extensions
44 | - Participation in PHP mailing lists
45 | - Contributions to other open-source projects
46 |
47 | This time, however, we have a clearer idea of the tasks that can be engaged in and so the pool of considered candidates will be wider.
48 |
49 | ## What are you going to work on?
50 |
51 | Strategic areas we’d like you to work on:
52 |
53 | - Security
54 | - Performance
55 | - Infrastructure
56 | - Web APIs (json, PDO, streams, etc.)
57 |
58 | This is not an exhaustive list. We encourage you to **provide as detailed a description of what you want to work on as possible**.
59 |
60 | Our primary selection criterion is **pragmatism**. We place greater emphasis on solutions that improve the developer experience and benefit businesses that rely on PHP, rather than new syntax features.
61 |
62 | Out of scope:
63 |
64 | - Pure documentation work
65 | - PHP packages
66 | - Websites
67 | - Translations
68 |
69 | ## What does working for the PHP Foundation look like?
70 |
71 | Working for the PHP Foundation offers a lot of freedom, but it also requires discipline. Your work will roughly consist of the following:
72 |
73 | - 40% Triaging issues and fixing bugs
74 | - 30% Working on strategic areas
75 | - 20% Code reviews
76 | - \>10% Preparing RFCs and developing new language features
77 |
78 | As you can see, developing new RFCs is a fairly small part of the job. Most of the work is typical maintenance of an open source project.
79 |
80 | We are a fully distributed team. You can work from any place**\*** and at any time. All communication is asynchronous via Slack, GitHub, and Email. We meet for synchronous calls 1-2 times a month.
81 |
82 | Your work should be in line with the foundation’s mission statement, and we expect you to follow [the code of conduct](https://thephp.foundation/code-of-conduct/).
83 |
84 | > **PHP Foundation Mission Statement**
85 | >
86 | > The PHP Foundation is a collective of people and organizations relying on the PHP language. Its mission is to ensure the long-term prosperity of the PHP language. The PHP Foundation focuses on providing financial support and guidance to PHP language developers to support its goals of improving the language for its users, providing high-quality maintenance, and improving the PHP language project to retain current contributors and to integrate new contributors. The PHP Foundation aims to promote the public image of the PHP language in the interest of retaining existing and gaining new users and contributors.
87 |
88 | ***\*** We do not consider applications from persons residing in sanctioned territories.*
89 |
90 | ## How to apply?
91 |
92 | Submit your application now and we will get back to you shortly. If you have any questions or suggestions, reach out to contact@thephp.foundation.
93 |
94 |
97 |
98 |
99 |
--------------------------------------------------------------------------------
/source/_posts/2024-09-30-call-fo-sponsors.md:
--------------------------------------------------------------------------------
1 |
2 | ---
3 | title: 'The PHP Foundation Calls for Sponsors: Help Shape the Future of PHP'
4 | layout: post
5 | tags:
6 | - update
7 | author:
8 | - name: Roman Pronskiy
9 | url: https://twitter.com/pronskiy
10 | published_at: 30 September 2024
11 |
12 | ---
13 |
14 | Hey there, PHP enthusiasts and tech leaders\! It's that time of the year again when everyone's crunching numbers and deciding on budgets. We've got an opportunity for you to make a real impact on the PHP ecosystem. Let's dive in.
15 |
16 | **Don't need convincing? [Sponsor us now](https://thephp.foundation/sponsor/)!**
17 |
18 | ## Join us\! Fund the Future of Web Development
19 |
20 | We just opened applications for PHP core language contributors: [The PHP Foundation application form for 2025 is now open](https://thephp.foundation/blog/2024/09/17/application-form-2025/).
21 |
22 | Here's the deal: **the more sponsors we get, the more ambitious we can be with our plans**. At a minimum, we finance maintenance and security support, but with more funding, we can continue high-reaching projects.
23 |
24 | Your sponsorship could help us:
25 |
26 | * **Tackle long-standing bugs** that have been bothering developers for ages.
27 | * **Implement cool new features** that will make PHP even more awesome.
28 | * **Improve performance and security** (because who doesn't want a faster PHP).
29 |
30 | And if we get enough sponsors, we might even venture into some experimental territory. Your support could lead to the next big breakthrough in PHP development.
31 |
32 | {{ include('quote.html', {
33 | name: 'Kévin Dunglas',
34 | title: 'author of [FrankenPHP](https://frankenphp.dev/)',
35 | image: '/assets/post-images/2024/report-2023/kevin_dunglas.png',
36 | quote: 'To achieve exceptional performance and simplify application deployment, FrankenPHP pushes the PHP engine to its limits and uses it in atypical ways (ZTS, musl libc, specific timeout management...).
37 |
38 | This would not be possible without the excellent work done by the PHP Foundation\'s team: they correct the problems we report, continuously improve performance and make the engine always more generic and modular, which not only enables us to innovate in FrankenPHP, but also benefits the entire ecosystem by making PHP faster and more reliable.
39 |
40 | By sponsoring the foundation, you\'re investing in the future of PHP!'
41 | }) }}
42 |
43 | ## 2025: The Year PHP Turns 30 (and It's Going to Be Epic\!)
44 |
45 | PHP is turning 30 in 2025, and we're planning a special celebration\! By sponsoring the PHP Foundation, you'll be front and center for this milestone year. Here's what we've got cooking:
46 |
47 | * A massive collaboration with the marketing teams from Laravel, JetBrains, and Zend by Perforce. It's like the Avengers of the PHP world coming together.
48 | * A much-needed facelift for php.net. Let's make it shine for PHP’s 30th birthday\!
49 |
50 | Imagine your company being visible as a part of this historic moment. Pretty cool, right?
51 |
52 | ## Why Sponsor the PHP Foundation?
53 |
54 | You might be wondering, "Why should I sponsor the PHP Foundation?" Let us list some of the reasons:
55 |
56 | 1. **Visibility:** Your brand will be seen by millions of developers worldwide. That's a lot of eyeballs.
57 | 2. **Influence:** Help shape the future of one of the most widely used programming languages on the web.
58 | 3. **Security:** Without sufficient funding, the PHP language will lack the resources to promptly address bugs your company runs into.
59 | 4. **Recruitment:** Attract top PHP talent by showing your commitment to the language.
60 | 5. **Giving Back:** If PHP has helped your business grow, here's your chance to return the favor.
61 | 6. **Tech Cred:** Nothing says "we're serious about web development" like sponsoring a major programming language.
62 |
63 | ## Ready to Jump In?
64 |
65 | Here's how you can get started:
66 |
67 | 1. Check out our sponsorship tiers on our website: [thephp.foundation/sponsor](https://thephp.foundation/sponsor/).
68 | 2. Reach out to us at [contact@thephp.foundation](mailto:contact@thephp.foundation).
69 | 3. Let's chat about how we can make this partnership beneficial for both of us.
70 | Office hours call: [cal.com/pronskiy/php-foundation-office-hours](http://cal.com/pronskiy/php-foundation-office-hours)
71 |
72 | ## Stay in the Loop
73 |
74 | Don't miss out on any PHP Foundation news. Follow us on:
75 |
76 | * LinkedIn: [PHP Foundation](https://www.linkedin.com/company/phpfoundation)
77 | * Twitter/X: [@ThePHPF](https://x.com/thephpf)
78 | * Mastodon: [@thephpf@phpc.social](https://phpc.social/@thephpf)
79 |
80 |
81 | And for those who prefer their news in their inbox, subscribe to our email newsletter. We send ~1–2 emails a month – just the good stuff about PHP and the Foundation.
82 |
83 | {% include "newsletter.html" %}
84 |
85 | P.S. If you have any questions or wild ideas about how you'd like to support PHP, don't hesitate to reach out. We're all ears.
86 |
--------------------------------------------------------------------------------
/source/_posts/2024-10-08-open-source-pledge.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'The PHP Foundation Supports The Open Source Pledge'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 8 October 2024
10 |
11 | ---
12 |
13 | The PHP Foundation is proud to announce our support for the Open Source Pledge initiative, launched by Sentry and its partners. This step addresses the sustainability challenges within the Open Source Software (OSS) community, particularly affecting PHP and its ecosystem.
14 |
15 | ## The Open Source Pledge: A Commitment to Sustainability
16 |
17 | The Open Source Pledge represents a commitment from member companies to provide meaningful financial support to Open Source maintainers. This initiative aims to prevent maintainer burnout and reduce the risk of high-profile security incidents that can impact the broader tech ecosystem.
18 |
19 | The OSS community, including PHP, faces significant challenges:
20 |
21 | * **Security risks:** High-profile incidents like Log4shell, XZ, and Heartbleed have highlighted the potential consequences of under-resourced projects.
22 | * **Developer burnout:** Many maintainers, often volunteers, are feeling exhausted and leaving the very projects you might be using.
23 | * **Losing maintainers:** The demanding nature of maintaining open-source software means we’re seeing fewer contributors over time.
24 |
25 | ## The PHP Foundation's Role
26 |
27 | As the main funder and steward of the PHP language, we’ve seen firsthand how a lack of funding impacts crucial projects. For example:
28 |
29 | * **Core language development:** Keeping PHP up to date and improving it takes a lot of time and expertise.
30 | * **Security support:** Without enough funding, PHP can’t address vulnerabilities quickly.
31 | * **Extension maintenance:** Many essential PHP extensions are struggling to find people to maintain them.
32 | * **Documentation efforts:** Keeping PHP’s extensive documentation current is always a big challenge.
33 |
34 | # How to Join the Pledge
35 |
36 | The Open Source Pledge offers a structured approach to supporting OSS with the following requirements:
37 |
38 | * Minimum contribution: $2,000 per year, per developer on staff.
39 | * Transparency: Companies should publish annual reports detailing their payments.
40 | * Direct impact: Funds go directly to maintainers, supporting their crucial work.
41 |
42 | Thanks to supporting the PHP Foundation, our major sponsors [Private Packagist](https://packagist.com/) and [Tideways](https://tideways.com/) are already part of the [Open Source Pledge](https://opensourcepledge.com/).
43 |
44 | # \[Action Required\] Join the Pledge\!
45 |
46 | We urge PHP-based companies, developers, and organizations to join the Open Source Pledge and **[sponsor The PHP Foundation](https://thephp.foundation/sponsor/)**.
47 |
48 | To learn more about the Open Source Pledge and how you can participate, visit [https://opensourcepledge.com/](https://opensourcepledge.com/).
49 |
50 | Help us spread the word by sharing this post.
51 |
52 | 💜️ 🐘
53 |
--------------------------------------------------------------------------------
/source/_posts/2024-11-19-pie-pre-release.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'Announcing the Pre-Release of the PHP Installer for Extensions (PIE)'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: James Titcumb
8 | url: https://phpc.social/@asgrim
9 | published_at: 19 November 2024
10 | ---
11 |
12 | We're thrilled to introduce the pre-release of the PHP Installer for Extensions (PIE) – [**github.com/php/pie**](https://github.com/php/pie)!
13 |
14 | PIE aims to simplify managing PHP extensions by providing a modern, flexible alternative to PECL and treating extensions as first-class citizens in the PHP ecosystem.
15 |
16 |
19 |
20 | This initial pre-release is available as a [PHAR download](https://github.com/php/pie/releases/tag/0.2.0), and we invite you to take it for a spin and share your feedback. While this release is an exciting milestone, we know there's a lot more work ahead to make PIE ready for widespread use, so your feedback is invaluable. If you encounter any issues, or have any questions, feel free to open an [issue on GitHub](https://github.com/php/pie/issues), and help us shape the future of PIE.
21 |
22 | ## Why PIE?
23 |
24 | With PIE, the process of managing PHP extensions becomes more streamlined. Extensions are distributed via [Packagist](https://packagist.org/extensions) just like regular PHP packages! It makes the installation and update process quite familiar if you already use Composer.
25 |
26 | We’re working to make PIE stronger and easier to use. We’re improving how PHP extensions are managed and using ideas from Composer to make the process smoother.
27 |
28 | ## Are you an extension author?
29 |
30 | Extensions do need to be made compatible with PIE by adding a `composer.json` (more instructions [here](https://github.com/php/pie/blob/main/docs/extension-maintainers.md)), and submitting it to [Packagist](https://packagist.org/packages/submit). Once a package has added support for PIE, it will appear on the Packagist [Extensions list](https://packagist.org/extensions) page.
31 |
32 | 💜️🐘
33 |
--------------------------------------------------------------------------------
/source/_posts/2024-11-22-php-foundation-turns-three.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'The PHP Foundation Turns Three!'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 22 November 2024
10 | ---
11 |
12 | Wow. Can you believe it? Just three years (and one day) ago, PHP had no organization behind it. Only two people were being paid to work on the language that powers 70% of the web.
13 |
14 | Here’s the very first announcement about the creation of the PHP Foundation:
15 | [The New Life of PHP – The PHP Foundation](https://blog.jetbrains.com/phpstorm/2021/11/the-php-foundation/).
16 |
17 | ## Fast forward to today
18 |
19 | We now have a team of 10 talented engineers dedicated to PHP. We’re supported by major companies, governments, and an incredible community. That same community is creating amazing projects with PHP, while businesses continue to thrive thanks to a mature, secure, and performant language.
20 |
21 | Since 2021, we’ve seen three PHP releases—PHP 8.2, 8.3, and the freshly released [PHP 8.4](https://www.php.net/releases/8.4/en.php). Here are just a few highlights from these releases, developed by the PHP Foundation team:
22 |
23 | - [Property hooks](https://wiki.php.net/rfc/property-hooks)
24 | - [Asymmetric Visibility](https://wiki.php.net/rfc/asymmetric-visibility-v2)
25 | - [Lazy Objects](https://wiki.php.net/rfc/lazy-objects)
26 | - [New tool for installing extensions: pie](https://thephp.foundation/blog/2024/11/19/pie-pre-release/)
27 | - [Support object type in BCMath](https://wiki.php.net/rfc/support_object_type_in_bcmath)
28 | - [Saner Increment/Decrement operators](https://wiki.php.net/rfc/saner-inc-dec-operators)
29 | - Multiple type system improvements: [null and false as stand-alone types](https://wiki.php.net/rfc/null-false-standalone-types), [Disjunctive Normal Form Types](https://wiki.php.net/rfc/dnf_types)
30 | - [Readonly amendments](https://wiki.php.net/rfc/readonly_amendments)
31 | - [Dynamic class constant fetch](https://wiki.php.net/rfc/dynamic_class_constant_fetch)
32 | - [Arbitrary static variable initializers](https://wiki.php.net/rfc/arbitrary_static_variable_initializers)
33 |
34 | ## Feature development is only about 20% of what the foundation team does
35 |
36 | Behind the scenes, there’s a lot more: triaging and fixing issues, handling security reports, reviewing code, updating documentation, and maintaining infrastructure. All of this work empowers the community and ensures PHP is stable and reliable.
37 |
38 | Here are some highlights:
39 |
40 | - The total contributions to the PHP repositories grew by 51+%
41 | - We conducted the first external security audit for PHP in 10 years
42 | - We extended security support for PHP versions by one year
43 | - We improved CI and testing infrastructure
44 | - We introduced automated benchmarks to track performance regressions
45 |
46 | None of this would be possible without our sponsors. Huge thanks to every company and individual who has supported us over the past three years!
47 |
48 | Special shout-outs to:
49 | JetBrains, Automattic, Sovereign Tech Agency, Craft CMS, Private Packagist, Tideways, Zend by Perforce, Laravel, Symfony, Mercari Inc., Les-Tilleuls.coop, pixiv Inc., Aternos GmbH, Sentry, Ardennes-étape, Cybozu,
50 |
51 | and many others — PHP is all of us!
52 |
53 | If you haven’t already, please consider [sponsoring the PHP Foundation](https://thephp.foundation/sponsor/) 🙏
54 |
55 | Here’s to PHP and many more years ahead!
56 | 🐘💜
57 |
--------------------------------------------------------------------------------
/source/_posts/2024-12-23-happy-holidays-from-the-php-foundation.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'Happy Holidays from The PHP Foundation!'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 23 December 2024
10 | ---
11 |
12 | As 2024 comes to a close, we at the PHP Foundation want to take a moment to thank everyone who has supported us this year. It’s been an incredible journey, and we couldn’t have done it without the amazing PHP community and our generous sponsors.
13 |
14 | ## A Year of Milestones
15 |
16 | In [its third year](https://thephp.foundation/blog/2024/11/22/php-foundation-turns-three), the PHP Foundation has achieved several milestones that have further strengthened the PHP ecosystem: first in a decade [security audit](https://thephp.foundation/blog/2024/11/22/php-foundation-turns-three/#feature-development-is-only-about-20%25-of-what-the-foundation-team-does), [pie](https://thephp.foundation/blog/2024/11/19/pie-pre-release/), numerous features and improvements for [PHP 8.4](https://www.php.net/releases/8.4/en.php), and much more to come next year!
17 |
18 | ## Celebrating Our Sponsors
19 |
20 | We owe a special thanks to our major sponsors who make our work possible:
21 |
22 | ### Platinum
23 |
24 | [**Sovereign Tech Agency**](https://www.sovereign.tech/)
25 |
26 | [**JetBrains**](https://www.jetbrains.com/)
27 |
28 | [**Automattic**](https://automattic.com/)
29 |
30 | ### Gold
31 |
32 | [**Laravel**](https://laravel.com/)
33 |
34 | [**GoDaddy**](https://www.godaddy.com/) **\[new! ✨\]**
35 |
36 | ### Silver
37 |
38 | [**Private Packagist**](https://packagist.com/)
39 |
40 | [**Craft CMS**](https://craftcms.com/)
41 |
42 | [**Cybozu**](https://cybozu.co.jp/en/company/)
43 |
44 | [**Tideways**](https://tideways.com/)
45 |
46 | [**Zend by Perforce**](https://www.zend.com/)
47 |
48 | [**Symfony Corp**](https://symfony.com/)
49 |
50 | [**Sentry**](https://sentry.io/welcome/)
51 |
52 | [**Manychat**](https://manychat.com/) **\[new! ✨\]**
53 |
54 | [**Mercari Inc.**](https://www.mercari.com/)
55 |
56 | [**Les-Tilleuls.coop**](http://Les-Tilleuls.coop)
57 |
58 | [**pixiv Inc.**](https://www.pixiv.net/en/)
59 |
60 | [**Aternos GmbH**](https://aternos.gmbh/en/)
61 |
62 | [**CH Studio**](https://chstudio.fr/en/homepage/)
63 |
64 | Big thanks to newly joined major sponsors: [**GoDaddy**](https://www.godaddy.com/) and [**Manychat**](https://manychat.com/)!
65 |
66 | Your contributions enable us to support developers, fund crucial projects, and ensure PHP is a modern and reliable choice for web development.
67 |
68 | If you are yet to decide on sponsoring the foundation, [here](https://thephp.foundation/blog/2024/09/30/call-fo-sponsors/) you can find information on how to join us and why it matters.
69 |
70 | ## Wishing You Joyful Holidays ✨
71 |
72 | To everyone in the PHP community, we wish you a joyful holiday season filled with warmth, happiness, and a well-deserved break. Thank you for your support, passion, and commitment to PHP.
73 |
74 | Here’s to a wonderful 2025! 🥂
75 |
76 | Warm wishes,
77 | The PHP Foundation
78 | 🐘💜
79 |
--------------------------------------------------------------------------------
/source/_posts/2025-01-31-laracons.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'Proud to Be Community Sponsors of Laracon EU and Laracon India'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 30 January 2025
10 | ---
11 |
12 | The PHP Foundation is thrilled to announce our community sponsorship of both Laracon EU and Laracon India! We believe in the power of in-person connections and are excited to support these conferences as they bring together PHP enthusiasts from around the world.
13 |
14 | ## [Laracon EU](https://laracon.eu/)
15 |
16 | * **Location:** Amsterdam, Netherlands
17 | * **Date:** February 3–4
18 | * **Meet us:** This year at Laracon EU you can meet [Roman Pronskiy](https://www.linkedin.com/in/pronskiy), [Sebastian Bergmann](https://www.linkedin.com/in/sebastian-bergmann-phpunit), and [Nils Adermann](https://www.linkedin.com/in/nilsadermann/) from the PHP Foundation board. Can you spot our first ever conference banner?
19 |
20 | ## [Laracon India](https://laracon.in/)
21 |
22 | * **Location:** Ahmedabad, India
23 | * **Date:** March 8–9
24 | * **Sponsorship:** Laracon India [welcomes sponsors](https://docs.google.com/forms/d/e/1FAIpQLScQTQJA9tnpwnED3Af61EyewEr7T2bybBR5GJ3MUd3x52FhrA/viewform) who are eager to support the Laravel community and connect with talented developers in India.
25 |
26 | ## Let's Collaborate!
27 |
28 | The PHP Foundation is committed to fostering the growth and development of the PHP ecosystem. We’re excited to collaborate with and support (non-financially) PHP conferences and meetups worldwide!
29 |
30 | 📩 Get in touch: contact@thephp.foundation.
31 |
32 | Here are a few upcoming events to watch for:
33 |
34 | * [PHP UK Conference 2025](https://www.phpconference.co.uk/) – London, UK, February 19.
35 | * [Dutch PHP Conference](https://phpconference.nl/) – Amsterdam, March 18–21.
36 | * [PHP Conference Odawara 2025](https://phpcon-odawara.jp/2025/) – Japan, April 12.
37 | * [PHPDay](https://www.phpday.it/) – Verona, May 16-17.
38 | * [php\[tek\] 2025](https://phptek.io/) – Chicago, IL, USA, May 20-22.
39 | * [PHPers Summit 2025](https://summit.phpers.pl/en/) – Poznań, Poland, 24-25 May.
40 | * [International PHP Conference](https://phpconference.com/berlin-en/) – Berlin, June, 3–5.
41 |
42 | 🐘💜
43 |
--------------------------------------------------------------------------------
/source/_posts/2025-04-03-welcoming-passbolt-to-the-php-foundation.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'Welcoming Passbolt to the PHP Foundation'
3 | layout: post
4 | tags:
5 | - news
6 | - sponsors
7 | author:
8 | - name: Roman Pronskiy
9 | url: https://twitter.com/pronskiy
10 | published_at: 3 April 2025
11 | ---
12 |
13 | We’re thrilled to announce that **Passbolt has joined the PHP Foundation** as a Silver sponsor! PHP powers over 77% of the web – including Passbolt’s collaborative password and secrets manager. Their support strengthens our mission to keep it thriving.
14 |
15 | Check out their heartfelt announcement here: **[Passbolt’s Blog](https://www.passbolt.com/blog/a-love-letter-passbolt-joins-the-php-foundation-as-a-company-member)**.
16 |
17 | The Foundation funds developers to ensure PHP remains fast, secure, and innovative. With Passbolt and many other industry leaders by our side, we’re building a sustainable future for the language we all rely on.
18 |
19 | > This post kicks off a new blog series highlighting our amazing sponsors. Stay tuned as we spotlight the companies and individuals driving PHP forward – each one a vital part of our community’s success.
20 |
21 | Want to join the effort? [Sponsor The PHP Foundation](https://thephp.foundation/sponsor/) and help us power the web’s backbone!
22 |
23 | 🐘💜
24 |
--------------------------------------------------------------------------------
/source/_posts/2025-04-10-php-core-security-audit-results.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'PHP Core Security Audit Results'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 10 April 2025
10 | ---
11 |
12 | The PHP Foundation is pleased to announce the completion of a comprehensive security audit of the PHP source code ([php/php-src](https://github.com/php/php-src)), **commissioned by the [Sovereign Tech Agency](https://www.sovereign.tech/)**.
13 |
14 | This initiative was organized in partnership with the [Open Source Technology Improvement Fund](https://ostif.org/) (OSTIF) and executed by the esteemed security group [Quarkslab](https://www.quarkslab.com/).
15 |
16 | ## Audit Overview
17 |
18 | Conducted over a two-month period in 2024, the audit encompassed:
19 |
20 | * Development of a threat model tailored to php-src
21 | * Manual code reviews
22 | * Dynamic testing procedures
23 | * Cryptographic assessments
24 |
25 | The collaboration between Quarkslab’s auditors and PHP maintainers ensured a thorough examination of the codebase.
26 |
27 | > _⚠️_
28 | Due to budget constraints, the recent security audit focused on the most critical components of the PHP source code rather than the entire codebase. Organizations interested in sponsoring a comprehensive audit or additional assessments are encouraged to [contact us](mailto:contact@thephp.foundation)!
29 | > _⚠️_
30 |
31 | ## Key Findings
32 |
33 | The audit identified 27 issues, with 17 having security implications:
34 |
35 | * 3 High-severity
36 | * 5 Medium-severity
37 | * 9 Low-severity
38 |
39 | Additionally, 10 informational findings were reported.
40 |
41 | Notably, four vulnerabilities received CVE identifiers:
42 |
43 | * CVE-2024-9026: Log tampering vulnerability in PHP-FPM, allowing potential manipulation or removal of characters from log messages.
44 | * CVE-2024-8925: Flaw in PHP’s multipart form data parsing, potentially leading to data misinterpretation.
45 | * CVE-2024-8929: Issue where a malicious MySQL server could cause the client to disclose heap content from other SQL requests.
46 |
47 | ## Recommendations and Resolutions
48 |
49 | Quarkslab’s report commended the overall high quality and specification adherence of the php/php-src project.
50 |
51 | The PHP development team has addressed all identified issues. Users are strongly encouraged to upgrade to the latest PHP versions to benefit from these security enhancements.
52 |
53 | ## Acknowledgments
54 |
55 | We extend our gratitude to the individuals and organizations that made this audit possible:
56 |
57 | * **The PHP Foundation Team and PHP maintainers:**
58 | Jakub Zelenka, Arnaud Le Blanc, Niels Dossche, Ilija Tovilo, Stas Malyshev, Dmitry Stogov, Derick Rethans, and Roman Pronskiy.
59 | * **Quarkslab Team:**
60 | Angèle Bossuat, Julio Loayza Meneses, Mihail Kirov, Sebastien Rolland, Ramtine Tofighi Shirazi.
61 | * **Sovereign Tech Agency:**
62 | Abigail Garner and the team – for commissioning the audit and all the help.
63 | * **OSTIF:**
64 | Amir Montazery, Derek Zimmer, Helen Woeste – for organizing the collaboration.
65 |
66 | This audit underscores our commitment to enhancing PHP’s security and reliability. We remain dedicated to ongoing improvements and collaborations to ensure PHP’s robustness for the global development community.
67 |
68 | ## Further Reading
69 |
70 | * [Audit Report](/assets/files/24-07-1730-REP-V1.4_temp.pdf)
71 | * [OSTIF Blog](https://ostif.org/php-audit-complete/)
72 | * [Quarkslab Blog](https://blog.quarkslab.com/security-audit-of-php-src.html)
73 |
74 | If your company is interested in commissioning another round of security audit, please contact The PHP Foundation team: [contact@thephp.foundation](mailto:contact@thephp.foundation).
75 |
76 | 🐘💜
77 |
--------------------------------------------------------------------------------
/source/_posts/2025-05-09-manychat-powered-by-php.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'Meet Manychat: A PHP Foundation Sponsor Sharing Their PHP Scaling Journey'
3 | layout: post
4 | tags:
5 | - news
6 | - sponsors
7 | author:
8 | - name: Roman Pronskiy
9 | url: https://twitter.com/pronskiy
10 | published_at: 9 May 2025
11 | ---
12 |
13 | At the PHP Foundation, we’re proud to be supported by companies that build amazing products and contribute back to the PHP ecosystem. Today we’d like to highlight [Manychat](https://manychat.com/?utm_source=phpfoundation&utm_medium=site&utm_campaign=casestudy) — one of our Silver sponsors.
14 |
15 | Manychat is the world’s leading chat marketing platform, helping businesses connect with their customers on Instagram, WhatsApp, Facebook Messenger, and beyond. With over **1 billion conversations powered every year** across **170+ countries**, Manychat is a great example of how PHP scales and supports high-traffic applications around the world.
16 |
17 | ## Why PHP? Because Speed Wins
18 |
19 | In their recently published case study — _[How Manychat Scaled to 1 Billion Conversations Using PHP](https://medium.com/manychat-engineering/how-manychat-scaled-to-1-billion-conversations-using-php-a-startups-guide-to-smart-tech-choices-781c74f16f23)_ — the Manychat team shares the story of how PHP helped them go from a tiny startup with just one developer to a platform supporting millions of users.
20 |
21 | > _“We could build right away — our only developer already knew PHP, so we skipped onboarding and got straight to work.”_
22 |
23 | By choosing PHP, Manychat was able to build their MVP in just a few days and start learning from real users immediately. As they grew, they faced the familiar scaling challenges of high traffic, heavy workloads, and resource management. Their case study provides mentions architectural decisions they made — from using asynchronous request handling with NGINX + Lua, to optimizing background task processing with PHP-CLI workers, and managing database connections efficiently with PgBouncer.
24 |
25 | ## PHP at the Heart of a Global Platform
26 |
27 | Today Manychat’s platform continues to run on PHP, handling millions of API calls and conversations while keeping infrastructure costs under control.
28 |
29 | If you’re excited about building products that reach millions and love working with PHP at scale, check out the [open positions at Manychat](https://careers.manychat.com/team/engineering?utm_source=phpfoundation&utm_medium=site&utm_campaign=casestudy). They’re hiring PHP engineers!
30 |
31 | ## Supporting the Community
32 |
33 | Manychat isn’t just building with PHP — they’re giving back to the community. As a **Silver sponsor** of the PHP Foundation, they help us fund initiatives that keep PHP stable, modern, and accessible to millions of developers worldwide.
34 |
35 | In addition, Manychat is active in the tech community, hosting [PHP meetups and events](https://www.eventbrite.com/o/manychat-46565622503) in **Barcelona** and **Amsterdam**. We love seeing our sponsors not only build great products but also foster connections between developers around the world.
36 |
37 | ## Read Their Story
38 |
39 | We encourage you to check out their full case study on scaling with PHP:
40 |
41 | 👉 _[How Manychat Scaled to 1 Billion Conversations Using PHP](https://medium.com/manychat-engineering/how-manychat-scaled-to-1-billion-conversations-using-php-a-startups-guide-to-smart-tech-choices-781c74f16f23)_
42 |
43 |
44 | **Thank you, Manychat, for your support!**
45 |
46 | 🐘💜
47 |
48 |
49 |
50 |
51 | > This post continues the [blog series](https://thephp.foundation/blog/tag/sponsors/) highlighting our amazing sponsors. Stay tuned as we spotlight the companies and individuals driving PHP forward – each one a vital part of our community’s success.
52 |
53 | Want to join the effort? [Sponsor The PHP Foundation](https://thephp.foundation/sponsor/) and help us power the web’s backbone!
54 |
55 |
56 |
--------------------------------------------------------------------------------
/source/_posts/2025-05-15-frankenphp.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 'FrankenPHP Is Now Officially Supported by The PHP Foundation'
3 | layout: post
4 | tags:
5 | - news
6 | author:
7 | - name: Roman Pronskiy
8 | url: https://twitter.com/pronskiy
9 | published_at: 15 May 2025
10 | ---
11 |
12 | [FrankenPHP](https://frankenphp.dev), a modern high-performance PHP application server created by [Kévin Dunglas](https://dunglas.dev) and sponsored by [Les-Tilleuls.coop](http://Les-Tilleuls.coop), is now officially supported by the PHP Foundation. FrankenPHP integrates PHP directly into Go and Caddy, simplifying deployment, improving performance, and reducing costs. It powers real-time features, supports advanced hosting scenarios, and offers a performance-boosting “worker mode” already integrated by Laravel, Symfony, and Yii. The PHP Foundation will actively contribute to FrankenPHP’s development and host its code on the official PHP GitHub, marking a major step toward modernizing the PHP ecosystem while keeping governance with the original maintainers.
13 |
14 | 
15 |
16 | PHP is a programming language used by around 70% of websites and applications, and by key software and frameworks such as [WordPress](https://wordpress.org), [Laravel](https://laravel.com), and [Symfony](https://symfony.com).
17 |
18 | FrankenPHP offers a host of new features that allow to:
19 |
20 | * simplify the development of applications written in PHP;
21 | * drastically improve performance, while considerably reducing hosting costs (FinOps) and energy consumption (GreenOps);
22 | * facilitate deployment in production, whether on bare-metal servers or in cloud-native environments;
23 | * easily develop real-time features thanks to native [Mercure](https://mercure.rocks) protocol support;
24 | * extend PHP apps with Go, C, and C++ programming languages;
25 | * support the PHP programming language in any application written in Go (server, proxy, in-house development...).
26 |
27 | Specifically, FrankenPHP integrates the official PHP interpreter as a module for Go and [Caddy](https://caddyserver.com), the popular next-generation web server that supports the latest web platform innovations in terms of performance, security, and DevOps: HTTP/3, compression with Zstandard, 103 Early Hints, automatic generation and renewal of HTTPS certificates, Encrypted Client Hello, structured logs, OpenMetrics/Prometheus metrics… Caddy is also co-maintained by Kévin and sponsored by Les-Tilleuls.coop.
28 |
29 | Thanks to its innovative architecture, FrankenPHP lets you install a complete PHP environment (interpreter, web server, extensions, etc.) optimized for performance and security, by downloading a standalone statically compiled executable or a Docker image.
30 |
31 | FrankenPHP also offers a performance-optimized mode called “worker mode”, which takes advantage of the capabilities of the Go programming language. When this optional mode is used, the PHP application will be able to retain in memory those elements that can be reused to process other HTTP requests instead of being completely reset to process each incoming HTTP request (“share nothing” model). Worker mode is especially useful for frameworks such as Symfony and Laravel that can prevent rebuilding their kernels and services again and again for nothing.
32 |
33 | Using this mode requires minimal adaptations to the code of modern PHP applications in line with good programming practice. The Laravel, Symfony and Yii frameworks already offer official integrations of FrankenPHP's worker mode, enabling worker mode to be activated without modifying the application code.
34 |
35 | According to [an analysis carried out this summer by Sylius](https://sylius.com/blog/ecosystem/month-of-sylius-august-2024/#frankenphp), the publisher of the eponymous e-commerce platform, the use of FrankenPHP's worker mode reduces the software's response times by 80%, while reducing by more than 6 the number of machines required to serve the same number of users.
36 |
37 | FrankenPHP is now a reliable, mature solution used in production for an ever-increasing number of projects. The project now has [almost 8,000 stars on GitHub](https://github.com/dunglas/frankenphp), has passed the symbolic 100-contributor mark, and is officially supported by numerous hosting providers, including Upsun, Laravel Cloud, and Clever Cloud.
38 |
39 | To get to this point, it was necessary to initiate close collaboration between the development teams of FrankenPHP, the PHP interpreter itself, the Caddy web server, and even the Go programming language.
40 |
41 | Today, we're proud to announce that, with the aim of intensifying this collaboration, enabling the project to gain momentum, and modernizing the entire PHP ecosystem, **the FrankenPHP project is now officially supported by the PHP Foundation**.
42 |
43 | In concrete terms, FrankenPHP's source code will be transferred to the PHP project's GitHub organization, and the PHP Foundation team will contribute to the maintenance and development of FrankenPHP to ensure its reliability, durability, and compatibility with the latest language innovations.
44 |
45 | Part of the FrankenPHP documentation will also be transferred to the PHP website.
46 |
47 | The governance of the project remains unchanged, and the current team of maintainers (Kévin Dunglas, Robert Landers, Alexander Stecher) will continue to be in charge of releases, as well as code reviews. They will be actively collaborating with the PHP Foundation team in charge of the language development.
48 |
49 | In addition to the support provided by the foundation, Les-Tilleuls.coop will continue to sponsor FrankenPHP (as well as PHP and Caddy) by providing developers and contributing financially.
50 |
51 | FrankenPHP is already [promoted by Caddy](https://caddyserver.com/#:~:text=4x%20faster%20PHP%20apps) as the official, modern solution for using PHP with this server.
52 | In the future, to simplify the PHP development experience (one-line installation of a complete development environment) and to promote a solution that, for projects requiring it, considerably improves the performance and efficiency of PHP applications, FrankenPHP may be highlighted on the PHP website as one of the ways to use the language (other SAPIs such as PHP-FPM will continue to be fully supported solutions).
53 |
54 | To find out more about FrankenPHP and the many new possibilities it offers, take a look at [its documentation](https://frankenphp.dev). To meet the software's authors and find out how it is used in production, don't miss [the API Platform conference](https://api-platform.com/con/) (by the same authors as FrankenPHP) taking place on September 18 and 19 in France (Lille).
55 |
56 | Also, join us online for [**PHPverse on June 17**](https://lp.jetbrains.com/phpverse-2025/) — a special event celebrating PHP’s 30th anniversary.
57 |
58 | Finally, to help keep the PHP ecosystem innovating, [support the foundation](https://thephp.foundation/sponsor/)!
59 |
60 | [The PHP Foundation](https://thephp.foundation/)
61 | [Les-Tilleuls.coop](http://Les-Tilleuls.coop)
62 | [The Caddy team](https://caddyserver.com)
63 |
--------------------------------------------------------------------------------
/source/_views/page-wide.html:
--------------------------------------------------------------------------------
1 | {% extends 'default' %}
2 |
3 | {% block content_wrapper %}
4 |
5 |
29 | 
9 | 
53 | 
