You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a template project so is meant to be used as a starting point for your rescript project. However, there is still a small amount of code and config -- I'm wondering if it might be better to add a LICENSE file (MIT/Unlicense/BSD etc) to this repository or explicitly state somewhere that the code in this repo is in the public domain.
Wait a sec, actually I do notice that package.json has the license key set to MIT. This could be interpreted as the template suggested a default key of MIT. It could also mean that the template code itself has been placed in MIT.
By placing a LICENSE file or explicitly indicating that this code is in the public domain will be useful to potential users of this template. The template is pretty trivial currently so one could argue all this is much ado about nothing. But in the future as the template becomes more sophisticated, it would be useful to know the license for this template.
The text was updated successfully, but these errors were encountered:
This is a template project so is meant to be used as a starting point for your rescript project. However, there is still a small amount of code and config -- I'm wondering if it might be better to add a LICENSE file (MIT/Unlicense/BSD etc) to this repository or explicitly state somewhere that the code in this repo is in the public domain.
Wait a sec, actually I do notice that
package.json
has the license key set to MIT. This could be interpreted as the template suggested a default key of MIT. It could also mean that the template code itself has been placed in MIT.By placing a LICENSE file or explicitly indicating that this code is in the public domain will be useful to potential users of this template. The template is pretty trivial currently so one could argue all this is much ado about nothing. But in the future as the template becomes more sophisticated, it would be useful to know the license for this template.
The text was updated successfully, but these errors were encountered: