Closed ajh123 closed 6 months ago
Yes, honestly, I just forgot about it here. oops.
I'll probably pick single MIT license for this project, just because i think it makes a lot of sense for a user-facing application like this.
Closed by 65bfa8fcc1200b48c459f71fdfd2bcaff2ab295a
Adding a license will control what people can legally do with your code. Currently we are not legally allowed to install your software, even though the code is public on GitHub it doesn't mean we can use it. (see more: https://choosealicense.com/no-permission/) Currently you are legally liable for any issues that occur, this may become an issue in the future if no license is applied.
To add a license create a file called
LICENSE
inside the root of this repository and paste the content of the license of your choice inside it (and modify placeholders if there are any). To choose a license visit https://choosealicense.com.In the Rust world it is common to have the MIT (found at https://choosealicense.com/licenses/mit/) and Apache 2.0 (https://choosealicense.com/licenses/apache-2.0/) licenses. This means instead of having a signal
LICENSE
file, you would create two files one calledLICENSE-MIT
and the otherLICENSE-APACHE
.Here is an example of what it will look like: