When I introduced the OSMF, many people told me it would not work unless some sort of license enforcement mechanism was in place. I disagreed and instead focused on education. It turns out we were both right.
Eight months ago WiX had 99 sponsors. Today it has 304. The Open Source Maintenance Fee is working and ready.
Since it's release almost a year ago now, I've been collecting feedback on the Open Source Maintenance Fee. Earlier this week, I integrated a piece of feedback that deserved to bump the version number. Let's talk about the change that produced OSMF v1.1.
We don't use Tailwind CSS at FireGiant, but I can't stop thinking about it. As a CEO responsible for keeping the lights on, and as a long-time Open Source maintainer, the situation is uncomfortably familiar. What does it mean that Tailwind is so popular and still unsustainable?
It's been a bit over a month since the Open Source Maintenance Fee was introduced into the WiX Toolset. So, let's take a moment to check in and see how things are going.
Today I'm launching an idea three years in the making. The Open Source Maintenance Fee tackles the sustainablity problem by charging a small fee for use of an Open Source Project. What? Why? How? All answered in more detail below.
