> On 28/10/18 11:54 pm, Kalle Sommer Nielsen wrote: > > Den lør. 27. okt. 2018 kl. 22.52 skrev Rasmus Lerdorf < ras...@lerdorf.com>: > >> But yes, perhaps it is time to end the mirror program and just CDN *. php.net. >>> What do others think? >> From a webmaster standpoint, I think it would ease management greatly >> to finally update that part of the infrastructure as often mirrors >> have some interested and hard to debug bugs. Besides, there isn't that >> many around who actively looks into mirrors so I think its just a >> win-win for us all. > >What are the next steps here? > >I have a contracting budget available for PHP upstream contributions, >which could be used to fund migration of the main website to HTTPS. >Getting rid of mirrors would presumably be part of that. The tricky >thing is finding someone with server access and time available. If >you're interested, please contact me with your desired hourly rate and >estimated number of hours. >
+1 on the entire modernizing the mirrors topic. I routinely field "questions" (whines, really) from people wondering why PHP is served via http:// rather than https:// and "because our mirror system is complicated, go use secure.php.net if you're worried" never satisfies anyone. Plus, I just did a scan of all our mirrors last night* (round-about reason why Derick pointed me to this thread in the first place) and came up that only about 8.75% of our mirrors run officially supported versions of PHP. Call that 40% if you want to include the recently EOL'd 5.6 and 7.0 branches, but even then few are at the tip of their branches, and many are lost in the past of 5.3 and 5.4. Aside: Shout-out to be2.php.net for running 7.3.0 As to how we make it happen: We almost certainly will need to change our deployment process to some notable degree. Personally, I would like to see us have *less* control over the systems than currently. There are a number of SaaS type vendors out there (who'd probably love to donate some bandwidth/cpu to our project btw) that deal with a lot of the overhead of systems administration and just expose the knobs of "what version of PHP do you want? What extensions? Now push your code to this git url". A couple years ago, I prototyped a migration of bugs.php.net to one of these and it was basically painless. In a perfect world, we'd have a beta.php.net site (or similar) which ran RC versions so we could bake them in prior to release. This would allow us to confidently keep php.net on the latest version and set a good example. But all that is cart before the horse. Perhaps we should start with an RFP. See who's willing to back this project, what kind of time commitment they'll give, and what they want in return. -Sara * Yes, I know there's a status page listing these versions, but the information there disagrees with the versions reported by some of the directly, so I decided not to trust it.
