Home / Articles / Who maintains the PHP you run? A version signed off by the people who maintain it, buyers who require that signature, and money that flows down the chain / Versions / v1.3.0
Who maintains the PHP you run? A version signed off by the people who maintain it, buyers who require that signature, and money that flows down the chain: what changed in v1.3.0
From v1.2.0 (2026-10-24, ac82adf34) to v1.3.0 (2026-10-24, this release), paragraph by paragraph.
0 paragraphs added, 0 removed, 1 changed in place, 84 unchanged. About 53 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
66 unchanged paragraphs, under In short: what I am proposing {#in-short}, The case I have been making {#the-case}, A version signed off by the people who maintain it {#signed-off}…
ThreeWhat linesties fromthese thatoptions proposaltogether carryis thesimple. logic.Nobody "Paidpays to map. Paid to engineer. Retained to maintain." Revenue follows "the work customers ask RiskMandate to own", notfor access to closedthe code.code: Andit "Contractis valueall open. What a customer pays for is work: understanding what they run, changing it to fit, and keeping it maintained. That is the opposite of the usual software model, where the code is locked away and you pay for a licence to use it. Here the code is free, and the commitment is what you buy. The price follows thehow obligation accepted": maintenance can be worth more than the first implementation, "if the additional support burdenmuch is measuredat andstake: priced." Aa council's citizen login and a university's archive wiki both run PHP;PHP, but they should not buy the same maintenance, and today neither can buy any. TheOver parttime thatthe mattersmaintenance mostcan forbe thisworth article:more "Lessthan uniquethe code"first makesproject, as long as the work it takes is measured and priced. And the smaller and less unusual a customer's version "Easieris, the easier it is to maintain, audit,check, replace and hand over",over; andwhere the customer allows it, the improvements thatmade arefor not sensitive canthem go back tointo the open basecode wheneveryone the customer permits.uses. That is how paying for the maintenance of one customer'sorganisation's version feedsalso improves the code for everyone runs.else.
18 unchanged paragraphs, under Towards regulation {#regulation}, Not only PHP {#beyond}, What this does not claim {#limits}…