This looks like a cool project. However, this project is missing a license file which is necessary for others to build upon this repo. A contributor can easily license this repo through the GitHub web interface by creating a file named LICENSE then selecting a template license from the menu that appears to the left. I highly recommend the ‘MIT license’, the ‘BSD 2-clause license’, the ‘BSD 3-clause license’, the ‘ISC license’, the ‘Apache 2.0 license’, or another “permissive” license. I highly recommend against “copyleft” licenses, such as the GNU GPL, since they do not reflect the true spirit of open source software and since such licenses are harmful to commercial software projects that would like to include the licensed work. So, to foster the integration of this code into other projects, I recommend the MIT license be given to this work.
Also, in addition, if this project used code from Atom/One-Dark-Syntax, then this repo must reproduce its license as it is required per the terms of using the code.
This looks like a cool project. However, this project is missing a license file which is necessary for others to build upon this repo. A contributor can easily license this repo through the GitHub web interface by creating a file named
LICENSEthen selecting a template license from the menu that appears to the left. I highly recommend the ‘MIT license’, the ‘BSD 2-clause license’, the ‘BSD 3-clause license’, the ‘ISC license’, the ‘Apache 2.0 license’, or another “permissive” license. I highly recommend against “copyleft” licenses, such as the GNU GPL, since they do not reflect the true spirit of open source software and since such licenses are harmful to commercial software projects that would like to include the licensed work. So, to foster the integration of this code into other projects, I recommend the MIT license be given to this work.Also, in addition, if this project used code from Atom/One-Dark-Syntax, then this repo must reproduce its license as it is required per the terms of using the code.