[jimjag]

Yet another Github project that could be useful, except that there is no explicit license. Which means it's under traditional copyright.

[rmc]

Not quite. Since it's on GitHub, the terms and conditions for uploading, means that github users have the permission to view and fork the repository. https://help.github.com/articles/open-source-licensing/

[jimjag]

Which really means nothing. It certainly is not an Open Source or Free Software license. View and fork does not mean use. Or distribute, etc...

[thephyber]

No longer an issue. MIT License.

https://github.com/Max00355/HTTPLang/blob/master/LICENSE.md

[baldfat]

https://help.github.com/articles/open-source-licensing/

[carbocation]

That leaves me more curious now. It contains the following:

> "Even if this is what you intend, if you publish your source code in a public repository on GitHub, you have accepted the Terms of Service which do allow other GitHub users some rights. Specifically, you allow others to view and fork your repository."

I wonder what it means, from the standpoint of using or modifying code within the copyright framework, to have this right to "fork your repository?"

[MatthewWilkes]

It doesn't grant any right to use or modify the code, just to re-host it for viewing. Say someone puts up a repository they don't intend to, then deletes it. This right ensures they can't demand you delete it if you hit the fork button in time.

[wyldfire]

> I wonder what it means, from the standpoint of using or modifying code within the copyright framework, to have this right to "fork your repository?"

It's a conflict between the hosting T&S and the copyright of a derivative work. Just because Github says you can, doesn't mean you can.

[WormyMcSquirmy]

So raise a pull request to add one.

[wyldfire]

https://github.com/Max00355/HTTPLang/pull/11