-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include a license file #54
Comments
@kaj Was the the omission of a license here intentional? |
Not more than that I thought the extra files would be redundant. The cargo manual says:
... so I though that since the |
* Issue #54: Add a LICENSE file. * PR #57: Allow channel string in rgba() * Issue #58: Let ructe::Error implement std::error::Error. * Issue #59: Improve `@import` and media rules. * Implement `@error` and `@warn` directives. * Improve string unquoting, including multi-position numerical escapes. * Improve at-rule parsing. * Fix strange operator handling. * Implement modulo operator. * Fix line breaks in comments. * Handle bad argument to `random()` function. * Update test suite to e9e219bdf (2019-12-19). * Some refactorig and clean-up. Thanks to @emielbeinema, @maxbrunsfeld, and @Boiethios for contributed code and suggestios.
The package's
Cargo.toml
specifies a License ofMIT/Apache-2.0
. But I think that conceptually, "MIT" and "Apache-2.0" are only templates for licenses, and the standard practice is to include in the repository (and in the published crate) a file calledLICENSE
containing your actual license (usually just the MIT/Apache template, with your name and the year filled in).When you get a chance, would you be up for adding a
LICENSE
file to your repo, to eliminate any legal issues with using this library?The text was updated successfully, but these errors were encountered: