What makes Open Source projects work? Today we discuss open source business models, motivations, what and how these projects work.
We moved from that into testing quality maintenance and ultimately SpaceX and Tesla. This conversation dives into how Elon Musk is transforming the industries that he’s in by looking at the delivery process.
How can promotion boards be hostile or hurtful to open source technology? We talk about the dynamics of corporate support in open source technology, and if being rewarded for internal work at companies translates into challenges for open source technology.
This discussion starts to peel apart what makes open source technology sustainable, and what it works for. We bring up an analogy of a lava lamp where things heat up and then cool down as part of a natural cycle, which can be a normal cycle for all software, and that led us back to how promotion boards work.
We covered a lot of ground through the dynamics of corporate software governance and open source and interweaving those together.
We talk about software licensing in open source, and what it means to the broader market. In fact, we cover how it’s changing what the market actually is!
This is not not just open source licensing in general because at the end we didn’t care about the license. We are more concerned about utility, serviceability and operability of the products we use. We need to understand whether or not we can rely on them!
In short, the supply chain of the software was much more important than the licenses of the software
Our scheduled topic was supply chains generally, but the Log4Shell vulnerability dominated the discussion. We dove into the challenge of patching and fixing a library that is literally in nearly every device or service for years and years.
That led us to supply chains in the context of software, and specifically Java Log4j. This is a critical topic and our conversation about it was very thoughtful. We really covered the angles of what it takes to produce and maintain a supply chain for software. Then we discussed alternatives and things to consider when you building anything: software products or physical products in which embedded systems and components impact your designs.
In this episode, we’re discussing how it could be possible for you, the consumer, to take products built and maintained by a company and maintain, change, own, and extend the product’s use past the life of the vendor of that product by getting fixes and repairs that the vendor doesn’t want to offer. Right now, the right to repair is essential from a consumer perspective, yet these rights seem to erode further every day. We are living in a society that doesn’t value the right to repair as a product feature, and we want to ignore that and get things that are easy to use and disposable.
As a consumer and as a company creating products, it makes me wonder if this narrative will switch. What will drive people to decide they want to control and to be able to repair, not just outsource, all of these components, assuming that they can quickly replace the device or patch system or get another service? I think we’ve been overlooking a lot of the complexity that’s building up in the ecosystems we have around these products, but this complexity is also the thing that makes them so hard to repair even if you had the right.
We have a lot to think about!
Please listen to the longer podcast where we talk about these issues and join us at the2030.Cloud.
Rob Hirschfeld and Stephen Spector announce the launch of a new community/event called Cloud 2030. This concept is based on the past Cloud 2020 event held at Switch in 2010 focused on the future of cloud.
In addition to being a global community of cloud operators this will operate as en event without a fixed schedule. Come join at cloud2030.mn.co to learn more.