Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For my own engine I was looking at my options for the future.

If I would ever release it with restrictions, I would call it "source available" or something like that.

I think as a community, we should also have a strict term for a project with source code, but too restrictive to be called open source.

From my search, "Source Available" was the best terminology, unless someone knows a better one.



I tend to like "source available with permissive license", but I agree that this class of license needs a catchier name.

EDIT: maybe "Awesome Source" ;-)


But it's not just "Source Available". You can modify source code, fork it and use your own version of the engine, and so on. The only restriction that you can't SELL the engine itself. What is the right name for that if not "Open source"?


"permissive", "really awesome", "generous", many other things.

Not "open source". That term has a meaning, and it's very important that meaning doesn't get diluted.


Perhaps "permissive source available"?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: