Alex King | Interviews |

King: I'm being pragmatic to my approach to licensing. I like Open Source, I like contributing things that has Open Source. I like the idea of people building on each other's work, rather than everybody having to recreate the same thing. I think tomorrow, we're going to release a product that we built, called Capsule. It's a new one, it's in the demo, here. It's a developer journal, that we're going to release as the free WordPress theme. We're not trying to make any money on it. We used a ton of different libraries and various Open Source components to put this thing together. There's a code editor. We're not going to create our own code editor , there's already one out there, we built it in there. But the market library we didn't have to write that, there's one out there. There's a JavaScript libraries for various features, there's free Open Source font icons that we're using. And I love that we're able to take all of these things that already existed in different forms, and put them together to create something. I think that is kind of how—we're solving a new problem. And so basically our default stamp unless there's something that's partially proprietary for our client or things like that, is when the code we built the new library and different things like that, we just put them out on RK Hub, and that really stuck. As much as we can, it Open Source. At the same time I'm not opposed to commercial either. I think that commercial software has a place to it, I don't believe it's been fully commoditized. I think that you can have commercial that's not just a hosted service and that's a legitimate thing to have as well, not everything has to be Open Source. Personally I believe that it doesn't make sense to invest time and energy, or put data into systems that may not be sustainable. So I care a lot about licensing from that perspective, and in my own usage. And we've created with our attorney and license that we're planning to use for some of our future commercial no WordPress things. That basically says this is a commercial license. It's not Open Source, but you are allowed to make modifications, you're allowed to distribute those modifications as long as they do not—in both cases as long as they do not implement paid features that are - like give them a higher version of the product. And that if we ever stop maintaining the product, then the code will have an Open Source license attached to it. So if Crowd Favourite ceases to exist as a business entity, or declares something as end of life or something like that, then if we release it under this license everyone will, all customers will automatically get an Open Source license for that code. So I think that as a developer, you have that type of responsibility to the people that are going to be using your software. Obviously, an Open Source license gives you that, with or without any reservations. But I don't think that - I think the viability of a project is not tied as much to its licensing as it is to its community.#