Open Source

The 2020 election for the Open Source Initiative Board of Directors is rapidly approaching. Before going to IBM FastStart in Las Vegas last week, I nominated myself for a seat on the board as an Individual Member. I spoke with a few friends in the months prior to submitting my nomination. It sounds like OSI could use my help. “Open source software has done nothing but provide opportunity after opportunity in my life. It should be cared for and maintained so that everyone willing can benefit from it as much as I have (hopefully more).” —Chris Short ...

A former co-worker and now friend has a tagline, “Every day is a school day.” I remind myself of this fact almost every time I learn something new. 2019 was the hardest year of my life. I’d like to share some things I picked up on this most recent journey around the sun we call 2019. I’ll make some predictions about 2020 in the process too. Kubernetes Last year, I said I thought Kubernetes would get easier. That didn’t happen. It’s not any easier to use Kubernetes. But, to be honest, I’m not sure if Kubernetes itself will ever get easier, it’ll be us getting more used to using it and building tools around it. I still think vendors need to focus on ease of use if they want to see their products getting adopted. But, the project in general, might not need to worry about ease of use. This seems like hair splitting, sure, but, it seems like Kubernetes did manage to penetrate every sector of tech in 2019. This is going to lend itself to a big ole ecosystem of people and orgs working on ease of use on behalf of the community. ...

Just when you thought a toxic, old, white guy with lousy hygiene was going to dominate the news this week, in walks Seth Vargo. On Thursday, Seth Vargo, a former Chef employee, learned something he wasn’t comfortable with about code he’d written. Seth discovered Chef had an active contract with the US Department of Homeland Security’s Immigration and Customs Enforcement (yes, that one). Seth then did something rather extraordinary. He yanked his code (including chef-sugar) from GitHub and RubyGems. This resulted in many production systems going offline across the globe. We could see some metrics about impact in a lawsuit at some point. When DM’ing Seth early Friday AM he told me, “It’s almost certain that Chef is going to sue.” ...

I was working on things for work (as one does) when it dawned on me. Very few folks understand the difference between upstream and downstream as it relates to open source software. I used Red Hat projects as a pointer. Here is the output of that effort (which was scratching the surface). Upstream vs. Downstream Upstream vs. Downstream is confusing at times. But, for the bigger Red Hat projects this holds true: ...

Since Sunday afternoon, I’ve been in a whirlwind of meetings, discussions, and calls about IBM’s plan to acquire Red Hat for $34 billion. My mind has been racing but, after some consideration, I’ve decided to share my thoughts as a narrative timeline. Trust me when say that I have given this format considerable thought. It is likely the safest way (regulatory-wise) to deliver my thoughts on the topic. I would like to point out that I have updated my disclaimer and this site’s terms. My views do not reflect those of my employer or entities I’m affiliated with. Names are withheld for obvious reasons. ...