John and Eric share more of the day-to-day behind-the-scenes work that goes on at php[architect]. This episode of php is sponsored by JetBrains PhpStorm We discuss php[tek] 2024, writing for the magazine, and what is coming in the next release of php[architect] magazine. Join the Discord at https://phpa.me/discord Subscribe to the Magazine Today https://phpa.me/signup Twitter * @phparch=> ‘Official PHP Architect’ * @phptek => ‘php[tek] Conference’ * @johncongdon=> Host John Congdon * @shocm=> Host Eric Van Johnson Mastodon * @[email protected] => ‘Official PHP Architect’ * @[email protected] => ‘Official PHP Architect’ * @[email protected]=> Host John Congdon * @[email protected]=> Host Eric Van Johnson

Interview With Eric Mann Release Manager PHP 8.3 In this episode, Scott talks with Eric Mann about his experience as one of the PHP 8.3 Release Managers and writing his book PHP Cookbook. Note: this transcript was transcribed by AI and then edited for clarity. Scott Keck-Warren: Hello developers, and welcome to the php[architect] community corner, where we have conversations with members of the web development community. I’m your host, Scott Keck-Warren, and today we’re talking with Eric Mann about being a release manager for PHP 8.3 and his new book PHP Cookbook. Eric Mann is a well-established cybersecurity, software, and infrastructure engineer, having led multiple teams of various sizes in the private sector. Eric has experience architecting highly-available and resilient SaaS platforms, scalable e-commerce websites, and industry-defining AI/ML operations. In addition to leading technical teams, Eric frequently lectures at events on both scalable engineering and cybersecurity. He also publishes books on programming and secure software design. Eric is a member of both ISACA (Information Systems Audit and Control Association) and OWASP (Open Worldwide Application Security Project) and is a release manager for PHP 8.3. I wanted to start out today and ask you about your experience as one of the release managers for PHP 8.3. Eric Mann Okay. Cool. Yeah. The experience has been fantastic thus far. It’s been a really supportive community, making sure that we get everything taken care of as quickly and as reliably as we can. One of the things that is really interesting, I did not understand the PHP release process before I started this. I knew we had release managers. I knew we had a release process, but I didn’t really understand what it looked like. So understanding that we cut the release or package the release on one day. On the next day, people will bundle the release for various distributions, and then on the third day we will announce it actually made me feel a lot better just knowing that everybody works from very disparate time zones. And I was really concerned about calendar coordination. So one of the biggest things I learned was both what the release process looked like, but also just how well suited it is for asynchronous operations and remote work. The fact that I am on the US West Coast and the rest of the release managers are not even in the US, it’s been amazing to coordinate with folks across borders and make sure that we can do things both across borders and across time zones. And as far as how seamless things are from the outside perspective, you can’t tell. Everything is just nice and smooth, and the operation moves forward perfectly well. And I think that’s been amazing and fantastic to learn and see from the inside. Scott Keck-Warren: So it kind of sounds like the whole process is set up to be asynchronous. Eric Mann It very much is. The way things will typically work is in a release week at some point in time on Tuesday, you will build the release, make sure everything is ready to go, tag the release and then email to tell everybody, hey, the release is ready. Please go ahead and run your builds for Debian and other operating systems, Windows and whatnot. Sometime on Wednesday, the builders will run their builds and say, hey, here are the builds. They’ll check to see if anything unexpected happened and then let people know where the builds live. And then on Thursday, at some point in time, the release manager will go through and post the announcement for the release, showing where the hash checksums live, where the signatures live, where the binaries live, and all of the compressed artifacts. But all of these happen at different times and everything’s coordinated completely asynchronously via email. I have now personally managed releases from three se...

John and Eric share more of the day-to-day behind-the-scenes work that goes on at php[architect]. This episode of php is sponsored by JetBrains PhpStorm We discuss php[tek] 2024, writing for the magazine, and what is coming in the next release of php[architect] magazine. Join the Discord at https://phpa.me/discord Subscribe to the Magazine Today https://phpa.me/signup Twitter * @phparch=> ‘Official PHP Architect’ * @phptek => ‘php[tek] Conference’ * @johncongdon=> Host John Congdon * @shocm=> Host Eric Van Johnson Mastodon * @[email protected] => ‘Official PHP Architect’ * @[email protected] => ‘Official PHP Architect’ * @[email protected]=> Host John Congdon * @[email protected]=> Host Eric Van Johnson   :q

In this episode, Scott talks with Eric Van Johnson of PHP[architect] LLC, about writing for the php[architect] magazine, the talk submissions process for php[tek], and why you should have a subscription to php[architect]. Interview With Eric Van Johnson   Note: this transcript was transcribed and then edited for clarity and to make it easier to read. Scott Keck-Warren: Hello Developers, and welcome to episode one of the PHP Architect Community Corner, where we have conversations with members of the PHP community and the technology community at large. I’m your host, Scott Keck-Warren. Today we’re talking with Eric Van Johnson about submitting articles to the php[architect] magazine, the selection process for talks at php[tek] 2024, and the benefits of having a subscription to the php[architect] magazine. Eric Van Johnson is one of the minds behind php[architect] LLC. Described as loud and passionate about the PHP programming language, he has been known to record a podcast or two, or maybe even three. Powered by scotch and hope, you can follow Eric on Twitter @shocm / Mastdon @[email protected]. Thank you, Eric, for finding time to talk with us today.   Eric Van Johnson: Scott, thanks for taking the time to talk to me, I appreciate it. Scott Keck-Warren: Absolutely!   Writing for php[architect]   Scott Keck-Warren: I know that the php[architect] magazine is a magazine made by the community for the community, and you’re constantly looking for contributors to help write articles. If I had an idea for an article, what would the process be? Eric Van Johnson: Right? Great question. I appreciate you asking. It’s really meant to be as least stressful as we can be. Essentially, there’s just so much good information out there that we as developers, hold onto, and we want to make sure everybody has an outlet to share that because it’s just nonstop. You know, our industry is always changing. There’s always new things emerging, how we do things. There’s no one right way to do things. So everybody has, you know, a thought or an understanding or knowledge of something.   If you’re interested in contributing to php[architect] the magazine. You just simply reach out to us and it can be as casual as, “Hey, I have an idea for an article. Is this something you would be interested in?” We’re pretty straightforward with you. We’ll give you a yes or no. Ideally, we like things focused on PHP. That’s kind of our always our free pass. But even if it’s PHP adjacent where it’s like web technology or web development or something like that, even then we’ll give it a listen and kind of talk through it.   Eric Van Johnson: After that, all we ask is for the article to be ideally between 2500 and 3500 words. That seems like a lot but really, once you start writing, it flies by. Commonly, people contribute well over 3500. And that’s okay as well. That 3500 is not the high bar if you hit it then everything gets cut off. It’s more like that’s the sweet spot for us to get it in one release of a magazine. We’ve had articles, 5000 words, 6000 words, and all we end up doing is breaking those out across a couple of releases.   Once we agree on a topic and you understand what we ask as far as a deliverable, you then tell us when you think you can have it done. Now, this is not a hard deadline you’re setting for yourself. It’s just for us on our end. We add those articles to our pipeline and we can see, oh, Scott says in December he’s going to have a feature article for us. Haven’t heard from Scott, so we’ll assume he’s still targeting that December release. If you do end up having to postpone it and you need more time,

John and Eric share more of the day to day behind the scenes work that goes on at php[architect]. This episode of php is sponsored by JetBrains PhpStorm Join the Discord at https://phpa.me/discord Subscribe to the Magazine Today https://phpa.me/signup Twitter * @phparch=> ‘Official PHP Architect’ * @phptek => ‘php[tek] Conference’ * @johncongdon=> Host John Congdon * @shocm=> Host Eric Van Johnson Mastodon * @[email protected] => ‘Official PHP Architect’ * @[email protected] => ‘Official PHP Architect’ * @[email protected]=> Host John Congdon * @[email protected]=> Host Eric Van Johnson   :q

John and Eric share more of the day to day behind the scenes work that goes on at php[architect]. This episode of php is sponsored by JetBrains PhpStorm Join the Discord at https://phpa.me/discord Subscribe to the Magazine Today https://phpa.me/signup Twitter * @phparch=> ‘Official PHP Architect’ * @phptek => ‘php[tek] Conference’ * @johncongdon=> Host John Congdon * @shocm=> Host Eric Van Johnson Mastodon * @[email protected] => ‘Official PHP Architect’ * @[email protected] => ‘Official PHP Architect’ * @[email protected]=> Host John Congdon * @[email protected]=> Host Eric Van Johnson   :q

John and Eric share more of the day to day behind the scenes work that goes on at php[architect]. This episode is sponsored by JetBrains PhpStorm Join the Discord at https://phpa.me/discord Subscribe to the Magazine Today https://phpa.me/signup Twitter @phparch @johncongdon @shocm Mastodon @[email protected] @[email protected] @[email protected]

John and Eric share more of the day to day behind the scenes work that goes on at php[architect]. This includes a lot of talk on php[tek]. They also talk about the latest edition of the magazine “Box of PHP”. Join the Discord at https://phpa.me/discord Get your early bird php[tek] tickets before the price goes up at https://tek.phparch.com   Subscribe to the Magazine Today https://phpa.me/signup Join us at php[tek] 2023 php[tek] 2023 Twitter @phparch @phptek @johncongdon @shocm Mastodon phparch.social@editor phparch.social@tek phparch.social@john phparch.social@eric

Join the Discord at https://phpa.me/discord Get your early bird php[tek] tickets before the price goes up at https://tek.phparch.com   Subscribe to the Magazine Today https://phpa.me/signup Join us at php[tek] 2023 php[tek] 2023 Twitter @phparch @phptek @johncongdon @shocm Mastodon phparch.social@editor phparch.social@tek phparch.social@john phparch.social@eric

Subscribe to the Magazine Today https://phpa.me/signup Join us at php[tek] 2023 php[tek] 2023 Twitter @phparch @phptek @johncongdon @shocm Mastodon phparch.social@editor phparch.social@tek phparch.social@john phparch.social@eric