-
Notifications
You must be signed in to change notification settings - Fork 10
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
Consider dual-license as Apache 2.0 #4
Comments
Matthew hello, sorry for late answer and thank you for your patience.
Sure I can add license ASL 2.0 to my project.
if it's still actual, could you please provide example or tutorial how I can make it. It would help me make it much faster and help avoid incorrect actions. my email - [email protected]
Четверг, 28 июня 2018, 19:01 +03:00 от Matthew Burgess ***@***.***>:
LIVR looks like a great tool for data validation and we are looking at it as a possible integration with Apache NiFi, but I don't think the Artistic License (even 2.0) is fully compatible with the ASL 2.0, and/or accepted by the Apache Software Foundation (please correct me if I'm wrong).
Is it possible to (and if so, would you please consider) also license this project under ASL 2.0?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub , or mute the thread .
Best regards!
|
Hello @vlbaluk, I follow this issue with interest. You ask about a sample to include the ASL2.0 license, I found the following sample from https://www.apache.org/licenses/LICENSE-2.0 Do you think is that okay for you? Thanks a-lot for this nice software.
|
LIVR looks like a great tool for data validation and we are looking at it as a possible integration with Apache NiFi, but I don't think the Artistic License (even 2.0) is fully compatible with the ASL 2.0, and/or accepted by the Apache Software Foundation (please correct me if I'm wrong).
Is it possible to (and if so, would you please consider) also license this project under ASL 2.0?
The text was updated successfully, but these errors were encountered: