On Sunday I met up with my friend and former OpenStack/HPE colleague Sean Dague who now also works on IBM Quantum. We’ve kept loosely in touch over social media, but it had been a few years since we’d actually connected in person, so it was really nice to have some time to catch up. That afternoon I also had the pleasure of finally meeting my colleague Rishi Misra in person, who I’ve worked closely with for years on s390x porting work. A nice start to a great week!

Monday kicked off with a series of opening keynotes. The other day I wrote a long, rambling blog post about open source and AI, so I won’t talk too much about the AI-heavy keynotes, except to say that there were some hopeful observations alongside the concerning ones around data and security. It was nice to see where the Linux Foundation was taking action to make sure we continue having an open source driven future. My favorite keynote of the morning was from Sean who talked about, you guessed it, IBM Quantum! Not only was I personally delighted to see Sean up on stage, I’ve always been fascinated by Quantum computing and have enjoyed seeing the progression over the past several years. His talk gave a whirlwind tour of the ecosystem and presented opportunities for developers that are still being offered by IBM. Also, it was a nice break from AI talks. Google and Microsoft also spoke on AI-related topics, with Microsoft also happening to mention an update around Azure Linux, which Steven Vaughan-Nichols helpfully covered here: Microsoft surprises with its first server Linux distribution: Azure Linux 4.0.

The next few talks I attended were around Open Source Program Offices (OSPOs), the first was a panel around scaling them, where I was happy to see a wide range of experiences presented from across industries, including Ford, Geico, and CISCO, with a moderator from GitHub. There’s definitely a trend of using AI tooling to help the work in OSPOs, especially as the work and importance of these organizations grow. I also enjoyed Dawn Foster’s talk on “Strategic Approach To Demonstrating the Value of OSS Efforts” where she presented the highlights of the Demonstrating Organizational Value Practitioner’s Guide that she co-wrote.

From there I dipped into a couple of MCP talks, starting with Automating MCP Server Testing from Neethu Elizabeth Simon of Arm. It was an interesting talk overall, but my big takeaway was the server she demonstrated with: the Arm MCP Server, which is “An MCP server providing AI assistants with tools and knowledge for Arm architecture development, migration, and optimization.” Cool. I took notes and was texting with Rishi about how we might be able to leverage something similar in the s390x world. From there I went to a talk on ContextForge in the context of managing MCP sprawl. It was also a timely talk for me since we had just on-boarded the project to our GitHub Actions runner a few weeks before and I’d been meaning to learn more about it. Done! It was also nice seeing Dave Neary and his What Developers Should Know About Hardware Architecture talk, where he throws out lots of interesting facts about things that matter in architectures, along with other topics like just how slow spinning disks are, especially compared to CPU caches.

Monday evening was the conference reception at the Mill City Museum. It’s a museum I had wanted to go to anyway, so I was happy to learn that was the reception venue. It was a nice museum about the history of flour milling in the city, and the elevator they converted into a “ride” that takes you up and down several floors through a history of the mill was an absolute delight. The views from the top where you’re let out were beautiful, especially since the rain hadn’t rolled in yet! Unfortunately, the rain did eventually come in, just as the scheduled drone show for the 35th anniversary of Linux was to start. The drone show still happened, but it wasn’t really dark enough and drizzle quickly turned into a thunderstorm.

Tuesday’s keynotes got us back in the realm of AI, with talks on Strands Agents from AWS and AI used in robotics. They also had a panel on the value of open source software foundations for projects, which surprised me as a keynote topic for an open source conference, because most of what was covered struck me as pretty basic, and I think a lot of folks in the audience had experience engaging with projects within foundations.

From there I went to a talk on Package Testing Across Distributions and Architectures at Scale where the presenter walked through a move away from dozens of servers and consolidated on x86 and arm64-based cloud servers, using Ansible Molecule. Alas, not immediately applicable in our s390x porting work, but it was an interesting tour of what they had done and how much disk speed impacts package building performance. An afternoon session from the OpenSSF that gave a whirlwind tour of their projects was also interesting, since it can be a little tricky to keep up if your day to day work is unrelated to security.

That evening was the Tux Trek in the expo hall, and in addition to some great conversations, including one where I got to nerd out about mainframe stuff to someone who was curious, I got a tux cotton candy! I then got to have dinner with Rishi and a colleague who I didn’t expect to see there: Cheryl Fillekes! She’s worked on various OpenShift products for Linux on IBM Z, and we’ve connected on various topics over the past several months (mostly when I needed something, hah!). It was really nice to meet her in person. I was also pleasantly surprised when she suggested our dinner adventure should include finding some Guinness 0 (non-alcoholic). You see, I’m a beer fan, but I got a bit sick back in March and have been taking a break from drinking until I feel better. Guinness 0 was a nice treat, and surprisingly good!

Day three began with the obligatory keynote discussion with Linus Torvalds, followed by another keynote about AI agents, but this time with a focus on specifically how they can help open source software maintainers. I really enjoyed Kate Stewart’s keynote on the Zephyr project though. Zephyr has been on my radar for a while, but playing with it is another one of those projects I am not sure I’ll get around to anytime soon. But hey, it turns out my RISC-V board is supported by Zephyr! That gets me one step closer!

The final keynote on Free to Use, Not Free to Run: Reinventing Package Registries is one that stuck with me. Basically, open source communities are running registries (PyPI, RubyGems, crates.io, etc) that companies using the ecosystem depend upon, but they’re becoming expensive to run, and projects are now hyper-aware of security and supply chain concerns that they need to take very seriously. So they’ve launched a Sustaining Package Registries Working Group to discuss concerns, and develop solutions together, up to and including starting to charge for industrial scale traffic. I’ve seen the thankless work that goes into things like PyPI. Helpfully, Stephen wrote about this too: 10 trillion downloads are crushing open-source repositories – here’s what they’re doing about it.

Most of the rest of my day was spent meeting up with people, but I also happy to make it to Rob Landley’s Building the Simplest Possible Linux System talk. I’ve seen Rob speak a few times over the years, and I love the enthusiasm for the work that he brings to it. He’s also been friendly in the realm of s390x porting, and I was delighted to see on his screen as he was preparing to begin that the emulated build he had up on the screen was s390x.

I talked a lot about sessions in this blog post, but ultimately what makes these events is the people. Connecting in person make a huge difference, and there were a lot of people I saw there who I hadn’t seen in a couple years. And this time I made sure to take lots of pictures!

With that, the summit came to an end. To close things out, I went out to enjoy another round of Guinness 0s with Cheryl before it was time to call it an early night before my 7AM flight home the next morning.

I also don’t think I’ve every heard the word “human” said so many times in a week. It’s weird to talk like that.

This blog post isn’t meant to be anything shocking or insightful in the realm of AI. It’s more a brain dump checkpoint for me personally to share what working through the shift to AI tooling is like from where I’m sitting. The value you can get from this post may vary ;)

The first thing I’ll say that I’ve never seen a tech industry shift happen this fast, and having been in the industry for nearly 25 years I’ve worked through some major transformations. In the past 9 months I’ve seen multiple cases where a conference CFP being 6+ months before the conference causes a considerable change in the resulting presentation material, I’ve seen two talks change their titles from what was listed because tools and companies rose and fell in that time. Tech has always been an industry of continuous learning, and I love that, but today if you haven’t spent some time learning about AI in the past 6 months, you’re going to be blindsided by a whole slew of terms and concepts. You’ll likely find it hard to learn at conferences because there’s so much new foundational AI knowledge that’s assumed. Indeed, I like to think I’ve stayed fairly well-informed, and even I had to go back to my room in the evening and do some learning so I could properly absorb what I had been exposed to throughout the day, and be ready for the next day. My conference notes have a lot more “learn more about this” notes than usual.

Career-wise, this has already proven to be a difficult time for people in tech. Huge layoffs have hit major tech companies with AI given as a reason. Obviously, this is incredibly painful for folks who have a mortgage to pay, health care costs, and mouths to feed; suddenly the market has become unrecognizable and they can’t find a new job. That sucks. The core programming skills that coding boot camps were founded on as being a golden ticket to a high paying job in tech are rapidly being replaced by AI tools. We’re not there yet, I’ve been reviewing some very bad AI-generated code in the past few months as I touched upon in my blog post about CPOSC, but there is a fast-paced trend of improvements. If the rise of AI in programming turns out to be sustainable (capacity can be expanded and that it continues to be cost-effective), the need for straight up entry level programmers will continue to decrease, and we’ll need more folks with more advanced skills related to computer science and architecture. How do you get more advanced skills without learning programming basics first? I don’t know the answer to that, but there are a lot of smart people trying to figure it out.

I’m also aware of the fact that adoption of things like AI agents will actually take a while in most companies. I think back to the rise of configuration management, and in spite of all the benefits, the amount of work it would take to rebuild their systems with configuration management in place was simply not a priority (indeed, in most shops I saw it implemented slowly, and only with new systems that were brought up). Will this be the case for AI agents as well? I had more than a few conversations where developers were using AI-assisted coding tools, but having an infrastructure that supported using agents to automatically carry out tasks was nowhere close to their reality. There’s also the question of economies of scale. A massive tech company like Google may see the value of heavily investing in AI, but for a company with a tech department of a half dozen folks? Maybe it doesn’t sense any time soon. After all, using that Perl script we’ve always used is still faster than re-writing everything in Puppet, since our ten servers are unique pets (no cattle here!).

Coming back to open source, I’ve also been thinking a lot about the reason companies invest in open source software. At the core, it’s because… of the core. Core technology is what everyone uses and there’s no business advantage to it, so it makes sense to invest in them collectively. Kubernetes is not what makes money, Red Hat OpenShift and the ecosystem built on top of it is, so SUSE can also play that game with Rancher. Is there a future where that core technology is created by AI, and it’s good and cheap, so the need for open source collaboration is no longer “worth the trouble”? I hope not. And not just because my livelihood depends upon it. I’ve always believed that open collaboration on tooling across the tech industry has literally made the world better.

At the Open Source Summit the keynotes were AI-heavy, as was to be expected. Jim Zemlin had a lot of positive things to say about the role of open source software today at every layer of the AI stack, but acknowledged that the final layer is what is missing: data.

The open data community will always lag behind here, because those who hold private data will always have the open data plus their own. It seems like the question that’s being asked is whether a vast pool of open data can be “enough”, even if it’s not “better” than the private data. This is already being seen with AI models, the best ones are proprietary, but the open ones? Pretty good! Probably good enough for most of us! The statistic Jim shared was that open source models only lag proprietary ones by 3-6 months, whereas the gap was measured in years back in 2022. The concern with data is that the desire for open data is arguably in direct competition with privacy and the ability for us to keep our servers running. What happens when you’re running a webserver and 80% of the traffic is bots collecting data rather than serving your customers? You get that bill, and that bill is getting larger. This leads to an inclination for organizations to pull back what they share, and put more and more behind paywalls and proxy services, or in apps that aren’t on the web. Still, the Linux Foundation still believes we’re in a world where the problem is not lack of data, but lack of coordination to collect and curate these data sources. Maybe.

Open source contributions were also a big topic. Speaking personally from a tiny, niche project I run, things have clearly changed. Until 2026, every contribution was from someone we personally engaged with in some way. This year we’ve received multiple small patches that have zero contextual awareness of the project, but fix common errors in code (cool, thanks!). My current core developer has pulled back on self-assigning issues when he creates them because we’ve started to see new contributors just show up and start working on them. That has never happened before. And are they AI-assisted? Definitely. In some ways this is great. A major change landed this week that would have taken us months to do without it. We’ve gotten lucky so far, that particular change had a clever developer behind it who was willing to engage with us through a month of back and forth with fixes and improvements, and he actually understood the code that was submitted. We can’t always bet on that, and that erodes trust. My default reaction to new contributors used to be elation, now it’s turning to apprehension. I hate that. We have drive-by contributors who will never use or care about the project, so their motivations aren’t driven by usage or focused on holistic improvements, but done in order to fill up their GitHub contributions graph. Some of this has always been this way, not everyone who contributes becomes part of a project in a real way, and some of these are changes that can improve the project! But it feels like the community element that drives lifelong open source contributors like myself to maintaining a project is slipping away. As someone whose closest and longest friendships have predominantly come from shared involvement and values related to open source, this is very sad for me.

See? I told you this blog post was personal. I’m getting all mushy when you expect me to only care about the code and what’s technically best for the project. But I’m human and me caring about community is what’s best for the project. That thrill of welcoming a new contributor and the connection we build as they move up through their career is what gets me through long nights, difficult decisions, and burnout, so I can continue being an effective contributor.

Another major topic of discussion at the summit related to AI was security. There have always been solid security teams for major open source projects, but the levels to which they were funded at and the tooling available have been less impressive. And smaller projects? Honestly, very little attention paid to security. This has started changing, but we’re not where we need to be, because the vulnerability landscape is changing much, much faster. By most estimates, the number of CVEs in 2026 is expected to exceed 50,000 for the first time. With AI-assisted scanning, it’s simple and cheap to find vulnerabilities in every single piece of open source code out there. So that little project on GitHub that had security through obscurity before? Not anymore. My little tool doesn’t just have bugs being identified and reported by AI tooling, it has security problems that are being identified and reported (or just exploited!).

There’s good work happening here though. The Open Source Security Foundation (OpenSSF) is leading the way on the foundation side, and continuously coming out with new tools to help projects (now they just need to adopt them, me included!). One of the talks I went to at the Open Source Summit was a really helpful project overview of projects within the OpenSSF. I took notes to look into incorporating Allstar and to revisit SLSA tooling (it’s been a while).

Projects like OSS-CRS are also great to see, even if I expect the industry to play a much bigger role in this kind of vulnerability scanning and remediation. For my employer’s part, IBM joined Project Glasswing, but more importantly announced a $5B investment in our own Project Lightwell. I’m really proud this, it’s what industry should be doing.

So, overall, how am I feeling?

Unsettled. Scared. AI has the power to be an existential threat, and at the very least it will transform computer-based work over the next decade, and people will lose their livelihood over it. A lot of them. I can’t stress enough how serious this is in the United States where we are seeing support structures being dismantled when they should be built up to prepare for this future. I am deeply concerned about what this means for our society, and my own family.

I’m also excited. Remember how I like technology? I do, I do! I have dozens of projects in my head that I’ve never done because I don’t have that much hobby time. AI-assisted tooling has already helped me start tackling some of that. I had several very fun conversations with folks at the summit around personal projects that ranged from useful to ridiculous that we’re having fun with because we can suddenly cut out six weeks of coding time from the equation and knock out a prototype in a weekend. It’s probably a bad prototype, but maybe it’s functional enough for personal use, and it simply wouldn’t exist otherwise. It’s also an exciting time for non-programmers who can now get computers to do innovative and new things they want them to do by simply speaking to them, a goal which has been worked on at least since Grace Hopper wrote FLOW-MATIC in 1955. AI is removing the barriers that have kept the full potential of computing in the realm of technologists, and that’s a good thing.

At the end of the day, we’re not going back. Even if the recent push-back of building data centers succeeds in a big way and capacity is limited, we’ll write better models and find ways to squeeze more computing power out of reduced resources. Things probably won’t continue to grow exponentially, but AI is here, and I see no benefit in fundamentally resisting it. Let’s keep an eye on privacy and safety though, shall we?

The flight down from San Francisco was a quick regional flight into Burbank, my go-to airport for this conference so I can avoid LAX. And then I spent Wednesday evening getting settled in and putting some finishing touches on my talk based on some feedback I had requested from some community members working on projects I had an interesting in learning about.

Thursday is when the magic began! I spent the morning picking up my badge and immediately seeing several familiar faces. It didn’t take long to meet up long time friends from our time in the Ubuntu community Jorge and Amber, and we all went out to lunch.

Talk-wise on Thursday I found myself attending several AI talks as part of the Kwaai Summit.

So, AI. We are in the middle of an AI revolution in the tech industry and things are moving fast. A year ago a lot of the AI being used in tech was being marketed as helpers for developers. At SCaLE I heard someone suggest that we treat AI like a junior developer. We’re now replacing junior developers. But I had an experience over the holidays where I was in the trenches with code these “AI junior developers” were spitting out, and it needs a lot of guidance. Without that, the code, documentation, and even commit messages can come out nonsensical and solving things in way that is not “clever”, they legitimately don’t make sense when viewed in the correct context. It also took away the thoughtful collaboration that I love of development: How do we solve this? Can you explain what I’m reviewing? Why did you make this decision? When you’re met with a series of shrugs and a finger pointed at the AI, the job of thinking ends up solely on the person reviewing the change, and that means more experienced developers doing the reviews are being buried in AI slop code.

The technology will get better, and I anticipate an absolute decimation of our industry job-wise. I’m not exempt from this. Plus, there are real environmental concerns about power consumption and resources being used to build out all the data centers to implement these AI solutions, and I worry that it will be painful for our society in a way that may not be ethical. But we aren’t going back, that’s not how technology works in our world.

Add in that so much of this space is flush with more money than the world has ever seen, and decisions driven by greed and a horrifying lack of consideration for humanity seem to winning.

So, why did I run off on this terrifying, negative AI rant? I wanted to share what head space I was in when I walked into SCaLE. I’ve used AI tooling, and I’m constantly learning, but I’m deeply worried about it.

Thankfully, there are still good people doing good things in AI and some of those people were speaking at SCaLE.

As I strolled into the Kwaai Summit it was refreshing to be reminded of some of the more optimistic views of AI, and how success doesn’t necessarily have to follow the money. AI can be used in ways that benefit us all. There are tedious tasks and “impossible” problems that are starting to be solved by AI. Can I actually get a good handle on a big chunk of open source projects on GitHub supporting s390x? Possibly! Can we finally cure some of the most dangerous forms of cancer? Maybe! And there are people building communities around things like Beneficial General Intelligence (BGI, a play on AGI, the Artificial General Intelligence that tends to be the holy grail of AI) where things like ethics and sustainability are considered. These are my people. These are the people who built the first online social networks and open source projects. This is the messaging that I found so inspiring when I first got into open source software and what made me so fully devote my life’s work to it. It was nice to be there.

On Friday I attended Guinevere Saenger’s talk on building out developer infrastructures, which brought up a lot of points one might not necessarily think about when doing so. From there I went to Jon “maddog” Hall’s talk on “Open Source In Computer Higher Education – Past, Present and Future” which was definitely a highlight for me. I don’t need to learn how to teach computer science in higher education, but I do love hearing whatever he has to talk about because he has so many wonderful stories. He took us on a tour of this career with an eye toward education, dropping references from everything to the IBM System/360 to learning assembly from difficult text books that he read solo and then went on to teach. He’s a strong proponent for learning topics deeply, and teaching students to learn how to learn so they can thrive in an industry that requires continuous learning. We’re all in agreement there.

That evening I joined a bunch of folks from The Software Freedom Conservancy for dinner and software freedom discussions. It was a lovely evening and I had the pleasure of meeting some new people, including a fellow from Oakland Privacy who told me about the StrayCap Multispace in Hayward that I’ll have to check out some time soon!

I’ve supported the Conservancy for many years, and have known several of their staff for even longer. Need a free software license violation acted upon? This is the group that does that. They get a remarkable amount done with the staff and budget they have, and I’m incredibly grateful for that. Please consider donating.

The keynote from Cindy Cohn, Executive Director of the EFF, on Saturday morning was wonderful. I’ve been a supporter of of the EFF for years, and am closely aligned with most of their views. It was fascinating to hear about her work in this space, and the fundamental protections that she’s worked to help pioneering technologists secure over the years. I vaguely knew that encryption was restricted by the US government in the earliest days of the internet, but I didn’t realize it was classified as munitions which ultimately meant that encryption algorithms couldn’t be shared and collaborated on online. Wow. Could you imagine the internet without encryption? Our world? Cindy, with an army of early free software hackers, argued in federal court in San Francisco and for over a decade beyond that to make sure encryption was freed from this classification. This story was the first of three that she dives into in her new book Privacy’s Defender: My Thirty-Year Fight Against Digital Surveillance which I promptly pre-ordered. Her call to action to us hackers today was to stay engaged in this fight so that we show up for all the future legal battles that have the potential to threaten the future of our world and lives with regard to digital freedom. I had the pleasure of running into her later in the conference to thank her for her talk, and I had the presence of mind to pull out a piece of paper to have her sign so I could put it in my book when it arrives; I’ll have a signed copy, kind of! Then I went to the EFF booth to do my annual contribution.

After the keynote I was able to meet up with Kaitlyn Davis, a new colleague at IBM who joined us from HashiCorp and I just started working with a couple weeks ago. She happens to live in southern California! So I made the case for her to come out to SCALE. She has some really helpful ideas around leveraging AI for open source contribution tracking and so we were able to sit down for about an hour and chat about IBM in general and drill down into some of the problems I’ve been focused on to see where she wants to jump in. It’s not every day that I have the pleasure of working with someone like her, so I’m really eager to see what we come up with together in the coming months. See? I’m not negative on all uses of AI.

From there, it was time for my talk on Open Source in Closed Ecosystems. Originally I was planning on just drawing from my experience in the mainframe world, but after a chat with John Mertic of The Open Mainframe Project I was convinced to draw from a broader pool of expertise and to look into Automotive and Motion Picture industry use cases. I was fortunate that Alison Chaiken of Automotive Grade Linux (AGL) and Emily Olin who has worked on both AGL and the Academy Software Foundation (ASWF) were able to get back to me quickly regarding questions I had about the initiatives. I was also thankful to get time with Nithya Ruff whose expertise in running open source software programs across the industry has been incredibly valuable to my own work, and the broader community through her extensive work in the community of the years, and direct contributions to the TODO Group.

The talk had some rough edges flow-wise, and I’d like to flesh it out with more examples and talk to more people in industries where open source hasn’t taken a firm hold yet to see what barriers they’re encountering in their organizations. But I had some great conversations after my talk and I think it generally went well. Slides from the talk are available here: /presentations/2026/Open_Source_in_Closed_Ecosystems_-_SCALE_23x.pdf (1.3M pdf)

It was nice to run into Dave Neary, whose Open Source in Business series on YouTube got me some clues I need for my talk too. He gave a couple multiarch talks, and though they were focused on ARM64 it was still nice to hear someone talk about multiarch manifests and containers, since I bump into some confusion from community members about them. He gave some nice demos using Argo CD and Argo Rollouts that I’d like to take a closer look at.

Speaking of multiarch, I then enjoyed a talk by Amy Parker whose talk focused on QEMU user mode. I’ve used QEMU on and off over the years, but honestly since I’ve shifted my focus to bare metal testing, I’ve used it a lot less. I don’t have a lot of experience with the user mode emulation that she covered, which made the talk a fascinating dive through binfmt_misc, ld_preload, and chroots to accomplish a lot of interesting work across architectures. She also talked about using FatELF to create universal binaries, which wasn’t even on my radar. So many fun things to dig into!

Saturday evening I had the pleasure of joining Nathan Handler for dinner at a sushi place nearby. I’ve now had my first sake bomb. But just one!

Happy Sunday! The opening keynote was presented by Mark Russinovich of Microsoft, who, poor guy, spent the first 15 minutes of his talk convincing us that in spite of being known for Windows Internals, both he and Microsoft have a lot of Linux credibility. With that taken care of, he dove straight into a great tour of open source security solutions and how they relate to the growing interest in secure supply chains today. I was happy to see the security components of my own talk from the previous day reiterated, but more broadly, I’m glad SCaLE brought someone in to talk about all of this. Open source has made tremendous strides in recent years related to security, but it doesn’t get as much attention as I believe it deserves, both in terms of usage and awareness, and having more people to work on it, and its importance is only increasing.

The expo hall at SCaLE is always a delightful place to walk through, and this year was no exception. They have a wonderful mix of big, paid booth areas for larger companies, and smaller booths for non-profits, so it always brings a great assortment of people. I had a lovely time catching up with my friends from the Ubuntu community. It’s always a pleasure to catch up with Nathan Haines and George Mulak who’ve been quite involved in the Los Angeles computing scene for years. It was nice to get some time to chat with Erich Eickmeyer, lead for Ubuntu Studio, and I was pleased to learn that his wife, Amy Eickmeyer, is a professional educator and actually got the Edubuntu flavor off the ground again back in 2022! I had planned on a DIY lockdown of Ubuntu for our kids this year, but I’ll have to take a look at Edubuntu now.

And the RISC-V booth was on my list too, as I’m always eager to learn the latest (you know me and architectures!). That’s where I met a fellow IBMer who was involved with the Works with RISC-V community which I didn’t even know existed. Cool. I was able to ask about HDMI support on my VisionFive 2 and learn that there should be mainline kernel support soon, and learned that people are saying good things about the latest RISC-V mainboard for the Framework laptop. My kids like to remind me I have a lot of laptops, so I’ve held off on Framework for now, but I’ll have to take a closer look at this one.

I also went to a talk by Brendan O’Leary on From COBOL to Claude: What Hopper Knew (actually, his slides swapped “Claude” for “Cursor” (the AI coding environment). Things in AI move fast). I enjoyed this talk and his premise, given all I’ve said above about the inevitability of AI in our industry. He began by talking about Rear Admiral Grace Hopper’s desire to make “programming” computers a more human-language driven endeavor, and how that began with her FLOW-MATIC and ultimately COBOL, which is still widely used today. His belief is that she’d be happy that anyone today can vibe code their own application, and made the same comparison I tend to do with evolution of coding. AI does have very, very important things that differentiate it from the previous major evolutionary steps of computer programming, but I just don’t believe that things like being nondeterministic are enough to so forcefully push back on it. Most of this talk continued by talking about how software engineering practices that professionals are using will simply need to be adjusted to have a lot more planning and a lot less hands-on coding, and with these research, plan, and implement frameworks in place we’ll be able to trust the results AI comes up with a lot more. I think he’s right.

The conference concluded with a walk down network memory lane with Professor Douglas Comer. I love computer history, so I was familiar with a lot of the general touch points he discussed, but since his focus was on networking there were a few things I’ve missed along the way. He talked about magentic tape mailers, how Endianness caused problem with computers communicating in the early days, and how a technology like TCP/IP or even the client/server model were not obvious. His stories around how phone companies charge for transit and the sorted path to get households connected to internet was really insightful, especially when paired with the observations from Cindy Cohn the day before.

Huge thanks to all the volunteers who makes SCaLE happen, I’m really happy I could make it down this year, and after seeing how many kids where there, I’m going to make plans to at least bring our eldest down for the weekend next year.

So first, thanks to Beth Lynn, Vance Kochenderfer, Susan Rose Dudenhoefer, and the other volunteers who brought the event together this year on a tight deadline. I’m so grateful I thought to include the conference on my quarterly event requests in spite of it not being announced yet!

I’ll also mention that I keep calling it “Ohio LinuxFest” but they rebranded as “OLF Conference” to reflect “Open Libre Free” and their goal to include operating systems beyond Linux, mea culpa!

The event itself was a lot of fun. It was smaller than in years past, as they went with one track. They mentioned at closing that doing it in December is too late in the year, and along with the short runway for the conference likely impacted attendance. Still, if I had to guess I’d say there were a couple hundred people there.

I saw a lot of familiar faces. My friend Scott came out from Pittsburgh, and though we still chat regularly in a group cobbled together from our Ubuntu Pennsylvania days, we hadn’t seen each other in person in years. It was really cool to catch up, and to laugh about kid stories, since we’ve both became parents since we last saw each other. I also got to spend a bunch of time with Amber Graner, who I also got to know very well during our time in the Ubuntu project. We’ve stayed in touch, so we’re still pretty close, but this was the first time in a while that we had more than 20 minutes to catch up. And new people! I got to chat with a student who was attending an open source conference for his first time, and met several folks who have been working in open source for decades. It really was a great mix of folks.

I really enjoyed the opening keynote from Don Vosburg on Passion and Pragmatism. He tugged on a familiar thread in the open source world around the fact that a lot of folks got into open source software “for fun” or the passion of it, but most of us eventually had to get professional jobs that may have tested our fundamental commitment to open source. Or other things that have arisen in our lives that require us to make a choice. I’ve definitely had to walk a line throughout my career, but consider myself quite lucky to have found myself a series of good positions that have allowed me to follow my passion and make a living.

My talk was just after the keynote, and I was very happy that most people stayed! It’s a re-working of a talk I gave last year, but I notably added an architecture and made some adjustments to my slides about software testing. I was amused to learn that my closing keynote back in 2018 was about doing software testing on your open source project, and that this could be seen as an expansion of that. I joked at the beginning that I was very glad everyone listened to me last time, and now that they all have software testing, it was time to add non-x86_64 hardware architectures into that testing matrix. The slides are available here: Will_your_open_source_project_run_on_a_mainframe_Or_a_watch_OLF_2025.pdf (1.2M)

Thanks to Scott for taking a picture during my talk!

Catherine Devlin’s “Graph Data for Heroes II: Rise of the Bot” was an interesting one. A large chunk of it had her scraping web data, and as I was live-posting about it on Mastodon and Bluesky I was speculating about how web scraping is one tech that hasn’t gotten a whole lot better in 25 years, then mused that it was actually a good use for AI/ML technologies. Indeed, that’s where her talk went!

Scattered throughout the conference foyer were a few tables from supporters and sponsors, and I was delighted to see a series of ChromeBooks that had been repurposed to use various Linux distributions. I was delighted to see that Xubuntu made the cut, and when I walked over to check it out I was presented with our shiny new website. Lovely!

In the afternoon I enjoyed seeing Steven Pritchard’s “The Great Open Source Rug-Pull” where he talked about open source software license changes, which have caused a lot of disruption and contention in the open source world these past few years. And although I had heard of Hacker Public Radio before, it wasn’t until murph’s talk on the topic, along with a bunch of great tips, that I got a serious look into what it was and how the episodes are crowd sourced. These folks are doing great work.

Amber Graner concluded the day with the closing keynote “Bless Their Hearts: Open Source, AI, and Southern Survival Skills.” She took us on a personal, funny journey through some of the characters and situations in the open source world. I particularly loved at the end where she shared a list of things she wished people had told her when she started contributing to open source. I’ll be keeping some of these things in mind as I continue working with students who need more than just the basic misconceptions about contributing corrected so they can effectively contribute.

The end of the event crept up quickly! The group hosted a small closing after party in the hotel lobby with pizza and my favorite, cake!

In what is perhaps one of my shortest conference trips, I flew out at 5AM the next morning to get home by midday on Sunday. It left me pretty tired, but it was worth it.

To celebrate, I wanted to bring our success story and opportunity for projects to GitHub Universe this year. I was lucky that it was taking place in San Francisco, so there were no travel costs for me, and doubly lucky that the IBM team sponsoring the booth was willing to have me join them. It was a great experience working with the organizers and my fellow booth staff, we had representation from various parts of IBM so it was easy to direct attendees to someone helpful based on what they were interested in. For my part, I wish I had brought along a bigger sign saying something like “I give free stuff to OSS projects!” so the hobbyist contributors weren’t scared off by the more enterprise nature of IBM. Maybe next time. I was able to have some great conversations though, and could show off the work we’re doing with a screencast of the on-boarding process that I prepared on my tablet.

And I wasn’t the only mainframer there! Folks from Broadcom had a booth where they were showing off their Code4Z products that integrate into a standard VS Code environment.

It was a great event for me to be at to show off mainframe goodies to a distributed tech world that’s less accustomed to them. I was even able to clue in a few IBMers to the business we’re doing over in IBM Z land.

Personally, it was a wonderful event to be at to catch up with folks I haven’t seen in a while from across my tenure in open source.

I think my two biggest takeaways from the conference were 1. Wow, AI. and 2. How different conferences are when the talks aren’t necessarily the centerpiece.

Most of us in tech have a very different immediate relationship with AI than people in the general public. For us it’s less about results from ChatGPT and AI-created images, and more about what AI that knows how can code will do to transform the tech industry and what’s possible. We all knew that basic Python coding tasks would start to be replaced by AI, but we’re actually seeing that in practice now. No longer just autocomplete, we can vibe code a whole application.

One of the keynotes showed the presenter finding an old Bluetooth-enabled Furby in a closet and using an AI coding assistant to update an old open source software library so he could use it in 2025. The story here was that as a silly fun thing, he probably wouldn’t have ever had time to tinker with it, but now it’s easy. I’m not saying anything new here, and I do understand the difference between vibe coding a Furby and writing a production application, but in the near term it clearly will make some of the more mundane tasks easier to pass off to AI. I really would like one to automatically keep up on Node.js dependencies for me, it’s the most dreadfully tedious task.

All of this is to say that at the conferences I attended this year, I saw a real maturity turning point in the AIs-that-can-code realm. And GitHub is a big player here because of how integrated their code tooling already is in so many organizations, and throughout open source software communities.

Phew.

As for my second point, the talks not being the centerpiece. I’d say there’s still the spine of what holds the conference together, but there were fascinating experiences scattered throughout the event, both from vendors and from GitHub. The vendor booths was woven throughout all the buildings, and there was often a seamless transition between GitHub activities and vendors. One moment you’re designing your own Octocat sticker, and the next you’re getting a coffee while chatting at the IBM booth.

I enjoyed the building activities, our options were a GitHub light or a GitHub Copilot Lego model, and I went for the Lego. It was a nice little relaxing break from conference chaos.

The venue of Fort Mason was also lovely, and they had regular shuttles from downtown San Francisco which made the hurdle of transportation a more surmountable one. Both mornings I had an easy journey on BART to a shuttle that left from Embarcadero station. Once there, the gorgeous San Francisco weather we enjoyed offered the perfect backdrop. If I needed some air, I could walk down a pier and get a glimpse of the Golden Gate Bridge. They also cleverly placed a giant GitHub sign so that you could see beautiful Alcatraz Island through it.

They served good food and we had lots of places to sit and enjoy it. And after one tour through the main keynote building where I played a game to get a juice, I had no problem finding a shady spot to sit down and do a half hour of urgent work that I had to knock out.

The electronic badges were also a lot of fun. You had the option of getting one during registration, and they were little devices powered by an ARM SBC. As “hackable” badges you could play with them as-is, but also make some changes to the code included on them to do things like show your GitHub stats and they had a whole area with laptops that would allow you to do this (good thing, I can’t plug anything USB into my work laptop!). Once mounted on your device, they have a whole website of activities and other tools you can add to them. Cool. The scavenger hunt was also fun. I found they held a charge for about 10 hours, depending on use, so while I charged my overnight and took it off the charger at 7AM to head to the city, it barely made it to 5PM. I brought my digital badge home and it’s sitting here by my desk, maybe I’ll vibe code some new stuff for it, haha!

I’m certain that having such a fun and engaging space is all designed for encouraging brand loyalty. People have a great experience at these events in addition to learning things. I have always had mixed feelings about GitHub, and I still do, but some of the high points are definitely around usability, in spite of being built around Git, a tool that’s notoriously difficult to use! And usability includes feeling comfortable, which GitHub Universe did beautifully this year.

For my part, I repeated the IBM LinuxONE AI Arcade that we did at the Red Hat Summit back in the spring, with a few adjustments. Our footprint was smaller (2 laptops instead of 4) and I made some tweaks. The biggest change was that during the sandbox (expo) opening Block Party on Monday evening I did a “Doom takeover” of the whole setup and let people play Freedoom, VNC-streamed directly from one of our IBM LinuxONE virtual machines. It was a huge hit. So much so that for the rest of the week we had folks dropping by the booth to ask if I still had it up, and a few commands later, I did! Using Windows laptops for all of this was certainly a new experience, so I was grateful that I thought to test it on a Windows 11 laptop we keep around for such things before the event. Did you know stock PowerShell on Windows 11 comes with SSH? Cool. But overall, aside from being fun to answer the question of “but does it run Doom?” with a demonstration, we all know that piping something over VNC isn’t that technically challenging, it’s the amusement and feeling it grants, and the fact that it’s coming from IBM, not some hip new startup where you may be more inclined expect it.

What else is cool? Quantum computers. They had an 80% scale model near the entrance to the Sandbox this year and it got near constant attention. It took until Wednesday until I was able to find a quiet moment to get a good picture with it. I’ve been reading about quantum computers since I first picked up an article about them in Discover Magazine back in the 1990s, so seeing them come together at IBM and be actively deployed to facilities around the world has been a thrilling experience.

And I know you’ll say the AI stuff currently taking over everything in the world is overblown, and it is, but there are some real use cases for it. IBM clients across industry and research have already come up with dozens of uses for AI/ML, just been waiting for the tech to catch up. As a result, IBM research has invested heavily for YEARS in AI hardware, which first came to market in an AI accelerator in the IBM Telum chip inside the IBM z16 and LinuxONE 4 a few years ago.

This year the Telum II came out in the z17 and LinuxONE Emperor 5, but the additional IBM Spyre AI Accelerator card using the same technology also hit the market. This SOC with 32 individual accelerator cores has definitely been the belle of the ball, with clients asking all week when they can get their hands on one (thankfully, it was swiftly announced that it would go Generally Available at the end of October). Theft jokes abounded once people learned that we had a non-working prototype inside of the IBM z17 plexiglass at our booth, and when I went to visit the new IBM Power 11 server at the Power booth I found they had a prototype you could HOLD at their booth! That’s where I got my photo with it. You see, these work in the Power systems as well.

Back at the IBM booth I got to hold a Telum II dual-chip module (DCM) which is always a delight. They also had display versions of the chips from the z15, z16 (Telum), and the new z16 (Telum II) which was neat to see side by side. I need to remind my friends who I spoke with a few months back about assembling a “petting zoo” of decommissioned hardware to bring to events, I love holding these things. Lots of nerdy technologists do, and when else would we get the chance for something like a mainframe component? Even if you have a mainframe, you really shouldn’t go poking around inside it.

Ferrari is also cool. IBM worked with Scuderia Ferrari on an AI-powered app (and more!), and if the keynote interview was any indication, both organizations are quite excited about it. Plus, we got to have what I’ve been told is one of the F1 cars from last year right there in the sandbox. It was beautiful. I bought a hat.

Also also cool? Lego. You know I love Lego, but a lot of other adults are waking up to the passion and it’s definitely boiling over in the tech industry with a lot of folks being more open about their collections in recent years. This has definitely leaked out into tech conferences I’ve been at these past few years. Booths offering custom minifig building, others doing custom Lego sets for attendees. It was super cute to see a Lego model of the Sandbox where the team there was collecting feedback of the event, both verbally and by having people vote with Lego.

And of course, when the IBM z16 came out we build a full-size model, which I wrote about here back in 2023. How do we follow that? I was absolutely delighted that this time around they focused on the IBM Telum II processor, by making a huge scaled-up model of it. Hanging next to the plexi, this model was based off of how the actual processor looks, but with whimsical details like frogs, robots, and airplanes to amusingly demonstrate various parts. I plan on writing more about this later, and my partner in writing this may have some surprises in store for something you can do at home too. Stay tuned!

Perhaps my favorite part of the event, and indeed a highlight of my year, was being invited to join PJ Catalano and Camillo Sassano to unbox a mainframe live on the expo hall floor. Normally such an unboxing is done quietly before the event so that people can see it in the final form, but PJ’s idea of a live unboxing built excitement. We had pre-event teasers, there were cool lights pointed at the crate during the opening party with signs to come back the next day, and it all resulted in well over 150 people trying to secure a great spot to watch it being unboxed.

It was my first time participating in uncrating a mainframe, so Camillo walked me through it live right there as PJ explained each step and why each component of the crate was in place. It was fascinating to see if all come apart and learn about how purpose-built the whole thing was. The crate door is not just a door, it’s the ramp! The mini flip up section on the top was so it could be built to fit inside a standard truck. And so much more. Once we gently rolled it out of the crate, we got it on the carpet and started putting the doors on. The doors can be put on either side, so on one side we put an IBM Z door, and on the other we put the LinuxONE door. Choose your mainframe! Or get a photo with both!

I hear the events team is putting together a full video of the unboxing from all the cameras they set up, but for now I was happy to be the first one to get to hug it for Hug Your Mainframe Day. Naturally, I hugged the LinuxONE side. After me, the whole rest of the event there was a steady stream of people getting their pictures with it, and hugging it. The IBM shop on-site even had t-shirts celebrating hugging mainframes, which was super fun (of course I got one).

At the end of the event, we didn’t do a formal packing up, but thankfully enough folks were still around to get the job done.

Throughout the event there were also a lot of pure fun things. A huge rainbow slide that Mae and I partook in a slide down. Lots of video games, including the ability to play Mario Kart on the keynote stage screen when it wasn’t otherwise engaged. There were spots for getting photos, one for silly photos and another across the expo hall for headshots. For an event with long days and so much serious content literally spread throughout the expo hall in the form of tech talks and sessions, it was nice that we had the ability to unwind and recharge before going on to the next thing. The event also featured an evening at Universal Islands of Adventure, where we really got to unwind! I was able to ride on Hagrid’s Magical Creatures Motorbike Adventure and the unforgettable Jurassic World VelociCoaster. I spent a good chunk of my late 20s and early 30s unable to go on such rides, which I also now realize was the height of when I suffered from migraines as an adult. Huh. Something was going on in my brain for a good decade there, but it seems like I’m in a better place now. While these rides are still thrilling and trigger a tinge motion sickness for me, it’s no more than the normal amount now, and the fun balances it out.

At the beginning of this post I mentioned that IBM has been doing cool stuff since the company began, which leads me to my last notable mention: the booth from the IBM Corporate Archives. I’m a fan of history, including the history of computing, so I have bias here, but I honestly believe in telling the continuous story of innovation at IBM. The booth featured a couple working vintage machines, including one that was hooked up to a large dot matrix printer and attendees could print out short messages on.

They also had a glass case display that changed daily featuring various pamphlets and memorabilia from various initiatives and notable releases over the years. The moon landing! The launch if the IBM System/360! All kinds of cool stuff. And what I considered the star of the exhibit and which welcomed attendees as they walked to the booth, an IBM System/360 Model 40 Operator’s Console. Love it.

I have really enjoyed seeing how this conference has evolved over the past three years to be bigger and better each year, and truly more fun and geeky. It’s a lot of work, but I can’t wait to see what they have and I get to participate in next year.

The Castro Valley Fall Festival took place on September 6th and 7th. The first day the boys got to visit a petting zoo, but the day was cut a bit short by a kiddo stomach ache.

We went back for day two so we could walk through the whole festival, and the boys enjoyed going on a bungee bouncing thing.

Last week I was able to sneak out for an evening to go see Hamilton at our local theater. The 10th anniversary release was really fun to see, even if I didn’t quite anticipate spending 3 hours on it. It included an introduction with interviews from the original cast reflecting on the experience and anniversary, and also included a 10 minute intermission. It all took me back to where I was 10 years ago, and just how much I loved the whole Hamilton experience as I fell in love with the soundtrack, and finally saw the show live in San Francisco.

The boys have continued swim classes, which are going well but they changed pools on us recently, which means we don’t have the fun opportunity to see an Amtrak train zooming through on a perfectly timed journey to the pool now. Fortunately, on our last Sunday at the last pool we got to see it, and the pool they moved us to is actually a lot nicer and isn’t much further away.

Day to day there’s been a lot of playing with our new cat, Zara, and doing little tasks around the house. The other day Adam helped me vacuum out the van so we could install a new all-weather mat in the back. MJ and I have been going through some paperwork to continue our organization project and clear out some of our storage areas.

I’ve also been trying, unsuccessfully, to resurrect one of our old servers. We have a couple small systems that we used for backups and media when we lived in San Francisco, but over time the raid arrays on those spinning disks died and the systems failed. I figured that bringing them back up would just be a matter of replacing the disks and doing some reconfiguration, but it’s been dreadful. VGA output appeared to have failed on one of the mother boards, so I moved everything over to the other system and then I was getting inconsistent booting even after I sorted out UEFI. I finally got it booted and the RAID5 array built, rebooted it, and VGA this system isn’t working, even in POST. Argh. Why? I guess it’s my fault trying to bring back old x86 systems. Even if it had worked, it wouldn’t be satisfying like getting my RISC-V SBC going a few months ago. Right now it’s just a disappointing time sink. I might try a few more things, but I’m close to giving up and starting again with new hardware and a more modern disk configuration.

And while I’m talking about old hardware, I hauled out my never-used Mycroft Mark I device recently. That’s been causing me a lot of headaches too, but at least there’s more novelty to it. I’ll write up a full blog post about it if I ever do get it running with something interesting. Right now I might be facing some hardware issues AND a system that’s simply too old to run some of the home assistant software that lives in the forks designed for it. I guess I’ll see how it goes. Computers, man.

I left off about a year ago when I succeeded in getting an older version of Debian on it, but attempts to get the tooling to install a more broadly supported version of U-Boot to the SPI flash were unsuccessful. Then I got pulled away to other things, effectively just bringing my VF2 around to events as a prop for my multiarch talks – which it did beautifully! I even had one conference attendee buy one to play with while sitting in the audience of my talk. Cool.

I was delighted to learn how much progress had been made since I last looked. Canonical has published more formalized documentation: Install Ubuntu on the StarFive VisionFive 2 in the place of what had been a rather cluttered wiki page. So I got all hooked up and began my latest attempt.

My first step was to grab the pre-installed server image. I got that installed, but struggled a little with persistence once I unplugged the USB UART adapter and rebooted. I then decided just to move forward with the Install U-Boot to the SPI flash instructions. I struggled a bit here for two reasons:

1. The documentation today leads off with having you download the livecd, but you actually want the pre-installed server image to flash U-Boot, the livecd step doesn’t come until later. Admittedly, the instructions do say this, but I wasn’t reading carefully enough and was more focused on the steps.
2. I couldn’t get the 24.10 pre-installed image to work for flashing U-Boot, but once I went back to the 24.04 pre-installed image it worked.

And then I had to fly across the country. We’re spending a couple weeks around spring break here at our vacation house in Philadelphia, but the good thing about SBCs is that they’re incredibly portable and I just tossed my gear into my backpack and brought it along.

Thanks to Emil Renner Berthing (esmil) on the Ubuntu Matrix server for providing me with enough guidance to figure out where I had gone wrong above, and got me on my way just a few days after we arrived in Philly.

With the newer U-Boot installed, I was able to use the Ubuntu 24.04 livecd image on a micro SD Card to install Ubuntu 24.04 on an NVMe drive! That’s another new change since I last looked at installation, using my little NVMe drive as a target was a lot simpler than it would have been a year ago. In fact, it was rather anticlimactic, hah!

And with that, I was fully logged in to my new system.

elizabeth@r2kt:~$ cat /proc/cpuinfo
processor : 0
hart : 2
isa : rv64imafdc_zicntr_zicsr_zifencei_zihpm_zba_zbb
mmu : sv39
uarch : sifive,u74-mc
mvendorid : 0x489
marchid : 0x8000000000000007
mimpid : 0x4210427
hart isa : rv64imafdc_zicntr_zicsr_zifencei_zihpm_zba_zbb

It has 4 cores, so here’s the full output: vf2-cpus.txt

What will I do with this little single board computer? I don’t know yet. I joked with my husband that I’d “install Debian on it and forget about it like everything else” but I really would like to get past that. I have my little multiarch demo CI project in the wings, and I’ll probably loop it into that.

Since we were in Philly, I had a look over at my long-neglected Raspberry Pi 1B that I have here. When we first moved in, I used it as an ssh tunnel to get to this network from California. It was great for that! But now we have a more sophisticated network setup between the houses with a VLAN that connects them, so the ssh tunnel is unnecessary. In fact, my poor Raspberry Pi fell off the WiFi network when we switched to 802.1X just over a year ago and I never got around to getting it back on the network. I connected it to a keyboard and monitor and started some investigation. Honestly, I’m surprised the little guy was still running, but it’s doing fine!

And it had been chugging along running Rasbian based on Debian 9. Well, that’s worth an upgrade. But not just an upgrade, I didn’t want to stress the device and SD card, so I figured flashing it with the latest version of Raspberry Pi OS was the right way to go. It turns out, it’s been a long time since I’ve done a Raspberry Pi install.

I grabbed the Raspberry Pi Imager and went on my way. It’s really nice. I went with the Raspberry Pi OS Lite install since it’s the RP1, I didn’t want a GUI. The imager asked the usual installation questions, loaded up my SSH key, and I was ready to load it up in my Pi.

The only thing I need to finish sorting out is networking. The old USB WiFi adapter I have it in doesn’t initialize until after it’s booted up, so wpa_supplicant on boot can’t negotiate with the access point. I’ll have to play around with it. And what will I use this for once I do, now that it’s not an SSH tunnel? I’m not sure yet.

I realize this blog post isn’t very deep or technical, but I guess that’s the point. We’ve come a long way in recent years in support for non-x86 architectures, so installation has gotten a lot easier across several of them. If you’re new to playing around with architectures, I’d say it’s a really good time to start. You can hit the ground running with some wins, and then play around as you go with various things you want to help get working. It’s a lot of fun, and the years I spent playing around with Debian on Sparc back in the day definitely laid the groundwork for the job I have at IBM working on mainframes. You never know where a bit of technical curiosity will get you.

Monday morning kicked off by going over to the Secure Open Source Software (SOSS) Community Day for the morning. I particularly enjoyed the keynote from Kate Stewart about the state of Software Bill of Materials (SBOMs). I remember when discussion of SBOMs in the open source world started picking up, also with Kate being a spokesperson for them, and at the time reflected upon how useful they’d be if they ever caught on. It feels like the increased focus on security due to some high profile vulnerabilities is what accelerated the interest and need for them and having a full keynote devoted to them at a security event seems to have confirmed my suspicions. It was great to get an overview of the types of SBOMs that exist (binary vs. source, where they are in phase of development/deployment), but also to learn how many governments have started mandating SBOMs to track what software they’re using. They’ve really hit their stride, and also launched SPDX 3.0, the latest in their iterations of “an open standard capable of representing systems with software components in as SBOMs.”

Monday afternoon took me over to CHAOSScon. I learned from their latest Community Health Analytics in Open Source Software (CHAOSS) project overview that they have a OSPO Metrics Working Group, which may be right up my alley these days. CHAOSS is one of those projects that I remember being launched and always wanted to be involved with, but never managed to make time for. I am concerned that’s still the case, but it was nice to check in with the community so I can more effectively determine whether it’s something I can finally carve out time for. We did an interactive workshop where we shared some thoughts and ideas, and then concluded with updates from a few of their projects, including the announcement of GrimoireLab 1.0 and an update from Augur.

I followed my friends (old and new!) to a CHOASScon after event at a nearby bar where I got to chat with a woman I met whose company was exploring their open source stack and thinking about building out an OSPO. It was nice having that conversation, as well as catching up with a bunch of folks.

Tuesday moved us beyond Community Day and officially kicked off the Open Source Summit, where we were welcomed to a series of keynotes that jumped right in with the topic of AI and work that’s going into enterprise-readiness with the launch of the Open Platform for Enterprise AI (OPEA). It was also nice to see quantum readiness mentioned. A keynote on Valkey, a Redis successor, also caught my attention, as there was a recent proposal to drop s390x support from it (thankfully a quick chat at their booth hopefully resolved this, hooray for conferences!).

Beyond the keynotes, it was generally a good day for talks. Kara Sowles of GitHub gave a great talk on open source funding (hint: there’s not nearly enough of it) and I went to a talk by my former colleague, Javier Perez, on some trends in open source software gathered from a survey that was concluded last year. Joe Winchester delighted with a talk on “Software in Space: Lessons Every Developer Can Learn From” where he took several examples of failures (or near failures) in space missions and drew parallels as to what software developers could learn. I think we all geeked out a bit over space science in that one.

Then for lunch I met up with Maemalynn Meanor of The Open Mainframe Project so I’d have a pal at the Women and Non-Binary Lunch, which is always a pleasure to attend.

Tuesday evening I made it over to a Open Source Summit [unofficial] AI Meetup After Hours which had a series of short talks from folks in the community to present their work, and what ultimately led to discussing ways they could collaborate, which was great to see. One of the things that came up was that even within the Linux Foundation community there is duplication of effort happening as everyone sees the same problems inside their own projects, meetups like this help break down those barriers.

Wednesday morning keynotes began with a “fireside chat” with Linus Torvalds, where he notably (for me) talked about RISC-V and concerns that they’d duplicate mistakes of past architectures when it came to software. When I stopped by the RISC-V booth later in the day it was clear that hit a nerve, and inspired some action in that community to make sure then don’t. He also seems to have come to the logical conclusion that the AI wave is not really worth the hype, but there is something there that we’d be wise to keep up with. Speaking of which, another keynote touched upon the rise of code being generated by AI tooling, and the need for securing our communities against manipulation that can happen to the source code bases that the AI is drawing from, underlining again that we need to bring trust and validation directly to open source projects.

After lunch I gave my talk on “How Our Mainframe-Focused Working Group Solved Our Linux Distribution Maintainer Isolation Problem” where, just like SCALE, I found myself with a small but deeply engaged audience. I also learned that while a handful of people in the room where focused on the topic, most of the questions were specifically related to mainframes, which I was also happy to answer! It was nice validation that there is appetite for the topic at events, and maybe I’ll re-focus on the technology at the next event I propose for, rather than going for a more social talk. Still, I was very happy I gave it, and some great contacts seem to have been made both for myself and for some audience members who got chatting afterwards.

Thursday was when the realization that I was on day eight of travel finally hit me and I started feeling a bit tired and I switched to mostly spending time in the expo hall meeting with people rather than trying to focus on sessions. Throughout my expo hall adventures I got to meet up with some friends from the Ubuntu community, a contact who I’d only spoken with online from OpenPOWER, and dozens of people I’ve known through various times in my career, who I’ve always been able to geek out with, regardless of my current focus – including mainframes!

Still, I caught the keynotes which were, once again, a bit AI-heavy. It’s important though, I know the tech industry is saturated with AI at the moment, but one of the things the Linux Foundation has the opportunity to be a steward of is the responsible development and use of it, so I’m grateful to see that coming together. Thursday was also delightfully broken up by the ability to pet some animals. I chose the rabbits.

The Open Source Summit is the largest open source events I attend, so I was really grateful to be back after the pandemic hiatus. I had a plan for the week, and accomplished most of what I planned on, but was constantly surprised at other opportunities that sprung up when I met with people. As valuable as the regional conferences are (and they ARE), this one is definitely the best conference of the year for core open source networking.

But first, I made a stop at the IBM office in Austin where I met up with my colleagues Daniel and Chris. I met Daniel at a taco truck where I had a much-needed post-flight lunch, and then he gave me a tour of the office. I even managed to find a random, roaming IBM Selectric II typewriter!

Then I got to enjoy happy hour out with several other folks from the office before returning back to my hotel for the night.

The first day of the conference I mostly spent meeting people and in the expo hall chatting with folks from Rocky Linux and AlmaLinux. They both have builds for s390x, so it was really nice to finally meet the folks I’ve worked with online, and talk with them in person about their current utilization and changes in needs. And that evening I was able to grab dinner and ice cream with my contact at Rocky Linux.

The second day was the one that was filled with talks. The event kicked off with a keynote from Anita Zhang about her career, and how unexpected choices at various stages led to the success she’s found today. From there I went directly to a talk by Matt Mullins of the Connections Museum Seattle titled “The oldest Linux peripheral” where he talked about a panel switch from 1923 that’s now hooked up to a Linux box to manage operations. It was a really cool talk, and looks to be a fascinating museum with a lot of old telecommunications equipment. The hours they’re open don’t line up with my upcoming visit to Seattle, but maybe next time, I know it’s something MJ would love to see.

From there I went to a talk from Paul Novarese on “The Legacy of Log4Shell and the Future of DevSecOps” where he gave a bit of a tour of the open source security landscape, and shared statistics around the exponentially growing number of open source projects and versions available, along with the corresponding rise in CVE assignments and NIST Vulnerability Database analysis work. Some of his observations centered around the fact that these procedures were developed at a time when the open source ecosystem was a lot smaller, and the dependency chain was somewhat less abstracted (or at least, less complicated). He talked about SBOMs (Software Bill of Materials) that can help organizations get a handle on the supply chain, but analysis and fixes also have to keep up so you have data to search for in that SBOM as you look for vulnerable software.

I took lunch a little early so I could prepare for my talk, and ended up at Terry Black’s BBQ across the street from the venue.

My talk on “Why (and how) would you run Linux on the Mainframe?” went well! It was well-attended and I think about half the attendees had a passing familiarity with mainframes, but a lot of the audience was new to the topic, which is about what I’d expect at a Linux event these days. People had great questions and it was really fun to geek out about it for the rest of the event, even at the after party for the conference the questions and discussions continued over drinks.

From there I went to Kyle J. Davis’ talk “Container Optimized Linux: The best idea you’re probably not using.” He had worked with Bottlerocket, but Flatcar and Talos are also in the host container OS space, and while I vaguely knew they existed, this was the first time I sat down and dedicated a few minutes to hear someone talk about them. The slim model they have for these distributions makes a lot of sense, since you really do only need a tiny, secure, environment to actually run the containers on, and everything can be externally orchestrated. While not directly applicable to me right now (IBM has done a lot of work on our own secure container environments), it is something I’ll keep in mind if the opportunity arises.

The final talk I attended before lightning talks and closing was around the Fedora work with Asahi Linux to bring it to the ARM-based Apple macs. I don’t have a great interest in this hardware specifically, but I always enjoy hearing about other architecture porting work that’s happening, and it was interesting to see the challenges that they’re presented with, along with progress and solutions.

For dinner before the after party I ended up eating with folks I knew from the OpenStack, and broadly, the Fedora community, before we all walked over to the Gibson Street Bar. I was feeling a little tired at this point, but I ended up staying clear through until 10PM. I then took a short detour over to a mailbox to send off a post card for the boys before retiring to my hotel.

Today is Sunday and I’m off on my next adventure: Seattle for the Open Source Summit!