• Archives

  • Categories:

  • Other profiles

Glass and monorail in Seattle

While I was in Seattle for the Open Source Summit, I also took a long lunch on day zero of the conference to take the monorail over to the Space Needle. I’ve been on the monorail several times, but I love it and I kind of feel like a trip to Seattle is incomplete without a ride or two.

When I was in Seattle in 2018 I went up to the top of the Space Needle with my friend Walt, which I wrote about in MST3K and the Space Needle. With that done, I didn’t feel the need to do it again, especially on a cloudy day, so instead I went over to the Chihuly Garden and Glass exhibit.

I knew of Chihuly from his glass flowers in The Bellagio, so it was lovely to see an entire exhibit devoted to his work, and it was breathtaking.

As you walk through the galleries you’re presented with a series of themes, and I admit being quite impressed by the sea creatures, from octopuses to eels.

But the big scenes he created were also quite stunning, including this one, and others with boats, fans, and chandeliers.

The glass house was also quite stunning, and as I was taking photos I realized I was standing under the Space Needle. Neat!

When I stepped outside I saw a vintage style Airstream which had been turned into a glass blowing studio. The crew was warming up when I arrived, but the glass blowing demonstration began swiftly and it was a lot of fun to watch. That’s where I also learned that the Space Needle gift shop was the recipient of the glass they blow in these demonstrations, and sales go to benefit local artists.

Halfway through the demonstration it started raining, so I was grateful to be under a tent outdoors and that it calmed down to a drizzle by the time the demonstration concluded and it was time for me to explore the outdoor gardens. The gardens are a literal garden with trees, flowers, and shrubs, accented with glass structures, which was quite lovely.

I was able to grab a quick lunch, and while I was walking around to find a place to eat I realized how much our boys would love a visit to Seattle. There’s the light rail to bring us in from the airport, the monorail, and then several spots around the Space Needle that the kids would love, including a science center, a children’s museum, and a really fun looking playground. It’s now high on my list of places to visit some summer with them.

With that thought tucked away I headed back to the convention center on the monorail.

And I did end up stopping by the Space Needle gift shop to take a piece of this journey home with me. Thankfully, they do shipping and it’s quite reasonable, so my new glass vase followed me home after a week or so in transit.

The rest of the week was spent at the conference, but I decided to take it easy in the evenings. I did a couple solo dinners at local sushi bars, one of which featured a “sushi donut” and the other that had “sushi burritos” both of which were fun and delicious. The big social for the conference was held at a bar and a bowling alley and I decided to skip it because I was feeling a little tired and was worried that an event in that environment would be a bit too loud and boisterous than what I was hoping for. I really prefer conference parties that are at interesting places that give you an option of things to do, ones at museums or aquariums have topped my lists. We can socialize like we would at a bar, but also find quiet spaces, or mingle and bond over exhibits if I’m feeling shy and don’t have a designated conference buddy to hang out with. And if I strike out at socializing, hey, I saw some cool exhibits at a new museum and it was a lovely night!

I’m glad I got to do a little bit of tourist stuff on this trip, but I’m also grateful to be home. Work trips are energizing for my soul and professionally inspiring, but as a parent now I do miss my family a lot and wished I had MJ with me when I was at the Chihuly exhibit. I also have a lot more house chaos to manage, so it’s good to be home to get back on top of things.

Open Source Summit 2024

My journey to the Open Source Summit North America came on the tail of the Texas Linux Fest, so I flew to Seattle from Austin on Sunday afternoon. A quick ride on light rail put me in downtown Seattle where a short walk got me settled in to my hotel that I’d call home base for the next few days.

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.

5 years at IBM

On April 30th 2019 I had my first day at IBM. Five years ago!

I began my job on the road, as would characterize much of 2019, where I met my new boss at IBM TechU, which I wrote about here: IBM TechU 2019 in Atlanta.

It’s with IBM that I found a new way to expand my career by developing a vast network of internal contacts. Prior to this, I’d been quite outward-facing, from getting involved with the Debian and Ubuntu communities at my first Linux Systems Administration job, or giving dozens of talks while I worked on the OpenStack Infrastructure team for HPE. My first foray into developer advocacy at the startup in San Francisco only managed to scratch the surface of internal network development as I brought requests from developers in, and then at IBM I had a gigantic wrench thrown in my plans to continue in the path of developer advocacy: a global pandemic. Less than 11 months into my time with IBM all travel was canceled and all of our work went online.

At first I tried to do the same thing as usual and hope it ended quickly, but I quickly found myself in a position of having to re-write my role to continue being effective. I ended up increasing my involvement with open source software communities who were developing for Linux on IBM Z (and LinuxONE) and I started developing metrics to track our progress. This ultimately led to the to launch a federated Open Source Program Office (OSPO) for IBM Z and LinuxONE. This OSPO would still refer to IBM global resources for policy and procedure, but gave me a virtual doorway for folks internally and externally to ask questions and get guidance. My internal network at IBM grew rapidly as I laid the groundwork for this OSPO, and even more now that it’s been open for a year.

It’s been quite the journey, and becoming the Global Head of this OSPO has been one of the most rewarding experiences of my career.

First, I get to work closely with open source software communities, which is my true passion. Second, I can directly connect that work to real impact for organizations who are using the platform. Third, I am constantly learning, both technically and through growth in this leadership role. And finally, I’m working with an amazing team with a great manager.

I fully believe that having five strong years at IBM are directly related to having the same supportive boss during my whole time. She has also brought together a team of remarkable, smart, and kind people who I love working with. This is no small feat! And if there’s one thing I’ve learned through my journey in tech, it’s that the people you work with make all the difference. You could be working on a technology you believe in and love, but if you don’t have a good team, your chance of success takes a nosedive. Find your people.

In spite of the progress I’ve been able to make during a global crisis, it’s been amazing to get to see people again as I’ve been able to resume some traveling. 2023 and 2024 have offered several opportunities to meet with my colleagues from around the world and firm up those professional relationships that I treasure so much.

Many thanks to everyone who has been with me at various parts of this journey, and let’s see what the next five years brings!

Texas Linux Fest 2024

The last Texas Linux Fest I attended was all the way back in 2014, which means it had been a full 10 years since I’d been. I was supposed to speak at the event in 2020, but no one spoke in 2020, so I was really happy to finally, finally be back.

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!

Spring break 2024 in Philly

For spring break (and an extra week) we decided to head out to Philadelphia to visit with the family, and have me do a couple side trips for Poughkeepsie and CPOSC. Unfortunately, for the first week a stomach bug swept through our house. First, Adam was sick for 24 hours. Two days later I came down with it. Two days after that it got Aaron. It meant that we kept believing we were in the clear and then being surprised by another one of us falling ill, and delayed any visits with family. Boo.

Thankfully we were clear by week two, and finally got to see people! Irina and little Sammy came over several evenings, and in spite of some squabbles between our pair of three year olds, it was really nice to just have chill family time at home.

I also decided I wanted to organize the toys a bit better, so one evening Adam helped me assemble a small, metal shelving unit.

Along with a new basket we picked up at Ross for their stuffed animals, the play area of the living room is looking a bit less chaotic now.

We got to hit all our favorite restaurants in the area and visit with our friends Danita and David before they left on their move to Portugal. Unfortunately the weather didn’t cooperate, and we had a bunch of rainy days, and it ended up being quite chilly out. Still, they are my little California boys and they long for the outdoors, so when it wasn’t raining we put on jackets and rode bikes.

The solar eclipse was on Monday, and so was our flight home. It was only partial for Philadelphia, so I didn’t feel that bad about being in the airport when it happened, and it was still a cool experience. It got a little dark outside, and I think it made our flight delayed a little, but that gave Aaron and Adam a little time to check out the cockpit of our plane.

I was only home for a couple of chaotic days before my next trip. I wish I could have planned it better, since Aaron started preschool the same morning I left, so I was scrambling to get everything ready for him. It worked out OK though, and we all made it to our respective places on Thursday. Unfortunately we were also hit with some unfortunate news right before I left, so MJ will need to book some travel very soon, which we’re hoping won’t overlap with my own travels this week.

Celebrating 60 years of mainframe in Poughkeepsie

On April 7, 1964 the IBM System 360 was launched, with much fanfare from (and risk to) IBM. I’ve recently been reading the biography on Tom Watson Jr. (The Greatest Capitalist Who Ever Lived) and it was fascinating to read about what led up to this launch, specifically that even 10 years prior to it, the company wasn’t certain that computers were the direction they’d go in. Mechanical tabulators were doing well! But it didn’t take long for computers to take off once organizations were introduced to the speed increases they offered. The System 360 was quite the gamble though. Massive investment in research, and it made the computers that came before it immediately undesirable due to their lack of flexibilty and inability to move into the future. Indeed, the 360 offered the opposite: a legacy that has now stretched into 60 years. Almost everything has changed about computing since 1964, but hints of the architecture built then are still present if you know where to look for them. In some cases, a program written for a 360 could even be tweaked to run on an IBM z16 that rolled off the assembly line today.

In order to celebrate hitting the milestone of 60 years since the release, IBM hosted internal events around the world. I happened to be in Philadelphia during the celebration day on Thursday, April 4th, and decided to make the trek up to the place where much of the research and development, and ultimately the launch, happened back then: Poughkeepsie, NY. I’d been to the office once before, back in 2019, but I was definitely overdue for another visit to the IBM mainframe homeland. This was a perfect opportunity.

I took an Amtrak up from Trenton, through New York City where I was treated to visiting the beautiful new Moynihan Train Hall at Penn Station.

From there I enjoyed the second leg of my journey that took me straight to Poughkeepsie, where I was met by the social media famous Pasquale “PJ” Catalano, who brought me to the office and introduced me to folks who worked on the test floor. Then I got to visit the test floor itself! He posts about it frequently on social media, what feels like a rare and remarkable glimpse inside an IBM facility, so I had a passing familiarity with various locations, but an in-person visit is something else entirely. 200+ mainframes humming away in various states of testing, it was like nowhere I’ve ever been!

It’s also a lovely datacenter. It’s obviously an active, used, test floor, but it’s well-organized and tidy, clearly the team has a level of discipline that many production data centers would envy. I think part of this comes from the culture at IBM in general, but I’m sure some of it is also hard-won from experience, if you fail to label something or are careless about routing, it will come back to haunt you, and waste a lot of time in the future.

I got to hold a memory chip and a heatsink for an IBM Telum for the first time!

Plus an actual dual-chip module holding a couple Telum chips (I had previously held just a Telum in a case back at TechXchange in September).

I got to check out a rack-mount z16 for the first time.

And to my delight I finally got to see the beautiful IBM LinuxONE doors!

Visiting the mainframes of today felt to be a truly fitting way to honor the 60 year legacy of the IBM System 360, but after getting to see some other mainframe goodies while PJ got some work done, we made our way to the cafeteria for the real party. The IBM Corporate Archives had put together a whole hallway of displays!

They even graciously honored PJ’s request to open up the IBM System 360 they had on display and let us get some pictures “inside” it. Bliss!

Let me tell you, I had a wonderful time geeking out with these folks. I’ve always loved history, and with my work in this space I’ve developed a true appreciation for how legendary IBM is, and this is the heart of it. I also fear I talked the ear off of one woman from the archives who had a typewriter skirt on, as I shared all about my collection. Next time I’m in Poughkeepsie I’m definitely going to ask to see their own typewriter and mechanical calculator collection.

From there we grabbed some lunch and then went to the celebration itself. I ran into several folks I didn’t know worked out of Poughkeepsie, so those were all delightful surprises. Career-wise I’ve definitely gained value in meeting up with colleagues in-person from time to time, as it really does help solidify those bonds that keep us working well together at a distance. I also finally got to meet our fearless leader in IBM Z and LinuxONE, Ross Mauri!

And then there was cake! After which I took some time to meet with a couple other colleagues, and concluded my day meeting with a long time friend who came down to visit from the IBM Quantum division. We had coffee and then he graciously dropped me back off at the train station for my 5:30 train back to Trenton.

In all, a long day but one that was incredibly satisfying. And I already have a list of people to talk to and things to see during my next visit, maybe some time over the summer?

CPOSC 2024

Regional open source conferences are so important. I’m reminded of this yet again as I come home from another Central Pennsylvania Open Source Conference (CPOSC), which for the second year in a row aligned with our spring visit to Philadelphia. They may not have the numbers power to impress the marketing team or whoever is looking at statistics for event sponsorship, but as a speaker or an individual attendee, they are some of the most important events I participate in.

First, they tend to mostly attract locals, so you meet folks you won’t see at other conferences and allow you to get an idea for what’s popular and how they’re using technology in their region. Secondly, they tend to be inexpensive, most are under $100. This is in vast contrast to some of the larger events put on by major tech players, where a ticket can easily run into the thousands. Plus, even if you can’t afford that, all the events I’ve gone to also have generously granted free passes to folks from various demographics, ensuring that the attendees are a diverse crowd. They also often happen on weekends (CPOSC is on a Saturday), which means folks who can’t get off from work to attend events can participate.

I also feel like these conferences get me closer to what most folks are doing with open source software at their organizations now. They aren’t all showing off the newest things, but they are showing off things that are incredibly popular and broadly used, and that gives a more genuine snapshot of where the industry is, rather than where it may be going. But I think the most important thing for me though is discovering pockets of innovation that I wouldn’t have otherwise encountered. From the individuals developing new ideas to the small companies that sponsor these events having innovative business models, these events are always remarkable for learning fascinating new things that may be overlooked elsewhere.

AI has been a big topic at a lot of events, and it was interesting to see how it unfolded at CPOSC. One talk centered around the idea of creating a digital self using the AI technology of today, including voice synthesis services and LLM prompts that are fed a lot of personal data. It was an interesting talk, but definitely keeps us in uncanny valley. The next talk that included an AI focus was a panel made up of a family unit, a pair of married professors whose work is both in computing, and a son who works in the tech industry but doesn’t code. The son demonstrated using ChatGPT to create code from a library for a device he was testing, and with English he was able to explain what he wanted the code to do, and have it spit out the code to do it. The resulting discussion was around how we teach software development. How much of the fundamentals of coding do we teach now? Should we also be teaching LLM prompt engineering? It was an interesting discussion that compared this transition to the one to higher level languages beyond Assembly (a parallel I’ve made myself as well) and doubling down on the fact that we will need some folks whose job is software engineering, even if some of the coding can now be done by AI.

I think for me the more interesting question for me was how many doors this opens for folks who don’t know how to code, but for whom having code written for them would transform their ability to succeed. I’ve known so many people over the years who needed to learn how to code, but don’t enjoy it and wish they could have stayed on their original path in arts, sciences, or where ever. How many ideas in the sciences have we lost because the experts in their respective fields are too busy doing basic coding work to make their breakthroughs? Or worse, just gave up? Or wasted their time doing things manually, forsaking computers entirely? There is a need for fast, high quality code, but I think for most people the ability to further streamline their interactions with computers on their own terms with code developed by LLMs is an exciting prospect. I’ve spent a lot of time feeling a bit apprehensive about use of AI in technology, but I’ve definitely turned a corner to be my more hopeful self again.

My own talk at the event happened just before lunch, where I was talking about building your open source project for various architectures. It was similar to the talk I gave a few weeks before at SCALE, but with a few localized tweaks and improvements from the last time I gave it, slides are here: Will_your_open_source_project_run_on_a_mainframe_Or_on_a_smartwatch_-_CPOSC_2024.pdf.

I’ve had some good feedback, and more to respond to post-event via email. Overall, I’m thrilled to see how much interest there is in software testing these days, and that people are thinking beyond the defaults in order to bring in more advanced testing techniques and tooling.

Naturally, I also brought along my props. This time it was an IBM Power Systems tux penguin, the VisionFive 2 SBC, and the 3d-printed IBM z16 I keep at our townhouse in Philadelphia, except for special outings like this one.

The final talk I went to before the closing lightning talks was on “How to get your ideas implemented at your organization” and it gave me a lot to think about. Career development-wise I’ve been advised to get more methodical about stakeholder buy-in, especially as I pursue ideas that are not universally popular. The speaker outlined the strategies he’s come up with for being successful here, partially based on the time he spent as a Chief Innovation Officer. A huge part of this is just sitting down with people to listen to how your idea impacts them, incorporate feedback, and develop a sense of shared ownership for the idea. It gave me a lot to think about and helped solidify my own natural tendency to just reach out to people and ask. I think for me what would help the most is some training on how to be more tactful and polished when I approach people, since I can be very technical and direct by nature.

Of course, I also know people at CPOSC. I was able to meet up with several folks I know, including my long-time events-all-over pal Jason Plum of GitLab. CPOSC or the Philly Linux Users Group are where I get to catch up with most people I see there, so I always look forward to this opportunity to catch up.

I went to the after party for a bit to grab pizza and a beer while continuing chats with folks, including a few people I randomly ended up with as we walked over to the venue. I think we all have a natural tendency not to end up alone at events, so we latch on to a few people, which I absolutely do, but I also have grown comfortable with walking around alone and coming up with things to talk about with strangers. It’s a little anxiety-inducing, but it pays off in spades over time. Many long-time relationships have been forged after chance meetups in hallways.

My friend Will walked me halfway to the train station at the conclusion of my stay in Lancaster, which was a lovely time to catch up. The train ride home was uneventful, though it was a long day and I was tired, so I curled up with some podcasts for most of the journey home. We’ll see where this event lands next year and whether I’m close enough to attend, but it certainly was a delight to stop by two years in a row!

An electromechanical calculator

Back in August, Adam and I came across a mechanical calculator while picking up my freshly repaired IBM Selectric II from Berkeley Typewriter. I knew mechanical calculators existed, but I didn’t really know anything about them. Still, I filed it away in my “maybe some day” list, if I happened to come across one.

Fast forward to March 2024 and we’re sitting at the San Francisco airport waiting on a dreadfully delayed flight, and a fellow I know through the Philadelphia area Linux community reached out and mentioned he was helping with an estate sale, and came across some typewriters and asked if I’d be interested in any of them. I had less interest in the typewriters, but among the photos he shared was a mechanical calculator! I’m in. Bonus: I’m about to board a flight to Philadelphia! What timing!

It was a bit of a trek to get up to the estate, but I was greeted with what turned out to be an electromechanical calculator, meaning it has a small DC motor inside to move the mechanical components that were driven by a hand crank in other models. The trouble with this is that we’re looking at a motor that’s easily over 70 years old, and the power cable is cracked and unusable, so will need to be replaced for it to work as an electric device again. Thankfully, the mechanical components looked clean and intact, so I purchased it from the estate.

Once I got it home, the first step was to do a once-over cleaning-wise, starting with the case, which had been living in a barn and was too dirty for me to even be comfortable bringing it into the house. On a beautiful Sunday morning, the boys enthusiastically helped me with it.

From there, I could take a closer look at the machine, in all its glory!

It really is in nice shape, I’d argue even better than the one we saw at the typewriter shop. I still need to clean it up a bit more, but a once-over was good enough for now.

Sunday night I went into research mode to see what I could discover about it, especially when it came to getting it working. After doing enough web searching to know what to look for, I found a tip that told me to peek inside a slot on the bottom to find the model number and serial number. It took a flashlight and some wrangling, but I found it: Monroe Model LA5-200, serial number 437578.

The first things I learned were that the “A” stands for automatic, which means it has the motor in there. I also learned from John Wolff’s Web Museum: The Monroe Calculating Machine Company that the LA5-200 is “a later ten-column machine with … a few minor changes, but is otherwise identical to” the LA5-160, which is good for me, since the 160 is a lot more common.

Resource-wise, I’ve found:

Monroe Service Training Course Book 2: Models LA, LA-5, LA-6, LA-7, function, adjustment, nomenclature which has some excellent diagrams and things, which will be incredibly useful when I start working on it. These three images are from that guide, and were already helpful in my initial pass.

Additionally, there are a handful of LA5-160 YouTube videos showing some tear-downs and repairs, including this series from DJD Labs that I’m certain I will find useful!

Given how heavy it is, this will be staying at our townhouse in Philadelphia. So, it’ll be a project for when I’m here, which is good, because I already have plenty to keep me busy in California for the foreseeable future.

That’s a lot about the calculator, but I will admit that I didn’t leave the estate sale with just that one, I did bring home a typewriter too. It’s a 1967 Olympia SM9 (s/n: 3242067) and it was in great condition, aside from a very dirty case, that the boys helped me clean so I could bring it inside.

It’s a lovely typewriter, and it also came with a small pamphlet and cleaning kit!

I’ll also be keeping it here in Philadelphia. I’ll clean it up and get a new ribbon for it during our next visit. Amusingly, I now have two Olympias, and they’re both here. I’m thinking about ultimately giving it to Adam to use when he’s a little older, if his interest in mechanical typewriters holds.

The rest of our visit is pretty packed, including a couple work-related day trips, so I probably won’t get to work on these any more, but I did take some time the other day to finally set up a full Typewriter Hunter TypewriterDatabase account, which I’ve now populated with photos of my collection: 9 Typewriter Galleries » Hunter: Elizabeth Joseph

Hamantaschen and flight delays

Following my trip down to Pasadena for the Southern California Linux Expo, I had three days of work and then a couple days off which I spent with the kids while we prepared for a visit to Philadelphia.

Having worked through the weekend, taking a couple days off the following week was the most logical thing to do over all, but it really worked out this time. First, it was a huge help in preparing to fly to Philadelphia on Saturday morning. I can squeeze in all our prep on a couple of late nights, but having the daytime to do it was especially beneficial, no late nights for me!

I also finally found someone to help me with chores and organization projects around the house three times a week. We have a house cleaner come by every two weeks, which is a huge help, but working full time, caring for the kids in the evening, and doing all the daily chores meant I had very little other time in my week for either personal time or other projects we want to tackle. I know that a lot of folks live like this, and have much more physically demanding jobs, but it’s not the life I want for myself. Since we have the means to hire someone to help for a few hours a week, I was finally able to convince myself that it’s the right thing to do for our family right now.

My new helper came by on Tuesday to meet and make sure we were a good fit (both sides, personality and task-wise) and then I had her come by for a couple hours on Thursday and Friday. It was especially nice to have someone help me prep everything for the trip, that took a full two hours of chores off my list (or, more realistically, took and hour off and allowed me to finally have the stroller cleaned, which I always say I’ll do but never get around to).

The other thing of note last week was that Purim was coming up, and I wanted to make Hamantaschen with the boys. This is my third year doing it, and this year we had the added pressure of promising Adam’s teacher that we’d bring some by on Friday before we left to share with his class as a culture sharing activity. On Thursday morning after dropping Adam off at school, Aaron and I got to work on the dough, which needed to chill in the refrigerator for three hours.

After lunch, we got to work on the cookies! This year we went with two flavors, MJ picked up some cherry pie filling to try out, and I also thawed some of our home made plum jam. They both came out beautifully, this was definitely my best year yet. On Friday we brought several to Adam’s class, and then we were able to pack the rest of the ones we didn’t eat for our trip to Philadelphia (and actual Purim, which was on Sunday).

Speaking of plums, we also spent some time last week doing a bit of yard work. The plum tree really needed some pruning, and so did the apple tree. So I watched a YouTube video about pruning fruit trees and went to work chopping. I wanted to make sure I did enough so the trees aren’t weighed down (last year a branch on the plum tree snapped), but I also want to make sure I don’t inflict so much trauma on the tree that it fails to produce fruit for a couple years, the boys love those fruit trees! I won’t know for a couple months whether I succeeded, but they do look a lot better now. Plus, the boys were actually a big help, they helped haul the branches into the compost, and were hilarious little helpers as I also spent a bit of time pulling up weeds in the back yard.

Saturday we flew to Philadelphia, on a flight that was delayed by over 5 hours. Unfortunately the delay didn’t hit until just before boarding, so we were stuck at the airport for all that time trying to keep a three year old and a five year old entertained without relying too much on screens, which we’d have to do in the air. We began our adventure playing by the gate a bit, hoping for a quick departure, but as soon as it was clear that wasn’t possible, we made our way to a restaurant for a snack and change of scenery.

After some time there, it was off to another restaurant where the boys could get ice cream. The remaining time was spent at an airport lounge, which also wasn’t terribly exciting for them, but breaking up the 5 hour wait with multiple locations did help stave off a lot of the boredom. Honestly, the boys really handled themselves well, all things considered. The arrival into Newark was another challenge, it was 2AM by the time we got in, limited ground staff meant they sent the stroller to baggage claim rather than having it at the gate, so we had to encourage two sleepy kiddos all the way to baggage claim. Then the air train wasn’t running, so we had to rework our whole plan to pick up the rental car. And suffice to say, we didn’t plan on getting to the townhouse nearly 5AM. As a result, Sunday was a little rough.

We’re now in Philadelphia for a couple weeks. We have some plans to meet up with some folks, and I will be heading up to the Poughkeepsie office for an IBM System 360 celebration next week. I’m rounding out the trip by speaking at the Central Pennsylvania Open Source Conference (CPOSC) on Saturday, April 6th. It’s nice to be here again.


The last conference I went to before the COVID-19 pandemic began was the Southern California Linux Expo, which I wrote about here: SCALE 18x. Being on the cusp of the pandemic, it was a surreal experience. But it’s still one of my favorite conferences, so I thoroughly enjoyed our time there, and the ability to bring the whole family along, which at that time just included little Adam.

Coming back to SCALE this year was like a rite of passage in this new existence in a world with COVID-19 floating around. It was an absolute pleasure to see everyone who I only see at this conference, and generally to get back into the swing of things. Plus, the first day of SCALE landed on Pi Day, so I got to wear my new pi dress! Logistically, bringing the whole family along this time didn’t work out, but we’re definitely keeping it in mind for next year.

My first stop at SCALE was an Ubucon, which just like me, had returned to SCALE for the first time since the pandemic. I quickly caught up with several old friends from the community, and then was delighted to meet Cody Smith and Simon Quigley, who I’d only known through the Ubuntu community online. It was also nice meeting some of the folks who came to the event from Canonical and the various projects they’re working on around automation and tooling, a few of whom I had the pleasure of having dinner with when the first day of the event concluded on Thursday.

Ubucon itself kicked off with a talk from Jason Nucciarone, who was standing in for a colleague who couldn’t make it, where he discussed changes that have been made in recent years to revitalize the Ubuntu community. A big one was communication methods. When I was largely involved with Ubuntu, most of the communications took place over IRC, and like many communities, the Ubuntu community had been slowly drifting away from that. Some folks went to just using the Discourse forums, others had Telegram groups, some went off to pockets of Discord. I’ve remained on a rather silent IRC partially because I don’t have a lot of time to work on Ubuntu these days, so I hadn’t looked into where to go next. Turns out, they’ve started using Matrix and it has started picking up steam. Another thing they’ve done is started up in-person events again. There’s a new Ubuntu Summit that has now had two iterations in 2022 they met in Prague and in 2023 the event was held in Riga, Latvia. The Local Community (LoCo) communities have also received a bit of an injection of activity, which is nice to see. It’s definitely a different Ubuntu community from the one I stepped back from a few years ago, but that’s the nature of communities and I was swiftly reminded at the event that Ubuntu is turning 20 years old this year. There’d be something wrong if it was the same community I created a vBulletin account on all the way back in 2005.

I also enjoyed the talk from Simon on “Open Source is Not Just Code” where he spoke about his own journey. This is quite a bit different from the list-of-things talks I’ve seen (and given!) on this topic, and I think by sharing his story and journey we got a much more memorable talk. He spoke honestly about the challenges of starting contributing as a young age, and how his curiosity and willingness to give a variety of things a try paved the way for him to become a release manager for Lubuntu and hold several other roles while he was still a teenager. I can definitely speak to his enthusiasm as well, he was a big help when I was still running the Ubuntu Weekly Newsletter, and I’m so happy to see him still contributing and making such a big impact.

Perhaps my favorite talk on the second day of Ubucon came from my friend George Mulak. I’ve known George through the Ubuntu California team for years, but his talk was my first glimpse into some of the paid work he’s done over the years. His talk was on “Setting up an Ubuntu lab for seniors and the disadvantaged” where he shared details of the mobile computer lab that he ran for communities around the Los Angeles area to learn skills and help with technical literacy. It was a fascinating project, but also connected me with Ken VanDine who works at Canonical but also participates in a non-profit that does custom images (which can be used on USB sticks) for computers they install Ubuntu on and then provide to the community, to the tune of thousands per year. It’ll be an interesting thing to explore for Partimus, since our reduced scale these days means resurrecting our netboot imaging machine doesn’t make a lot of sense anymore.

The expo hall also opened Friday afternoon, and that’s where I had the pleasure of formally meeting Jon “maddog” Hall for the first time. He’s a hero of mine, but I never gathered up the courage to say hello. No more of that! We had a lovely chat about mainframes, and on Saturday morning I went to his talk, “How Is Linux Like a Player Piano?” I adored his talk. As a fellow vintage-mechanical-things enthusiast, his love for player pianos really resonated with me, and the tale he weaved around the role of open standards and patents in the shaping of what technologies succeed was a compelling one. I also appreciate that he concluded his talk with a nod to Hedy Lamarr, whose technical collaborators during her development of frequency hopping included George Antheil, who had used player pianos in some of his own work, which was another round about way for today’s technologies to be linked to those of the past. Unfortunately, now I kinda want to have a player piano, hah!

On the topic of meeting people I had the pleasure of meeting Tommy Chang, who is famous in the mainframe world for being a hobbyist who owns a couple of vintage mainframes. It’s always a pleasure to catch up with community members who share my passion for the platform, especially at an event like a Linux conference because we have this immediate kinship, and can geek out about various historic computing finds of late. We probably won’t found a computing museum together, but it’s fun to dream about.

My own talk was on Saturday afternoon, which was on building your open source project for various architecture and titled “Will your open source project run on a mainframe? And beyond!” I brought along my VisionFive 2 and my LEGO IBM z16, which I spread out on a mat I got from the arm developer program and allowed attendees to check out along with some stickers.

On Saturday I also went to a talk from Tyler Menezes on “Nurturing the Next Generation of Open Source Contributors” where he talked about CodeDay Labs where they provide successful mentorships between students and open source maintainers and projects. It’s a fascinating project that I’ll keep in mind once I can clear more time for volunteering again, but in the shorter term it was interesting learning what college students are struggling with today when it comes to contributing, and how project maintainers can help. He covered making sure you have a CONTRIBUTING.md and ARCHITECTURE.md files so students can find their way, which should also have a quick start for building a dev environment, including on Windows. He also shared how important it was to have properly functioning tests to help them avoid making simple mistakes that slow down the contribution process and ultimately lead to reduction in enthusiasm and drive. The final piece of advice was around criteria for good-first-issue bugs for newcomers, stating that they should be rather self-contained (one file to fix?), require minimal tracing through the code base, be clearly defined so you don’t need to ask questions, and make sure they’re still applicable, since it can be incredibly frustrating to fix a bug, only to discover later it had been fixed and not documented several months ago.

Part of my time this trip to Pasadena was also spent enjoying Pasadena itself. One evening I took a long walk around the downtown and to a park southwest of the venue where I got to enjoy a spectacular sunset before doing my only take-out meal of the weekend. On Saturday evening before meeting my friend Nathan Handler for dinner, I went on a quest to find a post card to send to the boys, and along the way found some rainbow abacus earrings (perfect for celebrating St. Patrick’s Day at a Linux conference!) and got to snag a couple green doughnuts from Randy’s Donuts.

Sunday began with a keynote from Casey Handmer on “Hacky solutions to real world problems: Applied Computing Past, Present, and Future” which I really enjoyed. I think like many of us we’ve slipped into a bit of a doom loop regarding the struggling middle class in the United States and promises of AI that have questioning deliverables so far. His talk was a breath of fresh air, positivity, and real world problems and solutions that are being worked on today. He began by talking about the recent deciphering of crushed, burned, scrolls from Herculaneum by students with the help of AI-assisted technologies (article). He also shared about his own company, Terraform Industries, that’s working to do “gigascale atmospheric hydrocarbon synthesis” with the intent of producing cheap energy while also cutting CO2. He also brought some statistics about how in just my own lifetime, global poverty has gone down significantly, and a big piece of the puzzle to going further is making sure all humans have access to energy. I found myself reflecting on how myopic my views have been by focusing on what feels so hopeless at home, and I was really inspired by not only his perspective, but the fact that his company is actually doing something real to change things.

I had the pleasure of chatting with Duane O’Brian at SCALE this year, and then attended his talk in the last slot of the day where he spoke on some analysis he’s been doing on where funding is coming from and going in the open source world. He scoured historical event and foundation websites going back 10 years to see where much of the funding had come from and assembled it in a series of spreadsheets and publicly available data. It was fascinating to see the information come together, though it wasn’t particularly surprising overall. He shared a handful of other efforts around both community-driven and more academic focused approaches to digging deeper into the data, but this was a nice beginning of a glimpse into where major events and organizations in the United States are getting their funding from.

With Pi Day on the first day of SCALE, we capped off the event with another holiday: St. Patrick’s Day! I was sad to miss a festival this year that MJ and our au pair attended with the boys, but I tried to make up with it by joining my friend Mickey Lyle for lunch and having a green beer.

The event concluded with a closing keynote from Bill Cheswick, which I only caught part of due to it going a bit long and me having a flight to catch. What I caught of it was a fun trip down memory lane, but by catching the flight I did I was able to be home in time to tuck Adam and Aaron in to bed Sunday night, which is precisely where I wanted to be.

Many thanks to all the volunteers who make SCALE happen, it was great to see so many of you!