I don't use Kinopio for everything, but when I need to arrange ideas in a 2D way and think about webs of relationships, it's been an amazing addition to my set of "tools for thought". Thank you for all of your work on it <3
Making the Kinopio source code public
21–30 of 63 posts
Re: Making the Kinopio source code public
#22I don't use Kinopio for everything, but when I need to arrange ideas in a 2D way and think about webs of relationships, it's been an amazing addition to my set of "tools for thought". Thank you for all of your work on it <3
You’re very welcome :)
Re: Making the Kinopio source code public
#23I love Kinopio and I really appreciate being able to look around the code and perhaps even help make it better. Hopefully, this will spur innovations and new updates.
I’m looking forward to it too
Re: Making the Kinopio source code public
#24I've been following this project for a while - very excited to see this and even more excited that it is Vue!
I’m a big vue fan, it’s a great oss success story and feels good not to use any facebook tech
Re: Making the Kinopio source code public
#251. Not technically open source since you can’t use for commercial, but ignoring the pedantry. 2. You’re clearly worried about the commercial risk, why even do it? You have a section on this but even after reading - seems like a non answer.
> The big benefit of open source for me is that it’s another way to share the work that goes into Kinopio.
Re: Making the Kinopio source code public
#26Sorry to be pedantic, but since the licence forbids commercial use, the software isn't open source, but rather just source-available.
thanks for letting me know, I've changed the title of the post to "Making the Kinopio Source Code Available"
Re: Making the Kinopio source code public
#27Sorry to be pedantic, but since the licence forbids commercial use, the software isn't open source, but rather just source-available.
We definitely need a term, more accurate than source-available, that describes software whose usage and improvements can only orbit in non-commercial space.
For non-software creative works, we have Creative Commons NonCommercial licenses.
Re: Making the Kinopio source code public
#28Sorry to be pedantic, but since the licence forbids commercial use, the software isn't open source, but rather just source-available.
thanks for letting me know, I've changed the title of the post to "Making the Kinopio Source Code Available"
You might be interested in fair.io, launching next month. We ran into a similar problem a year ago that ended up stirring up a lot of drama, so we are now promoting the term Fair Source instead of Open Source.
Fair Source: https://fair.io/
Our drama: https://news.ycombinator.com/item?id=36971490
Lots more context: https://openpath.chadwhitacre.com/2024/the-historical-case-f...
Re: Making the Kinopio source code public
#29Sorry to be pedantic, but since the licence forbids commercial use, the software isn't open source, but rather just source-available.
We definitely need a term, more accurate than source-available, that describes software whose usage and improvements can only orbit in non-commercial space. For non-software creative works, we have Creative Commons NonCommercial licenses.
Yes! We aim to launch https://fair.io/ next month to promote the term Fair Source for this purpose. Early feedback is guardedly positive, e.g., ESR's take was "very clever."
https://openpath.chadwhitacre.com/2024/the-historical-case-f...
Re: Making the Kinopio source code public
#30Sorry to be pedantic, but since the licence forbids commercial use, the software isn't open source, but rather just source-available.
We definitely need a term, more accurate than source-available, that describes software whose usage and improvements can only orbit in non-commercial space. For non-software creative works, we have Creative Commons NonCommercial licenses.
Why? We all know what "source available" mean and that it's not really open-source.