Needs a license file

[darrenarmstrong85]

License requirements for this repo should be documented. Usually done by including a LICENSE plaintext file at top level of repository.

Others can then see what is expected of them if they use or contribute to the repository.

Possible suggestion based on pre-existing uses: MIT license?
https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project

If you’re starting from a blank slate, it’s hard to go wrong with the MIT License. It’s short, very easy to understand, and allows anyone to do anything so long as they keep a copy of the license, including your copyright notice. You’ll be able to release the project under a different license if you ever need to.

[SukumarMehta]

Hi @ryanhamilton - is there a plan to document the license requirements for this repo?

[darrenarmstrong85]

A note in passing was added here, but it could be made easier to find...

https://github.com/timeseries/kdb/blob/03dc2048d0251ba93df99a4a0a0dfbb64f8e9176/qunit/qunit.q#L11