2 ms·
I don't get into the OSS religious arguments. I consider almost all my stuff to be "open source," even the couple of projects that are "source available."[0] I
by ChrisMarshallNY 5y ago
I don't get into the OSS religious arguments.
I consider almost all my stuff to be "open source," even the couple of projects that are "source available."[0] I think that it's important to make it all available, if I will call it "open source," but there's no reason, in my mind, to make it so that people can just take my work and use it commercially.
That said, I generally like to use the MIT license, because I don't like coercive licenses. I just don't like it when people try to coerce me, so I won't do it to them.
I am currently working on a non-open-source/non-source-available project. Considerable parts of it are open-source (MIT license), but the core app code, as well as a modified variant of my BAOBAB server[1], are proprietary and locked away.
I don't think any of it is particularly awesome or worthy of secrets, but the folks I'm working with aren't as sanguine as am I, when it comes to opening the kimono, and I'll respect their wishes. I worked for years, for a corporation that had Fort Knox trade secret security. It's something that I'm used to doing.
[0] https://github.com/RiftValleySoftware/ambiamara https://github.com/RiftValleySoftware/ambiamara
[1] https://riftvalleysoftware.com/work/open-source-projects/#baobab https://riftvalleysoftware.com/work/open-source-projects/#ba...